[Skanpage] [Bug 451251] Multipage scanning only returns first 2 pages using auto document feeder (duplex)
https://bugs.kde.org/show_bug.cgi?id=451251 Tornado99 changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Tornado99 --- Same problem with Gnome document scanner. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 451251] New: Multipage scanning only returns first 2 pages using auto document feeder (duplex)
https://bugs.kde.org/show_bug.cgi?id=451251 Bug ID: 451251 Summary: Multipage scanning only returns first 2 pages using auto document feeder (duplex) Product: Skanpage Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: richrocksmywo...@gmail.com Target Milestone: --- Using skanpage-git r292.609a55b-1 built 7th March 2022 STEPS TO REPRODUCE 1. Using ADF Duplex with Epson WF-7720 and 4 sheets of double-sided A4 2. Only first 2 pages appear in Skanpage even though scanner pulls through all 4 sheets and scans them twice OBSERVED RESULT only first 2 pages scanned EXPECTED RESULT all eight pages scanned -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448136] New: Implement "ignore wayland scaling" flag for apps that have custom internal scaling mechanisms
https://bugs.kde.org/show_bug.cgi?id=448136 Bug ID: 448136 Summary: Implement "ignore wayland scaling" flag for apps that have custom internal scaling mechanisms Product: kwin Version: 5.23.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: richrocksmywo...@gmail.com Target Milestone: --- MATLAB (gtk2?) has its own internal scaling factor "s" which can be set to any value, such as 1, 1.25, 1.5, 2 etc. This scales all the UI elements. The font size can also be set independently. In Wayland environment with 100% Wayland scaling on a 4K monitor, MATLAB can be configured with perfect scaling and sharp fonts simply by increasing "s", and increasing font size. In Wayland environment with 200% Wayland scaling, both the UI and fonts are blurry as Wayland adds an extra scale factor which is not needed. Launching non-standard toolkit apps with custom internal scaling mechanisms should have an option to ignore the Display scaling set in Plasma System settings. https://uk.mathworks.com/matlabcentral/answers/406956-does-matlab-support-high-dpi-screens-on-linux -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447165] Permanent Blue horizontal line on hamburger menu after first time it is clicked in LibreOffice
https://bugs.kde.org/show_bug.cgi?id=447165 --- Comment #1 from Tornado99 --- Created attachment 144641 --> https://bugs.kde.org/attachment.cgi?id=144641&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447165] New: Permanent Blue horizontal line on hamburger menu after first time it is clicked in LibreOffice
https://bugs.kde.org/show_bug.cgi?id=447165 Bug ID: 447165 Summary: Permanent Blue horizontal line on hamburger menu after first time it is clicked in LibreOffice Product: Breeze Version: 5.23.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: richrocksmywo...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After clicking on the hamburger menu in right hand corner of LibreOffice for the first time, a blue horizontal line appears which does not disappear. Seems like a bug? STEPS TO REPRODUCE 1. Open LibreOffice 2. Click on hamburger menu in right hand corner 3. Click back to document OBSERVED RESULT permanent blue line EXPECTED RESULT no blue line? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436559] GTK3 CSD buttons are noticeably smaller than regular Breeze Qt style
https://bugs.kde.org/show_bug.cgi?id=436559
Tornado99 changed:
What|Removed |Added
CC||richrocksmywo...@gmail.com
--- Comment #14 from Tornado99 ---
I have 100% scaling and no forced font dpi on my 1440p monitor (although I did
have 125% in the past). Somehow the firefox buttons are still tiny. This code
in /home/[user]/.config/gtk-3.0/gtk.css fixes it
@import 'colors.css';
window headerbar.default-decoration button.titlebutton,
window .titlebar.default-decoration button.titlebutton {
padding: 0px;
min-height: 28px;
min-width: 28px;
margin: 0; }
window headerbar button.titlebutton,
window .titlebar button.titlebutton {
padding: 0px; }
window headerbar button.titlebutton.close,
window .titlebar button.titlebutton.close {
padding: 0px;
background-size: 28px 28px; }
window headerbar button.titlebutton.maximize,
window .titlebar button.titlebutton.maximize {
padding: 0px;
background-size: 28px 28px; }
window headerbar button.titlebutton.minimize,
window .titlebar button.titlebutton.minimize {
padding: 0px;
background-size: 28px 28px; }
.maximized window headerbar button.titlebutton.maximize, .maximized window
.titlebar button.titlebutton.maximize {
padding: 0px;
background-size: 28px 28px; }
window.background.chromium {
padding: 0px; }
window.background.chromium headerbar button.titlebutton.close,
window.background.chromium .titlebar button.titlebutton.close {
padding: 0px; }
window.background.chromium headerbar button.titlebutton.maximize,
window.background.chromium .titlebar button.titlebutton.maximize {
padding: 0px; }
window.background.chromium headerbar button.titlebutton.minimize,
window.background.chromium .titlebar button.titlebutton.minimize {
padding: 0px; }
window.background.chromium.maximized headerbar button.titlebutton.maximize,
.maximized .titlebar button.titlebutton.maximize {
padding: 0px; }
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 432452] Support ACPI platform profile, /sys/firmware/acpi/platform_profile_choices
https://bugs.kde.org/show_bug.cgi?id=432452 --- Comment #12 from Tornado99 --- Manjaro KDE 5.22.5, 5.87.0, kernel 5.14.10-1 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432452] Support ACPI platform profile, /sys/firmware/acpi/platform_profile_choices
https://bugs.kde.org/show_bug.cgi?id=432452 --- Comment #11 from Tornado99 --- No such file or directory for both 'cat' I rebooted. AMD Ryzen 3550H. My system definitely supports 3 profiles. I can switch for example to balanced using: kdesu bash -c "echo '\_SB.PCI0.LPC0.EC0.VPC0.DYTC 0x000FB001' | tee /proc/acpi/call" I have verified the max clock speed is different with the 3 different profiles using AMD uProf. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432452] Support ACPI platform profile, /sys/firmware/acpi/platform_profile_choices
https://bugs.kde.org/show_bug.cgi?id=432452 --- Comment #9 from Tornado99 --- I have a supported laptop (lenovo ideapad) and kernel 5.14. I installed the daemon but don't see anything in the UI. Am I missing something? In konsole I get: powerprofilesctl * balanced: Driver: placeholder power-saver: Driver: placeholder Although actually mine supports 3 profiles (quiet, balanced, performance) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 441057] 60% Charge Limit threshold not implemented for Lenovo Ideapads and Legion
https://bugs.kde.org/show_bug.cgi?id=441057 Tornado99 changed: What|Removed |Added Summary|Charge Limit threshold not |60% Charge Limit threshold |implemented for Lenovo |not implemented for Lenovo |Ideapads and Legion |Ideapads and Legion -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 441057] New: Charge Limit threshold not implemented for Lenovo Ideapads and Legion
https://bugs.kde.org/show_bug.cgi?id=441057 Bug ID: 441057 Summary: Charge Limit threshold not implemented for Lenovo Ideapads and Legion Product: Powerdevil Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: richrocksmywo...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Ideapad and Legion Lenovo laptops have BIOS setting to stop charging at 60% (toggled by echo 1 >/sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode) 2. Option for this is missing in Charge Limit Settings PAnel (https://invent.kde.org/plasma/powerdevil/-/merge_requests/5#note_288786). It is only implemented for Thinkpads. Can this be extended to these other laptops? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384054] Don't make windows translucent when moving by default
https://bugs.kde.org/show_bug.cgi?id=384054 --- Comment #11 from Tornado99 --- Sure, but if the effect increases usability why not enable it by default? I recall in the first days of windows managers (i.e. early Windows, Linux), dragging a window would show a dashed rectangle in place of the window. It was only later on that a solid window was added as an option. -- You are receiving this mail because: You are watching all bug changes.
