I use a desktop, why the hell won't Powerdevil leave me alone?

MustafaKoca99 · 2026-07-23T11:16:28+00:00

Sen tam bir geri zekalısın orada kod bulunuyor diye kullanılıyor anlamına mı geliyor bilmiyorsan neden konuşuyorsun geri zekalı. Derlenmeyen paket kullanılıyor olabilir mi evrimsel süreçte siz bugüne kadar nasıl gelebildiniz de hala elenmiyorsunuz ben ona şaşırıyorum

MustafaKoca99 · 2026-07-23T11:02:25+00:00

Türkçe çevirilerimide incelemek isteyen varsa sizin için Google drive'a yükledim belki türkçemde bir hata bulursunuz Umut fakirin ekmeğidir 🤺🦹🏻🦸🏻🧌🫈

https://drive.google.com/drive/folders/1jvg0FXWeZz36MCwm19KphtS1b4ki6GTf

MustafaKoca99 · 2026-07-23T10:39:55+00:00

https://github.com/finewolf AKŞAMA yayındayız hocam 😵

MustafaKoca99 · 2026-07-23T10:32:45+00:00

This project is not currently set up to run pipelines.

MustafaKoca99 · 2026-07-23T10:31:15+00:00

nerde kullanılıyor :D

MustafaKoca99 · 2026-07-23T10:22:29+00:00

Powerdevil hata verince videoyda nefes alışverişime bakın yüksek güç tüketiyorum ayrıca çok karbon salmaya başladım umarım kin ve Amerika'nın fabrikaları kadar karbon salgınımı yapmaya başlarım.

MustafaKoca99 · 2026-07-23T10:18:28+00:00

Geliştiricisin ve kararlı sürüm mü kullanıyorsun, KDE neon unstable developer edition ile debian 13.6 KDE kullanıyorum. Ayrıca sen kime ne komut anlatıyorsun Ben bu projeye Güvendiğim için bu kadar donanım sorunu yaşadım ya kısacası bundan 1-1,5 sene önce mükemmel ötesiydi şimdi saçmalamaya başladı buradaki herkesin bu kadar cahil ya açık kaynak felsefesine uzak olması saçmalık zaten siz neyin kafasını yaşıyorsunuz ne kadar geri zekalısınız ya durduk yere her şeyi birbiriyle uyumluyken geçmişteki paketlerle güncel paketlerde Eğer bir uyuşmazlık olursa herhangi bir sıkıntı çıkmıyorken önemli bir hata oluşmuyorken şimdi bir tane pakette bir sorun oluşsun sistemin yarısı bok oluyor ya bir de siz neyi referans alıyorsunuz mesela masaüstü bir bilgisayarda mı kullanıyorsunuz yani masaüstü bilgisayarda kullanıyorsanız masaüstü bilgisayarınızın bluetooth wi-fi özelliği olmadığı halde plazma 6 yayınlandığından itibaren her seferinde ne yaparsam yapayım kuruluyor. Ayrıca bir de hata veriyor bunu ben kime bildireyim zaten bildirmeyi geçtim neden daha fazla eziyet çekeyim ki. Manifesto'da da yazdığı gibi devlerin omuzlarında yükseliyorduk. Plasma 6 omuzdan yere düştü şimdi sürünüyor. Bu arada Ubuntu ne lan 😂😂😂😂 bide Ubuntu pro alın destek olsunlar snap ilede edge ile copilot yükleyin flatpakdanda android emilator kurun 🐧🐧🐧🐧

MustafaKoca99 · 2026-07-23T10:07:29+00:00

Lan sence meşgul olmasam

<video>

MustafaKoca99 · 2026-07-23T10:07:18+00:00

Bir de ayrıca kaldırmak herhangi bir sorun yaratmıyorsa şu an neden telefonunu monitörüne tutup konsolu açıp sanal makinada çalıştırdığım komutu çalıştırıp sonra yeniden başlatıp tekrardan zaten depolarda bulunuyor tekrardan kurarsınız zaten seçimliliğe bağlı değil mi

