[kde] [Bug 455887] New: generally can't group programs on text taskbar
https://bugs.kde.org/show_bug.cgi?id=455887 Bug ID: 455887 Summary: generally can't group programs on text taskbar Product: kde Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Usually no longer works to group programs on text taskbar. One is forced to select every program, then it may work initially, but if taskbar space frees up but then you open more programs to need grouping again (such as increases from one to two task rows) grouped ones never seem to regroup unless you undo & redo. STEPS TO REPRODUCE 1. Revert to normal text taskbar. 2. Group programs. 3. Free up space then open more programs to need group. OBSERVED RESULT Usually can't group programs. EXPECTED RESULT Group programs and return option to group /all/ without having to do dozens separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15.1-current / 5.25.1 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455887] generally can't group programs on text taskbar
https://bugs.kde.org/show_bug.cgi?id=455887 --- Comment #2 from David Chmelik --- > Can you be specific about how you are grouping your programs? There's apparently only one way left with text taskbar: right-button select the program -> more -> allow this program to be grouped. > A screen recording might help so we don't have to go back and forth a bunch. It's nothing complicated enough to do that (and the only way to do this) and can't do recordings anyway. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455950] New: users don't understand widgets (closing)
https://bugs.kde.org/show_bug.cgi?id=455950 Bug ID: 455950 Summary: users don't understand widgets (closing) Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Users don't understand widgets with no visible way to close (such as battery, calendar, clipboard, discs & devices, keyboard layout, lock keys, networks, notifications, night colour, printers, volume, weather forecast, etc.) STEPS TO REPRODUCE 1. Accidentally open widget. 2. See no X to close it. 3. Maybe can't use PC without invisible closing expert help. OBSERVED RESULT Users don't understand widgets with no visible way to close (such as battery, calendar, clipboard, discs & devices, keyboard layout, lock keys, networks, notifications, night colour, printers, volume, weather forecast, etc.) EXPECTED RESULT 𝘝𝘪𝘴𝘪𝘣𝘭𝘦 option to close widgets (not invisible!) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User - 5.25 KDE Plasma Version: [up-to-date one minute ago] KDE Frameworks Version: [up-to-date one minute ago] Qt Version: [up-to-date one minute ago] ADDITIONAL INFORMATION I administer KDE Neon GNU/Linux PCs for seniors who started using PCs with MS-DOS & Windows 3. They do not know what system-tray is (despite being told 100+ times) let alone widgets (despite being told 10+ times) and haven't been able to learn one must press same area that opened widget to close. Even I (BSc CS started with MS-DOS & no Windows) took time to learn. They're smart users (science PhD, MA) but you can't expect users who didn't grow up with PCs to learn more about them than they might about their car engines. Maybe this won't be a problem in 50 years but currently billions still don't understand PCs, and unnecessary pad/tab(let) conventions on desktop are making it hard for many... so certain older Apple & Windows 3 conventions shouldn't be dropped (X to close, types of program launcher groups/managers/menus, but I'm diverging now...) On top of it all, I noticed KDE Plasma panel is regularly unresponsive, which I think might've always been case (since KDEP4) though happened more to me when mining ethereum, etc... now I do use a miner that says it'll take it more easily because a monitor is detected, though I don't know still slows non-game usage... I know if I open some number over 10 programs panel halts for hours, but have to investigate/count how many and whether also widgets not just on my but users' PCs (isn't mining during their usage, at daytime.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455950] Widget pop-ups don't have close buttons, so "0-dots-in computers" people have trouble figuring out how to close them
https://bugs.kde.org/show_bug.cgi?id=455950 --- Comment #8 from David Chmelik --- (In reply to guimarcalsilva from comment #6) > Can you describe what those users are trying to do to close the panel? I explained they don't know, so don't try, and what they do (they ask me.) They don't pin them and they use kicker, not kickoff. If I'm very tired, sometimes I have same problem because widget interface deviated from older interface style to become counter-intuitive: there have been similar past bugs no visible way to do something causes what KDE people call 'discoverability problems.' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455950] Widget pop-ups don't have close buttons, so older users have trouble figuring out how to close them
https://bugs.kde.org/show_bug.cgi?id=455950 David Chmelik changed: What|Removed |Added Summary|Widget pop-ups don't have |Widget pop-ups don't have |close buttons, so |close buttons, so older |"0-dots-in computers" |users have trouble figuring |people have trouble |out how to close them |figuring out how to close | |them| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445454] programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #17 from David Chmelik --- I guess this works but options sound like doing opposite what they say. When I fixed it for some, others have problems but it's fewer now, but I'll close this a seem to be enough options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455950] Widget pop-ups don't have close buttons, so older users have trouble figuring out how to close them
https://bugs.kde.org/show_bug.cgi?id=455950 --- Comment #10 from David Chmelik --- (In reply to Nate Graham from comment #9) > Do these users have difficulty figuring out how to close normal menus? I ask > because the UX is very similar: you click on a thing to open a popup > adjacent to it, then you can close that popup by clicking on the same thing > or by clicking somewhere outside of the popup. No: we learned that in Windows 3.1, but isn't very similar: if a menu is open and you select a blank part of a menu-bar, the menu closes, but if a widget is open and you select a blank part of the panel, nothing happens. That's why they've asked me dozens times and maybe always will (and why I forget if I'm very tired.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428591] won't use time zone nor is selectable
https://bugs.kde.org/show_bug.cgi?id=428591 David Chmelik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from David Chmelik --- This works on new installations and as root (installed Fresh FreeBSD 13.1 and Slackware 15.1-current) though there might be something users do that can still cause this (or maybe daylight saving time does it) but may no longer be a bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455950] Widget pop-ups don't have close buttons, so older users have trouble figuring out how to close them
https://bugs.kde.org/show_bug.cgi?id=455950 --- Comment #12 from David Chmelik --- (In reply to Nate Graham from comment #11) > Got it, that makes sense. So if we fix that, do you think it would be > enough? If so this is a duplicate of Bug 367815. For me, yes; for users such as mentioned I'd have to wait & see. By time they tell me (sometimes email minutes/hours later) and then by time I check (if not immediately) sometimes they found a way (select some other area) or I explain. I think of drop-down widgets more like normally-closable programs in a tiling window manager (xmonad, etc., when arranged as tabs) and though they haven't used one (and I never learned to like those) they probably do also... -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 428592] night color thinks it's not running and won't turn off
https://bugs.kde.org/show_bug.cgi?id=428592 David Chmelik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from David Chmelik --- This seems to no longer happen or was part of a related bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384657] Gradient wallpaper option
https://bugs.kde.org/show_bug.cgi?id=384657 --- Comment #2 from David Chmelik --- Gradient would still be nice (currently I just make six versions (light, medium, dark, and duplicates 'redshifted') of all gradients for five or six or seven monitor resolutions (plus pads/tab(let)s/phones.) Thanks for fixing slideshow (and adding at least one colour behind can be changed; ) the new aspect ratio description seems equivalent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384657] wallpaper options
https://bugs.kde.org/show_bug.cgi?id=384657 David Chmelik changed: What|Removed |Added Summary|Gradient wallpaper option |wallpaper options -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 429220] KOrganizer uses time different than what's given
https://bugs.kde.org/show_bug.cgi?id=429220 David Chmelik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED --- Comment #6 from David Chmelik --- I think fresh reinstall fixed this but something might cause it to reoccur, which I can't test because KOrganizer apparently can no longer use Google Calendar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444525] can't always choose a different splash screen than global theme
https://bugs.kde.org/show_bug.cgi?id=444525 David Chmelik changed: What|Removed |Added Resolution|REMIND |WORKSFORME --- Comment #5 from David Chmelik --- Works now. [KSplash] Theme=org.kde.breeze.desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445451] some screen geometry detection critically buggy
https://bugs.kde.org/show_bug.cgi?id=445451 David Chmelik changed: What|Removed |Added Resolution|WORKSFORME |UPSTREAM --- Comment #9 from David Chmelik --- It never worked for me, but apparently isn't a KDE bug, but a X bug of whatever (Xinerama?) controls multi-monitor management for any window manager (WM) or desktop environment (DE) as I had same problem when using XFCE. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] forced to use KDE wallet
https://bugs.kde.org/show_bug.cgi?id=429274 David Chmelik changed: What|Removed |Added Resolution|REMIND |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #10 from David Chmelik --- It still happens with non-administrator user and polkit-0.120-x86_64-3, polkit-kde-agent-1-5.25.2-x86_64-1, polkit-qt-1-0.114.0-x86_64-1 . Now I leave KDE wallet on anyway, but don't use it; don't want to be forced to. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 --- Comment #10 from David Chmelik --- Created attachment 150349 --> https://bugs.kde.org/attachment.cgi?id=150349&action=edit other option -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 David Chmelik changed: What|Removed |Added Resolution|INTENTIONAL |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #11 from David Chmelik --- There was another option (shown in attachment) since Windows 9n (95, 98) & ME and a while after. I recall the shown menu style being an option for the start menu (so should be one for kicker, maybe kickoff, etc.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455887] generally can't group programs on text taskbar
https://bugs.kde.org/show_bug.cgi?id=455887 --- Comment #4 from David Chmelik --- Created attachment 150354 --> https://bugs.kde.org/attachment.cgi?id=150354&action=edit non-grouping This screen video shows Chrome/Chromium was meant to group, didn't, but only did after reset (Firefox does same.) I realize these aren't KDE programs but usually don't use more than one window with KDE programs... I can test one if depends more on who makes it. At time of this video, about 1% to 2% of system CPU resources were used, 10GB RAM free, no audible HDD activity (where /home/user/.kde is) but main KDE itself is on SSD. The video was too large and KDEnlive is counter-intuitive with outdated documentation, so I couldn't select part of it but had to end up using VLC and FFMPEG... video making/editing is extremely difficult and I'd rather not do it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] colours appearance may not update until you select something else
https://bugs.kde.org/show_bug.cgi?id=448995 --- Comment #6 from David Chmelik --- Created attachment 150355 --> https://bugs.kde.org/attachment.cgi?id=150355&action=edit colours not changing This video shows it happening again. Very soon after beginning, I press a which changes appearance of 'apply' button but nothing happens until I select another appearance tab then press popup's 'apply'... I could wait several minutes and the keyboard keystroke just no longer works... isn't just limited to this tab but several/many systemsettings tabs (so is probably a more general bug.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] colours appearance may not update until you select something else
https://bugs.kde.org/show_bug.cgi?id=448995 --- Comment #7 from David Chmelik --- At the time of recording I was using about 1% CPU resouces, had 17GB free RAM, and no audible HDD activity (/home/user/.kde is on it but main KDE is on SSD.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] colours appearance may not update until you select something else
https://bugs.kde.org/show_bug.cgi?id=448995 David Chmelik changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] some systemsettings options don't apply (though keystroke changes button appearance) until new tab selected then press popup's 'apply'
https://bugs.kde.org/show_bug.cgi?id=448995 David Chmelik changed: What|Removed |Added Summary|colours appearance may not |some systemsettings options |update until you select |don't apply (though |something else |keystroke changes button ||appearance) until new tab ||selected then press popup's ||'apply' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] some systemsettings options don't apply (though keystroke changes button appearance) until new tab selected then press popup's 'apply'
https://bugs.kde.org/show_bug.cgi?id=448995 David Chmelik changed: What|Removed |Added Version|5.23.5 |5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] forced to use KDE wallet
https://bugs.kde.org/show_bug.cgi?id=429274 David Chmelik changed: What|Removed |Added Version|5.20.2 |5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429275] atrocious grammar: enable option for more/most/all lowercase
https://bugs.kde.org/show_bug.cgi?id=429275
David Chmelik changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED|REOPENED
Resolution|INTENTIONAL |---
--- Comment #5 from David Chmelik ---
The worst offender is category lists (in menus (kicker, kickoff, top of
applications etc.) & sidebars (in file manager (dolphin, konqueror)) because
are large multiple instances. Second-worst (as is only one thing) is buttons.
The KDE style link is now a dead link. Normally university technical writing
classes are done by English experts (professors or their department's certified
tutors at a British English level) and if your standards (do you have a new
link?) weren't written with their help they're quite likely incorrect.
Please seriously consider my description how it's equivalent to how people
never describe (in capitals) a large sequence of average things they might
during the day ("I opened the Garage Door to go open the Toolbox to get my
Hammer and Nails to work on the Workbench to work on a Wooden Craft Project.)
Whether it's intentional, users who want stricter standards should have opt-out
option, though doesn't break functionality so could be put on wishlist.
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 429275] atrocious grammar: enable option for more/most/all lowercase
https://bugs.kde.org/show_bug.cgi?id=429275 David Chmelik changed: What|Removed |Added Platform|Other |Neon Packages Target Milestone|1.0 |--- Component|general |general Version|master |unspecified Product|plasmashell |kde -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429275] atrocious grammar: enable option for more/most/all lowercase
https://bugs.kde.org/show_bug.cgi?id=429275 David Chmelik changed: What|Removed |Added CC||k...@davidedmundson.co.uk Platform|Neon Packages |Other Component|general |general Product|kde |plasmashell Version|unspecified |git-stable-Plasma/5.24 Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 429275] atrocious grammar: enable option for more/most/all lowercase
https://bugs.kde.org/show_bug.cgi?id=429275 David Chmelik changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |kde Component|general |general Version|git-stable-Plasma/5.24 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 429275] atrocious grammar: enable option for more/most/all lowercase
https://bugs.kde.org/show_bug.cgi?id=429275 --- Comment #6 from David Chmelik --- Of course, I (and some friends/family) use British English KDE. Another mistake is systemsettings can't find 'alternative' where slang American English (bad grammar dialect) rewrote 'alternate' (not synonym: younger Americans using as such are absolutely incorrect.) Why would a German project not mainly use British English? I edited Kicker menu and Dolphin side panel, so those are almost solved except can't lowercase 'devices,' 'places' 'recent,' 'remote,' 'search,' 'recent applications,' 'power/session (nor sub-entries... slash standard is no spaces beside,)' Sure, some kicker/etc. menu categories can be academic/school/department subjects (development/programming, education, graphics, multimedia, network, system, but not likely games, help, lost & found, office, settings, nor anything in Dolphin) so that way are proper nouns, but same subjects in most (non-academic) usage aren't proper nouns (hence lowercase)... even clearer for those, and two I can't lowercase, and Dolphin sidebar... if you compare/contrast to anything else (Dolphin sidebar categories in normal conversation, Kicker 'recent applications' versus recent physical objects/appliances/tools used, and 'power/session' & etc. versus physical controls) any smart enough person (including British schoolkids who did okay through first year/class/grade) knows those are /never/ capitalized, nor are buttons/dials/knobs/levers/switches & etc... even in most substandard English (many Chinese-written) manuals that make several/many grammar/spelling mistakes, but typically only uppercase their company and maybe (in conjunction) product name. I don't know all KDE history but was inspired by CDE (apparently inspired by Windows (inspired by Apple))... but the two most popular desktop GUIs' founders/creators were American college dropouts. Bad grammar dialect country college dropouts set modern GUI text standards... yet most programmers follow! It's okay to ask a programmer about programming language, not necessarily human language. That's why I won't necessarily agree saying 'intended' nor your style guides are relevant (in contrast to higher academic English reference/textbooks, such as ones we have from London, etc., and ones from Oxford & Cambridge, and such standards-based technical writing.) Most programming/developing/engineering years/decades possibly haven't needed to read PC manual recently, so verify yours if buttons are lowercase (and in physical controls' design/instruction texts for all subjects/industries) and ask why is same different in GUI? Only because standards were set by bad grammar dialect country college dropouts, not British higher academic English experts. Having fixed most Kicker menu & Dolphin entries is almost enough, but fixing everywhere is a wish. Kicker's incorrect capitalization makes me think (stressful) I should be back in university focusing on several such categories again, and you've probably heard using all capitals in chat is like shouting... but when chatters capitalize every word (a few foreigners do) it's same, as is incorrect capitalization: for many years, also feels like shouting! Incorrect capitalization is harder to read/use. Try proper English conventions and see if you notice difference. If you command-line UNIX/GNU/Linux code in a directory/folder with some/many different languages and projects, you most likely made it all lowercase (to decrease typing, and looks nicer, not just there but everywhere.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 429275] atrocious grammar: internationalization including enable option for more/most/all lowercase (other than formally-named programs)
https://bugs.kde.org/show_bug.cgi?id=429275 David Chmelik changed: What|Removed |Added Summary|atrocious grammar: enable |atrocious grammar: |option for more/most/all|internationalization |lowercase |including enable option for ||more/most/all lowercase ||(other than formally-named ||programs) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 429275] atrocious grammar: internationalization including more/all lowercase option (except formally-named programs)
https://bugs.kde.org/show_bug.cgi?id=429275 David Chmelik changed: What|Removed |Added Summary|atrocious grammar: |atrocious grammar: |internationalization|internationalization |including enable option for |including more/all |more/most/all lowercase |lowercase option (except |(other than formally-named |formally-named programs) |programs) | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456278] New: Panels sometimes have motion/flickering and sometimes don't auto-hide (if set to.)
https://bugs.kde.org/show_bug.cgi?id=456278 Bug ID: 456278 Summary: Panels sometimes have motion/flickering and sometimes don't auto-hide (if set to.) Product: plasmashell Version: 5.25.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 150364 --> https://bugs.kde.org/attachment.cgi?id=150364&action=edit flickering panels SUMMARY Panels sometimes have motion/flickering and sometimes don't auto-hide (if set to.) STEPS TO REPRODUCE 1. Setup two or three monitors and set some panels auto-hide. 2. Open/use many programs. 3. Do many things and wait, maybe hours. OBSERVED RESULT Panels sometimes have motion/flickering and sometimes don't auto-hide (if set to,) shown (top and right-side panels auto-hide) in attached video (large size so short time so you should probably loop.) Some minimized programs flicker (most/all web browsers, as if having fast activity) on their taskbar section's lower area for a while, or even continually appear & disappear (HexChat) for a while, though haven't likely seen official KDE programs do either. With this setup, depending how one uses/selects programs (even excluding HexChat) an entire panel may flicker fast, like it's being redrawn too much (often if I selected a right-side lower screen program, top screen panel flickers fast, but different setups might react differently.) If displays idle then blank, sometimes 4K's panel moves (leaving desktop that was below) about 25% to the right and its right-side section moves onto part the 1080p screen (as sometimes still happens with programs snapped into the 4K right-side, which the latter is probably Xinerama but I never set panels to span after trying once years ago in a now-gone KDE installation.) EXPECTED RESULT Always auto-hide panels set to do so. Optionally don't show fast updates in panel for minimized programs. When screens blank, don't move things (panels, general programs, and under heavy background usage, also desktop icons.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15.1-current / 5.25.2 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Since I have 4K, 1600x1200, 1080p screens, don't think I had enough time to prove top (for file managers/Dolphin) & right-side monitors (for xterms/Konsole) are auto-hide, but setting these two up like that is always something I do (past five years) in first 24hrs setting up KDE with this monitor setup (and this KDE installation has been used since past Winter.) Luckily auto-hide panel doesn't appear over Konsole when maximized on right, but does appear over file managers maximized at top, sometimes for a long time. For attached video, almost 6/32 threads were left (6787.17 GFlops each according to bogomips, maybe 5% usage each) and 7GB RAM, with no audible activity on HDD (which has /home/user/.kde) and main KDE is on SSD/M2/NVME. I doubt problem is scant CPU resources, as some 2010s PCs run KDE Neon User 5.25 fine with two threads (typically using few programs, though all mine were idle besides aforementioned networking, SimpleScreenRecorder, a few daemons past first page of results in commands like top (atop, htop, btop.)) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 David Chmelik changed: What|Removed |Added CC|dchme...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] some systemsettings options don't apply (though keystroke changes button appearance) until new tab selected then press popup's 'apply'
https://bugs.kde.org/show_bug.cgi?id=448995 David Chmelik changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #9 from David Chmelik --- (In reply to Nate Graham from comment #8) > Your video show everything working properly: the app windows change color > when you change the color scheme In fact it shows it not working: I press a to change it, then 'apply' button gets a dotted line near its edge and does nothing. It's not until I select 'plasma style' do I get a message that says the colour theme wasn't applied, so do I want to apply before going to the plasma style menu. Never mind the part about changing plasma style: not an issue. I could redo this video showing me waiting half an hour with the 'apply' button not finishing and the colour theme not changing until I select another menu tab and get message it's not updated yet, and asking if I want to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454028] application launcher (cascading) broken
https://bugs.kde.org/show_bug.cgi?id=454028 David Chmelik changed: What|Removed |Added Resolution|FIXED |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456386] New: keystrokes can't apply some settings
https://bugs.kde.org/show_bug.cgi?id=456386
Bug ID: 456386
Summary: keystrokes can't apply some settings
Product: systemsettings
Version: 5.25.2
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: dchme...@gmail.com
Target Milestone: ---
SUMMARY
Keystrokes can't apply some settings.
STEPS TO REPRODUCE
1. Run systemsettings.
2. Go to settings such as appearance: plasma style, colours (possibly/probably
others: check all.)
3. Select new option and try keystroke (either doesn't exist or doesn't
complete processing.)
OBSERVED RESULT
Keystrokes can't apply some settings: plasma style no longer has standard
underlined-letter buttons indicating keystrokes to 'apply' nor
'cancel' (though ) cancels; ) colours accepts a but never processes
it (both may leave user hanging and force slow mouse usage.)
EXPECTED RESULT
Allow & process consistent standard underlined-letter button keystrokes
('apply' usually being a or sometimes p, l, or y but should
be same/standardized/consistent for all cases (no menu uses those letters for
other buttons) and include keystrokes for 'cancel' and all systemsettings
buttons.)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User 5.25.2 (up-to-date,) Slackware64 15.1-current
(up-to-date ) / 5.25.2
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5 (Neon,) 5.15.4 (Slackware)
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 452486] inconsistent menus
https://bugs.kde.org/show_bug.cgi?id=452486 --- Comment #2 from David Chmelik --- Most systemsettings uses a keystrokes to 'apply' (and certain letters for other buttons 'cancel,' 'discard') which users get used to. A few other systemsettings menus: regional (date & time, input method, spell-check,) hardware (all sub-menu 'apply' buttons) 'apply' use p, l, y, which confuses users and makes them usually press a, then nothing happens, then they must double-check and use unexpected keys. No other systemsettings buttons use a,p,l,y, so 'apply' should be same/standardized/consistent throughout all its menus. The current format prevents users from ever learning an easy system a button is same/standard/consistent, rather than be entirely different/non-standard/inconsistent, leaving users permanently mixing-up & confused. There may be other cases (haven't researched (in)consistency buttons besides 'apply.') -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 452486] inconsistent menus
https://bugs.kde.org/show_bug.cgi?id=452486 David Chmelik changed: What|Removed |Added Platform|Slackware Packages |Neon Packages Component|general |general Product|konsole |kde Version|21.12.3 |unspecified Assignee|konsole-de...@kde.org |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 452486] inconsistent menus
https://bugs.kde.org/show_bug.cgi?id=452486 --- Comment #3 from David Chmelik --- This bug report overall was about several cases, so has several different sets of steps to reproduce. I initially mentioned an earlier case (reported, maybe ignored, in KDE3 and/or KDEP4, but couldn't find it) but then only gave steps for Konsole. Other steps are below. STEPS TO REPRODUCE. 1. Run systemsettings. 2. Try 'apply' button in every (sub-)menu. 3. Notice they're widely different/non-standard/inconsistent, so never learn interface rather than remain permanently mixed-up confused. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] Non-root users can't authenticate to disable KWallet
https://bugs.kde.org/show_bug.cgi?id=429274 David Chmelik changed: What|Removed |Added Summary|Non-admin users can't |Non-root users can't |authenticate to disable |authenticate to disable |KWallet |KWallet --- Comment #11 from David Chmelik --- A workaround is--though recommended against--run X/KDE as root and disable KDE wallet there, but as users' wallets aren't necessarily root's (regardless root has access) this should never be required. It maybe used to happen on Kubuntu and KDE Neon User, but may no longer happen on KDE Neon User, though I had run X/KDE as root on that maybe to do this (then deleted root's config/local/X/KDE files) and maybe to install fonts and configure printers (these other cases for which there should be option systemsettings run that configuration as root, rather than run X/KDE as root, because it's said certain X things mess up as root.) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 455294] can't use classic clipboard icon
https://bugs.kde.org/show_bug.cgi?id=455294 David Chmelik changed: What|Removed |Added Platform|Slackware Packages |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 455294] can't use classic clipboard icon
https://bugs.kde.org/show_bug.cgi?id=455294 --- Comment #1 from David Chmelik --- update: checked on more, below. Linux/KDE Plasma: KDE Neon User 5.6 to 5.25.2 (up-to-date,) Slackware64 14.2 stable to 15.1-current (up-to-date) KDE Plasma Version: later 4 to 5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384657] wallpaper options
https://bugs.kde.org/show_bug.cgi?id=384657 David Chmelik changed: What|Removed |Added Platform|Slackware Packages |Neon Packages --- Comment #3 from David Chmelik --- update: checked on more, below. Linux/KDE Plasma: KDE Neon User 5.6 to 5.25.2 (up-to-date,) Slackware64 14.2 stable to 15.1-current (up-to-date) KDE Plasma Version: later 4 to 5.25.2 KDE Frameworks Version: later 4 to 5.95.0 Qt Version: later 4 to 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] New: broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 Bug ID: 456391 Summary: broken/nonexistent keyboard layout Product: plasmashell Version: 5.25.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY KDE system-tray used to have keyboard layout but currently has almost all past functionality removed (no customization) including icon never even displays in system-tray under any circumstances/settings! STEPS TO REPRODUCE 1. Edit 'system tray: keyboard layout:' add layouts including alternative/international option such as 'with dead keys' for a country/language/locale (UK, USA, maybe Germany, etc.) Try to customize text & flag labels to distinguish alternative/international layout (maybe usi, uki, whatever de/Deutsch/Austrian variant label: ) can't. 2. Set keyboard layout 'always show' (or 'show when relevant' or 'always hidden' but for either of latter two cases, subsequently make/test your own steps.) 3. See nothing work nor even keyboard layout icon display in system-tray! OBSERVED RESULT KDE system-tray used to have keyboard layout but currently has almost all past functionality removed (no customization) including icon never even displays in system-tray under any circumstances/settings! EXPECTED RESULT KDE system-tray keyboard layout should have improvements including all past functionality: firstly, display in system-tray! Secondly, allow customizing text labels such as for multiple dialect layouts, and preferably over flag (but because some are for international character set usage, allowing alternative flags would be good, for example I use USA default and international layouts, latter only for British English character set so want Union Jack (UK) but someone else might want one of many English dialect/country/locale options) as (bug 444864) previously worked. Don't require more than one spare layout (sure, family members who studied/majored in several languages use many, but I don't so want all my one to three extra layouts all set 'spare,' because so far may set but not use a fourth, and only rarely use a third, and want to avoid accidentally selecting the second (unless can have Union Jack) so currently want to forcing drop-down-select even second and all ojher spares.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User 5.25.2 (earlier,) Slackware64 15.1-current (up-to-date.) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15 (earlier) to 5.15.5 (as of which mostly fixed for KDE Neon User) ADDITIONAL INFORMATION System-tray icon displays again in KDE Neon User 5.25.2 as of newer minor version (apparently unspecified, non-findable?) that upgraded to Qt 5.15.5 (so presumably icon will display after Slackware-current update (still on KDEP 5.25.2, Qt 5.15.3)) but our KDE Neon PCs have old custom label 'usi'--now unchangeable--so currently if someone adds alternative/international layout presumably can't customize to distinguish from main, but this detail (and others) could be added to bug 444864. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #1 from David Chmelik --- EXPECTED RESULT '... want to forcing drop-down-select even second and all [other] spares.' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448995] some systemsettings options don't apply (though keystroke changes button appearance) until new tab selected then press popup's 'apply'
https://bugs.kde.org/show_bug.cgi?id=448995 --- Comment #11 from David Chmelik --- I did NOT report duplicate issues--reread the title: this always only was about the keystroke doesn't 'apply' the button, though apparently is duplicate of bug 440255. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] New: Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568
Bug ID: 456568
Summary: Keystrokes don't exist to apply some settings.
Product: systemsettings
Version: 5.25.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: dchme...@gmail.com
Target Milestone: ---
SUMMARY
Keystrokes don't exist to apply some settings.
STEPS TO REPRODUCE
1. Run systemsettings.
2. Go to settings such as appearance: global theme (possibly/probably others:
check all.)
3. Look for underlined letter to do keystroke (can't see any.)
OBSERVED RESULT
Keystrokes don't exist to apply some settings: global theme no longer has
standard underlined letter buttons indicating keystrokes to
'apply' nor 'cancel' (though ) cancels) etc: mouse usage forced (if
works.)
EXPECTED RESULT
Allow & process consistent standard underlined-letter button keystrokes
('apply' usually being a or sometimes p, l, or y but should
be same/standardized/consistent for all cases (no menu uses those letters for
other buttons) and include keystrokes for 'cancel' and all systemsettings
buttons.) Don't assume touchscreen-only (no keyboard) PC!
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User 5.25.2 (up-to-date,) Slackware64 15.1-current
(up-to-date ) / 5.25.2
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5 (Neon,) 5.15.4 (Slackware)
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 456568] Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568 David Chmelik changed: What|Removed |Added OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Keystrokes don't exist to apply some settings.
https://bugs.kde.org/show_bug.cgi?id=456568 David Chmelik changed: What|Removed |Added OS|All |Linux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #14 from David Chmelik --- (In reply to Andrey from comment #13) > Please check if it's related with bug 449531 It's not because I don't personally use Wayland (only lately family PC does but Wayland has many more its own problems). The bug is in X with101-key keyboards (at least obscure ones including PS/2 and that type connected from obscure KVM switches that convert them to USB, all described in more detail earlier). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #8 from David Chmelik --- 'Medium workload' in this case means even one program that does much, such as Pan NNTP newsreader loading almost 1,000 Usenet newsgroups, which causes zero slowdown in lighter X WM/DEs... but in KDE Plasma (KDE P) such usage of Pan alone lately causes immediate panel halt... I guess because panel updates with all activity (almost 1,000 newsgroups sometimes with hundreds posts & replies)... having panel update on all activity simply isn't feasible (reported in another bug) so unless panel updating on activity can be disabled, I can never recommend KDE (except up to KDE3/TDE) to programmers though users who don't do things this large (excludes many/most power users) might be okay using KDEP. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] forced to use KDE wallet
https://bugs.kde.org/show_bug.cgi?id=429274 --- Comment #9 from David Chmelik --- Of course I am using X/KDE as a non-administrator user. I have polkit-0.119-x86_64-1, polkit-qt-1-0.114.0-x86_64-1, polkit-kde-agent-1-5.22.5-x86_64-1. Some weeks/months ago I was able to disable it. This has been an intermittent problem since maybe KDE3 though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] forced to use KDE wallet
https://bugs.kde.org/show_bug.cgi?id=429274 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429274] forced to use KDE wallet
https://bugs.kde.org/show_bug.cgi?id=429274 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444525] New: can't always choose a different splash screen than global theme
https://bugs.kde.org/show_bug.cgi?id=444525 Bug ID: 444525 Summary: can't always choose a different splash screen than global theme Product: systemsettings Version: 5.23.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: m...@genda.life Target Milestone: --- SUMMARY I still prefer/use P4/Oxygen style but had been using Breeze splash screen to remember I'm not use KDE3 or P4. This seems no longer possible. I keep selecting Breeze splash screen but it keeps showing Oxygen splash screen when I start, instead. This happens on both Slackware GNU/Linux and KDE Neon GNU/Linux. STEPS TO REPRODUCE 1. Choose global theme (is Oxygen in my case). 2. Choose different splash screen (tried Breeze). 3. Restart, watch splash screen match global theme instead of what's chosen. OBSERVED RESULT You can't always choose a different splash screen than your global theme. Well you can choose it but it won't work (will match global theme). EXPECTED RESULT You should be able to choose a different splash screen than your global theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current & KDE Neon GNU/Linux / 5.23 KDE Plasma Version: 5.23.1, 5.23.2 KDE Frameworks Version: 5.87.0, ... Qt Version: 5.15.3, ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444864] New: keyboard layout indicator became worse/useless
https://bugs.kde.org/show_bug.cgi?id=444864 Bug ID: 444864 Summary: keyboard layout indicator became worse/useless Product: plasmashell Version: 5.23.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY The keyboard layout indicator used to be good/usable, but lately it's not. It used to let you have a label you wrote over a flag (though not choose the flag, which it should've). Now you can't have both, and can't write your own label in case you use two keyboard layouts from one country. I use US, US international with dead keys, for UK characters, which I labelled usi but would be easier if I could have over UK flag, and sometimes I've used Greek, which you should be able to abbreviate in their own language as el/Ελ (for Ellada, their name.) STEPS TO REPRODUCE 1. Start KDE after upgrade. 2. check keyboard layout indicator. 3. Became third-rate, removing your labels and not allowing both flag and label, leading to confusion about which you're using. OBSERVED RESULT Downgraded layout indicator. I can no longer tell whether I'm using US or US international keyboard layout--absolutely useless. EXPECTED RESULT Should let you use your own label on a flag, and because some people use international layouts more intended for other country's characters (like get UK characters with US keyboard or vice versa) let you choose the flag that best represents the international layout. My parents' KDE Neon PC had the same setup with us & usi (and French, German, Russian) but never noticed the difference between 'US' layouts (because of forced flag) then had problems typing (and similarly you should be able to write de and Cyrillic ru for these others.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current / 5.23.2 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444864] Can't display label over flag anymore
https://bugs.kde.org/show_bug.cgi?id=444864 --- Comment #4 from David Chmelik --- I don't know what KCM is--in technical writing you're supposed to define abbreviations before you use them, no matter how simple, if they haven't been used before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444864] Can't display label over flag anymore
https://bugs.kde.org/show_bug.cgi?id=444864 --- Comment #6 from David Chmelik --- I was able to add label Ελ where the flag was displayed but the letters weren't, so this isn't actually a bug, but as you said, hard to find... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445450] New: KDE uses language at end of list for messages/errors
https://bugs.kde.org/show_bug.cgi?id=445450 Bug ID: 445450 Summary: KDE uses language at end of list for messages/errors Product: plasmashell Version: 5.23.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY KDE seems to often/usually use languages from the end of the regional settings list. I had in order British English, American English, Greek. I was usually getting popup/error/etc. messages in Greek. I removed it (just kept the alternative keyboard layout) but it's still happening. STEPS TO REPRODUCE 1. Add languages in regional settings. 2. Do something to get a message. 3. See that it uses last, not first language on the list. OBSERVED RESULT Uses last language on your list for messages. Konsole errors, also various non-KDE program tool-tips, and others did this. EXPECTED RESULT Use first language on your list for messages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current / 5.23.2 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445451] New: some screen geometry detection critically buggy
https://bugs.kde.org/show_bug.cgi?id=445451 Bug ID: 445451 Summary: some screen geometry detection critically buggy Product: plasmashell Version: 5.23.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Sometimes when I open, for example, dolphin, from the upper screen menu, but it opens on my lower screen, I move it to my upper screen, but unless I keep it partially past the left or right edge (though I don't think it should be possible to go past the edge) it will jump back down to the lower screen. If I want it on the upper screen I'm forced to maximize it (which I normally wan to anyway but prefer to do after fitting it into the screen manually, which if I try to do, it jumps back down.) STEPS TO REPRODUCE 1. Open a program intended for the upper screen, but might open on a lower screen. 2. Try to size it to the upper screen. 3. See it jump back down. OBSERVED RESULT Depending how you move a program from the lower to upper screen and start moving/sizing it there, it may jump back down to the lower screen, because some of the geometry calculations are off. EXPECTED RESULT Once you have a program on the upper screen, don't force it back down onto the lower one just from moving/sizing it without going below the upper one. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current / 5.23.2 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I wish I could make a video for you but don't think I'm going to be able to. Let me know if I need to describe more. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445454] New: programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 Bug ID: 445454 Summary: programs usually open on a different screen Product: plasmashell Version: 5.23.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If you have two or (like I have) three or more screens, programs usually open on a different screen. STEPS TO REPRODUCE 1. Select a screen with the left mouse button. 2. Use that screen's menu to open a program. 3. Probably see it open on a random screen. OBSERVED RESULT Program often open on a screen other than I selected/started it on, not always even the primary display (which might be expected) but a totally random screen. KDE programs are particularly bad at this. Other programs like non-KDE IRC, web browsers, text editors, usually opened on the primary display, don't tend to do this. It's usually that I open konsole on the right-hand screen and dolphin on the upper screen but they usually open on a random screen, sometimes my main/left-hand one or the top one. EXPECTED RESULT Open programs on the same screen as beforehand selected and as the menu that opened them. If someone moves the mouse to another screen before it starts, I don't know if that must change it or if people could be given an option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.2 KDE Plasma Version: Slackware64-current / 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445451] some screen geometry detection critically buggy
https://bugs.kde.org/show_bug.cgi?id=445451 --- Comment #1 from David Chmelik --- My top screen is 1600x1200--I hope you still take such case (4:3 shape screens including some resolutions lower than this) into consideration. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Alt Accelerators don't appear on some buttons
https://bugs.kde.org/show_bug.cgi?id=456568 --- Comment #2 from David Chmelik --- Doesn't work for me in Slackware64-current nor KDE Neon (up-to-date today and a few minutes ago.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Alt Accelerators don't appear on some buttons
https://bugs.kde.org/show_bug.cgi?id=456568 --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #3) > Just in System Settings? Or in other KDE apps as well? It's only about systemsettings: appearance: global theme (unless you notice anything else; I don't such as Konsole, Dolphin, KATE are fine.) > Does it work if you use the Breeze application style? No (on Slackware64-current but haven't tested Neon) though if it did, since I only switch between Air & Oxygen that wouldn't be a solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456278] Task Manager icons sometimes move or flicker
https://bugs.kde.org/show_bug.cgi?id=456278 David Chmelik changed: What|Removed |Added Component|Task Manager and Icons-Only |Panel |Task Manager| --- Comment #2 from David Chmelik --- Multiple panel parts involving taskbar and systemtray. The main cases are when something is minimized from the taskbar to the system-tray (such as HexChat, Thunderbird) or action is done to temporarily hide from system tray (such as clearing Klipper history.) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456732] New: more configuration settings?
https://bugs.kde.org/show_bug.cgi?id=456732 Bug ID: 456732 Summary: more configuration settings? Product: okular Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Okular has scant configuration settings. OBSERVED RESULT Okular has scant configuration settings. Whenever I open a PDF, I always have to change the fit option to page or auto, because 'fit width' usually isn't any good (any more than 'fit height' would be, but should be option.) Users should have option to save their fit setting rather than being forced to use width every time. EXPECTED RESULT Have better default fit (i.e., 'fit page' or 'auto fit' depending what difference is) and allow users to save that (and probably other) option configuration. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15.1-current &Neon 5.25 GNU/Linuxes KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION My family and I use 16:10 to 16:9 monitors including my 4K, for which I typically snap Okular to one screen-half side so it's 1920x2160 (or would be longer if I can get a 4:3 to 16:10 4K) so Okular is always taller than any standard book-shaped (A4, USA letter, etc.) PDF so forced 'fit height' is time-wasting. I need to be able to save 'fit page' or 'auto fit'--whichever is better (I don't) know as a permanent configuration setting so 99% PDFs are viewable/readable, and it'd be good if the option works when paging down (for A4 and USA letter) instead of current behaviour it doesn't page down an exact page so every some dozens of pages is quite a few pixel lines offset (so shows a small section of a different page) and you have to recentre on the current page. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455887] Sometimes windows from the same app don't get grouped until the grouping option is toggled off and back on again
https://bugs.kde.org/show_bug.cgi?id=455887 --- Comment #6 from David Chmelik --- Part of it is also if a program is grouped, and you open another, the grouped one ungroups again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456739] New: 'recent' categories unconfigurable/unavailable
https://bugs.kde.org/show_bug.cgi?id=456739
Bug ID: 456739
Summary: 'recent' categories unconfigurable/unavailable
Product: plasmashell
Version: 5.25.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Application Menu (Kicker)
Assignee: plasma-b...@kde.org
Reporter: dchme...@gmail.com
Target Milestone: 1.0
SUMMARY
'Recent' ('recent files,' etc. like maybe 'recent searches,' whatever else
Kicker used to have) categories are unavailable, except 'recent applications,'
which is non-removable.
STEPS TO REPRODUCE
1. Upgrade KDE
2. Look to add kicker 'recent' entry ('recent files,' etc. like maybe 'recent
searches,' whatever else Kicker used to have) and/or remove 'recent
applications' entry.
3. Can't: only 'recent applications' exists anymore.
OBSERVED RESULT
'Recent' ('recent files,' etc. like maybe 'recent searches,' whatever else
Kicker used to have) categories are unavailable (except recent applications)
EXPECTED RESULT
Return all past 'recent' entries Kicker could have and allow including &
excluding all.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64 15.1-current & KDE Neon 5.25 GNU/Linuxes
KDE Plasma Version: Slackware: 5.25.3; Neon:
4:5.25.3-0xneon+20.04+focal+release+build58
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.4
ADDITIONAL INFORMATION
I like 'recent' categories but don't use them much (for privacy) but users
whose Neon PCs I administer likely like such features which make things easier.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 456747] New: attempting select application menu entry style crashes
https://bugs.kde.org/show_bug.cgi?id=456747 Bug ID: 456747 Summary: attempting select application menu entry style crashes Product: systemsettings Version: 5.25.3 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Attempting select application style menu entry crashes. STEPS TO REPRODUCE 1. Run systemsettings 2. Select appearance -> application style. OBSERVED RESULT Attempting select application style menu entry crashes. EXPECTED RESULT Allow select application style. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15.1-current (up-to-date.) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Doesn't crash on KDE Neon 5.25 (updated today.) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456732] more configuration settings?
https://bugs.kde.org/show_bug.cgi?id=456732 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from David Chmelik --- Okay (finally found it.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456739] 'recent' categories unconfigurable/unavailable
https://bugs.kde.org/show_bug.cgi?id=456739 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from David Chmelik --- The real problem was the particular theme (I don't normally use) had unnoticeably small scrollbars on 4K. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 456783] New: *Ubuntu AMD Radeon driver (also for Kubuntu) crashes login/keyboard
https://bugs.kde.org/show_bug.cgi?id=456783 Bug ID: 456783 Summary: *Ubuntu AMD Radeon driver (also for Kubuntu) crashes login/keyboard Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: dchme...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *Ubuntu AMD Radeon driver (also for Kubuntu) crashes login/keyboard. STEPS TO REPRODUCE 1. Install *Ubuntu AMD Radeon driver installer package .deb (repo.radeon.com. dpkg -i package.deb.) 2. Root text-edit (such as with emacs, mcedit, micro, nano, pico, vi) /usr/bin/amdgpu-install to add 'neon|' in front of 'ubuntu|linuxmint|debian' (about line 294.) 3. Install drivers such as: amdgpu-install --opencl=rocr,legacy --no-32 --accept-eula. 4. Reboot. OBSERVED RESULT *Ubuntu AMD Radeon driver (also for Kubuntu) crashes login/keyboard: disabled except software keyboard--though almost no one would know--one can use mouse to select button to reenable hardware keyboard, then an error displays (below) and can't login. The current theme cannot be be loaded due to the errors below, please select another theme. file:///user/share/sddm/themes/breeze/Main.qml:12.1:plugin cannot be loaded for module "org.kde.plasma.core": cannot load library /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5: undefined symbol: wl_proxy_marshal_flags. EXPECTED RESULT Never replace desktop hardware with software keyboard when there's no touchscreen! Don't have theme-dependent login. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.25 GNU with testing on Linux 5.15.0-42-lowlatency, some of 5.4.0-122-lowlatency, 5.8.0-63-lowlatency, 5.11.0-46-lowlatency, 5.13.0-51-lowlatency, 5.15.0-42-lowlatency (and some such generic kernels.) KDE Plasma Version: 4:5.25.3-0xneon+20.04+focal+release+build58 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 OTHER INFORMATION hardware: ASUS Tuf Radeon RX 5700 XT, Sapphire AMD Radeon RX 580. I hope I typed the error right and could (with instructions) copy error message from log file or photograph screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #3 from David Chmelik --- (In reply to Nate Graham from comment #2) > Does the tray icon show up if you restart the computer? Neither on Neon nor Slackware. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #2) > Does the tray icon show up if you restart the computer? I see does on one older Neon PC with a Dell USB 104-key keyboard and IBM PS/2 model M 101-key, which the latter is on main family PC (no layout detected) and mine, which, mine, however, is plugged into a Belkin KVM switch detected (lsusb) as 'Belkin Components F5U120-PC Dual PS/2 Ports / F5U118-UNV ADB Adapter' except temporarily plugged-in with KVM switch's USB connector (for keyboard & mouse.) I thought hardware detection is a matter of the Linux kernel but seems KDE usually (in our cases) isn't getting full information from it or started ignoring pre-GUI OS standard keyboards. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Alt Accelerators don't appear on some buttons
https://bugs.kde.org/show_bug.cgi?id=456568 --- Comment #6 from David Chmelik --- (In reply to Nate Graham from comment #5) > > It's only about systemsettings: appearance: global theme > So only that page in System Settings? Any other ones? I tried to check all systemsettings (unsure was able because still are many (sub)levels, which is good) and didn't notice any more cases. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456568] Alt Accelerators don't appear on some buttons
https://bugs.kde.org/show_bug.cgi?id=456568 --- Comment #8 from David Chmelik --- Created attachment 150683 --> https://bugs.kde.org/attachment.cgi?id=150683&action=edit screenvideo no buttons have underlines -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" feature is missing
https://bugs.kde.org/show_bug.cgi?id=443723 --- Comment #21 from David Chmelik --- (In reply to Vlad Zahorodnii from comment #3) > > I for one used this surprisingly much, and I do consider my use-case rather > > regular in nature. > What did you use it for? I'm a mathematician/geometer/artist so have many obvious cases: specific-size graphics, learning GUI CS, even just some extreme user precision, some of which also happen multiple/many times during many hours daily. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456816] New: allow standard/normal analogue clock face
https://bugs.kde.org/show_bug.cgi?id=456816 Bug ID: 456816 Summary: allow standard/normal analogue clock face Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Allow standard/normal analogue clock face. STEPS TO REPRODUCE 1. Add analogue clock to panel 2. See non-standard 'trendy' style; look for standard/normal style: all 12 numbers (at larger sizes, optionally additionally also 05 to 60 seconds marks... at smaller sizes at least 12 marks.) OBSERVED RESULT Can't have standard/normal analogue clock face. At my panel size (72px on 27" 4K) can't always estimate time without getting up out of my chair and looking closer (with low-contrast Oxygen/Air styles, which Breeze probably increased this extremely bad trend of grey-on-white & grey-on-black.) Without 12 marks/numbers, takes longer to estimate time (maybe with mistakes) than digital clock, which takes longer than standard/normal analogue ones. EXPECTED RESULT Allow standard/normal analogue clock face. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.25 & Slackware64 15.1-current GNU Linuxes KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Most panels may be too small to show numbers, though I use 4K and in future will use 8+K, projection-/video-wall if/when affordable... would also be nice to be able to see clock larger... some people might want to drop-down; some might prefer standalone window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456278] panel (task manager, system-tray) icons sometimes move or flicker
https://bugs.kde.org/show_bug.cgi?id=456278 David Chmelik changed: What|Removed |Added Summary|Task Manager icons |panel (task manager, |sometimes move or flicker |system-tray) icons ||sometimes move or flicker --- Comment #3 from David Chmelik --- KDE programs--even not in system-tray (Okular, etc.)--are also affected, such as if selected while others are flickering (usually/always from being minimized/maximized to/from system-tray). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456278] panel (task manager, system-tray) icons sometimes move or flicker
https://bugs.kde.org/show_bug.cgi?id=456278 --- Comment #4 from David Chmelik --- KDE programs--even not in system-tray (Okular, etc.)--are also affected, such as if selected while others are flickering (usually/always from being minimized/maximized to/from system-tray). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455887] Sometimes windows from the same app don't get grouped until the grouping option is toggled off and back on again
https://bugs.kde.org/show_bug.cgi?id=455887 --- Comment #7 from David Chmelik --- Actually on any sort of taskbar update/action they ungroup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456816] allow standard/normal analogue clock face
https://bugs.kde.org/show_bug.cgi?id=456816 --- Comment #2 from David Chmelik --- Created attachment 150730 --> https://bugs.kde.org/attachment.cgi?id=150730&action=edit clock screen (In reply to Nate Graham from comment #1) > Are you saying that you want all the hour numbers to be visible, not just > the 12? Certainly. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 456916] New: analogue plain complete clock widget?
https://bugs.kde.org/show_bug.cgi?id=456916 Bug ID: 456916 Summary: analogue plain complete clock widget? Product: Oxygen Version: 5.25.3 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- Created attachment 150739 --> https://bugs.kde.org/attachment.cgi?id=150739&action=edit hard-to-read clock SUMMARY Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.) STEPS TO REPRODUCE 1. Add analogue clock widget. 2. Sometimes have trouble reading it. OBSERVED RESULT Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.) EXPECTED RESULT Option to have all numbers (preferably outside absolute position marks) and option for just black on white (Air light Oxygen theme) and plain (no pattern) white/light-grey on black (Oxygen dark theme). SOFTWARE/OS VERSIONS Linux/KDE Plasma: FreeBSD UNIX 8-13, KDE Neon 5 & Slackware 13-15 GNU/Linuxes KDE Plasma Version: 4, 5 KDE Frameworks Version: 4, 5 Qt Version: 4, 5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #8 from David Chmelik --- (In reply to Andrey from comment #6) > - Is 1. essential for 3? I think only step two is necessary. > - Can you reproduce on KDE Plasma Version: 5.24.80? We only use KDEP 5.25 on PCs with standard 101-key keyboards (keyboard layout systemtray icon used to work for but now doesn't) (and 5.25 on PC that has 101-key and 104-key keyboards and keyboard layout icon appears on (unless 101-key keyboard is unplugged, I presume)) but if there will be KDE Neon User LTS we can downgrade/reinstall. (In reply to Andrey from comment #7) > Wayland? No. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456931] New: full cascading?
https://bugs.kde.org/show_bug.cgi?id=456931 Bug ID: 456931 Summary: full cascading? Product: plasmashell Version: 5.25.3 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: 1.0 Created attachment 150754 --> https://bugs.kde.org/attachment.cgi?id=150754&action=edit full cascading SUMMARY KDE imitated Windows 95 partial but not full cascading menu but should have full option (to immediately see everything and select faster). STEPS TO REPRODUCE 1. Use or upgrade to Kicker. 2. Fill up main menu or a submenu to beyond screen. 3. Cascade (slow). OBSERVED RESULT KDE imitated Windows 95 partial but not full cascading menu but should have full option (to immediately see everything and select faster). If menu extends past screen, with partial cascading you can't immediately see everything then must use scroll-bars or mouse wheel (takes 20 scrolls on some our menus four times long as average (1920x1080) screen and even 10 on my 4K) but full cascading menu extends more columns immediately sees, for which you can either scrollover or move mouse to (both much faster). EXPECTED RESULT Full cascading option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5, Slackware 13 to 15.1-current. KDE Plasma Version: 4, 5 KDE Frameworks Version: 4, 5 Qt Version: 4, 5 ADDITIONAL INFORMATION KDE is almost three decades behind the times in not having (fastest) full cascading! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #10 from David Chmelik --- (In reply to Andrey from comment #9) > Can you reproduce on wayland? On family PC with only 101-key IBM model M keyboard with Wayland, the icon for keyboard layout icon reappears but has so many other problems (including some found after the test) they won't be able to use it. I want to avoid Wayland on my own PC but would like keyboard layout to work as used to in X Window System. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456931] full cascading?
https://bugs.kde.org/show_bug.cgi?id=456931 --- Comment #2 from David Chmelik --- Do you know how to intend more than one thing? That's what an option is--a choice. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 451767] Add Open-Meteo to providers
https://bugs.kde.org/show_bug.cgi?id=451767 David Chmelik changed: What|Removed |Added CC||dchme...@gmail.com --- Comment #1 from David Chmelik --- Good idea; there's currently only one in KDEP5--sometimes down; what happened to the several werein KDEP4?! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457255] New: deselect/disappear after restart
https://bugs.kde.org/show_bug.cgi?id=457255 Bug ID: 457255 Summary: deselect/disappear after restart Product: dolphin Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: dchme...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Some panels deselect/disappear after restart: 'information' though haven't checked all (only not terminal)... doesn't always happen but after certain number restarts or maybe a crash 'information' deselects/disappears. STEPS TO REPRODUCE 1. Use Dolphin daily including after restarts/reboots. 2. Wait for 'information' disappear: it will! OBSERVED RESULT Some panels deselect/disappear after restart: 'information' though haven't checked all (only not terminal)... doesn't always happen but after certain number restarts or maybe a crash 'information' deselects/disappears. EXPECTED RESULT If user sets panels display and has a restart/crash don't unset them display. SOFTWARE/OS VERSIONS Linux/KDE Plasma: P4, 5 KDE Plasma Version: P4, 5 KDE Frameworks Version: 4, 5 Qt Version: 4, 5 ADDITIONAL INFORMATION Maybe never happened for 'folders', 'places' unless major reset most/all dolphin settings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457255] deselect/disappear after restart
https://bugs.kde.org/show_bug.cgi?id=457255 David Chmelik changed: What|Removed |Added OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457255] deselect/disappear after restart
https://bugs.kde.org/show_bug.cgi?id=457255 David Chmelik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Chmelik --- The problem was thinking F11 might maximize Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] New: KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 Bug ID: 457370 Summary: KDE Plasma typically immediately halts from medium-to-high workloads Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY KDE Plasma typically immediately halts from medium-to-high workloads STEPS TO REPRODUCE 1. Open something over 10 such as preferably 15 to 20+ programs as fast as you can, for which I suggest add panel launchers to start each in less than 1sec if possible. OBSERVED RESULT KDE Plasma can't handle medium-to-high workloads. If you open enough programs fast it may halt KDE, or at least will halt the panel and cause general slowdown, for which same number of programs in less powerful X window managers (WM) or desktop environments (DE) such as XFCE never halt from this and are even usually still much faster than KDE (I don't try or compare to GNOME/MATE because overall is among worst but would try and compare to TDE, (Ns)CDE which are probably best after some bugfixes). EXPECTED RESULT Start all programs the user wants and if they open a large number don't halt the panel--don't 'update' it which may halt it (updates being their task manager flashing every time they have activity?) Option: opt-out of panel task manager updating/flashing ever. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 from Slamd64 (unofficial) to Slackware64 13 to 15+current GNU/Linux, sometimes FreeBSD UNIX 7 to 13.1 KDE Plasma Version: 4, 5 to 5.25.3 KDE Frameworks Version: 4, 5 to 5.96.0 Qt Version: 4, 5 to 5.15.5 ADDITIONAL INFORMATION KDE3 was fine but halting has always been an intermittent critical problem from Plasma 4 to 5 current version, and Slackware even delayed KDEP5 (maybe years) because people were saying wasn't production-ready (still unsure is 100% production-ready). In this situation if you kill plasmashell and restart, it often immediately (even with 20+ programs) works well (but typically rearranges programs out-of-order you moved them in) but occasionally you may lose all programs that were minimzed to system tray. If you don't kill plasmashell you may wait one-half to two hours (I haven't waited longer but went away and came back, killed plasmashell) or more to see if it started responding to user yet. list of what I start (and usual order) which if something over 10 and almost always if 15+ and so far always 20+ always halt KDE/panel Konsole (always) Dolphin (always) KATE (always) NotepadQQ (sometimes) Libre Office (occasionally or always later after hours/days network programs) MComix (occasionally or always later after network programs) Okular (occasionally or always later after network programs) XMMS1 or Open Cubic Player or DeadBeef (occasionally or usually later after network programs) Thunderbird Mail (always if using any neworking) Pan NNTP newsreader (usually if using any networking. Almost 1,000 NNTP news-/discussion-groups) HexChat Internet Relay Chat (almost always if using any networking. 10+ servers/networks and 120+ channels) Pidgin instant messaging (IM) (usually or almost always later after web browsers. Almost 15+ accounts ) Mozilla/Pale_Moon web browser (almost always) Firefox web browser (usually) Chromium web browser (almost always if using any networking) Konqueror and/or Falkon web browsers (occasionally or always later in any short session if using any networking) Element matrix IM (usually) Discord IM (usually) Slack IM (usually) ICQ IM (occasionally) Skype IM (usually) Jitsi-meet IM (occasionally) Transmission-QT or GTK (almost always or always within 24hrs) Nicotine+ (almost always or always within 24hrs) EiskaltDC++ (lmost always or always within 24hrs) Geeqie and/or Eye of MATE (occasionally or always after hours/days) GIMP (occasionally or often later) KolourPaint (occasionally) InkScape (occasionally) I only start (or even think of) some less-used ones minutes/hours/days later. If I start first four slowly then subsequent more slowly, waiting some tens seconds or even 1+ minutes, I almost never have the problem. A typical session always has 10 programs above; usually 15+, and if I start daytime with IM/IRC then 20+ and at least if it doesn't crash and then writing/programming & graphics & audio later, then maybe 30+ including miscellaneous/testing (utilities, compiling, audio/trackers, p2p, trying others). Of course, it's almost always on three monitors (1600x1200, 4K, 1920x1080 latter also being drawing pad) unless I have a problem and quit soon (then only 4K). This isn't even including at least hours later I eventually start doing scientific computing & compiling with 24 to 28 of 32 5950X threads with 64GB RAM, so i
[plasmashell] [Bug 457370] KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #1 from David Chmelik --- I probably should've also said I have 12+ accounts (previously & eventually 16) in Thunderbird Mail, and 100+ Mozilla/Pale_Moon tabs, which is a lot, as is my HexChat IRC and especially Pan NNTP usage but none of these programs on their own (after file & writing utilities) were ever enough to cause halt on their own or even just two of these... always had to be some number more than 10 programs including web browsers and usually IM/P2P, but it's more opening speed than definite number (except maybe if I was using long-term/stable/user OS release weeks/months with no kernel upgrade so didn't reboot then ran out of RAM from memory leaks which are still a thing) but I use current/development/testing OS and upgrade kernel & reboot every some days/weeks. So it wasn't since Slackware 14.2 I could test running for weeks/months seeing if medium-to-high workloads halted (from memory leaks) and as for FreeBSD I generally use stable so may not be able to test case anymore of trying to have as much uptime you can while running sometimes 30+ programs (in such case I occasionally also edit many large files in GIMP & InkScape until I almost run out of RAM, wish I had 256+GB.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #12 from David Chmelik --- I don't entirely understand merge request 951 but are you saying may be result of (dis)connecting devices? When I boot I almost never (dis)connect something, not even external boot drive/disc, but haven't had keyboard layout icon for maybe 1+ years anyway so (as 99% happens without (dis)connecting devices) seems my bug is more than just what's in merge request 951 but don't understand it enough to know whether what I reported is related/superset to 951. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456747] attempting select application menu entry style crashes
https://bugs.kde.org/show_bug.cgi?id=456747 --- Comment #3 from David Chmelik --- Slackware generally doesn't compile in debugging but alternatively compiling KDE would be too big project so I did reported to Slackware but don't know there's anything else I can do here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #3 from David Chmelik --- Confirmed: more parts (than taskbar) or KDE in general: following test script soon apparently (waited maybe one-half hour) permanently halted KDE (within few minutes no I/O despite barely 10% or fewer CPU (water-cooled overclocked) resources used entire time--not enough parallel processing(!)--and only a few programs placed windows) but worked so perfectly/quickly in XFCE (so clearly optimization/parallelism rather than hardware problem) I use there to save great deal time/effort starting daily programs. I was able to out of KDE but not back in except only to see KDE's terminal output/errors: KDE couldn't even redraw (in at least two separate tests). I would've put it before rest of my comment in code block section but don't see you have formatting/mark(up|down) documented here. I'm willing to test more soon/eventually (maybe today) but was enthusiastic about KDE3 as were most KDE user scientists/programmers, whom almost all preferred older KDEB,1,2,3 (when I only knew twm) and whom most I know haven't used it maybe 15 years... it's bugs like this (and other crash/major/grave/criticals even 15 years back untested then falsely marked 'intentional') made me lose all enthusiasm and now most trust/faith that power users/programmers will even be equally considered... I could go on about dozens/hundreds aspects but that'd be best for forum.kde.org . #!/bin/sh dolphin 1>/dev/null 2>&1& kate 1>/dev/null 2>&1& mcomix 1>/dev/null 2>&1& okular 1>/dev/null 2>&1& xmms 1>/dev/null 2>&1& birdtray 1>/dev/null 2>&1& pan 1>/dev/null 2>&1& hexchat 1>/dev/null 2>&1& pidgin 1>/dev/null 2>&1& palemoon-bin 1>/dev/null 2>&1& firefox 1>/dev/null 2>&1& chromium 1>/dev/null 2>&1& element 1>/dev/null 2>&1& discord 1>/dev/null 2>&1& slack 1>/dev/null 2>&1& skypeforlinux 1>/dev/null 2>&1& transmission 1>/dev/null 2>&1& nicotine 1>/dev/null 2>&1& eiskaltdcpp-qt 1/dev/null 2&1& -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] KDE Plasma typically immediately halts from medium-to-high workloads
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #4 from David Chmelik --- I meant 'power users, general/polymath scientists/programmers & Renaissance people'. Obviously KDE is adequate for average users who only use one program at a time but even for some them I administer KDE Neon for in recent years (even since Kubuntu days) are telling me KDE is slow at times. I can no longer recommend it to scientists/polymaths (whom do as much work in as many programs as me) and don't know how much longer for average & power users either. More recent KDE Neon running only either more recent Firefox or Chromium (which has/had memory leaks, maybe some repaired) seem acceptably-fast for them though (now getting off-topic) some user theme material has disappeared & reappeared & disappeared in Neon so they may be switching back to Kubuntu... and they never ask/report online so it's either Neon tests all historical default KDE themes or I report it or users switch away. -- You are receiving this mail because: You are watching all bug changes.
