[kwin] [Bug 419408] New: The desktop tabbox should not be displayed in the tabbox client switching mode.

2020-03-29 Thread digl
https://bugs.kde.org/show_bug.cgi?id=419408

Bug ID: 419408
   Summary: The desktop tabbox should not be displayed in the
tabbox client switching mode.
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: diguoli...@uniontech.com
  Target Milestone: ---

SUMMARY
In the switching mode (tabbox window mode is switched to the same group mode of
the current window), the desktop tabbox should not be displayed, because the
desktop does not belong to tabbox.

STEPS TO REPRODUCE
Set configuration ShowDesktopMode to ShowDesktopClient, run the kwin_X11
program, and switch tabbox window mode to the same group mode of the current
window in desktop tabbox highlight, can reproduce the problem easily. 

OBSERVED RESULT
the desktop tabbox is displayed.

EXPECTED RESULT
desktop tabbox should not be displayed, no response to this operation.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops

2020-03-29 Thread Henry Pfeil
https://bugs.kde.org/show_bug.cgi?id=419406

--- Comment #2 from Henry Pfeil  ---
Using kcmshell5 kcm_kwin_virtualdesktops, Cube Animation started working when I
changed the Rotation Duration to Default. Still crashes from the System
Settings module. No longer an issue for me, since I can right-click the Task
Manager widget to Configure Virtual Desktops in addition to kcmshell5.
Would Qt 5.13.2 have something to do with it?

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

[okular] [Bug 419359] Embedded video in PDF has wrong size and position

2020-03-29 Thread Elvis Stansvik
https://bugs.kde.org/show_bug.cgi?id=419359

--- Comment #9 from Elvis Stansvik  ---
Thanks a lot for checking Luigi. Maybe my LO bug can be closed as fixed then. I
should have found some newer LO packages to test before filing it.

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

[rkward] [Bug 418591] Keep showing Transferring dialog while loading help files

2020-03-29 Thread Thomas Friedrichsmeier
https://bugs.kde.org/show_bug.cgi?id=418591

--- Comment #5 from Thomas Friedrichsmeier 
 ---
Interesting. That won't be _directly_ related, as we are not even using
qtwebengine, so far (incidentally, I just started working on that, though). But
it might have been a dependency.

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

[systemsettings] [Bug 419406] System Settings - Workspace Behavior - Virtual Desktops

2020-03-29 Thread Henry Pfeil
https://bugs.kde.org/show_bug.cgi?id=419406

--- Comment #1 from Henry Pfeil  ---
`kcmshell5 kcm_kwin_virtualdesktops` works as advertised.

/usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml seems to
be at fault.

Motivation for accessing kcm_kwin_virtualdesktops: Desktop Cube Animation
stopped working. Konsole kcmshell5 reports
qml/org/kde/kirigami.2/FormLayout.qml:112:21: Unable to assign [undefined] to
double
Constructing a KPluginInfo object from old style JSON. Please use
kcoreaddons_desktop_to_json() for
"/usr/lib64/qt5/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so"
instead of kservice_desktop_to_json() in your CMake code.

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

[okular] [Bug 419356] Default pageview (e.g. fit page, fit width) does not register sometimes

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419356

--- Comment #2 from norwegian_panca...@protonmail.ch ---
I just opened a new document to try it out, and the default that I set, Fit
Page, now applies to said document.

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

[ark] [Bug 419309] Multi-volume (splitted) zip cannot be opened using libzip plugin

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419309

2wxsy5823...@opayq.com changed:

   What|Removed |Added

Summary|Ark cannot open |Multi-volume (splitted) zip
   |multi-volume (splitted) zip |cannot be opened using
   ||libzip plugin

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

[frameworks-knewstuff] [Bug 416460] Replace Vokoscreen with VokoscreenNG

2020-03-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=416460

--- Comment #5 from Nate Graham  ---
Thanks! You did great. Fantastic first patch.

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

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-03-29 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=416262

