veromix-plasmoid hangs the entire plasma-desktop

[GoogleCodeExporter]

Which frontend do you use (KDE/Gtk): KDE

What steps will reproduce the problem?
1. Install veromix on Gentoo. 
2. Enable veromix in the system tray. All works fine for now.
3. Log out and back in.

Alternatively:

1. Kill all veromix-related processes, if any
2. plasmoidviewer veromix-plasmoid
3. plasmoidviewer veromix-plasmoid

What is the expected output? What do you see instead?

It should work just fine, but unfortunately plasma-desktop spins 100% of one 
CPU core, and the whole desktop is frozen.

In the second case, I can see the that only the second command manages to 
create the following process:

/usr/bin/python2.7 
/home/.../.kde4/share/apps/plasma/plasmoids/veromix-plasmoid//dbus-service/verom
ix-service-qt.py

The first process keeps spinning the CPU at 100%, without presenting any window.

What version of the product are you using? On what operating system?
Veromix 0.18.3, plasma-workspace 4.8.3, python 2.7

Please provide any additional information below.
Gentoo stable on x86_64, 8 cores, 16GB RAM.

Original issue reported on code.google.com by cheepe...@gmail.com on 18 Jul 2012 at 12:55

[GoogleCodeExporter]

I cannot reproduce it on my ubuntu with kde 4.8.3. I need some more information:

- do you see multiple processes of veromix-service-qt.py (there should be only 
1 even if you have multiple plasmoids/plasmoidviewer's running)? 

- please start "dbus-monitor" in a terminal before running your second test and 
watch (grep) for veromix related messages - is dbus flooded by veromix?

- can can you reproduce your first example if you disable both mediaplayer 
control settings (mpris2 and nowplaying)

- do you have multiple files referencing veromix in 
.local/share/dbus-1/services/ ?

Original comment by nik.lutz on 18 Jul 2012 at 9:03

• Changed state: Hold

[GoogleCodeExporter]

Unfortunately veromix locks plasma-desktop, so after logging in there is no 
possibility for me to launch dbus-monitor. However, I have done tests within 
plasmoidviewer, where we get the same problem.

To answer your questions one by one:

- no, there is only one python process running veromix-service-qt.py
- dbus is not flooded by veromix. In fact, in the instances when it locks there 
is no dbus activity at all. I must conclude that the thingie hangs before 
reaching dbus code
- yes, plasma-desktop locked with both disabled. I also disabled LADSPA, but 
didn't help
- in tests I've done previous to reporting this I have found an older version 
referring to VeromixService.py (I had veromix, but uninstalled it because it 
seemed to leak memory, although it didn't lock up the whole KDE). I removed all 
files there, and now there's only one file referring veromix-service-qt.py

Original comment by cheepe...@gmail.com on 19 Jul 2012 at 6:32

[GoogleCodeExporter]

Is there any way to see the console of the python program when running it 
within plasmoidviewer?

Original comment by cheepe...@gmail.com on 19 Jul 2012 at 6:38

[GoogleCodeExporter]

> Is there any way to see the console of the python program when running it 
within plasmoidviewer?

- you should see python output (print xyz) directly in the konsole where you 
started plasmoidviewer

- when adding veromix to the desktop you should see the python output in 
~/.xsession-errors

--
Can you add the following statement on line 479 of contents/code/main.py:

    def applyConfig(self):
        if 1 == 1:
            return 1

--
Maybe we get the endless loop there..

Original comment by nik.lutz on 20 Jul 2012 at 8:57

[GoogleCodeExporter]

I'm seeing the same thing with kde-4.8.4 on Gentoo, but only if /usr is mounted 
read only. Please try to reproduce the problem when /usr is mounted read only 
and most probably you will see hangs during login, plasma-desktop eating 100% 
cpu of one core, ...

Original comment by anstei...@googlemail.com on 20 Jul 2012 at 2:05

[GoogleCodeExporter]

My /usr is and was read-write, so I believe this is unrelated to the veromix 
problem.

Original comment by cheepe...@gmail.com on 24 Jul 2012 at 11:37

[GoogleCodeExporter]

Is this problem only occuring with veromix? According to:
- https://bugzilla.redhat.com/show_bug.cgi?id=710918
- https://bugs.kde.org/show_bug.cgi?id=272505

other plasmoids can trigger the same problem. One users says:
I did have weather applet on the desktop background - I removed it as I was 
aware of the CPU monitor issue ... so far the 100% CPU has not come back.
--
The plasma lead developper noted:

Aaron J. Seigo 2011-05-27 23:25:45 UTC
bug in the python bindings. several samplings of these problems have been 
forwarded on to the bindings team. this feature set is not maintained by the 
core plasma team, however, so marking as 'upstream' as the closest accurate 
resolution.
----

Maybe it is sufficient to rebuild (looks like you are all running Gentoo) 
plasma-scriptengine-python.

Original comment by nik.lutz on 25 Jul 2012 at 1:49

[GoogleCodeExporter]

I have applied the change you requested to applyConfig, but the same.

However, following comment #7 I've taken a closer look at the logs of success 
versus failure. It seems that it is yet another plasma-workspace problem. Seems 
like the system hangs before reaching veromix's code. I've attached the logs 
for reference.

However, I have no package plasma-scriptengine-python. I'll try to rebuild all 
plasma-related ebuilds.

Original comment by cheepe...@gmail.com on 26 Jul 2012 at 10:03

Attachments:

• veromix-success.txt
• veromix-failure.txt

[GoogleCodeExporter]

I have rebuilt all plasma-related packages and I see no change. I guess I'm 
going to settle with the clumsy KMix for a while.

Original comment by cheepe...@gmail.com on 26 Jul 2012 at 10:20

[GoogleCodeExporter]

It happens here also. Archlinux 64 bits. Sometimes I can't power off my 
computer because, veromix crashes and i have to close manually the warning 
windows.

Original comment by avercuan...@gmail.com on 29 Aug 2012 at 10:39

[GoogleCodeExporter]

Hi,

long time after...

I had the exact same issue.
When KDE plasma-desktop starts, the whole desktop is frozen for a bunch of 
seconds (less than a minute).
I'm also using Gentoo on a i7.

Finally I've found a workaround : I just removed veromix-plasmoid from the 
system tray and put it as a standalone plasmoid in my taskbar, near to the 
system tray.
The result is pretty much the same as expected but no lag on kde's starts !

Hope it helps.

Original comment by gst...@gmail.com on 24 Jun 2014 at 3:15