[kwin] [Bug 372576] Present Windows lags when closing window

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=372576

--- Comment #26 from Martin Flöser  ---
I don't think we will add a workaround. This issue is only present on one
driver on X11. With the same driver on Wayland this issue doesn't exist. Adding
a workaround has the risk of breakage in other areas. As we are feature Frozen
on X11 and most devs are on Wayland I at least consider the risk of breakage as
too high.

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

[Breeze] [Bug 379637] breeze-gtk should draw shadows for client-side-decorated windows

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=379637

Martin Flöser  changed:

   What|Removed |Added

 Resolution|LATER   |FIXED

--- Comment #21 from Martin Flöser  ---
No, gtk nowadays doesn't add shadows if the window manager does not announce
support for the gtk specific property.

We really need to stop thinking KWin could do anything here. I analyzed this
whole mess years ago. If there were any easy solution it would have been added.

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

[digikam] [Bug 403569] Error while uploading image to google picasa/photos

2019-02-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=403569

Maik Qualmann  changed:

   What|Removed |Added

 CC||philippe.roub...@free.fr

--- Comment #3 from Maik Qualmann  ---
*** Bug 404138 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 404138] can't connect to my account

2019-02-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=404138

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||metzping...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #2 from Maik Qualmann  ---


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

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

[kwin] [Bug 404152] Support for pointer_axis_descrete needed

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=404152

Martin Flöser  changed:

   What|Removed |Added

Summary|Apps running on Xwayland|Support for
   |scroll twice on every   |pointer_axis_descrete
   |second mouse wheel movement |needed
  Flags||Wayland+, X11-

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

[kwin] [Bug 404146] Tabbox kcm incorrectly falls back to informative on broken theme

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=404146

--- Comment #3 from Martin Flöser  ---
Well the fallback will have to be removed.

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

[kwin] [Bug 403601] KWin crash on boot

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=403601

Martin Flöser  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #5 from Martin Flöser  ---
Distribution issue.

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