--- Comment #12 from Jan Grulich  ---
(In reply to mirh from comment #11)
> (In reply to Jan Grulich from comment #9)
> > The reason why we disabled them was to avoid hardcoding kernel version
> > requirements. With all those enabled, Qt build was requiring kernel 3.17.y
> > or something like that, why without those enabled it was kernel 2.x.
> 
> If I look at the sources, that was never committed though. 
> 
> I can only see bug 403042 which pertains flatpak specifically, but qt-base
> is still untouched to this day. I just banged my head like two afternoons
> before realizing sddm wasn't booting on 3.16 due to this.

This was pushed only to our Flatpak builds, not to upstream.

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

[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.

2020-03-29 Thread Wayne
https://bugs.kde.org/show_bug.cgi?id=419379

--- Comment #9 from Wayne  ---
I will do so in future,  I just need to learn the correct way to do so.

Thank you for your help and time.

Get Outlook for Android


From: Bug Janitor Service 
Sent: Monday, March 30, 2020 5:33:12 AM
To: wolf-eye...@hotmail.com 
Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new
canvas.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #8 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

--
You are receiving this mail because:
You reported the bug.

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

[okular] [Bug 419224] okular impossible to print

2020-03-29 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=419224

--- Comment #11 from Jan Grulich  ---
The trick is usage of "--socket=cups". It only works with Flatpak 1.6.0 and
newer. Older Flatpak releases don't support CUPS socket.

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

[krita] [Bug 418807] BRUSHES DON'T WORK

2020-03-29 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418807

--- 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 418832] Tiny fonts on Kmymoney 5.0.0 Home page & Reports

2020-03-29 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418832

--- Comment #33 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.

[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.

2020-03-29 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=419379

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #8 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[krita] [Bug 418861] comic manager

2020-03-29 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418861

--- 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.

[kuser] [Bug 419407] New: Managing groups

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419407

Bug ID: 419407
   Summary: Managing groups
   Product: kuser
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: gyu...@freemail.hu
  Reporter: techxga...@outlook.com
  Target Milestone: ---

SUMMARY
KDE needs a way to manage user groups by default, just like LXQt's.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-18-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM

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

[Discover] [Bug 373019] Discover crashed after click on installed application

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=373019

julio.coste...@gmail.com changed:

   What|Removed |Added

 CC||julio.coste...@gmail.com

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

[kdevelop] [Bug 373996] Crash when try to delete file from "Save as..." dialog

2020-03-29 Thread Julian Borrero
https://bugs.kde.org/show_bug.cgi?id=373996

Julian Borrero  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||julbo...@gmail.com
 Status|CONFIRMED   |NEEDSINFO

--- Comment #10 from Julian Borrero  ---
I can't reproduce this bug, my steps were:

1-Open Kdevelop
2-New Project(QT GUI), with GIT and CMake options
3-File->New: WrongName.cpp
4-Edit that file: added a main function
5-Save
6-Save as: delete the WrongName.cpp from the dialog

My setup: Kdevelop 5.4.2, Plasma 5.16.5, Kubuntu 19.10

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

[kamoso] [Bug 416951] kamoso crash after click record a video button

2020-03-29 Thread Ian Nicholson
https://bugs.kde.org/show_bug.cgi?id=416951

Ian Nicholson  changed:

   What|Removed |Added

 CC||i...@binaryash.net

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

[kamoso] [Bug 416951] kamoso crash after click record a video button

2020-03-29 Thread Ian Nicholson
https://bugs.kde.org/show_bug.cgi?id=416951

--- Comment #5 from Ian Nicholson  ---
Created attachment 127099
  --> https://bugs.kde.org/attachment.cgi?id=127099&action=edit
New crash information added by DrKonqi

kamoso (3.2.3) using Qt 5.12.4

- What I was doing when the application crashed: The camera display that Kamoso
showed was white, I clicked the "take a picture" button at the bottom of the
window, then clicked the "take a video" button" next to it, at which point
Kamoso crashed

- Custom settings of the application:Creative Labs N10225 webcam

-- Backtrace (Reduced):
#11 0x7f9362aec93d in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlContextData*, QFlags)
() from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f9362a33b59 in
QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData*, QV4::Value const&) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f9362a344de in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*,
QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&)
() from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f9362a34633 in QV4::QObjectWrapper::virtualPut(QV4::Managed*,
QV4::PropertyKey, QV4::Value const&, QV4::Value*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
[...]
#18 0x7f93629df093 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5

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

[systemsettings] [Bug 419406] New: System Settings - Workspace Behavior - Virtual Desktops

2020-03-29 Thread Henry Pfeil
https://bugs.kde.org/show_bug.cgi?id=419406

Bug ID: 419406
   Summary: System Settings - Workspace Behavior - Virtual
Desktops
   Product: systemsettings
   Version: 5.18.3
  Platform: Slackware Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: hpf...@psnarf.org
  Target Milestone: ---

Application: systemsettings5 (5.18.3)

Qt Version: 5.13.2
Frameworks Version: 5.68.0
Operating System: Linux 5.4.28 x86_64
Windowing system: X11
Distribution: Slackware 14.2 x86_64 (post 14.2 -current)

-- Information about the crash:
- What I was doing when the application crashed:
In Workspace Behavior, choose Virtual Desktops, instant crash.
It was working as advertised, kwinrc contains my 6 virtual desktops.
Slackware-current upgrade introduced the crashes. Full system reinstall,
created a new user, same crashes.

The crash can be reproduced every time.

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

Thread 29 (Thread 0x7f03e700 (LWP 9050)):
#0  0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f047eba4d6b in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#2  0x7f047eba49d7 in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#3  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#4  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f0409cae700 (LWP 9048)):
#0  0x7f048bb51e9f in poll () at /lib64/libc.so.6
#1  0x7f04880a53ee in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f04880a550f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f048c25739b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f048c20292b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f048c03cc31 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f048dfdca05 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f048c03dc73 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#9  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f04165b5700 (LWP 8991)):
#0  0x7f048bb51e9f in poll () at /lib64/libc.so.6
#1  0x7f04880a53ee in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f04880a5753 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f040a5e66c6 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f04880cd13d in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#6  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f04179ee700 (LWP 8990)):
#0  0x7f048bb51e9f in poll () at /lib64/libc.so.6
#1  0x7f04880a53ee in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f04880a550f in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f04880a5561 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f04880cd13d in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#6  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f040b6d3700 (LWP 8936)):
#0  0x7f048bb4d86c in read () at /lib64/libc.so.6
#1  0x7f0415c959c1 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-13.0.so
#2  0x7f0415d16a2e in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f0415d17460 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f0415d17520 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f0415d24df6 in  () at /usr/lib64/libpulse.so.0
#6  0x7f0415cbffc8 in  () at /usr/lib64/pulseaudio/libpulsecommon-13.0.so
#7  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#8  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f0428965700 (LWP 8880)):
#0  0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f047eba4d6b in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#2  0x7f047eba49d7 in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#3  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#4  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f0429477700 (LWP 8879)):
#0  0x7f048b609966 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f047eba4d6b in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#2  0x7f047eba49d7 in  () at /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#3  0x7f048b60306b in start_thread () at /lib64/libpthread.so.0
#4  0x7f048bb5d72f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f042a078700 (LWP 8878)):
#0  0x7f048b60996

[lattedock] [Bug 419405] adding a 3rd dock to the bottom breaks latte

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419405

--- Comment #1 from andresdor...@gmail.com ---
Created attachment 127098
  --> https://bugs.kde.org/attachment.cgi?id=127098&action=edit
t

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

[systemsettings] [Bug 418730] [Wayland] System Settings may crash when entering Regional Settings for the first time

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=418730

--- Comment #1 from magib...@hotmail.com ---
Another crash. This time when entering the Appearance > Cursors section.
All these System Settings entries take a few seconds to load on my HDD. In the
backtraces, a 'timeout' parameter can be seen in calls close to the error. I
wonder if that has anything to do with the issue.

> Application: System Settings (systemsettings5), signal: Aborted
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> [Current thread is 1 (Thread 0x7f71050dfcc0 (LWP 15254))]
> 
> Thread 10 (Thread 0x7f70e57e1700 (LWP 16653)):
> #0  0x7f7107779479 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
> #1  0x7f71077ca56e in g_main_context_acquire () from 
> /usr/lib/libglib-2.0.so.0
> #2  0x7f71077ca647 in ?? () from /usr/lib/libglib-2.0.so.0
> #3  0x7f71077ca871 in g_main_context_iteration () from 
> /usr/lib/libglib-2.0.so.0
> #4  0x7f7109dbe0ec in QEventDispatcherGlib::processEvents 
> (this=0x7f70d40f93f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
> #5  0x7f7109d6457c in QEventLoop::exec (this=this@entry=0x7f70e57e0d40, 
> flags=..., flags@entry=...) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:136
> #6  0x7f7109b88e62 in QThread::exec (this=) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:118
> #7  0x7f7108e28f89 in ?? () from /usr/lib/libQt5Qml.so.5
> #8  0x7f7109b89fd6 in QThreadPrivate::start (arg=0x563044a19d40) at 
> thread/qthread_unix.cpp:342
> #9  0x7f71083e246f in start_thread () from /usr/lib/libpthread.so.0
> #10 0x7f71098103d3 in clone () from /usr/lib/libc.so.6
> 
> Thread 9 (Thread 0x7f70dbfff700 (LWP 16456)):
> #0  0x7f71098014fc in read () from /usr/lib/libc.so.6
> #1  0x7f71077798c0 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x7f71077c9001 in g_main_context_check () from 
> /usr/lib/libglib-2.0.so.0
> #3  0x7f71077ca748 in ?? () from /usr/lib/libglib-2.0.so.0
> #4  0x7f71077ca871 in g_main_context_iteration () from 
> /usr/lib/libglib-2.0.so.0
> #5  0x7f7109dbe0ec in QEventDispatcherGlib::processEvents 
> (this=0x7f70d0017870, flags=...) at kernel/qeventdispatcher_glib.cpp:425
> #6  0x7f7109d6457c in QEventLoop::exec (this=this@entry=0x7f70dbffed60, 
> flags=..., flags@entry=...) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:136
> #7  0x7f7109b88e62 in QThread::exec (this=) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:118
> #8  0x7f7109b89fd6 in QThreadPrivate::start (arg=0x563041e52ca0) at 
> thread/qthread_unix.cpp:342
> #9  0x7f71083e246f in start_thread () from /usr/lib/libpthread.so.0
> #10 0x7f71098103d3 in clone () from /usr/lib/libc.so.6
> 
> Thread 8 (Thread 0x7f70f92b6700 (LWP 15262)):
> #0  0x7f7107779479 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
> #1  0x7f71077ca08c in g_main_context_prepare () from 
> /usr/lib/libglib-2.0.so.0
> #2  0x7f71077ca6c6 in ?? () from /usr/lib/libglib-2.0.so.0
> #3  0x7f71077ca871 in g_main_context_iteration () from 
> /usr/lib/libglib-2.0.so.0
> #4  0x7f7109dbe0ec in QEventDispatcherGlib::processEvents 
> (this=0x7f70dc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
> #5  0x7f7109d6457c in QEventLoop::exec (this=this@entry=0x7f70f92b5d40, 
> flags=..., flags@entry=...) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:136
> #6  0x7f7109b88e62 in QThread::exec (this=) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:118
> #7  0x7f7108e28f89 in ?? () from /usr/lib/libQt5Qml.so.5
> #8  0x7f7109b89fd6 in QThreadPrivate::start (arg=0x5630368ea7a0) at 
> thread/qthread_unix.cpp:342
> #9  0x7f71083e246f in start_thread () from /usr/lib/libpthread.so.0
> #10 0x7f71098103d3 in clone () from /usr/lib/libc.so.6
> 
> Thread 7 (Thread 0x7f70faffd700 (LWP 15261)):
> #0  0x7f7109805abf in poll () from /usr/lib/libc.so.6
> #1  0x7f71077ca7a0 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x7f71077ca871 in g_main_context_iteration () from 
> /usr/lib/libglib-2.0.so.0
> #3  0x7f7109dbe0ec in QEventDispatcherGlib::processEvents 
> (this=0x7f70eb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
> #4  0x7f7109d6457c in QEventLoop::exec (this=this@entry=0x7f70faffcd40, 
> flags=..., flags@entry=...) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:136
> #5  0x7f7109b88e62 in QThread::exec (this=) at 
> ../../include/QtCore/../../src/corelib/global/qflags.h:118
> #6  0x7f7108e28f89 in ?? () from /usr/lib/libQt5Qml.so.5
> #7  0x7f7109b89fd6 in QThreadPrivate::start (arg=0x5630366cae30) at 
> thread/qthread_unix.cpp:342
> #8  0x7f71083e246f in start_thread () from /usr/lib/libpthread.so.0
> #9  0x7f71098103d3 in clone () from /usr/lib/libc.so.6
> 
> Thread 6 (Thread 0x7f70fb7fe700 (LWP 15260)):
> #0  0x7f71083e8cf5 in pthread_cond_wait@@GLIBC_2.3.2 () from 
> /usr/lib/libpthread.so.0
> #1  

[www.kde.org] [Bug 419403] Create User Suggestions Page

2020-03-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419403

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||n...@kde.org
 Resolution|--- |NOT A BUG

--- Comment #1 from Nate Graham  ---
https://bugs.kde.org is still the right place for this. :) We read your bug
reports and have conversations with users daily on proposed features. The
"wishlist" status is adequate, for our purposes at least, to know that a bug
report is a feature request. In the end it's just more efficient for everyone
to have all the data in once place.

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

[lattedock] [Bug 419405] New: adding a 3rd dock to the bottom breaks latte

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419405

Bug ID: 419405
   Summary: adding a 3rd dock to the bottom breaks latte
   Product: lattedock
   Version: 0.9.10
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: andresdor...@gmail.com
  Target Milestone: ---

SUMMARY

adding a 3rd dock to the bottom of the screen makes latte start flickering
STEPS TO REPRODUCE
1. create a 3rd dock after having one on the left and on the top
2. it should create the new dock on the bottom
3. latte will start freaking out and you cant even remove the dock as the
settings page is unusable since its flickering

OBSERVED RESULT

everything is flickering preventing me from using latte dock
EXPECTED RESULT
no flicker latte works as expected

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.18.3
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version:5.68 
Qt Version: 5.14.1

ADDITIONAL INFORMATION

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

[kamoso] [Bug 419404] New: Kamoso crashes on startup when webcam is plugged in

2020-03-29 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=419404

Bug ID: 419404
   Summary: Kamoso crashes on startup when webcam is plugged in
   Product: kamoso
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: ejsta...@joyrex.net
  Target Milestone: ---

Application: kamoso (19.12.3)

Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.5.13-arch1-1 x86_64
Windowing system: X11
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:
Opening Kamoso with webcam plugged in.  When it's unplugged, this doesn't
happen.  Kamoso opens fine.  When the webcam gets plugged in Kamoso will then
crash.  I plugged the webcam into a different USB bus and received the same
result.

- Custom settings of the application:

$ sudo lsusb -v -s 001:007

Bus 001 Device 007: ID 046d:08aa Logitech, Inc. Labtec Notebooks
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0x08aa Labtec Notebooks
  bcdDevice1.00
  iManufacturer   0 
  iProduct2 Camera 
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0150
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0080  1x 128 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   2
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x00c0  1x 192 bytes
bInterval   1
  Endpoint Descriptor:
bLength

[www.kde.org] [Bug 419403] New: Create User Suggestions Page

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419403

Bug ID: 419403
   Summary: Create User Suggestions Page
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: squidin...@gmail.com
  Target Milestone: ---

The release of KDE 5.18 introduced the user feedback tool, which indicates that
the developers wish to learn more about how people use KDE and what features
they like. 
I thought that it would be a nice addition if on the KDE website there was a
special page for suggestions and feature requests, separate from bugs.kde.org,
which feels out of place for feature requests. users could submit ideas (like
this one) to the dev team and others could vote on which ones they would like
to be implemented. It would be a nice way to interact with users to improve KDE
for everyone.

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

[kwin] [Bug 419402] New: [Wayland] Only mouse cursor is drawn after updating Window Decorations

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419402

Bug ID: 419402
   Summary: [Wayland] Only mouse cursor is drawn after updating
Window Decorations
   Product: kwin
   Version: 5.18.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: magib...@hotmail.com
  Target Milestone: ---

SUMMARY

When changing Window Decorations settings through the System Settings
application, the display enters in a state where only the mouse cursor is being
updated.

STEPS TO REPRODUCE
1. Start a Plasma Wayland session.
2. Open System Settings and go to Application Style > Window Decorations.
3. Change the window border size setting and click on Apply to make the changes
effective.

OBSERVED RESULT

You can move the mouse cursor around, but nothing else is updated on screen.
The window manager is still working because the cursor's shape changes when
hovering over text areas or dragging windows from the titlebar. If switching to
another VT and then back to Plasma, the mouse cursor is still there but
everything else is black.

After restarting plasma, the new settings set in Window Decorations are
working.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.5.13-arch1-1
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 11,6 GiB of RAM

ADDITIONAL INFORMATION

Changing the Window Decoration settings causes the following messages to be
logged to stdout/stderr:

> libpng error: profile 'Generic RGB Profile': 0h: length does not match profile
> libpng error: profile 'sRGB IEC61966-2.1': 40F0C6E4h: length does not match 
> profile
> kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/tags.so' from launcher.
> kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/tags.so'
> kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/trash.so' from launcher.
> kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/trash.so'
> kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/file.so' from launcher.
> kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/file.so'
> kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/file.so' from launcher.
> kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/file.so'
> kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/file.so' from launcher.
> kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/file.so'
> kdeinit5: PID 14273 terminated.
> kdeinit5: PID 14268 terminated.
> kdeinit5: PID 14270 terminated.
> kdeinit5: PID 14272 terminated.
> kdeinit5: PID 14269 terminated.
> OpenGL vendor string:   Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 
> (Skylake GT2) 
> OpenGL version string:  4.6 (Core Profile) Mesa 19.3.4
> OpenGL shading language version string: 4.60
> Driver: Intel
> GPU class:  Unknown
> OpenGL version: 4.6
> GLSL version:   4.60
> Mesa version:   19.3.4
> X server version:   1.20.7
> Linux kernel version:   5.5.13
> Requires strict binding:no
> GLSL shaders:   yes
> Texture NPOT support:   yes
> Virtual Machine:no
> Filter multi-plane format 961959257
> Filter multi-plane format 825316697
> Filter multi-plane format 842093913
> Filter multi-plane format 909202777
> Filter multi-plane format 875713881
> Filter multi-plane format 961893977
> Filter multi-plane format 825316953
> Filter multi-plane format 842094169
> Filter multi-plane format 909203033
> Filter multi-plane format 875714137
> Filter multi-plane format 842094158
> Filter multi-plane format 909203022
> CoverSwitchConfig::instance called after the first use - ignoring
> FlipSwitchConfig::instance called after the first use - ignoring
> KscreenConfig::instance called after the first use - ignoring
> MouseClickConfig::instance called after the first use - ignoring
> SlideConfig::instance called after the first use - ignoring
> SlidingPopupsConfig::instance called after the first use - ignoring

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

[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.

2020-03-29 Thread David Lopes
https://bugs.kde.org/show_bug.cgi?id=414576

David Lopes  changed:

   What|Removed |Added

 CC||davidlopesplay...@gmail.com

--- Comment #48 from David Lopes  ---
Krita

 Version: 4.2.9
 Languages: en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en,
en_US, en, en_US, en, pt_BR, pt, en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.7
  Version (loaded): 5.12.7

OS Information

  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.18363
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info

  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce 9600 GSO 512/PCIe/SSE2" 
  Version:  "3.3.0" 
  Shading language:  "3.30 NVIDIA via Cg compiler" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 3.3, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 3.3
 Supports deprecated functions true 
 is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: false 
  isQtPreferAngle: false 

Hardware Information

  GPU Acceleration: desktop
  Memory: 4095 Mb
  Number of Cores: 2
  Swap Location: C:/Users/david/AppData/Local/Temp

Current Settings

  Current Swap Location: C:/Users/david/AppData/Local/Temp
  Undo Enabled: 1
  Undo Stack Limit: 30
  Use OpenGL: 1
  Use OpenGL Texture Buffer: 1
  Use AMD Vectorization Workaround: 0
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 900
  Use Backup Files: 1
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Use Win8 Pointer Input: 0
  Use RightMiddleTabletButton Workaround: 0
  Levels of Detail Enabled: 0
  Use Zip64: 0


Display Information
Number of screens: 1
Screen: 0
Name: \\.\DISPLAY1
Depth: 32
Scale: 1
Resolution in pixels: 1280x1024
Manufacturer: 
Model: 
Refresh Rate: 60
















i have the same bug, and i use xp-pen star 03


this bug started after 4.2.8 update

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

[kscreenlocker] [Bug 419355] Unable to log back in after screensaver

2020-03-29 Thread John Bennett
https://bugs.kde.org/show_bug.cgi?id=419355

--- Comment #2 from John Bennett  ---
:/$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop 
OpenGL version string:  3.0 Mesa 19.2.8
OpenGL shading language version string: 1.30
Driver: Intel
GPU class:  Haswell
OpenGL version: 3.0
GLSL version:   1.30
Mesa version:   19.2.8
Linux kernel version:   5.3
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
"file:///usr/share/plasma/wallpapers/org.kde.plasma.worldmap/contents/ui/main.qml"
 
 "Error loading QML file.\n23: module \"org.kde.marble.private.plasma\" is not
installed\n"
Locked at 1585529631
UdevQt: unable to create udev monitor connection
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:138:13:
QML PropertyChanges: Cannot assign to non-existent property "opacity"
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:139:17:
Unable to assign [undefined] to QObject*
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/lockscreen/LockScreenUi.qml:158:
ReferenceError: wallpaper is not defined
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/SessionManagementScreen.qml:64:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/ActionButton.qml:33:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/KeyboardLayoutButton.qml:29:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/Battery.qml:48:9:
Unable to assign [undefined] to double
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/UserDelegate.qml:41:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:120:17:
Unable to assign [undefined] to QObject*
file:///usr/share/plasma/look-and-feel/org.feren.dark/contents/components/WallpaperFader.qml:119:13:
QML PropertyChanges: Cannot assign to non-existent property "opacity"


Works OK. But, as I said, issue is intermittent...

*Do you know if Feren OS has a customised lock screen compared to default
Plasma?*
Not sure, but when invoked, these services run:
kscreenlocker_greet
kcheckpass

Thanks.

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

[systemsettings] [Bug 419141] Cannot create more than one row on the "Virtual Desktops" settings page

2020-03-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419141

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.18.4
  Latest Commit||https://commits.kde.org/kwi
   ||n/ae022e92c9f516877fa59d510
   ||4a84c981895cddf
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Nate Graham  ---
Git commit ae022e92c9f516877fa59d5104a84c981895cddf by Nate Graham, on behalf
of Eugene Popov.
Committed on 30/03/2020 at 00:15.
Pushed by ngraham into branch 'Plasma/5.18'.

[kcmkwin/kwindesktop] Fix inability to create more than one row on the "Virtual
Desktops" settings page

Summary:
When a spinbox with the number of rows loses focus, the value of this spinbox
(i.e., the count of rows) is always reset to 1. Thus, it's impossible to create
more then one row.

To fix this bug, we need to implement `valueFromText` function.
FIXED-IN: 5.18.4

Reviewers: ngraham, zzag, davidedmundson

Reviewed By: ngraham, davidedmundson

Subscribers: kwin

Tags: #kwin

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

M  +1-0kcmkwin/kwindesktop/package/contents/ui/main.qml

https://commits.kde.org/kwin/ae022e92c9f516877fa59d5104a84c981895cddf

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

[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=385920

h...@live.com changed:

   What|Removed |Added

 CC||h...@live.com

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

[plasmashell] [Bug 419401] New: Plasma Crashed when changing volume

2020-03-29 Thread Christian
https://bugs.kde.org/show_bug.cgi?id=419401

Bug ID: 419401
   Summary: Plasma Crashed when changing volume
   Product: plasmashell
   Version: 5.18.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: legonxtj...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.3)

Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.4.28-1-MANJARO x86_64
Windowing system: X11
Distribution: Manjaro Linux

-- Information about the crash:
- What I was doing when the application crashed:
I have a Logitech G933 headphone, which has a volume wheel. I attempted
to use the wheel to increase my volume when the system crashed. This is rare,
and increasing the volume now works as expected
- Unusual behavior I noticed:
When I first turned my headset on. I heard nothing. Clicking on the
default volume plasmoid did not produce a working window, it was jumbled up
graphical artifacting of I believe the plasma task bar. I clicked the window
several times before I attempted to increase the volume with my headphones and
produced the crash
- Custom settings of the application:
I am running Plasma with "export KDEWM=/usr/bin/i3" to use i3 as my
window manager in the plasma session. I dont believe it is causing an issue,
but is important to know

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

Thread 12 (Thread 0x7f5e81159700 (LWP 69577)):
#0  0x7f5ebe553cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5ebf113cc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f5ebf113da2 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f5ec0e7156b in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f5ec0e717fb in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f5ebf10dfd6 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5ebe54d46f in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5ebed943d3 in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f5e8195a700 (LWP 69345)):
#0  0x7f5ebed89abf in poll () at /usr/lib/libc.so.6
#1  0x7f5ebd62a7a0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5ebd62a871 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5ebf3420ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5ebf2e857c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5ebf10ce62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5ebf10dfd6 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f5ebe54d46f in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5ebed943d3 in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f5e83fff700 (LWP 69288)):
#0  0x7f5ebe553cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5ebf113cc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f5ebf113da2 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f5ec0e7156b in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f5ec0e717fb in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f5ebf10dfd6 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5ebe54d46f in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5ebed943d3 in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f5e8a293700 (LWP 69183)):
#0  0x7f5ebed854fc in read () at /usr/lib/libc.so.6
#1  0x7f5ebd5d98c0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5ebd629001 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f5ebd62a748 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f5ebd62a871 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f5ebf3420ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f5ebf2e857c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f5ebf10ce62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f5e8a79f16b in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#9  0x7f5ebf10dfd6 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f5ebe54d46f in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f5ebed943d3 in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f5e97e8c700 (LWP 68798)):
#0  0x7f5ebd62823d in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f5ebd628cf6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5ebd629fbb in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5ebd62a6c6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f5ebd62a871 in g_main_context_itera

[plasmashell] [Bug 419310] Kickoff (also maybe for alternative menus too): Security concerns

2020-03-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419310

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.18.4

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

[systemsettings] [Bug 418466] Intalled Global themes not showing up in Setting's Global theme section.

2020-03-29 Thread Pieter van der Vegte
https://bugs.kde.org/show_bug.cgi?id=418466

Pieter van der Vegte  changed:

   What|Removed |Added

 CC||pvdve...@posteo.net

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

[plasmashell] [Bug 354541] panel flickers a lot

2020-03-29 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=354541

João Vidal da Silva  changed:

   What|Removed |Added

 CC|joao.vidal.si...@gmail.com  |

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

[ktorrent] [Bug 314958] ktorrent will not download / find peers / move *some* magnetic links into the queue even thought they "should" have plenty seeders/leechers :( ..also clicking same magnet twice

2020-03-29 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=314958

João Vidal da Silva  changed:

   What|Removed |Added

 CC|joao.vidal.si...@gmail.com  |

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

[plasmashell] [Bug 346658] no option for suspend

2020-03-29 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=346658

João Vidal da Silva  changed:

   What|Removed |Added

 CC|joao.vidal.si...@gmail.com  |

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

[kscreenlocker] [Bug 419400] New: kscreenlocker lock screen "after waking from sleep" option does not work

2020-03-29 Thread Logan Rathbone
https://bugs.kde.org/show_bug.cgi?id=419400

Bug ID: 419400
   Summary: kscreenlocker lock screen "after waking from sleep"
option does not work
   Product: kscreenlocker
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: popro...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY

I am not sure why, as it used to work - but at some point in time,
kscreenlocker's "Lock screen: after waking from sleep" option stopped working.
Upon wake from sleep, the desktop simply resumes on my system, regardless of my
settings.


EXPECTED RESULT

Settings should be honoured; screen should successfully lock upon resume if
that is what my settings are.

SOFTWARE/OS VERSIONS

Linux

Operating System: Slackware Current (ktown; mostly vanilla builds)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2
Kernel Version: 4.14.59
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4710HQ CPU @ 2.50GHz
Memory: 7.7 GiB of RAM

kscreenlocker version:  5.18.3

ADDITIONAL INFORMATION

I am not running systemd. Perhaps that has something to do with it. Running
ConsoleKit2 &c.

Contents of my ~/.config/kscreenlockerrc file:

***
[$Version]
update_info=kscreenlocker.upd:0.1-autolock

[Greeter]
Theme=org.kde.breeze.desktop

[Greeter][Wallpaper][org.kde.image][General]
Image=file:///usr/share/wallpapers/Next/contents/images/1366x768.png
***

I also tried manually adding:

[Daemon]
LockOnResume=true

to the configfile, and it made no difference.

Marking this as "major" as it has security (with a small "s") implications.

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

[krita] [Bug 419399] New: Laggy interface with kinetic scrolling and canvas and UI glitches.

2020-03-29 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=419399

Bug ID: 419399
   Summary: Laggy interface with kinetic scrolling and canvas and
UI glitches.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: rgbe...@gmail.com
  Target Milestone: ---

Created attachment 127097
  --> https://bugs.kde.org/attachment.cgi?id=127097&action=edit
Screenshot of blacked out presets.

SUMMARY
With the git Next build of krita 4.30 and in the master branch build via git,
there is stutter and lag when using kinetic scrolling in the dockers and the
interface. The most noticeable is when scrolling in the dockers or preset
menus. 
Any zooming, on the canvas, in and out is choppy as well; there is no smooth
transition/animation. 
When resizing the brush size via the keyboard and pen input, the animation
stutters and is laggy as well. Adjustments made using the value bars with the
mouse behaves the same. The reference image opacity and saturation bars are the
worst.
In the preset docker and in the brush editor, several of the preset
images/previews are blacked out. And when opening the "chose preset" button on
the top glitches and shows the painting/image before the preset images appear.
The preset images are all the default ones and this issue is not in the
previous versions/builds of krita.
Then when saving manually, the save time is unusually long.
All this with the OpenGL enabled.

STEPS TO REPRODUCE
1. Any time krita version 4.30 or git master is opened the interface and
blacked out icons are present. 
2. Scrolling in dockers or resize bar animations stutter or lag out when
changing.
3. Saving the document takes a very long time to finish.

OBSERVED RESULT
Laggy interface and poor performance.
Missing icon images and unresponsive controls every time.

EXPECTED RESULT
A smooth working interface and tools, especially when the previous version, or
pre-update did not suffer from these issues.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.5.3-gentoo-x86_64
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-5820K CPU @ 3.30GHz
Memory: 15.5 GiB of RAM


ADDITIONAL INFORMATION

I had not had any changes on my system except to upgrade to the newest
kde-frameworks version 5.68.0. But once I updated my git version I could not go
back to what I had built before (which worked fine). The build started to throw
errors with cmake and now I can no longer build krita via git on my system. So
right now I am using the krita appimages but the same issues are present in
Next build as well.

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

[Spectacle] [Bug 419398] New: When using rectangular region mode with two monitors area of capturing becomes small

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419398

Bug ID: 419398
   Summary: When using rectangular region mode with  two monitors
area of capturing becomes small
   Product: Spectacle
   Version: 19.04.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: desudesu...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. I have two monitors with different resolution and screen scaling 1.7
2. I use rectangular region mode of caturing


OBSERVED RESULT

The area of possible capturing becomes small so I can not capture some area at
all

EXPECTED RESULT

I can screen any area I see

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.14 

ADDITIONAL INFORMATION
Kubuntu 19.10

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

[krita] [Bug 419397] New: Reference image open in another window deletes when using transform tool in other window.

2020-03-29 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=419397

Bug ID: 419397
   Summary: Reference image open in another window deletes when
using transform tool in other window.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: rgbe...@gmail.com
  Target Milestone: ---

SUMMARY
In Krita git master and 4.2.9 appimage on gentoo linux, when using a reference
image in another sub window, that has been zoomed in, and in the other sub
window that has the painting, if the transform tool is used on the painting
document. Then the reference, that is in the it's own window, will be deleted
until enter is hit to set the transform on the other document and then will
reappear.

STEPS TO REPRODUCE
1. Have to have the two sub-windows open beside each other. 
2. Zoom in on the reference window. 
3. Use the selection tool to isolate an area on the painting document, then use
the transform tool to edit the painting.

OBSERVED RESULT
The other document/image is deleted and doesn't remain until on the painted
document is finished with hitting enter when transform tool is used.

EXPECTED RESULT
Thes expected result is the image in another sub-window not to be affected when
the focus is in another sub-window/document.

SOFTWARE/OS VERSIONS

Operating System: Gentoo Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.5.3-gentoo-x86_64
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-5820K CPU @ 3.30GHz
Memory: 15.5 GiB of RAM


ADDITIONAL INFORMATION

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

[Falkon] [Bug 406375] Falkon KDE Frameworks Integration: KIO URLs are not saved in the browser history

2020-03-29 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=406375

--- Comment #2 from Kevin Kofler  ---
Ping?

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

[kio-gopher] [Bug 406383] kio-gopher 0.1.99 fails to display URLs containing a question mark separator, e.g. on Veronica2

2020-03-29 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=406383

--- Comment #2 from Kevin Kofler  ---
Ping?

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

[KBibTeX] [Bug 417210] Edit Element dialog closes w/o confirming, possibly losing edits

2020-03-29 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=417210

Thomas Fischer  changed:

   What|Removed |Added

  Latest Commit|3e145c0516a9eaaf8d035fb471d |22ca454abbd7f3a8576844f1140
   |4c40e   |019ed1

--- Comment #7 from Thomas Fischer  ---
New forced push to test repository/branch.

> Tested. All appear resolved except (d). Current behavior on Plain
> Text/Reference/Source Code dropdown menus is:
> 
> - dropdown menu changes do trigger the discard dialog, but...
> 
> - when the attached text field is blank, the dropdown menu's value is
> "saved" whether the user discarded or saved
That should be fixed. Issue was for blank values the reset of the widget was
skipped, ignoring that the type (plain/reference) may have been changed.

> - but I think the menu value only gets saved to the dialog window. Example:
> I have 2 elements, both w/ a blank Abstract. The pulldown menu for both
> elements' Abstracts are set to Plain Text. I edit element 1 and change its
> Abstract's dropdown from Plain to Source. Whether I discard the change or
> not, if I then re-open element 1, the Abstract dropdown is still set to
> Source. If I view the 2nd element, its Abstract's dropdown also shows Source.
This is mostly a GUI glitch. I think I fixed that now.

> - in contrast, when the Abstract field isn't blank, the pulldown menu always
> says Plain Text -- if I change it to Source and click OK, then re-open, it
> still says Plain.
> - ... however, even if the field says Plain Text, TeX commands are
> interpreted correctly in e.g. the Reference Preview. In effect, maybe Source
> Code is really always set, but the dropdown always shows Plain Text.
Actually, there are just two types in most cases:
1. plain text like   title={Hello}   which just shows the text inside the curly
brackets. For deeper-nested curly brackets like   title={{A}bc {D}ef}  just the
outer pair is hidden, and  {A}bc {D}ef  is shown
2. reference like  title=Hello  which refers to a string macro with key  Hello
Source is just showing how the value would look like in a BibTeX file, meaning
for plain text it would include the outer curly brackets. However, it is no
type on its own and only meant for inspection or manual editing. As you can
easily shoot yourself into the foot by entering invalid BibTeX code, this mode
should be used with care.

Please test the latest code and let me know if that fixes all problems. I was
trying to follow your explanation, but I cannot rule out that I missed
something.

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

[krusader] [Bug 419396] New: When trying to open a 7z encrypted archive, Krusader does not ask for a password

2020-03-29 Thread Toni Asensi Esteve
https://bugs.kde.org/show_bug.cgi?id=419396

Bug ID: 419396
   Summary: When trying to open a 7z encrypted archive, Krusader
does not ask for a password
   Product: krusader
   Version: Git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: krarc
  Assignee: krusader-bugs-n...@kde.org
  Reporter: toni.ase...@kdemail.net
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY

When trying to open a 7z encrypted archive: Krusader does not ask for a
password (as it does when opening e.g. encrypted zip archives). Instead,
Krusader waits a lot, and finally shows only "..".

STEPS TO REPRODUCE

1) Creating a 7z encrypted archive that can not be browsed without a password
(because its headers are also encrypted):
7z a /tmp/test-mhe.7z -mhe -ptest /etc/papersize /etc/hosts
entering the archive, and finding problems (like not being asked for a
password, waiting a lot, and finally seeing only "..").

2) Creating a 7z encrypted archive that can be browsed without the password:
7z a /tmp/test-without-mhe.7z -ptest /etc/hosts /etc/hosts.allow
/etc/hosts.deny
entering the archive, and finding problems when trying to use F3 to see the
content of e.g. its "hosts" file.

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

[kdiff3] [Bug 406576] Windows binaries for new versions of kdiff3

2020-03-29 Thread michael
https://bugs.kde.org/show_bug.cgi?id=406576

michael  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from michael  ---
Posted at
https://download.kde.org/stable/kdiff3/kdiff3-1.8.2-windows-64-cl.exe.mirrorlist

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

[krusader] [Bug 413428] Please add bookmarks for "folder pairs"

2020-03-29 Thread Toni Asensi Esteve
https://bugs.kde.org/show_bug.cgi?id=413428

Toni Asensi Esteve  changed:

   What|Removed |Added

 CC||toni.ase...@kdemail.net
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Toni Asensi Esteve  ---
Hi! Does a "Synchronizer Profile" work for your case?

Some notes:

"If you regularly perform the same synchronize operation, you can save the
synchronize settings in a Synchronizer Profile.":
https://docs.kde.org/trunk5/en/extragear-utils/krusader/profiles.html#synchronizer_profiles

"Profiles: If you have to synchronize the same folders often, you can save the
settings e.g. include files, exclude files, ... Press the Profile button, and
you will be able to add / load / save / remove synchronizer profiles.":
https://docs.kde.org/trunk5/en/extragear-utils/krusader/synchronizer.html

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

[kdiff3] [Bug 419284] KDiff3 crashes when dialogue box cancelled on possibly binary file warning

2020-03-29 Thread michael
https://bugs.kde.org/show_bug.cgi?id=419284

michael  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from michael  ---
Are you able to reproduce this in 1.8.2?
https://download.kde.org/stable/kdiff3/kdiff3-1.8.2.tar.xz.mirrorlist.

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

[ksysguard] [Bug 418491] ksysguard crashes on close

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=418491

benaventeadr...@gmail.com changed:

   What|Removed |Added

 CC||benaventeadr...@gmail.com

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

[gwenview] [Bug 419395] New: Crash while browsing

2020-03-29 Thread marco
https://bugs.kde.org/show_bug.cgi?id=419395

Bug ID: 419395
   Summary: Crash while browsing
   Product: gwenview
   Version: 18.04.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: marcobe...@gmail.com
  Target Milestone: ---

Application: gwenview (18.04.3)

Qt Version: 5.11.3
Frameworks Version: 5.55.0
Operating System: Linux 5.0.16-100.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Twenty Eight)"

