I also have a MS HD-3000, and usually leave it disconnected until I need it.
Seeing your issue, I plugged mine in, and found it behaving normally. The light lit while it was being sensed/negotiated, and then turned off until I launched Jami (conf call client) and went into its config which lit the camera and showed me a video preview. Once I existed the config/Jami, the light went out.
Makes me wonder if you might have a startup launching app that is triggering the camera.
In case it denotes a useful difference, I’ve been on the 5.13.x kernels ever since they were available, and just swapped to the 5.14.10 Kernel with this update.
Sound card not recognized and no sound with Baytrail rt5640 (bytcr-rt5640) with SOF.
SOF-firmware version 1.8-1 (stable branch). Is the 1.9-1 version solve the issue with Baytrail hardware ?
Mutter 40.5 version (Manjaro) doesn’t resolve regression with auto screen rotation with wayland. Need to use Mutter-git to solve the problem.
Using openbox with KDE fails to launch plasmashell
Hi guys,
I had this configuration working on Manjaro for years.
Then after the last update I get:
> kquitapp5 plasmashell && kstart5 plasmashell
"Application plasmashell could not be found using service org.kde.plasmashell and path /MainApplication."
plasmashell --replace &
~> kf.plasma.quick: Applet preload policy set to 1 trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for proper ty "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for proper ty "height" Failed to determine whether virtual desktop navigation wrapping is enabled:
"The name org.kde.KWin was not provided by any .service files" Plasma Shell startup completed