X2Go Bug report logs - #367
wine does not start within x2goclient: Application tried to create a window, but no driver could be loaded.

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.x2go.org
From: owner@bugs.x2go.org (X2Go Bug Tracking System)
Subject: Bug#367 closed by Stefan Baur <X2Go-ML-1@baur-itcs.de>
 (Closing/Archiving)
Message-ID: <handler.367.q367.170662837714937.notifdone@bugs.x2go.org>
References: <715cb10f-def8-47ef-9928-cf21c9de008b@baur-itcs.de>
X-X2go-PR-Keywords: fixed-upstream moreinfo
X-X2go-PR-Message: they-closed 367
X-X2go-PR-Package: nxagent
X-X2go-PR-Source: nx-libs
Date: Tue, 30 Jan 2024 15:30:02 +0000
Content-Type: multipart/mixed; boundary="----------=_1706628602-15284-0"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your Bug report
which was filed against the nxagent package:

#367: wine does not start within x2goclient: Application tried to create  a window, but no driver could be loaded.

It has been closed by Stefan Baur <X2Go-ML-1@baur-itcs.de>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Stefan Baur <X2Go-ML-1@baur-itcs.de> by
replying to this email.


-- 
367: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=367
X2Go Bug Tracking System
Contact owner@bugs.x2go.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefan Baur <X2Go-ML-1@baur-itcs.de>

To: 367-quiet@bugs.x2go.org

Subject: Closing/Archiving

Date: Tue, 30 Jan 2024 16:26:12 +0100

Control: close -1
Control: archive -1

This should no longer be a problem as the reported issue was fixed long ago.

Kind Regards,
Stefan Baur
-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

[Message part 3 (message/rfc822, inline)]

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: submit@bugs.x2go.org

Cc: mh@bzd.de

Subject: wine does not start within x2goclient: Application tried to create a window, but no driver could be loaded.

Date: Thu, 12 Dec 2013 22:38:18 +0000

[Message part 4 (text/plain, inline)]

Package: nxagent
Severity: important

While scanning our bug tracker logs, I found this mail from Matthias  
Hellinghausen which got not processed into the tracker, because the  
Package: <package> line was missing at the beginning of the mail...

Mike


"""
Hello

After upgrading the x2goserver from the following Versions

x2goagent      2:3.5.0.14-0~247~oneiric1
x2goserver     3.1.1.3-0~571~oneiric1

to

x2goagent     2:3.5.0.15-0~263~oneiric1
x2goserver    3.1.1.4-0~592~oneiric1

wine (v. 1.2.3) programs do not start anymore within the x2goclient session.

The following is what wine tells us when starting notepad:

mh@ltsp3:~$ notepad
Application tried to create a window, but no driver could be loaded.
Unknown error (998).
err:systray:initialize_systray Could not create tray window
Application tried to create a window, but no driver could be loaded.
Unknown error (998).

All other X-applications are working fine. The version of the x2goclient
did not change.

please let me know, If there is anything more you need to know...

kind regards
Matthais

-- 
Dipl.-Ing.(FH)  Matthias Hellinghausen
EDV-Abteilung
BZD Gesellschaft f. Transfusionsmedizin Duisburg mbH
K<F6>nigstrasse 63 - 47051 Duisburg

Tel.:    +49 (0) 203 - 300 95 8557
Fax:     +49 (0) 203 - 300 95 8564
Email:   mh@bzd.de

Sitz der Gesellschaft: Duisburg
Amtsgericht Duisburg HRB 4273
Gesch<E4>ftsf<FC>hrung: Sybille Trobisch, Olaf Frahm
"""
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 5 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.