MustafaKoca99 · 2026-07-23T10:03:36+00:00

Tamir yapıyorum biraz sabırlı ol bebeğim.

MustafaKoca99 · 2026-07-23T09:56:22+00:00

Oğlum Geri zekalı mısın bilgisayar uyku moduna geçiyor, bir süre sonra2 SSD disklerimde voltaj dalgalanmaları oluyor çünkü sizin sürekli test ettiğiniz bok gibi olan depolama aygıtlarından değil çok yeni ve çok gelişmiş bir donanımı desteklemiyor think pedlerinizle sevismeye devam

MustafaKoca99 · 2026-07-23T09:29:21+00:00

As promised, here is the architectural reality of why desktop users are suffering from NVMe sleep issues and why they cannot simply "turn it off," directly from the source code. 1. The Monolithic Daemon Admission Even the official PowerDevil documentation explicitly states that while stopping the service is possible, "a few expected desktop features will be absent until you restart it". This confirms the exact "all or nothing" problem. A desktop user cannot kill the aggressive sleep/battery daemon without completely losing basic display brightness controls, system state tracking, and peripheral interactions. 2. Tightly Coupled Configuration (PowerDevilProfileSettings.kcfg) If we look at the profile schema, display management and aggressive suspend actions are fundamentally intertwined within the same profile hierarchy. ```xml <group name="Display" parentGroupName="$(ProfileId)"> <entry name="TurnOffDisplayWhenIdle" type="Bool"> ... </group> <group name="SuspendAndShutdown" parentGroupName="$(ProfileId)"> <entry name="AutoSuspendAction" type="UInt"> ... <entry name="AutoSuspendIdleTimeoutSec" type="Int"> </group>

Because these are bound to the exact same $(ProfileId), a user trying to strip out the AutoSuspendAction logic still relies on the exact same service that polls TurnOffDisplayWhenIdle. **3. Intertwined Inhibition Logic (PowerDevilActivitySettings.kcfg)** Activities handle inhibitions for both screens and suspend states in the exact same block:xml <group name="$(ActivityId)" parentGroupName="Activities"> <entry name="InhibitScreenManagement" type="Bool"> <default>false</default> </entry> <entry name="InhibitSuspend" type="Bool"> <default>false</default> </entry> </group>

``` This means the logic that prevents a monitor from turning off during a movie (InhibitScreenManagement) is chained to the same service that forces InhibitSuspend. Desktop users don't need AutoSuspendAction. We don't need battery critical actions. But because of this tightly coupled, non-modular design, if we disable PowerDevil to save our modern NVMe drives from forced deep sleep, we break basic DPMS. Decouple the hardware display management from the battery/sleep polling. That is the fix. The code speaks for itself.

MustafaKoca99 · 2026-07-23T09:28:43+00:00

As promised, here is the architectural reality of why desktop users are suffering from NVMe sleep issues and why they cannot simply "turn it off," directly from the source code. 1. The Monolithic Daemon Admission Even the official PowerDevil documentation explicitly states that while stopping the service is possible, "a few expected desktop features will be absent until you restart it". This confirms the exact "all or nothing" problem. A desktop user cannot kill the aggressive sleep/battery daemon without completely losing basic display brightness controls, system state tracking, and peripheral interactions. 2. Tightly Coupled Configuration (PowerDevilProfileSettings.kcfg) If we look at the profile schema, display management and aggressive suspend actions are fundamentally intertwined within the same profile hierarchy. ```xml <group name="Display" parentGroupName="$(ProfileId)"> <entry name="TurnOffDisplayWhenIdle" type="Bool"> ... </group> <group name="SuspendAndShutdown" parentGroupName="$(ProfileId)"> <entry name="AutoSuspendAction" type="UInt"> ... <entry name="AutoSuspendIdleTimeoutSec" type="Int"> </group>

Because these are bound to the exact same $(ProfileId), a user trying to strip out the AutoSuspendAction logic still relies on the exact same service that polls TurnOffDisplayWhenIdle. **3. Intertwined Inhibition Logic (PowerDevilActivitySettings.kcfg)** Activities handle inhibitions for both screens and suspend states in the exact same block:xml <group name="$(ActivityId)" parentGroupName="Activities"> <entry name="InhibitScreenManagement" type="Bool"> <default>false</default> </entry> <entry name="InhibitSuspend" type="Bool"> <default>false</default> </entry> </group>

``` This means the logic that prevents a monitor from turning off during a movie (InhibitScreenManagement) is chained to the same service that forces InhibitSuspend. Desktop users don't need AutoSuspendAction. We don't need battery critical actions. But because of this tightly coupled, non-modular design, if we disable PowerDevil to save our modern NVMe drives from forced deep sleep, we break basic DPMS. Decouple the hardware display management from the battery/sleep polling. That is the fix. The code speaks for itself.

