[neon] [Bug 406396] The Kate snap does not open files

[Ivo C]

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

Ivo C  changed:

   What|Removed |Added

 CC||waz...@protonmail.com

--- Comment #2 from Ivo C  ---
I am also experiencing this bug on Ubuntu 16.04. Neither the open nor save file
dialog box show up. Channel stable 19.04.0

$ snap version
snap2.38
snapd   2.38
series  16
ubuntu  16.04
kernel  4.15.0-47-generic

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

[neon] [Bug 406727] New: Kate snap fails to run due to missing dependencies

[Ivo C]

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

Bug ID: 406727
   Summary: Kate snap fails to run due to missing dependencies
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Snaps
  Assignee: neon-b...@kde.org
  Reporter: waz...@protonmail.com
CC: neon-b...@kde.org
  Target Milestone: ---

SUMMARY
Kate snap fails to start unless also the snap kde-frameworks-5 is manually
installed in addition. This was tested on a brand new and fully updated
installation of Ubuntu 16.04.

STEPS TO REPRODUCE
$ snap version
snap2.38
snapd   2.38
series  16
ubuntu  16.04
kernel  4.15.0-47-generic

$ snap list
No snaps are installed yet. Try 'snap install hello-world'.

$ sudo snap install kate
kate 19.04.0 from KDE✓ installed

$ snap list
Name Version   Rev  Tracking  Publisher   Notes
core18   20190409  941  stablecanonical✓  base
kate 19.04.0   26   stablekde✓-
kde-frameworks-5-core18  5.56.029   stablekde✓-

$ snap run kate
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it
was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen,
vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted (core dumped)

$ sudo snap install kde-frameworks-5
Setup snap "core" (6673) security profiles 
\2019-04-21T10:28:17+02:00 INFO Waiting for restart...
kde-frameworks-5 5.47.0 from KDE✓ installed

$ sudo snap list
Name Version   Rev   Tracking  Publisher   Notes
core 16-2.38   6673  stablecanonical✓  core
core18   20190409  941   stablecanonical✓  base
kate 19.04.0   26stablekde✓-
kde-frameworks-5 5.47.027stablekde✓-
kde-frameworks-5-core18  5.56.029stablekde✓-

After that, Kate snap runs fine. (except for bug 406396)

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

[systemsettings] [Bug 393061] Focus not transferred properly to child windows in sidebar view

[Ivo C]

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

--- Comment #3 from Ivo C  ---
Created attachment 114355
  --> https://bugs.kde.org/attachment.cgi?id=114355=edit
video demonstration

Unfortunately, I am unable to test with the master branch, but my system has
since been updated to newer versions and it still occurs at random very often
but not always. I don't use any kind of special focus prevention rules: the
policy is "click to focus", low stealing prevention and click raises active
window is enabled.

I have added an attachment video to demonstrate this odd issue if it wasn't
clear what is happening on my end. Here, it doesn't happen the first time, but
does the second and I try to show the effects. When I click on the child
window, it starts behaving normally.

Plasma: 5.13.3
KDE frameworks: 5.48.0
Qt: 5.10.1

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

[kwin] [Bug 393139] Jarring restoration of minimized window with activated "show selected window" in task switcher settings

[Ivo C]

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

--- Comment #6 from Ivo C <waz...@protonmail.com> ---
Created attachment 112197
  --> https://bugs.kde.org/attachment.cgi?id=112197=edit
KWin supportInformation

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

[systemsettings] [Bug 388574] Application Launcher keyboard shortcuts can launch only certain applications.

[Ivo C]

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

--- Comment #4 from Ivo C <waz...@protonmail.com> ---
When you first add an application with '+' and set a global shortcut for
launching it like shown in comment 2, it doesn't work initially. This applies
to Dolphin, for example.

However, it WILL work on the next log in. It seems like this bug only affects
newly added entries before there has been a log out. Modifying already existing
entries seems to work fine and they take effect immediately.

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

[systemsettings] [Bug 388574] Application Launcher keyboard shortcuts can launch only certain applications.

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||waz...@protonmail.com

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