-- Information about the crash:
I was browsing a directory with images.
When I tried to change to a neighbour directory using the breadcumb the crash
happened

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7fbba1bdc700 (LWP 10318)):
#0  0x7fbbbd12cb1d in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fbbbd0e5d6c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7fbbc5ac9d5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fbbc5a785bb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fbbc58e0c16 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fbbc7aaeb39 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#6  0x7fbbc58ea08b in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fbbc42c0594 in start_thread () from /lib64/libpthread.so.0
#8  0x7fbbc4c25e5f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fbba8d61700 (LWP 10317)):
#0  0x7fbbc4c1b329 in poll () from /lib64/libc.so.6
#1  0x7fbbc2a5204f in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fbbc2a53caa in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fbbaac9cf09 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7fbbc58ea08b in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fbbc42c0594 in start_thread () from /lib64/libpthread.so.0
#6  0x7fbbc4c25e5f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fbbcde506c0 (LWP 10316)):
[KCrash Handler]
#6  0x7fbbc5aba22b in (anonymous namespace)::clear(QVariant::Private*) ()
from /lib64/libQt5Core.so.5
#7  0x7fbbcd369bc8 in QMap::~QMap() () from
/lib64/libgwenviewlib.so.5
#8  0x7fbbcd365f82 in
Gwenview::MprisMediaPlayer2Player::onMetaInfoUpdated() () from
/lib64/libgwenviewlib.so.5
#9  0x7fbbcd3668d1 in
Gwenview::MprisMediaPlayer2Player::onCurrentUrlChanged(QUrl const&) () from
/lib64/libgwenviewlib.so.5
#10 0x7fbbc5aa1973 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#11 0x7fbbcd37ac89 in Gwenview::ContextManager::currentUrlChanged(QUrl
const&) () from /lib64/libgwenviewlib.so.5
#12 0x7fbbcd2cf39c in Gwenview::ContextManager::setCurrentUrl(QUrl const&)
() from /lib64/libgwenviewlib.so.5
#13 0x7fbbcd2cf43d in
Gwenview::ContextManager::slotCurrentChanged(QModelIndex const&) () from
/lib64/libgwenviewlib.so.5
#14 0x7fbbc5aa1973 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#15 0x7fbbc5a4272e in QItemSelectionModel::currentChanged(QModelIndex
const&, QModelIndex const&) () from /lib64/libQt5Core.so.5
#16 0x7fbbc5a4922b in
QItemSelectionModelPrivate::_q_rowsAboutToBeRemoved(QModelIndex const&, int,
int) () from /lib64/libQt5Core.so.5
#17 0x7fbbc5a4b6d9 in QItemSelectionModel::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Core.so.5
#18 0x7fbbc5aa184e in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#19 0x7fbbc5a354a2 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex
const&, int, int, QAbstractItemModel::QPrivateSignal) () from
/lib64/libQt5Core.so.5
#20 0x7fbbc5a3c009 in QAbstractItemModel::beginRemoveRows(QModelIndex
const&, int, int) () from /lib64/libQt5Core.so.5
#21 0x7fbbc5a55c8d in
QSortFilterProxyModelPrivate::remove_proxy_interval(QVector&,
QVector&, int, int, QModelIndex const&, Qt::Orientation, bool) () from
/lib64/libQt5Core.so.5
#22 0x7fbbc5a5a6c7 in
QSortFilterProxyModelPrivate::remove_source_items(QVector&, QVector&,
QVector const&, QModelIndex const&, Qt::Orientation, bool) () from
/lib64/libQt5Core.so.5
#23 0x7fbbc5a5a8d1 in
QSortFilterProxyModelPrivate::source_items_about_to_be_removed(QModelIndex
const&, int, int, Qt::Orientation) () from /lib64/libQt5Core.so.5
#24 0x7fbbc5a5d3bd in QSortFilterProxyModel::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Core.so.5
#25 0x7fbbc5aa184e in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#2

