The 15-Minute Bug Initiative (KDE)

What no one dared to say about KDE:

 
Wow that's depressing! How many bugs are triggered in the 16th minute? I haven't used KDE in more than a decade, and that piece makes me thing I can wait another before trying it again.
 
It's just someone trying to improve KDE quality, and that's a good thing. But I think it gives a wrong impression. KDE already is a great desktop, and I have the impression it works better on FreeBSD than some other desktops (well, especially GNOME....)

Although I don't use it myself much (I prefer my "desktop" around fvwm3 with a few extra tools), I installed it on my mother's notebook after the bundled OEM Win7 went EOL. So, she's now using FreeBSD; easier for me to fix little things remote than with Windows, and she never had a problem related to KDE so far...
 
It's just someone trying to improve KDE quality, and that's a good thing. But I think it gives a wrong impression. KDE already is a great desktop, and I have the impression it works better on FreeBSD than some other desktops (well, especially GNOME....)
Sure, it's not as buggy as it was years ago, but three things I can think of didn't get much attention:
  • I am always greeted with a bug in kwin on the first start of a new installation which leaves a bad taste in my mouth.
  • The lock screen stays dead until you decide to enter the password blindly, getting into a loop of input and error.
  • The cycle of entering the root password and applying for each change in the preferences is absurd. A global session is required that lasts until you close the preferences window.
 
Talking about improving KDE quality.
Wow, now that's a classic example for FUD. So Qt adds a feature to their UI framework they sell, targeting mobile as well, a feature lots of "shareware" and "freemium" software publishers want, and this article starts talking about KDE, just because it uses the Qt opensource edition. 🤦‍♂️ Well, at best a stupid clickbait.

I am always greeted with a bug in kwin on the first start of a new installation which leaves a bad taste in my mouth.
I remember having seen kwin crash, but not really often, more like less than 5 times in several years...
The lock screen stays dead until you decide to enter the password blindly, getting into a loop of input and error.
Never seen that myself. Would probably make sense to further investigate the conditions for triggering it.
The cycle of entering the root password and applying for each change in the preferences is absurd. A global session is required that lasts until you close the preferences window.
Not a bug but a feature request. Would probably be nice, but keep in mind these are separate tools just integrated in a common UI, and only the one tool you currently need runs with elevated privileges. So, what you suggest could be dangerous, there's some potential for security bugs...
 
It's a compositing issue. In the preferences it shows a warning that OpenGL has caused a KWin crash in the past and is probably due to a driver error. I always got this on my Linux boxes with integrated Nvidia/Intel card. It's not nice even though it's not a real Plasma issue.

On the lock screen, it's displayed but not the username and password input field, which appears a long time later. Mouse, Esc key or spacebar doesn't fully wake up the screen, you must enter the password blindly, press Enter and cross your fingers, or press Enter and wait for a while after the password field with the wrong password message directly.
 
Wow, now that's a classic example for FUD. So Qt adds a feature to their UI framework they sell, targeting mobile as well, a feature lots of "shareware" and "freemium" software publishers want, and this article starts talking about KDE, just because it uses the Qt opensource edition. 🤦‍♂️ Well, at best a stupid clickbait.
There's no indication that this new feature is restricted to the paid version of Qt. Some corporate flack contributed the following in the comments section:
Just to make things clear, we are offering the opportunity to startups, open source users and commercial Qt users to create new business models monetizing from running ads inside their Qt runtime. We are giving the opportunity to new ideas to come to life, to startupper or OSS developers to generate revenues in their early stage, to validate MVPs or absorb some investment costs.
(Emphasis mine)

Looks like ads are coming soon to Qt apps in KDE and any other DE.
 
Qt allowing ads doesn't mean its users will jump on the possibility. I don't think many free software projects will try that, it would be a sure way to annoy and loose numerous users.
 
Qt allowing ads doesn't mean its users will jump on the possibility. I don't think many free software projects will try that, it would be a sure way to annoy and loose numerous users.
Well, we're gonna find out one way or another. I'm pessimistic. There are too many idiot product managers out there intent on "disrupting" things.
 
I know I for sure will either downgrade to an older version and/or stop using the software with ads in it (hence why I refuse to touch ubuntu). Otherwise, I've done enough compiling that I am perfectly comfortable compiling my own software, so I also have the option of ripping the ads out.
 
I feel you, and will likely do the same. However, my experiences with Systemd showed the limits of such resistance. At some point it becomes too much for one person or even a small team to do. Look at the GTK 2->3 fiasco, the MATE desktop, etc. Eventually the large and well-funded organizations will win.

The only way this dies is if there's a large and sudden resistance to these developments. Again, I'm pessimistic. People are getting increasingly accustomed to being bombarded with ads in all aspects of their online lives. I expect young people will come to regard ads as a normal part of using computers.
 
