[plasmashell] [Bug 466355] New: plasmashell service reports multiple child processes
https://bugs.kde.org/show_bug.cgi?id=466355
Bug ID: 466355
Summary: plasmashell service reports multiple child processes
Classification: Plasma
Product: plasmashell
Version: 5.27.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-performance
Assignee: plasma-b...@kde.org
Reporter: q9hc2...@duck.com
Target Milestone: 1.0
SUMMARY
***
Whenever I launch a program from the application menu they automatically get
added to the plasmashell service status. Consequently increasing the memory
usage of the plasmashell service. If for example plasmashell crashes it takes
down any subprocesses with it including FF, Sublime or any other open program.
The question is whether this design is normal behavior, or something changed as
part of the Linux Kernel ?
If I launch FF or any program directly from the terminal then the plasmashell
service status does not get populated with additional processes.
I can understand why FF has these processes as these are controlled via
"dom.ipc.processCount.webIsolated", but the above question remains.
systemctl --user status plasma-plasmashell
plasma-plasmashell.service - KDE Plasma Workspace
Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service;
disabled; preset: enabled)
Active: active (running) since Fri 2023-02-24 13:58:42 GMT; 28min ago
Main PID: 17576 (plasmashell)
Tasks: 669 (limit: 38199)
Memory: 1.9G
CPU: 1min 9.815s
CGroup:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
├─17576 /usr/bin/plasmashell --no-respawn
├─18895 /usr/lib/kf5/kioslave5
/usr/lib/qt/plugins/kf5/kio/kio_http.so https ""
local:/run/user/1000/plasmashellJwEIqa.7.kioworker.socket
├─18923 /usr/lib/kf5/kioslave5
/usr/lib/qt/plugins/kf5/kio/kio_http.so https ""
local:/run/user/1000/plasmashellPuaGeu.8.kioworker.socket
├─19651 /usr/lib/firefox/firefox
├─19733 /usr/lib/firefox/firefox -contentproc -parentBuildID
20230214230245 -prefsLen 33391 -prefMapSize 236521 -appDir
/usr/lib/firefox/browser {813ad8db-5cd6-477d-b667-f80d6f1edf69} 19651 true
socket
├─19758 /usr/lib/firefox/firefox -contentproc -childID 1
-isForBrowser -prefsLen 33494 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{760ccd13-cd8b-4e56-82a8-39b4fbde7>
├─19799 /usr/lib/firefox/firefox -contentproc -childID 2
-isForBrowser -prefsLen 34350 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{9893cd18-6f48-48e6-bfba-48c792baf>
├─19849 /usr/lib/firefox/firefox -contentproc -childID 3
-isForBrowser -prefsLen 38793 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{2272922a-6902-4e12-8b5f-18660cc8f>
├─19905 /usr/lib/firefox/firefox -contentproc -childID 4
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{f51b37ec-b30c-4e63-a0d0-da3ad2a57>
├─19908 /usr/lib/firefox/firefox -contentproc -childID 5
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{789d89e8-3c67-4ee5-bfe8-dd84b8669>
├─19913 /usr/lib/firefox/firefox -contentproc -childID 6
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{9acb5117-941b-41a3-a80c-471c5cbf4>
├─20019 /usr/lib/firefox/firefox -contentproc -childID 7
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{174f3e05-e6e7-4754-a3f9-86ecea1f8>
├─20022 /usr/lib/firefox/firefox -contentproc -childID 8
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{d1657234-8c22-4058-a5cc-b2430beb2>
├─20050 /usr/lib/firefox/firefox -contentproc -childID 9
-isForBrowser -prefsLen 38780 -prefMapSize 236521 -jsInitLen 246560
-parentBuildID 20230214230245 -appDir /usr/lib/firefox/browser
{ebba6a2a-4230-4aff-bd21-92261e3b4>
├─20106 /usr/bin/subl --detached
├─20192 /opt/sublime_text/plugin_host-3.3 20106
/opt/sublime_text/sublime_text
├─20195 /opt/sublime_text/plugin_host-3.8 20106
/opt/sublime_text/sublime_text
***
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Linux Kernel: 6.1.13-1-lts
(available in About System)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
--
You are receiving this mail
[plasmashell] [Bug 466355] plasmashell service reports multiple child processes
https://bugs.kde.org/show_bug.cgi?id=466355 GoldBarb changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466355] plasmashell service reports multiple child processes
https://bugs.kde.org/show_bug.cgi?id=466355 GoldBarb changed: What|Removed |Added CC||k...@davidedmundson.co.uk Component|generic-performance |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466355] plasmashell service reports multiple child processes
https://bugs.kde.org/show_bug.cgi?id=466355 --- Comment #2 from GoldBarb --- (In reply to David Edmundson from comment #1) > >. If for example plasmashell crashes it takes down any subprocesses with it > >including FF, Sublime or any other open program. > > Please verify that is the case. It has happened a few days ago. FF was running, along with Spotify. Something caused Plasmashell to crash resulting in both programs to subsequently exit. Some further observations. Currently I have launched FF from the terminal. As you can see from the below systemctl status from plasmashell FF doesn't appear in the list of subprocesses. plasma-plasmashell.service - KDE Plasma Workspace Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service; disabled; preset: enabled) Active: active (running) since Fri 2023-02-24 14:51:19 GMT; 2h 17min ago Main PID: 24669 (plasmashell) Tasks: 113 (limit: 38199) Memory: 1.0G CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service ├─24669 /usr/bin/plasmashell --no-respawn ├─25927 "/opt/discord/Discord --type=zygote --no-zygote-sandbox" ├─25928 "/opt/discord/Discord --type=zygote" ├─25930 "/opt/discord/Discord --type=zygote" ├─25972 "/opt/discord/Discord --type=gpu-process --field-trial-handle=3519898571147893682,6286612681406132475,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,Ha> ├─29204 /usr/bin/subl --detached ├─29279 /opt/sublime_text/plugin_host-3.3 29204 /opt/sublime_text/sublime_text /home/.config/sublime-text /home/.cache/sublime-text /opt/sublime_text/Packages ├─29282 /opt/sublime_text/plugin_host-3.8 29204 /opt/sublime_text/sublime_text /home/.config/sublime-text /home//.cache/sublime-text /opt/sublime_text/Packages ├─36858 /usr/lib/kf5/kioslave5 /usr/lib/qt/plugins/kf5/kio/kio_http.so https "" local:/run/user/1000/plasmashellgwdWPV.22.kioworker.socket └─36962 /usr/lib/kf5/kioslave5 /usr/lib/qt/plugins/kf5/kio/kio_http.so https "" local:/run/user/1000/plasmashellhebSYC.23.kioworker.socket Is there some special inner mechanism of how systemd works with managing CGroups ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466355] plasmashell service reports multiple child processes
https://bugs.kde.org/show_bug.cgi?id=466355 GoldBarb changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #3 from GoldBarb --- After further investigation I was initially launching FF by calling a shell script to run on the discrete GPU. This shell script sets a few environment variables and then runs FF. I modified the application entry for FF inside kmenuedit and instead of calling a shell script, I entered the environment variables manually, and inside Program I entered firefox. After making this change, FF no longer appears inside the systemctl status of plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467785] New: [NOT A BUG] Spotify Album Art is not displayed inside media player
https://bugs.kde.org/show_bug.cgi?id=467785
Bug ID: 467785
Summary: [NOT A BUG] Spotify Album Art is not displayed inside
media player
Classification: Plasma
Product: plasmashell
Version: 5.27.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Media Player
Assignee: plasma-b...@kde.org
Reporter: q9hc2...@duck.com
CC: k...@privat.broulik.de
Target Milestone: 1.0
SUMMARY
***
Note. this is not a bug, but an issue with the Spotify client.
This is just a comment on how I was able to create a workaround.
When playing audio through Spotify, the media controller applet refuses to
render the album art of the playing track.
The journal logs show.
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/AlbumArtStackView.qml:132:13:
QML Image: Error decoding:
https://open.spotify.com/image/ab67616d1e021cf647cd17bc7382a8056456:
Unsupported image format
Spotify is incorrectly using some invalid the album art url.
qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2
org.mpris.MediaPlayer2.Player.Metadata
mpris:artUrl:
https://open.spotify.com/image/ab67616d1e021cf647cd17bc7382a8056456
Workaround.
I made an update locally to main.qml
Commented out
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/applets/mediacontroller/package/contents/ui/main.qml#L51
Added.
property string albumArt: {
if (!currentMetadata){
return ""
}
var mprisArtUrl = currentMetadata["mpris:artUrl"].toString()
if (mprisArtUrl.length > 0){
if (mprisArtUrl.indexOf("https://open.spotify.com";) == 0){
return
mprisArtUrl.replace("https://open.spotify.com","https://i.scdn.co";)
}
}
}
Then restarted the plasma-plasmashell service.
After the restart the media controller applet now displays the album art.
***
STEPS TO REPRODUCE
1. Play music using Spotify, with the media controller applet loaded
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 467785] [NOT A BUG] Spotify Album Art is not displayed inside media player
https://bugs.kde.org/show_bug.cgi?id=467785 GoldBarb changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 458078] Haruna crashes on startup
https://bugs.kde.org/show_bug.cgi?id=458078 GoldBarb changed: What|Removed |Added CC|ec...@duck.com | -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 458078] Haruna crashes on startup
https://bugs.kde.org/show_bug.cgi?id=458078 GoldBarb changed: What|Removed |Added CC|q9hc2...@duck.com | -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 458078] Haruna crashes on startup
https://bugs.kde.org/show_bug.cgi?id=458078 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477084] New: Kate - AppImage Release/Nightly Download links broken
https://bugs.kde.org/show_bug.cgi?id=477084 Bug ID: 477084 Summary: Kate - AppImage Release/Nightly Download links broken Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: q9hc2...@duck.com Target Milestone: --- SUMMARY The Download AppImage links from Get Kate - Kate are returning 404. https://binary-factory.kde.org/job/Kate_Release_appimage-centos7/ https://binary-factory.kde.org/job/Kate_Nightly_appimage-centos7/ The following Jenkins Jobs are no longer available: - Kate_Release_appimage-centos7 - Kate_Nightly_appimage-centos7 Have the AppImage packages been discontinued ? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477084] Kate - AppImage Release/Nightly Download links broken
https://bugs.kde.org/show_bug.cgi?id=477084 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477084] Kate - AppImage Release/Nightly Download links broken
https://bugs.kde.org/show_bug.cgi?id=477084 --- Comment #2 from GoldBarb --- (In reply to Christoph Cullmann from comment #1) > I think they are in the process to move to GitLab, see > https://invent.kde.org/utilities/kate/-/merge_requests/1319 Thanks for the heads up, I will close this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477084] Kate - AppImage Release/Nightly Download links broken
https://bugs.kde.org/show_bug.cgi?id=477084 GoldBarb changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from GoldBarb --- The Jenkins Jobs are being migrated to Gitlab, which explains why the AppImage links are showing 404. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463868] New: Haruna does not autoplay next video in playlist
https://bugs.kde.org/show_bug.cgi?id=463868 Bug ID: 463868 Summary: Haruna does not autoplay next video in playlist Classification: Applications Product: Haruna Version: 0.10.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: q9hc2...@duck.com Target Milestone: --- SUMMARY *** Haruna does not autoplay next video in the playlist *** STEPS TO REPRODUCE 1. Open a video from a directory containing multiple videos 2. The playlist populates with the videos from the directory OBSERVED RESULT Haruna reports the following error: unknown() : qrc:/qml/MpvVideo.qml:146: TypeError: Property 'playNext' of object PlayListModel(0x560b66476e20) is not a function This issue occurs in 0.10.0. A downgrade to 0.9.3 fixes the issue. EXPECTED RESULT Haruna should play the next video in the playlist SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION This issue occurs on the Flatpak (0.10.0) version too. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463868] Haruna does not autoplay next video in playlist
https://bugs.kde.org/show_bug.cgi?id=463868 GoldBarb changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 458078] Haruna crashes on startup
https://bugs.kde.org/show_bug.cgi?id=458078 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com --- Comment #20 from GoldBarb --- Created attachment 155223 --> https://bugs.kde.org/attachment.cgi?id=155223&action=edit haruna log -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 458078] Haruna crashes on startup
https://bugs.kde.org/show_bug.cgi?id=458078 --- Comment #21 from GoldBarb --- Getting the same issue too. Haruna fails to open on NVIDIA drivers (525.78.01) I followed the comments on https://bugs.kde.org/show_bug.cgi?id=458078#c14 This could be a NVIDIA issue since downgrading the drivers helps and Haruna loads up fine. I am on Arch too, so maybe its an issue there too.. I am not entirely sure though. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 493244] New: [Neon Testing - 6.2 BETA] - systemonitor fails to open
https://bugs.kde.org/show_bug.cgi?id=493244 Bug ID: 493244 Summary: [Neon Testing - 6.2 BETA] - systemonitor fails to open Classification: Applications Product: plasma-systemmonitor Version: git-stable-Plasma/6.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: q9hc2...@duck.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Failed to start plasma-systemonitor. Running from the terminal results in the following output: QQmlApplicationEngine failed to load component qrc:/main.qml:17:1: plugin cannot be loaded for module "org.kde.ksysguard.page": Cannot load library /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/ksysguard/page/libPagePlugin.so: (libKSysGuardSensorFaces.so.1: cannot open shared object file: No such file or directory) STEPS TO REPRODUCE 1. open konsole 2. launch plasma-systemonitor OBSERVED RESULT EXPECTED RESULT systemonitor should open SOFTWARE/OS VERSIONS KDE Neon Testing Edition. Plasma 6.2 BETA ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are vertically mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com --- Comment #87 from GoldBarb --- (In reply to David Edmundson from comment #85) > Git commit e82957f5e6fc72e446239e2ee5139b93d3ceac85 by David Edmundson. > Committed on 22/11/2024 at 21:57. > Pushed by davidedmundson into branch 'master'. > > Use Qt text rendering when high DPI scaling > > It is known that native rendering performs badly with scaling and an > existing workaround is in place. > > The current check does not work on Wayland that has per-window rather > than per-screen scaling. Given Qt changes hinting preferences when any > scaling is used anyway, we may as well commit to using the non-native > rendering throughout. > > For QtQuick the Qt renderer is more performant, handles transformations > better and avoids this issue. Given the results look basically > identical, we can simplify the existing code. > > M +9-8kirigami-plasmadesktop-integration/plasmadesktoptheme.cpp > > https://invent.kde.org/frameworks/qqc2-desktop-style/-/commit/ > e82957f5e6fc72e446239e2ee5139b93d3ceac85 Does the environment variable: QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor Still need to be set ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 495903] 'get new global themes' - all categories missing error on Plasma 5.27
https://bugs.kde.org/show_bug.cgi?id=495903 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com --- Comment #5 from GoldBarb --- See the following comment https://discuss.kde.org/t/global-theme-all-categories-missing/24747/43 On Ubuntu 24.04.1 LTS | KWin version: 5.27.11 | Qt compile version: 5.15.13 the following is output: kf.newstuff.core: Could not find category "121" Each category inside store.kde.org has a corresponding category id. In this case 121 maps to Global Themes (Plasma 5) - KDE Store which is Global Themes (Plasma 5) The framework knewstuff makes use of configuration files inside /usr/share/knsrcfiles Backup the following file and then edit /usr/share/knsrcfiles/lookandfeel.knsrc Update Categories=121 With Categories=Global Themes (Plasma 5) Then try to get new themes again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470826] Demonstration video does not load after click on "Show/hide video" button
https://bugs.kde.org/show_bug.cgi?id=470826 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com --- Comment #12 from GoldBarb --- Fedora 41 KWin version: 6.2.4 Qt compile version: 6.8.0 Launching systemsettings kcm_kwin_effects then opening a preview of an effect results in the following error message. [ogg @ 0x7f2824001600] Broken file, keyframe not correctly marked. A quick look at the src code shows the kwin effect demo videos are served over on https://files.kde.org/plasma/kwin/effect-videos/ Using mpv https://files.kde.org/plasma/kwin/effect-videos/fade_desktop.ogv lets you play the video, but throws the same error message. Further logging. export QT_FFMPEG_DEBUG=1 systemsettings kcm_kwin_effects qml: Pushed pages do not conform to the rules. Please check the documentation. "FFmpeg log: Starting connection attempt to 49.12.122.15 port 443" "FFmpeg log: Successfully connected to 49.12.122.15 port 443" "FFmpeg log: Starting connection attempt to 46.37.189.155 port 443" "FFmpeg log: Successfully connected to 46.37.189.155 port 443" "FFmpeg log: Starting connection attempt to 49.12.122.15 port 443" "FFmpeg log: Successfully connected to 49.12.122.15 port 443" "FFmpeg log: Starting connection attempt to 46.37.189.155 port 443" "FFmpeg log: Successfully connected to 46.37.189.155 port 443" "FFmpeg log: Starting connection attempt to 49.12.122.15 port 443" "FFmpeg log: Successfully connected to 49.12.122.15 port 443" "FFmpeg log: Starting connection attempt to 46.37.189.155 port 443" "FFmpeg log: Successfully connected to 46.37.189.155 port 443" "FFmpeg log: Starting connection attempt to 49.12.122.15 port 443" "FFmpeg log: Successfully connected to 49.12.122.15 port 443" "FFmpeg log: Starting connection attempt to 46.37.189.155 port 443" "FFmpeg log: Successfully connected to 46.37.189.155 port 443" "FFmpeg log: Starting connection attempt to 49.12.122.15 port 443" "FFmpeg log: Successfully connected to 49.12.122.15 port 443" "FFmpeg log: Starting connection attempt to 46.37.189.155 port 443" "FFmpeg log: Successfully connected to 46.37.189.155 port 443" "FFmpeg log: Broken file, keyframe not correctly marked." "FFmpeg log: Statistics: 294426 bytes read, 4 seeks" Is this a FFmpeg decoding issue ? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 501455] File Metadata / Tags / Stream Information
https://bugs.kde.org/show_bug.cgi?id=501455 GoldBarb changed: What|Removed |Added Status|REPORTED|RESOLVED CC||q9hc2...@duck.com Resolution|--- |DUPLICATE --- Comment #1 from GoldBarb --- I don't see this functionality as being essential. Haruna is foremost a media player, anything else like viewing metadata is just extra at this point. > If not, there are other tools to edit and probe multimedia information Case in point.. *** This bug has been marked as a duplicate of bug 491154 *** -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 491154] [Feature Request] Show Media info
https://bugs.kde.org/show_bug.cgi?id=491154 GoldBarb changed: What|Removed |Added CC||jake.nickl...@gmail.com --- Comment #6 from GoldBarb --- *** Bug 501455 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 502249] The fullscreen setting does not work
https://bugs.kde.org/show_bug.cgi?id=502249 GoldBarb changed: What|Removed |Added CC||q9hc2...@duck.com --- Comment #1 from GoldBarb --- (In reply to Mr from comment #0) > I am using Zorin 17.3 which, I believe, uses Ubuntu. I installed Haruna from > the Zorin Software Store. > > Unfortunately, Settings > General: 'start in fullscreen mode' does not work. > It is not obvious to me whether this option means start Haruna in fullscreen > mode or start playback in fullscreen mode. However, it does not matter what > the correct interpretation is because neither one is working on my > platform. Haruna always opens at the default screen size and always plays > in the default screen size. Fullscreen always has to be manually selected. Start in fullscreen mode = starts playback in fullscreen Tested and it works across the following (all in Wayland sessions) - Arch Linux - Fedora 41 - Kubuntu 24.10 # flatpak - Zorin OS 17.3 (core edition) based on Ubuntu 22.04.5 # flatpak Installed via Zorin Software Store -- You are receiving this mail because: You are watching all bug changes.
