Summary: | gui-wm/sway-1.9-r1: unable to run on fresh install (cannot detect wlroots) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Den <ya.dmikha> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | bobstayshaky, speedjack95, ya.dmikha |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Den
2024-05-27 17:10:06 UTC
I don't think the subproject thing is related. That's just because it's not building a bundled copy. Please share the full output from when you try to run sway. here it is den@gentoo ~ $ dbus-run-session sway nvc0_screen_create:1001 - Base screen init failed: -19 libEGL warning: egl: failed to create dri2 screen 00:00:00.119 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to create screen" nvc0_screen_create:1001 - Base screen init failed: -19 libEGL warning: egl: failed to create dri2 screen 00:00:00.121 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to create screen" nvc0_screen_create:1001 - Base screen init failed: -19 libEGL warning: egl: failed to create dri2 screen 00:00:00.124 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to create screen" 00:00:00.124 [ERROR] [wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "eglInitialize" 00:00:00.124 [ERROR] [wlr] [render/egl.c:269] Failed to initialize EGL 00:00:00.124 [ERROR] [wlr] [render/egl.c:572] Failed to initialize EGL context 00:00:00.124 [ERROR] [wlr] [render/gles2/renderer.c:804] Could not initialize EGL 00:00:00.124 [ERROR] [wlr] [render/wlr_renderer.c:423] Could not initialize renderer 00:00:00.124 [ERROR] [sway/server.c:143] Failed to create renderer Hello, I have some update, I've just complete the fresh install of gentoo with sway, but on the other host and it succeed. The major difference between hosts is GPU, the failed node has nvidia (nouveau), on the second there is intel gpu. The irony is that on the failing host the fresh install of gentoo linux with sway has been successful without any issue just around a month ago... can't really understand what wrong with newest ebuilds... (In reply to Den from comment #3) > Hello, > I have some update, I've just complete the fresh install of gentoo with > sway, but on the other host and it succeed. > The major difference between hosts is GPU, the failed node has nvidia > (nouveau), on the second there is intel gpu. The irony is that on the > failing host the fresh install of gentoo linux with sway has been successful > without any issue just around a month ago... can't really understand what > wrong with newest ebuilds... https://geometrylite.io For dev-qt/designer, dev-qt/pixeltool, dev-qt/qdoc (where the fix did seem a little differently), dev-qt/qtdiag, dev-qt/qtpaths, and dev-qt/qtplugininfo, they were necessary. Since they appear to function without the prior hack, I suppose it would be feasible to use the same technique for the remaining packages that are derived from Qttools, but this was not investigated. |