Hi, I’m unable to remove spectacle that came with Plasma 6.3 as it apparently breaks dependency required by plasma-meta. I use Flameshot instead and do not want spectacle. According to the changelog of 6.3, it is not crucial for KDE at all. It wasn’t crucial before either, as I removed spectacle MONTHS ago.
Why is this the case now? Do they need to push their bloat just cause?
Are you using Arch? KDE does not control their packaging, you’ll have to ask them.
Oh yeah I forgot to specify that. I am using Arch Linux. Is that an Arch problem?
I wouldn’t call it a problem, rather a decision made by the Arch packagers.
There doesn’t seem to be a hard dependency on spectacle, except for plasma-meta.
1 Like
Why would you want to?
I specifically said why I don’t want spectacle on the first message.
Who said I’m worried about disk space? Like I don’t understand. Do you think people who don’t want bloat run their OS on 32 GB flash drive or something? I’m not that extreme. I would just use Arch without any DE if I was that extreme. My only concern is that having more than one screenshot program when the other one fits my needs perfectly. And it somehow messes with Prtsc key. I did configure it so Spectacle wouldn’t use Prtsc and Flameshot still can’tuse Prtsc. Is that hard to understand?
It was extremely simple to understand your initial post, as it was written. I have also seen this kind of reaction from people over the years who feel offended when they cannot have complete control over things like this - to blame this on KDE trying to force you to accept software or some other kind of malicious intent is frankly ridiculous - hence my assertion that it is possibly the result of some kind of non-typical response… apparently flagged and hidden.
Still, this is a common issue in some forums, where people state a ‘problem’ unrelated to their actual issue (though sometimes this isn’t the case - as I remember a similar argument about someone unable to completely purge vlc from their system due to it’s being chosen as the backend for other items).
However, now that you have added another clause - seemingly also asking if it was difficult to understand from your original post (where it was NOT included that you have an issue with PrScr)…
You had merely stated that your issue is that you can no longer remove that single application (which is part of a meta package and unrelated to your problem with the Prtsc key).
As you can see by all the responses, I am not alone in responding to this deception… which is a kind of XYZ problem.
Unable to set flameshot shortcut to PrScr after 6.3
It turns out to be a kind of XYZ problem, do you understand?
This would, indeed, be an issue - as I actually have flameshot installed and I have many shortcuts set up… here you can see that a simple press of PrScrn is set up to execute ‘flameshot launcher’ - which works with spectacle installed… as does ‘flameshot gui’ or ‘flameshot full’.
So I would suspect that something is fundamentally specific to you if you cannot set these shortcuts to your PrScr button.
BTW I am using Manjaro (Testing) - so I am not expecting to see 6.3 for a while yet. Perhaps someone else could confirm that they can verify this issue of not being able to set PrScr for any other action whilst Spectacle is installed.
Indeed, I can set PrScr to do pretty much anything I like - completely unrelated to Printing the Screen.
1 Like
This is not a problem KDE can solve. Take it up with your distro.
Please remember to be courteous and respectful. Avoid sarcasm and snippiness.
Read the CoC if in doubt on how to respond:
Repeat offenders will be banned
Thread locked.
KDE moved spectacle from Gear to Plasma as it considers it belonging to the DE “experience”, and Arch just followed that for the “install everything Plasma without much thinking about it” plasma-meta package.
Which leads to that an Arch user who likes everything clean and lean does not install plasma-meta to begin with.
There is no way you can not remove a package if you have read the manual pacman - ArchWiki
Actually, this is not the problem - this is a miscommunication. Op has already stated that the ONLY reason they ‘need to remove spectacle’ is that spectacle is interfering and preventing OP from re-assigning the shortcut for PrScr.
Therefore, OP has somehow deduced that the proper solution is to remove spectacle.
My experience is that PrScr can be assigned to anything I choose, and spectacle has no forced binding and that removing spectacle is - at best - only going to mask this problem.
I would suggest that OP first verify that this is a problem by creating a new user account and testing the theory on a vanilla desktop.
Following that, OP will find out which part of the setup is causing this issue.
2 Likes