[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402328

d...@donstrenzwood.com changed:

   What|Removed |Added

 CC||d...@donstrenzwood.com

--- Comment #53 from d...@donstrenzwood.com ---
(In reply to lurulf from comment #46)
> (In reply to Andras from comment #28)
> > Created attachment 117491 [details]
> > plasma-discover 5.14.5 crashes on launch (after reinstalling it)
> > 
> > My system
> > plasma-discover 5.14.5
> > Qt Version: 5.11.2
> > KDE Frameworks Version: 5.54.0
> > Kernel Version: 4.15.0-43-generic
> > Distribution: KDE neon User Edition 5.14
> > 
> > Previously it worked however I reinstalled Discover trying to resolve this
> > bug: https://bugs.kde.org/show_bug.cgi?id=399981.
> > It's probably fwupd related indeed because Discover starts after:
> > fwupdmgr refresh
> > fwupdmgr update
> 
> Yes, I can confirm the same. An available update for Logitech Unifying
> Receiver in Fwupd seems to crash Discover. After fwupdmgr refresh &&
> fwupdmgr update, Discover does not crash.

Same here. Same bug fixed same way with update to the Logitech Unifying
Receiver.

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

[latte-dock] [Bug 399149] Wine application with latte-dock master and plasma 5.14 beta always uses cpu

2019-02-09 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=399149

--- Comment #36 from Michail Vourlakos  ---
(In reply to Alexandre Pereira from comment #35)
> Hi,
> 
> Can you give some info as how and where it was resolved ?
> 
> I still suffer from this problem :( Only workaround I found was using the
> app through explorer.exe virtual desktop, but its bad, wine's virtual
> desktop is really bad at managing windows :( ( really hurts my workflow ).

It could be, does that application has an option to hide that clock in order to
check this out?

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

[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue

2019-02-09 Thread Max Di Cosimo
https://bugs.kde.org/show_bug.cgi?id=402328

Max Di Cosimo  changed:

   What|Removed |Added

 CC|mdicos...@yahoo.com |

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

[plasmashell] [Bug 404165] New: Plasman crash upon clicking on Audio Application menu

2019-02-09 Thread Vishnu
https://bugs.kde.org/show_bug.cgi?id=404165

Bug ID: 404165
   Summary: Plasman crash upon clicking on Audio Application menu
   Product: plasmashell
   Version: 5.14.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vishn...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.14.5)

Qt Version: 5.12.1
Frameworks Version: 5.54.0
Operating System: Linux 4.20.6-artix1-1-ARTIX x86_64
Distribution (Platform): Archlinux Packages

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

There was a video file I was playing using 'mpv', and then I clicked the
following button:

Audio Tray > 'Applications' tab > The three-line menu button of the mpv
application

- Unusual behavior I noticed:

The plasma panel disappeared and came back

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

Thread 16 (Thread 0x7f0148c94700 (LWP 10002)):
#0  0x7f01bab977a4 in read () at /usr/lib/libc.so.6
#1  0x7f01a4d026e2 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-12.2.so
#2  0x7f01a59cf75f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7f01a59d01d1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f01a59d0291 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f01a59de7ae in  () at /usr/lib/libpulse.so.0
#6  0x7f01a4d3259c in  () at /usr/lib/pulseaudio/libpulsecommon-12.2.so
#7  0x7f01b9dbba9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f01baba6b23 in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f019088a700 (LWP 9781)):
#0  0x7f01b9dc1afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f01baec2bfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01baec2cea in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f01bcc7692d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f01bcc76b9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f01baebc91c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f01b9dbba9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f01baba6b23 in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f0149495700 (LWP 8572)):
#0  0x7f01b9dc1afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f01baec2bfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01baec2cea in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f01bcc7692d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f01bcc76b9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f01baebc91c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f01b9dbba9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f01baba6b23 in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f01777fe700 (LWP 6244)):
#0  0x7f01b9dc1afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f01baec2bfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01baec2cea in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f01bcc7692d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f01bcc76b9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f01baebc91c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f01b9dbba9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f01baba6b23 in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f01767fc700 (LWP 6243)):
#0  0x7f01b9dc1afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f01baec2bfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01baec2cea in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f01bcc7692d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f01bcc76b9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f01baebc91c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f01b9dbba9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f01baba6b23 in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f014b8b9700 (LWP 6228)):
#0  0x7f01b9dc1afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f01baec2bfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f01baec2cea in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f01bcc7692d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f01bcc76b9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f01baebc91c in  () at 

[kwin] [Bug 372576] Present Windows lags when closing window

2019-02-09 Thread Madhav Kanbur
https://bugs.kde.org/show_bug.cgi?id=372576

Madhav Kanbur  changed:

   What|Removed |Added

 CC||abcd...@gmail.com

--- Comment #25 from Madhav Kanbur  ---
Still present in Plasma 15.14.5, Arch linux, intel modesetting. It's been
almost 2 years since this bug was reported. I know that it's not a major bug,
but it sure is annoying for intel users. Can we please get the workaround
merged? Thanks

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

[kmymoney] [Bug 391163] Can't adjust font in reports

2019-02-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=391163

--- Comment #5 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 402516] Logout from kde and show a black page on Fedora-KDE-Live-x86_64-28-1.1 Virtual machines installed on Qemu and VMware

2019-02-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402516

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kmymoney] [Bug 403396] KMyMoney 5.0.2 crashes on import of OFX file

2019-02-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=403396

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

2019-02-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=403596

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen

2019-02-09 Thread Eike Hein
https://bugs.kde.org/show_bug.cgi?id=396697

--- Comment #17 from Eike Hein  ---
Investigation is half the battle, thanks for this! One of the reasons I've been
ignoring this issue for so long, to be honest, is that I moved 8500km and spent
the last three years with only a laptop - no multi-monitor. But over the last
few months I bought first a TV, and now a new laptop with a painfree-working
HDMI-out. I can finally test this now and will move it higher on my todo, sorry
for the wait!

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

[Powerdevil] [Bug 403776] Powerdevil suddenly crashes during normal operation

2019-02-09 Thread Peter J. Mello
https://bugs.kde.org/show_bug.cgi?id=403776

Peter J. Mello  changed:

   What|Removed |Added

 CC||ad...@petermello.net

--- Comment #3 from Peter J. Mello  ---
I'm seeing the same behavior (I think) on my Lenovo ThinkPad T420s running
Kubuntu 18.10 Cosmic. Including the trace in case it can aid in isolating the
issue.

Application: org_kde_powerdevil (org_kde_powerdevil), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e0366b840 (LWP 5552))]

Thread 6 (Thread 0x7f5dfa093700 (LWP 23743)):
#0  0x7f5e09a156d9 in __GI___poll (fds=0x7f5de4007030, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5e001709b1 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f5e001621e0 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f5e0016282e in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f5e001628e0 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f5e001708f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f5dfac8f6f8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so
#7  0x7f5e089fb164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f5e09a21def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f5dfb7fe700 (LWP 5634)):
#0  0x7f5e09a10f64 in __GI___libc_read (fd=13, buf=0x7f5dfb7fdc90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f5e0776a180 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e0772491f in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e07724df0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5e077251d2 in g_main_loop_run () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5e0079d7b6 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7f5e0774d135 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f5e089fb164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f5e09a21def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f5dfbfff700 (LWP 5633)):
#0  0x7f5e09a10f64 in __GI___libc_read (fd=11, buf=0x7f5dfbffeca0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f5e0776a180 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e0772491f in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e07724df0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5e07724f6c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5e07724fb1 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f5e0774d135 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f5e089fb164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f5e09a21def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f5e0135f700 (LWP 5630)):
#0  0x7f5e09a156d9 in __GI___poll (fds=0x7f5df4012930, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5e07724e46 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5e07724f6c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5e09f3815b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5e09ee516b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5e09d340b6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5e0a1f1545 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f5e09d3dc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5e089fb164 in start_thread (arg=) at
pthread_create.c:486
#9  0x7f5e09a21def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f5e01f70700 (LWP 5577)):
#0  0x7f5e09a156d9 in __GI___poll (fds=0x7f5e01f6fc78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5e090df917 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f5e090e153a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f5e02ed2159 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f5e09d3dc87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5e089fb164 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f5e09a21def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f5e0366b840 (LWP 5552)):
[KCrash Handler]
#6  0x7f5e09d87ac3 in QHashData::nextNode(QHashData::Node*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5e0af18543 in
PowerDevil::PolicyAgent::onServiceUnregistered(QString const&) () at

[plasmashell] [Bug 403989] Popup animation is not smooth

2019-02-09 Thread Ivan Safonov
https://bugs.kde.org/show_bug.cgi?id=403989

Ivan Safonov  changed:

   What|Removed |Added

 CC||safonov.iva...@gmail.com

--- Comment #2 from Ivan Safonov  ---
Same issue on Kde Neon

Operating System: Kde Neon 5.14
KDE Plasma Version: 5.14.5
Qt Version: 5.12.0
KDE Frameworks Version: 5.54.0
Kernel Version: 4.15.0-45-generic
OS Type: 64-bit

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

[frameworks-kwidgetsaddons] [Bug 404150] KDE printing properties dialog is showing a misleading preview of different pages per sheet layouts

2019-02-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=404150

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #2 from Christoph Feck  ---
The print dialog is QPrintDialog from Qt libraries. Please report this issue
directly to Qt developers via https://bugreports.qt.io/

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

[dragonplayer] [Bug 320003] Audio track cannot be changed

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=320003

Neousr  changed:

   What|Removed |Added

 CC||neo...@protonmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Neousr  ---


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

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

[dragonplayer] [Bug 327586] Dragon player cannot see all available audio channels

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=327586

Neousr  changed:

   What|Removed |Added

 CC||u.alma...@gmail.com

--- Comment #4 from Neousr  ---
*** Bug 320003 has been marked as a duplicate of this bug. ***

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

[kile] [Bug 404164] Crashes when saving document upon closing

2019-02-09 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404164

John Scott  changed:

   What|Removed |Added

   Platform|Debian stable   |Debian testing

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

[kile] [Bug 404164] New: Crashes when saving document upon closing

2019-02-09 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404164

Bug ID: 404164
   Summary: Crashes when saving document upon closing
   Product: kile
   Version: 2.9.92
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: jsc...@posteo.net
  Target Milestone: ---

Application: kile (2.9.92)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-2-amd64 x86_64
Distribution: Debian GNU/Linux buster/sid

-- Information about the crash:
Closing Kile without saving a document first and proceeding to save as
suggested makes Kile crash, but doesn't have any practical consequences and is
an annoyance at worst. I reported it downstream [1] where someone chimed in
with details on the probable upstream issue.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919030

The crash can be reproduced every time.

-- Backtrace:
Application: Kile (kile), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=0, expected=0, futex_word=0x55b22ef72190) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
[Current thread is 1 (Thread 0x7fd057feb880 (LWP 3911))]

Thread 5 (Thread 0x7fcffbfff700 (LWP 5830)):
#0  0x7fd06294a289 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fd05d023f1a in g_cond_wait_until (cond=cond@entry=0x55b22ed02a68,
mutex=mutex@entry=0x55b22ed02a60, end_time=end_time@entry=12062223028) at
../../../glib/gthread-posix.c:1449
#2  0x7fd05cfac051 in g_async_queue_pop_intern_unlocked
(queue=queue@entry=0x55b22ed02a60, wait=wait@entry=1,
end_time=end_time@entry=12062223028) at ../../../glib/gasyncqueue.c:422
#3  0x7fd05cfac611 in g_async_queue_timeout_pop (queue=0x55b22ed02a60,
timeout=timeout@entry=1500) at ../../../glib/gasyncqueue.c:545
#4  0x7fd05d002d61 in g_thread_pool_wait_for_new_pool () at
../../../glib/gthreadpool.c:167
#5  0x7fd05d002d61 in g_thread_pool_thread_proxy (data=) at
../../../glib/gthreadpool.c:364
#6  0x7fd05d002325 in g_thread_proxy (data=0x7fd008005190) at
../../../glib/gthread.c:784
#7  0x7fd05fac0fa3 in start_thread (arg=) at
pthread_create.c:486
#8  0x7fd06294f80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fd04d2e6700 (LWP 3916)):
#0  0x7fd05fac6fbc in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55b22efde638) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fd05fac6fbc in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55b22efde5e8, cond=0x55b22efde610) at pthread_cond_wait.c:502
#2  0x7fd05fac6fbc in __pthread_cond_wait (cond=0x55b22efde610,
mutex=0x55b22efde5e8) at pthread_cond_wait.c:655
#3  0x7fd04d8caa32 in cnd_wait (mtx=0x55b22efde5e8, cond=0x55b22efde610) at
../src/../include/c11/threads_posix.h:155
#4  0x7fd04d8caa32 in util_queue_thread_func
(input=input@entry=0x55b22f31fab0) at ../src/util/u_queue.c:270
#5  0x7fd04d8ca5f7 in impl_thrd_routine (p=) at
../src/../include/c11/threads_posix.h:87
#6  0x7fd05fac0fa3 in start_thread (arg=) at
pthread_create.c:486
#7  0x7fd06294f80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fd04700 (LWP 3914)):
[KCrash Handler]
#6  0x7fd05fda6cfd in _mm_loadu_si128(long long __vector(2) const*)
(__P=) at
/usr/lib/gcc/x86_64-linux-gnu/8/include/emmintrin.h:1397
#7  0x7fd05fda6cfd in ucstrncmp (l=, b=0x55b230a21878,
a=0xab645fd2c8c0) at tools/qstring.cpp:685
#8  0x7fd05fda6cfd in ucstrcmp(QChar const*, size_t, QChar const*, size_t)
(a=a@entry=0xab645fd2c8c0, alen=13, b=0x55b230a21878, blen=11) at
tools/qstring.cpp:899
#9  0x7fd05fdacb0a in qt_compare_strings (cs=Qt::CaseSensitive, rhs=...,
lhs=...) at ../../include/QtCore/../../src/corelib/tools/qstringview.h:275
#10 0x7fd05fdacb0a in operator<(QString const&, QString const&) (s1=...,
s2=...) at tools/qstring.cpp:3214
#11 0x7fd062c75b70 in qMapLessThanKey(QString const&, QString
const&) (key2=..., key1=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:69
#12 0x7fd062c75b70 in QMapNode::lowerBound(QString
const&) (akey=..., this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:155
#13 0x7fd062c75b70 in QMapData::findNode(QString
const&) const (this=, akey=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:287
#14 0x7fd062c72805 in QMap::constFind(QString
const&) const (this=0x55b22fceef70, akey=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:867
#15 0x7fd062c72805 in KileParser::LaTeXParser::parse()
(this=0x55b230c874f0) at ./src/parser/latexparser.cpp:186
#16 0x7fd062c79362 in KileParser::ParserThread::run() (this=0x55b22eeff2c0)
at ./src/parser/parserthread.cpp:193
#17 0x7fd05fd39cd7 in QThreadPrivate::start(void*) 

[kdeconnect] [Bug 404163] Disconnect on screen blanking

2019-02-09 Thread kmahyyg
https://bugs.kde.org/show_bug.cgi?id=404163

--- Comment #1 from kmahyyg  ---
Maybe I think you need to send keepalive both from PC and Android.

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

[dragonplayer] [Bug 381673] problems with changing to full-screen mode and returning back to normal mode.

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=381673

Neousr  changed:

   What|Removed |Added

 CC||neo...@protonmail.com

--- Comment #1 from Neousr  ---
I can get an idea from the attachment but im not able to reproduce.

What version of dragon player is used and are you able to reproduce the issue
in a more recent version.

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

[kdeconnect] [Bug 404163] New: Disconnect on screen blanking

2019-02-09 Thread kmahyyg
https://bugs.kde.org/show_bug.cgi?id=404163

Bug ID: 404163
   Summary: Disconnect on screen blanking
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: i...@kmahyyg.xyz
  Target Milestone: ---

Created attachment 117960
  --> https://bugs.kde.org/attachment.cgi?id=117960=edit
The transmission packet from Android to PC captured by wireshark.

SUMMARY

After screen blanking, the Android closed connection to PC.

STEPS TO REPRODUCE

1. Find an Android phone (N/O may be both okay.) and install kdeconnect.

**Then give all the permissions the application wanted, if you are using MIUI
or that kind of third party UI of Android, please ensure that all the
permission managers in the system have granted all the permissions to the
application.**

2. Using kdeconnect from plasma or gsconnect from gnome on PC are okay.

3. pair and send a ping, after that, lock the phone screen.

OBSERVED RESULT:

https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/272#issuecomment-462095788

https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/272#issuecomment-462096535

EXPECTED RESULT

Worked as intended. Connection still be kept after screen blanking.

SOFTWARE/OS VERSIONS 

Linux/KDE Plasma:  Arch Linux, kdeconnect 1.3.3-1
(available in About System)
KDE Plasma Version: Plasma 5.14.5-2 and Gnome 3.30.2-1
KDE Frameworks Version: \
Qt Version: 5.12.1-2

ADDITIONAL INFORMATION

See: https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/272

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

[kturtle] [Bug 404162] File/Save acts always acts like "Save as..."

2019-02-09 Thread Alexander Wessel
https://bugs.kde.org/show_bug.cgi?id=404162

--- Comment #1 from Alexander Wessel  ---
I just realized that this happens only to *new* scripts, not to scripts that
have been opened before via "File/Open" or the Open... button.

So to reproduce:

1. File/New
2. File/Save - Dialog appears, save the file.
3. File/Save - Dialog appears again.

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

[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue

2019-02-09 Thread Armando
https://bugs.kde.org/show_bug.cgi?id=402328

--- Comment #52 from Armando  ---
Created attachment 117959
  --> https://bugs.kde.org/attachment.cgi?id=117959=edit
New crash information added by DrKonqi

plasma-discover (5.14.5) using Qt 5.12.0

- What I was doing when the application crashed:

Started up KDE Neon, proceeded to open Discover through menu. Crash. Attempted
opening via terminal. Crash. Crashes consistently every single time.

As another user reported in a comment, I was able to avoid a crash by removing
the file fwupd-backend.so. Replacing the file to the
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover directory reproduced consistent
crashes at every effort to open Discover.

As some others have expressed in comments, after running fwupdmgr refresh &&
fwupdmgr update, Discover does not crash.

-- Backtrace (Reduced):
#6  0x7fadc73b1d62 in AbstractResource::reportNewState
(this=0x564d4e978170) at ./libdiscover/resources/AbstractResource.cpp:143
#7  0x7fadc41faf3f in QtPrivate::QSlotObjectBase::call (a=0x7ffeb8717940,
r=0x564d4e978170, this=0x564d4e978990) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
[...]
#10 0x7fadc73c2cf3 in AbstractResource::stateChanged
(this=this@entry=0x564d4e978170) at
./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430
#11 0x7fad7d5a1a2d in FwupdResource::setState
(this=this@entry=0x564d4e978170,
state=state@entry=AbstractResource::Upgradeable) at
./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141
#12 0x7fad7d5a6cb5 in FwupdBackend::createApp
(this=this@entry=0x564d4d09f430, device=device@entry=0x7fad74002d90) at
./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235

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

[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue

2019-02-09 Thread Armando
https://bugs.kde.org/show_bug.cgi?id=402328

Armando  changed:

   What|Removed |Added

 CC||armandogarci...@gmail.com

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

[kmplot] [Bug 139097] kmplot wish more than one parameter

2019-02-09 Thread Orivej Desh
https://bugs.kde.org/show_bug.cgi?id=139097

Orivej Desh  changed:

   What|Removed |Added

 CC||ori...@gmx.fr

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

[latte-dock] [Bug 399149] Wine application with latte-dock master and plasma 5.14 beta always uses cpu

2019-02-09 Thread Alexandre Pereira
https://bugs.kde.org/show_bug.cgi?id=399149

--- Comment #35 from Alexandre Pereira  ---
Hi,

Can you give some info as how and where it was resolved ?

I still suffer from this problem :( Only workaround I found was using the app
through explorer.exe virtual desktop, but its bad, wine's virtual desktop is
really bad at managing windows :( ( really hurts my workflow ).

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

[dragonplayer] [Bug 327586] Dragon player cannot see all available audio channels

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=327586

Neousr  changed:

   What|Removed |Added

 CC||neo...@protonmail.com

--- Comment #3 from Neousr  ---
I just retested on version 18.12.2 on Gstreamer and VLC backend this is no
longer the case im able to see and select from multiple audio channels and
change between them.

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

[plasmashell] [Bug 396316] wayland: journal error on mouse over icons when using icons only task manager

2019-02-09 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=396316

--- Comment #4 from Serhiy Zahoriya  ---
Is this workaround/fix ok?

return model.AppPid ? model.AppPid : 0;

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=386379

--- Comment #40 from Colin Griffith  ---
Ah, durp... I see what you mean now. Yeah, though I think Nate was talking
about the size of the 'base' step that's considered 1 'line'.

If I knew what the preferred way of querying the line height of the text is,
I'd try writing the patch myself. As it is, however, I'm not quite that
confident I'd write it in a satisfactory way; I feel like I'd I'd start jumping
through hoops and unnecessarily complicating the code simply due to
unfamiliarity with what's available in which parts of the API.

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

[dragonplayer] [Bug 401130] pressing skip repeatedly causes the movie to restart at the beginning

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=401130

Neousr  changed:

   What|Removed |Added

 CC||neo...@protonmail.com

--- Comment #1 from Neousr  ---
I can confirm the restart of the the current media being played by using the
right arrow.

What backend are you using you can check under System Settings >Multimedia >
Audio and Video > Backend.

Can you retest by instead of skipping by pressing the right arrow key in quick
succession just leave it pressed at least 10 seconds and report back.

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

[kturtle] [Bug 404162] New: File/Save acts always acts like "Save as..."

2019-02-09 Thread Alexander Wessel
https://bugs.kde.org/show_bug.cgi?id=404162

Bug ID: 404162
   Summary: File/Save acts always acts like "Save as..."
   Product: kturtle
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: c...@kde.nl
  Reporter: fl...@chello.at
  Target Milestone: ---

File/Save acts always acts like "Save as..."

When saving an existing script, File/Save should automatically overwrite the
existing file, but it always acts like File/Save As... The file requester
dialog appears and overwriting the existing script must be confirmed always.

The existing script should simply be overwritten when using CTRL+S (File/Save).

This is likely similar to bug 156322 and bug 156328.

Version 0.8.1 beta on Linux 4.20.3-gentoo, compiled from the Gentoo
kapps-turtle-18.12.1(5)(03:16:11 01/25/19) ebuild.

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

[kvoctrain] [Bug 156322] When 'Save' is clicked, it acts like 'Save As'

2019-02-09 Thread Alexander Wessel
https://bugs.kde.org/show_bug.cgi?id=156322

Alexander Wessel  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=404162

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

[kwordquiz] [Bug 156328] When 'Save' is clicked, it acts like 'Save As'

2019-02-09 Thread Alexander Wessel
https://bugs.kde.org/show_bug.cgi?id=156328

Alexander Wessel  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=404162

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

[plasmashell] [Bug 396316] wayland: journal error on mouse over icons when using icons only task manager

2019-02-09 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=396316

--- Comment #3 from Serhiy Zahoriya  ---
And 

/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:437:
ReferenceError: VirtualDesktop is not defined

if there are multiple windows for icon being hovered

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

[latte-dock] [Bug 399149] Wine application with latte-dock master and plasma 5.14 beta always uses cpu

2019-02-09 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=399149

Michail Vourlakos  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED

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

[latte-dock] [Bug 403840] [feature] - option to enable/disable Meta pressed action

2019-02-09 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=403840

Michail Vourlakos  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/lat
   ||te-dock/20b76a182ccf51f6533
   ||2535802b7eb0b0beea919
 Status|REPORTED|RESOLVED

--- Comment #8 from Michail Vourlakos  ---
Git commit 20b76a182ccf51f65332535802b7eb0b0beea919 by Michail Vourlakos.
Committed on 10/02/2019 at 00:39.
Pushed by mvourlakos into branch 'master'.

add/enable option for MetaPressAndHold action

--user can now enable/disable the Meta pressAndHold
behavior that shows shortcuts badges. The new option
is located at Latte preferences.

M  +1-1app/lattecorona.cpp
M  +1-1app/lattecorona.h
M  +9-2app/settings/settingsdialog.cpp
M  +22   -0app/settings/universalsettings.cpp
M  +5-0app/settings/universalsettings.h
M  +10   -0app/shortcuts/globalshortcuts.cpp
M  +19   -1app/shortcuts/modifiertracker.cpp
M  +6-0app/shortcuts/modifiertracker.h

https://commits.kde.org/latte-dock/20b76a182ccf51f65332535802b7eb0b0beea919

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

[plasmashell] [Bug 396316] wayland: journal error on mouse over icons when using icons only task manager

2019-02-09 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=396316

Serhiy Zahoriya  changed:

   What|Removed |Added

 CC||serhiy@gmail.com
 Status|REPORTED|CONFIRMED
Version|5.13.2  |5.14.90
 Ever confirmed|0   |1

--- Comment #2 from Serhiy Zahoriya  ---
Getting this error on 5.14.90 on Ubuntu 19.04.

Additionally, every time a launched icon is hovered message changes to

> qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 19784, 
> resource id: 56623121, major code: 142 (Unknown), minor code: 3

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

[plasmashell] [Bug 391595] Icons-only Task Manager spewing out a lot of errors in syslog in KDE 5.12

2019-02-09 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=391595

Serhiy Zahoriya  changed:

   What|Removed |Added

 CC||serhiy@gmail.com

--- Comment #4 from Serhiy Zahoriya  ---
Maybe it wasn't completely fixed. Getting the first error on 5.14.90. Will
continue in https://bugs.kde.org/show_bug.cgi?id=396316

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Cqoicebordel
https://bugs.kde.org/show_bug.cgi?id=386379

--- Comment #39 from Cqoicebordel  ---
I understood that.

I was just referencing the comment of Nate Graham 
> I think the height of a single line of text might make sense. If that's not 
> fast enough by default, we could do two or three. I'll experiment.

and wanted to point out that doing it hardcoded, by the height of a single line
wasn't needed, as the setting I mentioned gives the users the choice of number
of lines of text to scroll.

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=386379

--- Comment #38 from Colin Griffith  ---
Cqoicebordel, the problem is that in Dolphin it doesn't go by lines of text, it
counts the number of icons. So in most applications, having that option set to
'3' will cause scrolling by 3 lines of text... But in Dolphin it scrolls by the
height of 3 icons - and that includes the text under the icon, so folders with
long names cause one tick of the scroll wheel to fly the view more than a
screen's worth of icons downward/upward at a time.

The patch mentioned earlier in this thread makes it so that it uses the height
of the shortest icon to determine scroll height, but that doesn't help if you
have a folder full of things that are similarly long. And even if all icons
have short, one-line names you still end up scrolling by waay more than 3 lines
of text worth.

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

[dolphin] [Bug 367890] Dolphin crashed when moving many files in parallel from a external HD to athe internal SSD

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=367890

--- Comment #26 from spaginni2...@yahoo.com ---
I'll try it when I can.

On Sat, Feb 9, 2019, 4:00 PM Julian Schraner  https://bugs.kde.org/show_bug.cgi?id=367890
>
> --- Comment #24 from Julian Schraner  ---
> Ah, I've just seen that there is indeed a bug report with the same crash
> cause
> that happens with Dolphin 18.04. Would it be possible for you to install
> Dolphin 18.12 on your current system and try if you can reproduce the bug?
> We
> will of course reopen this report if the crash is not fixed, but it'd be
> great
> to have confirmation that the bug does still exist.
>
> For your baloo-related problems: You might want to seek help on #kde or
> alternatively disable baloo temporarily with 'balooctl disable'. Hope that
> helps!
>
> (In reply to spaginni2000 from comment #23)
> > Created attachment 117947 [details]
> > attachment-13836-0.html
> >
> > I reported it happen on 18.04, i moved my OS because it keeps happeing.
> > baloo also just DOES no want to work. If you install debug, everything
> goes
> > to hell.
> >
> > Will Plaza
> > Mobile Communication ~
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Cqoicebordel
https://bugs.kde.org/show_bug.cgi?id=386379

--- Comment #37 from Cqoicebordel  ---
I think that there is a setting for the amount of lines scrolled
https://i.imgur.com/CHmX5ms.png

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

[dolphin] [Bug 367890] Dolphin crashed when moving many files in parallel from a external HD to athe internal SSD

2019-02-09 Thread My1
https://bugs.kde.org/show_bug.cgi?id=367890

--- Comment #25 from My1  ---
(In reply to Julian Schraner from comment #22)
> (In reply to My1 from comment #21)
> > so if this has been fixed (status does say resolved fixed), in what version
> > has it been fixed, so we can somehow get the update or at least know when we
> > got a fixed version, because apparently this thing still does appear in the
> > wild.
> 
> I do not know the exact version that this bug was fixed in, but nobody has
> been able to reproduce it with a version newer than 17.12.3. If you still
> encounter this crash with a version newer than 17.12.3 (preferably 18.12.x,
> as this is the newest version right now), please reopen this report. Thanks!

the question is are the newer versions even stable, or still in beta, and if
they are stable why are they not released?
the Software center still reports the latest version as "4:17.12.3-0ubuntu1" in
my kubuntu 18.04.
and then how am I supposed to get a newer dolphin? is there a .deb lying around
somehwere?

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=386379

--- Comment #36 from Nate Graham  ---
Yep, that'll do it. Nice find!

I think the height of a single line of text might make sense. If that's not
fast enough by default, we could do two or three. I'll experiment.

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

[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2019-02-09 Thread Robin Laing
https://bugs.kde.org/show_bug.cgi?id=366421

Robin Laing  changed:

   What|Removed |Added

 CC||me...@telusplanet.net

--- Comment #5 from Robin Laing  ---
Don't know if this will help or not but I found that I can generate as many
error messages as I like by just moving my mouse between two different
indicators on the task manager on my KDE desktop.

qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37284, resource
id: 69206033, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37303, resource
id: 79691782, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37321, resource
id: 69206033, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37332, resource
id: 79691782, major code: 141 (Unknown), minor code: 3

The sequence number changes but the resource id remains the same between each
application displayed.  Still happening in the current plasma on Fedora 29.

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

[dragonplayer] [Bug 402898] Dragon Doesn't Reproduce Any Media

2019-02-09 Thread Neousr
https://bugs.kde.org/show_bug.cgi?id=402898

Neousr  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

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

[kpat] [Bug 404161] New: kpat crashes when trying to play the second or third different game

2019-02-09 Thread Víktor
https://bugs.kde.org/show_bug.cgi?id=404161

Bug ID: 404161
   Summary: kpat crashes when trying to play the second or third
different game
   Product: kpat
   Version: 3.6
  Platform: Chakra
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: viktor...@gmail.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: kpat (3.6)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.19.12-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
- What I was doing when the application crashed:
I can play as many games as I want, as far as I don't change the game. If I
change the game a couple of times, it crashes. Always.

The crash can be reproduced every time.

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1ecb5e5800 (LWP 32743))]

Thread 4 (Thread 0x7f1ea57f4700 (LWP 32756)):
#0  0x7f1ec267977d in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f1ea65d69ab in ?? () from /usr/lib/dri/i965_dri.so
#2  0x7f1ea65d6717 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f1ec6bf848f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1eae7fc700 (LWP 32750)):
#0  0x7f1ec6bee00b in poll () from /usr/lib/libc.so.6
#1  0x7f1ebe99257e in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f1ebe99264c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f1ec785c40b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f1ec780695b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f1ec7650bb6 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f1ec38fac05 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f1ec7651f02 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f1ec6bf848f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f1eb680d700 (LWP 32749)):
#0  0x7f1ec6bee00b in poll () from /usr/lib/libc.so.6
#1  0x7f1ebcd3e922 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f1ebcd40727 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f1eb95f817a in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f1ec7651f02 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f1ec2673523 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f1ec6bf848f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1ecb5e5800 (LWP 32743)):
[KCrash Handler]
#6  MemoryManager::new_from_block (this=0x5600be42c190, s=72) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/memory.cpp:165
#7  0x5600bd2314a7 in Solver<22ul>::pack_position
(this=this@entry=0x5600be7496d0) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:209
#8  0x5600bd23195e in Solver<22ul>::insert (this=this@entry=0x5600be7496d0,
cluster=cluster@entry=0x7ffc7022627c, d=0, node=node@entry=0x7ffc70226280) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:873
#9  0x5600bd231a4a in Solver<22ul>::new_position
(this=this@entry=0x5600be7496d0, parent=parent@entry=0x0,
m=m@entry=0x7ffc702262c0) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:906
#10 0x5600bd2390e6 in Solver<22ul>::doit (this=0x5600be7496d0) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:487
#11 0x5600bd239177 in Solver<22ul>::patsolve (this=0x5600be7496d0,
_max_positions=) at
/chakra/desktop/kpat/src/kpat-18.12.1/patsolve/patsolve.cpp:794
#12 0x5600bd207f7f in DealerScene::isGameLost (this=0x5600be33ce10) at
/chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1821
#13 0x5600bd20f3b1 in DealerScene::takeState
(this=this@entry=0x5600be33ce10) at
/chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1314
#14 0x5600bd21346c in DealerScene::animationDone (this=0x5600be33ce10) at
/chakra/desktop/kpat/src/kpat-18.12.1/dealer.cpp:1530
#15 0x7f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#16 0x7f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#17 0x7f1ec7831d90 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#18 0x7f1ec783d997 in QTimer::timeout(QTimer::QPrivateSignal) () from
/usr/lib/libQt5Core.so.5
#19 0x7f1ec78324ab in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#20 0x7f1ec8c95bd1 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#21 0x7f1ec8c9d180 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#22 

[plasmashell] [Bug 404091] Panel elements disappearing after reboot only with NVIDIA GPU

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404091

--- Comment #2 from policra...@gmail.com ---
(In reply to David Edmundson from comment #1)
> After a reboot? Not after a suspend?
> That's new.
> 
> Please attach a screenshot.
> 
> Also please try the following in order.
> 
> Add to ~/.config/plasmashellrc
> 
> [QtQuickRendererSettings]
> GraphicsResetNotifications=true
> 
> 
> Then also try
> 
> [QtQuickRendererSettings]
> SceneGraphBackend=software
> 
> And report back on what either accomplis(In reply to David Edmundson from 
> comment #1)
> After a reboot? Not after a suspend?
> That's new.
> 
> Please attach a screenshot.
> 
> Also please try the following in order.
> 
> Add to ~/.config/plasmashellrc
> 
> [QtQuickRendererSettings]
> GraphicsResetNotifications=true
> 
> 
> Then also try
> 
> [QtQuickRendererSettings]
> SceneGraphBackend=software
> 
> And report back on what either accomplish

(In reply to David Edmundson from comment #1)
> After a reboot? Not after a suspend?
> That's new.
> 
> Please attach a screenshot.
> 
> Also please try the following in order.
> 
> Add to ~/.config/plasmashellrc
> 
> [QtQuickRendererSettings]
> GraphicsResetNotifications=true
> 
> 
> Then also try
> 
> [QtQuickRendererSettings]
> SceneGraphBackend=software
> 
> And report back on what either accomplish

Thanks for the response.

I've been trying to reproduce the issue to post a screenshot after it happens,
but I don't know why, it's not happening again, even without changing
~/.config/plasmashellrc. Probably the last updates fixed it.

I think this report can be closed. If it happens again, I'll open another one
with the effects. Thanks!

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

[krita] [Bug 404160] New: Krita creates a garbled image when converting from png or jpg to gif

2019-02-09 Thread Antti Savolainen
https://bugs.kde.org/show_bug.cgi?id=404160

Bug ID: 404160
   Summary: Krita creates a garbled image when converting from png
or jpg to gif
   Product: krita
   Version: 4.1.7
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: antti.s...@gmail.com
  Target Milestone: ---

SUMMARY
When you want to convert a png or a jpg as a single image to gif, it creates a
garbled image. Here is a link to test images and a .kra
https://mega.nz/#F!UQRkRAyD!44LNVoMwoP7EuqY3D4Ybcg 

STEPS TO REPRODUCE
1. Open the linked .kra in krita
2. Save it as a gif

OBSERVED RESULT
Krita creates a garbled image, similar to what is seen in the link

EXPECTED RESULT
A normal still image in gif format

SOFTWARE/OS VERSIONS
Xubuntu 18.10
Version: krita 4.2.0-pre-alpha

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

[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software

2019-02-09 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=386379

Colin Griffith  changed:

   What|Removed |Added

 CC||tyna...@gmail.com

--- Comment #35 from Colin Griffith  ---
Ok, I've been reading the code pointed to in comment 18, and started to go off
on some weird tangents... And overall I'm not convinced that the actual bug is
in any of that code.

Instead, I started tracking what code calls THAT code, and I found this:

https://lxr.kde.org/source/kde/applications/dolphin/src/kitemviews/kitemlistcontainer.cpp#0264

I'm fairly sure that this is where the decision is made to scroll by the height
of an item, and as a result this is the code we need to look toward changing to
fix this bug.

I've honestly got no clue what to use instead of the item height (I don't know
whether it's appropriate to query the currently used Qt style, some KDE
setting, or try to access some other member of view), but it appears this is
where we need to actually be looking.

Really happy I found that. This has been the most annoying bug in KDE for me
for quite some time.

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

[frameworks-kfilemetadata] [Bug 403902] Baloo_file_extractor Crashes in KFileMetaData::TagLibExtractor::extract() on XML files with the .spx extension

2019-02-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=403902

--- Comment #8 from Nate Graham  ---
The above commit should make Baloo shop crashing because it removes these files
from indexing consideration. The bug is still open because this doesn;t
actually fix the crash itself, it just avoids it. But from a user perspective,
there shouldn't be any more crashes on .spx files starting in KDE Frameworks
5.56.

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

[latte-dock] [Bug 403611] [feature] - option to enable/disable audio indicator actions

2019-02-09 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=403611

Michail Vourlakos  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/lat
   ||te-dock/8f9140f67a2baff4409
   ||e9d40d72f075142c9e756

--- Comment #1 from Michail Vourlakos  ---
Git commit 8f9140f67a2baff4409e9d40d72f075142c9e756 by Michail Vourlakos.
Committed on 09/02/2019 at 23:12.
Pushed by mvourlakos into branch 'master'.

option to enable/disable audio badge actions

M  +3-0containment/package/contents/config/main.xml
M  +1-0containment/package/contents/ui/main.qml
M  +1-0plasmoid/package/contents/ui/main.qml
M  +8-3plasmoid/package/contents/ui/task/AudioStream.qml
M  +13   -1shell/package/contents/configuration/pages/TasksConfig.qml

https://commits.kde.org/latte-dock/8f9140f67a2baff4409e9d40d72f075142c9e756

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

[kdevelop] [Bug 404159] New: open project file dialog doesn't remember sort options

2019-02-09 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=404159

Bug ID: 404159
   Summary: open project file dialog doesn't remember sort options
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

SUMMARY
The file dialog presented when importing a project does not retain the selected
sorting method

STEPS TO REPRODUCE
1. Project\Open/Import Project, note the sorting method used
2. set a (different) sorting method by clicking on one of the column headers
(in detail/detailed tree view)
3. import a project (or not)
4. back to 1.

OBSERVED RESULT
The sorting method is back to the initial sorting method noted in 1)


EXPECTED RESULT
The sorting method should remain as set in 2)

SOFTWARE/OS VERSIONS
KDE Frameworks Version:  5.52
Qt Version: 5.9.7
KDevelop 5.3 branch head.

ADDITIONAL INFORMATION
It seems that the open project file dialog uses the sorting set in the regular
open file dialog.

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

[plasmashell] [Bug 404158] New: plasmashell crashes when an openGL app is running

2019-02-09 Thread Mathias Homann
https://bugs.kde.org/show_bug.cgi?id=404158

Bug ID: 404158
   Summary: plasmashell crashes when an openGL app is running
   Product: plasmashell
   Version: 5.14.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mathias.hom...@opensuse.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.14.90)

Qt Version: 5.12.1
Frameworks Version: 5.54.0
Operating System: Linux 4.12.14-lp150.12.45-default x86_64
Distribution: "openSUSE Leap 15.0"

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

Running an openGL based video game

Since updating to the  G05 driver series the crashes happen less often but they
still happen.

The crash can be reproduced sometimes.

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

Thread 17 (Thread 0x7f51a3fff700 (LWP 15745)):
#0  0x7f5206c3889d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5209eb892b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5209eb8c39 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f520e251658 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f520e251a8a in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7f5209eb17e2 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5206c32559 in start_thread () at /lib64/libpthread.so.0
#7  0x7f52097b281f in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f51963fe700 (LWP 19427)):
#0  0x7f5206c3bc4d in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7f5206c34f88 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7f51eb2da4cc in  () at /usr/lib64/libGLX_nvidia.so.0
#3  0x7f51eb2a9ae8 in  () at /usr/lib64/libGLX_nvidia.so.0
#4  0x7f51eb2a3b50 in glXReleaseTexImageEXT () at
/usr/lib64/libGLX_nvidia.so.0
#5  0x7f51dfbfecbf in  () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#6  0x7f51dfc01f2c in  () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#7  0x7f51dfc02a27 in  () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#8  0x7f51dfc02de4 in  () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#9  0x7f520e2a3658 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
at /usr/lib64/libQt5Quick.so.5
#10 0x7f520e2a3ee3 in QQuickWindowPrivate::updateDirtyNodes() () at
/usr/lib64/libQt5Quick.so.5
#11 0x7f520e2a5262 in QQuickWindowPrivate::syncSceneGraph() () at
/usr/lib64/libQt5Quick.so.5
#12 0x7f520e24cef4 in  () at /usr/lib64/libQt5Quick.so.5
#13 0x7f520e24e304 in  () at /usr/lib64/libQt5Quick.so.5
#14 0x7f520e251a48 in  () at /usr/lib64/libQt5Quick.so.5
#15 0x7f5209eb17e2 in  () at /usr/lib64/libQt5Core.so.5
#16 0x7f5206c32559 in start_thread () at /lib64/libpthread.so.0
#17 0x7f52097b281f in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f517deec700 (LWP 4047)):
#0  0x7f5206c3889d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5209eb892b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5209eb8c39 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f520e251658 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f520e251a8a in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7f5209eb17e2 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5206c32559 in start_thread () at /lib64/libpthread.so.0
#7  0x7f52097b281f in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f517f0fd700 (LWP 4035)):
#0  0x7f5206c3889d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5209eb892b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5209eb8c39 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f520e251658 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f520e251a8a in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7f5209eb17e2 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5206c32559 in start_thread () at /lib64/libpthread.so.0
#7  0x7f52097b281f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f517700 (LWP 3997)):
#0  0x7f52097a3b68 in read () at /lib64/libc.so.6
#1  0x7f51c76ac751 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7f51c7b32dde in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f51c7b33850 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f51c7b33910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0

[Falkon] [Bug 394093] Falkon 3.0.1 appimage not working in ubuntu 14.04

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394093

antident...@hotmail.com changed:

   What|Removed |Added

 CC||antident...@hotmail.com

--- Comment #12 from antident...@hotmail.com ---
I've got the same problem with Debian 9 Stretch:
./Falkon-3.0.1.AppImage 
Falkon: 1 extensions loaded
qt.network.ssl: QSslSocket: cannot resolve TLSv1_client_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_client_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_server_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_server_method
qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_server_method
qt.network.ssl: QSslSocket: cannot resolve i2d_SSL_SESSION
qt.network.ssl: QSslSocket: cannot resolve d2i_SSL_SESSION
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function
SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_new
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get_ciphers
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_free
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_free

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

[dragonplayer] [Bug 402898] Dragon Doesn't Reproduce Any Media

2019-02-09 Thread Alberto Díaz López
https://bugs.kde.org/show_bug.cgi?id=402898

--- Comment #4 from Alberto Díaz López  ---
(In reply to Neousr from comment #3)
> If Gstreamer is the only backend it possibly lacks some plugins (
> gstreamer1.0-plugins-good and gstreamer1.0-plugins-ugly name can vary on
> your distro) to be able to play the media. On the other hand Dragon can use
> the VLC Phonon backend if you install the corresponding packages
> (phonon4qt5-backend-vlc and libvlc) and prioritize the backend on the
> settings menu.
> 
> If you are fine with VLC at the moment let me now so i can close this report.

Yeah, it is good to know, thanks. I am pretty fine with VLC, but i realized an
attempt to use as much Qt only and later KDE software as i can/could, but looks
like Dragon can not replace VLC in my case, at least not for now.

For sure, thanks for your help and you can close this bug.

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

[juk] [Bug 404157] New: Track length is not updated when advancing in the playlist

2019-02-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=404157

Bug ID: 404157
   Summary: Track length is not updated when advancing in the
playlist
   Product: juk
   Version: 18.12.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: whee...@kde.org
  Reporter: aro...@archlinux.org
CC: mp...@kde.org
  Target Milestone: ---

SUMMARY
When a sing ends and the playlist advances to the next song, the track length
is not updated, so the progress bar is in a broken state. Using gstreamer
backend.

This is another regression from f07d305eb627028ff87475506f8fa466801f8890

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

[kwin] [Bug 404152] Apps running on Xwayland scroll twice on every second mouse wheel movement

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404152

pmarget...@gmail.com changed:

   What|Removed |Added

 CC||pmarget...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from pmarget...@gmail.com ---
Confirming, happens under 5.14.5 as well.
Easily reproducible on firefox tabs where a single mouse wheel turn flips 2
tabs.

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

[konsole] [Bug 404096] Adjust size of preferences window to eliminate unnecessary vertical scroll bar

2019-02-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=404096

--- Comment #3 from Nate Graham  ---
I can't wait to see!

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

[www.kde.org] [Bug 404148] KDE's Bugtracking bug entry page is unstructured and messy

2019-02-09 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=404148

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|REPORTED|RESOLVED
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
In fact, that wouldn't help you since Okular's printing dialog is provided by
Qt. :)

The best you can do is report it anyway and a friendly helpful bug triager will
route it appropriately.

As for your request, I completely agree. We're currently waiting for a new
upstream release of Bugzilla, and then we have active plans to do this.

Marking as RESOLVED LATER since it's on the roadmap but there's nothing we can
do right now.

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

[latte-dock] [Bug 404122] [feature] - colored backgrounds for running tasks like Unity's launcher/Ubuntu Gnome

2019-02-09 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=404122

--- Comment #6 from Michail Vourlakos  ---
(In reply to trmdi from comment #4)
> (In reply to Michail Vourlakos from comment #3)
> > (In reply to trmdi from comment #2)
> > > (In reply to Michail Vourlakos from comment #1)

There is a chance that we might can support this like,

Indicator Style: Latte | Plasma | Unity

because there are some plasma applets that could also follow it... 
I will play with it and see its boundaries...

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

[kmymoney] [Bug 404156] Can't select many columns as memo

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404156

k.bu...@gmail.com changed:

   What|Removed |Added

 CC||k.bu...@gmail.com
   Keywords||reproducible, usability

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

[kmymoney] [Bug 404156] New: Can't select many columns as memo

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404156

Bug ID: 404156
   Summary: Can't select many columns as memo
   Product: kmymoney
   Version: 5.0.3
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: k.bu...@gmail.com
  Target Milestone: ---

SUMMARY
In version 4 when importing csv it was possible to select more than one column
from file to be imported into Memo. In version 5 i can select only one column.

STEPS TO REPRODUCE
1. File -> import -> CSV
2. Add new profile 
3. Select csv file with more than one column
4. when selecting columns for import select column numbers for each property

OBSERVED RESULT
It is impossible to select more than one column for memo

EXPECTED RESULT
Option to select more than one like before (* sign on selected columns in
dropdown)
Or other field type that would allow selecting many columns 

SOFTWARE/OS VERSIONS
Windows: 10 

ADDITIONAL INFORMATION
Tested on Version 5.03 downloaded from here:
https://binary-factory.kde.org/job/KMyMoney_Release_win64/

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

[juk] [Bug 403170] lyrics aren't retrieved when advancing in the playing queue

2019-02-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=403170

--- Comment #2 from Antonio Rojas  ---
Also, this is only reproducible with phonon-vlc, not with gstreamer.

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

[klipper] [Bug 404155] New: Need to select/click on last copied item to enable copying it

2019-02-09 Thread Sylvain
https://bugs.kde.org/show_bug.cgi?id=404155

Bug ID: 404155
   Summary: Need to select/click on last copied item to enable
copying it
   Product: klipper
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kde.s...@9ox.net
  Target Milestone: ---

It randomly happens with Klipper that I select a portion of text and press
Ctrl+C, only then Ctrl+V copies nothing as if the clipboard is empty. I have to
open the Klipper applet menu and select the copied item (which is actually
present) by clicking on it, and then I can copy it fine.

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

[dolphin] [Bug 367890] Dolphin crashed when moving many files in parallel from a external HD to athe internal SSD

2019-02-09 Thread Julian Schraner
https://bugs.kde.org/show_bug.cgi?id=367890

--- Comment #24 from Julian Schraner  ---
Ah, I've just seen that there is indeed a bug report with the same crash cause
that happens with Dolphin 18.04. Would it be possible for you to install
Dolphin 18.12 on your current system and try if you can reproduce the bug? We
will of course reopen this report if the crash is not fixed, but it'd be great
to have confirmation that the bug does still exist.

For your baloo-related problems: You might want to seek help on #kde or
alternatively disable baloo temporarily with 'balooctl disable'. Hope that
helps!

(In reply to spaginni2000 from comment #23)
> Created attachment 117947 [details]
> attachment-13836-0.html
> 
> I reported it happen on 18.04, i moved my OS because it keeps happeing.
> baloo also just DOES no want to work. If you install debug, everything goes
> to hell.
> 
> Will Plaza
> Mobile Communication ~

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

[dolphin] [Bug 404154] New: Nothing appears in Recent Files (Places panel section)

2019-02-09 Thread Sylvain
https://bugs.kde.org/show_bug.cgi?id=404154

Bug ID: 404154
   Summary: Nothing appears in Recent Files (Places panel section)
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kde.s...@9ox.net
  Target Milestone: ---

The "Recent Files" section in Dolphin's Places panel displays nothing. I can
open the four timelines "today", "yesterday", "this month" and "last month" but
it is as if there had been no activity on the computer, while obviously I
constantly create, save and edit files of all kinds.

I use KDE on Kubuntu 18.04.1 LTS with Dolphin 17.12.23

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

[okular] [Bug 404120] Add TexStudio support

2019-02-09 Thread Victor Porton
https://bugs.kde.org/show_bug.cgi?id=404120

--- Comment #4 from Victor Porton  ---
On 09/02/2019 22:50, Albert Astals Cid wrote:
>
> *Comment # 3  on bug 
> 404120  from Albert 
> Astals Cid  *
> Well, since it seems you've done it already, what would be the command line
> needed for texstudio?
texstudio --line %l

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

[okular] [Bug 404120] Add TexStudio support

2019-02-09 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=404120

--- Comment #3 from Albert Astals Cid  ---
Well, since it seems you've done it already, what would be the command line
needed for texstudio?

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

[dolphin] [Bug 404153] New: Carry [copying] operation on while waiting for prompt after minor error

2019-02-09 Thread Sylvain
https://bugs.kde.org/show_bug.cgi?id=404153

Bug ID: 404153
   Summary: Carry [copying] operation on while waiting for prompt
after minor error
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kde.s...@9ox.net
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Oftentimes I use Dolphin to manage different disks and different partitions
systems. This is prone to producing errors, because some files on my ext4
partitions ext4 have weird characters in their filenames (notably two dots,
exclamation mark and interrogation mark) which are incompatible with exfat FS.

When such an error happens, Dolphin asks what to do about it (Ignore, Retry
etc) and it seems the operation is suspended until the user would prompt in.
This is quite inconvenient as it prevents getting away from a potentially long
task that one hopes would complete after a while.

Ideally I suppose the task would carry on running in the background, and
potential new errors add up to the error window list (instead of triggering
multiple windows). In my case the system could simply suggest to replace the
problematic characters.

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

[Breeze] [Bug 379637] breeze-gtk should draw shadows for client-side-decorated windows

2019-02-09 Thread Gianluca Pettinello
https://bugs.kde.org/show_bug.cgi?id=379637

--- Comment #20 from Gianluca Pettinello  ---
(In reply to Martin Flöser from comment #19)
> Ok, I think I need to explain more on the situation on X11. The problem is
> not that the code is fragile, undocumented or umaintained. The code is good,
> the quality of the code in question is superb and one can easily understand
> which area of X11 it reflects. No increase of documentation would make it
> possible to implement this change request.
> 
> Let's look at the root problem. On X11 the window geometry is retrieved
> through the get_geometry call:
> https://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html#requests:
> GetGeometry
> 
> This specifies the geometry of a drawable - either a pixmap or a window.
> That's what KWin's geometry handling code is based on. Now what GTK did is
> use this window geometry and added the shadow into it. Additional there is a
> property which indicates what to subtract from the x geometry to get to the
> window geometry. If we wouldn't subtract it, we would snap to shadow, quick
> tiling would include shadow, maximize would include shadow, etc. etc.
> 
> So basically everywhere where we use geometry we would have to remove that
> this maps to x window geometry and replace it by an abstract geometry
> concept which is either the geometry or the geometry subtracted by shadow.
> And this is the fundamental problem for us. When KWin was developed nobody
> thought that the geometry of a window would not match the geometry. Now you
> might wonder how things like window decorations work? Well it's still a
> window. The actual client window gets reparented to the window decoration
> and then we just use the geometry of the decoration window again.
> 
> The geometry handling in KWin is deep involved and the assumption is carried
> everywhere. It goes into the effect system (e.g. Present Windows uses it to
> layout), it's deep in the compositor (we actually have a check to verify the
> geometry matches the pixmap size, if it doesn't we don't render the window,
> see https://phabricator.kde.org/source/kwin/browse/master/scene.cpp$1042).
> We have multiple level of convenient api for it: Toplevel::width,
> Toplevel::height, Toplevel::x, Toplevel::y, Toplevel::size, Toplevel::pos,
> etc. So it's not just one method we have to check. Then there are methods
> like isOnScreen intersecting the screen geometry with the window geometry.
> 
> So all of that is a huge effort to restructure the code base to support this
> new requirement. And then there are multiple things which are completely
> unknown to me as this is a not standardized protocol: when resizing do we
> have to add the shadow or not? A maximized window does it include the shadow
> or not? How does gravity interact with shadow? What if a base increment is
> set? What about vertical only or horizontal only maximize state? Gtk doesn't
> like those, so do they support it? Is it possible to have shadows only on
> some sides or is it always all? Can we expect that Gtk won't change that?
> After all they broke us here several times.
> 
> So to reiterate some important points:
>  * this is not a bug on our side, our code is written against the X
> protocol, ICCCM and EWMH
>  * GTK changed basic understanding of what a window geometry is, this
> understanding is completely incompatible to the assumptions KWin was
> implemented on
>  * The code base is in a superb state, geometry handling has very seldom
> bugs, it's a done and working code base
>  * The effort is comparable to adding Wayland support - the difficult part
> was getting the geometry handling done
>  * implementing the change is a huge effort as the code base is large and it
> touches complex areas of X where the expected behavior is undocumented by
> GTK (I just tried google for _GTK_FRAME_EXTENTS and found nothing)
> 
> 
> Comparing to the state on Wayland: on Wayland the geometry and visual
> geometry are separated. The visual geometry is defined by the size of the
> attached buffer. The geometry of the window is not directly mapped from the
> buffer as we have concepts such as scale built into the protocol. While KWin
> still is largely based on the idea that visual geometry matches window
> geometry, it's not as bad as on X11. We already weakened the assumption a
> lot by adding window decorations ;-). Implementing the required request
> should be relatively straight forward and doable without larger problems. We
> have a well tested code base on Wayland and I am sure it can be implemented
> without regressions. The main reason why the request is not implemented is
> that there was a little bit of version mess when that area of code got
> written. That's now resolved and it's possible to test with real world
> applications.
> 
> Overall I think the way forward is supporting Wayland. On X11 we need to
> find different solutions which don't involve changing KWin or convince GTK
> to not build a GUI based on 

[Spectacle] [Bug 372408] Option to omit shadow and transparent border from windows in Active Window and Window Under Cursor modes

2019-02-09 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=372408

Rog131  changed:

   What|Removed |Added

 CC||j...@eclipso.de

--- Comment #11 from Rog131  ---
*** Bug 404143 has been marked as a duplicate of this bug. ***

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

[Spectacle] [Bug 404143] Window Snapshot includes plasma theme decoration

2019-02-09 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=404143

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Rog131  ---


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

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

[kwin] [Bug 404146] Tabbox kcm incorrectly falls back to informative on broken theme

2019-02-09 Thread Chris Holland
https://bugs.kde.org/show_bug.cgi?id=404146

--- Comment #2 from Chris Holland  ---
The main reason I made this bug is for when a downloaded QML skin from the KDE
Store is loaded but fails to load (eg: was written for KWin 4.x).

However, you do raise a good point, I completely forgot "informative" is part
of kdeplasma-addons.

So it seems the hardcoded default needs to be... "org.kde.breath.desktop" so
that it loads:
/usr/share/plasma/look-and-feel/org.kde.breath.desktop/contents/windowswitcher/WindowSwitcher.qml

However that still depends on the breeze package. KWin itself does not seem to
ship with any "QML" tabbox skins that I can see. So does this mean it needs to
somehow fallback to a C++ TabBox theme? Like the "kwin/effects/coverswitch"
desktop effect? I'm not quite sure how it loads the C++ effects to be honest...

Looking at the kcm code, it seems that the desktop effect itself has a "TabBox"
config property. I take it that it will then take over the "Alt+Tab" and
"Alt+Shift+Tab" shortcuts.

*
https://github.com/KDE/kwin/blob/cfecb1e0770ca6c8fa879124e11b03081342b9ed/kcmkwin/kwintabbox/main.cpp#L368
*
https://github.com/KDE/kwin/blob/master/effects/coverswitch/coverswitch.kcfg#L35
* 

Falling back to a "kwin effect" skin sounds like a fairly complicated fallback,
as you'd need to copy the kcm's save() code.

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

[kwin] [Bug 404152] New: Apps running on Xwayland scroll twice on every second mouse wheel movement

2019-02-09 Thread mthw0
https://bugs.kde.org/show_bug.cgi?id=404152

Bug ID: 404152
   Summary: Apps running on Xwayland scroll twice on every second
mouse wheel movement
   Product: kwin
   Version: 5.14.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jari...@hotmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open Firefox, Chromium, or even Minecraft

OBSERVED RESULT
scroll once - > content moves by one line
scroll again - > content moves by two lines
scroll again - > content moves by one line
...
etc.

EXPECTED RESULT
Every 'scroll' should trigger the scrolling action exactly once

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.54
Qt Version: 5.12.1

ADDITIONAL INFORMATION
This issue isn't present on Gnome Wayland and was fixed in Xwayland by
https://gitlab.freedesktop.org/xorg/xserver/commit/cd285922cdec966825e47220b1182a57abc1ff90
but this still happens on Plasma Wayland

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

[systemsettings] [Bug 404151] Time Format setting to en_SE results in unrecognized LC_TIME

2019-02-09 Thread Clarence Risher
https://bugs.kde.org/show_bug.cgi?id=404151

Clarence Risher  changed:

   What|Removed |Added

  Component|kcm_clock   |kcm_formats
   Assignee|p...@taniwha.com|se...@kde.org

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

[systemsettings] [Bug 404151] New: Time Format setting to en_SE results in unrecognized LC_TIME

2019-02-09 Thread Clarence Risher
https://bugs.kde.org/show_bug.cgi?id=404151

Bug ID: 404151
   Summary: Time Format setting to en_SE results in unrecognized
LC_TIME
   Product: systemsettings
   Version: 5.14.90
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_clock
  Assignee: p...@taniwha.com
  Reporter: spa...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

When I use the Formats module in System Settings to set the local Time format
to en_SE this results in ~/.config/plasma-locale-settings.sh trying to set
LC_TIME to en_SE.UTF-8 which is not a locale recognized by seemingly anything
else. This leads to many programs spewing locale-related errors, including man
and perl.

STEPS TO REPRODUCE
1. System Settings > Regional > Detailed Settings > Time > "Sweden - English
(en_SE)
2. Apply
3. Log out
4. Log in
5. Open a terminal
6. `perl`
7. `man`

OBSERVED RESULT
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_MONETARY = "en_US.UTF-8",
LC_TIME = "en_SE.UTF-8",
LC_NUMERIC = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").

man: can't set the locale; make sure $LC_* and $LANG are correct

EXPECTED RESULT
no errors

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

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

[kwin] [Bug 403601] KWin crash on boot

2019-02-09 Thread tai133
https://bugs.kde.org/show_bug.cgi?id=403601

--- Comment #4 from tai133  ---
Update: Today I applied 52 updates to the old 16.04 VM. After doing so, the
system booted normally and without any KWin errors.

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

[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()

2019-02-09 Thread Alexander
https://bugs.kde.org/show_bug.cgi?id=357206

Alexander  changed:

   What|Removed |Added

 CC|dct...@web.de   |

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

[KScreen] [Bug 376341] dual screen setup broken after suspend

2019-02-09 Thread Sergey
https://bugs.kde.org/show_bug.cgi?id=376341

--- Comment #26 from Sergey  ---
I currently use Plasma 5.14.5, KDE Frameworks 5.54.0 but I'm not sure how long.

I'll try to disable my scripts and check.

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

[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland

2019-02-09 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=400658

Patrick Silva  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REPORTED

--- Comment #8 from Patrick Silva  ---
This annoying problem is back with plasma 5.15 beta.

I use alt+tab to walk through all apps and alt + ' (alt + key above TAB key)
to walk through windows of the current app. These same shorcuts work as
expected under X11.

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

[kwin] [Bug 404146] Tabbox kcm incorrectly falls back to informative on broken theme

2019-02-09 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=404146

Martin Flöser  changed:

   What|Removed |Added

Summary|When a QML tabbox skin  |Tabbox kcm incorrectly
   |fails to load, fall back to |falls back to informative
   |"Informative" like we do|on broken theme
   |when the configured file|
   |does not exist  |

--- Comment #1 from Martin Flöser  ---
This means the kcm is wrong - I reworded the title accordingly. The informative
theme is not part of KWin (any more) and not installed by default in most
distributions. Using it as fallback is an obvious oversight.

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

[KScreen] [Bug 376341] dual screen setup broken after suspend

2019-02-09 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=376341

--- Comment #25 from smihael  ---
This seems to not be an issue anymore using KDE neon 5.14 with Plasma 5.14.5,
KDE Frameworks 5.54.0 and generic Linux 4.15.0 kernel.

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

[www.kde.org] [Bug 404148] KDE's Bugtracking bug entry page is unstructured and messy

2019-02-09 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=404148

smihael  changed:

   What|Removed |Added

Summary|Bugtracking entry page is   |KDE's Bugtracking bug entry
   |unstructured and messy  |page is unstructured and
   ||messy

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

[plasmashell] [Bug 403812] Rendering problems with desktop effects enabled (OpenGL) and latest Plasma update

2019-02-09 Thread JEREMY COX
https://bugs.kde.org/show_bug.cgi?id=403812

JEREMY COX  changed:

   What|Removed |Added

 CC||jeremy.m@gmail.com
 OS|Linux   |FreeBSD

--- Comment #3 from JEREMY COX  ---
I would also like to report the same issues with the QT5 update to 5.12.0.
While I was using QT5 5.11 there were no flickering issues, but once I updated
to QT5 5.12.0 the flickering issues started for me too. I am using FreeBSD 12
stable, with the Intel driver. By switching to the modesetting driver, the
issue stopped for me. I didn't try to switch the compositor to XRender from
OpenGL. I just switched the driver from Intel to modesetting. I would also like
to point out there is a thread on the Mageia Bugzilla website that describes a
very similar issue to this. It's probably the same issue. 

https://bugs.mageia.org/show_bug.cgi?id=24060

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

[frameworks-kwidgetsaddons] [Bug 404150] New: KDE printing properties dialog is showing a misleading preview of different pages per sheet layouts

2019-02-09 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=404150

Bug ID: 404150
   Summary: KDE printing properties dialog is showing a misleading
preview of different pages per sheet layouts
   Product: frameworks-kwidgetsaddons
   Version: 5.54.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: smih...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 117955
  --> https://bugs.kde.org/attachment.cgi?id=117955=edit
Misleading preview

Consider the following case.

I want to print a chapter from a study script. In order to save paper I want to
print 2 pages next to each other. I can go to Printer properties > Page > Page
Layout and select "2 (2x1)" as pages per sheet layout and "Left to Right, Top
to Bottom" as page order. The preview (see screenshot) is misleading as it
seems that pages will be printed one below other (orientation of the "text
lines" in the preview). 

The actual printing result is still as expected.

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

[frameworks-kwidgetsaddons] [Bug 404150] KDE printing properties dialog is showing a misleading preview of different pages per sheet layouts

2019-02-09 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=404150

--- Comment #1 from smihael  ---
Created attachment 117956
  --> https://bugs.kde.org/attachment.cgi?id=117956=edit
Actual printout (correct)

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

[plasmashell] [Bug 404149] New: Natural sorting for items in activities pager

2019-02-09 Thread Dimitrios T Tanis
https://bugs.kde.org/show_bug.cgi?id=404149

Bug ID: 404149
   Summary: Natural sorting for items in activities pager
   Product: plasmashell
   Version: 5.12.6
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Pager
  Assignee: h...@kde.org
  Reporter: dimitrios.ta...@kdemail.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
It would be nice for activities to use natural order when displayed sorted.

STEPS TO REPRODUCE
1. Assign number prefixes to activities (eg 1.Home, 2.Work, ... 9.Holidays,
10.Fun) 
2. Add Activities pager to desktop or panel
3. Set display: Activity Name in activities pager settings

OBSERVED RESULT
Activities are ordered in the classic way (1.Home, 10.Fun, 2.Work, etc)

EXPECTED RESULT
Activities should be ordered naturally (1.Home, 2.Work,... 9.Holidays, 10.Fun)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4

ADDITIONAL INFORMATION
This does not affect activities:/ path in dolphin where activities use natural
order when sorted by name.

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

[juk] [Bug 403170] lyrics aren't retrieved when advancing in the playing queue

2019-02-09 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=403170

--- Comment #1 from Antonio Rojas  ---
This is a regression from
https://cgit.kde.org/juk.git/commit/?id=f07d305eb627028ff87475506f8fa466801f8890

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

[www.kde.org] [Bug 404148] New: Bugtracking entry page is unstructured and messy

2019-02-09 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=404148

Bug ID: 404148
   Summary: Bugtracking entry page is unstructured and messy
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: smih...@gmail.com
  Target Milestone: ---

When trying to fill a bug, it's unclear in which category to fill it since
there are zillions of categories on the first page of bugs.kde.org. Some
structuring would help (e.g. KDE Apps/Frameworks/Plasma/Services/Websites).

Example: if I want to report strange behaviour of printing dialog that I
noticed, let's say in Okular (but it is not app specific to okular), it's not
immediately clear where is should go.

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

[krita] [Bug 404147] New: old display / no pressure / crashes

2019-02-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404147

Bug ID: 404147
   Summary: old display / no pressure / crashes
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: miniky...@gmail.com
  Target Milestone: ---

Created attachment 117954
  --> https://bugs.kde.org/attachment.cgi?id=117954=edit
"old-looking" display

Hi,
Ever since the last update, Krita doesn't want to run properly on my laptop. I
tried de-install/reinstall it, multiple time in different condition with more
or less old setup file. But no matter how much I tried, it kept crashing when
opening a file, or creating a new canvas (or basically anything).
So I recovered a previous version, before the update. And it kept crashing, but
the display suddenly looked like a really old version (light grey, blocky,
feels off and not up to date).
I just bought krita from steam, to see if this will change anything. And it did
not. I can open files, but it's crashing down sometimes, the pressure of my pen
is nowhere to be seen (only in krita) and I still have this "old-looking"
display.



SOFTWARE/OS VERSIONS
Windows: 7

KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.9.3

Krita
  Version: 4.1.7

Qt
  Version (compiled): 5.9.3
  Version (loaded): 5.9.3

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.1.7601
  Pretty Productname: Windows 7 SP 1 (6.1)
  Product Type: windows
  Product Version: 7sp1

Hope you can help me, you can also find how the display looks like in the
attachment.

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

[plasmashell] [Bug 404145] New: impossible to use virt-manager in Plasma - keyboard stops working when copying/pasting clipboard

2019-02-09 Thread Matej Parm
https://bugs.kde.org/show_bug.cgi?id=404145

Bug ID: 404145
   Summary: impossible to use virt-manager in Plasma - keyboard
stops working when copying/pasting clipboard
   Product: plasmashell
   Version: 5.14.5
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bumba0...@email.cz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
I'm unable to use virt-manager and virtualizing Windows / other KDE Plasma and
copying or pasting text. If I want to use clipboard, I have to close
virt-manager or "hope" that next copy / past won't freeze keyboard. I had to
jump to GNOME in order to do some virtualization... And I'd love to use Plasma
;-)

STEPS TO REPRODUCE
1. install Debian Testing with KDE Plasma 5.14
2. install virt-manager and run Windows with Spice drivers of Ubuntu with
Plasma
3. copy and paste text withing host or between host and VM (guest) or just in
VM (guest)
4. keyboard freeze randomly stops working for approx 60 seconds when copy /
past (it's random, sometime it's OK, sometime not)

OBSERVED RESULT
typing on keyboard does nothing

EXPECTED RESULT
keyboard should work

SOFTWARE VERSIONS
plasmashell --version
plasmashell 5.14.5

dpkg --list | grep plasma
ii  kde-plasma-desktop5:102amd64  KDE Plasma Desktop
and minimal set of applications
ii  kdeplasma-addons-data 4:5.14.5-1   alllocale files for
kdeplasma-addons
ii  libkdeclarative5  4:4.14.38-3  amd64  declarative library
for plasma
ii  libkf5plasma5:amd64   5.54.0-1 amd64  Plasma Runtime
components
ii  libkf5plasmaquick5:amd64  5.54.0-1 amd64  Plasma Runtime
components
ii  libplasma-geolocation-interface5  4:5.14.5-1   amd64  Plasma Workspace for
KF5 library
ii  libplasma34:4.14.38-3  amd64  Plasma Library for
the KDE Platform
ii  plasma-dataengines-addons 4:5.14.5-1   amd64  additional data
engines for Plasma
ii  plasma-desktop4:5.14.5-1   amd64  Tools and widgets for
the desktop
ii  plasma-desktop-data   4:5.14.5-1   allTools and widgets for
the desktop data files
ii  plasma-discover   5.14.5-1 amd64  Discover software
management suite
ii  plasma-discover-common5.14.5-1 allDiscover software
manager suite (common data files)
ii  plasma-framework  5.54.0-1 amd64  Plasma Runtime
components
ii  plasma-integration5.14.5-1 amd64  Qt Platform Theme
integration plugins for KDE Plasma
ii  plasma-nm 4:5.14.5-1   amd64  Plasma5
networkmanager library.
ii  plasma-pa 4:5.14.5-1   amd64  Plasma 5 Volume
controller
ii  plasma-runners-addons 4:5.14.5-1   amd64  additional runners
for Plasma 5 and Krunner
ii  plasma-scriptengine-javascript4:17.08.3-2  amd64  JavaScript script
engine for Plasma
ii  plasma-wallpapers-addons  4:5.14.5-1   amd64  additional wallpaper
plugins for Plasma 5
ii  plasma-widgets-addons 4:5.14.5-1   amd64  additional widgets
for Plasma 5
ii  plasma-workspace  4:5.14.5-1   amd64  Plasma Workspace for
KF5

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

[kwin] [Bug 404146] New: When a QML tabbox skin fails to load, fall back to "Informative" like we do when the configured file does not exist

2019-02-09 Thread Chris Holland
https://bugs.kde.org/show_bug.cgi?id=404146

Bug ID: 404146
   Summary: When a QML tabbox skin fails to load, fall back to
"Informative" like we do when the configured file does
not exist
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: zrenf...@gmail.com
  Target Milestone: ---

Issue was raised when discussing the workaround in
https://phabricator.kde.org/T10464

The relevant code is at:
*
https://github.com/KDE/kwin/blob/cfecb1e0770ca6c8fa879124e11b03081342b9ed/tabbox/tabboxhandler.cpp#L281

1. It first checks if a
"plasma/look-and-feel/%1/contents/windowswitcher/WindowSwitcher.qml" file
exists and uses that.
2. If not, it looks for a "kwin/tabbox/%1/contents/ui/main.qml"
3. Then it uses the hardcoded "informative" QML file
"kwin/tabbox/informative/contents/ui/main.qml" as a fallback (I always wondered
why it was using informative when I selected certain "look and feel" skins).

So it seems we need a new function perform the QML loading stuff which returns
a `QObject` or `nullptr`. Something like this:


QObject *TabBoxHandlerPrivate::loadSwitcherItem(QString file)
{
if (file.isNull()) {
m_qmlComponent->loadUrl(QUrl::fromLocalFile(file));
if (m_qmlComponent->isError()) {
m_qmlComponent.reset(...) // ???
return nullptr;
} else {
QObject *object =
m_qmlComponent->create(m_qmlContext.data());
return object
}
}
}

QObject *TabBoxHandlerPrivate::createSwitcherItem(bool desktopMode)
{
QString lookAndFeelFilepath = desktopMode ? ... : ...
QString file = lookAndFeelFilepath;
QObject *object = loadSwitcherItem(file);
if (object != nullptr) {
return object;
}

QString tabboxFilepath = ...
QString file = tabboxFilepath;
QObject *object = loadSwitcherItem(file);
if (object != nullptr) {
return object;
}

QString informativeTabboxFilepath = ...
QString file = informativeTabboxFilepath;
QObject *object = loadSwitcherItem(file);
if (object != nullptr) {
QStringList args;
args << QStringLiteral("The Window Switcher failed to
load, using Informative")
KProcess::startDetached(QStringLiteral("kdialog"),
args);

return object;
} else {
QStringList args;
args << QStringLiteral("The Window Switcher
installation is broken, resources are missing.\nContact your distribution about
this")
KProcess::startDetached(QStringLiteral("kdialog"),
args);

return nullptr;
}
}

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

[amarok] [Bug 404144] Error message: Could not find requested component

2019-02-09 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=404144

--- Comment #1 from Axel Braun  ---
Created attachment 117953
  --> https://bugs.kde.org/attachment.cgi?id=117953=edit
Debug output when starting amarok

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

  1   2   3   >