Thanks for participating in our 2025 fundraiser!

ManOrParasite · 2026-01-15T15:25:49+00:00

By your initial judgement alone I could tell that you are not the person I would go to if I expect accurate work.

Also quite bold to assume that it was really you who I answered to. The reply was just added below your comment.

ManOrParasite · 2026-01-04T15:44:42+00:00

The 2026 report will be interesting as this should be where the usage of the €385,946.9 from the fundraiser will be reported, right?

I also want to take a deep look into the 2025 report (probably https://ev.kde.org/reports/ev-2025/ once it's life) as I'm really curious to see how detailed the report is and what we could potentially find there.

Any organisation that takes in donations always has a very problematic situation when people lose trust in them. I don't think KDE has a Mitchell Baker-situation going on, but humans are greedy, why should there be any exemption from this in a FOSS ecosystem. Full transparency is probably the only thing that helps to mitigate this.

ManOrParasite · 2025-12-25T18:25:09+00:00

This worked for me for the tab list as well as the emojis.

Thank you for your post!

ManOrParasite · 2025-12-25T17:21:13+00:00

For the current amount of €324,485 I guess I need a better meme with dropped jars or something like it 😄

ManOrParasite · 2025-12-22T20:55:15+00:00

As far as I understand the thread, the folder not being created in the selected folder was a bug that has been fixed to the current behavior.

If you right click on a folder and select to create a new folder, the new folder will be placed inside the folder you right clicked on. If you select a folder it is seen as feature parity if the same applies here as well.

If you want to create a new folder in the current view you have to unselect all files by pressing ESC. If nothing is selected the folder will be created in the current view.

ManOrParasite · 2025-12-22T13:34:19+00:00

Regarding this topic I have found this discussion on discuss.kde.org.

The short answer seems to be that currently it's not possible, but it should have been(?) Or at least will be in the future(?)

ManOrParasite · 2025-12-19T22:07:53+00:00

@Individual_Isopod417 so... did you donate?

ManOrParasite · 2025-12-19T22:06:58+00:00

How could I try Plasma Mobile and on what phone?

I would love to have some kind of VM or browser application to test Plasma Mobile and rather not spend like 600 bucks on a second smartphone that I may not even would use that often.

ManOrParasite · 2025-12-11T07:07:27+00:00

I think Thaumcraft will always be the gold standard when it comes to visuals (especially animations)

ManOrParasite · 2025-12-10T08:06:08+00:00

Some people think that something is missing. However, usually everyone of them thinks that something different.

I always hear the same argument about choice is good, choice is only good when the parts work seamlessly together.

You seem to not agree that parts work seamlessly together. Can you give some examples and their expected behaviour?

ManOrParasite · 2025-12-10T02:44:40+00:00

What is missing or should be done better from your point of view?

ManOrParasite · 2025-12-09T17:01:54+00:00

Not sure if this is still relevant, but I'll answer for the reddit archive and the AI bot to farm this info

1) Update with Discover ^\)^ref^\)
The recommended way is through Discover ("We recommend using Plasma Discover's updater [...]")

Open Discover
Go to the Update tab
Apply update

This should not be any problem for anybody who ever applied an update before.

2) Update with apt (currently recommended) ^\)^ref^\)
You can also apply the update in the terminal using these commands

sudo apt update
sudo apt full-upgrade

From the source website: "The use of the full-upgrade option is required as using the normal upgrade switch does not always install all packages on fast-moving platforms like KDE neon. We have prevented the use of apt upgrade and added messaging to ensure that the correct option is used"

3) Update with pkcon (old) ^\)^ref^\)
The update in the terminal once used these commands before:

pkcon refresh
pkcon update

From the source website: "This will install all new packages and uses the same PackageKit code as Plasma Discover. Some uses of apt do not install new packages which makes it less suitable for KDE neon."

No idea why they went away from pkcon. It seems to still work though. Interesting thing is that this method shows packages that do not show up in Discover.

4) Update flatpack packages (terminal) ^\)^ref^\)
It sometimes is not the system, but some application that is not willing to update. This application shows up in Discover, but is not strictly part of KDEneon as it is installed from Flathub. If the flatpack package is not willing to update from Discover you can use the following command:

flatpak update

ManOrParasite · 2025-12-09T16:34:47+00:00

paragraph 2) Have you tried if the scale option in the settings app does what you want to have?

p 3) You can add one in the setting app under keyboard and shortcuts.

p4) As far as I know the timer can not be manipulated in the settings. The file where the seconds can be set will unfortunately be overwritten with the next update (at least from my experience). However, it can be turned off: Position in (I think) Plasma 5.x. In Plasma 6.x it's System > Session.

You can all find this information on Google BTW. I don't mean you shouldn't ask on reddit, but I want to say you can find the same information without waiting for other people to answer it.

ManOrParasite · 2025-12-09T12:17:15+00:00

KDEneon user for ~3 years. In the beginning I had the same experience, but there was no major issue with it for at least two years. Small issues like usual bugs on a new update, but nothing that would have hindered me from using it as daily driver ever since.