[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||waz...@protonmail.com

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

[systemsettings] [Bug 391277] Application Global shortcuts broken

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||waz...@protonmail.com

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

[kwin] [Bug 393139] Jarring restoration of minimized window with activated "show selected window" in task switcher settings

[Ivo C]

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

--- Comment #4 from Ivo C <waz...@protonmail.com> ---
https://paste.kde.org/pwfgaf5ab

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

[systemsettings] [Bug 393403] New: Application launcher global shortcuts get assigned to random neighbours

[Ivo C]

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

Bug ID: 393403
   Summary: Application launcher global shortcuts get assigned to
random neighbours
   Product: systemsettings
   Version: 5.12.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: accessibility, usability
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: k...@michael-jansen.biz
  Reporter: waz...@protonmail.com
  Target Milestone: ---

Application launcher global shortcuts get assigned to random neighbours.

Steps to reproduce:
0. Assuming no launcher shortcuts (like a clean install of Tumbleweed) but also
happens with multiple launcher shortcuts already present
1. Add Dolphin to the list, add Konsole
2. Assign e.g. ctrl+alt+e for launching Dolphin
3. Select apply
4. The same shortcut is assigned to Konsole somehow.

Always reproducible with and without a VM and with multiple distibutions. There
is also the fact that, even after manually resolving the conflict, global
shortcuts doesn't function at all for launching Dolphin. See Bug 388574

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

[plasmashell] [Bug 393401] New: Kickoff favorites should update with "Show applications by name"

[Ivo C]

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

Bug ID: 393401
   Summary: Kickoff favorites should update with "Show
applications by name"
   Product: plasmashell
   Version: 5.12.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: waz...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

The favourites in Kickoff should switch their title and sub-title (e.g. Dolphin
- File Manager) accordingly whenever the option "Show applications by name" is
changed.

Currently, they remain unchanged, which can lead to a mix of both, and removing
and re-adding a favourite is necessary to update it.

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

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

[Ivo C]

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

--- Comment #10 from Ivo C <waz...@protonmail.com> ---
Created attachment 112151
  --> https://bugs.kde.org/attachment.cgi?id=112151=edit
screenshot

(In reply to Ben Cooksley from comment #9)
> Can you please post a screenshot and the link to the page which offers that
> so I can investigate?

> users that don't have the right to change the severity shouldn't have the
> ability to attempt to set it when filing a bug through the "Enter Bug" form
> on website.

URL: https://bugs.kde.org/enter_bug.cgi?product=elisa

Here is a screenshot of my new bug page for all available products.

This is a separate issue but I decided to comment here since it's related,
however I could file a separate bug report for this.

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

[kwin] [Bug 393139] Jarring restoration of minimized window with activated "show selected window" in task switcher settings

[Ivo C]

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

--- Comment #2 from Ivo C <waz...@protonmail.com> ---
Task Manager's option to "Highlight windows" also results in the same
behaviour.

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

[plasmashell] [Bug 393041] Crash when applying desktop layout type in Wallpaper configuration

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC|waz...@protonmail.com   |

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

[plasmashell] [Bug 393048] Log out dialogue - bad visibility of selected option

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC|waz...@protonmail.com   |

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

[systemsettings] [Bug 392987] Crash on reopening after task switcher demo preview got stuck on screen

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC|waz...@protonmail.com   |

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

[partitionmanager] [Bug 393275] Crash after dismissing "Scanning devices..." and closing KPM

[Ivo C]

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

--- Comment #7 from Ivo C <waz...@protonmail.com> ---
I wasn't sure if this is an actual crash in comment #1 with version 3.2.1
because of "signal: Aborted" and because I observed something strange:

1. Perform steps from original report
2. One of the KPM processes crashes/aborts
3. Close drkonqi and that process resumes
4. "No administative privileges" dialogue appears
5. Select "run"
6. KPM opens again

However, the fix should take care of this scenario. Still, I thought it's worth
mentioning to you. Is this the desired behaviour when one process crashes?

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

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||waz...@protonmail.com

--- Comment #7 from Ivo C <waz...@protonmail.com> ---
In that case, users that don't have the right to change the severity shouldn't
have the ability to attempt to set it when filing a bug through the "Enter Bug"
form on website. I was very confused about why someone had to fix my severity
even though I had (attempted to) set it correctly.

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

[Powerdevil] [Bug 393273] Add option for different timeout for switching off screen while session is locked

[Ivo C]

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

--- Comment #2 from Ivo C <waz...@protonmail.com> ---
XScreenSaver implements this by setting a different power configuration profile
while it's running, so it might be possible to implement this without modifying
powerdevil.

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

[partitionmanager] [Bug 393275] Crash after dismissing "Scanning devices..." and closing KPM

[Ivo C]

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

--- Comment #1 from Ivo C <waz...@protonmail.com> ---
Actually, could this be drkonqi activating erroneously?

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

[partitionmanager] [Bug 393275] New: Crash after dismissing "Scanning devices..." and closing KPM

[Ivo C]

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

Bug ID: 393275
   Summary: Crash after dismissing "Scanning devices..." and
closing KPM
   Product: partitionmanager
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: waz...@protonmail.com
  Target Milestone: ---

Application: partitionmanager (3.2.1)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.17-300.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Steps to reproduce:
1. Run KPM
2. Enter root password
3. Close "Scanning devices..." with 'X'
4. Immediately close KPM while the cursor is still busy
5. KPM crashes

Additional info:
This also occurs after an operation was completed. After the report dialogue
window is dismissed, the user may want to quit immediately and does above steps
3 and 4. It doesn't seem to happen after the spinner cursor is gone or when run
without root privileges.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feedf798e00 (LWP 7010))]

