does not run under Gnome 42 and wayland
dpriedel opened this issue · comments
I have built the latest fvim version from git using the AUR package.
When I then run fvim under Gnome 42/wayland, all I get is a blank window which does not respond to any keyboard or mouse input. I have to force the application to quit by 'control-C'
Fvim does run under Gnome 42/Xorg.
Is this expected?
Thanks
I did have it working under Arch/GNOME42/Wayland. Not sure what's going on here.
Is the blank window picking up colorscheme?
No. The window is completely empty and does not respond to any mouse
clicks or keyboard input.
But I can resize the window by dragging the borders or clicking in the zoom box. The close box does not do anything.
Here is trace output
fvim --trace-to-stdout
log: fvim started. time = 8/15/2022 4:00:05 PM
model: starting neovim instance...
model: opts = Embedded ("nvim", ["--embed"],
System.Text.UTF8Encoding+UTF8EncodingSealed)
neovim.process: Starting process. Program: nvim; Arguments: ["--embed"]
neovim.process: begin read loop
model: commencing early initialization...
editorvm #1: ctor
ui: GetTypeface: allocating new typeface Monospace:false:false
frame: configBackground: SolidBackground (1.0, #00000000)
ui: SetWindowBackgroundComposition: desired=None actual=Transparent
mainwindow: set position: 300, 300
main: mainwin bound adjusted to 300, 300, 800, 600
editor #1: viewmodel connected
editor #1: render tick 0
editor #1: MeasureOverride: 800, 600
editorvm #1: set measured size: 800, 600
ui: GetTypeface: allocating new typeface :false:false
mainwindow: first PositionChanged event: 37, 106 (delta=-263, -194)
…On 8/15/22 9:27 AM, Yatao Li wrote:
I did have it working under Arch/GNOME42/Wayland. Not sure what's
going on here.
Is the blank window picking up colorscheme?
—
Reply to this email directly, view it on GitHub
<#230 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUOHSQVWTKVA6YVXOWNLI3VZJASPANCNFSM5YKDOVLA>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
looks like early initialization is stuck.
does fvim -u NORC help?
No.
trace looks the same, behavior still the same
fvim -u NORC --trace-to-stdout
log: fvim started. time = 8/16/2022 9:37:12 AM
model: starting neovim instance...
model: opts = Embedded
("nvim", ["--embed"; "-u"; "NORC"],
System.Text.UTF8Encoding+UTF8EncodingSealed)
neovim.process: Starting process. Program: nvim; Arguments: ["--embed";
"-u"; "NORC"]
neovim.process: begin read loop
model: commencing early initialization...
editorvm #1: ctor
ui: GetTypeface: allocating new typeface Monospace:false:false
frame: configBackground: SolidBackground (1.0, #00000000)
ui: SetWindowBackgroundComposition: desired=None actual=Transparent
mainwindow: set position: 300, 300
main: mainwin bound adjusted to 300, 300, 800, 600
editor #1: viewmodel connected
editor #1: render tick 0
editor #1: MeasureOverride: 800, 600
editorvm #1: set measured size: 800, 600
ui: GetTypeface: allocating new typeface :false:false
mainwindow: first PositionChanged event: 960, 69 (delta=660, -231)
…On 8/16/22 1:58 AM, Yatao Li wrote:
looks like early initialization is stuck.
does |fvim -u NORC| help?
—
Reply to this email directly, view it on GitHub
<#230 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUOHSU5KR2CN6KMGJPZQUTVZMUZXANCNFSM5YKDOVLA>.
You are receiving this because you authored the thread.Message ID:
***@***.***>