[kdiff3] [Bug 419267] kdiff3 ftp:// files not working anymore

2020-03-29 Thread michael
https://bugs.kde.org/show_bug.cgi?id=419267

michael  changed:

   What|Removed |Added

   Version Fixed In||1.8.2

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

[rkward] [Bug 418591] Keep showing Transferring dialog while loading help files

2020-03-29 Thread Adley
https://bugs.kde.org/show_bug.cgi?id=418591

--- Comment #4 from Adley  ---
Hi,
It's back to normal after I installed the qtwebengine. the help file show
immediately and the latex greek letters and symbols display normally. 
I am not sure whether it's the solution (since many other updates during the
time).

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

[kdiff3] [Bug 419267] kdiff3 ftp:// files not working anymore

2020-03-29 Thread michael
https://bugs.kde.org/show_bug.cgi?id=419267

michael  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from michael  ---
Should be fixed in 1.8.2. Just released at
https://download.kde.org/stable/kdiff3/kdiff3-1.8.2.tar.xz.mirrorlist.

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

[ark] [Bug 419309] Ark cannot open multi-volume (splitted) zip

2020-03-29 Thread Alberto
https://bugs.kde.org/show_bug.cgi?id=419309

--- Comment #7 from Alberto  ---
(In reply to 2wxsy58236r3 from comment #6)
> How about disabling "Libzip" and "Unarchiver" plugins and try again?

Disabling libzip fix the problem...
Wtf. Is it not intended to happen, right no?

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

[okular] [Bug 419394] Provide an easy way to extract an image from a pdf

2020-03-29 Thread Jonathan
https://bugs.kde.org/show_bug.cgi?id=419394

--- Comment #1 from Jonathan  ---
Created attachment 127096
  --> https://bugs.kde.org/attachment.cgi?id=127096&action=edit
pdf containing an image

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

[okular] [Bug 419394] New: Provide an easy way to extract an image from a pdf

2020-03-29 Thread Jonathan
https://bugs.kde.org/show_bug.cgi?id=419394

Bug ID: 419394
   Summary: Provide an easy way to extract an image from a pdf
   Product: okular
   Version: 1.9.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: jonat...@demeyer.name
  Target Milestone: ---

AFAIK, there are no easy way to extract an image from a pdf. On evince, it is
quite obvious, you put the mouse over the image, right-click and you get a
"save image as...". There is a snapshot functionality in Okular but it is very
hard to have pixel precision with this tool.

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

[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM

2020-03-29 Thread mirh
https://bugs.kde.org/show_bug.cgi?id=416262

mirh  changed:

   What|Removed |Added

 CC||m...@protonmail.ch

--- Comment #11 from mirh  ---
(In reply to Jan Grulich from comment #9)
> The reason why we disabled them was to avoid hardcoding kernel version
> requirements. With all those enabled, Qt build was requiring kernel 3.17.y
> or something like that, why without those enabled it was kernel 2.x.

If I look at the sources, that was never committed though. 

I can only see bug 403042 which pertains flatpak specifically, but qt-base is
still untouched to this day. I just banged my head like two afternoons before
realizing sddm wasn't booting on 3.16 due to this.

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

[krita] [Bug 419277] krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command

2020-03-29 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=419277

Robert  changed:

   What|Removed |Added

 CC||rgbe...@gmail.com

--- Comment #5 from Robert  ---
I have this same issue. 
But thing is I had a successful build prior to trying to update krita a few
days ago. All using the same cmake version in gentoo cmake-3.16.5. 
I also downgraded the cmake version and have the same error.
The only thing that is different is that I have upgraded to
kde-frameworks/extra-cmake-modules-5.68.0 since the last time that I built
krita. But I do not know if that would affect the build.

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

[kde] [Bug 324488] assigning Ctrl+² shortcut

2020-03-29 Thread Titouan
https://bugs.kde.org/show_bug.cgi?id=324488

--- Comment #2 from Titouan  ---
Same here with other keys like "é" ; "è" ; "ç" ... And all others accentuated
letters.
KDE Neon 5.18.3

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

[kde] [Bug 324488] assigning Ctrl+² shortcut

2020-03-29 Thread Titouan
https://bugs.kde.org/show_bug.cgi?id=324488

Titouan  changed:

   What|Removed |Added

 CC||tachion.d3...@gmail.com

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

[kamoso] [Bug 419393] New: App will not start. Crashes as soon as started.

2020-03-29 Thread Petar Vujovic
https://bugs.kde.org/show_bug.cgi?id=419393

Bug ID: 419393
   Summary: App will not start. Crashes as soon as started.
   Product: kamoso
   Version: 19.12
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: petarvujovi...@gmail.com
  Target Milestone: ---

Created attachment 127095
  --> https://bugs.kde.org/attachment.cgi?id=127095&action=edit
The coredump generated

SUMMARY
App will not start. Crashes as soon as started.

STEPS TO REPRODUCE
1. Launch the app

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[klipper] [Bug 416510] Klipper applet closes itself when I click on a history item while the system tray popup is pinned open

2020-03-29 Thread popov895
https://bugs.kde.org/show_bug.cgi?id=416510

--- Comment #4 from popov895  ---
Submitted a patch: https://phabricator.kde.org/D28408

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

[okular] [Bug 418520] Find function misses occurrences of target string that wrap from one line to next line of document text.

2020-03-29 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=418520

--- Comment #11 from avlas  ---
(In reply to David Hurka from comment #10)
> > I assume there is no simple heuristic to workaround these
> > wrongly formatted pdfs, which highly affect features such
> > as searching, highlighting and selecting/extracting text.
> 
> It’s that TextEntity reordering thing.
> 
> @avlas Can you search for
> 
> will overshadowing would apply
> 
> (in the Thumbnails panel, not in the search bar), so we can see the geometry
> of the TextEntity objects? If the words are cleary separated between the
> columns, its a problem with Okular.
> 
> Okular breaks the document appart in single letters, and then reorders them
> based on their positions. It uses XY-Cut to separate colums, so it needs
> some horizontal space between them. Thats pretty useful for many PDFs which
> are arround in the web (like MeanWell datasheets...), but sometimes doesn’t
> work.
> 
> It looks like it’s a scanned paper. If it isn’t aligned perfectly vertical,
> the columns overlap, and XY-Cut fails.
> 
> https://phabricator.kde.org/source/okular/browse/master/core/textpage.cpp;
> 9694113a961cb5a5d6ef18ce0beeaa975a8c6db3$1890 if you are interested...
> 
> Of course it may still be a problem with the PDF. To check that, you can
> open it in e. g. Firefox and select some text.

Please see:

https://i.imgur.com/OV7BLRx.png

I checked it in Chromium and seems to work fine. Please see the previous
example when typing "circumstances":

https://i.imgur.com/8vn1Kpp.png

This is an official paper from a journal that I downloaded, but the paper is
from 1975, so not sure about the underlying technicalities of the pdf. Yet,
text management seems to work just fine (selecting, highlighting, etc). All
that does not consider line breaks and columns, which fail in okular but seem
to work just fine in chromium. So it might be the heuristic in okular compared
to that in chromium, perhaps.

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

[okular] [Bug 418520] Find function misses occurrences of target string that wrap from one line to next line of document text.

2020-03-29 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=418520

--- Comment #10 from David Hurka  ---
> I assume there is no simple heuristic to workaround these
> wrongly formatted pdfs, which highly affect features such
> as searching, highlighting and selecting/extracting text.

It’s that TextEntity reordering thing.

@avlas Can you search for

will overshadowing would apply

(in the Thumbnails panel, not in the search bar), so we can see the geometry of
the TextEntity objects? If the words are cleary separated between the columns,
its a problem with Okular.

Okular breaks the document appart in single letters, and then reorders them
based on their positions. It uses XY-Cut to separate colums, so it needs some
horizontal space between them. Thats pretty useful for many PDFs which are
arround in the web (like MeanWell datasheets...), but sometimes doesn’t work.

It looks like it’s a scanned paper. If it isn’t aligned perfectly vertical, the
columns overlap, and XY-Cut fails.

https://phabricator.kde.org/source/okular/browse/master/core/textpage.cpp;9694113a961cb5a5d6ef18ce0beeaa975a8c6db3$1890
if you are interested...

Of course it may still be a problem with the PDF. To check that, you can open
it in e. g. Firefox and select some text.

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

[systemsettings] [Bug 419390] the kernal sees my wifi adapter but i cant use it

2020-03-29 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419390

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from David Edmundson  ---
If nmtui doesn't see it, then it's not a KDE bug

(btw, you probably want to check rfkill)

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

[digikam] [Bug 403144] Disable Popup for "move here"

2020-03-29 Thread Thomas
https://bugs.kde.org/show_bug.cgi?id=403144

Thomas  changed:

   What|Removed |Added

Version|6.0.0   |7.0.0

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

[digikam] [Bug 403144] Disable Popup for "move here"

2020-03-29 Thread Thomas
https://bugs.kde.org/show_bug.cgi?id=403144

--- Comment #1 from Thomas  ---
Just wanted to file a similar wish. I would love this too. This popup keeps me
from using this great software. Please delete it. Or add some key
"SHIFT+drag/drop" or "ALT+drag/drop" for moving/copyign. And ESC to cancel
drag&drop.

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

[wacomtablet] [Bug 419392] New: Settings for touch zone are not saved

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419392

Bug ID: 419392
   Summary: Settings for touch zone are not saved
   Product: wacomtablet
   Version: 3.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jazzv...@gmail.com
  Reporter: jan.clausse...@web.de
  Target Milestone: ---

SUMMARY
Everytime I disconnect my external monitor, I the settings are being reset. It
would be really great if these settings could be saved, once they are set. 

STEPS TO REPRODUCE
1. Connect external monitor to 2-in-1 device
2. Set touch zone to laptop screen
3. Disconnect external monitor

OBSERVED RESULT

EXPECTED RESULT
The settings are reset and the touch input lands on the external monitor

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

[frameworks-kirigami] [Bug 419391] New: Passive notifications lack padding when using Plasma style

2020-03-29 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=419391

Bug ID: 419391
   Summary: Passive notifications lack padding when using Plasma
style
   Product: frameworks-kirigami
   Version: Master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: nicolas.fe...@gmx.de
  Target Milestone: Not decided

Created attachment 127094
  --> https://bugs.kde.org/attachment.cgi?id=127094&action=edit
Screenshot

When running apps with Plasma as QQC2 style passive notifications needs some
left/right padding. See screenshot

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

[systemsettings] [Bug 419390] New: the kernal sees my wifi adapter but i cant use it

2020-03-29 Thread Andrew A
https://bugs.kde.org/show_bug.cgi?id=419390

Bug ID: 419390
   Summary: the kernal sees my wifi adapter but i cant use it
   Product: systemsettings
   Version: 5.12.8
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: andrewapple...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. open terminal
2. type sudo lspci
3. then type nmtui to try to add it

OBSERVED RESULT
the terminal shows the hardware but the networkmanager tui doesnt see it.

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

[krusader] [Bug 419266] Copying file continues for 8 seconds after canceled

2020-03-29 Thread Davide Gianforte
https://bugs.kde.org/show_bug.cgi?id=419266

Davide Gianforte  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||dav...@gengisdave.org
 Resolution|--- |NOT A BUG

--- Comment #1 from Davide Gianforte  ---
In Linux, file copies (really, all files) are handled through a memory buffer.
When you start a copy, you should see a fast progress because it is filling the
buffer and when it is filled, the real write starts.

Using a system monitor (e.g. KSysGuard, htop) you can see a memory drop when
the copy ends, meaning that the buffer was freed. For the same reason, if you
copy a file over a network share you also see that the traffic starts a bit
after. Almost all systems, like KIO which is used by Krusader, show the
percentage of data sent to the buffer and it seems that the copy stucks at 100%
because the buffer size is yet to be written on disk.

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

[krusader] [Bug 419373] Synchronizer: Files that are linked lose their dates

2020-03-29 Thread Toni Asensi Esteve
https://bugs.kde.org/show_bug.cgi?id=419373

--- Comment #2 from Toni Asensi Esteve  ---
Created attachment 127093
  --> https://bugs.kde.org/attachment.cgi?id=127093&action=edit
Experimental code that keeps dates intact using `cp -a`

If it may be helpful when investigating more about the bug, if the attached
experimental code is used:
- The bug does not happen.
- Additionally, the dates of the symlinks that are copied are kept intact.
However, the experimental code is aimed to help investigating, not to be a
formal solution.

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

[frameworks-kcoreaddons] [Bug 419389] kcoreaddons-git 5.69.0.r961.gfcdf263 doesn't play well with fuse

2020-03-29 Thread deemon
https://bugs.kde.org/show_bug.cgi?id=419389

--- Comment #1 from deemon  ---
Also if you right click on desktop and choose "Configure Desktop..." while you
have added any wallpapers to your list from the same fuse mount, the entire
thing crashes.

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

[konsole] [Bug 419388] Wrong number of cores when run nproc or run multicore proccess

2020-03-29 Thread Gustavo Alvarez
https://bugs.kde.org/show_bug.cgi?id=419388

--- Comment #1 from Gustavo Alvarez  ---
Htop (in yakuake) when run multicore proccess on konsole
https://i.ibb.co/YdYLj0z/Screenshot-20200329-192231.png

same process run in yakuake
https://i.ibb.co/SXJ75C3/Screenshot-20200329-193114.png

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

[kruler] [Bug 415465] Opacity slider does not make window transparent when compositing is off

2020-03-29 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=415465

Alexander Potashev  changed:

   What|Removed |Added

Summary|Opacity slider does not |Opacity slider does not
   |make window transparent |make window transparent
   ||when compositing is off

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

[kruler] [Bug 415465] Opacity slider does not make window transparent

2020-03-29 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=415465

--- Comment #3 from Alexander Potashev  ---
If opacity setting cannot work without compositing, then I would suggest that
the Opacity menu should be disabled if compositing is disabled.

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

[frameworks-kcoreaddons] [Bug 419389] New: kcoreaddons-git 5.69.0.r961.gfcdf263 doesn't play well with fuse

2020-03-29 Thread deemon
https://bugs.kde.org/show_bug.cgi?id=419389

Bug ID: 419389
   Summary: kcoreaddons-git 5.69.0.r961.gfcdf263 doesn't play well
with fuse
   Product: frameworks-kcoreaddons
   Version: 5.69.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: pr...@ww.ee
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
could not edit anything with KATE in my pCloudDrive folder (fuse mount I
assume)

STEPS TO REPRODUCE
1. 
[deemon@Zen ~]$ kate pCloudDrive/manjaro/firewall.txt
ASSERT failure in Q_UNREACHABLE(): "Q_UNREACHABLE was reached", file
/build/src/kcoreaddons/src/lib/io/kdirwatch.cpp, line 956
Aborted (core dumped)

2. 
3. 

OBSERVED RESULT
kate didn't open and wasn't able to edit the file.

EXPECTED RESULT
kate did open and was able to edit the file.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE stable 2020-03-28 update.
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
downgrading koreaddons-git to 5.69.0.r960.g9348039 worked for me and KATE was
able to open the file.

[deemon@Zen ~]$ downgrade kcoreaddons-git

Downgrading from A.L.A. is disabled on the stable branch. To override this
behavior, set DOWNGRADE_FROM_ALA to 1 .
See https://wiki.manjaro.org/index.php?title=Using_Downgrade  for more details.

Available packages:

-  1)  kcoreaddons-git5.67.0.r935.g7113ba4  1  x86_64  (local)
-  2)  kcoreaddons-git5.67.0.r940.g1d6da11  1  x86_64  (local)
-  3)  kcoreaddons-git5.67.0.r943.gee3eaa8  1  x86_64  (local)
-  4)  kcoreaddons-git5.68.0.r949.ga4446e0  1  x86_64  (local)
-  5)  kcoreaddons-git5.68.0.r950.g55e855b  1  x86_64  (local)
-  6)  kcoreaddons-git5.69.0.r952.g8927a8c  1  x86_64  (local)
-  7)  kcoreaddons-git5.69.0.r960.g9348039  1  x86_64  (local)
+  8)  kcoreaddons-git5.69.0.r961.gfcdf263  1  x86_64  (local)