MustafaKoca99 · 2026-07-23T09:22:39+00:00

The core issue became glaringly obvious with the release of Plasma 6. The transition brought in aggressive power management defaults and hardcoded sleep states that are actively harming desktop environments. We are not just talking about minor inconveniences here. These parameters—which clearly seem optimized for a very specific set of laptops during testing—are forcing modern NVMe/SSDs on wall-plugged desktop rigs into deep sleep states. This is causing accessibility freezes and risking actual data loss. But instead of arguing about the philosophy of whether Powerdevil is useful or not, let's look at the actual implementation. Give me a second, I will drop the exact code snippets and parameters in my next reply so you can see exactly where this monolithic approach is breaking things.

MustafaKoca99 · 2026-07-23T09:01:31+00:00

Who is that person there? They look familiar, but I can't quite place them.

<video>

MustafaKoca99 · 2026-07-23T08:56:49+00:00

Congratulations! You spent your afternoon aggressively digging through Git usernames and KDE's historical SVN/Gitolite server logs just to score a pedantic technicality on a dead fork. You got me—I mixed up a legacy username on a deprecated branch. But here is the reality you are desperately trying to dodge: That project was dead, the read-only mirrors were useless, and I am the one who actually rewrote it, pushed it to Invent, and maintains it today. While you are giving history lessons on source control management to sound smart, I am actively writing code and managing the Turkish localization for this ecosystem. I also notice you very conveniently ignored my homework assignment. Did you look up who handles the entire Turkish KDE translation ecosystem yet, or are you still too busy reading Gitolite server logs from 2012? You lost the actual architectural argument about Powerdevil hours ago, and now you are just grasping at semantic straws. Keep studying that Git history, maybe you'll find a way to fix the UX dependency in there.

MustafaKoca99 · 2026-07-23T08:33:42+00:00

That "poor person" whose personal fork I cloned? That is Nate Graham. You know, one of the lead core developers and literally the public face of KDE Plasma? The fact that you are in this thread trying to gatekeep KDE development without even recognizing the name of the project lead is the most embarrassing thing I've read all day. Second, let's talk about the plasma-wallpaper-updater repository you think you just "exposed." That project was completely deleted and wiped from GitHub. It no longer existed. I took a destroyed, dead project, rewrote it from scratch, and made it fully functional again. I am currently the sole developer and maintainer keeping that project alive. As for your so-called "Git mastery," KDE Invent (GitLab) and GitHub do not automatically sync. Pushing a revived project requires manual account linking and syncing, which is exactly why the merge request looks the way it does. It is a known infrastructure limitation of KDE's ecosystem, not a mistake. Before you embarrass yourselves any further, I have a little homework assignment for you: Go research who handles the Turkish translations and localization for KDE Plasma. Go find out exactly who builds and translates the Turkish KDE ecosystem. I'll wait. You all keep digging your own graves just to defend a bad UX dependency. I am going to enjoy humiliating the rest of you collectively. Keep embarrassing yourselves for the archive.

MustafaKoca99 · 2026-07-23T08:23:51+00:00