Thread 3 (Thread 0x7feea375f700 (LWP 8748)):
#0  0x7feed9bead66 in ppoll () from /lib64/libc.so.6
#1  0x7feedaa45ec5 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/bits/poll2.h:77
#2  qt_ppoll (timeout_ts=0x0, nfds=4, fds=0x7feea375e6a0) at
kernel/qcore_unix.cpp:81
#3  qt_safe_poll (fds=0x7feea375e6a0, nfds=4, timeout_ts=) at
kernel/qcore_unix.cpp:102
#4  0x7feeda98de02 in qt_poll_msecs (timeout=,
nfds=, fds=0x7feea375e6a0) at
../../include/QtCore/5.9.4/QtCore/private/../../../../../src/corelib/kernel/qcore_unix_p.h:353
#5  (anonymous namespace)::QProcessPoller::poll
(this=this@entry=0x7feea375e6a0, timeout=) at
io/qprocess_unix.cpp:188
#6  0x7feeda98f327 in QProcessPrivate::waitForFinished
(this=this@entry=0x7fee940bce70, msecs=msecs@entry=-1) at
io/qprocess_unix.cpp:871
#7  0x7feeda9858cb in QProcess::waitForFinished
(this=this@entry=0x7feea375e7f0, msecs=msecs@entry=-1) at io/qprocess.cpp:1924
#8  0x7feedf12aa3e in ExternalCommand::waitFor
(this=this@entry=0x7feea375e7f0, timeout=timeout@entry=-1) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/util/externalcommand.cpp:98
#9  0x7feedf12ac3a in ExternalCommand::run (this=this@entry=0x7feea375e7f0,
timeout=timeout@entry=-1) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/util/externalcommand.cpp:114
#10 0x7feedf0e190a in FS::ntfs::readUsedCapacity
(this=this@entry=0x7fee94001600, deviceNode=...) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/fs/ntfs.cpp:111
#11 0x7feebb4ffb92 in readSectorsUsed (mountPoint=..., p=..., d=...,
pedDisk=0x7fee940b1560) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/plugins/libparted/libpartedbackend.cpp:206
#12 LibPartedBackend::scanDevicePartitions (this=this@entry=0x565055600150,
d=..., pedDisk=pedDisk@entry=0x7fee940b1560) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/plugins/libparted/libpartedbackend.cpp:358
#13 0x7feebb50028a in LibPartedBackend::scanDevice (this=0x565055600150,
deviceNode=...) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/plugins/libparted/libpartedbackend.cpp:407
#14 0x7feebb500db5 in LibPartedBackend::scanDevices (this=0x565055600150,
excludeReadOnly=false) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/plugins/libparted/libpartedbackend.cpp:454
#15 0x7feedf0f09d5 in DeviceScanner::scan (this=0x56505560a830) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/core/devicescanner.cpp:67
#16 0x7feeda84cde2 in QThreadPrivate::start (arg=0x56505560a830) at
thread/qthread_unix.cpp:368
#17 0x7feed6c1f50b in start_thread () from /lib64/libpthread.so.0
#18 0x7feed9bf516f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7feebbf0f700 (LWP 7012)):
#0  0x7feed9beac6b in poll () from /lib64/libc.so.6
#1  0x7feed2acae99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7feed2acafac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7feedaa49c4b in QEventDispatcherGlib::processEvents
(this=0x7feeb4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7feeda9f796a in QEventLoop::exec (this=this@entry=0x7feebbf0ec20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7feeda8488ca in QThread::exec (this=this@entry=0x7feedc5b1060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:515
#6  0x7feedc33d449 in QDBusConnectionManager::run (this=0x7feedc5b1060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7feeda84cde2 in 

[kscreenlocker] [Bug 393273] New: Add option for different timeout for switching off screen while session is locked

[Ivo C]

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

Bug ID: 393273
   Summary: Add option for different timeout for switching off
screen while session is locked
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: waz...@protonmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

It would be very useful to have an option for a different timeout for switching
off the screen while the session is locked. This option could also be active by
default with a value of a few minutes. I'm not sure if this would belong in the
Screen Locker or Energy Saving KCM.

Some other screen lockers and other operating systems have this functionality.
For example, while I may want a 15 minute screen timeout while the computer is
not locked, I would like to have a shorter timeout of 1 minute while
kscreenlocker is active.

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

[partitionmanager] [Bug 393236] KDE Partition Manager crash when observing or scrolling detailed report

[Ivo C]

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

--- Comment #2 from Ivo C <waz...@protonmail.com> ---
It was a GPT disk and I was resizing a Windows NTFS partition (primary type but
a data partition, not Windows system, flags: msft-data). It was positioned last
on the disk and I shrunk it from 490 to 440 GB, to free up space at the end of
the disk.

As the operation first started, I clicked opened the collapsible item in the
top part first and then clicked "Details >>". I scrolled a few times at the
start of the operation. Then I didn't touch it and let it finish. I came back
after it had finished, saw "successfully completed" and scrolled to the top to
review the output and as I was scrolling/looking at it, it crashed. I can't say
with certainty whether it's related to scrolling or if it happened exactly when
scrolling, because that's not something I paid attention to.

I think that's all the detail I can provide. I can try to play around more with
it when I have the time and see if I can reproduce it. But I don't know how
effective it will be because I can't really do resizes of this magnitude (and
under the same circumstances unless I reformat it with Windows) and this is my
production system. I hope these details can help you and I'm willing to do what
I can to help narrow it down if possible.

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

[partitionmanager] [Bug 393236] New: KDE Partition Manager crash when observing or scrolling detailed report

[Ivo C]

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

Bug ID: 393236
   Summary: KDE Partition Manager crash when observing or
scrolling detailed report
   Product: partitionmanager
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: waz...@protonmail.com
  Target Milestone: ---

Application: partitionmanager (3.2.1)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.16-300.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I resized a partition and the operation succeeded. I was viewing the detailed
command line report in the window and scrolling through it when Partition
Manager crashed. No attempt to reproduce it because I don't need any other
partitioning operations.

- Unusual behavior I noticed:
This is done from a Fedora 27 KDE live media (respin 2018-04-15). The PC has an
NVIDIA GPU and is currently using the nouveau driver which causes random and
fairly minor graphical artifacts in all applications (especially text boxes and
buttons) but this hasn't impacted the stability of any other applications, so
is unlikely to be related to the crash.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f22210d2e00 (LWP 1982))]