I thought the original topic of this thread was the 15-minute bug initiative, not the blowback over QT's decision to sneak ads into OSS software.
--
For the 15-minute bug initiative: I think that's a big-time misnomer. You kind of have to be awfully familiar with the project to realize what's a quick fix, and what's not. Applying a verified patch can very well be a 15-minute chore even for a competent programmer. Coming up with a 10-liner that solves a pain point without messing things up elsewhere - think that's easy? A quick-and-dirty fix may turn out to be worse than the problem it solves.
--
QT's decision to sneak ads into OSS software: NO FRIGGING WAY. I really hope KDE stands its ground and keeps its branched copy of QT free of that. 👿
 
So, the FUD obviously works, wording like "sneaking in" proves it...

The title of this article doesn't even talk about Qt, but about KDE, which is completely unrelated here. If that's not a clickbaiting fallacy, I don't know ... don't fall for such stupid nonsense.

As for Qt, they don't "sneak in" anything, they offer a new feature. Again, Qt is sold as a product, for example to publishers of (Windows) shareware, or mobile apps. These customers will probably like that feature, so it makes sense.

Trying to force ads on someone using some open-source software running locally is one of the weirder ideas. First thing that would happen is patches removing it again (and they will be quite simple). So, it makes no sense at all.
 
First thing that would happen is patches removing it again (and they will be quite simple).
If that's the case, I would think that such a patch should definitely qualify for the 15-minute bug initiative. I want my KDE install to be clean, and ad-free.
 
So, the FUD obviously works, wording like "sneaking in" proves it...

The title of this article doesn't even talk about Qt, but about KDE, which is completely unrelated here. If that's not a clickbaiting fallacy, I don't know ... don't fall for such stupid nonsense.
The article I linked is specifically about Qt, and published on the qt.io domain. It contains statements from someone who works at Qt that explicitly state this new feature is aimed at open source developers and projects. What you or I think doesn't matter. The intentions of the developers of Qt are clear and explicitly stated.

There's no FUD or clickbait there.
 
Jose, first of all, I wasn't talking about your link. Is it that hard to understand the context of a thread? I was talking about a silly nonsense article titled "Ads may be coming to KDE [...]".

Second, the one you cite just adds "OSS developers" as one target to a list. It's definitely not the best one, and your emphasis is very misleading.

And finally, your last link just confirms what I said. People will patch it away if someone tries this with open-source software, so it's pretty pointless.
 
Wow that's depressing! How many bugs are triggered in the 16th minute? I haven't used KDE in more than a decade, and that piece makes me thing I can wait another before trying it again.
What DE do yo use? I used Gnome 3 for quite a while but their dialogs started being so unusable that I was forced to switch to KDE and keep my sanity. The latter is not far behind Gnome though, for example - where is the button "Go 1 directory higher" when browsing or selecting something in the dialog? Where can I paste my file system path in the dialog? In general those GUIs are simply impossible to use productively with keyboard only. The scrollbars are tiny and you are lucky if you could succeed dragging the damn things.

I have not been turned off by the bugs in KDE to be honest, but certain parts of its UI design need serious changes.

These products used to be nice and slick, then something changed and they turned our mighty workstations into smartphones with large screens. I hate it.
I wish I had time to reprogram the dialogs once and for all but I am simply too preocupied writing my own junk. :)
 
Jose, first of all, I wasn't talking about your link. Is it that hard to understand the context of a thread? I was talking about a silly nonsense article titled "Ads may be coming to KDE [...]".
Does KDE not use Qt apps?
Second, the one you cite just adds "OSS developers" as one target to a list. It's definitely not the best one, and your emphasis is very misleading.
I see no evidence that Qt expects more or less use from the OSS community. They are targeted just as much as commercial developers.
And finally, your last link just confirms what I said. People will patch it away if someone tries this with open-source software, so it's pretty pointless.
Yeah? How many forks of Audacious are there? Do any of them have as many users as Audacious? How about a year from now?

I expect Audacious will follow the same path Plex and Kodi (XBMC) followed after they split.

What DE do yo use?
I don't. Openbox + terminal is all I need and want. I forced Xfce on my family when I forced Linux on them. It was just ok, and I stopped that a decade ago.
 
Does KDE not use Qt apps?
How is that relevant? Does KDE have to use every feature Qt has to offer?
I see no evidence that Qt expects more or less use from the OSS community. They are targeted just as much as commercial developers.
This has nothing to do with the target audience of this specific new feature. Sure, it could be used on opensource software. But it's much more likely (and, useful) in shareware and similar stuff.
 
How is that relevant? Does KDE have to use every feature Qt has to offer?
I don't think that it will be out of question for ads to appear anyway, even if the API for the monetization is not explicitly used. It's a common practice to bake an annoying feature in so hard that it's next to impossible to remove. Does anyone remember Carrier IQ debacle from a few years ago? That one 'feature' was impossible to remove or disable without completely messing up the phone. Definitely not a 15-minute chore to just patch up the phone. I don't want QT to go down the same road. 😩
--
Carrier IQ was intended for something different, but it shouldn't be that difficult to imagine how advertising networks took advantage of it. Tying it all back to the topic of this thread: Including a "Monetization API" is a move by QT that I really don't like - and I imagine it won't be a simple 15-minute fix to undo the damage.
--
If somebody actually sees a 15-minute fix, I think they should have the opportunity to do it, or publish a solution.
 
Back
Top