public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: Wyser Klaus <Klaus.Wyser@smhi.se>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: SV: octave doesn't work any longer with qt graphics toolkit
Date: Tue, 24 Jan 2023 12:50:39 +0100	[thread overview]
Message-ID: <d0715ee0-2295-7db2-6aa6-621e999d8f9e@gmail.com> (raw)
In-Reply-To: <729a0c25decc409dbb04f13264a66b3b@smhi.se>

On 17.01.2023 12:29, Wyser Klaus wrote:
> Hej Marco---
> 
> Thanks for your reply. I tried to send the cygcheck output to the Cygwin mailing list last week, but the file was too big (2M) and the post was rejected. I therefore put the file on a temporary platform for file exchange:
> http://exporter.nsc.liu.se/2ce844aaa0014c9f9cf889f2b062fdc7/cygcheck.out
> from where you should be able to fetch it.
> 
> I tried to repeat exactly the example that you suggested, no success unfortunately. I attach the XWin logfile, maybe it helps you to spot anything.
> 
> Best wishes,
> Klaus
> 
> 

Hi Klaus,

my guess is that there is an issue with the drivers


[183955.593] (EE) AIGLX: No native OpenGL in modes with a root window
[183955.843] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so 
failed (No such process)
[183955.843] (EE) AIGLX error: unable to load driver swrast
[183955.843] (EE) GLX: could not load software renderer
[183955.843] (II) GLX: no usable GL providers found for screen 0

on my system I see

glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
(II) AIGLX: Testing pixelFormatIndex 1
GL_VERSION:     4.5.0 - Build 22.20.16.4815
GL_VENDOR:      Intel
GL_RENDERER:    Intel(R) UHD Graphics 620
(II) GLX: enabled GLX_SGI_make_current_read



  reply	other threads:[~2023-01-24 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 14:32 Wyser Klaus
2023-01-12 15:19 ` marco atzeri
2023-01-17 11:29   ` SV: " Wyser Klaus
2023-01-24 11:50     ` Marco Atzeri [this message]
2023-01-24 14:43       ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0715ee0-2295-7db2-6aa6-621e999d8f9e@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=Klaus.Wyser@smhi.se \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).