select a package by number: 7
loading packages...
warning: downgrading package kcoreaddons-git (5.69.0.r961.gfcdf263-1 =>
5.69.0.r960.g9348039-1)
resolving dependencies...
looking for conflicting packages...

Packages (1) kcoreaddons-git-5.69.0.r960.g9348039-1

Total Installed Size:  3.11 MiB
Net Upgrade Size:  0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring 
  
[#]
100%
(1/1) checking package integrity   
  
[#]
100%
(1/1) loading package files
  
[#]
100%
(1/1) checking for file conflicts  
  
[#]
100%
(1/1) checking available disk space
  
[#]
100%
:: Processing package changes...
(1/1) downgrading kcoreaddons-git  
  
[#]
100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the MIME type database...
add kcoreaddons-git to IgnorePkg? [y/n] y
[deemon@Zen ~]$ kate pCloudDrive/manjaro/firewall.txt
kf5.kservice.sycoca: Parse error in 
"/home/deemon/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" ,
line  1 , col  1 :  "unexpected end of file"
kf5.kservice.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :  "/usr/share/applications/qemu.desktop"
kf5.kio.core: We got some errors while running testparm "Error loading
services."
kf5.kio.core: We got some errors while running 'net usershare info'
kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n"

and kate opened the file fine and was able to edit it.

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

[konsole] [Bug 419388] New: Wrong number of cores when run nproc or run multicore proccess

2020-03-29 Thread Gustavo Alvarez
https://bugs.kde.org/show_bug.cgi?id=419388

Bug ID: 419388
   Summary: Wrong number of cores when run nproc or run multicore
proccess
   Product: konsole
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: sl1pk...@gmail.com
  Target Milestone: ---

Created attachment 127092
  --> https://bugs.kde.org/attachment.cgi?id=127092&action=edit
screensot yakuake, konsole and qterminal

when run konsole (standalone or throuth dolphin) nproc or do a run multicore
process, the number of cores is set wrongly

see attach

up: yakuake
left: Konsole
right: qterminal

EXPECTED RESULT


show the real number of cores/threads (40 in my case)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14/5.15

ADDITIONAL INFORMATION

i have set isolcpus=10,11,22,23,34,35,46,47 nohz_full=10,11,22,23,34,35,46,47
rcu_nocbs=10,11,22,23,34,35,46,47 in boot. I need these cores for
Virtualization (libvirt+cpupinned)

lscpu:
└───╼  lscpu
Arquitectura:x86_64
modo(s) de operación de las CPUs:32-bit, 64-bit
Orden de los bytes:  Little Endian
Tamaños de las direcciones:  46 bits physical, 48 bits virtual
CPU(s):  48
Lista de la(s) CPU(s) en línea:  0-47
Hilo(s) de procesamiento por núcleo: 2
Núcleo(s) por «socket»:  12
«Socket(s)»  2
Modo(s) NUMA:2
ID de fabricante:GenuineIntel
Familia de CPU:  6
Modelo:  79
Nombre del modelo:   Genuine Intel(R) CPU  @ 2.20GHz
(Engineering Sample)
Revisión:0
CPU MHz: 2195.060
CPU MHz máx.:2200,
CPU MHz mín.:1200,
BogoMIPS:4391.16
Virtualización:  VT-x
Caché L1d:   768 KiB
Caché L1i:   768 KiB
Caché L2:6 MiB
Caché L3:60 MiB
CPU(s) del nodo NUMA 0:  0-11,24-35
CPU(s) del nodo NUMA 1:  12-23,36-47
Vulnerability:  secret ;)
Indicadores: fpu vme de pse tsc msr pae mce cx8 apic
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 ds_cpl vmx smx est
tm2
  ssse3 sdbg fma cx16 xtpr pdcm pcid dca
sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm
3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2
smep bmi2 erms 
 invpcid rtm cqm rdt_a rdseed adx smap
intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat
pln pts


working as spected since ages. seems is a regression. i'm not sure when start
failed

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

[kmenuedit] [Bug 419386] KDE Menu Editor crashed after saving the menu using 'Restore to System Menu'

2020-03-29 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419386

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|NEEDSINFO

--- Comment #2 from David Edmundson  ---
What do you mean by "in an xwayland" session?

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

[kmenuedit] [Bug 419386] KDE Menu Editor crashed after saving the menu using 'Restore to System Menu'

2020-03-29 Thread Markus Schmits
https://bugs.kde.org/show_bug.cgi?id=419386

--- Comment #1 from Markus Schmits  ---
If it's of interest: I was using KDE in a Xwayland session. The crash happened
another time before. Afterwards, I couldn't reproduce it on a X11 session.

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

[kdeplasma-addons] [Bug 386957] Spinbox suffixes need plurals

2020-03-29 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=386957

--- Comment #2 from Alexander Potashev  ---
Fixed in
https://commits.kde.org/kdeplasma-addons/f2647deeeac7cc91dbc719e1456a978135fa39f7

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

[frameworks-kirigami] [Bug 415684] Drawers are often much too wide, but sometimes too narrow

2020-03-29 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=415684

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

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

[kwin] [Bug 419387] New: Frame drops when the second monitor has 30Hz refresh rate

2020-03-29 Thread Guo Yunhe
https://bugs.kde.org/show_bug.cgi?id=419387

Bug ID: 419387
   Summary: Frame drops when the second monitor has 30Hz refresh
rate
   Product: kwin
   Version: 5.18.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: i...@guoyunhe.me
  Target Milestone: ---

SUMMARY
When you have two monitors with different refresh rates, the one higher refresh
rate drop frames (noticeably).

STEPS TO REPRODUCE
1. Connect to two 1080p monitors, we call them A and B
2. In KDE Settings, set refresh rates of both to 60Hz
3. Watch this video in monitor A https://www.youtube.com/watch?v=Cyxixzi2dgQ
4. In KDE Settings, set refresh rate of A to 60Hz and B to 30Hz
5. Watch the same video in monitor A
6. Shift+Alt+F12 to disable KWin composition
7. Watch the same video in monitor A
OBSERVED RESULT
When B is 60Hz, monitor A doesn't drop frames.
When B is 30Hz, monitor A drop frames noticeably. 
When B is 30Hz but KWin composition is off, monitor A doesn't drop frames.

EXPECTED RESULT
Monitor A shouldn't drop frames when monitor B has a different refresh rate.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20200326
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.5.11-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.1 GiB

ADDITIONAL INFORMATION
I think this is not deal to GPU performance limitation, because when you reduce
refresh rate of monitor B, the total computing load is smaller and GPU should
render faster.

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

[kmenuedit] [Bug 419386] New: KDE Menu Editor crashed after saving the menu using 'Restore to System Menu'

2020-03-29 Thread Markus Schmits
https://bugs.kde.org/show_bug.cgi?id=419386

Bug ID: 419386
   Summary: KDE Menu Editor crashed after saving the menu using
'Restore to System Menu'
   Product: kmenuedit
   Version: 5.18.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: marsh.exhe...@gmail.com
  Target Milestone: ---

Application: kmenuedit (5.18.3)
 (Compiled from sources)
Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.5.10 x86_64
Windowing system: X11
Distribution: Exherbo Linux

-- Information about the crash:
- What I was doing when the application crashed:
First, I executed 'Restore to System Menu'. Reason was, to recreate the menu to
default settings and include all known applications. Afterwards, by pressing
the 'Save' button, the application crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault
Using host libthread_db library
"/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2dfcac1440 (LWP 4132))]

Thread 8 (Thread 0x7f2df1002700 (LWP 4139)):
#0  0x7f2dffc67bc5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f2df348999b in cnd_wait (mtx=0x55b33de078a8, cond=0x55b33de078d0) at
../mesa-20.0.2/include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x55b33dd0b7d0) at
../mesa-20.0.2/src/util/u_queue.c:275
#3  0x7f2df3489557 in impl_thrd_routine (p=) at
../mesa-20.0.2/include/c11/threads_posix.h:87
#4  0x7f2dffc613f7 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#5  0x7f2e02196503 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 7 (Thread 0x7f2df1803700 (LWP 4138)):
#0  0x7f2dffc67bc5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f2df348999b in cnd_wait (mtx=0x55b33de078a8, cond=0x55b33de078d0) at
../mesa-20.0.2/include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x55b33ddd45e0) at
../mesa-20.0.2/src/util/u_queue.c:275
#3  0x7f2df3489557 in impl_thrd_routine (p=) at
../mesa-20.0.2/include/c11/threads_posix.h:87
#4  0x7f2dffc613f7 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#5  0x7f2e02196503 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 6 (Thread 0x7f2df2004700 (LWP 4137)):
#0  0x7f2dffc67bc5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f2df348999b in cnd_wait (mtx=0x55b33de078a8, cond=0x55b33de078d0) at
../mesa-20.0.2/include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x55b33dc560c0) at
../mesa-20.0.2/src/util/u_queue.c:275
#3  0x7f2df3489557 in impl_thrd_routine (p=) at
../mesa-20.0.2/include/c11/threads_posix.h:87
#4  0x7f2dffc613f7 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#5  0x7f2e02196503 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 5 (Thread 0x7f2df2805700 (LWP 4136)):
#0  0x7f2dffc67bc5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f2df348999b in cnd_wait (mtx=0x55b33de078a8, cond=0x55b33de078d0) at
../mesa-20.0.2/include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x55b33dea51c0) at
../mesa-20.0.2/src/util/u_queue.c:275
#3  0x7f2df3489557 in impl_thrd_routine (p=) at
../mesa-20.0.2/include/c11/threads_posix.h:87
#4  0x7f2dffc613f7 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#5  0x7f2e02196503 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 4 (Thread 0x7f2df3006700 (LWP 4135)):
#0  0x7f2dffc67bc5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f2df348999b in cnd_wait (mtx=0x55b33e144870, cond=0x55b33e144898) at
../mesa-20.0.2/include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x55b33dbbd5a0) at
../mesa-20.0.2/src/util/u_queue.c:275
#3  0x7f2df3489557 in impl_thrd_routine (p=) at
../mesa-20.0.2/include/c11/threads_posix.h:87
#4  0x7f2dffc613f7 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#5  0x7f2e02196503 in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 3 (Thread 0x7f2dfa155700 (LWP 4134)):
#0  0x7f2e02187a6c in read () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6
#1  0x7f2dff0c9d57 in g_wakeup_acknowledge (wakeup=0x55b33dafb5b0) at
../glib-2.64.1/glib/gwakeup.c:210
#2  0x7f2dff084d06 in g_main_context_check
(context=context@entry=0x7f2dec000c20, max_priority=2147483647,
fds=fds@entry=0x7f2dec004e60, n_fds=n_fds@entry=1) at
../glib-2.64.1/glib/gmain.c:3825
#3 

