Plasma Bigscreen issueshttps://invent.kde.org/plasma/plasma-bigscreen/-/issues2024-03-08T14:06:26Zhttps://invent.kde.org/plasma/plasma-bigscreen/-/issues/21Plasma Bigscreen Master Branch is no longer supported on Post market OS2024-03-08T14:06:26ZAditya MehraPlasma Bigscreen Master Branch is no longer supported on Post market OSAs plasma bigscreen has been droped from edge branch of Post market OS and the packager has no plans to support unsupported, this case is being marked for reference to future releases.
- Ensure Plasma Bigscreen is upto release quality
-...As plasma bigscreen has been droped from edge branch of Post market OS and the packager has no plans to support unsupported, this case is being marked for reference to future releases.
- Ensure Plasma Bigscreen is upto release quality
- Approach alternate distribution accepting plasma bigscreen developmenthttps://invent.kde.org/plasma/plasma-bigscreen/-/issues/20starting bigscreen kactivitymanagerd not running2022-05-27T10:47:31ZLuis Büchistarting bigscreen kactivitymanagerd not runningAfter building bigscreen & dependencies from source I run `QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland "plasmashell -p org.kde.plasma.mycroft.bigscreen"` as shown in the Readme and while this does create a new window with a mou...After building bigscreen & dependencies from source I run `QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland "plasmashell -p org.kde.plasma.mycroft.bigscreen"` as shown in the Readme and while this does create a new window with a mouse cursor (and sometimes I've even had highlighted hot corners!) the screen stays black. In konsole I get the following:
```
dbus-daemon[3432]: [session uid=1000 pid=3432] Activating service name='org.kde.ActivityManager' requested by ':1.1' (uid=1000 pid=3441 comm="/usr/bin/plasmashell -p org.kde.plasma.mycroft.big" label="unconfined")
Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
starting invalid corona "org.kde.plasma.mycroft.bigscreen"
dbus-daemon[3432]: [session uid=1000 pid=3432] Successfully activated service 'org.kde.ActivityManager'
```
So it seems it's trying to start ActivityManager, but not waiting for it to be started before trying to move on? But what does "starting invalid corona" mean? (This is also the only error I get when trying to `plasmashell --replace -p org.kde.plasma.mycroft.bigscreen` instead of running in a window) Googling this is absolutely impossible thanks to a certain pandemic.
I've run it both from an X11 host session as well as a Wayland host session (the log comes from the latter) and the result is always the same. The issue may actually lie with plasma-nano as running that using the same command as provided here just with `org.kde.plasma.nano` instead of `org.kde.plasma.mycroft.bigscreen` also yields the same error, but considering they provide different instructions for starting the shell I guess it's more relevant for here
I'm running on an Intel Atom (in an UP-Board) on the newest KDE Neon image (downloaded just 2 days ago) - the Atom line does sometimes tend to do weird things to software but in the end it's x86 so mostly it should be fine.
For completeness sake, here is the entire console output, including all the stuff that seemingly went right before the error:
<p>
<details>
<summary>Full log</summary>
<pre><code>QT_QPA_PLATFORM=wayland dbus-run-session kwin_wayland "plasmashell -p org.kde.plasma.mycroft.bigscreen"
No backend specified through command line argument, trying auto resolution
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor is running
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5127:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5129:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5131:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5135:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5137:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5145:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5149:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5151:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5155:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5158:46: this compose sequence is a duplicate of another; skipping line
kwin_core: Failed to update gamma ramp for output KWin::Wayland::WaylandOutput(0x7f8ff400b5c0, name="WL-0", geometry=QRect(0,0 1024x768), scale=1)
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (CHV)
OpenGL version string: 4.6 (Core Profile) Mesa 21.2.6
OpenGL shading language version string: 4.60
Driver: Intel
GPU class: Cherryview
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 21.2.6
Linux kernel version: 5.13
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
kwin_xkbcommon: XKB: inet:224:50: unrecognized keysym "XF86FullScreen"
dbus-daemon[3432]: [session uid=1000 pid=3432] Activating service name='org.kde.ActivityManager' requested by ':1.1' (uid=1000 pid=3441 comm="/usr/bin/plasmashell -p org.kde.plasma.mycroft.big" label="unconfined")
Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
starting invalid corona "org.kde.plasma.mycroft.bigscreen"
dbus-daemon[3432]: [session uid=1000 pid=3432] Successfully activated service 'org.kde.ActivityManager</code></pre>
</details>
</p>
Edit: After rebuilding Plasma Nano I managed to get it to run "properly" (at least it showed me date and time and a wallpaper, even though it's not really responding to any of my inputs), Plasma Bigscreen still has the same issues though. Difference here: I built Plasma Nano with the provided instructions from another issue instead of kdesrc-build.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/19VPN support2021-12-25T14:57:48ZYoram Bar-HaimVPN supportVPN connectivity works well via network-manager cli. however, current UI can only display, disable and delete VPN connections.VPN connectivity works well via network-manager cli. however, current UI can only display, disable and delete VPN connections.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/17draft: [design proposal] Increase padding overall, use components closer to K...2022-04-07T15:15:20ZManuel Jesús de la Fuentem@nueljl.indraft: [design proposal] Increase padding overall, use components closer to Kirigami, use of grids etc## Grids and margin
Use grids throughout the UI to make Voice skills, native Bigscreen apps and the Home screen with Settings be more consistent and readable. We should add more padding around the screen edges and set a "diffuse" region...## Grids and margin
Use grids throughout the UI to make Voice skills, native Bigscreen apps and the Home screen with Settings be more consistent and readable. We should add more padding around the screen edges and set a "diffuse" region. I'll be explaining this below.
For these examples, we're assuming the display resolution will be 1920x1080@2x as a baseline since it's probably the most common resolution, but as the display resolution and density is scaled everything will look the same.
#### Margin
First, we need to think about the margin between the main content and screen edge. The diffuse region in the example below is 64px@1x (units.smallSpacing * 16). In this area, content may still present and legible when overflowing the visible area, but not in focus so it should have less visual weight or importance.
![Screenshot_20211025_220222](/uploads/7d9e220b88fee2940ed5cadf9109e07a/Screenshot_20211025_220222.png)
The upper margin between the content and the screen edge would still be used as an always displayed header. If non fullscreen UI elements add a scrim to the previous content, it can use less padding as long as the text label stays inside the region. Footers with additional information would be displayed on the lower margin, as much as possible.
![Screenshot_20211025_221500](/uploads/c26b7830ec1f13fc61cee39bd65251a2/Screenshot_20211025_221500.png)
![Screenshot_20211025_221526](/uploads/c8e94a279a91b25d4777ddf3d14d033b/Screenshot_20211025_221526.png)
This makes it so the information is never obscured to the user but it still gets out of the way.
#### Grid
The grid isn't a magical or mythical number of lines that are chosen randomly. It should work the way users do, aiding at displaying and organizing the content, be it apps, videos, songs etc. We need to balance the density of information like text and images with the negative background. In a TV environment, we should strive to display content in a way where users don't get stressed with small text and images, or have to keep pressing buttons to continue searching for information.
We want to ideally display two to three lines of cards, which may vary depending on the additional information presented to the user.
Comfort at all times: Our eyes love staying at the vertical center of our vision, where there's less eye strain. Think about the way dense information on museums are written, with content being centered vertically and starting just above the center and titles right above that. Never push important information away from the center.
Control at all times: We must try avoiding making the user feel lost after selecting an option. They should always feel in control of their devices and feel like second nature to use. Went down a row of content? Display part of the previous one on the top, set the selected row at the center and expose the third row so the user knows what to expect. Searched content inside a skill on a search bar? Display a FAB in the diffuse region so users don't have to go all the way up to switch between views or search again.
---
wip
Expose settings clearly, and when it matters. When selecting an option with settings on the sidebar/drawer, use a scrim on the main content area to bring focus towards the settings. Use the new keyboard highlight style for navigation, and break down the options into Kirigami style cards, which look more interactive then floating components.
* Take weight away from the panel and into the content by increasing the background contrast with smooth gradients so the panel isn't the protagonist on the screen. Add useful information like the time and date.
* More use of typography overall.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/16Wayland support: use an out-of-process arrow-controllable keyboard2022-05-02T08:06:11ZBart RibbersWayland support: use an out-of-process arrow-controllable keyboardMaybe this could use Maliit like Plasma Desktop and Mobile, but it currently [doesn't support arrow control](https://github.com/maliit/keyboard/issues/21) (although they _do_ want that).
On the Bigscreen BoF at Akademy @adityam said he ...Maybe this could use Maliit like Plasma Desktop and Mobile, but it currently [doesn't support arrow control](https://github.com/maliit/keyboard/issues/21) (although they _do_ want that).
On the Bigscreen BoF at Akademy @adityam said he would look into creating a virtual-keyboard app using QtVirtualKeyboard.
Issue split out from #12.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/15QtWidgets apps don't open the virtual keyboard2021-08-06T10:16:50ZBart RibbersQtWidgets apps don't open the virtual keyboardFor example, launch Konsole or Falkon.
This issue is split out from #12.For example, launch Konsole or Falkon.
This issue is split out from #12.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/12Notes for Akademy bof2021-08-06T10:26:44ZMarco MartinNotes for Akademy bof
* tons of repositories all over the place. It's a mess!
* see what's still on github, migrate to invent what's possible
* debos reciped: can they be on more than one group in gitlab?
* need a list of all repos involved an...
* tons of repositories all over the place. It's a mess!
* see what's still on github, migrate to invent what's possible
* debos reciped: can they be on more than one group in gitlab?
* need a list of all repos involved and put them in a gitlab group
* a sysadmin ticket for group creation and move of all the stuff in that group
* get the apps like the browser out of personal repos
* get in kdereview all the repos
* can those be released with the same big script, the same day as plasma releases?
* decoupling bigscreen with mycroft, possible to have releases without.
* it seems it's mostly ui stuff
* open an issue about this.
* migrate to wayland
* libcec: Aleix did a merge request for cec in kwin:
https://invent.kde.org/plasma/kwin/-/merge_requests/1061
* virtual keyboard: manage to have arrow controllable keyboard out of process (not maliit?)
TODO Aditya looks into creating a VK app using QtVK
* missing applications
* kirigami apps by default don't work well (keyboard navigation is lacking in some places)
* kirigami needs https://invent.kde.org/frameworks/kirigami/-/merge_requests/292
* apps would need always some manual adjustment
* discover is a priority. New frontend vs using file selectors?
* image releases
* need a beta3 release next month
* can we do nightly or monthly releases? probably go to automanted
* priority bugs:
* konsole and falkon don't open the keyboard when open (maybe all qwidget apps?)
* shutdown gets stuck on some systemd service
https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/systemd/logind.conf.d/40_kde_neon_allyourprocessarebelongtous.conf
https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/systemd/system.conf.d/40_kde_neon_destroyer_of_worlds.confhttps://invent.kde.org/plasma/plasma-bigscreen/-/issues/10[Feature Request] Use local Mozilla Deepspeech for voice recognition2020-12-06T10:09:13ZVagano Honeo[Feature Request] Use local Mozilla Deepspeech for voice recognitionhttps://invent.kde.org/plasma/plasma-bigscreen/-/issues/9Documentation editing2020-09-08T09:39:20ZMawoka HansDocumentation editingPlease change the installation instruction for plasma-nano!Please change the installation instruction for plasma-nano!https://invent.kde.org/plasma/plasma-bigscreen/-/issues/7Ideas for other ways Bigscreen could be used2024-03-08T22:02:37ZNoah DavisIdeas for other ways Bigscreen could be usedThis is for brainstorming, not necessarily things we must do.
- As a UI for speakers giving talks on a stage
- May need an app for browsing documents with a remote.This is for brainstorming, not necessarily things we must do.
- As a UI for speakers giving talks on a stage
- May need an app for browsing documents with a remote.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/6Compile/run issues on Kubuntu2021-08-22T03:49:00ZJames HallCompile/run issues on KubuntuWhen I run cmake after having all of the requisite software installed I get:
CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/KF5Package/KF5PackageMacros.cmake:74 (message):
KPackage components should be specified in reverse d...When I run cmake after having all of the requisite software installed I get:
CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/KF5Package/KF5PackageMacros.cmake:74 (message):
KPackage components should be specified in reverse domain notation.
Appstream information won't be generated for kcm_audiodevice.
Call Stack (most recent call first):
kcms/audio-device-chooser/CMakeLists.txt:25 (kpackage_install_package)
CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/KF5Package/KF5PackageMacros.cmake:74 (message):
KPackage components should be specified in reverse domain notation.
Appstream information won't be generated for kcm_mediacenter_wifi.
Call Stack (most recent call first):
kcms/wifi/CMakeLists.txt:25 (kpackage_install_package)
CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/KF5Package/KF5PackageMacros.cmake:74 (message):
KPackage components should be specified in reverse domain notation.
Appstream information won't be generated for kcm_mediacenter_kdeconnect.
Call Stack (most recent call first):
kcms/kdeconnect/CMakeLists.txt:25 (kpackage_install_package)
and then when I try to run it with `plasmashell --replace -p org.kde.plasma.mycroft.bigscreen` I get:
org.kde.plasmaquick: Applet preload policy set to 1
Could not set containment property on rootObject
and the screen is black with nothing on it.https://invent.kde.org/plasma/plasma-bigscreen/-/issues/2Add debian packaging2022-09-28T14:38:15ZAlex AntonovAdd debian packagingPlease, add debian packaging filesPlease, add debian packaging files