[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu

2021-04-17 Thread remi
https://bugs.kde.org/show_bug.cgi?id=391322

remi  changed:

   What|Removed |Added

 CC||remigiush...@gmail.com

--- Comment #58 from remi  ---
Bug is present after installing different application menu (start menu) from
the built-in widget store. Changing in "kwinrc" is not helping. After assigning
"Meta" + "F1", when only "Meta" key is pressed application menu is opening.

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

[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu

2021-04-17 Thread remi
https://bugs.kde.org/show_bug.cgi?id=391322

--- Comment #59 from remi  ---
(In reply to remi from comment #58)
> Bug is present after installing different application menu (start menu) from
> the built-in widget store. Changing in "kwinrc" is not helping. After
> assigning "Meta" + "F1", when only "Meta" key is pressed application menu is
> opening.

To be more precise I installed Ditto Menu.

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

[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu

2021-04-17 Thread remi
https://bugs.kde.org/show_bug.cgi?id=391322

remi  changed:

   What|Removed |Added

   Platform|openSUSE RPMs   |Archlinux Packages
Version|5.14.3  |5.21.3

--- Comment #60 from remi  ---
Fix should be easy. After installing application menu widget (start menu) the
"Meta" + "F1" or "Alt" + "F1" (as I read it is default) should be reassigned to
use "Meta" key itself.

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

[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu

2021-04-17 Thread remi
https://bugs.kde.org/show_bug.cgi?id=391322

--- Comment #61 from remi  ---
It stops working because after installing application menu widget (start menu)
the "Alt" + "F1" key assignment is deleted.

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

[kate] [Bug 476083] New: External Tools / Run Shell Script : does not work

2023-10-25 Thread remi
https://bugs.kde.org/show_bug.cgi?id=476083

Bug ID: 476083
   Summary: External Tools / Run Shell Script : does not work
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: remiforkdebugrep...@gmail.com
  Target Milestone: ---

SUMMARY
External Tools / Run Shell Script : does not execute the shell script

Example script :
#!/bin/bash
echo hello
echo hello > ~/hello

STEPS TO REPRODUCE
1. Open a valid bash script :
- begins with #!/bin/bash
- owned by the current user
- has +x file permission
- executed successfully when launched from konsole
2. Click Menu > Tools > External Tools > Tools > Run Shell Script

OBSERVED RESULT
Konsole window opens and closes immediately
The script is not executed

EXPECTED RESULT
The script is executed
Konsole window shows the result
Konsole window waits a key press to close the window

SOFTWARE/OS VERSIONS
Linux: Debian 11
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This bug is due to the default command arguments configured with "Run Shell
Script" tool, which is :
-e sh -c "cd %{Document:Path} && pwd && chmod -vc a+x %{Document:FileName}
&& ./%{Document:FileName} ; echo Press any key to continue. && read -n 1"

When running the following command :
sh -c read -n 1

We get an error :
-n: 1: read: arg count

On my system it can be solved by replacing :
echo Press any key to continue. && read -n 1"
by :
echo Press enter to continue. && read null"

Which is a valid sh command

I can open a minimal merge request but I don't know the eventual implications
on other systems

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

[kate] [Bug 476083] External Tools / Run Shell Script : does not work

2023-10-25 Thread remi
https://bugs.kde.org/show_bug.cgi?id=476083

--- Comment #1 from remi  ---
Some additional questions :

Is it reasonable to change the file permission (the 'chmod' part) by default ?

What's the goal of 'pwd' in the command ?

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

[kate] [Bug 476083] External Tools / Run Shell Script : does not work

2023-10-25 Thread remi
https://bugs.kde.org/show_bug.cgi?id=476083

--- Comment #2 from remi  ---
The default command has been introduced in this commit :
https://invent.kde.org/utilities/kate/-/commit/0d1c47d198f6a3220fb10973635689416feab4e9

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

[kate] [Bug 476083] External Tools / Run Shell Script : does not work

2023-10-25 Thread remi
https://bugs.kde.org/show_bug.cgi?id=476083

--- Comment #3 from remi  ---
Reply to my previous comment : 'pwd' is useful, otherwise the konsole window
does not show the path

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

[frameworks-ktexteditor] [Bug 329247] Indenting a selection that starts or ends in leading whitespace changes the selection

2023-10-26 Thread remi
https://bugs.kde.org/show_bug.cgi?id=329247

remi  changed:

   What|Removed |Added

 CC||remiforkdebugreport@gmail.c
   ||om

--- Comment #10 from remi  ---
I have been able to reproduce this bug in a unit test.

If I can, I'll propose a fix that only involves the indent/unindent part of the
code.

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

[kmymoney] [Bug 492582] New: Please change "Versement" and "Dépôt" by "Recette" and "Dépense" in french translation

2024-09-03 Thread Remi
https://bugs.kde.org/show_bug.cgi?id=492582

Bug ID: 492582
   Summary: Please change "Versement" and "Dépôt" by "Recette" and
"Dépense" in french translation
Classification: Applications
   Product: kmymoney
   Version: unspecified
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: translation
  Assignee: kmymoney-de...@kde.org
  Reporter: r.rel...@posteo.net
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Please change "Versement" and "Dépôt" by "Recette" and "Dépense" in french
translation

In french version,   5.1.80-d5e4277 Appimage, "Versement" and "Dépôt" are very
confusing.

Please, replace with "Recette" and "Dépense" in great book view and new
transaction view.





STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 492582] Please change "Versement" and "Dépôt" by "Recette" and "Dépense" in french translation

2024-09-04 Thread Remi
https://bugs.kde.org/show_bug.cgi?id=492582

--- Comment #3 from Remi  ---
They are too close to each other in meaning and I have found myself on several
occasions wondering where I should put my amount, something that never happened
to me before with terms like "Recette" and "Dépense".

"Versement" we don't really know in which direction the financial flow takes
place, in + or in -..."Dépôt" is for me the payment of a sum in cash into an
account (we sometimes speak of an account deposit elsewhere).

"Recette" is very clear, it is an income, "Dépense" is an exit.

No possible confusion.

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

[krita] [Bug 395469] New: crashes with color sliders with HSI, HSY'...

2018-06-15 Thread remi
https://bugs.kde.org/show_bug.cgi?id=395469

Bug ID: 395469
   Summary: crashes with color sliders with HSI, HSY'...
   Product: krita
   Version: 4.0.4
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: remifon...@yahoo.fr
  Target Milestone: ---

when playing with color sliders with multiple color model at the same time, I
quickly get crash.

steps to reproduce the crash:
1. open Krita
2. create new document:
my document was open in RGA/Alpha. 32bitsfloat/channel, profile
"sRGB-elle-V2-g10.icc (default)".
3. in "Advanced color Selector" click on the setting icon and in Docker:"Color
sliders" add "HSV", "HSI" and "HSY'" all sliders, then validate settings
4. play with color sliders in the "Color Sliders" docker.

in following reported crash I had HSV, HSI and HSY' at the same time, and was
playing with each sliders to understand their how they are related. Krita would
crash quickly (less than 5 min).


attached is a backtrace of the crash I got when launching krita as follow:

lldb /Applications/Krita.app/Contents/MacOS/krita 

my os: OSX 10.11.6
MacBook Pro (15-inch, Mid 2009)
2.66 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
NVIDIA GeForce 9600M GT 256 MB

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

[krita] [Bug 395469] crashes with color sliders with HSI, HSY'...

2018-06-15 Thread remi
https://bugs.kde.org/show_bug.cgi?id=395469

--- Comment #1 from remi  ---
Created attachment 113364
  --> https://bugs.kde.org/attachment.cgi?id=113364&action=edit
lldb backtrace

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

[drkonqi] [Bug 405361] New: Can't log in with drkonqi to report a crash

2019-03-11 Thread Remi Rampin
https://bugs.kde.org/show_bug.cgi?id=405361

Bug ID: 405361
   Summary: Can't log in with drkonqi to report a crash
   Product: drkonqi
   Version: 5.12.7
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: remiram...@gmail.com
  Target Milestone: ---

Created attachment 118723
  --> https://bugs.kde.org/attachment.cgi?id=118723&action=edit
Screenshot of the wizard page

SUMMARY


STEPS TO REPRODUCE
1. An app crash, drkonqi pops up to report bug
2. Check that you can provide "what I was doing when the application "Plasma"
crashed"
3. Enter KDE BTS username and password

OBSERVED RESULT
The "next", "finish", and "login" button are all disabled, preventing me from
reporting the crash.

EXPECTED RESULT
I can report a crash with the crash reporting assistant.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.04
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Plasma crashed when I clicked "disconnect" next to my WiFi connection, which is
what triggered drkonqi in the first place.

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

[drkonqi] [Bug 405361] Can't log in with drkonqi to report a crash

2019-03-11 Thread Remi Rampin
https://bugs.kde.org/show_bug.cgi?id=405361

Remi Rampin  changed:

   What|Removed |Added

 CC||remiram...@gmail.com

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

[kwin] [Bug 383416] New: Compositor crashed

2017-08-12 Thread Remi Gastaldi
https://bugs.kde.org/show_bug.cgi?id=383416

Bug ID: 383416
   Summary: Compositor crashed
   Product: kwin
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: remi.gasta...@protonmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Open youtube video on vivaldi browser on second screen and then on other screen
switch window with alt-tab

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f73d62f2840 (LWP 547))]

Thread 12 (Thread 0x7f73a35ef700 (LWP 772)):
#0  0x7f73d5c70f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f73d3281ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f73d328333f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f73d3229ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f73d304340e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f73cd90d1d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f73d304815b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f7394c38700 (LWP 666)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73d21a0b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f73d21a0b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f7395c3a700 (LWP 658)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f739643b700 (LWP 657)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f7396c3c700 (LWP 656)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f739743d700 (LWP 655)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f7397e43700 (LWP 654)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f7398785700 (LWP 653)):
#0  0x7f73cee121ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73a104352c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f73a1043238 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73cee0c049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d5c7af0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f73b142d700 (LWP 641)):
#0  0x7f73d5c70f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f73d3281ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f73d328333f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f73d3229ffb in
QEventLoop::exec(QFlags) () at
/usr/

[kde] [Bug 368497] New: Le bureau KDE s'est planté quand j'ai ouvert une troisième fenêtre Dolphin

2016-09-09 Thread Remi Losno via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368497

Bug ID: 368497
   Summary: Le bureau KDE s'est  planté quand j'ai ouvert une
troisième fenêtre Dolphin
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: lo...@ipgp.fr

Application: plasma-desktop (4.11.16)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.4.16-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:
Je transférais des fichiers en sftp avec Dolphin. La petite barre de
progression sur l'icône du lanceur de Dolphin était activé. J'ai ouvert une
troisième fenêtre et il y a eu un plantage du bureau de kde. La barre de
progression sur le lanceur Dolphin a disparu ensuite.

-- Backtrace:
Application: Outil de gestion de fenêtres Plasma (plasma-desktop), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f71b374e780 (LWP 8777))]

