[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 --- Comment #7 from HD Scania --- Created attachment 158203 --> https://bugs.kde.org/attachment.cgi?id=158203=edit My SDDM logs up to 18 April simplified with only Wayland related, warnings, and errors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |hd-sca...@users.sf.net --- Comment #6 from HD Scania --- Created attachment 158185 --> https://bugs.kde.org/attachment.cgi?id=158185=edit My SDDM logs ... SDDM is where i usually start Plasma Wayland compositions from -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|hd-sca...@users.sf.net |kwin-bugs-n...@kde.org --- Comment #5 from HD Scania --- There was a log running the Plasma Wayland compositions on QTerminal under Trinity X11, but ok for being told what's going wrong? (In reply to Aleix Pol from comment #3) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |hd-sca...@users.sf.net CC||hd-sca...@users.sf.net --- Comment #4 from HD Scania --- Created attachment 158184 --> https://bugs.kde.org/attachment.cgi?id=158184=edit Was a log run on Trinity X11 just now demonstrating whatever was going on with my Plasma Wayland compositions -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 --- Comment #2 from HD Scania --- Where to get logs for Wayland-related issues? And will going frozen then having to reboot even be loggable? I'm quite unsure -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 468635] New: Plasma/Wayland always goes frozen on an AMD APU
https://bugs.kde.org/show_bug.cgi?id=468635 Bug ID: 468635 Summary: Plasma/Wayland always goes frozen on an AMD APU Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net CC: aleix...@kde.org Target Milestone: --- SUMMARY *** AMD APU Zen2 Lucienne-G R4750G with 48GB SoDiMM DDR4 With Artix being installed and run an BtrFS partition on Samsung 980 PRO NVMe SSD 1.82TiB with heatsink KDE Plasma v5.27.4 Qt v5.15.9 KDE frameworks v5.105.0 Linux kernel 6.2.6-artix1-1 (Which commands to check for Wayland version?) Trinity R14.0.13 (Never crashes) XFCE R4.15.x (Never crashes) (Not tested for Plasma/X11, but if doesn't crash or go frozen that often then Wayland is to be blamed for being not that ready on AMD APU's :) ) Never Trinity or XFCE crashes so unlikely h/w fault, but too usually Plasma/Wayland is that way mcuh unstable Every time Plasma/Wayland gets into a crash, frozen and has to reboot always, unable to even get into tty *** STEPS TO REPRODUCE 1. Reboot in SDDM, and log in as a normal user on Plasma/Wayland 2. Operating Plasma as normal, but when idle Plasma/Wayland goes frozen 3. For going frozen and unable to even get into tty, reboot and let local partitions force checked 4. Back to SDDM and log in again as a normal user, and leave Plasma/Wayland idle for a few moments 5. Plasma/Wayland goes frozen again somewhy, so go for Plasma/X11 and/or sth else like Trinity and/or XFCE 6. Upgrade your OS packages for Plasma and trace to up-to-date, Plasma/Wayland still goes frozen somewhy OBSERVED RESULT Plasma/Wayland goes frozen at a random tme somewhy EXPECTED RESULT Plasma/Wayland no longer goes frozen for being idle for a few moments SOFTWARE/OS VERSIONS (Provided at top of this message) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UPSTREAM|--- --- Comment #6 from HD Scania --- I have an issue there, but people there aren’t that active, so also filing that bug here. https://github.com/sddm/sddm/issues/1332 (In reply to Nicolas Fella from comment #4) > Does this actually have anything to do with Plasma? > Sounds like it should be reported to SDDM instead > (https://github.com/sddm/sddm/issues) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added Assignee|plasma-b...@kde.org |hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #3 from HD Scania --- Created attachment 133637 --> https://bugs.kde.org/attachment.cgi?id=133637=edit My last known working sysctl.conf from a backup on an USB SSD -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #2 from HD Scania --- Created attachment 133636 --> https://bugs.kde.org/attachment.cgi?id=133636=edit My current sysctl.conf with NO hardenings left, but SDDM is still being dead; see my first logfile that is the most recent SDDM status -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #1 from HD Scania --- Created attachment 133635 --> https://bugs.kde.org/attachment.cgi?id=133635=edit The Lynis entries for kernel hardening, as of upgraing your scores for Lynis system auditing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429631] New: SDDM crash after hardening
https://bugs.kde.org/show_bug.cgi?id=429631 Bug ID: 429631 Summary: SDDM crash after hardening Product: plasmashell Version: 5.20.3 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: 1.0 Created attachment 133634 --> https://bugs.kde.org/attachment.cgi?id=133634=edit My /var/log/sddm.log SUMMARY SDDM is being crashed for some system security settings STEPS TO REPRODUCE 1. Using kernel hardening instructions for /etc/sysctl.conf from Lynis 2. Restarting SDDM using ‘‘sudo service sddm restart’’ 3. If SDDM is crashed, comment those hardening entries 4. Re-uncomment hardening entries ONE BY ONE to see if the causes are found OBSERVED RESULT SDDM is being dead for some bugs reported from DBus and PAM EXPECTED RESULT The system hardened correctly doesn’t crash any desktop functionalities SOFTWARE/OS VERSIONS FreeBSD/KDE Plasma: GhostBSD (based on 12.2-STABLE) (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.x Qt Version: 5.15.x -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426947] Global Plsama theme changes are crashing the shell
https://bugs.kde.org/show_bug.cgi?id=426947 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|plasma-b...@kde.org |hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426947] New: Global Plsama theme changes are crashing the shell
https://bugs.kde.org/show_bug.cgi?id=426947 Bug ID: 426947 Summary: Global Plsama theme changes are crashing the shell Product: plasmashell Version: 5.19.5 Platform: Netrunner Rolling OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: 1.0 SUMMARY https://invent.kde.org/plasma/plasma-desktop/-/issues/10 STEPS TO REPRODUCE 1. Download new Plasma themes on Artix 2. sudo cp -rrff ~/.local/share/plasma/* /usr/share/plasma 3. sudo rm -rrff ~/.local/sahre/plasma 4. KWin_X11 fine, but the panel are all dead, and backgrounds are locked from any further changes OBSERVED RESULT Not just from step 4 of my reproductions, but also, everything Qt5 too is broken, only SDDM and System Settings are still functional EXPECTED RESULT With a new Plasma global theme done being set, everything is backed to normal SOFTWARE/OS VERSIONS FreeBSD/Linux: Artix runit; 5.9rc6 Linux kernels KDE Plasma version: 5.19.5 KDE frameworks version: 5.74.0-1 Qt Version: 5.15.1-1 ADDITIONAL INFORMATION If those Plasma global theme changes are made outside Plasma itself, i.e. at SDDM>XFCE or SDDM>Enlightenment, there won’t even be those Plasma-crashing bugs at all -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389010] devices cannot see eachother
https://bugs.kde.org/show_bug.cgi?id=389010 HD Scania changed: What|Removed |Added OS|Linux |FreeBSD Version|1.2 |1.10 Platform|Gentoo Packages |FreeBSD Ports -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389010] devices cannot see eachother
https://bugs.kde.org/show_bug.cgi?id=389010 --- Comment #10 from HD Scania --- I’m on HardenedBSD 13-CURRENT and has the same bugs there below, > https://git-01.md.hardenedbsd.org/HardenedBSD/hardenedbsd-ports/issues/5#issuecomment-107 And Mr. dSP, how is your ‘‘pcapng’’ file looked like? Please take some screenshots for us to briefly and clearly explain how your bug is looked like on Gentoo > My system: HardenedBSD CURRENT > Plasma, KDE connect, KF5 are up to date > (but the same combo on Linux never suffers not to connect like this) > KDE connect on Android is up to date too > And both Android and laptop are connected to the same active wifi named ‘‘KK’’ > Laptop model: ASUS K43SJ > Android: Samsung J7-2015 with Android 7.1.1 based AOKP -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389010] devices cannot see eachother
https://bugs.kde.org/show_bug.cgi?id=389010 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|albertv...@gmail.com|hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs
https://bugs.kde.org/show_bug.cgi?id=417530 HD Scania changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421815] KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect
https://bugs.kde.org/show_bug.cgi?id=421815 --- Comment #1 from HD Scania --- Created attachment 128630 --> https://bugs.kde.org/attachment.cgi?id=128630=edit This is how my HardenedBSD’s KDE Connect is looked like, which my Android device ‘‘j7eltexx’’ doesn’t show there -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421814] The frontends, Plasmoids, modules were messed up
https://bugs.kde.org/show_bug.cgi?id=421814 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|albertv...@gmail.com|hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421815] KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect
https://bugs.kde.org/show_bug.cgi?id=421815 HD Scania changed: What|Removed |Added Assignee|albertv...@gmail.com|hd-sca...@users.sf.net CC||hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421815] New: KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect
https://bugs.kde.org/show_bug.cgi?id=421815 Bug ID: 421815 Summary: KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect Product: kdeconnect Version: 1.10 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 128629 --> https://bugs.kde.org/attachment.cgi?id=128629=edit As my middle step of reproduction suggests wtf was happened SUMMARY KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect STEPS TO REPRODUCE 1. Connect to the same domestic wifi SSID on both HardenedBSD and Android 2. As the screenshot suggests, Android does NOT see HardenedBSD at all over KDE Connect, even connected to the same wifi 3. Try to connect to mobile wifi and try again, to check if the issue is remained 4. If connecting properly with changed wifi SSID, it becomes weird issue that’s SSID-dependent OBSERVED RESULT HardenedBSD is unseen to Android somewhy EXPECTED RESULT My HardenedBSD starts connecting with my Android over KDE Connect SOFTWARE/OS VERSIONS FreeBSD distro: HardenedBSD 13-CURRENT KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION On the same laptop, but different distro like Artix, PCLinuxOS, KaOSx, those desktop distro are properly connected with the Android -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 373327] KDE Connect cannot see laptop on the android app and can't see android on laptop
https://bugs.kde.org/show_bug.cgi?id=373327 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421814] New: The frontends, Plasmoids, modules were messed up
https://bugs.kde.org/show_bug.cgi?id=421814 Bug ID: 421814 Summary: The frontends, Plasmoids, modules were messed up Product: kdeconnect Version: 1.7 Platform: Chakra OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 128628 --> https://bugs.kde.org/attachment.cgi?id=128628=edit As which my final step of your reproduction suggests SUMMARY The frontends, Plasmoids, modules were messed up STEPS TO REPRODUCE 1. Wipe every Plasmoids used for KDE Connect 2. Wipe then reinstall KDE Connect packages 3. Open KDE Connect notifications, then it still reports to you the ‘‘module’’ org.kde.kdeconnect is ‘‘not installed’’ OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux distro: Chakra (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs
https://bugs.kde.org/show_bug.cgi?id=417530 --- Comment #1 from HD Scania --- Created attachment 125922 --> https://bugs.kde.org/attachment.cgi?id=125922=edit What are libs metadata issue is looked like -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs
https://bugs.kde.org/show_bug.cgi?id=417530 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|notm...@gmail.com |hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417530] New: PlasmaShell crashes due to "invalid metadata" at libs
https://bugs.kde.org/show_bug.cgi?id=417530 Bug ID: 417530 Summary: PlasmaShell crashes due to "invalid metadata" at libs Product: frameworks-plasma Version: 5.67.0 Platform: Netrunner Rolling OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: hd-sca...@users.sf.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 125921 --> https://bugs.kde.org/attachment.cgi?id=125921=edit Plasma no panels at all, but also stuck at empty layout selections SUMMARY PlasmaShell just crashes, with serious unknown lib metadata issues somewhy, but also no panels could be set, and background layout changes could never be made PLASMASHELL LOGS org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/appimagethumbnail.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kamera.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/krunner_webshortcuts.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kipiplugin_yandexfotki.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kio_kamera.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_autostart.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_info.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kopete_otr.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/mobithumbnail.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/akonadi_serializer_addressee.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/ffmpegthumbs.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/plasma_runner_marble.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_groupwise.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_keyboard.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_chatwindow.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_grub2.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kdeconnect_pausemusic_config.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_componentchooser.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/powerdevilbrightnesscontrolaction_config.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/jpegthumbnail.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kontactsummary.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_networkmanagement.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/krunner_converter.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_webshortcuts.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_wp.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kstyle_breeze_config.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kgamma.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/krunner_placesrunner.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_gadu.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/powerdevildpmsaction_config.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kio_msits.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kipiplugin_dropbox.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/dolphinpart.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_sddm.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/chattexteditpart.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/libplasmanetworkmanagement_openconnectui.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kopete_pluginconfig.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kontact_summaryplugin.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/akonadi_serializer_kcalcore.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_history.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/krunner_windows.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/djvuthumbnail.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kwinscreenedges.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/powerdevilhandlebuttoneventsaction_config.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_samba.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kopete_privacy.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/sambausershareplugin.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_about_distro.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kopete_contactnotes.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/accountwizard_plugin.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/gvpart.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/kcm_kopete_highlight.so" org.kde.plasma: invalid metadata "/usr/lib/qt/plugins/krunner_browsertabs.so" org.kde.plasma: invalid metadata
[Active Window Control] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added Assignee|zrenf...@gmail.com |hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 416491] New: Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.
https://bugs.kde.org/show_bug.cgi?id=416491 Bug ID: 416491 Summary: Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up. Product: Active Window Control Version: unspecified Platform: Netrunner Rolling OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: hd-sca...@users.sf.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 125257 --> https://bugs.kde.org/attachment.cgi?id=125257=edit The screencap which is shown to the issue i need to report SUMMARY Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix (available in About System) KDE Plasma Version: 5.18 KDE Frameworks Version: 5.67 Qt Version: 5.16 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416243] Plasma not ‘‘finishing customizing’’ panels
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416243] Plasma not ‘‘finishing customizing’’ panels
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416243] Plasma not ‘‘finishing customizing’’ panels
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added Component|general |Panel -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 416243] New: Plasma not ‘‘finishing customizing’’ panels
https://bugs.kde.org/show_bug.cgi?id=416243 Bug ID: 416243 Summary: Plasma not ‘‘finishing customizing’’ panels Product: plasma-integration Version: master Platform: Netrunner Rolling OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 125116 --> https://bugs.kde.org/attachment.cgi?id=125116=edit It never really ‘‘finishes customizing’’ the Plasma layouts SUMMARY See ny screenshots, and as told from the title EXPECTED RESULT To get the Plasma shell ‘‘finish customizing’’ the panels, then i could add panels back once Plasma global themes are changed and the system has been next time upgraded with Qt, Plasma, KF upgrades too. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix OpenRC (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