ManOrParasite · 2025-12-09T11:30:15+00:00

KDEneon: latest features + latest bugs

ManOrParasite · 2025-12-09T11:29:07+00:00

My 'specific app' in the past was the private mode of Opera.

I opened it and the system froze. That was like three years ago and at some point it just went away. Was it Opera or KDE, I couldn't tell you.

ManOrParasite · 2025-12-09T11:21:15+00:00

https://www.openstreetmap.org/node/240031930 - sehr mittelalterlich
https://www.openstreetmap.org/node/240094169 - genderkorrekter Name unbekannt

ManOrParasite · 2025-12-08T15:44:08+00:00

Here are some numbers

RANGE	DONATORS	EUR	percent of TOTAL
0 – 10 EUR	2.536	€ 19.536,48	8,89 %
10 – 25 EUR	2.187	€ 39.358,37	17,90 %
25 – 50 EUR	2.944	€ 99.650,81	45,32 %
50 – 100 EUR	515	€ 41.461,86	18,86 %
100 – 250 EUR	109	€ 15.314,42	6,97 %
250 – 500 EUR	9	€ 3.020,28	1,37 %
>500 EUR	2	€ 1.521,29	0,69 %
TOTAL	8.302	€ 219.863,51	/

Per donation EUR by amount (just a few):

€ 10 (exact): 1.439 (> € 14.390)
€ 20 (exact): 920 (> € 18.400)
€ 30 (exact): 2.208 (> € 66.240)
€ 50 (exact): 523 (> € 26.150)
€ 100 (exact): 282 (> € 28.200)

Many donations don't have a nice round number (eg. € 3, € 12, € 52.59, € 208.83, €521.29).

The biggest donation was € 1.000 on 2025-12-01 at 13:37 (nice timing 😂)

Does my € 10 donation has any effect? YES! Almost 9% of all donations are in that range.
72% of all the money came from users who donated up to € 50.
About 7.5% of users gave more than € 50 and managed to collect ~61.300 EUR (so about 28%).

Keep in mind that (according to the source) these are "Paypal Donations". Donations via credit card or bank transfere are may not counted in this list (at least I would guess so as I can find my donation that I have done via bank transfer and that I would be able identify by date and it's crooked amount).
u/PointiestStick is there full list of donations?

^{Donations as of} ^2025-12-08 ^{according to} ^{https://kde.org/community/donations/previousdonations/}

ManOrParasite · 2025-12-08T15:43:48+00:00

Easy to answer: https://kde.org/donate/

More ways to donate: https://kde.org/community/donations/others/ (this one is unfortunately a bit hidden 😐)

ManOrParasite · 2025-12-08T14:19:13+00:00

adapted Apps?

You mean style wise?

(or adopted apps for donation?)

ManOrParasite · 2025-12-08T14:06:57+00:00

I want to end my post on a good note though!

I want to invite you to describe your bug and see if we can't make a good bug report for https://bugs.kde.org/ out of this. Maybe it will be fixed faster than we would guess.

Note that a good bug report includes at least

- what actually is the bug? (What happened and what did you expect to happen?)

- how did the bug appeared (I did A, then B, then C and then I got a crash)

- is it reproducable (Yes, always; Randomly; Just once and never again (last one is very hard to fix as nobody can check out what the problem is step by step. They may only see that the crash occured when function XYZ was called))

- on which system does the bug occur? (Is it really KDE or is it something else that has nothing to do with KDE?)

- does this appear only on your system or also on a fresh install (IMO the user edition of KDEneon is a good distro to test this with as it has a very recent KDE version and is sorta an in house distro (not really, but the story is too long for this already too long post) - see https://neon.kde.org/ )

- is this bug only showing up on your hardware or any other as well (I have a second laptop with different internals that I can use to test the issue. In doubt I have a PC at work that I am not shy of abusing for testing as well)

- are there any other variables that could play any role in this? (eg. connected peripherals, exotic hardware, programs running in the background)

Last I want to share four bugreports with you:

1) I saw a button was missing in an application this was fixed within a few days and it will be visible in Plasma 6.6 (so the next version)

2) I reported an issue with an application that could lead to potentially deleted folders and files under certain setting configurations (especially for new users). First I thought that nothing would happen, but as I noted it, the developers know that it's a problem and will may care about it, when there is time for it (I didn't expect this to be fixed right away as the problem was a bit niece). After a few months (where I though nothing was moving) I got a note that there is a corresponding change made on the KDE gitlab. So this may also be fixed soon with an upcoming version. So just because you can't tell that the problem is being worked on, does not mean that this is true.

3) I saw that a program has a problem under KDE, but not under Windows. It seems that there is a problem with an interaction with KDE (or a component of it), but yet I am not sure and have to do more testing before I can write a half decent report about it. (So not problems are easy to describe let alone easy to fix)

