• 33 Posts
  • 529 Comments
Joined 1 year ago
cake
Cake day: February 8th, 2025

help-circle












  • Well that’s interesting,

    I ran journalctl -xe expecting not to get much of an output however, my log is full of:

    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
    Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
    Mar 24 17:00:00 debian systemd[2614]: Started drkonqi-sentry-postman.service - Submitting pending crash events.
    ░░ Subject: A start job for unit UNIT has finished successfully
    ░░ Defined-By: systemd
    ░░ Support: https://www.debian.org/support
    ░░ 
    ░░ A start job for unit UNIT has finished successfully.
    ░░ 
    ░░ The job identifier is 4486.
    Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
    Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
    Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
    Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
    Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
    Mar 24 17:04:12 debian plasmashell[2938]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact.applet", fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact>
    Mar 24 17:04:13 debian kmenuedit[3266]: QThreadStorage: Thread 0x55c784c1f8d0 exited after QThreadStorage 8 destroyed
    Mar 24 17:04:13 debian systemd[2614]: app-org.kde.kmenuedit@c3c9752c88b040738079b63d23e609ee.service: Consumed 3.486s CPU time, 34.4M memory peak.
    

    Appears to be related to my wallpaper, perhaps the KDE Wallpaper Engine plugin i use borked, however i never did mention in the main post but i did backup and reset my desktop environment following Debians documentation and that didn’t resolve the hanging issue either so i am hesitant to say the desktop itself is borked, seems more like a dependency that’s failing to talk with plasma.

    Edit: After doing some digging it appears others have encountered the same kwin error message along with comments of freezing and crashing. Appears to be a driver issue and is patched in 580.xx versions which Debian 13 does not ship on its stable branch.


  • systemd-analyze Can tell you about how long thing took to start, and the -blame flag can help pinpoint hangs and so on.

    I ran this command the output is as such:

    Startup finished in 7.208s (firmware) + 2.336s (loader) + 3.601s (kernel) + 15.279s (userspace) = 28.426s 
    graphical.target reached after 15.279s in userspace.
    

    Which is weird, i timed how long it took from rebooting to landing at the desktop and i got between 5-6 minutes, 30 seconds to reboot and land at SDDM but another 4.5-5 minutes actually loading the desktop itself.





  • source

    I’m repeating it again: Holy smokes, what a ride. Fluxer is taking off much earlier than I’d expected.

    I know it’s hard to resist, but please wait a little longer before you dive deep into the current codebase or try to set up self-hosting. I’m aware the current stack isn’t very lightweight. I’m working on making self-hosting as straightforward as possible and the development environment likewise.

    Self-hosted deployments won’t include any traces of Plutonium, and nothing is paywalled. You can still configure your own tiers and limits in the admin panel.

    Thanks for bearing with me. Development on Fluxer is about to get much easier, and the project will be made sustainable through community contributions and bounties for development work. Stay tuned – there’s not much left now.

    I thought I could take it a bit easier while shipping this stabilising update, but Discord’s announcement in Februrary has changed things.

    There’s just been a lot of work involved in keeping the production deployment up and running, handling trust & safety concerns, answering support emails, handling billing issues, and working on the refactor at the same time. I’m really excited to open up development and make it easier for others to contribute, and I can’t wait to see what the community builds on Fluxer!

    As soon as the refactor is ready (not much longer now!), I’ll enable PRs and interact more actively and push updates to this repository more frequently. The remaining parts of the refactor are currently being worked on and being tested live in production that has over 125,000 users (and we’re only two full-time employees for now). After that, all work will happen openly in public.

    The team is also growing, though we remain small and can’t offer very competitive salaries just yet – but if you want to work part-time or contract on projects, or you think you’re a great fit for the roles we’re hiring for (though not as actively across all roles at this time, but we’ll keep you on file for when we are), check out the careers page :D







  • People don’t like being proven wrong, and often try to dismiss it with some variation of “Im not gonna sit here and be told the whatfer by some random idiot”

    Sounds like you’re describing yourself here.

    • Refused to accept documentation from a valid source.

    • Instead of having a discussion, you proceed with a pointless “Sure, buddy” at an attempt to deflect from the topic.

    So when it came to registering on Lemmy, that popped up in my head and bobs your uncle.

    Real nice honeypot too, every time someones wrong and backs themselves into a corner instead of admitting they are wrong, they inevitably give some variation of “living up to your user name, huh”, which just continues to prove that the actual idiot is the one lashing out like that.

    You chose to make the two comments above, I simply humoured your ignorance and lack of understanding of the subject.