Thread 3 (Thread 0x7f7180408700 (LWP 8780)):
#0  0x7f71b1fdb67f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f719dfb573a in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQtScript.so.4
#2  0x7f719dfb5769 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQtScript.so.4
#3  0x7f7199efd754 in ?? () from /usr/lib64/nvidia304/libGL.so.1
#4  0x7f71b1fd65bd in start_thread () from /lib64/libpthread.so.0
#5  0x7f71b0d4e62d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f70fbdd8700 (LWP 8784)):
#0  0x7f71b0d42d6d in poll () from /lib64/libc.so.6
#1  0x7f71ade28eb4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f71ade28fbc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f71b2393e3e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQtCore.so.4
#4  0x7f71b2365931 in
QEventLoop::processEvents(QFlags) () from
/lib64/libQtCore.so.4
#5  0x7f71b2365c45 in
QEventLoop::exec(QFlags) () from
/lib64/libQtCore.so.4
#6  0x7f71b2263899 in QThread::exec() () from /lib64/libQtCore.so.4
#7  0x7f71b23473d3 in QInotifyFileSystemWatcherEngine::run() () from
/lib64/libQtCore.so.4
#8  0x7f71b2265fff in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#9  0x7f7199efd754 in ?? () from /usr/lib64/nvidia304/libGL.so.1
#10 0x7f71b1fd65bd in start_thread () from /lib64/libpthread.so.0
#11 0x7f71b0d4e62d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f71b374e780 (LWP 8777)):
[KCrash Handler]
#5  0x7f70f2aec541 in mov_probe () from /lib64/libavformat.so.56
#6  0x7f70f800c6a5 in FFMPEGEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /usr/lib64/strigi/strigiea_ffmpeg.so
#7  0x7f71a205f6a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#8  0x7f71a2036bf5 in Strigi::AnalysisResult::indexChild(std::string
const&, long, Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#9  0x7f71a207a753 in OdfEndAnalyzer::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#10 0x7f71a205f6a8 in
Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&,
Strigi::StreamBase*) () from /lib64/libstreamanalyzer.so.0
#11 0x7f71a26c7471 in KFileMetaInfoPrivate::init(QIODevice&, KUrl const&,
long, QFlags) () from /usr/lib64/libkio.so.5
#12 0x7f71a26c795a in KFileMetaInfo::KFileMetaInfo(QString const&, QString
const&, QFlags) () from /usr/lib64/libkio.so.5
#13 0x7f71a26b495f in KFileItem::metaInfo(bool, int) const () from
/usr/lib64/libkio.so.5
#14 0x7f7188b75f6c in ToolTipWidget::metaInfo() const () from
/usr/lib64/kde4/plasma_applet_folderview.so
#15 0x7f7188b787fb in ToolTipWidget::setContent() () from
/usr/lib64/kde4/plasma_applet_folderview.so
#16 0x7f7188b78aee in ToolTipWidget::toolTipAboutToShow() () from
/usr/lib64/kde4/plasma_applet_folderview.so
#17 0x7f71b236ea72 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () from
/lib64/libQtCore.so.4
#18 0x7f71b2370d2e in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from
/lib64/libQtCore.so.4
#19 0x7f71a097e69a in Plasma: