Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

2020-05-22 Thread Florian Bruhin
Hey,

Upstream here - no idea what's happening there I'm afraid. I'm guessing you'll
have similar issues with other Qt/QtWebEngine applications as well though, I
doubt this is qutebrowser-specific. Can you try with e.g. Falkon as well?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature


Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

2020-05-12 Thread Nicolas Schier
Hi Axel,

> > qutebrowser does not start on my arm64 machine (pinebook, a64) (but 
> > it does well, on my amd64 machine).
> 
> Interesting. I just tried it on Debian Sid armhf and it works there as
> well. Do you know if earlier versions of qutebrowser worked on your Pinebook?

I tried several version during the last months, but none of them had 
worked.

> I'll probably try to setup an arm64 Raspberry Pi to check if I can
> reproduce it. Then I might give some more guidance.

On my Rasperry Pi (w/ xpra as xserver) I get the same error message.

Thanks in advande and kind regards,
Nicolas


> Maybe Florian (upstream) has some suggestions and maybe arm64
> experiences, too.
> 
>   Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

-- 
epost: nico...@fjasle.eu   irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb  c82b 7d97 0932 55a0 ce7f
 -- frykten for herren er opphav til kunnskap --


signature.asc
Description: PGP signature


Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

2020-05-12 Thread Axel Beckert
Hi Nicolas,

thanks for the bug report!

Nicolas Schier wrote:
> qutebrowser does not start on my arm64 machine (pinebook, a64) (but it
> does well, on my amd64 machine).

Interesting. I just tried it on Debian Sid armhf and it works there as
well. Do you know if earlier versions of qutebrowser worked on your Pinebook?

I'll probably try to setup an arm64 Raspberry Pi to check if I can
reproduce it. Then I might give some more guidance.

Maybe Florian (upstream) has some suggestions and maybe arm64
experiences, too.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

2020-05-12 Thread Nicolas Schier
Package: qutebrowser
Version: 1.11.1.post1-1
Severity: normal

Dear Maintainer,

qutebrowser does not start on my arm64 machine (pinebook, a64) (but it
does well, on my amd64 machine).  Starting it (with `-l debug`) results
in these messages:

~ $ qutebrowser -l debug
DEBUGinit   earlyinit:init_log:275 Log initialized.
DEBUGinit   app:run:83 Initializing directories...
DEBUGinit   standarddir:init:336 Base directory: None
DEBUGmisc   standarddir:_writable_location:263 writable location for 
ConfigLocation: /home/nicolas/.config
DEBUGmisc   standarddir:_writable_location:263 writable location for 
AppLocalDataLocation: /home/nicolas/.local/share
DEBUGmisc   standarddir:_writable_location:263 writable location for 
CacheLocation: /home/nicolas/.cache
DEBUGmisc   standarddir:_writable_location:263 writable location for 
DownloadLocation: /home/nicolas/Downloads
DEBUGmisc   standarddir:_writable_location:263 writable location for 
RuntimeLocation: /run/user/1000
DEBUGinit   app:run:87 Initializing config...
DEBUGinit   app:run:90 Initializing application...
DEBUGinit   app:__init__:478 Qt arguments: ['/usr/bin/qutebrowser', 
'--reduced-referrer-granularity'], based on Namespace(backend=None, 
basedir=None, color=True, command=[], config_py=None, debug=False, 
debug_flags=[], enable_webengine_inspector=False, force_color=False, 
json_args=None, json_logging=False, logfilter=None, loglevel='debug', 
loglines=2000, no_err_windows=False, nowindow=False, override_restore=False, 
qt_arg=None, qt_flag=None, session=None, target=None, temp_basedir=False, 
temp_basedir_restarted=None, temp_settings=[], url=[], version=False)
WARNING  qt-qt.glx  Unknown module:none:0 qglx_findConfig: Failed to finding 
matching FBConfig for QSurfaceFormat(version 2.0, options 
QFlags(), depthBufferSize -1, redBufferSize 1, 
greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, 
samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, 
colorSpace QSurfaceFormat::DefaultColorSpace, profile  
QSurfaceFormat::NoProfile)
WARNING  qt-qt.glx  Unknown module:none:0 qglx_findConfig: Failed to finding 
matching FBConfig for QSurfaceFormat(version 2.0, options 
QFlags(), depthBufferSize -1, redBufferSize 1, 
greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, 
samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, 
colorSpace QSurfaceFormat::DefaultColorSpace, profile  
QSurfaceFormat::NoProfile)
CRITICAL qt Unknown module:none:0 Could not initialize GLX
Fatal Python error: Aborted

Current thread 0xb6997010 (most recent call first):
  File "/usr/lib/python3/dist-packages/qutebrowser/app.py", line 479 in __init__
  File "/usr/lib/python3/dist-packages/qutebrowser/app.py", line 92 in run
  File "/usr/lib/python3/dist-packages/qutebrowser/qutebrowser.py", line 201 in 
main
  File "/usr/bin/qutebrowser", line 11 in 
Avbrutt (SIGABRT)


As far as I know, Xorg xserver is using a simple framebuffer device.
Do I have to specify, what kind of framebuffer (?) I am using?  Do you
need anything else for further debugging?

Kind regards,
Nicolas


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.6.0-1-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE, TAINT_SOFTLOCKUP
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to nb_NO.UTF-8), LANGUAGE=nb:nn:se:dk:de:C (charmap=UTF-8) (ignored: LC_ALL 
set to nb_NO.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qutebrowser depends on:
ii  libqt5core5a 5.12.5+dfsg-10
ii  libqt5sql5-sqlite5.12.5+dfsg-10
ii  python3  3.8.2-3
ii  python3-attr 19.3.0-4
ii  python3-jinja2   2.11.1-1
ii  python3-pkg-resources46.1.3-1
ii  python3-pygments 2.3.1+dfsg-3
ii  python3-pypeg2   2.15.2-2
ii  python3-pyqt55.14.2+dfsg-1+b1
ii  python3-pyqt5.qtopengl   5.14.2+dfsg-1+b1
ii  python3-pyqt5.qtquick5.14.2+dfsg-1+b1
ii  python3-pyqt5.qtsql  5.14.2+dfsg-1+b1
ii  python3-ruamel.yaml  0.15.89-3+b2
ii  python3-sip  4.19.22+dfsg-1+b1
ii  python3-yaml 5.3.1-2
ii  qutebrowser-qtwebengine  1.11.1.post1-1
ii  qutebrowser-qtwebkit 1.11.1.post1-1

qutebrowser recommends no packages.

Versions of packages qutebrowser suggests:
pn  libjs-pdf 
ii  nodejs10.20.1~dfsg-1
pn  python3-colorlog  

-- no debconf information