skillbert / alt1-electron

Experimantal electron implementation of Alt1 Toolkit
GNU General Public License v3.0
57 stars 16 forks source link

Unable to get working on Arch #22

Open sdooweloc opened 1 year ago

sdooweloc commented 1 year ago

Found this and was super excited for it. However, found that anything requiring screen capture does not work for me. Also running npm run watch seems to never finish.

I have included logs and system info below.

OS: Arch Linux x86_64 Host: B650 AORUS ELITE AX Kernel: 6.2.9-zen1-1-zen Uptime: 10 days, 9 hours, 29 mins Packages: 1553 (pacman) Shell: zsh 5.9 Resolution: 3440x1440, 2560x1440 DE: Plasma 5.27.4 WM: KWin WM Theme: Arc-Dark Theme: [Plasma], Breeze [GTK2/3] Icons: Papirus-Dark [Plasma], Papirus-Dark [GTK2/3] Terminal: kitty CPU: AMD Ryzen 7 7700X (16) @ 4.500GHz GPU: AMD ATI 13:00.0 Raphael GPU: AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT Memory: 27478MiB / 31236MiB

npm run watch - hangs

> alt1lite@0.0.1 watch
> npm run build -- --watch

> alt1lite@0.0.1 build
> node -r ts-node/register ./node_modules/webpack/bin/webpack.js --watch

assets by status 4.91 KiB [cached] 1 asset
assets by path appframe/ 82.4 KiB 4 assets
assets by path tests/ 889 KiB
  asset tests/index.bundle.js 889 KiB [compared for emit] (name: tests/index)
  asset tests/index.html 39 bytes [compared for emit] [from: tests/index.html] (auxiliary name: tests/index)
assets by path settings/ 21 KiB
  asset settings/index.bundle.js 20.9 KiB [compared for emit] (name: settings/index)
  asset settings/index.html 129 bytes [compared for emit] [from: settings/index.html] (auxiliary name: settings/index)
assets by path tooltip/ 19.2 KiB
  asset tooltip/index.bundle.js 19.1 KiB [compared for emit] (name: tooltip/index)
  asset tooltip/index.html 133 bytes [compared for emit] [from: tooltip/index.html] (auxiliary name: tooltip/index)
assets by path overlayframe/ 11.8 KiB
  asset overlayframe/index.bundle.js 11.4 KiB [compared for emit] (name: overlayframe/index)
  asset overlayframe/index.html 337 bytes [compared for emit] [from: overlayframe/index.html] (auxiliary name: overlayframe/index)
asset alt1lite.bundle.js 524 KiB [compared for emit] (name: alt1lite)
runtime modules 6.56 KiB 34 modules
cacheable modules 944 KiB
  modules by path ./ 579 KiB 60 modules
  modules by path ../ 365 KiB 22 modules
modules by path external "electron/ 126 bytes
  external "electron/main" 42 bytes [built] [code generated]
  external "electron/common" 42 bytes [built] [code generated]
  external "electron/renderer" 42 bytes [built] [code generated]
modules by path external "@electron/ 84 bytes
  external "@electron/remote/main" 42 bytes [built] [code generated]
  external "@electron/remote" 42 bytes [built] [code generated]
+ 8 modules
webpack 5.72.0 compiled successfully in 1638 ms

npm run UI - tried using clue sovler but said no clue was found

❯ npm run ui                                                          

> alt1lite@0.0.1 ui
> electron --inspect=9228 ./dist/alt1lite.bundle.js

Debugger listening on ws://127.0.0.1:9228/86e89454-aa38-438d-b055-abea8409cbbd
For help, see: https://nodejs.org/en/docs/inspector
xdg-mime: application argument missing
Try 'xdg-mime --help' for more information.

(electron:1296387): Gtk-WARNING **: 18:03:45.805: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name

(electron:1296387): Gtk-WARNING **: 18:03:45.805: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
native: X record extension version: 1.13
new rs client tracked with handle: 98566152
[1296446:0417/180345.905077:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.

Screenshot_20230417_180421

maxice8 commented 1 year ago

Are you using the Wayland version of Kwin ? as far as I can tell (I didn't run it, just looked at the code), it uses X11 to grab the screen (https://github.com/skillbert/alt1-electron/blob/master/native/os_x11_linux.cc)

sdooweloc commented 1 year ago

Are you using the Wayland version of Kwin ? as far as I can tell (I didn't run it, just looked at the code), it uses X11 to grab the screen (https://github.com/skillbert/alt1-electron/blob/master/native/os_x11_linux.cc)

No I am using X11.

image

DeeeeLAN commented 1 year ago

npm run watch not finishing makes sense, it is usually used for watching for code changes while developing and recompiling when a change is detected.

DeeeeLAN commented 1 year ago

I don't have capture working either, also on Arch, using Qtile X11 for my WM. I tried changing the capture setting but it didn't seem to save, so I am not sure if it is working.