[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Giusy Digital changed: What|Removed |Added CC|kurmi...@libero.it | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it --- Comment #166 from Giusy Digital --- Definitely not resolved. The following commit (https://cgit.kde.org/konsole.git/commit/?id=54820e0ff2745add8b8353f538ad67d66b657d49) is causing weird font showing inside konsole. Commenting `QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true);` in `src/main.cpp` or setting it to `false` or launching the application with `QT_AUTO_SCREEN_SCALE_FACTOR=0` fixes the issue. See also here: https://bbs.archlinux.org/viewtopic.php?pid=1881713 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Giusy Digital changed: What|Removed |Added CC|kurmi...@libero.it | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 --- Comment #6 from Giusy Digital --- (In reply to David Edmundson from comment #5) > One thing that I can't follow is you say your fontconfig were changed just > on it's own? > > I can see how they're overwritten if you open and close the font KCM, but I > can't see a path that syncs on startup. My system-wide fontconfig was not changed. Kcm keeps rewriting its own fontconfig and there's no way to keep it empty avoiding to override the system options. I noticed this behavior at the opening of the kcm and at the start of the session. In every case, the file emptied before was rewritten after. Maybe this is not a big issue for the majority of users, but it's not a good behavior. Just write what the user choose in the kcm and give him/her the chance to keep it empty leaving the option to rely on system ones. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 --- Comment #4 from Giusy Digital --- First thing to do is to readd "leave system congif" which was previously present and don't know for what reason it was removed. That could just resolve the issue leaving the local config file empty. Then writing kcm config in a separate config is a good idea also. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 --- Comment #2 from Giusy Digital --- Not a bug? It broke my config and this should not be considered a bug? When you broke something as a developer, do not expect the user to fix it in a configuration file. Please, fix it in the graphic interface. I think people uses Plasma Desktop to configure things by the graphic interface, not for writing in a text file because you chose a bad configuration as the default. There's also the issue that disabling the antialiasing in the kcm will gray out the other options, which is completely meaningless. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] New: Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 Bug ID: 413133 Summary: Plasma always forces its own font configuration breaking system one Product: systemsettings Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: kurmi...@libero.it CC: unassigned-b...@kde.org Target Milestone: --- SUMMARY Since the last upgrade on Arch Linux, Plasma Desktop is forcing it's own fontconfig on local settings. In details, it is overwriting antialiasing 'on', hintslight and subpixel rendering 'rgb'. I'm aware that this is the optimal configuration in most cases, but there's also some particular cases where this configuration is not chosen by the user to due his/her specific system characteristics. The bad behavior of this new upgrade is that even if I choose to NOT use kcm font settings, plasma keeps overwriting ~/.config/fontconfig/fonts.conf with its own options. This is also breaking my system-wide settings that I accurately wrote inside /etc/fonts/conf.d/ having the purpose to avoid to reconfig fonts for every user on my Linux installation. In fact, having Plasma to use its local configuration made fonts looks very bad on my systems, especially inside GTK browsers like Firefox and Chromium. The only way I can avoid this behavior is to symlink ~/config/fontconfig to /dev/null, which is unacceptable on a desktop environment like Plasma that claims to be highly customizable. Doing that I got a good looking fonts having all applications to rely only on system fontconfig, like it should be in my specific context where I configured fonts directly in /etc/fonts and do NOT want others to interfere with it. STEPS TO REPRODUCE 1. By default Plasma Desktop write it's own options inside ~/config/fontconfig/fonts.conf 2. Disable options under fonts kcm (plasma systemsettings5) OBSERVED RESULT ~/config/fontconfig/fonts.conf contains the default settings, which I don't want. Besides, If I empty it manually, Plasma will rewrite it when I relog into the session or enter into fonts kcm. EXPECTED RESULT Plasma should leave that file blank and does NOT have to interfere with system-wide configuration. ADDITIONAL INFORMATIONS I remember that font kcm had some options where you specified to leave the system configuration. It seems that these ones were removed? Why? Besides, why antialiasing is enabling the other settings like subpixel rendering and hinting style? Do you know that these options are independent? Maybe I want to configure hints 'full' leaving antialiasing 'off'. But this is not intended to be done inside the kcm because disabling antialiasing is graying out the others. The concept is just wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 Giusy Digital changed: What|Removed |Added Platform|Archlinux Packages |Compiled Sources Version|5.16.4 |5.16.5 --- Comment #11 from Giusy Digital --- New version 5.16.5 of plasma-pa on Arch Linux and the issue is still there. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 --- Comment #10 from Giusy Digital --- New Plasma version landed on Arch Linux and the bug is not fixed yet. I still have the microphone indicator while I'm not using a microphone. As I said before, "pulseeffects (mic)" is an input sink monitor and it should not count as a microphone. I think it's simple, just don't consider sinks showed as 'device class="monitor"' in "pactl list sources". -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 --- Comment #9 from Giusy Digital --- But since it's built-in, will you get the indicator even without pulseeffects? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 --- Comment #6 from Giusy Digital --- If you mean "don't actually have microphone connected to the system", that's okay I think. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 --- Comment #4 from Giusy Digital --- If you tested with PulseEffects and it's resolved, close the bug. Otherwise I will test when the update is coming onto Arch Linux. Thanks anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 --- Comment #2 from Giusy Digital --- (In reply to Kai Uwe Broulik from comment #1) > I ran the commands in the GitHub ticket: > > pactl load-module module-null-sink sink_name="test" > gst-launch-1.0 pulsesrc device="test.monitor" ! queue ! pulsesink > > I get a recording stream that isn't marked as virtual: > "VirtualStream" QVariant(bool, false) Do not know why QVariant reports it like that, but install PE and start an a/v stream, then run "pactl list sources": Name: PulseEffects_mic.monitor Description: Monitor of PulseEffects(mic) Driver: module-null-sink.c Properties: device.description = "Monitor of PulseEffects(mic)" device.class = "monitor" device.icon_name = "audio-input-microphone" -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410637] New: Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor
https://bugs.kde.org/show_bug.cgi?id=410637 Bug ID: 410637 Summary: Do not show microphone icon when an application (like PulseEffects) is using a recording PulseAudio sink monitor Product: plasma-pa Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kurmi...@libero.it CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Because of a bad implementation, Plasma is showing the microphone icon in the system tray when PulseEffects is running, reporting that "PulseEffects is using the microphone". Read here for more info: https://github.com/wwmm/pulseeffects/issues/547#issuecomment-517027185 As explained in the reported issue, PulseEffects loads a virtual monitor sink where it records the input stream, but this sink should not be considered as a real microphone the user is using. So Plasma should only consider non-virtual recording sinks to show the microphone icon in the system tray. STEPS TO REPRODUCE 1. Install and launch PulseEffects. 2. Launch any audio/video stream from whichever application 3. PulseEffects pipeline will be initialized and a microphone icon is showed on the system tray even if the user is not really using a microphone. EXPECTED RESULT No microphone icon showed, unless the user will really connect and use a microphone on its system. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 --- Comment #11 from Giusy Digital --- First thing would be something for totally disabling geolocalization inside the application just to avoid that annoying popup at every startup. KTottent is a good torrent client, but unfortunately it's no longer maintained, I ended up using transmission-qt. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it --- Comment #4 from Giusy Digital --- https://dev.maxmind.com/geoip/geoip2/geolite2/ https://support.maxmind.com/geolite-legacy-discontinuation-notice/ On January 2, 2019, we discontinued our GeoLite Legacy databases. This discontinuation was first announced on January 2, 2018. GeoLite Legacy databases are no longer available for download. Attempting to download a GeoLite Legacy database file will result in the error: “Database edition not found”. Free geolocation data is still available through our GeoLite2 databases. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 --- Comment #12 from Giusy Digital --- Okay, let's wait. Meanwhile, while we're waiting, I'd like to tell you my opinion. Maybe the reason it's the same of wasting time on writing a new volume manager plasma-pa exclusively for Pulseaudio when you already have a working volume manager KMix suitable for both alsa and Pulseaudio. So I think you will waste other time waiting to write from zero a new touchpad KCM for X11 rather than adapt an already usable KCM which only issue is not applying its config at startup. I think Plasma is a good DE, but I can't understand some of choices you developers made. Fortunately system configurations can be applied even without the help of user interface, but if I use a DE and I'm forced to use the shell or write config in a text file, you made something wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #10 from Giusy Digital --- I'm not using plasma-pa anymore. Kmix is better because you can choose to control whatever output you want, even one that's not marked as the default sink. Anyway, if it's working, you can switch the status of this bug report to fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update
https://bugs.kde.org/show_bug.cgi?id=398538 --- Comment #8 from Giusy Digital --- Is it fixed then? Anyway, KMix is working pretty fine for me and I don't need plasma-pa anymore. I wonder why Plasma did a volume manager for Pulseaudio if there's already something like KMix that works for ALSA and Pulseaudio. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 --- Comment #10 from Giusy Digital --- Current status of this bug report is WAITINGFORINFO. What info are you waiting for? Can you explain me that? This are my touchpad settings on Plasma: https://imgur.com/a/edLyDVJ Tons of useless options, most of all greyed out and others half-working (acceleration that supports only positive values rather than 1- to 1 range). It's build for synaptics, but do you know it's deprecated from years? Pointing devices KCM works, it only needs to be well implemented to apply settings at startup. In my current status, I have to apply touchpad configurations with xinput from a script executed at Plasma startup. It's quite a shame for a DE like Plasma. It's years you can't do a touchpad KCM for X11, maybe you don't have time or people to do it, I understand, but if there's something that just works, what are you waiting for? Someone to write another touchpad KCM starting from zero? It's pointless. It's more reasonable that you just merge pointing devices and apply settings at startup and the problem is solved. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it --- Comment #2 from Giusy Digital --- (In reply to Nate Graham from comment #1) > I'm not sure of the history here (it was before my time), but it's a shame > this never went in. Who was your mentor? Can you fill in some of the blanks > regarding why this never got merged? Is it really relevant? This works even if it looks old. It's way better than that useless default kcm touchpad with tons of options that only works with old synaptic driver. Please, merge it. It doesn't change nothing for me because I already have it thanks to AUR, but other people using libinput without Wayland needs it on other distributions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it -- You are receiving this mail because: You are watching all bug changes.