[plasmashell] [Bug 419310] Kickoff (also maybe for alternative menus too): Security concerns

2020-03-29 Thread Gabriel Fernandes
https://bugs.kde.org/show_bug.cgi?id=419310

--- Comment #12 from Gabriel Fernandes  ---
>But that requires explicit user activity to get it in locations first, right?

Yes, the user has to enter the location. Much less likely to happen.
I just wanted to point out, even though it says open, in fact it executes the
file: https://imgur.com/a/NHjKpuS

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

[dolphin] [Bug 384974] Dolphin crashes after failing to copy files to Android phone over mtp

2020-03-29 Thread David Tonhofer
https://bugs.kde.org/show_bug.cgi?id=384974

--- Comment #15 from David Tonhofer  ---
I don't know why there should be two implementation paths (different
libraries?), but as a replacement solution, downloading pics from an attached
phone via gwenview works A-OK.

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

[systemsettings] [Bug 419374] Scaling for GTK doesn't work

2020-03-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419374

--- Comment #2 from jan.clausse...@web.de ---
No screenshot necessary. This is caused by GTK3, since it doesn't support
non-integer scaling. When I set the scaling to 200%, GTK scales as well. But
then the performance in Xournal++ gets really bad. One the other hand palm
rejection works again.

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

[kwin] [Bug 419385] New: Windows snapped to side edges do not show the border of the side snapped