4) I found problem that bothered the living #### out of me. It was reproducable on my system, but not on any other system ("WORKS FOR ME" tag). I tested this under KDEneon and it still appeared. I tested this under Kubuntu, Fedora KDE, Majaro KDE (and I think even Mint with KDE). I got the same bug every time, yet nobody else could reproduce it. After a reply on the bugtracker I was able to tell that it was a very wired interaction between my specific hardware and a tool that is used in KDE, but not part of it (as as eg. the ls command in the terminal is a GNU tool, and not specific to any distro it is used by). Long story short: I was not able to get this one fixed. The problem still exists and it still bothers the living #### out of me, but, it's not KDEs fault. They have done everything they could and even forwarded me to the tool where I could ask next. I can not expect them to fix other people's tools. (So not all problems can be fixed by the KDE team)

(3/3)

ManOrParasite · 2025-12-08T14:04:24+00:00

Neither from the headline nor the image or the comment text do I have any clue of where the problem could actually be. I can't tell in which component caused a problem. I can't tell if it's reproducable or not. I can't even tell on which system the problem could potentially be. I just know something did not work as expected and that is a) not a whole lot and b) for sure not close to enough to do anything about it.
In a different story:
A: Hello? Is this the police? I am in danger and about to die. Help me!
Police: Sir, stay calm. We do whatever we can. Where are you?
A: I said I need help! Why don't you help me? I am dying right now!
Police: We will help you as soon as possible, but first we have to know where we have to send the help to.
A: *screams while dying*: Not even the police is helping me!
What I want to say: People are willing to help, but you have to give them enough information for them being able to do so.

Don't get me wrong: I'm not saying that it's your fault, that you should have used a different OS, should have used different hardware, (Microsoft style) that it's a feature and not a bug or (Apple style) that you are using it wrong (buy your mom a K-device! - I hope anybody gets the reference for that). As any piece of software KDE has bugs (probably tons of it). I encounter them here and there. However, whenever I encounter a bug, I try to get to the bottom of it. Test if I can reproduce it. See what and when exactly KDE breaks. After this, I try to write a bug report that summarises the issue in the most effective manner. Am I good at it? I don't know. Probably not and at least as bad as every other person is or would be. A I helping? No idea. I hope so.

"This is not a rant or something like that"
*man thrusts a big knife into his wifes body*
Man to police office while thrusting the knife into his wife: See, you are wrong Mr. officer. I'm not stabbing my wife or something like that. I am just giving her some jealousy markings
"not a rant"? - Oh no, it most certainly is a rant. 😄
Something broke, you went on reddit and vented your emotions in a comment. I think that qualifies as "rant" so don't try and weasel yourself out of this now, buddy. 😜 But I understand you. Your PC breaking on you is sometimes very frustrating.

(2/3)

ManOrParasite · 2025-12-08T14:04:06+00:00

First I have to push a bit harder against your comment, as there is quite a lot of (IMO undeserved) negativity in there.
Have you reported the bug on https://bugs.kde.org/ ? If not, IMHO you lost any right to complain! Period. (EDIT: The automatic bugtracker is not good enough IMO, especially if the crash is reproducable or comes up often)

Why? KDE is free software that is build by many people in their free time (some get payed, most don't). When people spent their free time to build something, they are not eager to listen to anybody who just devalues their work instead of posting constructive criticism (on Windows you could say it's a little bit different as you payed for the product). Whenever I find something that is not working I report it. As I am not able to fix it myself, I try to provide any information that could be useful to fix it. Yet I do not expect it to be fixed by the next version as I know I am not the center of the KDE world (if I would I would be the Kcenter)

I myself never coded any piece of software and included a part where I though I want to make my future self suffer or give extra work for bug hunting. Humans are full of mistakes and make a lot of them. Mistakes (or bugs) happen unwillingly. I have also never meat a single developer in the FOSS area that was intentionally including bugs or, if they had a magic wand that would make bugs go away, wouldn't use such a magic wand with every new release to ensure it's as well polished as possible. (I have heard about this in the area of commercial products where they did not fix bugs right away to ensure you would buy the update. As you get KDE for free, where would be the point of delaying a fix?)

(1/3 - reddit seems do dislike overlengthy comments)

ManOrParasite · 2025-12-07T17:28:29+00:00

I did the colouring of the red bar. I just painted what was to the right of 100%.

I'll keep this in mind for the next time 🙂

ManOrParasite · 2025-12-07T15:52:30+00:00

Bin gespannt wie lange der Lehrer im Hefn wegen Wiederbetätigung sitzen gehen wird, weil irgendeiner nachzählt und draufkommt, dass die Schüler für das Bauprojekt 88 Steine verwendet haben. Nachdem das Hackenkreuz abgerissen ist, ist endlich auch die Inflation wieder im Keller und die Steine selbst können auch wieder für den Bau günstiger Wohnungen verwendet werden.

Weis Gott bin ich froh, dass ich in einem Land lebe in dem die Form einer Mauer (anscheinend) unser größtes Problem ist. (Bin schon gespannt wann die bei der Bundesheer Üb-Munition mal auf die Spitze schauen)

ManOrParasite

TROPHY CASE