[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=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 #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.
[kde] [Bug 457401] (re)using CDE-inspired aspects (inspired by Windows 3)?
https://bugs.kde.org/show_bug.cgi?id=457401 --- Comment #1 from David Chmelik --- Intended importance is 'wishlist' which I forgot about because made suggestions which would save users a large amount of time daily but were just closed rather than maybe being considered by more than one person. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457401] New: (re)using CDE-inspired aspects (inspired by Windows 3)?
https://bugs.kde.org/show_bug.cgi?id=457401 Bug ID: 457401 Summary: (re)using CDE-inspired aspects (inspired by Windows 3)? Product: kde Version: unspecified Platform: Other OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY I read KDE's name was inspired by CDE which I know imitated Win3 which I preferred aspects (but seem absent). STEPS TO REPRODUCE 1. Read history KDE name was inspired by CDE. 2. Look for superior CDE usability (Windows 3, Win3-inspired). OBSERVED RESULT I read KDE's name was inspired by CDE which I know imitated Win3 which I preferred aspects. Win3 had program manager/groups which was still usable in Win95/98 (and WinME?). I always liked program manager/groups but always abhorred (to this day) Win95 (to Win10) inferior start menu which became (Ns)CDE & KDEs kmenu/kicker/kickoff. Win3 program groups show any or all groups of only-related programs wth large/recognizable icons and could start as many you want in one go from still-open groups and be reminded what else one might want/need to start (or optionally minimize). Start & applications menus were regression to one-at-a-time text & less-reocgnizable small icons: rather than one go you reopen menu over & over, maybe 10 or 20+ times (typically 20 to 30+ for me and I know some who use more) let alone mouse slips on very position-sensitive menu that opens/causes many mistakes and can take many more seconds to reopen than a still-program group, and when you start a few/couple and are doing another but then one takes 'current focus' status and closes to draw over start/application menu (or even doesn't draw over at all but goes to other side but still closes menu(!))) and in contrast start/application menus can't remain open for reminder while using other programs. I'd like back whatever Win3-style KDE program groups--whatever you call them--may have made inspired by CDE (or do they still exist hidden? Then unhide them) and might even remove kicker afterwards, because that Win95 aspect always was--and still is--worst (and has only gotten worse as in its newer-style imitation reported elsewhere). Apparently some KDE (and GNOME/Ubuntu/etc.?) people realized Win3 had a good idea and Win3 start menu was a regression, but maybe mostly weren't win3 users, because they made almost-similar fullscreen menu/launcher--also inferior to Win3: can't view all program groups same time as using other programs. No other UI was as good except classic Apple with sytem menu bar that could have each application menu bar attached/underneath (as in KDE3, but of course both lacked superior Win3-style program groups, and Windows always lacked superior Apple-style top bars). I was most productive in (Apple &) Win3: I much more quickly saw what I had, and started all I wanted from all groups in one go, but still saw what else I may use later, or otherwise minimized, and could come back and do same repeatedly. KDE-style launchers were almost as good until I filled half taskbar with 20 or 30+ most-used programs but of course unable to immediately see related utilities. EXPECTED RESULT Allow/add all historical menu/launcher types from where you get your name. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NetBSD & FreeBSD & Slackware post-2002-4-3 (and maybe earlier) to current-day KDE Plasma Version: 3, 4, 5 to 5.25.3 KDE Frameworks Version: 3, 4, 5 to 5.96.0 Qt Version: 3, 4, 5 to 5.18.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457409] New: Accidentally moving out of tab bar's y-coordinate range stops movement
https://bugs.kde.org/show_bug.cgi?id=457409 Bug ID: 457409 Summary: Accidentally moving out of tab bar's y-coordinate range stops movement Product: kate Version: 22.04.3 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Accidentally moving out of tab bar's y-coordinate range stops movement. STEPS TO REPRODUCE 1. Try to move tab. 2. Keep moving but accidentally slightly move above or below tab bar. 3. Tabs tops and one must move back within tab bar's y-coordinate range--often multiple times--to resume moving. OBSERVED RESULT Accidentally moving out of tab bar's y-coordinate range stops movement. Tab stops and isn't even positioned right but a space appears... one must move back within tab bar's y-coordinate range--often multiple times--to resume moving. EXPECTED RESULT Ingore y-coordinate moving tabs; let user continue: only keep checking x-coordinate. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 15 KDE Plasma Version: 5 to 5.25.3 KDE Frameworks Version: 5 to 5.96.0 Qt Version: 5 to 5.15.5 ADDITIONAL INFORMATION Despite TVs get larger & larger, monitors with comparative resolution get smaller & smaller: much, much smaller pixels than older monitors, so some 8K are same size as 4k are smaller than some 1080p. All GUI elements get too small: panels, titlebars, menubars, toolbars, tabbars, infobars, scrollbars, so you CANNOT assume a user will even easily be able to stay within an element's range when still acting on it so absolutely shouldn't expect/make them to. Best/original tab definers like Firefox don't care if you move out of tab bar y-coordinate range. Worst UI implementers such as Google (zero design sense) do same and worse--if you move out-of-range tab will pop out as a new window. Best to not do that and not stop until user releases (unless some users want option if they move out-of-range, then stop, but would they be crazy or what?) -- 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.
[plasmashell] [Bug 457708] Lost the ability to display the layout's label on top of the flag
https://bugs.kde.org/show_bug.cgi?id=457708 --- Comment #13 from David Chmelik --- In reply to Andrey from comment #12) > As you tried it, were there any benefit in direct kxkbrc editing instead of > putting the text in the KCM UI? Text configuration has it's place for theoretical computer science specific practical implementations in computer hardware/firmware/driver/OS & programming languages design/engineering & usage, command-line/shells, and all should be available to power users but unnecessary, and past necessity in GNOME/MATE is why I won't ever even consider those X desktop environments (DE) even though no longer require, so I can't say there's ever any GUI text configuration benefit other than should always be an option for every option/aspect/detail, but I'd rather not need I won't mind having to (re)set/hack this for long/indefinite time in a file in family PCs and--when can try KDE again--my own PC, but more urgent/critical bugs prevent me from retrying KDE on mine (as much I'd like to, gave up earlier Summer 2022.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457708] Lost the ability to display the layout's label on top of the flag
https://bugs.kde.org/show_bug.cgi?id=457708 --- Comment #11 from David Chmelik --- (In reply to Andrey from comment #10) > You can try to directly put unicode text to label by opening > ~/.config/kxkbrc in your favorite text editor. Works but would sound too involved/difficult for many/most users. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 454030] can't use Google Drive (no longer allowed because of authentication)
https://bugs.kde.org/show_bug.cgi?id=454030 --- Comment #2 from David Chmelik --- (In reply to Elvis Angelaccio from comment #1) > Please make sure you are using kio-drive compiled with the KAccounts backend. How can I find out? Will it be in KDE Plasma 5 (KDEP5, KDE5) or only 6? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459438] New: doesn't use system/printer settings
https://bugs.kde.org/show_bug.cgi?id=459438 Bug ID: 459438 Summary: doesn't use system/printer settings Classification: Applications Product: okular Version: 22.08.1 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Okular doesn't use system/printer settings; we use British & American English and set some (locale, programs) locale to British English, but when I try to print from Okular, despite my PC (British English locale) and network printer settings' both are set/overrided to USA letter print-format, Okular preselects an International Standards Organization (ISO) letter print-format: A4 (British Isles & ISO/mostly-worldwide), and other family PCs (past British, now USA English locale with only date/clock format override) have/had mixed language settings same behaviour (we occasionally use some French, German, Spanish, Russian, Greek locale/software keyboards). STEPS TO REPRODUCE 1. Set mixed locale system/programs/printer: PC whatever but override printer to different dialect locale letter print-format (different shape/size). 2. Set Okular to system dialect (didn't automatically use mine... minor error many/most/all KDE programs have; I'll maybe report later). 3. Open Okular print menu for any text/ebook. OBSERVED RESULT Uses neither default PC letter setting nor (network) printer's default. EXPECTED RESULT Preselect use PC/printer letter setting: at least your PC's, if not (network) printer's (if different, I don't know). SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: Slackware 15 (stable, current) & KDE Neon 5.25 GNU/Linuxes (presumably all OS with Okular 20+... can check most/all main *BSD on request) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I've never printed A4 with current printer nor this KDE/Okular configuration (erased/restarted .kde*, .config/(k*|okular) Spring 2022). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457515] New: window decorations disappear
https://bugs.kde.org/show_bug.cgi?id=457515 Bug ID: 457515 Summary: window decorations disappear Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave 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 Window decorations disappear: if users had selected Plastik (or some others?) its buttons disappear from all open programs leaving blank titlebar and leaving them thinking their PC has crashed. STEPS TO REPRODUCE 1. Run systemsettings. 2. Select Plastik (or some others?). OBSERVED RESULT Window decorations disappear: if users had selected Plastik (or some others?) its buttons disappear from all open programs leaving blank titlebar and leaving them thinking their PC has crashed. EXPECTED RESULT Don't disappear currently-installed standard window decorations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.25.3 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Happened in some earlier KDE Neon versions. Doesn't happen in superior strictly UNIX[-like] OS like FreeBSD UNIX, Slackware GNU/Linux; don't know about Kubuntu GNU/Linux but of not fixed in Neon it'll probably happen in the rest. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429276] folders is called F
https://bugs.kde.org/show_bug.cgi?id=429276 David Chmelik changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #13 from David Chmelik --- Fix is lock dolphin 'places'. -- 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 #5 from David Chmelik --- Of course, I removed taskbars; should I remove anything else, and if I do is it going to erase all my settings/customization (as happened with taskbars)? -- 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 #6 from David Chmelik --- Of course, I removed task managers; should I remove anything else, and if I do is it going to erase all my settings/customization (as happened with task managers)? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457512] New: inconsistent menus
https://bugs.kde.org/show_bug.cgi?id=457512 Bug ID: 457512 Summary: inconsistent menus Product: konsole Version: 22.04.3 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Inconsistent menus: right button menu item 'switch profile' underlined keystroke eventually changes from 's' to 'w' (may need to wait hours) and may change back & forth. STEPS TO REPRODUCE 1. Run Konsole. 2. Press right mouse button in main window area. 3. Try to select menu item 'switch profile': underlined keystroke eventually changes from 's' to 'w' (may need to wait hours) and may change back & forth. OBSERVED RESULT Inconsistent menus: right button 'switch profile' menu item underlined keystroke eventually changes from 's' to 'w' (may need to wait hours) and may change back & forth.. EXPECTED RESULT Pick one keystroke and stick with it; don't continually change it and confuse users (and prevent them from learning simple/standardized Konsole usage). SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 7+, Slackware 13+, KDE Neon * KDE/Plasma Version: 3, 4, 5 to 5.25.4 KDE/Frameworks Version: 3, 4, 5 to 5.96.0 Qt Version: 3, 4, 5 to 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457513] New: inconsistent menus:
https://bugs.kde.org/show_bug.cgi?id=457513 Bug ID: 457513 Summary: inconsistent menus: Product: systemsettings Version: 5.25.4 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Inconsistent menus: underlined 'apply' button keystroke everywhere varies among 'a', 'p', 'l', 'y'. STEPS TO REPRODUCE 1. Run systemsettings. 2. Go to all menus with 'apply' button. 3. Try to select 'apply': button keystroke everywhere varies among 'a', 'p', 'l', 'y'. OBSERVED RESULT Inconsistent menus: underlined 'apply' button keystroke everywhere varies among 'a', 'p', 'l', 'y'. EXPECTED RESULT Pick one keystroke and stick with it: don't everywhere vary it and confuse users (and prevent them from learning simple/standardized systemsettings usage). SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 7+, Slackware 13+, KDE Neon * KDE/Plasma Version: 3, 4, 5 to 5.25.4 KDE/Frameworks Version: 3, 4, 5 to 5.96.0 Qt Version: 3, 4, 5 to 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444082] wrong window behaviour on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=444082 David Chmelik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from David Chmelik --- Happens similarly in other X Window System (X) window managers (WM) & desktop environments (DE) also so seems upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] bad keyboard layout counts
https://bugs.kde.org/show_bug.cgi?id=457550 --- Comment #1 from David Chmelik --- Since resultant zero usability causes people to reboot I want to change it to major/grave (beyond crash, which isn't a crash but for usability major/grave and even actually critical (though I'd prefer that describe worst/system crashes)). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] New: bad keyboard layout counts
https://bugs.kde.org/show_bug.cgi?id=457550 Bug ID: 457550 Summary: bad keyboard layout counts Product: plasmashell Version: 5.25.4 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY Keyboard layouts require minimum 2/3 (of three) layout to be non-spare (if there are only two, neither can be spare) and I thought had maximum but the latter was either older v5.n or fluke or confusion/imagination (so may not matter). STEPS TO REPRODUCE 1. Add keyboard layouts (such as dialects/languages). 2. Try to make them spare. OBSERVED RESULT For a layout to be non-spare you're required to add two more layouts but then only one can be spare. People accidentally press layout which immediately may change to something unexpected/unknown... exacerbated by you don't even seem to be able to have custom layout name anymore, nor flag simultaneously, so won't necessarily even know it changed. EXPECTED RESULT Any & all extra layouts should be able to be spare (or not, and not necessarily in order) so one can require drop-down (to avoid confusion/reboot) instead of minimum 2/3 (of three) non-spare and press layout to change (often accident). There should be no maximum fewer than all layouts. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 5+, Slackware 8+, NetBSD 1+, Neon * KDE/Plasma Version: 3, 4, 5 to 5.25.4 KDE/Frameworks Version: 3, 4, 5 to 5.96.0 Qt Version: 3, 4, 5 to 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457708] New: keyboard layout indicator limitations/regression
https://bugs.kde.org/show_bug.cgi?id=457708 Bug ID: 457708 Summary: keyboard layout indicator limitations/regression Product: systemsettings Version: 5.25.4 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: butir...@gmail.com Target Milestone: --- SUMMARY Keyboard layout indicator limitations/regression exists: can no longer have custom label including text on flag. STEPS TO REPRODUCE 1. Add keyboard layouts (such as more dialects/languages). 2. Edit indicator. OBSERVED RESULT Keyboard layout indicator limitations/regression exists: can no longer have custom label including text on flag. EXPECTED RESULT Allow set custom label (chosen text/flag/both). SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 13+, Slackware 15+, NetBSD 9+, OpenBSD 7+, Neon 5+ KDE Plasma Version: 5.2n.m KDE Frameworks Version: 5.9n.m Qt Version: 5.1n.m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] Option to not switch layouts on click; require the use of the context menu to switch with a pointing device
https://bugs.kde.org/show_bug.cgi?id=457550 --- Comment #7 from David Chmelik --- (In reply to Andrey from comment #5) > I think we could remove min two main layouts restriction as I can't recall > if it gives us any real benefits. Such number of minimum to (possible/past) maximum layouts are the issue (as in original bug description/title) and minimum two main ones has only ever been hindrance for me and everyone I know. When labels could be flags only without text it was exacerbated due to dialects: no way knowing one is using their country's English or international layout only for dialect/characters elsewhere (unfortunately requiring same flag). For that case for average users who forget, they accidentally press it and don't notice anything until things start going wrong. They use Wayland, but I don't; proper technical writing is full term then define acronym afterwards, but anything 'on layout change' is zero help if a user comes to a PC after change was made. I've always only known main layouts as those not allowing drop-down and spare layouts as those requiring; this issue never has primarily been about drop-down which is only an effect of specific numbers of layouts. Rewriting the issue to a derived aspect is over-simplification but in fact complication. I never asked to require drop-down for main layouts, just that being forced to have two minimum (and any maximum other than all) is a bad number (as described and not everyone is bilingual nor necessarily even uses more than one dialect) (so I won't be writing a duplicate report what I already very clearly put as first part of original description/title). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] bad keyboard layout counts
https://bugs.kde.org/show_bug.cgi?id=457550 David Chmelik changed: What|Removed |Added Summary|Option to not switch|bad keyboard layout counts |layouts on click; require | |the use of the context menu | |to switch with a pointing | |device | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457708] Lost the ability to display the layout's label on top of the flag
https://bugs.kde.org/show_bug.cgi?id=457708 --- Comment #2 from David Chmelik --- (In reply to Nate Graham from comment #1) > The ability to set a custom label is still there, it just moved into System > Settings Label doesn't mean only plaintext but its entire area including all other text/graphics (see typical labels in clothes, on food packages, etc.). > Any specific reason you want it back? Already stated can be re-added (bug 444864) after new report. Only flags are quickly-noticeable but, due to dialects, useless/hindrance on their own; black on grey (or dark themes maybe unreadable black on dark grey) isn't noticeable, so without both (or everything custom for dialects) it takes longer before users notice/recall which layout is set. It's comically absurd to create things users use and then remove them and then ask use case (happening since KDE3's end and indicates critical problems in a project). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] keyboard layouts should allow only one main layout within total (main and spare) of two to unlimited
https://bugs.kde.org/show_bug.cgi?id=457550 David Chmelik changed: What|Removed |Added Summary|remove min 2 main layouts |keyboard layouts should |restriction for option to |allow only one main layout |not switch layouts on |within total (main and |click; require the use of |spare) of two to unlimited |the context menu to switch | |with a pointing device | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] keyboard layouts should allow only one main layout within total (main and spare) of two to unlimited
https://bugs.kde.org/show_bug.cgi?id=457550 --- Comment #10 from David Chmelik --- (In reply to Andrey from comment #8) > Sorry, the Summary you provided is not descriptive. It was but needed more detail. > Returning corrected description. That new one seemed excessive and I never mentioned pointing devices (but that it's not about those, only minimum main & possibly-seen maximum total layouts): some X window managers (WM) & desktop environments (DE) don't need pointing devices and if that is (or will be) possible with X/KDE then I'd want to learn/use (can be faster with more keyboard keystrokes). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457708] layout indicator should allow custom label
https://bugs.kde.org/show_bug.cgi?id=457708 David Chmelik changed: What|Removed |Added Summary|Lost the ability to display |layout indicator should |the layout's label on top |allow custom label |of the flag | --- Comment #6 from David Chmelik --- (In reply to Andrey from comment #3) > Let's not misuse the term. Label is always text-only here [...] 'Keyboard layout indicator: configure: configure: label' column is both text & flag! > (but you could try to put unicode symbols there). That'd be excellent/best if works in future (doesn't yet because flags are newer unicode/emojis that paste in wrong). (In reply to Andrey from comment #4) > text on flag was hardly distinguishable even on old applet. It always was very distinguishable for me (may depend on flag). > There should be really smart reasons to re-add this, I would rather solve > not noticeable label if that's the problem. For flags, customization is necessary because of dialects; we (me and users whose PCs I administer) use British Isles (multiple) & USA English (with international layouts only for dialects elsewhere) so flags alone are worse than useless: dialect can only be indicated by retaining text on flag or (another idea) changing flag. Same for French, German, Portugese, Russian, Spanish (multiple dialects/languages in countries I'm unsure even label over one type of flag is enough). Dark Oxygen & dark Breeze lately had few/no system tray icon noticeability problems but can't check others until I have indicator for my layouts (disappeared, reported) or users whose PC I administer use dark themes (unlikely ever)... other themes would be their own issue, anyway. -- 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.
[systemsettings] [Bug 444864] Poor UI for configuring label to be displayed over flag
https://bugs.kde.org/show_bug.cgi?id=444864 --- Comment #8 from David Chmelik --- (In reply to Nate Graham from comment #1) > One issue per bug report please. :) Let's use this one to track the > inability to overlay the label on top of the flag. That was a (and for me, #1) main aspect but became focused on my minor afterthought of non-Latin/-English alphabet usage Andrey replied then asked (re)open keyboard layout indicator flag with text issue, so I did (duplicate besides afterthought not in above steps nor observed & expected results). > This is a fairly crummy and undiscoverable UI, though. Can you file a > separate bug report about that? You can file it to systemsettings | > key_keyboard. Thanks! You mean that the label column contains flag (normally) but text only when selected? I suppose. I memorized so no issue but agree is to others (whom you haven't told) so will report that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457768] New: hidden text in keyboard layout indicator label configuration
https://bugs.kde.org/show_bug.cgi?id=457768 Bug ID: 457768 Summary: hidden text in keyboard layout indicator label configuration Product: systemsettings Version: 5.25.4 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: butir...@gmail.com Target Milestone: --- SUMMARY 'Keyboard layout indicator: configure: configure: label' shows flag but hidden/invisible text label only visible when selected. STEPS TO REPRODUCE 1. Select (right mouse button) keyboard layout indicator or go to its system settings. 2. Select 'configure'. 3. Select 'configure' (again). 4. Select a (layout) row 'label' column entry. OBSERVED RESULT Keyboard indicator layout label is shown as flag; no one knows of text aspect unless selects a (layout) row 'label' column entry. EXPECTED RESULT Don't hide anything not selected to hide. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 13+, Slackware64 15+, KDE Neon 5.25 KDE Plasma Version: 5.2n.m KDE Frameworks Version: 5.9n.m Qt Version: 5.1n.m ADDITIONAL INFORMATION (In reply to Nate from bug 444864 comment #1) > As for custom text, the new applet does actually respect custom text set in > the KCM. You have to set it in the KCM, though. You can do this by > double-clicking on the "Label" cell in the table. There, you can set > whatever text you want. I just confirmed that this works for me. > > This is a fairly crummy and undiscoverable UI, though. Can you file a > separate bug report about that? You can file it to systemsettings | > key_keyboard. Thanks! I didn't find key_keyboard (maybe this was the right place). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457708] Lost the ability to display the layout's label on top of the flag
https://bugs.kde.org/show_bug.cgi?id=457708 --- Comment #8 from David Chmelik --- (In reply to Andrey from comment #7) > "Label" is only a text in this context so wrong Summary. It started by saying 'Keyboard layout indicator'; isn't that the main graphical/text area--icon? 'Icon' doesn't imply (nor exclude) text. I'll say 'keyboard layout indicator'. > Might be just pasting problem. I recall I managed to put Emojis in Label > text field and it worked. It was Wayland (I consider under development/experiment/testing) KDE Neon but I could (after bug 456391) try X (preferable/stabler). > There might be also just Emojis package missing in system. On KDE Neon?! > So no problem for Dark Oxygen & dark Breeze then? I think (99%) were fine earlier 2022 but don't use them on my PC anymore (except icons, GTK) and unlikely family PC will use them. Maybe later I can double-check. > > but can't check others until I have indicator for my > > layouts (disappeared, reported) > bug number? Bug 456391 (being worked on weeks/months by some people, which for my PC is more important, and for family PC clearly-indicated layout is more important, but they have more important usage (international/family documents/correspondence, not just getting single-quotation marks, pound monetary sign, attempting French & Germanic & Slavic languages, and editing Greek mythology texts (my usage))). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457401] (re)using CDE-inspired aspects (inspired by Windows 3)?
https://bugs.kde.org/show_bug.cgi?id=457401 David Chmelik changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from David Chmelik --- This feature was actionable 32 years ago including in what inspired KDE. It's one of the simplest feature requests. -- 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 #5 from David Chmelik --- (In reply to Nate Graham from comment #4) > So you're saying that the underlined letter for alt-accelerators in menus > aren't consistent? Am I understanding the issue? I don't recall term 'alt-accelerators' but think so: that I described that and every case I found (though I guess should be different bug reports). 'Konsole -> right mouse button -> switch profile' first has s underlined but later w then continually switches back & forth every few hours. Systemsettings underlines a, p, l, y on different menus' 'apply' buttons. -- 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
[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.
[systemsettings] [Bug 457513] Apply button has a different Alt accelerator key depending on the page
https://bugs.kde.org/show_bug.cgi?id=457513 --- Comment #2 from David Chmelik --- (In reply to Nate Graham from comment #1) > [...] If we could guarantee the use of US English [...] Hopefully also standard/definitive/British English for which all words would presumably be same (as well as most/all international English)... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457645] New: keyboard layout indicator limitations/regression
https://bugs.kde.org/show_bug.cgi?id=457645 Bug ID: 457645 Summary: keyboard layout indicator limitations/regression Product: systemsettings Version: 5.25.4 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: butir...@gmail.com Target Milestone: --- SUMMARY Keyboard layout indicator limitations/regression exists; can no longer have custom text label on flag and when editing label (unclear how) won't change in editor: only on panel/systemtray/indicator, beforehand making you think can't change. STEPS TO REPRODUCE 1. Add keyboard layouts (such as for more dialects/languages). 2. Edit indicator text and/or flag. OBSERVED RESULT Keyboard layout indicator limitations/regression exists; can no longer have custom text label on flag and when editing label (unclear how) won't change in editor: only on panel/systemtray/indicator, beforehand making you think can't change. EXPECTED RESULT Should be able to set custom label /and/ custom flag (such as choosing international English keyboard layout for characters across Atlantic, allow overriding flag for clarity) and update within editor (in clear way) and not just on panel/ssytemtray/indicator. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 13+, Slackware 15+, NetBSD 9+, Neon 5+ KDE Plasma Version: 5.2n.m KDE Frameworks Version: 5.9n.m Qt Version: 5.1n.m ADDITIONAL INFORMATION I use UK English with some USA settings including USA custom locale & spare keyboard setting: international with dead keys for British punctuation/quotation & moetary pound symbols, despite being USA layout I don't consider it one and would like to override USA with UK flag to usage clear. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457645] keyboard layout indicator limitations/regression
https://bugs.kde.org/show_bug.cgi?id=457645 --- Comment #1 from David Chmelik --- Though the main limitation used to be standard so this is a regression (and resulting confusing effects could be considered major/grave/critical) it's possible this is more a minor/wishlist level issue... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] bad keyboard layout counts
https://bugs.kde.org/show_bug.cgi?id=457550 --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #3) > So you want to make it so that the Keyboard Layout System Tray applet never > changes layout when clicked, and you have to explicitly choose a layout from > context menu to switch? Do I have that right? That's the main/last part; yes: there's no reason users should be forced to have two main layouts rather than maximum one or any number they choose.. even all main layouts, on the other hand, anything from one to all main, or any combination of main and spare. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457649] New: unmovable false default profile
https://bugs.kde.org/show_bug.cgi?id=457649 Bug ID: 457649 Summary: unmovable false default profile Product: konsole Version: 22.04.3 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Unmovable false default profile: I use my own profiles including set one default, but recent Konsole versions have their own 'default' when you press right mouse button in terminal area for menu, first is KDE's default falsely-labelled in the case (such as myself) one has one's own default and KDE's can't be moved below true default nor alternatives. STEPS TO REPRODUCE 1. Create Konsole profiles including new default. 2. Look for true default. OBSERVED RESULT Unmovable false default profile: I use my own profiles including set one default, but recent Konsole versions have their own 'default' when you press right mouse button in terminal area for menu, first is KDE's default falsely-labelled in the case (such as myself) one has one's own default and KDE's can't be moved below current/true default nor alternatives. EXPECTED RESULT Label current/true default--and system/original/KDE's default--as such and allow all custom profiles to be moved above or below old/system/original/KDE's default in user's chosen order. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD 13+, Slackware 15+, OpenBSD 7+, NetBSD 9+, Neon * KDE Plasma Version: 5.25.n KDE Frameworks Version: 5.9n.m Qt Version: 5.1n.m -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461268] New: .AVIF image format support?
https://bugs.kde.org/show_bug.cgi?id=461268 Bug ID: 461268 Summary: .AVIF image format support? Classification: I don't know Product: kde Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Today I found out (downloading images) .AVIF is a new (2019) image/video format meeting International Standards Organization (ISO) and other specifications, and has better compression than most/all other formats, so should KDE support it for things like file managers & image viewers (or general library that would work for all)? STEPS TO REPRODUCE 1. Try to view/open an .AVIF in a file manager or image viewer/editor. OBSERVED RESULT .AVIF seems currently unsupported. EXPECTED RESULT Consider programming .AVIF support. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: FreeBSD UNIX 13.1, Slackware64 15+current & KDE Neon 20.04 GNU/Linuxes KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION X11. I can later possibly also test NetBSD, maybe DragonFlyBSD. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461268] .AVIF image format support?
https://bugs.kde.org/show_bug.cgi?id=461268 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from David Chmelik --- Slackware: kimageformats-5.99.0-x86_64-1 Neon: updated this month, but forgot how to check package -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466861] default print format overridden
https://bugs.kde.org/show_bug.cgi?id=466861 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #3) > Can you supply the following? > > - The output of running `env | grep LANG` in a terminal window > - The contents of ~/.config/plasma-localerc > - The contents of /etc/locale.conf u@Hilltop-Heaven:~$ env|grep LANG LANGUAGE=en_US LANG=en_US.UTF-8 #/etc/locale.conf [Formats] LANG=en_US.UTF-8 [Translations] LANGUAGE=en_US u@Hilltop-Heaven:~$ cat /etc/locale.conf LANG=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_TIME=en_US.UTF-8 Another thing I noticed in KATE is it lists page margins in millimetres, though Okular lists it in inches... but both are outside printable area (2.96mm or 0.12"). The above is for KDE Neon; of course on my Slackware PC I added British English the above is different, but I'm unsure this actually happened on there... just when I used the network printer I thought it might've. We installed printer drivers because they seem to work better than the so-called 'driverless', and are unable to delete that one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466861] default print format overridden
https://bugs.kde.org/show_bug.cgi?id=466861 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from David Chmelik --- This happens on a KDE Neon PC we didn't set any locale, language, format settings--just left default since installation. The only step is as stated: try to print (preview) from any KDE program such as KATE, Okular, etc., which (though systemsettings says is set to USA letter) are all set on 2L. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466861] New: default print format overridden
https://bugs.kde.org/show_bug.cgi?id=466861 Bug ID: 466861 Summary: default print format overridden Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Default print format set in systemsettings is overridden by most/all KDE programs (KATE, Okular, etc.). STEPS TO REPRODUCE 1. Print preview. OBSERVED RESULT If you have USA settings (as we always left default in KDE Neon) programs (KATE, Okular) change the set default print format USA letter to 2L, which I don't know what it is and we don't have that size paper. If I have British English dialect but all the rest defaults were left on USA settings including USA letter (as in Slackware) it may be overridden to 2L or A4 (international/EU/UK letter). EXPECTED RESULT Make programs use the default print format. SOFTWARE/OS VERSIONS UNIX/Linux/KDE Plasma: KDE Neon 22.04 5.27.1, Slackware64 15+current KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Used to not happen but started earlier this or last year. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465493] Dolphin calls home directory/folder Downloads
https://bugs.kde.org/show_bug.cgi?id=465493 --- Comment #6 from David Chmelik --- (In reply to Méven Car from comment #5) > [...] Do you have xdg-user-dir installed ? yes > Did you use system-settings to change the Download folder path ? yes > I wonder if it is because of your distro. no, but maybe theme -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force printer to use drivers
https://bugs.kde.org/show_bug.cgi?id=468889 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from David Chmelik --- I couldn't have been clearer if I said give the option to delete the driverless version; that's what drivers being the 'only choice' means in this case. -- 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 #10 from David Chmelik --- (In reply to Nate Graham from comment #9) Okay > - See if you're running out of RAM The example command to launch 20 programs simultaneously (including resource-intensive) permanently halts KDE panel within 1sec (but works speedily in XFCE) so it's not a problem of running out of RAM (which I checked using 'free' RAM information on command-line never happens in that short time rather than a few days/weeks) rather than presumably a problem of CPU or graphics usage/thrashing probably of panel, which I suspect if programs like a Usenet newsreader or filesharing are doing millions updates (and they are) the panel lately tries to update/blink/etc. for each of multiple millions and gets overloaded... If I start the 20 programs with a maybe minute between each, I often do okay until more than one are doing millions updates again. Programs like top, btop, htop show high CPU activity when I start these 20, but it's not always 100%, just sometimes close, so it's a bit puzzling why the panel isn't using more a little more CPU resources if that could speed it up... if I turn off number-crunching on the other 24 threads, in fact CPU threads usage is overall rather low so it's possible it's not so much CPU as much as graphics not being able to do multiple millions updates (but I don't know a command to monitor graphics load). > - Simplify your system bit-by-bit to see if any specific element is causing > the issue; remove widgets-one-by-one; remove external screens, disable > virtual desktops and Activities, etc. I don't use virtual desktops nor activities, and only minimal and a couple extra basic widgets: menu, task manager, clock, launchers that change into task manager entries, weather forecast, and a cartoon/comic reader, which are usually idle.It's probable the problem is the task manager in the panel trying to do multiple millions updates, but if I remove task manager, I may as well remove KDE. Panels aren't normally visible on the other screens so probably are unrelated, but I can try again with temporarily unplugging those screens, and as such will leave this as 'waiting for info' until I get to that... if my report about the 'free' and (though might need more investigation) top/etc commands are enough, you can change it to 'reported. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force printer to use drivers by deleting driverless option
https://bugs.kde.org/show_bug.cgi?id=468889 David Chmelik changed: What|Removed |Added Summary|way to force driverless |way to force printer to use |printer to use drivers |drivers by deleting ||driverless option -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force printer to use drivers by deleting driverless option
https://bugs.kde.org/show_bug.cgi?id=468889 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #3) > But do you know that your driverless printer actually supports using > drivers? Does this work? I described using drivers, so it's clear they do. The problem is you can't get rid of the driverless option, which isn't as good. -- 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 #12 from David Chmelik --- (In reply to Nate Graham from comment #11) > Thanks. So when you remove the Task Manager widget from your panel (not > permanently; just temporarily for testing purposes), the problem stops > happening? I'm happy to report (also with unplugging of two screens for this test) it does (at least 18/20 launched at once, but I think something over 10 or at most 15 is close enough to the medium-to-large quite resource-intensive workload) so this is likely a duplicate of a specific bug report for the task manager (classic including text) in the panel I reported or commented on but hadn't heard any update on lately, Two that didn't launch were discord (needed update, but not resource-intensive) and pan 2 NNTP newsreader which was one that does some of the most updates in task manager, but so do the filesharing, and they all launched, and I launched another resource-hungry web browser in short time, and three my web browsers currently have something from maybe 20+ to 70+ tabs so would've been more updates than usual, and hexchat has close to 150 channels now so also would've been many updates, so I think it's safe to say this is a task manager problem. In this test, the almost 10 programs that minimized to the panel, and task switching with was all super-fast like KDE3 and like newer when I didn't open as much too fast nor had as many task manager updates. I would close this but don't know which other bug it is which should probably be marked duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468887] New: KATE printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=468887 Bug ID: 468887 Summary: KATE printing formatting problems Classification: Applications Product: kate Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- KATE has several printing formatting problems, including a general KDE one I reported elsewhere. When we have our measurements set to imperial/USA lengths, KATE doesn't show us the margins in that format rather than millimetres, which some are too short or not used at all, because on a several page file (after we select USA letter format which the paper is) all the last lines got cut in half at the bottom of the page, unreadable. When I print previewed a 12-page document it said it was 11 pages. STEPS TO REPRODUCE 1. Print preview and then print multiple-page document 2. View measurements about the page including margins (see locale not used, which you may need to add an alternative/secondary language/dialect despite not actually using its measurements) and number of pages (if it's 11 & 1/2 it'll say 11 rather than 12) 3. Check each bottom line OBSERVED RESULT Wrong formatting used in description, print preview, and for the bottom line which gets cut off. EXPECTED RESULT USE the correct lengths that are set in the locale. Check if there is space for the bottom line, and if not, start it on the next page. Round up number of pages if even goes over by one character. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.27 22.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.19.9 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] New: way to force printer to use drivers
https://bugs.kde.org/show_bug.cgi?id=468889 Bug ID: 468889 Summary: way to force printer to use drivers Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: dchme...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Systemsettings sets up so-called 'driverless' printers, sometimes (if removed) multiple times, which I've found lack quality/settings that drivers have, and seems there's no way to get rid of. STEPS TO REPRODUCE 1. Add printer drivers. 2. Watch users assume printer is set right or select one. OBSERVED RESULT Printer drivers are sometimes better than so-called 'driverless' which seems there's no way to get rid of. When users accidentally selected the driverless (not default) option we've had whole sections omitted within documents when printed, regardless of text editor or word processor. EXPECTED RESULT If one wants to use drivers, allow that and for it to be the only choice if desired. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.n 20+ to 5.27 22.04 KDE Plasma Version: 5.n to 5.27.4 KDE Frameworks Version: 5.n to 5.105.0 Qt Version: 5.n to 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468888] New: KATE printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=46 Bug ID: 46 Summary: KATE printing formatting problems Classification: Applications Product: kate Version: 23.04.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- KATE has several printing formatting problems, including a general KDE one I reported elsewhere. We use imperial/USA measurements--inches--but KATE describes page/margins in millimetres. We print previewed a 12-page document it said was 11 pages. It only printed the top half of lines at page bottoms. STEPS TO REPRODUCE 1. Print preview a multiple-page document 2. Check formatting of margins (maybe need to add alternative language/dialect despite not using its measurements) and number of pages 3. Print and check every line at bottom of page OBSERVED RESULT KATE misformats documents, including using other measurements than set in locale, and doesn't round up number of pages if even goes over one character, and only prints top half of lines at bottom of pages. EXPECTED RESULT Use locale. Round up number of pages. Check if last line will fit, including bottom half, and if not, start it on next page. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE Neon 5.27 22.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I can test on FreeBSD UNIX, Slackware GNU/Linux, connected to same printer (on KDE Neon host) over network. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465494] New: Okular doesn't use locales' nor printer's standard page print format
https://bugs.kde.org/show_bug.cgi?id=465494 Bug ID: 465494 Summary: Okular doesn't use locales' nor printer's standard page print format Classification: Applications Product: okular Version: 22.12.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Okular doesn't use locales' nor printer's standard page print format. If I have my locale including page size American English, except language British English, Okular overrides locale's & printer's USA letter print page size with A4. If we have locales all-American, Okular uses overrides locale's & printer's USA letter print page size with 2L (maybe first in the list) which I don't know what it is and we have no such paper. This is all for USA letter size documents you'd think would be detectable. STEPS TO REPRODUCE 1. Print in Okular (after optionally setting different system dialect, but some bug happens either way) OBSERVED RESULT Okular doesn't use system print page sizes. EXPECTED RESULT Use system print page sizes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 22.0.4, Slackware64 15+current, KDE Plasma Version: 5.26 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465493] Dolphin calls home directory/folder Downloads
https://bugs.kde.org/show_bug.cgi?id=465493 David Chmelik changed: What|Removed |Added Platform|Other |Slackware Version|unspecified |22.12.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465493] New: Dolphin calls home directory/folder Downloads
https://bugs.kde.org/show_bug.cgi?id=465493 Bug ID: 465493 Summary: Dolphin calls home directory/folder Downloads Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dchme...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I don't use preset user folders such as Downloads and set that one to my home user directory/folder (for example /home/user). When I open another tab, the tabs call home directory Downloads instead of normal path or name. STEPS TO REPRODUCE 1. Set Downloads to home user directory/folder, in this example /home/user. 2. Open another /home/user directory tab. OBSERVED RESULT Calls /home/user Downloads. EXPECTED RESULT Call the /home/user its path or main name (home). SOFTWARE/OS VERSIONS UNIX/GNU/Linux: Slackware64 15+current KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] New: systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 Bug ID: 465495 Summary: systemsettings no longer shows language dialect in use (if different from rest of locale) Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Slackware OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY I've always used KDE with American locale but almost always British English dialect, which is first in my language list but the main regional settings screen shows it to be American English instead, despite still working elsewhere (like Dolphin saying wastebin instead of trash). STEPS TO REPRODUCE 1. Change dialect. OBSERVED RESULT In main screen, doesn't show dialect actually first in list. EXPECTED RESULT In main screen, show dialect actually first in list. SOFTWARE/OS VERSIONS UNIX/GNU/Linux: Slackware64 15+current KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465496] New: nonstandard phone number formats
https://bugs.kde.org/show_bug.cgi?id=465496 Bug ID: 465496 Summary: nonstandard phone number formats Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY Systemsettings added a phone number format, which is actually nonstandard. The standard USA format, in phone books and diallers, is +1 (123) 123-4567. You forgot the hyphen. Parts before and after it have specific names according to phone companies. Maybe what you put is specified by some obscure organization no one pays attention to nor follows when writing phone numbers, so isn't really standard. A newer alternative format is +1-123-123-4567... so virtually anywhere you see these written have at least one hyphen. Some other English-speaking countries use dots instead of hyphens, for whatever standards they use (you don't have either) and is occasionally seen in USA but of course nonstandard here. STEPS TO REPRODUCE 1. View phone number format. OBSERVED RESULT Doesn't actually use standard format all phone companies/books, diallers, average people use. EXPECTED RESULT Consider adding formats all phone companies/books, diallers, and people actually use. SOFTWARE/OS VERSIONS UNIX/GNU/Linux: KDE Neon 22.0.4, Slackware64 15+current KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #6 from David Chmelik --- I added British English and moved it to top. I'm not talking about other formatting, just that the top language isn't listed as the language in use. I don't know what that stuff is but will work on it later. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465493] Dolphin calls home directory/folder Downloads
https://bugs.kde.org/show_bug.cgi?id=465493 --- Comment #4 from David Chmelik --- It was hidden in the first place. I don't know if it's safe to edit that file, but I guess I could make a backup and delete all the locations. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465493] Dolphin calls home directory/folder Downloads
https://bugs.kde.org/show_bug.cgi?id=465493 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from David Chmelik --- I saw no way to delete it, but was able to edit it though now tabs don't call it what I edited to (home) just the path, which is fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #8 from David Chmelik --- d@cosmos:~$ cat /etc/locale.conf cat: /etc/locale.conf: No such file or directory d@0.cosmos:~$ cat ~/.config/plasma-localerc [Formats] LANG=en_US.UTF-8 LC_NAME=en_GB.UTF-8 LC_TIME=en_150.UTF-8 [Translations] LANGUAGE=en_GB:en_US -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #9 from David Chmelik --- I don't know what QML theming is or what the implications of it being broken are. I do have qt5ct, which I thought was a dependency of something else I have, but might not be, so can probably uninstall it. Slackware has qqc2-desktop-style. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #3 from David Chmelik --- Created attachment 156178 --> https://bugs.kde.org/attachment.cgi?id=156178=edit regional -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #2 from David Chmelik --- Created attachment 156177 --> https://bugs.kde.org/attachment.cgi?id=156177=edit languages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] Task manager causes Plasma to hang with heavy usage
https://bugs.kde.org/show_bug.cgi?id=457370 David Chmelik changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #16 from David Chmelik --- (In reply to Nate Graham from comment #13) > Ok, so the issue in the Task Manager code somewhere. > > Can you clarify what "doing millions updates again" means? Are any of these > apps rapidly changing their window title or rapidly changing whether audio > is played or not? Not those but other things that may have been causing the task manager to update/flash mostly/all text/file updates... many on status bars or elsewhere, but not title bar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] Task manager causes Plasma to hang with heavy usage
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #18 from David Chmelik --- I can only theorize why KDE halts on opening 10 (maybe) or 15 (likely) or 20+ (definitely) programs. Of course I can't screen record; all you'd see is shell command I use to launch programs--I 혥혪혥 state which (twice)--and before they do much/anything than open a window area, KDE apparently halts permanently (sometimes I even went to do something else and checked back an hour or two later): thus, there'd be no way to save the recording. I guess I can learn video camera, but I doubt you'll see much useful from a video with one to few seconds activity. My description what slows task manager is only what I saw some programs updating and slowing but not always halting KDE, more than a year ago (so don't recall which other than mostly in my twice-given list). I seem to recall at some time most programs (on any internal activity) caused task manager updates/flashes, but the task manager may have been reconfigured/recoded to not as much/anymore. It probably wasn't programs that wait to do much/anything, though I opened quite a few of those (one is KATE I have 10 tabs in which change in titlebar but I don't know if opening a session changes those); some were dozens/hundreds tabs in chats (hexchat, pidgin, which both change titlebar on tab opening) & web browsers (some which change titlebar on tab opening though are also just sessions similar to KATE), pan (Usenet newsreader, with 1400+ subscriptions some doing 100,000+ updates in status bar) and eiskaltdcpp & nicotine & transmission which open hundreds thousands of files (though none in titlebar, 2/3 maybe status bars and opening the files causes temporary slowdown). I'd have to go use KDE again and test these to see/record if they do that but don't know if they're actually the reason or if it's just starting 20 programs in something from a fraction of a second (launcher) to a minute or two (manually, which can have same effect) is too fast for the task manager for some other reason. I'm willing to do this after trying to make a video of the halt but don't think any these on their own will halt KDE... even the chats, which I now realize do almost 200 titlebar updates, won't halt KDE on their own, and web browsers won't either, but it could be the case all these opened fast might do it which I can check later. I also know people who use significantly more programs than me on their PC, which is what I might call a high workload. Mine was just medium-to-high and the report title no longer reflects that--it wasn't every time I opened all these but is increasing over time except when I only use X for a short while. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472987] no longer can select hidden files for desktop background
https://bugs.kde.org/show_bug.cgi?id=472987 --- Comment #3 from David Chmelik --- (In reply to Nate Graham from comment #2) > Are you saying that in the "Select file" dialog that's asking you to choose > an image file, you can't navigate to or find your hidden file? Desktop settings may be able to find them but refuses to load them anymore (only non-hidden). I keep backgrounds like in /home/user for easier usage there but of course they don't need to see it every time they open the Dolphin or Konqueror file managers (so hidden). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472981] on opening KATE, can't see paths or other differences between files
https://bugs.kde.org/show_bug.cgi?id=472981 --- Comment #2 from David Chmelik --- (In reply to Christoph Cullmann from comment #1) > We show the full name in the tool tip at the moment. That works for me personally but doesn't seem to necessarily work for the users I help: I don't think they know/use tooltips unless they show up automatically merely when opening a program... so apparently they miss those and open/edit files from backup drives. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472981] New: on opening KATE, can't see paths or other differences between files
https://bugs.kde.org/show_bug.cgi?id=472981 Bug ID: 472981 Summary: on opening KATE, can't see paths or other differences between files Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- On opening KATE, in the screen that shows files you used to be editing and asks what you want to do, you can't see paths or other differences between files. Sometimes we have several files named the same and no way to know which is which (because two users sharing account have some named same and all also on always-on backup drives they sometimes forget to not edit). STEPS TO REPRODUCE 1. Start KATE and look at introduction screen (without automatically reopening a saved session). OBSERVED RESULT Can't see paths or differences between files (such as of same name). EXPECTED RESULT Option to always show paths or some way to see differences. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.27 22.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472987] New: no longer can select hidden files for desktop background
https://bugs.kde.org/show_bug.cgi?id=472987 Bug ID: 472987 Summary: no longer can select hidden files for desktop background Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Earlier this year I was able to select hidden files for desktop background, and still have some saved for it, but then we got a larger monitor, so I made a new background file (hidden) but now can't load it. STEPS TO REPRODUCE 1. Try to type in a hidden (dotfile) image in desktop background setting. OBSERVED RESULT No longer works. EXPECTED RESULT Restore functionality. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.27 22.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472981] on opening KATE, can't see paths or other differences between files
https://bugs.kde.org/show_bug.cgi?id=472981 David Chmelik changed: What|Removed |Added Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472981] on opening KATE, can't see paths or other differences between files
https://bugs.kde.org/show_bug.cgi?id=472981 David Chmelik changed: What|Removed |Added Version|unspecified |23.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] Task manager causes Plasma to hang with heavy usage
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #20 from David Chmelik --- Good: no longer seems to be a problem, and is duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468887] Kate printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=468887 David Chmelik changed: What|Removed |Added Platform|Fedora RPMs |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468887] Kate printing formatting problems
https://bugs.kde.org/show_bug.cgi?id=468887 --- Comment #3 from David Chmelik --- Why was the OS I reported this on removed? I hadn't heard it's fixed. Please, if you add to a report on another GNU/Linux, don't change it to that; leave it or at least change it to what sounds more general: 'unspecified'. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483719] display problems (no icons, etc.)
https://bugs.kde.org/show_bug.cgi?id=483719 --- Comment #3 from David Chmelik --- Problem was qt5ct, not 'assembling our systems from bits and pieces'--GNU/Linux Mint isn't Linux From Scratch. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482133] no desktop on upgrade to KDEP6
https://bugs.kde.org/show_bug.cgi?id=482133 --- Comment #3 from David Chmelik --- I agree set 'RESOLVED > WORKSFORME' despite don't consider it resolved, but unless there will be KDE Neon long-term serivce (LTS) release, we're waiting before using KDE Plasma 6 (KDEP6) and switched back to GNU/Linux Mint or might use Kubuntu for family PCs... lately most have hardware problems we must fix before I consider testinf KDEP6 later. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483719] display problems (no icons, etc.)
https://bugs.kde.org/show_bug.cgi?id=483719 --- Comment #1 from David Chmelik --- Note, when I say only Dolphin custom-icon entries/files/directories/folders display, I don't mean chosen from KDE's available (I did some but they don't display) rather than only images/icons that have previews or I manually added such as to /usr/share/pixmaps (such as you can see Mount Olympus in my Dolphin information panel was the last image I hovered over, and similarly, only directories/folders I added my own images for custom icons display those as icons, you can see in the folders panel). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483719] New: display problems (no icons, etc.)
https://bugs.kde.org/show_bug.cgi?id=483719 Bug ID: 483719 Summary: display problems (no icons, etc.) Classification: I don't know Product: kde Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- Created attachment 167290 --> https://bugs.kde.org/attachment.cgi?id=167290=edit display problems screenshot SUMMARY On our KDE Plasma 5 (KDEP5) personal computers (PCs) icons no longer display on toolbars nor for preset/'places' (just custom) Dolphin entries/files/directories/folders--see screenshot--and a Konsole display problem (you can see but I should report separately next) is cursor & selection are offset from actual text location. STEPS TO REPRODUCE 1. Run standard programs like Konsole, Dolphin, KATE. 2. Edit toolbars to set 'text under icons' (or any icons). 3. Look for error/missing display aspects. OBSERVED RESULT There are no icons (screenshot Dolphin directory/folder shown is symbolic link to user-owned /user/share/doc normally showing all as directory/folder icons) with exception of Dolphin custom-icon entries/files/directories/folders. You can also see on Konsole (I don't use toolbars but tested and no longer have icons) a display problem is cursor & selection are offset from actual text position... in screenshot Konsole I didn't press spaces, but initially and when I type, cursor is at least a tab's length past actual text location, and when I select text, highlighted range is similarly offset (confusing/impossible to copy correctly). All this persists on updates & reboots, though seemingly-universal display problem is no standard icons; I should report Konsole text display problem separately. EXPECTED RESULT Display normally (icons). SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: GNU/Linux Mint 21.3 (XFCE variant) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 HARDWARE SSD: OS (after KDE Neon 6, quick-formatted for GNU/Linux Mint 21.3) HDD: /home (kept from KDE Neon 6 but deleted KDE configuration) ADDITIONAL INFORMATION We had KDE Neon 6 which critically broke on 2/3 our family PCs (one unusable) and someone on Libera IRC #kde said Neon is 'almost rolling release' so we switched back to Mint with same /home hard disc drives (HDDs). I deleted ~/.kde , KDE files/directories/folders in ~/.config , ~/.local/share , and was extremely thorough (think I got all not starting with k)--deleted much I didn't need to--only stuff I know is left. We prefer Oxygen (detailed desktop-oriented) over Breeze (over-simple/-dull pad/tab(let)-oriented) and use other themes (GTK Clearlooks* & Greybird*) for specific settings (colours, icons/widgets) so don't know avoiding Breeze has to do with this... where Breeze is better for things (like newer startup/loading screen style) we occasionally use it. There's a small chance I missed deleting some configuration and--since reinstall apparently 'quick formatted'--small chance some package/theme data was leftover on OS' solid state drives (SSD)... wondering if we need to zero SSDs or delete more configuration... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457515] Window Decorations disappear when selecting Plastik
https://bugs.kde.org/show_bug.cgi?id=457515 David Chmelik changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from David Chmelik --- They came back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] New: middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 Bug ID: 481707 Summary: middle of screen set offset Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY The middle of screen is set offset, so windows don't snap halfway rather than wrong position. STEPS TO REPRODUCE 1. Start KDE. 2. Find 'middle' of screen. OBSERVED RESULT The middle of screen is set offset, so windows don't snap halfway rather than wrong position. EXPECTED RESULT Set middle of screen at middle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon GNU/Linux 5.27 22.04 KDE Plasma Version: 5.27 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from David Chmelik --- (In reply to fanzhuyifan from comment #3) > How are you finding the middle of the screen? Is this an issue with quick > tiling? Already stated/shown (image): snapping, KRuler (I don't know what quick tiling is). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #9 from David Chmelik --- Actually, middle should be 1920 (it's mistakenly offset so programs try to snap to what looks like (but isn't exact) about 1/16 & 15/16 the screen). d@cosmos:~$ kscreen-doctor -o Output: 84 DisplayPort-0 enabled connected priority 1 DisplayPort Modes: 89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@50 92:3840x2160@48 93:3840x2160@30 94:2560x1600@60 95:2560x1440@60 96:1920x1200@60 97:1920x1080@60 98:1920x1080@60 99:1920x1080@60 100:1600x1200@60 101:1680x1050@60 102:1280x1024@60 103:1440x900@60 104:1280x960@60 105:1280x800@60 106:1280x720@60 107:1280x720@60 108:1024x768@60 109:1440x480@60 110:1440x480@60 111:832x624@75 112:800x600@60 113:720x480@60 114:720x480@60 115:640x480@60 116:640x480@60 117:720x400@70 118:640x350@70 Geometry: 0,1200 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 85 DisplayPort-1 enabled connected priority 2 DisplayPort Modes: 98:1920x1080@60*! 102:1280x1024@60 108:1024x768@60 112:800x600@60 116:640x480@60 1913:1680x1050@60 1914:1440x900@60 1915:1366x768@60 1916:1280x800@60 1917:1280x720@60 Geometry: 3840,1200 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 86 DisplayPort-2 enabled connected priority 3 DisplayPort Modes: 102:1280x1024@60 104:1280x960@60 108:1024x768@60 111:832x624@75 112:800x600@60 116:640x480@60 117:720x400@70 1895:1600x1200@60*! 1896:1280x1024@75 1897:1440x900@60 1898:1280x800@60 1899:1152x864@75 1900:1280x720@60 1901:1024x768@75 1902:1024x768@70 1903:800x600@72 1904:800x600@75 1905:800x600@56 1906:640x480@75 1907:640x480@73 1908:640x480@67 Geometry: 1183,0 1600x1200 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 87 HDMI-A-0 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 155 DisplayPort-1-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 156 DisplayPort-1-4 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 157 DisplayPort-1-5 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 158 HDMI-A-1-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #2 from David Chmelik --- Created attachment 166030 --> https://bugs.kde.org/attachment.cgi?id=166030=edit 1 screenshot (didn't originally fit) with KRuler showing wrong middle -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #1 from David Chmelik --- Top screen is 1600x1200. Left-side screen is 4K. Right-side screen is 1080p. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #13 from David Chmelik --- On the OS I'm temporarily using (I now of course switched to XFCE) the windows now snap to real centre (in KDE) but KRUler's centre is still offset to be at the end of 1080 pixels instead of half of 4K... so this is now only a KRuler program. As I show the case with KRuler, you won't need a video... but I guess it should be moved to be a KRuler but or opened as one? Unsure what to do about that or how. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 David Chmelik changed: What|Removed |Added Product|kruler |kwin Version|23.08.4 |unspecified Assignee|soe...@pprojekt.de |kwin-bugs-n...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED Component|general |general --- Comment #14 from David Chmelik --- Didn´t start as a KRuler bug so I'll mark this resolved -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 481714] New: KRuler middle isn´t at screen middle
https://bugs.kde.org/show_bug.cgi?id=481714 Bug ID: 481714 Summary: KRuler middle isn´t at screen middle Classification: Applications Product: kruler Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: soe...@pprojekt.de Reporter: dchme...@gmail.com Target Milestone: --- Created attachment 166035 --> https://bugs.kde.org/attachment.cgi?id=166035=edit KRuler screenshot SUMMARY KRuler middle isn´t at screen middle. STEPS TO REPRODUCE 1. Start KRuler. OBSERVED RESULT KRuler middle isn't at screen middle (it's at 1080px instead of 3840/2=1920px in screenshot). EXPECTED RESULT same KRuler & screen middle SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: KDE neon GNU/Linux 5.27 22.04 KDE Plasma Version: 5.27 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 David Chmelik changed: What|Removed |Added Component|general |general Assignee|kwin-bugs-n...@kde.org |soe...@pprojekt.de Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|git-stable-Plasma/5.27 |23.08.4 Product|kwin|kruler -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #11 from David Chmelik --- (In reply to fanzhuyifan from comment #10) > Looking at the output, there is no fractional scaling. Could you elaborate > on what you mean by snapping? Or maybe upload a screencast if that is > easier? I still don't quite follow, and on my end quick tiling to the edges > correctly fill up half of the screen. You already described snapping and I can't elaborate on that. My 4K screen is 3840px wide. 3840/2=1920, so the middle should be at 1920 and snap to there. If you see my KRuler, it didn't put the middle there rather than at 1080px. You'd think then it'd snap to 1080px but it actually snaps to 1080/2 (540) on that side and 3840-540 on the other side. The screenshot already shows the middle has been miscalculated, and it'd take much effort/time to make a 'screencast' to show snapping is similarly wrong but even if I did that, you wouldn't see anything significantly different than you already see with KRuler. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481707] middle of screen set offset
https://bugs.kde.org/show_bug.cgi?id=481707 --- Comment #12 from David Chmelik --- I can maybe do it but will have to find/install/learn a desktop video-making program. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 David Chmelik changed: What|Removed |Added CC||dchme...@gmail.com --- Comment #44 from David Chmelik --- I have the same problem on KDE(P)6 Neon and recall same problem on KDE(P)5 (Slackware, Neon, etc.). I don't see how to create the files for these entries. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482133] New: no desktop on upgrade to KDEP6
https://bugs.kde.org/show_bug.cgi?id=482133 Bug ID: 482133 Summary: no desktop on upgrade to KDEP6 Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal 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: --- Created attachment 166243 --> https://bugs.kde.org/attachment.cgi?id=166243=edit broken desktop GUI SUMMARY We updated/upgraded three KDE Neon 5 desktop PCs, and then upgraded them to KDEP6. One now has had the panel removed (and can't be put back) so has no functional desktop/GUI other than a search, and two blank rectangles/'desktops' (that do nothing when selected) and a plus that adds more blank rectangles... no other controls/menus work/appear (such as right mouse button). Even a known command-line force KDE logout command (maybe 'qdbus org.kde.ksmserver /KSMServer logout 0 0 1') did nothing (which I could've temporarily used an alternative X window manager or desktop environment and maybe reconfigured KDE). STEPS TO REPRODUCE 1. Use certain hardware types (see below)? 2. apt-get update 3. apt-get dist-upgrade 4. reboot OBSERVED RESULT No functional desktop/GUI; see attached photograph. EXPECTED RESULT Continue normal desktop GUI, not changing broken mode to whatever's in that photograph. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6 22.04 KDE Plasma Version: 6 KDE Frameworks Version: whatever came with the above Qt Version: whatever came with the above HARDWARE CPU: i7700K system-/logic-/main-/mother-board: GA-Z170XP-SLI RAM: 64GB monitor: 2560x1600 display/video/graphics card: Radeon Vega 64 ADDITIONAL INFORMATION I can't get Frameworks, QT information because this PC now runs GNU/Linux Mint, though I doubt Frameworks, QT for users changed within a few hours of release... if they did, or if you know what happened above, I'm willing to test again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482126] New: KDEP5 to 6 upgrade error (qt6-sensors-manual format)
https://bugs.kde.org/show_bug.cgi?id=482126 Bug ID: 482126 Summary: KDEP5 to 6 upgrade error (qt6-sensors-manual format) Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: dchme...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY On 28th of February, We updated/upgraded three KDE Neon 5.27 PCs and then upgraded them to KDEP6. All three said the following. Processing 1 changed doc-base file, 3 added doc-base files... Error in `/usr/share/doc-base/qt6-sensors.qt6-sensors-manual', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. STEPS TO REPRODUCE 1. apt-get update 2. apt-get dist-upgrade OBSERVED RESULT A file has errors. EXPECTED RESULT Fix formatting. SOFTWARE/OS VERSIONS UNIX/GNU/Linux/KDE Plasma: Neon 6 22.04 KDE Plasma Version: 6 KDE Frameworks Version: whatever came with the above Qt Version: whatever came with the above ADDITIONAL INFORMATION Couldn't check Frameworks, QT versions, because of more critical bugs we switched these to GNU/Linux Mint, but I doubt Frameworks, QT for users were updated within first few hours after release... if so I'm willing to test again. -- You are receiving this mail because: You are watching all bug changes.