2020-03-29 Thread Michael D
https://bugs.kde.org/show_bug.cgi?id=419385

Bug ID: 419385
   Summary: Windows snapped to side edges do not show the border
of the side snapped
   Product: kwin
   Version: 5.18.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nortex...@gmail.com
  Target Milestone: ---

I've set the breeze decoration option "allow resizing of maximized windows from
window edges" which allows the border to show when maximizing windows. It also
seems to show top and bottom borders when snapping to sides. However, the
border of the side snapped does not show--apparently the snapping does not take
into account the window's side border. I'm guessing it should, especially when
the option to allow resizing of maximized windows is checked.

On my set-up this is very obvious since my window borders are a different color
from the window background.

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

[kwin] [Bug 404669] Show FPS effect does not work on dual monitors

2020-03-29 Thread Guo Yunhe
https://bugs.kde.org/show_bug.cgi?id=404669

Guo Yunhe  changed:

   What|Removed |Added

 CC||i...@guoyunhe.me

--- Comment #8 from Guo Yunhe  ---
When the two monitors have different refresh rate: one in 60Hz, the other in
30Hz, shouldn't two FPS widgets be shown?

* Left 3840x2160@30Hz
* Right 1920x1080@60Hz
* Top alignment

In my case, the FPS widget always show FPS of the lower refresh rate screen,
but the widget is shown in the higher refresh rate screen, which is confusing.

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

