[systemsettings] [Bug 409374] New: You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make
https://bugs.kde.org/show_bug.cgi?id=409374 Bug ID: 409374 Summary: You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make fonts unreadable and you can remove checkmark but gets placed back upon opening and close Product: systemsettings Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: freefreen...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- Created attachment 121261 --> https://bugs.kde.org/attachment.cgi?id=121261&action=edit This is how it locks itself after you enable font anti-aliasing SUMMARY In fonts section of system settings for two days in Arch Linux after the latest two batches of KDE updates I can not enable font anti-aliasing because when I do and close out system settings and open it again and then open Dolphin at the same time it automatically puts a check mark in the box for blocking anti-aliasing so therefore it makes fonts completely unusable. This happened and I thought I had a corrupt system so I spent the time to completely reinstall Arch yesterday and it happened again as soon as I turned font anti-aliasing on. I normally use fonts with enabled anti-aliasing and RGB sub-pixel rendering with slight hinting for best looking fonts but the way it is now I can't not enable any of that because when I do enable it then it automatically puts a check mark in box for blocking anti-aliasing and sets it from 1-99. You can go and remove check mark and it puts it back again upon opening a couple apps. One last thing I am not for sure Dolphin has anything to do it with I know if you open and close system settings with Dolphin open it may talke a couple times but this happens for sure. STEPS TO REPRODUCE 1. Enable font anti-aliasing with RGB sub-pixel rendering and slight hinting 2. Close settings and open Dolphin 3. Open System Settings at the same time as Dolphin and you may have to open system setting and dolphin several times but the fonts will become unreadable. OBSERVED RESULT Unreadable fonts EXPECTED RESULT Readable fonts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59 Qt Version: 5.13 ADDITIONAL INFORMATION I am on Arch Linux stable and this happened on clean install after I thought my system was corrupt I reinstalled. This is pretty serious bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412796] New: Can we get an icon for Gravit designer ???
https://bugs.kde.org/show_bug.cgi?id=412796 Bug ID: 412796 Summary: Can we get an icon for Gravit designer ??? Product: Breeze Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: freefreen...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 123114 --> https://bugs.kde.org/attachment.cgi?id=123114&action=edit Shows the icon isn't there. SUMMARY Gravit designer application does not have a icon or if it does it not working it doesn't seem. STEPS TO REPRODUCE 1. Install Gravit 2. See that there is no icon 3. OBSERVED RESULT no icon EXPECTED RESULT visible icon 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 413414] New: System Settings crashes from time to time while doing multiple things.
https://bugs.kde.org/show_bug.cgi?id=413414 Bug ID: 413414 Summary: System Settings crashes from time to time while doing multiple things. Product: systemsettings Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: freefreen...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.1) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: I was just flipping thru the settings after doing a clean install of KDE Plasma on Arch Linux. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54c84ab800 (LWP 9136))] Thread 8 (Thread 0x7f54a3fff700 (LWP 9243)): #0 0x7f54cd4eda5e in () at /usr/lib/libQt5Core.so.5 #1 0x7f54cd715122 in () at /usr/lib/libQt5Core.so.5 #2 0x7f54caf59912 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f54caf5b118 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f54aa96e700 (LWP 9144)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f54bcd0d700 (LWP 9143)): #0 0x7f54cd16b42c in read () at /usr/lib/libc.so.6 #1 0x7f54caf0b9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf59a31 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f54caf5b118 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f54beb6a700 (LWP 9142)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f54bf36b700 (LWP 9140)): #0 0x7f54cbd50c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f54bf84c50c in () at /usr/lib/dri/i965_dri.so #2 0x7f54bf84c108 in () at /usr/lib/dri/i965_dri.so #3 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f54c60fe700 (LWP 9139)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.
[systemsettings] [Bug 413529] New: System Settings Crash while switching to the window decorations section
https://bugs.kde.org/show_bug.cgi?id=413529 Bug ID: 413529 Summary: System Settings Crash while switching to the window decorations section Product: systemsettings Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: freefreen...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.1) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: While opening the window decorations section the system settings crashed The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f442f6f0800 (LWP 41602))] Thread 8 (Thread 0x7f43ff136700 (LWP 42319)): #0 0x7ffd3d3dd923 in clock_gettime () #1 0x7f44343cc56b in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f4434959302 in () at /usr/lib/libQt5Core.so.5 #3 0x7f4434957bea in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f44349581b6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f443495975f in () at /usr/lib/libQt5Core.so.5 #6 0x7f443219fa50 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7f44321a0096 in () at /usr/lib/libglib-2.0.so.0 #8 0x7f44321a0241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7f4434959a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f44349004ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7f4434732385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7f4433a3b849 in () at /usr/lib/libQt5Qml.so.5 #13 0x7f44347335b0 in () at /usr/lib/libQt5Core.so.5 #14 0x7f4432f8f4cf in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f44343bf2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f441973a700 (LWP 41611)): #0 0x7ffd3d3dd923 in clock_gettime () #1 0x7f44343cc56b in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f4434959302 in () at /usr/lib/libQt5Core.so.5 #3 0x7f4434957bea in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f44349581b6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f443495975f in () at /usr/lib/libQt5Core.so.5 #6 0x7f443219fa50 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7f44321a0096 in () at /usr/lib/libglib-2.0.so.0 #8 0x7f44321a0241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7f4434959a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f44349004ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7f4434732385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7f4433a3b849 in () at /usr/lib/libQt5Qml.so.5 #13 0x7f44347335b0 in () at /usr/lib/libQt5Core.so.5 #14 0x7f4432f8f4cf in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f44343bf2d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f441b5ef700 (LWP 41609)): #0 0x7f44343b49ef in poll () at /usr/lib/libc.so.6 #1 0x7f44321a0170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f44321a0241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4434959a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f44349004ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f4434732385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4433a3b849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f44347335b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4432f8f4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f44343bf2d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f4425bb6700 (LWP 41608)): #0 0x7ffd3d3dd923 in clock_gettime () #1 0x7f44343cc56b in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f4434959302 in () at /usr/lib/libQt5Core.so.5 #3 0x7f4434957bea in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f44349581b6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f443495975f in () at /usr/lib/libQt5Core.so.5 #6 0x7f443219fa50 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7f44321a0096 in () at /usr/lib/libglib-2.0.so.0 #8 0x7f44321a0241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7f4434959a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.s
[kde-gtk-config] [Bug 413762] New: GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 Bug ID: 413762 Summary: GTK2 themes are not working at all and the previews aren't working either for only gtk2 Product: kde-gtk-config Version: 5.17.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: manutort...@chakra-project.org Reporter: freefreen...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 123678 --> https://bugs.kde.org/attachment.cgi?id=123678&action=edit Shot of gtk2 preview with theme applied. The gtk3 works fine SUMMARY STEPS TO REPRODUCE 1. Move your gtk theme to ~/.local/share/themes 2. Open system settings to apply theme 3. OBSERVED RESULT Once the theme is applied check the previews The previews for gtk2 are not working as well as the actual gtk2 themes such as gimp and inkscape. EXPECTED RESULT Previews should work as well as the actual gtk 2 theme itself SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 Kernel Version: 5.3.8-arch1-1 OS Type: 64-bit ADDITIONAL INFORMATION These are themes I have made with the actual Breeze GTK script so there may be something wrong with that script. I have the theme engine gtk-engines installed -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 406826] New: When trying to compare two folders in KDE Plasma on the latest 19.04.0-1 version you cannot select two folders and right click and compare. If you have single click activat
https://bugs.kde.org/show_bug.cgi?id=406826 Bug ID: 406826 Summary: When trying to compare two folders in KDE Plasma on the latest 19.04.0-1 version you cannot select two folders and right click and compare. If you have single click activated you cannot select from Kompare application because they open instead of select. Product: kompare Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: freefreen...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #2 from Josh Freeno --- Yes after further use it is the sub-pixel rendering doing this for sure and not the font anti-aliasing. When you choose RGB it blocks anti-aliasing from 0 to 99. There was a big update yesterday in Arch and I thought it might fix the problem but no it did not. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 5.1.16-arch1-1-ARCH So the bug is with the fonts but now I am sure it is the sub-pixel rendering doing this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #4 from Josh Freeno --- Is this a KDE problem or an Arch problem is the next question ??? It has been long enough for a fix to come down the chain so I am hoping this is not KDE and it is Arch but usually Arch is pretty good about fixing stuff within a day to two days at most. I am not seeing anyone talk about this anywhere. I posted on the KDE Reddit site and a couple people have the same problem. I really think it is an Arch problem now so maybe we need to both report to Arch. If you will report to Arch and leave me the link here I will follow up.I wanted to edit my bug report but I don't see how to edit it at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #9 from Josh Freeno --- I reported this days ago before the new updates even came out so I really don't understand what the deal is. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #10 from Josh Freeno --- (In reply to Michael from comment #8) > Sorry for typos. Right now I am having to use without sub-pixel rendering at all and i make themes for KDE so my screenshots look real nice as you can imagine. I have tried back and forth as you said but with not luck. This font config file goes into home directory correct -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #16 from Josh Freeno --- Created attachment 121471 --> https://bugs.kde.org/attachment.cgi?id=121471&action=edit This is how it locks itself after you enable sub-pixel rendering Here is my kdeglobals config after enabling sub-pixel rendering. Here is my info on OS. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 5.2.0-arch2-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #17 from Josh Freeno --- Created attachment 121472 --> https://bugs.kde.org/attachment.cgi?id=121472&action=edit This both my fontconfig and kdeglobals while I am in broken state. I add the fontconfig to the kdegobals because it would not let me select two files for some reason. This my first bug report so sorry if I have made mistakes in the reports. I just wanted to help get the info out there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #18 from Josh Freeno --- Also I would like to add that when I select defaults in font settings it does not reset fonts to the correct settings. It sets them to wrong size and and to noto black. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable
https://bugs.kde.org/show_bug.cgi?id=409374 Josh Freeno changed: What|Removed |Added Version|5.16.2 |5.16.3 Summary|You can not enable font |You can not enable |anti-aliasing with |sub-pixel rendering other |sub-pixel rendering because |than vendor default because |system settings will|system settings will put a |automatically put a check |check mark in the box to |mark in the box to block|block anti-aliasing and |anti-aliasing and make |make fonts unreadable and |fonts unreadable and you|you can remove check mark |can remove checkmark but|but gets placed back upon |gets placed back upon |opening and close |opening and close | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #19 from Josh Freeno --- Created attachment 121504 --> https://bugs.kde.org/attachment.cgi?id=121504&action=edit >From 5.16.2 thru 5.16.3 and after the Noto-font update 20190111-2 I still can not enable sub-pixel rendering other than vendor default because the check mark gets placed in the box to block aliasing This started in 5.16.2 and continues into 5.16.3. I am gonna leave my kdeglobals and my fontconfig. The Noto fonts were updated to "20190111-2" but this did not help the matter either. Fonts work fine with vendor default selected for sub-pixel rendering but if I try RGB then minutes later my font-aliasing is blocked from 0 to 99 so fonts become completely unusable. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #20 from Josh Freeno --- Created attachment 121505 --> https://bugs.kde.org/attachment.cgi?id=121505&action=edit KDE globals from 5.16.3 while not broken. The only thing that breaks the fonts in the sub-pixel rendering kde globals while not broken. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #24 from Josh Freeno --- Well I really don't understand now. Vendor default is the only thing saving me right now. Any other sub-pixel rendering is totally breaking fonts. I am now about to report another bug with KDE completely freezes 10 times a day and you can't do anything at all and I work on my PC so yea not very fun. Seems as if we are now using a BETA OS once again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 --- Comment #25 from Josh Freeno --- I have still got this problem as of today. It has done several times today already. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 Kernel Version: 5.2.2-arch1-1-ARCH OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #4 from Josh Freeno --- The gtk2 themes do work if placed in the root directory as @Mikhail Zolotukhin has stated. Inkscape and gimp still do not work if themes are placed in the home directory. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #6 from Josh Freeno --- In KDE we are instructed to put gtk themes into the ~/local/share/themes dir and not the the ~themes dir so I guess for now we need to place into in the root. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #8 from Josh Freeno --- (In reply to b2.temp from comment #7) > Can someone provide a script to do the fix (i.e some a sh with `find` `mv`, > etc) waiting for the Plasma fix ? > > For now it's not clear how to fix it manually. For example here on F31 I > have the BSM themes in ~/.themes and they do not work (the preview yes but > the few GTK2 apps I use, notably Lazarus and what is produced with it, don't > apply them). Open your terminal in the same folder as the themes you would like to move and do sudo mv or sudo cp-r with the name of theme theme after. mv for move cp for copy. The locations should be /usr/share/themes -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #10 from Josh Freeno --- You still have to apply the theme.This just moves or copies the themes to the root theme folder. On Sun, Jan 26, 2020 at 9:53 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=413762 > > --- Comment #9 from b2.t...@gmx.com --- > (In reply to Josh Freeno from comment #8) > > (In reply to b2.temp from comment #7) > > > Can someone provide a script to do the fix (i.e some a sh with `find` > `mv`, > > > etc) waiting for the Plasma fix ? > > > > > > For now it's not clear how to fix it manually. For example here on F31 > I > > > have the BSM themes in ~/.themes and they do not work (the preview yes > but > > > the few GTK2 apps I use, notably Lazarus and what is produced with it, > don't > > > apply them). > > > > Open your terminal in the same folder as the themes you would like to > move > > and do sudo mv or sudo cp-r with the name of theme theme after. mv for > move > > cp for copy. The locations should be /usr/share/themes > > Unfortunately the themes are still not applied for me. > I suspect that this is another problem. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] New: KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 Bug ID: 416967 Summary: KDE Partition manager fails to format USB with ntfs Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: freefreen...@gmail.com Target Milestone: --- Created attachment 125561 --> https://bugs.kde.org/attachment.cgi?id=125561&action=edit Screenshot of error SUMMARY NTFS format fails STEPS TO REPRODUCE 1. Open KDE Partition manager 2. Try to format USB with ntfs 3. OBSERVED RESULT It fails with errors EXPECTED RESULT Format USB with ntfs without errors SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416968] New: Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working
https://bugs.kde.org/show_bug.cgi?id=416968 Bug ID: 416968 Summary: Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working Product: partitionmanager Version: 4.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: freefreen...@gmail.com Target Milestone: --- Created attachment 125562 --> https://bugs.kde.org/attachment.cgi?id=125562&action=edit Screenshot after using the application SUMMARY Using the KDE Partition manager to format disk causes Dell touch pad tap-to-click to stop working and makes all the settings under tapping become greyed out until logging out and back into the desktop. STEPS TO REPRODUCE 1. Use KDE Partition manager to format disk 2. Close close the app 3. OBSERVED RESULT Tap-to-click stops working on touch pad EXPECTED RESULT Should not have any effect on touch pad at all SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION All the selections under tapping in input settings become greyed out until logging out and back into the desktop. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #2 from Josh Freeno --- (In reply to Andrius Štikonas from comment #1) > What are the errors? > > Does "mkfs.ntfs --quick --verbose deviceNode" work? Screenshot is of what is does every time and I tried this three or four times but I finally just put into my windows PC and formatted it so I did not try to manually do it. I have package ntfs-3g installed too. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #4 from Josh Freeno --- (In reply to Andrius Štikonas from comment #3) > Unfortunately, without more info, I won't be able to do anything. > I just tried with my USB, it works fine. > > My theory (although I have no strong proof) is that for some reason your > Linux kernel marked USB as read only... Note that error happened immediately > (in 0 seconds). In that case there is nothing KDE Partition Manager can do... What more info do you need or want and I will get to you as soon as possible. Unless the partition manager is marking it read only then I can tell you that is not the problem. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #6 from Josh Freeno --- (In reply to Andrius Štikonas from comment #5) > (In reply to Josh Freeno from comment #4) > > (In reply to Andrius Štikonas from comment #3) > > > Unfortunately, without more info, I won't be able to do anything. > > > I just tried with my USB, it works fine. > > > > > > My theory (although I have no strong proof) is that for some reason your > > > Linux kernel marked USB as read only... Note that error happened > > > immediately > > > (in 0 seconds). In that case there is nothing KDE Partition Manager can > > > do... > > > > What more info do you need or want and I will get to you as soon as > > possible. Unless the partition manager is marking it read only then I can > > tell you that is not the problem. > > If you can, try to format the same USB again and see if you can still > reproduce this. > > If yes, try to see more logs by clicking Details button. > > Running "cat /sys/block/sdb/ro" might tell you if device is read only. > Running "dmesg" in terminal might also give some clues. > > ntfs-3g is needed but I think in this case error happens much earlier. You > can't even create partition (formatting partition happens after first > creating unformatted partition). I will look for logs although it happened three or four times on same USB. The very same USB I have formatted with windows to go on it now. I will look though and post here anything I find. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413529] System Settings Crash while switching to the window decorations section
https://bugs.kde.org/show_bug.cgi?id=413529 Josh Freeno changed: What|Removed |Added CC||freefreen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413529] System Settings Crash while switching to the window decorations section
https://bugs.kde.org/show_bug.cgi?id=413529 --- Comment #1 from Josh Freeno --- Created attachment 123835 --> https://bugs.kde.org/attachment.cgi?id=123835&action=edit New crash information added by DrKonqi systemsettings5 (5.17.2) using Qt 5.13.2 - What I was doing when the application crashed: When opening the window decorations section my system settings crashes and it is happening quite often. I have all my updates applied on stable Arch. -- Backtrace (Reduced): #6 0x7fbd13375a96 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /usr/lib/libQt5Core.so.5 #7 0x7fbd125ccfd8 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fbd125db202 in QV4::QmlListWrapper::toVariant() const () at /usr/lib/libQt5Qml.so.5 #9 0x7fbd1251b726 in () at /usr/lib/libQt5Qml.so.5 #10 0x7fbd1251bba5 in QV4::ExecutionEngine::toVariant(QV4::Value const&, int, bool) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413529] System Settings Crash while switching to the window decorations section
https://bugs.kde.org/show_bug.cgi?id=413529 --- Comment #2 from Josh Freeno --- Created attachment 123899 --> https://bugs.kde.org/attachment.cgi?id=123899&action=edit New crash information added by DrKonqi systemsettings5 (5.17.3) using Qt 5.13.2 - What I was doing when the application crashed: Opening window decorations causes the systemsettings to crash. This happens to me 3 out of 10 times. It happens when opening that section in the settings. You do not have to change window decorations just open that section. -- Backtrace (Reduced): #6 0x7f7dd5a36a96 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7dd4c8dfd8 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f7dd4c9c202 in QV4::QmlListWrapper::toVariant() const () at /usr/lib/libQt5Qml.so.5 #9 0x7f7dd4bdc726 in () at /usr/lib/libQt5Qml.so.5 #10 0x7f7dd4bdcba5 in QV4::ExecutionEngine::toVariant(QV4::Value const&, int, bool) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 414209] New: Kinfocenter crashes when opening energy information
https://bugs.kde.org/show_bug.cgi?id=414209 Bug ID: 414209 Summary: Kinfocenter crashes when opening energy information Product: kinfocenter Version: 5.17.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Energy Information Assignee: k...@privat.broulik.de Reporter: freefreen...@gmail.com Target Milestone: --- SUMMARY The Kinfocenter crashes while opening the energy information section. STEPS TO REPRODUCE 1. Open Kinfo 2. Select energy information 3. OBSERVED RESULT Kinfocenter crashes EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.3.11-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION I seen this in the bug reports but it says resolved/fixed but it is not resolved. -- You are receiving this mail because: You are watching all bug changes.
