[plasmashell] [Bug 457498] Allow setting Floating and Adaptive Transparency panel settings via Desktop Scripting for Global Theme Layouts
https://bugs.kde.org/show_bug.cgi?id=457498 --- Comment #3 from The Feren OS Dev --- (In reply to Nate Graham from comment #2) > Fixed bi Niccolò Venerandi with > https://invent.kde.org/plasma/plasma-workspace/-/commit/ > 089eb522d5598bb89bf184f4649a69417a732f31 for Plasma 6.0! I don't think this accounts for Adaptive Transparency, though, unless I'm mistaken - haven't had time yet to compile and check in a VM. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475582] libappstream5 is missing from the repositories - Discover depends on libappstream5
https://bugs.kde.org/show_bug.cgi?id=475582 The Feren OS Dev changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from The Feren OS Dev --- Ok, this is plain weird - after updating APT cache again, plasma-discover no longer has a dependency issue, so... I guess it got RESOLVED since...? Guess I'll just... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475582] libappstream5 is missing from the repositories - Discover depends on libappstream5
https://bugs.kde.org/show_bug.cgi?id=475582 --- Comment #3 from The Feren OS Dev --- Ignore the /usr/bin/git - that's just something my current fish config likes to do. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475582] libappstream5 is missing from the repositories - Discover depends on libappstream5
https://bugs.kde.org/show_bug.cgi?id=475582 --- Comment #2 from The Feren OS Dev --- (In reply to Jonathan Riddell from comment #1) > We did update to a newer appstream for a while but that should now be undone. > > You don't say what edition of Neon you're using (user?) or what version of > plasma-discover you're installing > > Please paste: > apt-cache policy plasma-discover > apt-cache policy libappstreamqt2 I mean, I did choose Packages User Edition, assuming that would've been an indicator. Anyway: plasma-discover: Installed: (none) Candidate: 5.27.8-0xneon+22.04+jammy+release+build39 Version table: 5.27.8-0xneon+22.04+jammy+release+build39 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.27.8-0xneon+22.04+jammy+release+build29 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.27.7-0xneon+22.04+jammy+release+build27 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.27.6-0xneon+22.04+jammy+release+build26 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 5.24.7-0ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 5.24.4-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages libappstreamqt2: Installed: 0.16.2-0xneon+22.04+jammy+release+build40 Candidate: 0.16.2-0xneon+22.04+jammy+release+build40 Version table: *** 0.16.2-0xneon+22.04+jammy+release+build40 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 100 /var/lib/dpkg/status 0.15.2-2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages /usr/bin/git -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475582] New: libappstream5 is missing from the repositories - Discover depends on libappstream5
https://bugs.kde.org/show_bug.cgi?id=475582 Bug ID: 475582 Summary: libappstream5 is missing from the repositories - Discover depends on libappstream5 Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ferenos...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After the recent-ish changes to the KDE neon repository, libappstream5 is entirely missing from the repositories, meaning dependencies for Discover can no longer be satisfied currently. STEPS TO REPRODUCE 1. Uninstall libappstream5 if you have it installed 2. Refresh the APT cache 3. Attempt to install libappstream5 OBSERVED RESULT The package is missing EXPECTED RESULT The package installs SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 --- Comment #5 from The Feren OS Dev --- (In reply to The Feren OS Dev from comment #4) > Created attachment 162180 [details] > Bug in effect Weirdly enough, it seems to be inconsistent - race condition perhaps? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 --- Comment #4 from The Feren OS Dev --- Created attachment 162180 --> https://bugs.kde.org/attachment.cgi?id=162180&action=edit Bug in effect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 The Feren OS Dev changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #3 from The Feren OS Dev --- Nevermind, managed to reproduce it on 5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 The Feren OS Dev changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from The Feren OS Dev --- Nevermind, can no longer reproduce on 5.27.8, so given how frequently it happened in 5.27.5 meaning it couldn't have been an unlucky occurrence, I'm gonna assume this was indeed a bug that accidentally got fixed. Still, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 --- Comment #1 from The Feren OS Dev --- Additional note: The parent process of the troubled xsettingsd is systemd. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474795] New: [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications
https://bugs.kde.org/show_bug.cgi?id=474795 Bug ID: 474795 Summary: [X11] xsettingsd's Plasma-started instance has no effect on Flatpak'd GTK applications Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY After logging in, KDE Plasma successfully launches xsettingsd as expected. However, this same instance of xsettingsd appears to do literally nothing to Flatpak applications. Starting xsettingsd by yourself fixes this issue... until the next time you log in with no prior running xsettingsd instances. STEPS TO REPRODUCE 1. Log in 2. See xsettingsd running in System Activity 3. Open a Flatpak'd GTK application like Mozilla Firefox OBSERVED RESULT Those applications use their fallback font, whatever that may be in your context, as one example of the notable consequences of being unaffected. EXPECTED RESULT The outcome of launching xsettingsd manually. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION May be the same bug as https://bugs.kde.org/show_bug.cgi?id=426788, but the issue's too vague to be sure. Will test on KDE neon 5.27.8 in the coming hours. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 471250] KIconLoader ignores the icon set's higher-priority hicolor Inherit and uses Breeze before hicolor
https://bugs.kde.org/show_bug.cgi?id=471250 --- Comment #2 from The Feren OS Dev --- (In reply to Nate Graham from comment #1) > Wanna submit a patch? A patch is on my todo list once I have released Feren OS 2023.11, for sure. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 471250] KIconLoader ignores the icon set's higher-priority hicolor Inherit and uses Breeze before hicolor
https://bugs.kde.org/show_bug.cgi?id=471250 The Feren OS Dev changed: What|Removed |Added Summary|KIconLoader bypasses the|KIconLoader ignores the |icon set's Inherits and |icon set's higher-priority |uses Breeze irregardless|hicolor Inherit and uses ||Breeze before hicolor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 471250] New: KIconLoader bypasses the icon set's Inherits and uses Breeze irregardless
https://bugs.kde.org/show_bug.cgi?id=471250 Bug ID: 471250 Summary: KIconLoader bypasses the icon set's Inherits and uses Breeze irregardless Classification: Frameworks and Libraries Product: frameworks-kiconthemes Version: 5.107.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: ferenos...@outlook.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Rather than respecting the Inherits value of the currently applied icon set, KIconLoader appears to use icons from Breeze before it considers hicolor for icons, which causes side-effects such as icon sets who do not want to theme 3rd-party icons theming 3rd-party icons anyway in KDE Applications and Plasma. STEPS TO REPRODUCE 1. Have an icon set that does not theme certain icons, such as LibreOffice's icons, and give it an Inherits such as Inherits=gnome,hicolor,breeze 2. Apply it OBSERVED RESULT Breeze icons are used for those unthemed icons, instead of hicolor ones EXPECTED RESULT hicolor would theme those icons, while Breeze would only theme icons both hicolor and the test-case icon set lack SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This may be because of the code order seen at https://invent.kde.org/frameworks/kiconthemes/-/blob/master/src/kiconloader.cpp?ref_type=heads#L492 , as well as https://invent.kde.org/frameworks/kiconthemes/-/blob/master/src/kiconloader.cpp?ref_type=heads#L501 If this is the case, I think we should make an exception for if Breeze is not present in the Inherits, or has lower priority than hicolor in Inherits, that gives Breeze lower priority than hicolor as the icon spec might not account for Breeze itself being a fallback in the same vain as hicolor is in this context. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426950] If the WiFi connection temporarily drops host resolution gets stuck and times out until the Networks Plasmoid is opened
https://bugs.kde.org/show_bug.cgi?id=426950 The Feren OS Dev changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from The Feren OS Dev --- Can't say I have encountered this issue anymore in the years since, so, probably best to close this one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424970] If the browser set as Default Browser is uninstalled, preferred://browser entries are left empty
https://bugs.kde.org/show_bug.cgi?id=424970 --- Comment #2 from The Feren OS Dev --- (In reply to Nate Graham from comment #1) > Yeah. Not sure what we could really do about it though. Removing it > automatically wouldn't be very nice. Maybe we could fall back to the > next-most-preferred browser? Or just the next one in alphabetical order? Next most preferred browser would be best, if that's possible, but if not, alphabetical order would definitely work too, I would think. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467685] cupsDoAuthentication() immediately fails without prompting a password
https://bugs.kde.org/show_bug.cgi?id=467685 The Feren OS Dev changed: What|Removed |Added Summary|CupsDoAuthentication|cupsDoAuthentication() |immediately fails without |immediately fails without |prompting a password|prompting a password -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467685] New: CupsDoAuthentication immediately fails without prompting a password
https://bugs.kde.org/show_bug.cgi?id=467685 Bug ID: 467685 Summary: CupsDoAuthentication immediately fails without prompting a password Classification: Applications Product: systemsettings Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY If you attempt to open the Add a Printer dialog on a user account that is not in the group 'lpadmin', it will instantly fail to find printers with the error 'Forbidden'. STEPS TO REPRODUCE 1. Add a user 2. Make sure that user does NOT have lpadmin 3. 'Add a Printer' OBSERVED RESULT A password dialog will show to elevate its privileges for the next steps EXPECTED RESULT Terminal output: libkcups: CUPS-Get-Devices last error: 1025 Forbidden libkcups: Calling cupsDoAuthentication() password_retries: 0 libkcups: Called cupsDoAuthentication(), success: false (nothing prompted for authentication) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27 (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This bug also affects Kubuntu 22.04 LTS. All other Desktop Environments scan printers without an error without lpadmin, including system-config-printer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425564] SEGFAULT occurs in plasma when a certificate is untrusted
https://bugs.kde.org/show_bug.cgi?id=425564 --- Comment #3 from The Feren OS Dev --- Created attachment 155208 --> https://bugs.kde.org/attachment.cgi?id=155208&action=edit New crash information added by DrKonqi plasmashell (5.25.5) using Qt 5.15.6 Whenever Weather refreshes on a connection with an 'untrusted certificate' the certificate dialog appears, but most of the time Plasma crashes, taking the dialog with it, before the dialog can even render a window body, and in times it can be used to accept a certificate Plasma crashes anyway once you hit Forever and never appears to actually save your choice of Forever Trust Certificate. There again the latter may be a separate bug with Weather trying to read the wifi's network sign in page as, well, weather information, and so possibly crashing from trying? -- Backtrace (Reduced): #3 0x7ff0e113fda4 in QTextDocument::docHandle() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #4 0x7ff0e1137f8c in QTextFrame::begin() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 [...] #7 0x7ff0e117e898 in QTextDocumentLayout::doLayout(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7ff0e117fd8b in QTextDocumentLayout::documentChanged(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7ff0e1155b78 in QTextDocumentPrivate::clear() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425564] SEGFAULT occurs in plasma when a certificate is untrusted
https://bugs.kde.org/show_bug.cgi?id=425564 --- Comment #2 from The Feren OS Dev --- Created attachment 154162 --> https://bugs.kde.org/attachment.cgi?id=154162&action=edit New crash information added by DrKonqi plasmashell (5.25.5) using Qt 5.15.6 When signed out of our college's network, the certificate becomes untrusted. Unlike Dr Konqi and co., Plasma always crashes when its certificate accepting dialog appears, whereas Dr Konqi only crashes sometimes and when it does it's only after accepting or revoking the certificate. -- Backtrace (Reduced): #3 0x7fa53018bda4 in QTextDocument::docHandle() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #4 0x7fa530183f8c in QTextFrame::begin() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 [...] #7 0x7fa5301ca898 in QTextDocumentLayout::doLayout(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7fa5301cbd8b in QTextDocumentLayout::documentChanged(int, int, int) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fa5301a1b78 in QTextDocumentPrivate::clear() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425564] SEGFAULT occurs in plasma when a certificate is untrusted
https://bugs.kde.org/show_bug.cgi?id=425564 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 462217] New: KRunner crashes if the current LookAndFeelPackage doesn't exist
https://bugs.kde.org/show_bug.cgi?id=462217 Bug ID: 462217 Summary: KRunner crashes if the current LookAndFeelPackage doesn't exist Classification: Plasma Product: krunner Version: 5.25.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: alexander.loh...@gmx.de Target Milestone: --- Application: krunner (5.25.5) (Compiled from sources) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.4.0-132-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.25.5 [CoredumpBackend] -- Information about the crash: KRunner crashes if kdeglobals's KDE/LookAndFeelPackage value is set to the ID of a Global Theme that doesn't actually exist. Setting it to one that does exist immediately fixes the crashes, and while in the non-existent-Global-Theme state restarting KRunner from DrKonqi can yield the same bug that was reported in bug report 447113 on the rare occassion. ksplashqml also crashes if its theme value in ksplashrc is set to a non-existent Global Theme ID, too, just for an additional note. The crash can be reproduced every time. -- Backtrace: Application: KRunner (krunner), signal: Segmentation fault [New LWP 16845] [New LWP 16848] [New LWP 16850] [New LWP 16853] [New LWP 16851] [New LWP 16855] [New LWP 16857] [New LWP 16854] [New LWP 16846] [New LWP 16852] [New LWP 16849] [New LWP 16856] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/krunner'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI___sigprocmask (how=1, set=, oset=0x0) at ../sysdeps/unix/sysv/linux/sigprocmask.c:39 [Current thread is 1 (Thread 0x7fe0d153c9c0 (LWP 16845))] __preamble__ [Current thread is 1 (Thread 0x7fe0d153c9c0 (LWP 16845))] Thread 12 (Thread 0x7fe0c4ff9700 (LWP 16856)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556fc2bf66c8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556fc2bf6678, cond=0x556fc2bf66a0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556fc2bf66a0, mutex=0x556fc2bf6678) at pthread_cond_wait.c:647 #3 0x7fe0cd5a85eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fe0cd5a81eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fe0d5361609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fe0d58ec133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fe0ccad0700 (LWP 16849)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556fc2c20c48) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556fc2c20bf8, cond=0x556fc2c20c20) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556fc2c20c20, mutex=0x556fc2c20bf8) at pthread_cond_wait.c:647 #3 0x7fe0cdc9407b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fe0cdc93edb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fe0d5361609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fe0d58ec133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fe0c6ffd700 (LWP 16852)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556fc2c2b5c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556fc2c2b570, cond=0x556fc2c2b598) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556fc2c2b598, mutex=0x556fc2c2b570) at pthread_cond_wait.c:647 #3 0x7fe0cdc9118b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fe0cdc9110b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fe0d5361609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fe0d58ec133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fe0d0744700 (LWP 16846)): #0 0x7fe0d58df99f in __GI___poll (fds=0x7fe0c80053c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe0d40ba36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe0d40ba4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe0d5eb0b6b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe0d5e54b0b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe0d5c6e342 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe0d6114f4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe0d5c6f543 in ?? () from /usr/lib/
[plasmashell] [Bug 457498] New: There is no way to set Floating and Adaptive Transparency in Desktop Scripting for Global Theme Layouts
https://bugs.kde.org/show_bug.cgi?id=457498 Bug ID: 457498 Summary: There is no way to set Floating and Adaptive Transparency in Desktop Scripting for Global Theme Layouts Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Basically, the panel scripting thingy documented at https://userbase.kde.org/Plasma/How_to_create_a_Unity-like_look_and_feel_theme_using_Plasma%E2%80%99s_Desktop_Scripting_API has 0 way right now to give a newly birthed panel the Floating attribute, nor any of the non-default Adaptive Transparency values, despite everything I've tried (likely because of its positioning of the configs in plasmashellrc instead of plasma-org.kde.plasma.desktop-appletsrc). Even Global Theme Explorer's layout saver cannot save those attributes on panels. STEPS TO REPRODUCE 1. N/A OBSERVED RESULT The inability to pre-set floating or solid/transparent adaptive transparency options in panels in Desktop Layouts EXPECTED RESULT The ability to pre-set floating or solid/transparent adaptive transparency options in panels in Desktop Layouts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.25 (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Two fixes I can think of are: Either move the configuration over to the plasma-...-appletsrc file instead of plasmashellrc, or allow scripting to change the values, for newly created panels we store as variables in our desktop-generation script, in plasmashellrc as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457282] New: KDE Plasma crashes when changing the Desktop Layout
https://bugs.kde.org/show_bug.cgi?id=457282 Bug ID: 457282 Summary: KDE Plasma crashes when changing the Desktop Layout Product: plasmashell Version: 5.25.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.3) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.17.5-76051705-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Every time the Desktop Layout is changed, KDE Plasma crashes twice. It only started happening in 5.25. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [New LWP 24946] [New LWP 24949] [New LWP 24991] [New LWP 25043] [New LWP 25044] [New LWP 25046] [New LWP 25047] [New LWP 25048] [New LWP 25049] [New LWP 25050] [New LWP 25051] [New LWP 25052] [New LWP 25053] [New LWP 25054] [New LWP 25055] [New LWP 25056] [New LWP 25057] [New LWP 25058] [New LWP 25059] [New LWP 25060] [New LWP 25061] [New LWP 25062] [New LWP 25311] [New LWP 25359] [New LWP 25365] [New LWP 25366] [New LWP 25504] [New LWP 25505] [New LWP 25506] [New LWP 25507] [New LWP 25508] [New LWP 25509] [New LWP 25510] [New LWP 25511] [New LWP 25512] [New LWP 25513] [New LWP 25514] [New LWP 25515] [New LWP 25516] [New LWP 25517] [New LWP 25518] [New LWP 25519] [New LWP 25520] [New LWP 25521] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7c0038f99f in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7f7bfc4ba9c0 (LWP 24933))] Thread 45 (Thread 0x7f7b18bf9700 (LWP 25521)): #0 0x7f7c000b9376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c007255fb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c023bf2f4 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f7c023bf769 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 44 (Thread 0x7f7b193fa700 (LWP 25520)): #0 0x7f7c000b9376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7bea4385eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f7bea4381eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 43 (Thread 0x7f7b19bfb700 (LWP 25519)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 42 (Thread 0x7f7b1a3fc700 (LWP 25518)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 41 (Thread 0x7f7b1abfd700 (LWP 25517)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7c00722aa1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7c0071f553 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7c000b2609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f7c0039c133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 40 (Thread 0x7f7b517fa700 (LWP 25516)): #0 0x7f7c000b97d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f7c00725588 in QWaitCondition::wait(QMutex*, QD
[systemsettings] [Bug 456487] Color Schemes' inactive titlebars are now always tinted with the accent color even when the rest of the window is not tinted with the accent color
https://bugs.kde.org/show_bug.cgi?id=456487 The Feren OS Dev changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from The Feren OS Dev --- Turns out this was fixed in .3 by https://invent.kde.org/plasma/plasma-workspace/-/commit/00a18a8c5aeb6c0b4e2b157dec11e4e1032d20cd, thus this is now RESOLVED. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456487] (Regression) Color Schemes' inactive titlebars are now tinted with the accent colour when they're set to not do so
https://bugs.kde.org/show_bug.cgi?id=456487 --- Comment #2 from The Feren OS Dev --- (In reply to Nate Graham from comment #1) > Based on the code, I see that this is intentional, and the option to not > tint inactive titlebars was removed from Plasma 5.26. > > I don't see a visual problem in the screenshot; can you explain it? Basically, some themes are designed where the titlebar becomes the background of the toolbar below it when inactive, to better emphasise that they're inactive windows (and increase contrast between active and inactive windows). Suffice to say, with tinting on them like that, it can also look rather off-putting (given the lack of tinting right below it, as if it's an unintentional change the colour scheme's designer did not expect), and adds overall design inconsistency with how the titlebar looks if the user isn't using accent colours whatsoever (given the aforementioned theme design). Sure, the minor tinting is a good idea for inactive windows, but the option being there initially was ultimately done to avoid the aforementioned design situation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456487] New: (Regression) Color Schemes' inactive titlebars are now tinted with the accent colour when they're set to not do so
https://bugs.kde.org/show_bug.cgi?id=456487 Bug ID: 456487 Summary: (Regression) Color Schemes' inactive titlebars are now tinted with the accent colour when they're set to not do so Product: systemsettings Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY Colour Schemes that have Apply Accent To Inactive Titlebars turned OFF still get inactive titlebars tinted even though they're not configured to tint at all, and literally have the option for colour overriding in inactive titlebars off. Suffice to say, this leads to undesirable results like this: https://i.imgur.com/eKohgym.png (while the screenshot was taken from a modded Colors KCM, I've also reproduced it in KDE neon without modifications) STEPS TO REPRODUCE 1. Edit a Colour Scheme to have active titlebar colouring on, inactive titlebar colouring off, and tinting completely off 2. Save the changes 3. Apply your new colour scheme 3.alt: Alternatively, just apply Breeze Classic OBSERVED RESULT Inactive titlebars are tinted EXPECTED RESULT Inactive titlebars are left unmodified from how they are in the colour scheme itself SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.25.2 (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455142] Tinted color scheme applies wrong color to titlebars
https://bugs.kde.org/show_bug.cgi?id=455142 The Feren OS Dev changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #3 from The Feren OS Dev --- *** Bug 455537 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455537] Header colour doesn't properly update when using wallpaper accent and changing the wallpaper
https://bugs.kde.org/show_bug.cgi?id=455537 The Feren OS Dev changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ferenos...@outlook.com --- Comment #1 from The Feren OS Dev --- *** This bug has been marked as a duplicate of bug 455142 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 452961] New: fuse3 no longer Provides fuse
https://bugs.kde.org/show_bug.cgi?id=452961 Bug ID: 452961 Summary: fuse3 no longer Provides fuse Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ferenos...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY The fuse3 package in KDE neon no longer provides the package 'fuse', which can cause some KDE components to get uninstalled in a system update using apt, among other potential issues from the sudden loss of 'fuse' providing by fuse3. STEPS TO REPRODUCE 1. Update your system using apt, I suppose OBSERVED RESULT In my cases, it ended up uninstalling these items as a result of the fuse3 upgrade: kdeconnect:amd64 (21.12.3-0xneon+20.04+focal+release+build36), ntfs-3g:amd64 (1:2017.3.23AR.3-3ubuntu1.1), gvfs-fuse:amd64 (1.44.1-1ubuntu1), python3-fuse:amd64 (2:1.0.0-3build1), exfat-fuse:amd64 (1.3.0-1), sshfs:amd64 (3.6.0+repack+really2.10-0ubuntu1) EXPECTED RESULT APT wouldn't end up uninstalling those packages SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 KNOWN FIX You can fix this by re-adding the "Provides: fuse" line in fuse3's DEBIAN control file, as was already present beforehand in the Ubuntu repositories version of the package. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451864] Plasma 5.24.3 crashes whenever changing the Desktop Layout most of the time
https://bugs.kde.org/show_bug.cgi?id=451864
--- Comment #2 from The Feren OS Dev ---
Additionally, the diff for the panelspacer.cpp crash fix:
diff --git a/applets/panelspacer/plugin/panelspacer.cpp
b/applets/panelspacer/plugin/panelspacer.cpp
index 0753815f40..66c56781db 100644
--- a/applets/panelspacer/plugin/panelspacer.cpp
+++ b/applets/panelspacer/plugin/panelspacer.cpp
@@ -123,6 +123,7 @@ PlasmaQuick::AppletQuickItem *PanelSpacer::twinSpacer()
const
PlasmaQuick::AppletQuickItem *PanelSpacer::containmentGraphicObject() const
{
+if (!containment()) return nullptr;
return
containment()->property("_plasma_graphicObject").value();
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 451864] Plasma 5.24.3 crashes whenever changing the Desktop Layout most of the time
https://bugs.kde.org/show_bug.cgi?id=451864 --- Comment #1 from The Feren OS Dev --- Extra note: Aside the ones compiled from source, KDE neon User Edition packages are used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451864] New: Plasma 5.24.3 crashes whenever changing the Desktop Layout most of the time
https://bugs.kde.org/show_bug.cgi?id=451864 Bug ID: 451864 Summary: Plasma 5.24.3 crashes whenever changing the Desktop Layout most of the time Product: plasmashell Version: 5.24.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.3) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.13.0-37-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.24.3 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: Changing the Desktop Layout. It doesn't happen all the time, but most of the time the Desktop Layout is changed. A similar crash occurs with panelspacer.cpp, but a single line addition from another KDE Developer fixed panelspacer.cpp's crash-causing, now leaving systemtray.cpp, and rarely shell instead, to be the one causing the crashes instead. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 77439] [New LWP 77560] [New LWP 77562] [New LWP 77443] [New LWP 77444] [New LWP 77449] [New LWP 77482] [New LWP 77460] [New LWP 77561] [New LWP 77442] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9c930b403b in raise () from /lib/x86_64-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x7f9c8f2cf9c0 (LWP 77439))] __preamble__ [Current thread is 1 (Thread 0x7f9c8f2cf9c0 (LWP 77439))] Thread 10 (Thread 0x7f9c8e25a700 (LWP 77442)): #0 0x7f9c931839cf in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9c958b6c1a in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9c958b890a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9c8e9761a8 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f9c93513623 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9c92ea7609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f9c93190163 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7f9c6927f700 (LWP 77561)): #0 0x7f9c92eae7b1 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f9c93519618 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9c93516b21 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9c93513623 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9c92ea7609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7f9c93190163 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7f9c6bf08700 (LWP 77460)): #0 0x7f9c931839cf in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9c91a1836e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9c91a184a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9c93754642 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9c936f887b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9c93512442 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9c950d343a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f9c93513623 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9c92ea7609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f9c93190163 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f9c62ffd700 (LWP 77482)): #0 0x7f9c931839cf in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9c91a1836e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9c91a184a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9c9375465b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9c936f887b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9c93512442 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9c608e707c in KCupsConnection::run() () at /lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f9c93513623 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9c92ea7609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f9c93190163 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f9c86474700 (LWP 77449)): #0 0x7f9c931839cf in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9c9
[plasmashell] [Bug 451451] KDE Plasma Adaptive Transparency overrides the no-Compositor styling
https://bugs.kde.org/show_bug.cgi?id=451451 The Feren OS Dev changed: What|Removed |Added Summary|KDE Plasma Adaptive |KDE Plasma Adaptive |Transparency overrides the |Transparency overrides the |no-Compositor panel styling |no-Compositor styling -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451451] New: KDE Plasma Adaptive Transparency overrides the no-Compositor panel styling
https://bugs.kde.org/show_bug.cgi?id=451451 Bug ID: 451451 Summary: KDE Plasma Adaptive Transparency overrides the no-Compositor panel styling Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: 1.0 SUMMARY The panel styling for Adaptive Transparency overrides the 'opaque' panel styling Plasma is meant to use when there's no compositor, making the compositorless panel in KDE Plasma use the 'solid' styling when a window is maximised, which to put it simply IS NOT meant to occur at all as 'solid' IS NOT meant for use without a compositor by design. STEPS TO REPRODUCE 1. Turn on Adaptive Transparency 2. Turn off the Compositor 3. Maximise a window OBSERVED RESULT 'solid' styling is used. EXPECTED RESULT 'opaque' styling stays used. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon Developer Edition Unstable 5.24.80 (available in About System) KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION You can easily check this bug using this theme: https://github.com/feren-OS/feren-theme/tree/work/2022-redesign/plasma/feren-coloured (may be broken unless you also put https://github.com/feren-OS/feren-theme/tree/work/2022-redesign/plasma/feren in the same folder) (the theme has a grey 'opaque' panel, but otherwise uses a darkened version of the colour scheme's Selected Background for the panels' colour - just panels for now, though, as menus are to be done - irregardless you can easily see the bug with this theme) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450162] New: Switching pages in System Settings during the period it's frozen in when changing Global Themes causes it to crash
https://bugs.kde.org/show_bug.cgi?id=450162 Bug ID: 450162 Summary: Switching pages in System Settings during the period it's frozen in when changing Global Themes causes it to crash Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: --- Application: systemsettings (5.24.80) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.24.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: Click another page of System Settings, during the brief period System Settings is frozen, while a Global Theme is being applied, such as the Colours page. I suspect SySe tries to do a finishing task for kcm_globaltheme while the KCM is no longer kcm_globaltheme due to working on switching pages at the same time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [New LWP 8546] [New LWP 8554] [New LWP 8562] [New LWP 8563] [New LWP 8740] [New LWP 8555] [New LWP 8556] [New LWP 8557] [New LWP 8558] [New LWP 8559] [New LWP 8739] [New LWP 8793] [New LWP 8553] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/systemsettings'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7ff7253079c0 (LWP 8546))] __preamble__ [Current thread is 1 (Thread 0x7ff7253079c0 (LWP 8546))] Thread 13 (Thread 0x7ff72450e700 (LWP 8553)): #0 0x7ff729bd5aff in __GI___poll (fds=0x7ff72450dae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff728623c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff72862590a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff724c50f98 in QXcbEventQueue::run (this=0x56541e8dace0) at qxcbeventqueue.cpp:228 #4 0x7ff729f64543 in QThreadPrivate::start (arg=0x56541e8dace0) at thread/qthread_unix.cpp:331 #5 0x7ff7285dc609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff729be2293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7ff6eb94a700 (LWP 8793)): #0 0x7ff729bd5aff in __GI___poll (fds=0x7ff6e02f3470, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff727c1e36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff727c1e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff72a1a59f2 in QEventDispatcherGlib::processEvents (this=0x7ff6e03bd0e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7ff72a149c9b in QEventLoop::exec (this=this@entry=0x7ff6eb949bc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7ff729f63362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7ff728bb8569 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7ff729f64543 in QThreadPrivate::start (arg=0x565420f34fb0) at thread/qthread_unix.cpp:331 #8 0x7ff7285dc609 in start_thread (arg=) at pthread_create.c:477 #9 0x7ff729be2293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7ff718f48700 (LWP 8739)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7ff718f47b50, clockid=, expected=0, futex_word=0x56541ebcce90) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7ff718f47b50, clockid=, mutex=0x56541ebcce40, cond=0x56541ebcce68) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x56541ebcce68, mutex=0x56541ebcce40, abstime=0x7ff718f47b50) at pthread_cond_wait.c:656 #3 0x7ff729f6a668 in QWaitConditionPrivate::wait_relative (this=0x56541ebcce40, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x56541ebcce40) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x56541ebcf040, mutex=mutex@entry=0x56541ebd5e38, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7ff729f67b71 in QThreadPoolThread::run (this=0x56541ebcf030) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7ff729f64543 in QThreadPrivate::start (arg=0x56541ebcf030) at thread/qthread_unix.cpp:331 #8 0x7ff7285dc609 in start_thread (arg=) at pthread_create.c:477 #9 0x7ff729be2293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0
[lattedock] [Bug 446249] [feature] - improve "--import-layout" functionality
https://bugs.kde.org/show_bug.cgi?id=446249 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #2 from The Feren OS Dev --- What needs to happen is this: - Command line argument is left as it usually is, BUT... - Whenever Latte is already running, and said command line argument is used on a new instance, instead of launching Latte Settings it needs to send the DBus signal to the proper Latte instance to make it switch the layout to the .layout.latte file's one. Once that's done, Global Theme applying a Latte layout can just call the command via already identified means (via the Feren OS patch linked prior) to switch the layout reliably. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442339] New: A cursor with a fixed size disables the whole footer
https://bugs.kde.org/show_bug.cgi?id=442339 Bug ID: 442339 Summary: A cursor with a fixed size disables the whole footer Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: --- Created attachment 141491 --> https://bugs.kde.org/attachment.cgi?id=141491&action=edit Disabled footer SUMMARY A cursor theme with only 1 size entirely disables the footer, instead of the dropdown itself. STEPS TO REPRODUCE 1. Go into Get New Cursors 2. Get a cursor like Burning Super Death Sword (https://www.pling.com/p/1309303) 3. Select the BURNING SUPER DEATH SWORD OBSERVED RESULT The whole footer is made insensitive/disabled, thus meaning Cursor Management becomes inaccessible. EXPECTED RESULT Only the dropdown would be disabled. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Feren OS (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I guess someone routed the disabling code to the wrong piece of the QML file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435706] Allow applications to draw content in the KWin titlebar
https://bugs.kde.org/show_bug.cgi?id=435706 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #1 from The Feren OS Dev --- A person from KDE has already expressed a similar idea: https://kver.wordpress.com/2014/10/25/presenting-dwd-a-candidate-for-kde-window-decorations/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435425] New: Plasma Style checkboxes get messed up if the toolbutton styling in the Plasma Style involves solid backgrounds
https://bugs.kde.org/show_bug.cgi?id=435425 Bug ID: 435425 Summary: Plasma Style checkboxes get messed up if the toolbutton styling in the Plasma Style involves solid backgrounds Product: plasmashell Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Suffice to say, if the 'toolbutton' styling in a Plasma Style involves a solid hover look, when hovering over checkboxes or if checkboxes are focused, the solid toolbutton styling wrongly overlays the checkbox. STEPS TO REPRODUCE 1. Make a Plasma Style with a toolbutton hover style that is opaque/solid in appearance 2. Apply the Plasma Style 3. Hover or focus on a checkbox OBSERVED RESULT Toolbutton styling is applied, which completely conceals the checkbox EXPECTED RESULT Toolbutton styling isn't applied so as to not conceal the checkbox SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.2 (first seen in 5.20.0) (available in About System) KDE Plasma Version: 5.21.2 (first seen in 5.20.0) KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Plasma Styles like Feren OS's employ a solid toolbutton hover style to be consistent with the hovered appearance of toolbuttons in the Feren OS Application Style. Toolbuttons refer to buttons with a background-less appearance on their normal states, and the 'toolbutton' element in Plasma Styles. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo content indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #10 from The Feren OS Dev --- ...and in Dolphin, searching 'hosts' in / produces NOTHING as before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo content indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #9 from The Feren OS Dev --- I'm also getting weird behaviour in /, though, despite this: dominich@dominic-80e5:~/Downloads$ cd / dominich@dominic-80e5:/$ baloosearch hosts /home/dominich/Games/sonic-3-angel-island-revisited/drive_c/windows/system32/drivers/etc/hosts /home/dominich/Games/fortnite/drive_c/windows/system32/drivers/etc/hosts /home/dominich/Games/epic-games-store/drive_c/windows/system32/drivers/etc/hosts Elapsed: 1.82707 msecs dominich@dominic-80e5:/$ ls /etc/host* /etc/host.conf /etc/hostname /etc/hosts /etc/hosts.allow /etc/hosts.deny -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo content indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #8 from The Feren OS Dev --- ...and now Dolphin search works, too... weird. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo content indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #7 from The Feren OS Dev --- Update: Upon now changing directory to the Downloads folder, I get this: dominich@dominic-80e5:~/Downloads$ baloosearch adwaitrecolour /home/dominich/Downloads/adwaitrecolour /home/dominich/adwaitrecolour Elapsed: 4.25353 msecs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo content indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 The Feren OS Dev changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from The Feren OS Dev --- dominich@dominic-80e5:~$ baloosearch adwaitrecolour Elapsed: 0.449031 msecs dominich@dominic-80e5:~$ ls ~/Downloads/adwait* /home/dominich/Downloads/adwaitrecolour -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434809] Switched Global Theme
https://bugs.kde.org/show_bug.cgi?id=434809 --- Comment #4 from The Feren OS Dev --- For the record, the latest ISO has 5.21.2 already if you ever want to check it for whatever reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434809] Switched Global Theme
https://bugs.kde.org/show_bug.cgi?id=434809 --- Comment #2 from The Feren OS Dev --- (In reply to Nate Graham from comment #1) > Trying to destroy an immutable applet: > > #4 Plasma::Applet::immutability (this=0x0) at > /home/dominic/git-stuff/5.21.2/plasma-framework-patching/src/plasma/applet. > cpp:477 > #5 0x7fc69387c69d in Plasma::Applet::destroy (this=0x0) at > /home/dominic/git-stuff/5.21.2/plasma-framework-patching/src/plasma/applet. > cpp:289 > > > Do you have any custom patches applied? They're over at https://github.com/feren-OS/plasma-workspace-patching/tree/Plasma/5.21 and https://github.com/feren-OS/plasma-framework-patching respectively. Weird... never seen it crash in 5.21.2 patch compiles besides the usual crash from immediately opening a different KCM while it's applying the Global Theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434447] Kickoff Favourites (and potentially other menus) omit preferred://filemanager
https://bugs.kde.org/show_bug.cgi?id=434447 --- Comment #2 from The Feren OS Dev --- (In reply to Nate Graham from comment #1) > Yeah I think only the Task Manager can handle these. Weird, given it can handle preferred://browser just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434447] New: Kickoff Favourites (and potentially other menus) omit preferred://filemanager
https://bugs.kde.org/show_bug.cgi?id=434447 Bug ID: 434447 Summary: Kickoff Favourites (and potentially other menus) omit preferred://filemanager Product: plasmashell Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Simply put, having preferred://filemanager as a Kickoff favourite... causes it to not show up in Favourites. STEPS TO REPRODUCE 1. Manually add preferred://filemanager somehow to Kickoff's favourites via configuration changing 2. Open Kickoff with those changes set OBSERVED RESULT preferred://filemanager isn't displayed there EXPECTED RESULT The default file manager displays in Favourites SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.2 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 205866] wobbly window's advanced configuration allows windows to be to wobbly
https://bugs.kde.org/show_bug.cgi?id=205866 --- Comment #9 from The Feren OS Dev --- no offence by the way, I just found this earlier because someone else showed me it... fair enough for closing it the way you did... it's just... this 'feature' is... something. Probably should be reopened though for its potential epilepsy problems due to the flashing that can occur. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434417] Forcing all Plasma windows to be the maximum possible size KWin allows causes CPU and memory leaking
https://bugs.kde.org/show_bug.cgi?id=434417 --- Comment #1 from The Feren OS Dev --- For context: I used Menu -> More Options -> Configure Special Window Settings... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 205866] wobbly window's advanced configuration allows windows to be to wobbly
https://bugs.kde.org/show_bug.cgi?id=205866 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #8 from The Feren OS Dev --- This was marked as INTENTIONAL? LMAO -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434417] New: Forcing all Plasma windows to be the maximum possible size KWin allows causes CPU and memory leaking
https://bugs.kde.org/show_bug.cgi?id=434417 Bug ID: 434417 Summary: Forcing all Plasma windows to be the maximum possible size KWin allows causes CPU and memory leaking Product: plasmashell Version: 5.21.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I decided for a laugh to try a suggestion by an internet friend that tried to make Kickoff be at a maximum size, and due to this I found out something interesting: If you make a window rule from a pinned Plasma Plasmoid popup's window menu for Plasma, with the window set to all types of window, and the only rule being Force size at the maximum possible value it allows in both width and height, and then save... well, looking at top it seems to max out CPUs and eat A LOT of RAM. STEPS TO REPRODUCE 1. Trigger the window menu via the menu hotkey on a pinned Plasmoid popup (a non-pinned one will cause the menu to immediately close with the popup itself) 2. Make a rule for that window 3. Set the window types to match to be ALL the window types 4. Add the Size effect 5. Set the effect to Force 6. Set the values it forces to to the maximum values (quick way is typing 9) 7. Save OBSERVED RESULT The RAM usage and CPU usage skyrockets because of plasmashell, and eventually the DE dies because of Linux freaking out, probably, since both resource types are being used uncontrollably. EXPECTED RESULT The DE wouldn't 'leak' those resources when trying to cope with this...? That or KWin wouldn't even allow this to be possible to begin with. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.2 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION bruh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 The Feren OS Dev changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/com ||mit/1b9b03529b5f1da1872b07d ||18a0daf7230899fbf Version Fixed In||5.81 --- Comment #6 from The Feren OS Dev --- Git commit 1b9b03529b5f1da1872b07d18a0daf7230899fbf by Dominic Hayes. Committed on 11/03/2021 at 20:34. Pushed by ngraham into branch 'master'. Change ContrastEffect check to AdaptiveTransparency in A.T. check Fix Contrastless Plasma Styles not being able to use Adaptive Transparency by changing the check, for ContrastEffect being enabled in the Plasma Style to instead check if AdaptiveTransparency is enabled in the Plasma Style, for determining if Adaptive Transparency should be available. FIXED-IN: 5.81 M +1-1src/plasma/private/theme_p.cpp https://invent.kde.org/frameworks/plasma-framework/commit/1b9b03529b5f1da1872b07d18a0daf7230899fbf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434233] Margins don't get recognised on 'opaque' panels (no compositor)
https://bugs.kde.org/show_bug.cgi?id=434233 The Feren OS Dev changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from The Feren OS Dev --- *** This bug has been marked as a duplicate of bug 430622 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430622] Panel applet margins are bigger with compositing turned on than with it turned off
https://bugs.kde.org/show_bug.cgi?id=430622 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #21 from The Feren OS Dev --- *** Bug 434233 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434233] Margins don't get recognised on 'opaque' panels (no compositor)
https://bugs.kde.org/show_bug.cgi?id=434233 --- Comment #2 from The Feren OS Dev --- I just realised this is literally 430622 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 The Feren OS Dev changed: What|Removed |Added Assignee|niccolo.venera...@gmail.com |ferenos...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 --- Comment #5 from The Feren OS Dev --- Fixed it with https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/212 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 --- Comment #3 from The Feren OS Dev --- ...'sides, themes like the Plasma Style Feren OS uses don't have contrast on but still are opaque enough by design to give decent contrast. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 --- Comment #2 from The Feren OS Dev --- (In reply to Marco Martin from comment #1) > It's kinda intentional, the very translucent backgrounds need blur contrast > to be used at all (that's since plasma 5.0, is just more obvious now) > > the rationale is a conscious decision on ensuring that popup contents are > actually readable Wouldn't be that sure, for this use-case, since Adaptive Transparency, well, makes stuff opaque. Not allowing it when contrast is off does the complete opposite of your rationale when a window's maximised. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434233] New: Margins don't get recognised on 'opaque' panels (no compositor)
https://bugs.kde.org/show_bug.cgi?id=434233 Bug ID: 434233 Summary: Margins don't get recognised on 'opaque' panels (no compositor) Product: plasmashell Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: 1.0 SUMMARY The margins in the opaque panel-background.svgz get entirely ignored, as if they don't even exist, in compositor-less opaque panel mode. STEPS TO REPRODUCE 1. Add a margin separator to show margins being recognised 2. Turn off the compositor 3. Check the margins again OBSERVED RESULT Margins are gone now EXPECTED RESULT Margins would remain intact SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.2 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434202] Adaptive panel opacity feature in Frameworks 5.80 changes looks of Plasma 5.21 without a way to adjust
https://bugs.kde.org/show_bug.cgi?id=434202 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #3 from The Feren OS Dev --- Not bug janitor found a merge request that might be related ;) https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/211 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 The Feren OS Dev changed: What|Removed |Added Assignee|visual-des...@kde.org |niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434200] New: Contrastless Breeze can't use Adaptive Transparency
https://bugs.kde.org/show_bug.cgi?id=434200 Bug ID: 434200 Summary: Contrastless Breeze can't use Adaptive Transparency Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY You can't, for some reason, use Adaptive Transparency in Plasma Styles like Breeze if you turn their ContrastEffect value off in their metadata. Having ContrastEffect on makes it work however. STEPS TO REPRODUCE 1. Edit /usr/share/plasma/desktoptheme/default/metadata.desktop to disable ContrastEffect 2. Ensure AdaptiveTransparency is on 3. Apply the Style again and maximise a window OBSERVED RESULT Adaptive Transparency... doesn't appear to work. EXPECTED RESULT Adaptive Transparency would make the panel opaque irregardless. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.2 (available in About System) KDE Plasma Version: 5.21.2 (I compiled it with the Adaptive Transparency patches from master) KDE Frameworks Version: 5.79.0 (again, compiled Plasma Framework with Adaptive Transparency patch from master) Qt Version: 5.15.2 ADDITIONAL INFORMATION Yeah, it's actually technically stable Plasma, although I compiled it WITH all the commits relating to Adaptive Transparency that niccolove linked me, and the extra commit in Plasma Workspace that wasn't by niccolove relating to said feature. I didn't know what to therefore count the version as to prevent confusion so I just marked it as 'master' since it's a feature from master. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo Indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #2 from The Feren OS Dev --- Created attachment 136420 --> https://bugs.kde.org/attachment.cgi?id=136420&action=edit Baloo KCM -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] New: If Baloo Indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 Bug ID: 433967 Summary: If Baloo Indexing is disabled, but Baloo is enabled, searches immediately return 0 results Product: dolphin Version: 20.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: ferenos...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If you turn off Baloo File Indexing overall, but keep Baloo enabled, and then search for files in Dolphin it'll immediately finish with 0 results, irregardless of if there's actual files to find that match your query. STEPS TO REPRODUCE 1. Turn off indexing file content and folder-specific indexing in File Search KCM 2. Keep Baloo itself enabled 3. Apply, and perform a search in Dolphin OBSERVED RESULT Search immediately finishes with 0 results EXPECTED RESULT Search would continue using the filename search service if not Baloo searching by filenames. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Turning off Baloo entirely makes search work by using the other engine for searches. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433333] [systemd] Enabling systemdBoot breaks 'startkde'
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #7 from The Feren OS Dev --- (In reply to David Edmundson from comment #5) > Can I see your ~/.config/startkderc please? There is none, nor is there one in /etc/xdg and co. Upon applying the setting, this is local startkderc: [General] systemdBoot=true -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433333] [systemd] Enabling systemdBoot breaks 'startkde'
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #4 from The Feren OS Dev --- Error: org.freedesktop.systemd1.NoSuchUnit Unit xdg-desktop-autostart.target not found. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433333] [systemd] Enabling systemdBoot breaks 'startkde'
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #2 from The Feren OS Dev --- Created attachment 135981 --> https://bugs.kde.org/attachment.cgi?id=135981&action=edit journalctl --user -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433333] New: Enabling systemdBoot breaks 'startkde'
https://bugs.kde.org/show_bug.cgi?id=43 Bug ID: 43 Summary: Enabling systemdBoot breaks 'startkde' Product: plasmashell Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: 1.0 Created attachment 135977 --> https://bugs.kde.org/attachment.cgi?id=135977&action=edit xsession-errors SUMMARY Enabling systemdBoot via 'kwriteconfig5 --file startkderc --group General --key systemdBoot true' completely breaks startplasma-x11 with a 'startkde' error occuring every time you log in from that point onwards until you disable systemdBoot. STEPS TO REPRODUCE 1. Run 'writeconfig5 --file startkderc --group General --key systemdBoot true' 2. Log out 3. Log in again OBSERVED RESULT startkde: Could not start Plasma session. appears in an X11 dialog, closing that logs you out. KWin and co. don't start. EXPECTED RESULT The Desktop works fine. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.0 (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION No useful information in the .xsession-errors file, except for the message in the X11 dialog. Running it via manual startx /usr/bin/startplasma-x11 causes it to yield the same 'startkde: Starting up...' and 'startkde: Could not start Plasma session.' output as in the .xsession-errors log. The plasma-plasmashell.service service seems to be disabled but enabling it does nothing to change the situation. Furthermore, systemctl --user status plasma-plasmashell.service shows that it never attempted to run the service. Disabling systemdBoot in the config file resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433151] Refreshing KickOff's application list twice without changing the category empties the right view
https://bugs.kde.org/show_bug.cgi?id=433151 --- Comment #2 from The Feren OS Dev --- Demonstrated the bug in this video: https://www.youtube.com/watch?v=Wl5gzc2wVd4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433119] New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.'
https://bugs.kde.org/show_bug.cgi?id=433119 --- Comment #6 from The Feren OS Dev --- Demonstrated the bug in this video: https://www.youtube.com/watch?v=Wl5gzc2wVd4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433151] Refreshing KickOff's application list twice without changing the category empties the right view
https://bugs.kde.org/show_bug.cgi?id=433151 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #1 from The Feren OS Dev --- I can reproduce this and was gonna show it off in the Telegram chat later today. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433130] Application launcher does not auto-update changes.
https://bugs.kde.org/show_bug.cgi?id=433130 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #1 from The Feren OS Dev --- This is probably the same bug as https://bugs.kde.org/show_bug.cgi?id=433119. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433119] New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.'
https://bugs.kde.org/show_bug.cgi?id=433119 --- Comment #3 from The Feren OS Dev --- ...and even when trying to reinstall plasma-desktop plasma-desktop-data plasma-workspace plasma-widgets-addons it's still occuring, so I don't think it's something I did since that would've been overridden by the reinstalls. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433119] New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.'
https://bugs.kde.org/show_bug.cgi?id=433119 --- Comment #2 from The Feren OS Dev --- Managed to produce it again but this time using a Terminal command to remove the icon for me while I had Kickoff open from a Plasma panel, and same with the Terminal adding the icon back for me as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433119] New: New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.'
https://bugs.kde.org/show_bug.cgi?id=433119 Bug ID: 433119 Summary: New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.' Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Basically, I was working on a fork of Kickoff's new redesign when I noticed it didn't remove the "Facebook" icon I had just removed via a file manager, and then later didn't add it back in when I restored said icon via a file manager. Confused, I tried doing it in official Kickoff and yielded the exact same result there. STEPS TO REPRODUCE 1. Get a .desktop file in ~/.local/share/applications or something that Kickoff registers as being an application in a category 2. Open up Kickoff (in my testing I used plasmoidwindowed to keep the Plasmoid visible) 3. Delete the .desktop file alternative 3. Restore the .desktop file after having deleted it 3. OBSERVED RESULT The menu doesn't automatically add or remove the icon depending on the context - a category change and back is necessary EXPECTED RESULT The menu automatically adds or removes the icon depending on the context immediately upon timing out the "Applications Updated." label (aka when it normally refreshes) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.21.0 (available in About System) KDE Plasma Version: 5.21.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427864] PlasmoidHeading area has wrong color when using Breeze Dark plasma theme
https://bugs.kde.org/show_bug.cgi?id=427864 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #10 from The Feren OS Dev --- I think I just indirectly made a fix to this bug without even knowing about this bug report: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/124 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427638] System Tray selection box is too small width-wise
https://bugs.kde.org/show_bug.cgi?id=427638 --- Comment #5 from The Feren OS Dev --- Could spacing be potentially decreased while then increasing the width of the parent's box as to counteract the spacing decrease, potentially, maybe? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427638] System Tray selection box is too small width-wise
https://bugs.kde.org/show_bug.cgi?id=427638 --- Comment #1 from The Feren OS Dev --- Created attachment 132323 --> https://bugs.kde.org/attachment.cgi?id=132323&action=edit the bug in action -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427638] System Tray selection box is too small width-wise
https://bugs.kde.org/show_bug.cgi?id=427638 The Feren OS Dev changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427638] New: System Tray selection box is too small width-wise
https://bugs.kde.org/show_bug.cgi?id=427638 Bug ID: 427638 Summary: System Tray selection box is too small width-wise Product: plasmashell Version: 5.19.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: 1.0 SUMMARY The 5.20 system tray selection box has been shortened in width compared to 5.19's one, thus meaning it looks ugly on every Plasma Style that has a selection box style that fills (nearly) all of the box. STEPS TO REPRODUCE 1. Apply a Plasma Style that does that, I guess 2. Be on Plasma 5.20 3. Profit OBSERVED RESULT You get the point. EXPECTED RESULT The box would be as wide as it is in 5.19 at the very least. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20.0 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427294] Supporting Group Policy restrictions
https://bugs.kde.org/show_bug.cgi?id=427294 --- Comment #2 from The Feren OS Dev --- I think Group Policy is a Windows Active Directory thing, pretty sure it is... by supporting I mean, if it's even possible to do so, translate all the policies that can be translated into KDE Kiosk Mode's respective restrictions when logged in as appropriate Active Directory users. Haven't really explored how it works in Ubuntu 20.10, to be honest - all I've seen is that they've uploaded documentation for enterprises about it, and a checkbox at the bottom of the User Information step of Ubiquity in Ubuntu 20.10. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427394] Calamares no longer works on 1 CPU
https://bugs.kde.org/show_bug.cgi?id=427394 --- Comment #1 from The Feren OS Dev --- Screenshot of Feren OS using KDE neon User Edition 5.19.5's packages, including its Calamares package, with this said issue occurring: https://imgur.com/a/OJcpvS8 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427394] New: Calamares no longer works on 1 CPU
https://bugs.kde.org/show_bug.cgi?id=427394 Bug ID: 427394 Summary: Calamares no longer works on 1 CPU Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ferenos...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After updating to Calamares 3.2.30, Calamares no longer functions unless you have 2 or more CPU cores. It gets stuck on 'Checking module requirements...' when using the '-d' flag. STEPS TO REPRODUCE 1. Make an ISO with the latest version of Calamares, of Neon's compiling, in it 2. Boot into the ISO using a VM (or potentially machine too) with just one CPU core 3. Launch Calamares OBSERVED RESULT Calamares gets stuck. Using '-d' shows that it's stuck on that aforementioned line. EXPECTED RESULT Calamares functioning just fine SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon User Edition 5.19.5 (in the screenshot shown below it's Feren OS on 20.04 using KDE neon User Edition 5.19.5's packages) (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION ArcoLinux has also been encountering this exact same issue. Also when I compiled Calamares manually myself ahead of Neon compiling this version of Calamares (I compiled 3.2.30 beforehand) this issue didn't occur. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 427294] New: Supporting Group Policy restrictions
https://bugs.kde.org/show_bug.cgi?id=427294 Bug ID: 427294 Summary: Supporting Group Policy restrictions Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: --- SUMMARY With Ubuntu recently adding the option to have Active Directory integration in Ubuntu 20.10's Ubiquity, it reminded me of the fact that basically no DEs, as far as I know, integrate with Group Policy to restrict their experiences accordingly. If it's feasible to do, it would be cool if Group Policy support was implemented, via the already existing appropriate Kiosk restrictions being applied on each Active Directory user. This would be handy for businesses, and places of education, where they usually have different restrictions per user on Windows. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426950] If the WiFi connection temporarily drops host resolution gets stuck and times out until the Networks Plasmoid is opened
https://bugs.kde.org/show_bug.cgi?id=426950 --- Comment #1 from The Feren OS Dev --- Frameworks Version: 5.74.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426950] New: If the WiFi connection temporarily drops host resolution gets stuck and times out until the Networks Plasmoid is opened
https://bugs.kde.org/show_bug.cgi?id=426950 Bug ID: 426950 Summary: If the WiFi connection temporarily drops host resolution gets stuck and times out until the Networks Plasmoid is opened Product: plasma-nm Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ferenos...@outlook.com Target Milestone: --- SUMMARY If the WiFi Connection temporarily drops before immediately reconnecting, the internet connection will indefinitely try to resolve hosts resulting in timeouts and a non-working internet connection until the Networks Plasmoid is opened, where the network then immediately unfreezes. STEPS TO REPRODUCE 1. Connect to WiFi 2. Wait for it to drop out (a good indication is Android reconnecting to the WiFi connection suddenly) 3. Try to do any host resolving such as going to a website in your browser 4. See that it fails 5. Repeat, but this time open the Networks Plasmoid while it's doing it OBSERVED RESULT The host resolving is stuck and gets unstuck immediately when the Networks Plasmoid is opened. EXPECTED RESULT The network would be reconnected properly without having to correct it manually by opening the Networks Plasmoid. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.19.5 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: (I'll fill this in slightly later) Qt Version: (I'll fill this in slightly later) ADDITIONAL INFORMATION A good indication of when this happens is that on Android it'll visibly disconnect and then immediately reconnect to that WiFi connection. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426777] (5.20) Users KCM Avatars list no longer lists custom entries in /usr/share/user-manager/avatars
https://bugs.kde.org/show_bug.cgi?id=426777 The Feren OS Dev changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416072] Breeze's Plasma Theme has not been updated to adapt to the changed icon name for the Milou Plasmoid
https://bugs.kde.org/show_bug.cgi?id=416072 The Feren OS Dev changed: What|Removed |Added Assignee|ferenos...@outlook.com |visual-des...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426776] When bluetooth is unavailable, KCM Bluetooth just acts as if Bluetooth is merely disabled
https://bugs.kde.org/show_bug.cgi?id=426776 The Feren OS Dev changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 --- Comment #4 from The Feren OS Dev --- (although for me it absolutely does not change the avatar at all despite seeming like it did in the KCM - not even .face changes) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #3 from The Feren OS Dev --- Reproduced on KDE neon Unstable 5.19.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422182] Users avatars look blurry/pixelated in the new Users kcm
https://bugs.kde.org/show_bug.cgi?id=422182 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #2 from The Feren OS Dev --- Reproduced in KDE neon Unstable 5.19.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426778] New: Users KCM requires authentication to update the user's avatar once more
https://bugs.kde.org/show_bug.cgi?id=426778 Bug ID: 426778 Summary: Users KCM requires authentication to update the user's avatar once more Product: systemsettings Version: 5.19.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: uhh...@gmail.com Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY User Manager recently had an update that made it not need authentication to update the avatar of the user when changing the user's avatar in there and saving. Now in 5.19.90/5.20 the new Users KCM requires authentication once more. STEPS TO REPRODUCE 1. Go into User Manager (Old) 2. Change the avatar and save 3. Repeat this process on Users (New) KCM at any time OBSERVED RESULT Authentication is required EXPECTED RESULT Authentication isn't required SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon Unstable 5.19.90 (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426777] (5.20) Users KCM Avatars list no longer lists custom entries in /usr/share/user-manager/avatars
https://bugs.kde.org/show_bug.cgi?id=426777 --- Comment #1 from The Feren OS Dev --- Update: I guess the list is entirely hardcoded currently as adding items to 'photos' for instance doesn't add them to the list of available avatars. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426777] New: (5.20) Users KCM Avatars list no longer lists custom entries in /usr/share/user-manager/avatars
https://bugs.kde.org/show_bug.cgi?id=426777 Bug ID: 426777 Summary: (5.20) Users KCM Avatars list no longer lists custom entries in /usr/share/user-manager/avatars Product: systemsettings Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: uhh...@gmail.com Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The new 5.20 Users KCM's Avatars list no longer lists custom images in /usr/share/user-manager/avatars/(insert custom avatar set name here which contains custom avatars). For instance Feren OS comes pre-bundled with its own set of avatars in /usr/share/user-manager/avatars/feren. STEPS TO REPRODUCE 1. Get a custom avatar set in /usr/share/user-manager/avatars/(name here) 2. Open Users KCM 3. Change the user avatar OBSERVED RESULT Only files in konqui and photos are listed EXPECTED RESULT Files in all folders in there excluding 'circles' would be listed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon Unstable 5.19.90 (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION This is a regression from the old version of the 'User Manager' KCM which listed the custom avatars fine -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426776] When bluetooth is unavailable, KCM Bluetooth just acts as if Bluetooth is merely disabled
https://bugs.kde.org/show_bug.cgi?id=426776 The Feren OS Dev changed: What|Removed |Added Summary|When bluetooth is |When bluetooth is |unavailable, it just acts |unavailable, KCM Bluetooth |as if Bluetooth is merely |just acts as if Bluetooth |disabled|is merely disabled -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426776] New: When bluetooth is unavailable, it just acts as if Bluetooth is merely disabled
https://bugs.kde.org/show_bug.cgi?id=426776 Bug ID: 426776 Summary: When bluetooth is unavailable, it just acts as if Bluetooth is merely disabled Product: systemsettings Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_bluetooth Assignee: now...@gmail.com Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The new bluetooth KCM does not indicate that Bluetooth is entirely unavailable on the hardware it's running on, instead merely being stuck on the "Bluetooth is disabled" screen where the button to enable it therefore does absolutely nothing. STEPS TO REPRODUCE 1. Put KDE neon Unstable in a Virtual Machine that does not support Bluetooth (such as VirtualBox) or any installation with Plasma 5.19.90/5.20 2. Open the Bluetooth KCM OBSERVED RESULT The "Bluetooth is disabled" screen shows EXPECTED RESULT A "Bluetooth is not available" screen should show SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon Unstable 5.19.90 (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Maybe the Bluetooth KCM rewriter simply forgot to make this screen a thing? -- You are receiving this mail because: You are watching all bug changes.