[okular] [Bug 419359] Embedded video in PDF has wrong size and position

2020-03-29 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=419359

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #8 from Luigi Toscano  ---
It is not much relevant here, but for the record, I exported the ODT document
to PDF with LibreOffice 6.4.2 and the video is now placed correctly.

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

[lattedock] [Bug 419384] New: Make the tracking of different feature of applications (geometry, title...) optional

2020-03-29 Thread Pierpaolo Valerio
https://bugs.kde.org/show_bug.cgi?id=419384

Bug ID: 419384
   Summary: Make the tracking of different feature of applications
(geometry, title...) optional
   Product: lattedock
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: pierpaolo.vale...@gmail.com
  Target Milestone: ---

This is a bug report in response of the discussion here:
https://www.reddit.com/r/kde/comments/fpc7rt/latte_bug_fix_release_0910/flrb31d/

Right now the idea is that the window tracking feature of latte ignores plasma
popups, but not windows like krunner or yakuake. This is the intended behaviour
for deciding whether the panel should be transparent or not, if the
transparency option is set, as those are windows positioned directly next to a
top panel.

The behaviour, however, doesn't match the appmenu applet, which is set to
ignore all plasma popups. So if the window-title, window-buttons and
window-appmenu applet are present, opening krunner changes the behaviour of the
buttons and the title applets, but the appmenu keeps referring to the previous
app.

The proposed suggestion is to implement new properties such as skipTaskBar,
skipSwitcher, skipPager for the LastActiveWindow class, so that the applets can
ignore some apps if needed.

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

[releaseme] [Bug 419383] New: License headers do not match COPYING file

2020-03-29 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=419383

Bug ID: 419383
   Summary: License headers do not match COPYING file
   Product: releaseme
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: aspotas...@gmail.com
  Target Milestone: ---

SUMMARY
License headers do not match COPYING file:
 - COPYING contains GNU GPL v3
 - Some source files contain license header for GPL2/3/KDEeV-approved (e.g.
lib/releaseme/projects_api.rb)
 - Some source files contain one-line header mentioning "GNU GPL v2 or later"

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
1. Add more COPYING.* files to cover all licenses that may apply.
2. Include full license headers in all source files where applicable. Header
templates are included as part of GNU licenses.

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

[dolphin] [Bug 418475] Crash when hiding several offline NFS mount points

2020-03-29 Thread Alan Mimms
https://bugs.kde.org/show_bug.cgi?id=418475

--- Comment #3 from Alan Mimms  ---
I will try to reproduce this today.

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

[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)

2020-03-29 Thread João Vidal da Silva
https://bugs.kde.org/show_bug.cgi?id=387663

João Vidal da Silva  changed:

   What|Removed |Added

 CC||joao.vidal.si...@gmail.com

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

[okular] [Bug 419359] Embedded video in PDF has wrong size and position

2020-03-29 Thread Elvis Stansvik
https://bugs.kde.org/show_bug.cgi?id=419359

--- Comment #7 from Elvis Stansvik  ---
Reported against LibreOffice here instead:
https://bugs.documentfoundation.org/show_bug.cgi?id=131673

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

[okular] [Bug 419359] Embedded video in PDF has wrong size and position

2020-03-29 Thread Elvis Stansvik
https://bugs.kde.org/show_bug.cgi?id=419359

--- Comment #6 from Elvis Stansvik  ---
Thanks for checking! I'll file an issue with them.

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

[plasmashell] [Bug 419310] Kickoff (also maybe for alternative menus too): Security concerns

2020-03-29 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419310

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-workspace/97bf7d777e56a
   ||451eb91731d9209fb1d55689957
 Status|ASSIGNED|RESOLVED

--- Comment #11 from David Edmundson  ---
Git commit 97bf7d777e56a451eb91731d9209fb1d55689957 by David Edmundson.
Committed on 29/03/2020 at 15:13.
Pushed by davidedmundson into branch 'Plasma/5.18'.

[runners/recentdocuments] disable executables or .desktop files

Summary:
It's possible to have a .desktop file in your recent documents list as
you were editing it. Either as a .desktop file or masquerading as
something else.

By default we would process the .desktop file like a .desktop file.

You do get a prompt if the .desktop file is not executable like in
dolphin.

Given we know from context that we're showing recent "Documents" we may
as well turn that behaviour off without risk of ill effects.

Test Plan:
Created .desktop file (masquerading as something else)
Had it in my recent documents after opening in another format
Loaded the file from krunner. It now opened in my text editor instead of
running
the Exec line

Reviewers: #plasma, ngraham

Reviewed By: ngraham

Subscribers: ngraham, plasma-devel

Tags: #plasma

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

M  +2-1runners/recentdocuments/recentdocuments.cpp

https://commits.kde.org/plasma-workspace/97bf7d777e56a451eb91731d9209fb1d55689957

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

[plasmashell] [Bug 419310] Kickoff (also maybe for alternative menus too): Security concerns

2020-03-29 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419310

--- Comment #10 from David Edmundson  ---
>But the "Locations" runner does execute the .desktop file

But that requires explicit user activity to get it in locations first, right?

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

[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.

2020-03-29 Thread Wayne
https://bugs.kde.org/show_bug.cgi?id=419379

--- Comment #7 from Wayne  ---
It does seem odd.

Get Outlook for Android


From: Boudewijn Rempt 
Sent: Sunday, March 29, 2020 3:56:55 PM
To: wolf-eye...@hotmail.com 
Subject: [krita] [Bug 419379] Issues with screen dissapering when i load a new
canvas.

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

--- Comment #6 from Boudewijn Rempt  ---
That's curious, because there were no changes to the opengl canvas that I know
of between 4.2.8 and 4.2.9...

--
You are receiving this mail because:
You reported the bug.

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

  1   2   3   >