Nixpkgs: next-browser : UI is blank

[mmequignon]

Describe the bug
Pages seems to be loaded (I can see queries and traffic), but nothing appears

To Reproduce
Steps to reproduce the behavior:

1. nix-env -iA nixpkgs.next
2. next https://github.com

Expected behavior
I should see something here

Screenshots

Metadata

• system: "x86_64-linux"
• host os: Linux 5.5.4, NixOS, 20.09pre213994.e2b4abe3c8f (Nightingale)
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.3.3
• channels(root): "home-manager, nixos-20.09pre213994.e2b4abe3c8f"
• channels(matthieu): "home-manager, nixos-20.03pre204199.3140fa89c51"
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

[worldofpeace]

I believe this is a bug with visiting certain https websites.

[worldofpeace]

Can you try to get logs by running it from a terminal? Or figuring out where logs are stored?

[mmequignon]

Sure :

Next version 1.4.0
Loading configuration from #P"/home/matthieu/.config/next/init.lisp"...
 <WARN> [16:29:20] next utility.lisp (setf get-default) -
  The (setf (get-default ...)) and (add-to-default-list ...) forms are deprecated.
 <INFO> [16:29:20] next remote.lisp (initialize-instance :after remote-interface) -
  D-Bus addresses: (#<Unix socket address: @"/tmp/dbus-Oy8VzgpqSN">)
 <INFO> [16:29:20] next remote.lisp (initialize-instance :after remote-interface) -
  Bus connection name: :1.824
 <INFO> [16:29:20] next port.lisp (run-program port) -
  Current directory: /home/matthieu/
 <INFO> [16:29:20] next port.lisp (run-program port) -
  Platform port path: /nix/store/wwd29hwja4p8qhgvbbdbzhicd3xc6rps-next-gtk-webkit-1.4.0/bin/next-gtk-webkit
 <INFO> [16:29:20] next port.lisp (run-program port) -
  Platform port arguments: NIL
 <INFO> [16:29:20] next port.lisp (run-program port) -
  Platform port log file: /home/matthieu/.local/share/next/next-gtk-webkit.log
 <WARN> [16:29:20] next remote.lisp (current-buffer) -
  No active window, picking last active buffer.
 <INFO> [16:29:20] next session.lisp (restore-sexp-session form-fun-4) -
  Restoring (https://github.com/  The world’s leading software development platform · GitHub
             https://linuxfr.org/  Accueil - LinuxFr.org
             https://www.google.com/  )
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading global history of 7 URLs."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://github.com/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://linuxfr.org/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://www.google.com/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://linuxfr.org/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://github.com/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://www.google.com/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://github.com/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://linuxfr.org/."
 <INFO> [16:29:21] next minibuffer.lisp (echo form-fun-6) -
  "Loading: https://www.google.com/."
 <INFO> [16:29:22] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://linuxfr.org/."
 <INFO> [16:29:22] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://github.com/."
 <INFO> [16:29:25] next minibuffer.lisp (echo form-fun-6) -
  "Finished loading: https://www.google.com/."

[mmequignon]

Here's the config file :

; $HOME/.config/next/init.lisp
(in-package :next)
(add-to-default-list 'vi-normal-mode 'buffer 'default-modes)

[mmequignon]

bump

[bqv]

Tracked upstream: https://github.com/atlas-engineer/next/issues/422

[bqv]

A reliable fix seems to be to set WEBKIT_DISABLE_COMPOSITING_MODE=1 in your environment

[mmequignon]

yep, it works with that env variable

[stale[bot]]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.