search

jriddell / kdeneon-docker

KDE neon Docker Images
6 stars 0 forks source link

bluedevil causes errors and high CPU load #1

Open mviereck opened 7 years ago

mviereck commented 7 years ago

Hello, I did some tests with kdeneon/all:user-lts. As docker containers have no bluetooth device, bluedevil fails to start, but tries over and over again and does not stop. I get repeating error messages:

bluedevil: ObexManager operational changed false

Also, this causes high CPU usage. I tried a test build adding this lines:

RUN apt-get remove -y bluedevil
RUN apt-get autoremove -y

This avoids the repeating error message, and the CPU calms down.

If I remember right, I've already seen this error on KDE installations years ago. Maybe bluedevil is running on every KDE installation as default, even if no bluetooth hardware is available? This could be a reason for often-heard "KDE is slow/eats too much CPU". I'm not sure where this could be reported as a bug; maybe you as a KDE developer could tell this at the right place?

mviereck commented 5 years ago

Two years later, the issue isn't fixed.

The CPU is still glowing.

Is this repository maintained at all?

mviereck commented 5 years ago

Two further possibilities to fix this issue:

# delete bluez service
RUN rm /usr/share/dbus-1/services/org.bluez.obex.service /usr/share/dbus-1/system-services/bluez.service

Or use x11docker with systemd in container:

x11docker --desktop --gpu --init=systemd -- kdeneon/plasma:user-lts