[kigo] [Bug 316041] Cursor keeps flashing, sometimes invisible
https://bugs.kde.org/show_bug.cgi?id=316041 Yannis changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME CC||ya...@mailbox.org Status|NEEDSINFO |RESOLVED --- Comment #5 from Yannis --- (In reply to Justin Zobel from comment #3) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Hello, thanks for the reminder. I no longer have that machine which ran on NVIDIA graphics. I have a newer computer now, again on NVIDIA with KDE and I've just tested the game. Kigo worked flawlessly and it is a very polished experience. Thank you for making this great program. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471387] Feature request: Load existing pictures into Spectacle Annotations Editor via GUI
https://bugs.kde.org/show_bug.cgi?id=471387 --- Comment #5 from Yannis --- (In reply to Noah Davis from comment #4) > There are dedicated image editors with more functionality and more editing > focused user interfaces than Spectacle will ever have, so I think it could > be fair to tell people to use them instead. However, maybe you want this > because Spectacle's annotation UI is more desirable in certain ways than the > image editors you know? Perhaps if we add a hamburger button (main menu > button), we could move some of the existing less commonly used controls > there and then we'd have room to add a GUI option to open an image file. I do find the annotation UI much more desirable than alternatives. I also use ShareX on Windows (a FOSS program) for the same purpose, which likewise has a strong annotation editor built in. It is the focus on the annotation experience that makes it so useful. In particular, it is useful for quickly hiding confidential information (by blurring or pixellating), which is very useful in my working environment. Oftentimes, it is unclear which screenshots will be the most useful so it is only worth blurring/pixellating confidential text at the time of sharing - which is later than whenever the screenshot was captured. I also occasionally use it for demonstration purposes, so I would again be modifying an image hours/days after I have captured and stored it, adding arrows, and saving a separate copy. I agree that the existing image editor is a more niche feature, so it would be a good fit for the hamburger menu as far as placing a button goes. There are two more key considerations: 1. That passing an image to spectacle with 'Open with' should open it in editing mode. I am happy to log a separate issue for this if it would be useful to keep track. 2. That Spectacle's editor should always act as if it is in multi-window mode if it was used to open an existing image, regardless of the chosen setting. That is, if a user hits PrtSrc while in the editor window, it should not take a new screenshot. Perhaps this could a different setting, enabled by default. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471387] Feature request: Load existing pictures into Spectacle Annotations Editor
https://bugs.kde.org/show_bug.cgi?id=471387 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471387] Feature request: Load existing pictures into Spectacle Annotations Editor
https://bugs.kde.org/show_bug.cgi?id=471387 --- Comment #3 from Yannis --- As an interested party, could I ask that this is kept open please? I agree with the reporter that having an Edit button after taking a screenshot is a great advancement. However, the other use case of loading arbitrary images from storage to edit, has not been fully met (as of Spectacle 24.05 on my distribution). I was not aware of the command line switch so glad to hear it is possible. I think that to close the request, you would need to implement graphical interface for this too. It could perhaps have a different desktop file, or allow for multiple windows in order to use an editor separately. Either way, it would need some consideration as to how the user interface will be presented. Thanks for your consideration. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 397602] Configuration files should contain only persistent configuration and not state
https://bugs.kde.org/show_bug.cgi?id=397602 Yannis changed: What|Removed |Added CC||anthymidis.ioan...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471375] Firefox copy failure with middle-click-to-paste disabled
https://bugs.kde.org/show_bug.cgi?id=471375 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 452748] Group albums by Artist in Album view
https://bugs.kde.org/show_bug.cgi?id=452748 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 407964] Option to sort by Album Artist
https://bugs.kde.org/show_bug.cgi?id=407964 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 422599] Sort by SORT-suffix using {ALBUM|ALBUMARTIST|ARTIST|COMPOSER|TITLE}SORT tags if available
https://bugs.kde.org/show_bug.cgi?id=422599 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417964] Artist and Album names are case sensitive
https://bugs.kde.org/show_bug.cgi?id=417964 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 463175] Album should be grouped even if there are multiple artists linked to it.
https://bugs.kde.org/show_bug.cgi?id=463175 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440904] Sidebar for commands
https://bugs.kde.org/show_bug.cgi?id=440904 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416687] Add support for Windows .URL files to open Internet URL from file content via KDE Dolphin
https://bugs.kde.org/show_bug.cgi?id=416687 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439610] Autoscroll using middle click
https://bugs.kde.org/show_bug.cgi?id=439610 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466293] Cannot scroll beyond the border of the screen using Wayland
https://bugs.kde.org/show_bug.cgi?id=466293 Yannis changed: What|Removed |Added CC||ya...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464208] KDE Connect Cannot Send SMS
https://bugs.kde.org/show_bug.cgi?id=464208 yannis changed: What|Removed |Added CC||yan...@tsopokis.gr Platform|Neon|Android OS|Linux |Android 4.x -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464208] KDE Connect Cannot Send SMS
https://bugs.kde.org/show_bug.cgi?id=464208 yannis changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430838] New: Grey out slider when is global mute enabled (tweak to disabled state)
https://bugs.kde.org/show_bug.cgi?id=430838 Bug ID: 430838 Summary: Grey out slider when is global mute enabled (tweak to disabled state) Product: plasmashell Version: master Platform: Compiled Sources OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: anthymidis.ioan...@gmail.com CC: n...@kde.org, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 134339 --> https://bugs.kde.org/attachment.cgi?id=134339&action=edit Audio volume applet illustrating lack of desired style I was advised by Nate to post this here: https://pointieststick.com/2020/12/18/this-week-in-kde-all-the-things/#comment-18154 I have also attached the image I was referring to - the bars are the audio bars and it would be nice to have them go grey when global mute is on in the audio plasmoid. I'll reproduce the comment here also for posterity: "There is one concern I still have – to be clear this is going from your screenshot only. The position of the Global Mute is the best now for sure. But a concern remains about how it indicates its state. I understand from your screenshot that those devices are at the levels shown, but global mute is enabled. Can this be made a bit clearer so all the bars get greyed out when you enable global mute? I think some redundancy would help there as it’s easy to look at the enabled-looking devices and wonder why your audio isn’t working. Thanks!" Nate's (cc'd) reply: "> Can this be made a bit clearer so all the bars get greyed out when you enable global mute? They do, sort of. When global mute is activated, the sliders enter their disabled state. The disabled state for Plasma Breeze Theme sliders makes the handle partially transparent, but not the bar itself. So this would need to be fixed by changing the appearance of the disabled state for the Plasma Breeze theme styling for the Slider control itself. Can you submit a bug report to Plasmashell | Theme – Breeze asking for that?" As requested. 🙂 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 393700] File type editor doesn't respect set order after pressing Apply
https://bugs.kde.org/show_bug.cgi?id=393700 Yannis changed: What|Removed |Added CC||ya...@mailbox.org --- Comment #7 from Yannis --- Created attachment 178833 --> https://bugs.kde.org/attachment.cgi?id=178833&action=edit The preferred program resets on plaintext, but not other file types -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 393700] File type editor doesn't respect set order after pressing Apply
https://bugs.kde.org/show_bug.cgi?id=393700 --- Comment #8 from Yannis --- I have confirmed the bug on version 6.3.0. It is definitely happening on plain text but not every file type. One suggestion for this specific bug: The product might be better listed as systemsettings and the component as kcm_filetypes, but I don't seem to have the ability to do this on this ticket. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure
https://bugs.kde.org/show_bug.cgi?id=483130 Charitakis Yannis changed: What|Removed |Added CC||kde-yan...@ych.gr --- Comment #1 from Charitakis Yannis --- Hello all, After installing and configuring the fingerprint sensor, I had the same issue as above. But I think I have found a workaround. Please note however that I am far from an expert and I maybe wrong. I am on EndeavourOS using KDE Plasma 6.0.2, linux 6.6.22-1-lts on a thinkpad X270. Based on man pam_fprintd: ``` LIMITATIONS The PAM stack is by design a serialised authentication, so it is not possible for pam_fprintd to allow authentication through passwords and fingerprints at the same time. It is up to the application using the PAM services to implement separate PAM processes and run separate authentication stacks separately. This is the way multiple authentication methods are made available to users of gdm for example. ``` Since kscreenlocker does permit both password and finderprint at the same time, I believe this is what it does. That is, it uses two separate PAM processes: One, let's call it password PAM process, is using the /etc/pam.d/kde configuration. The other, let's call it fingerprint PAM process, using the /etc/pam.d/kde-fingerprint configuration. kscreenlocker will unlock if any of the two above PAM processes succeeds. The other however will fail. When using the password PAM process, succesful login will clear the previous faillock incidents. This is what it happens by observing the contents of the original /etc/pam.d/kde. The fingerprint PAM process though, differs. Unfortunately I didn't keep the original /etc/pam.d/kde-fingerprint, but the updated seems to work correctly: [root@gordon pam.d]# cat kde-fingerprint #%PAM-1.0 auth requiredpam_shells.so auth requisite pam_nologin.so auth requisite pam_faillock.so preauth # <--- I think I added this line -auth requiredpam_fprintd.so auth optionalpam_permit.so auth requiredpam_env.so auth requiredpam_faillock.so authsucc # <--- I think I added this line account requisite pam_faillock.so preauth # <--- Surely added this line accountinclude system-local-login account requiredpam_faillock.so authsucc # <--- Surely added this line password requiredpam_deny.so sessioninclude system-local-login [root@gordon pam.d]# The above change was based on the following note from pam_faillock: [...] Due to complications in the way the PAM stack can be configured it is also possible to call pam_faillock as an account module. In such configuration the module must be also called in the preauth stage.[...] Using the above configuration and unlocking multiple times using the fingerprint works ok. Still though, there is a single faillock incident after each try, but they do not accumulate. Faillock is being reset by the fingerprint PAM process and just after reset the password PAM process registers a failed incident. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure
https://bugs.kde.org/show_bug.cgi?id=483130 --- Comment #3 from Charitakis Yannis --- (In reply to TraceyC from comment #2) > Thank you for the bug report. Unfortunately we were not able to get to it > yet. Can we ask you to please check if this is still an issue with Plasma > 6.3.2 (the latest released version)? Thanks! Hello, thank you for your time. I am on Plasma 6.3.0 and it seems resolved but I am on different hardware (same system disk as before but on a different laptop). It works ok and it doesn't lock me out as before after a few succesful but in short time logins. I do however get a relevant message on the logs everytime I succesfully login with fingerprint: Μαρ 05 07:17:07 gordon kscreenlocker_greet[1299820]: pam_unix(kde:auth): username [haritak] obtained Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: pam_unix(kde:auth): authentication failure; logname=haritak uid=1000 euid=1000 tty= ruser= rhost= user=haritak Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: Failed to write to the pipe: Εσφαλμένος περιγραφέας αρχείου. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure
https://bugs.kde.org/show_bug.cgi?id=483130 --- Comment #8 from Charitakis Yannis --- (In reply to Anthony Wang from comment #7) > I'm also running into this bug in Plasma 6.3.2 on Arch Linux. If I turn my > computer off and on four times and use fingerprint login, then it locks me > out for 10 minutes the fourth time. Adding the line `auth required > pam_faillock.so authsucc` to the end of the `auth` section in > `/etc/pam.d/kde-fingerprint` fixes this problem for me. I already had this line in my config, maybe that's why I wasn't locked out. ``` #%PAM-1.0 auth requiredpam_shells.so auth requisite pam_nologin.so auth requisite pam_faillock.so preauth -auth requiredpam_fprintd.so auth optionalpam_permit.so auth requiredpam_env.so auth requiredpam_faillock.so authsucc < this line account requisite pam_faillock.so preauth accountinclude system-local-login account requiredpam_faillock.so authsucc password requiredpam_deny.so sessioninclude system-local-login ``` If it's not there by default, I can't recall when did I place it there sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure
https://bugs.kde.org/show_bug.cgi?id=483130 --- Comment #5 from Charitakis Yannis --- (In reply to Charitakis Yannis from comment #3) > (In reply to TraceyC from comment #2) > > Thank you for the bug report. Unfortunately we were not able to get to it > > yet. Can we ask you to please check if this is still an issue with Plasma > > 6.3.2 (the latest released version)? Thanks! > > Hello, thank you for your time. > I am on Plasma 6.3.0 and it seems resolved but I am on different hardware > (same system disk as before but on a different laptop). > It works ok and it doesn't lock me out as before after a few succesful but > in short time logins. > > I do however get a relevant message on the logs everytime I succesfully > login with fingerprint: > > Μαρ 05 07:17:07 gordon kscreenlocker_greet[1299820]: pam_unix(kde:auth): > username [haritak] obtained > Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: qt.qpa.wayland: Could > not create EGL surface (EGL error 0x3000) > Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: pam_unix(kde:auth): > authentication failure; logname=haritak uid=1000 euid=1000 tty= ruser= > rhost= user=haritak > Μαρ 05 07:17:09 gordon kscreenlocker_greet[1299820]: Failed to write to the > pipe: Εσφαλμένος περιγραφέας αρχείου. One more note which maybe relevant, back then I was using validity-sensors (https://aur.archlinux.org/packages/python-validity) since my hardware was not supported. When I changed my laptop, I had removed validity-sensors and installed fprintd. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361862] New: Feature request: I would like the view area to remain the same when switching pages
https://bugs.kde.org/show_bug.cgi?id=361862 Bug ID: 361862 Summary: Feature request: I would like the view area to remain the same when switching pages Product: okular Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: yannis1...@gmail.com In Skim (on the Mac) I have the feature that when I select to view an area of the page (for example the lower part of the page to inspect footnotes) and I switch to the next page, the area does not change. So, for example, I can check all footnotes of a document without having to draw the window to the bottom every time, and without having to view the entire page at once. Is it possible to have this behavior with Okular on Debian? For the moment, what Okular does (as well as evince) is to switch to the top of the page whenever I switch to another page. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