Thread 3 (Thread 0x7f21ebd2f700 (LWP 2060)):
#0  0x7f221855582d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f21f1218f4b in util_queue_thread_func () from
/usr/lib64/dri/nouveau_dri.so
#2  0x7f21f1218e67 in impl_thrd_routine () from
/usr/lib64/dri/nouveau_dri.so
#3  0x7f221854f50b in start_thread () from /lib64/libpthread.so.0
#4  0x7f221b52516f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f21fd897700 (LWP 1984)):
#0  0x7f22143fa4e8 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#1  0x7f22143fadcb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f22143fafac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f221c379c4b in QEventDispatcherGlib::processEvents
(this=0x7f21f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f221c32796a in QEventLoop::exec (this=this@entry=0x7f21fd896c20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f221c1788ca in QThread::exec (this=this@entry=0x7f221dee1060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:515
#6  0x7f221dc6d449 in QDBusConnectionManager::run (this=0x7f221dee1060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7f221c17cde2 in QThreadPrivate::start (arg=0x7f221dee1060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7f221854f50b in start_thread () from /lib64/libpthread.so.0
#9  0x7f221b52516f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f22210d2e00 (LWP 1982)):
[KCrash Handler]
#4  0x7f2220a2e34f in Partition::sectorsUsed
(this=this@entry=0x7f22e2d0) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/core/partition.cpp:185
#5  0x7f2220a6255c in Partition::used (this=0x7f22e2d0) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/core/partition.h:175
#6  PartWidget::paintEvent (this=0x560abe7c67c0) at
/usr/src/debug/kpmcore-3.2.1-1.fc27.x86_64/src/gui/partwidget.cpp:96
#7  0x7f221cfd82a8 in QWidget::event (this=0x560abe7c67c0,
event=0x7ffe828513f0) at kernel/qwidget.cpp:9279
#8  0x7f221cf9992c in QApplicationPrivate::notify_helper (this=, receiver=0x560abe7c67c0, e=0x7ffe828513f0) at
kernel/qapplication.cpp:3722
#9  0x7f221cfa1174 in QApplication::notify (this=0x7ffe828533d0,
receiver=0x560abe7c67c0, e=0x7ffe828513f0) at kernel/qapplication.cpp:3481
#10 0x7f221c328be7 in QCoreApplication::notifyInternal2
(receiver=receiver@entry=0x560abe7c67c0, event=event@entry=0x7ffe828513f0) at
kernel/qcoreapplication.cpp:1016
#11 0x7f221cfd139a in QCoreApplication::sendSpontaneousEvent
(event=0x7ffe828513f0, receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#12 QWidgetPrivate::sendPaintEvent (this=this@entry=0x560abe50ef90,
toBePainted=...) at kernel/qwidget.cpp:5714
#13 0x7f221cfd195a in QWidgetPrivate::drawWidget
(this=this@entry=0x560abe50ef90, pdev=pdev@entry=0x560abe4d0a30, rgn=...,
offset=..., flags=flags@entry=36, sharedPainter=sharedPainter@entry=0x0,
backingStore=) at kernel/qwidget.cpp:5654
#14 0x7f221cfd25d0 in QWidgetPrivate::paintSiblingsRecursive
(this=this@entry=0x560abe13cd10, pdev=pdev@entry=0x560abe4d0a30, 

[kwin] [Bug 393139] New: Jarring restoration of minimized window with activated "show selected window" in task switcher settings

[Ivo C]

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

Bug ID: 393139
   Summary: Jarring restoration of minimized window with activated
"show selected window" in task switcher settings
   Product: kwin
   Version: 5.12.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: waz...@protonmail.com
  Target Milestone: ---
 Flags: Usability+

When the option "show selected window" is enabled in the task switcher settings
(available for most task switchers) and the user uses the task switcher with
alt-tab, while still holding alt a preview of the currently selected window is
shown on screen above the rest. On releasing tab, the window preview
immediately disappears and the relatively slow restore from minimized state
animation plays if enabled, or if disabled it still takes a noticeable moment
for the window to appear after its preview has already disappeared. This is a
jarring and unpolished transition with distracting flashing of said window.

Steps to reproduce (try with and without "Minimize Animation" from Desktop
Effects):
1. Make sure that "show selected window" is activated in task switcher settings
with any task switcher that supports it
2. Minimize a window
3. Use the task switcher (alt-tab by default) to highlight that window and keep
the alt key pressed.
4. A preview of the window appears on screen
5. Release alt

Actual results:
A jarring restoration of the minimized window happens and there is flashing, as
described in more detail above.

Expected results:
There is a smooth and seamless transition between the preview and the actual
window.

Possible solution:
Perhaps the restore from minimized state animation should not be played at all
when "show selected window" is activated. Additionally, there should be no
flashing, for example by keeping the window preview visible until the actual
window has been drawn below it.

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

[kwin] [Bug 393139] Jarring restoration of minimized window with activated "show selected window" in task switcher settings

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

   Keywords||usability
  Flags|Usability+  |

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

[kde-cli-tools] [Bug 364985] KCM standalone window gets corrupted on minimize/maximize

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

   Assignee|kdelibs-b...@kde.org|aleix...@kde.org
  Component|kcmshell|general
Product|systemsettings  |kde-cli-tools

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

[systemsettings] [Bug 364985] KCM standalone window gets corrupted on minimize/maximize

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||11tet...@gmail.com

--- Comment #8 from Ivo C <waz...@protonmail.com> ---
*** Bug 344199 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 344199] Wrong size when maximized systemsettings window it's open

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from Ivo C <waz...@protonmail.com> ---


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

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

[systemsettings] [Bug 364985] KCM standalone window gets corrupted on minimize/maximize

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

Summary|Font Management window gets |KCM standalone window gets
   |corrupted on|corrupted on
   |minimize/maximize   |minimize/maximize
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
Version|5.6.5   |5.12.4
  Component|kcm_fontinst|kcmshell
 CC||waz...@protonmail.com
   Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org

--- Comment #7 from Ivo C <waz...@protonmail.com> ---
As noted in duplicate Bug 385076, this affects every standalone KCM window and
is a bug in kcmshell.

I can reproduce it with:
systemsettings 5.12.4
KDE Frameworks 5.44.0
Qt 5.9.4 (built against 5.9.4)

(This is my first attempt at triaging, so please forgive me if I made a
mistake.)

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

[systemsettings] [Bug 393061] Focus not transferred properly to child windows in sidebar view

[Ivo C]

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

--- Comment #1 from Ivo C <waz...@protonmail.com> ---
A likely related side effect of this bug is this scenario:

1. Open System Settings in Sidebar View as a window (not maximized)
2. Open About KDE from the hamburger menu
3. Do not click inside the child window and close it using the title bar close
button
4. Mouse over exactly one top level sidebar item and then move the mouse
pointer off to the left out of the System Settings window 
5. The tooltip stays open and even clicking to change focus to another program
doesn't dismiss it

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

[systemsettings] [Bug 393061] New: Focus not transferred properly to child windows in sidebar view

[Ivo C]

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

Bug ID: 393061
   Summary: Focus not transferred properly to child windows in
sidebar view
   Product: systemsettings
   Version: 5.12.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sidebarview
  Assignee: notm...@gmail.com
  Reporter: waz...@protonmail.com
  Target Milestone: ---

On the main page of System Settings in Sidebar View mode so that the top level
items of the sidebar are visible, when opening a child window such as About KDE
or Configuration, the focus isn't transferred properly the that child window.
The title bar of the child window is highlighted as if it had focus, but
mousing over items in that window such as tabs or links doesn't produce the
expected feedback and mousing over the top level items of the sidebar view on
the left produces tooltips that are drawn over the child window. Clicking once
inside the child window transfers focus properly and the problems no longer
occur for that specific child window.

Steps to reproduce:
1. Open System Settings in Sidebar View
2. Open About KDE from the hamburger menu
3. Do not click inside the child window, but you may drag it by the title bar
4. Mousing over the top level sidebar items through the child window results in
tooltips
5. Mousing over the contents of child window doesn't produce the expected
visual feedback

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

[plasmashell] [Bug 393048] Log out dialogue - bad visibility of selected option

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

   Keywords||accessibility, usability
 CC||waz...@protonmail.com

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

[plasmashell] [Bug 393048] New: Log out dialogue - bad visibility of selected option

[Ivo C]

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

Bug ID: 393048
   Summary: Log out dialogue - bad visibility of selected option
   Product: plasmashell
   Version: 5.12.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: waz...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 111975
  --> https://bugs.kde.org/attachment.cgi?id=111975=edit
Dialogue in question with default theme

The currently selected option in the log out dialogue is highlighted in white,
while the other options are grey, at least in most configurations and default
themes, which is not a great difference in contrast. This leads to bad
visibility of which option is selected in case of a low quality screen, low
brightness level, bad light conditions or a visual impairment of the user.

This screen not only acts as a confirmation screen, but can also be configured
to be triggered e.g. with the power button or another shortcut. This visually
unclear highlighting effect becomes problematic when the user wants to use the
keyboard to select and confirm the desired action because it can be difficult
to see which option is currently selected.

The screen should have a much more clear indicator about which option is
selected. Ideally it should not only be a change of colour like currently, but
instead have an additional indicator such as a clearly visible rectangular
selector with a distinct colour.

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

[plasmashell] [Bug 393041] Crash when applying desktop layout type in Wallpaper configuration

[Ivo C]

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

Ivo C <waz...@protonmail.com> changed:

   What|Removed |Added

 CC||waz...@protonmail.com

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

[plasmashell] [Bug 393041] New: Crash when applying desktop layout type in Wallpaper configuration

[Ivo C]

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

Bug ID: 393041
   Summary: Crash when applying desktop layout type in Wallpaper
configuration
   Product: plasmashell
   Version: 5.12.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: waz...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Plasma version: 5.12.4
KDE Frameworks version: 5.44.0
Qt version: 5.9.4
Distro and kernel version: Fedora 27, all updated, 4.15.15-300.fc27.x86_64

Steps to reproduce:
1. Open "Configure Desktop" wallpaper configuration
2. Select a different layout
3. Click either apply button
4. plasmashell always crashes. It may not crash on the first try, in which case
repeat steps 2 and 3 until it does.

Backtrace:

Breakpoint 2 at 0x70194e60
Breakpoint 3 at 0x70194eb0
Continuing.
[New Thread 0x7fffd9f0b700 (LWP 4677)]
[New Thread 0x7fffd3d72700 (LWP 4678)]
[New Thread 0x7fffd232d700 (LWP 4679)]
[New Thread 0x7fffcbdc6700 (LWP 4680)]
[New Thread 0x7fffc9d66700 (LWP 4681)]
[New Thread 0x7fff36247700 (LWP 4682)]
[New Thread 0x7fff21538700 (LWP 4683)]
[New Thread 0x7fff0e6e1700 (LWP 4685)]
[New Thread 0x7fff07fff700 (LWP 4686)]
[Thread 0x7fff07fff700 (LWP 4686) exited]
[New Thread 0x7fff07fff700 (LWP 4687)]
[New Thread 0x7fff061ee700 (LWP 4688)]
[Thread 0x7fff061ee700 (LWP 4688) exited]
[Thread 0x7fff0e6e1700 (LWP 4685) exited]

Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
0x7fffef86a8fd in malloc_consolidate () from /lib64/libc.so.6

Thread 11 (Thread 0x7fff07fff700 (LWP 4687)):
#0  0x7fffef8d7c6b in poll () from /lib64/libc.so.6
#1  0x7fffe7b9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fffe7b9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7072dc2f in QEventDispatcherGlib::processEvents
(this=0x7fff50b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x706db96a in QEventLoop::exec (this=this@entry=0x7fff07ffec40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7052c8ca in QThread::exec (this=this@entry=0x58eaddf0) at
thread/qthread.cpp:515
#6  0x747a2245 in QQmlThreadPrivate::run (this=0x58eaddf0) at
qml/ftw/qqmlthread.cpp:147
#7  0x70530de2 in QThreadPrivate::start (arg=0x58eaddf0) at
thread/qthread_unix.cpp:368
#8  0x7fffeec3150b in start_thread () from /lib64/libpthread.so.0
#9  0x7fffef8e216f in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fff21538700 (LWP 4683)):
#0  0x7fffef8d7c6b in poll () from /lib64/libc.so.6
#1  0x7fffe7b9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fffe7b9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7072dc2f in QEventDispatcherGlib::processEvents
(this=0x7fff1c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x706db96a in QEventLoop::exec (this=this@entry=0x7fff21537c20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7052c8ca in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fff23eb55a7 in KCupsConnection::run() () from /lib64/libkcupslib.so
#7  0x70530de2 in QThreadPrivate::start (arg=0x5874cc50) at
thread/qthread_unix.cpp:368
#8  0x7fffeec3150b in start_thread () from /lib64/libpthread.so.0
#9  0x7fffef8e216f in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fff36247700 (LWP 4682)):
#0  0x7fffef8d7c6b in poll () from /lib64/libc.so.6
#1  0x7fffe7b9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fffe7b9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7072dc2f in QEventDispatcherGlib::processEvents
(this=0x7fff3b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x706db96a in QEventLoop::exec (this=this@entry=0x7fff36246bf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7052c8ca in QThread::exec (this=this@entry=0x57057870) at
thread/qthread.cpp:515
#6  0x75341116 in QQuickPixmapReader::run (this=0x57057870) at
util/qquickpixmapcache.cpp:868
#7  0x70530de2 in QThreadPrivate::start (arg=0x57057870) at
thread/qthread_unix.cpp:368
#8  0x7fffeec3150b in start_thread () from /lib64/libpthread.so.0
#9  0x7fffef8e216f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fffc9d66700 (LWP 4681)):
#0  0x7fffeec3782d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x77668604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x77668649 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7fffeec3150b in start_thread () from 

[systemsettings] [Bug 392816] Crash when changing Login Manager Background image

[Ivo C]

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

Ivo C <waz...@tutanota.com> changed:

   What|Removed |Added

 CC||waz...@tutanota.com

--- Comment #4 from Ivo C <waz...@tutanota.com> ---
Really sorry, looked at and commented on wrong bug.

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

[systemsettings] [Bug 392816] Crash when changing Login Manager Background image

[Ivo C]

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

Ivo C <waz...@tutanota.com> changed:

   What|Removed |Added

 CC|waz...@tutanota.com |

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

[systemsettings] [Bug 392816] Crash when changing Login Manager Background image

[Ivo C]

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

Ivo C <waz...@tutanota.com> changed:

   What|Removed |Added

 CC|waz...@tutanota.com |

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

[systemsettings] [Bug 392816] Crash when changing Login Manager Background image

[Ivo C]

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

Ivo C <waz...@tutanota.com> changed:

   What|Removed |Added

 CC||waz...@tutanota.com

--- Comment #3 from Ivo C <waz...@tutanota.com> ---
Created attachment 111943
  --> https://bugs.kde.org/attachment.cgi?id=111943=edit
version info

about system shows qt 5.9.4 not 5.10?

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

[systemsettings] [Bug 392987] Crash on reopening after task switcher demo preview got stuck on screen

[Ivo C]

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

Ivo C <waz...@tutanota.com> changed:

   What|Removed |Added

 CC||waz...@tutanota.com

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

[systemsettings] [Bug 392987] New: Crash on reopening after task switcher demo preview got stuck on screen

[Ivo C]

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

Bug ID: 392987
   Summary: Crash on reopening after task switcher demo preview
got stuck on screen
   Product: systemsettings
   Version: 5.12.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: waz...@tutanota.com
  Target Milestone: ---

Application: systemsettings5 (5.12.4)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.14-300.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I was messing with chaning and trying different task switchers for a few
minutes, and also made use of the preview task switcher function that displays
a dummy. Somehow the preview got stuck on screen, I closed System Settings and
it still remained on screen above everything else including the actual task
switcher, reopened System Settings and it immediately crashed but the preview
was now gone.

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

Thread 3 (Thread 0x7f2b6fe28700 (LWP 3612)):
#0  0x7f2b85a9f3f4 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f2b85a59399 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f2b85a59dcb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f2b85a59fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f2b8e95bc4b in QEventDispatcherGlib::processEvents
(this=0x7f2b68000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f2b8e90996a in QEventLoop::exec (this=this@entry=0x7f2b6fe27ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f2b8e75a8ca in QThread::exec (this=this@entry=0x7f2b903d6060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:515
#7  0x7f2b90162449 in QDBusConnectionManager::run (this=0x7f2b903d6060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f2b8e75ede2 in QThreadPrivate::start (arg=0x7f2b903d6060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x7f2b8a5bc50b in start_thread () from /lib64/libpthread.so.0
#10 0x7f2b8db1016f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f2b7971c700 (LWP 3611)):
#0  0x7f2b8db05c6b in poll () from /lib64/libc.so.6
#1  0x7f2b8942cfe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f2b8942edda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f2b7c2babf9 in QXcbEventReader::run (this=0x55e868423000) at
qxcbconnection.cpp:1335
#4  0x7f2b8e75ede2 in QThreadPrivate::start (arg=0x55e868423000) at
thread/qthread_unix.cpp:368
#5  0x7f2b8a5bc50b in start_thread () from /lib64/libpthread.so.0
#6  0x7f2b8db1016f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f2b93c5c540 (LWP 3610)):
[KCrash Handler]
#6  QWidgetPrivate::createTLExtra (this=0x55e86873f9e0) at
kernel/qwidget.cpp:1762
#7  0x7f2b8f83c568 in QWidget::setAttribute (this=0x55e86847d600,
attribute=, on=true) at kernel/qwidget.cpp:11300
#8  0x7f2b8f83d930 in QWidget::winId (this=0x55e86847d600) at
kernel/qwidget.cpp:2551
#9  0x55e86726a08a in SystemSettingsApp::::operator()
(__closure=) at
/usr/src/debug/plasma-systemsettings-5.12.4-1.fc27.x86_64/app/SystemSettingsApp.cpp:31
#10 QtPrivate::FunctorCall, QtPrivate::List<>, void,
SystemSettingsApp::SystemSettingsApp(int&, char**):: >::call
(arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:130
#11 QtPrivate::Functor, 0>::call, void> (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:240
#12 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobject_impl.h:168
#13 0x7f2b8e933637 in QtPrivate::QSlotObjectBase::call (a=0x7fff074957a0,
r=0x7fff07496140, this=0x55e868475540) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#14 QMetaObject::activate (sender=sender@entry=0x55e86845d580,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff074957a0) at kernel/qobject.cpp:3749
#15 0x7f2b8e933b87 in QMetaObject::activate
(sender=sender@entry=0x55e86845d580, m=m@entry=0x7f2b90cc06e0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff074957a0)
at kernel/qobject.cpp:3628
#16