• 83 Posts
  • 538 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.