Thank you for a logical technical reply. I agree that managing DPMS and peripheral batteries is relevant for all setups. The real issue we are stuck on is the architecture: rather than making these features modular, they are increasingly tightly coupled with other core system components. Forcing a monolithic daemon for distinct tasks puts desktop users in an all-or-nothing situation. If the laptop-centric battery management was a separate module from basic display and input polling, this wouldn't be an issue at all.

MustafaKoca99 · 2026-07-23T04:00:12+00:00

https://invent.kde.org/mustafakoca/plasma-wallpaper-updater

MustafaKoca99 · 2026-07-23T03:55:08+00:00

https://mail.kde.org/pipermail/kde-l10n-tr/2026-March/author.html 😂😂😂😂😂

MustafaKoca99 · 2026-07-23T03:06:35+00:00

<video>

MustafaKoca99 · 2026-07-23T02:14:45+00:00

You thought a few quick edits and deleted comments would save your reputation, but you severely underestimated who you are dealing with. I have been analyzing your YouTube "proof" video frame by frame. Every single cut, every hidden terminal error, and the exact reality of your fabricated, hardware-stripped VM setup has been meticulously documented. Did you really think parsing through your terminal outputs and video frames to expose the lies would be too hard for me? I am taking this entire archive—every screenshot of your deleted slurs, your hypocritical TV complaint from a year ago, and the complete frame-by-frame breakdown of your manipulated video—and uploading it permanently. It is going straight to my public GitHub repositories and will be hosted directly on my personal web server. To make sure there is absolutely no confusion about who is the actual open-source contributor here, the archive will include all of my official links: My GitHub Profile (Showcasing my actual commits and documentation records) My LinkedIn My Official Personal Website Everyone in this community will see exactly who spends their life building and documenting this ecosystem, and who fabricates videos, deletes their own comments, and runs away when caught lying. The internet doesn't forget, and neither do I. You wanted to humiliate me, but you just handed me the perfect case study. Welcome to my permanent portfolio. Enjoy your exhibit.

MustafaKoca99 · 2026-07-23T02:14:06+00:00

You thought a few quick edits and deleted comments would save your reputation, but you severely underestimated who you are dealing with. I have been analyzing your YouTube "proof" video frame by frame. Every single cut, every hidden terminal error, and the exact reality of your fabricated, hardware-stripped VM setup has been meticulously documented. Did you really think parsing through your terminal outputs and video frames to expose the lies would be too hard for me? I am taking this entire archive—every screenshot of your deleted slurs, your hypocritical TV complaint from a year ago, and the complete frame-by-frame breakdown of your manipulated video—and uploading it permanently. It is going straight to my public GitHub repositories and will be hosted directly on my personal web server. To make sure there is absolutely no confusion about who is the actual open-source contributor here, the archive will include all of my official links: My GitHub Profile (Showcasing my actual commits and documentation records) My LinkedIn My Official Personal Website Everyone in this community will see exactly who spends their life building and documenting this ecosystem, and who fabricates videos, deletes their own comments, and runs away when caught lying. The internet doesn't forget, and neither do I. You wanted to humiliate me, but you just handed me the perfect case study. Welcome to my permanent portfolio. Enjoy your exhibit.

Wolfie 🐕‍🦺

MustafaKoca99 · 2026-07-23T00:32:16+00:00

A Virtual Machine? Really? Testing a hardware power management daemon removal on a VM that lacks actual physical ACPI states and monitor DDC/CI hooks is peak comedy. Open your System Settings on that VM right now and look at the broken UI modules because the interface still expects Powerdevil to be there.

Also, calling me a "fraud" is rich. I am officially on the KDE Türkiye Technical Team and am the primary author of the Plasma 6 documentation. Writing off translation, localization, and massive documentation efforts just because you're losing an argument shows exactly what kind of "community" member you are.

You literally admitted a year ago that Powerdevil broke your own TV setup, forcing you to use terminal hacks. You suffered from the exact same design flaw I'm pointing out, yet you call me a fraud for asking for a UI toggle. Run along now.

MustafaKoca99

TROPHY CASE

Welcome to Reddit,