[systemsettings] [Bug 433115] New: Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-17 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 Bug ID: 433115 Summary: Global Scaling Options Seems to "lower" resolution unlike old "force font DPI" Product: systemsettings Version: 5.21.0 Platform: Archlinux Packages

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-17 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 Dimitris Giannos changed: What|Removed |Added CC||aclassifiedm...@gmail.com -- You are

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-17 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #2 from Dimitris Giannos --- I will try to answer all those. But I cannot guarantee when that happens. (Not because I'm lazy) -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-18 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #4 from Dimitris Giannos --- Created attachment 135829 --> https://bugs.kde.org/attachment.cgi?id=135829&action=edit 200% Scaling Here is the image with Global Scaling set to 200%. It seems like it has affected only apps oth

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-18 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #5 from Dimitris Giannos --- Created attachment 135830 --> https://bugs.kde.org/attachment.cgi?id=135830&action=edit 150% Scaling And here is with 150%. I think that they all downgrade. Here it seems like it downgrades less. You

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-18 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #6 from Dimitris Giannos --- I also opened inkscape. Seems like everything has been scaled without loss of quality. Also notice from the screenshots that plasma's mouse has been affected badly. -- You are receiving this mail because

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-18 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #8 from Dimitris Giannos --- Where am I supposed to write this line? I typed it in terminal and seems like, after restarting, nothing changed. -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"

2021-02-19 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #10 from Dimitris Giannos --- The command seemed to make Firefox look neater, probably as it should be in this screen, but it seems like there were a lot of screen tearings (or some similar bugs) and plasma couldn't handle it, so it

[plasmashell] [Bug 433303] New: Executable: plasmashell PID: (Various) Signal: Segmentation fault (11)

2021-02-20 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433303 Bug ID: 433303 Summary: Executable: plasmashell PID: (Various) Signal: Segmentation fault (11) Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS

[kwin] [Bug 433307] New: One curve for all 4 window edges

2021-02-20 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433307 Bug ID: 433307 Summary: One curve for all 4 window edges Product: kwin Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist

[kde] [Bug 433325] New: Crashes after Screen Locks

2021-02-20 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 Bug ID: 433325 Summary: Crashes after Screen Locks Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash

[plasmashell] [Bug 433303] Executable: plasmashell PID: (Various) Signal: Segmentation fault (11)

2021-02-22 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433303 --- Comment #4 from Dimitris Giannos --- Oh, I didn't see that there were already other posts regarding this. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 433307] Have the same corner radius for all 4 window edges

2021-02-22 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433307 --- Comment #4 from Dimitris Giannos --- Then, how about no curvy edges and just angles? Although I think this will lool, perhaps, too strange for Plasma. I don't know. -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-22 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #2 from Dimitris Giannos --- I have reinstalled plasma and I will see whether they will pop up again. Sorry, I thought I had attached a screenshot with dev info from all 3 crashes. Also forgot to mention that this happened in wayland. I&#

[kwin] [Bug 433307] Have the same corner radius for all 4 window edges

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433307 --- Comment #5 from Dimitris Giannos --- Created attachment 136078 --> https://bugs.kde.org/attachment.cgi?id=136078&action=edit Window corners when snapped to screen corners/edge Could also add a new feature (not sure how had to implement:

[kwin] [Bug 433307] Have the same corner radius for all 4 window corners

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433307 Dimitris Giannos changed: What|Removed |Added Summary|Have the same corner radius |Have the same corner radius

[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"; consider re-adding it as an option

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #14 from Dimitris Giannos --- If that's more convenient for everyone.. then yes. -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #3 from Dimitris Giannos --- Created attachment 136089 --> https://bugs.kde.org/attachment.cgi?id=136089&action=edit My Displays Okay, I was given the luck to find more info about this case. This will take some comments because

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #4 from Dimitris Giannos --- Created attachment 136090 --> https://bugs.kde.org/attachment.cgi?id=136090&action=edit Crash Reports Here are the 3 reports I get after every screen lock WHILE I have ONLY the DP (60Hz) display enabl

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-23 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #5 from Dimitris Giannos --- Created attachment 136092 --> https://bugs.kde.org/attachment.cgi?id=136092&action=edit WeirdDesktop And here is what I saw after a screen lock while having both displays enabled (one on top of th

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-24 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #7 from Dimitris Giannos --- Alright, I'll try the next times... But I really wonder why they don't contain debug symbols by default... -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-02-24 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #9 from Dimitris Giannos --- Ye, now I have to recompile everything from source :/ (or I don't get it). Would be so much better if debug symbols were enabled by default in official packages. -- You are receiving this mail because

[kscreenlocker] [Bug 433577] New: Lock Screen: need to click on type bar before writing password to unlock

2021-02-25 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433577 Bug ID: 433577 Summary: Lock Screen: need to click on type bar before writing password to unlock Product: kscreenlocker Version: 5.10.3 Platform: Archlinux Packages

[plasmashell] [Bug 433577] Lock Screen: need to click on type bar before writing password to unlock

2021-02-25 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433577 --- Comment #2 from Dimitris Giannos --- Well yes, 5.21... what do you mean "fixed"? -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 433577] Lock Screen: need to click on type bar before writing password to unlock

2021-02-26 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433577 --- Comment #4 from Dimitris Giannos --- It seems to be a bit more complicated: I realized that before my screen is disabled, there is a small period that plasma log you out in lock screen and after some seconds or minutes it disables my screen. After

[plasmashell] [Bug 433577] Lock Screen: need to click on type bar before writing password to unlock

2021-02-26 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433577 --- Comment #6 from Dimitris Giannos --- If by "login screen" you mean sddm then no. I'm talking about the screen that appears NOT when you command to log out but when you let the device alone for some minutes (and then the screen turns

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-03-12 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #12 from Dimitris Giannos --- Well I don't get the bug anymore after rearranging screens. I get it rarely but I don't know how to reproduce it. I also suspect it's a drivers' issue. Should this be closed for now? -- Yo

[ksmserver] [Bug 433325] Crashes after Screen Locks

2021-03-12 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=433325 --- Comment #13 from Dimitris Giannos --- (In reply to Dimitris Giannos from comment #12) > Well I don't get the bug anymore after rearranging screens. I get it rarely > but I don't know how to reproduce it. I also suspect it&#x

[plasmashell] [Bug 434487] New: New Behaviour: "Windows can cover" make panel to move out of boundaries instead of covering.

2021-03-16 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=434487 Bug ID: 434487 Summary: New Behaviour: "Windows can cover" make panel to move out of boundaries instead of covering. Product: plasmashell Version: 5.21.2 Platform: Archlinux Packa

[plasmashell] [Bug 434487] New Behaviour: "Windows can cover" make panel to move out of boundaries instead of covering.

2021-03-17 Thread Dimitris Giannos
https://bugs.kde.org/show_bug.cgi?id=434487 --- Comment #1 from Dimitris Giannos --- Ah, I also noticed that once I hover over to the edge to which I have my panel, while having a window maximized, the panel appears but doesn't auto-disappear... Is this what should happen? I don't rem