libGL errors when starting X applications via SSH

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have read a bunch of similar questions on this site and others, but all of them either didn't reflect my situation or didn't provide a working solution.



So I have a Debian stretch x64 server running in a virtual KVM machine. I have installed Cygwin on Windows 7 Pro x64 and would like to run X applications on the Debian machine, using the Cygwin X server at the Windows machine.



This is my server-side SSH daemon configuration (Debian side):



AcceptEnv LANG LC_*
AllowAgentForwarding no
AllowTcpForwarding no
AllowStreamLocalForwarding no
ChallengeResponseAuthentication no
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr
Compression no
DebianBanner no
HostKeyAlgorithms ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-rsa,ssh-ed25519
KbdInteractiveAuthentication no
KexAlgorithms curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
ListenAddress 192.168.20.12:22
LoginGraceTime 20
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com
PasswordAuthentication no
PermitUserRC no
Protocol 2
PubkeyAcceptedKeyTypes ssh-rsa,ssh-ed25519
RekeyLimit 100M 20m
Subsystem sftp /usr/lib/openssh/sftp-server
TCPKeepAlive no
X11Forwarding yes
X11UseLocalhost yes


This is the batch file I use to start konsole on the server (Windows side):



set CYG=c:cygwin64

%CYG%binrun.exe XWin -multiwindow -resize -clipboard -listen inet :1
SET DISPLAY=:1
SET LANG=en_US.UTF-8
%CYG%binssh.exe -f -Y root@192.168.20.12 "LANG=en_US.UTF-8 konsole"
"C:Program Files (x86)cmdowcmdow.exe" X-Morn-multiwindow /HID
exit


In principle, this works: When executing this batch file, konsole starts in a window on my Windows desktop. But there are two error messages in the cmd window:



libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast


As a last resort, I could live with those errors because konsole (and the other applications I need) obviously actually work, but I really would prefer knowing what is going on there (i.e. what causes the error messages).



From reading the other questions / threads / blog entries I have mentioned above, I got the impression that the problem might be related to missing nvidia or mesa components. So I installed some of these components on the Debian server doing (as root):



aptitude install libgl1-mesa-glx libgl1-glvnd-nvidia-glx


Indeed, when I then ran the batch file mentioned above, the libGL errors were not thrown any more. But unfortunately, now the konsole window did not appear on the Windows desktop any more.



After uninstalling the two packages again, the konsole window again appeared when I ran my batch file - of course, this is true for the libGL error messages as well.



I would like to understand both of the phenomena. So what could be the cause of the libGL error messages (given the fact that missing mesa or nvidia drivers or libraries should not play a role when running X applications via SSH), and why does installing the two packages mentioned above keep the konsole windows from appearing?



Once again, all other questions I saw were relating to situations where the OP wanted to start X applications locally, i.e. wanted to run them on the same machine where the X server ran, or did not have a solution which was working in my case.










share|improve this question























  • In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
    – Rui F Ribeiro
    Dec 8 at 9:50











  • I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
    – Binarus
    Dec 8 at 10:15











  • The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
    – Rui F Ribeiro
    Dec 8 at 10:23










  • TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
    – Rui F Ribeiro
    Dec 8 at 10:34







  • 1




    I have found out by accident how to solve the problem - see my own answer.
    – Binarus
    Dec 13 at 7:24














up vote
0
down vote

favorite












I have read a bunch of similar questions on this site and others, but all of them either didn't reflect my situation or didn't provide a working solution.



So I have a Debian stretch x64 server running in a virtual KVM machine. I have installed Cygwin on Windows 7 Pro x64 and would like to run X applications on the Debian machine, using the Cygwin X server at the Windows machine.



This is my server-side SSH daemon configuration (Debian side):



AcceptEnv LANG LC_*
AllowAgentForwarding no
AllowTcpForwarding no
AllowStreamLocalForwarding no
ChallengeResponseAuthentication no
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr
Compression no
DebianBanner no
HostKeyAlgorithms ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-rsa,ssh-ed25519
KbdInteractiveAuthentication no
KexAlgorithms curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
ListenAddress 192.168.20.12:22
LoginGraceTime 20
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com
PasswordAuthentication no
PermitUserRC no
Protocol 2
PubkeyAcceptedKeyTypes ssh-rsa,ssh-ed25519
RekeyLimit 100M 20m
Subsystem sftp /usr/lib/openssh/sftp-server
TCPKeepAlive no
X11Forwarding yes
X11UseLocalhost yes


This is the batch file I use to start konsole on the server (Windows side):



set CYG=c:cygwin64

%CYG%binrun.exe XWin -multiwindow -resize -clipboard -listen inet :1
SET DISPLAY=:1
SET LANG=en_US.UTF-8
%CYG%binssh.exe -f -Y root@192.168.20.12 "LANG=en_US.UTF-8 konsole"
"C:Program Files (x86)cmdowcmdow.exe" X-Morn-multiwindow /HID
exit


In principle, this works: When executing this batch file, konsole starts in a window on my Windows desktop. But there are two error messages in the cmd window:



libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast


As a last resort, I could live with those errors because konsole (and the other applications I need) obviously actually work, but I really would prefer knowing what is going on there (i.e. what causes the error messages).



From reading the other questions / threads / blog entries I have mentioned above, I got the impression that the problem might be related to missing nvidia or mesa components. So I installed some of these components on the Debian server doing (as root):



aptitude install libgl1-mesa-glx libgl1-glvnd-nvidia-glx


Indeed, when I then ran the batch file mentioned above, the libGL errors were not thrown any more. But unfortunately, now the konsole window did not appear on the Windows desktop any more.



After uninstalling the two packages again, the konsole window again appeared when I ran my batch file - of course, this is true for the libGL error messages as well.



I would like to understand both of the phenomena. So what could be the cause of the libGL error messages (given the fact that missing mesa or nvidia drivers or libraries should not play a role when running X applications via SSH), and why does installing the two packages mentioned above keep the konsole windows from appearing?



Once again, all other questions I saw were relating to situations where the OP wanted to start X applications locally, i.e. wanted to run them on the same machine where the X server ran, or did not have a solution which was working in my case.










share|improve this question























  • In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
    – Rui F Ribeiro
    Dec 8 at 9:50











  • I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
    – Binarus
    Dec 8 at 10:15











  • The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
    – Rui F Ribeiro
    Dec 8 at 10:23










  • TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
    – Rui F Ribeiro
    Dec 8 at 10:34







  • 1




    I have found out by accident how to solve the problem - see my own answer.
    – Binarus
    Dec 13 at 7:24












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have read a bunch of similar questions on this site and others, but all of them either didn't reflect my situation or didn't provide a working solution.



So I have a Debian stretch x64 server running in a virtual KVM machine. I have installed Cygwin on Windows 7 Pro x64 and would like to run X applications on the Debian machine, using the Cygwin X server at the Windows machine.



This is my server-side SSH daemon configuration (Debian side):



AcceptEnv LANG LC_*
AllowAgentForwarding no
AllowTcpForwarding no
AllowStreamLocalForwarding no
ChallengeResponseAuthentication no
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr
Compression no
DebianBanner no
HostKeyAlgorithms ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-rsa,ssh-ed25519
KbdInteractiveAuthentication no
KexAlgorithms curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
ListenAddress 192.168.20.12:22
LoginGraceTime 20
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com
PasswordAuthentication no
PermitUserRC no
Protocol 2
PubkeyAcceptedKeyTypes ssh-rsa,ssh-ed25519
RekeyLimit 100M 20m
Subsystem sftp /usr/lib/openssh/sftp-server
TCPKeepAlive no
X11Forwarding yes
X11UseLocalhost yes


This is the batch file I use to start konsole on the server (Windows side):



set CYG=c:cygwin64

%CYG%binrun.exe XWin -multiwindow -resize -clipboard -listen inet :1
SET DISPLAY=:1
SET LANG=en_US.UTF-8
%CYG%binssh.exe -f -Y root@192.168.20.12 "LANG=en_US.UTF-8 konsole"
"C:Program Files (x86)cmdowcmdow.exe" X-Morn-multiwindow /HID
exit


In principle, this works: When executing this batch file, konsole starts in a window on my Windows desktop. But there are two error messages in the cmd window:



libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast


As a last resort, I could live with those errors because konsole (and the other applications I need) obviously actually work, but I really would prefer knowing what is going on there (i.e. what causes the error messages).



From reading the other questions / threads / blog entries I have mentioned above, I got the impression that the problem might be related to missing nvidia or mesa components. So I installed some of these components on the Debian server doing (as root):



aptitude install libgl1-mesa-glx libgl1-glvnd-nvidia-glx


Indeed, when I then ran the batch file mentioned above, the libGL errors were not thrown any more. But unfortunately, now the konsole window did not appear on the Windows desktop any more.



After uninstalling the two packages again, the konsole window again appeared when I ran my batch file - of course, this is true for the libGL error messages as well.



I would like to understand both of the phenomena. So what could be the cause of the libGL error messages (given the fact that missing mesa or nvidia drivers or libraries should not play a role when running X applications via SSH), and why does installing the two packages mentioned above keep the konsole windows from appearing?



Once again, all other questions I saw were relating to situations where the OP wanted to start X applications locally, i.e. wanted to run them on the same machine where the X server ran, or did not have a solution which was working in my case.










share|improve this question















I have read a bunch of similar questions on this site and others, but all of them either didn't reflect my situation or didn't provide a working solution.



So I have a Debian stretch x64 server running in a virtual KVM machine. I have installed Cygwin on Windows 7 Pro x64 and would like to run X applications on the Debian machine, using the Cygwin X server at the Windows machine.



This is my server-side SSH daemon configuration (Debian side):



AcceptEnv LANG LC_*
AllowAgentForwarding no
AllowTcpForwarding no
AllowStreamLocalForwarding no
ChallengeResponseAuthentication no
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr
Compression no
DebianBanner no
HostKeyAlgorithms ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-rsa,ssh-ed25519
KbdInteractiveAuthentication no
KexAlgorithms curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
ListenAddress 192.168.20.12:22
LoginGraceTime 20
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com
PasswordAuthentication no
PermitUserRC no
Protocol 2
PubkeyAcceptedKeyTypes ssh-rsa,ssh-ed25519
RekeyLimit 100M 20m
Subsystem sftp /usr/lib/openssh/sftp-server
TCPKeepAlive no
X11Forwarding yes
X11UseLocalhost yes


This is the batch file I use to start konsole on the server (Windows side):



set CYG=c:cygwin64

%CYG%binrun.exe XWin -multiwindow -resize -clipboard -listen inet :1
SET DISPLAY=:1
SET LANG=en_US.UTF-8
%CYG%binssh.exe -f -Y root@192.168.20.12 "LANG=en_US.UTF-8 konsole"
"C:Program Files (x86)cmdowcmdow.exe" X-Morn-multiwindow /HID
exit


In principle, this works: When executing this batch file, konsole starts in a window on my Windows desktop. But there are two error messages in the cmd window:



libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast


As a last resort, I could live with those errors because konsole (and the other applications I need) obviously actually work, but I really would prefer knowing what is going on there (i.e. what causes the error messages).



From reading the other questions / threads / blog entries I have mentioned above, I got the impression that the problem might be related to missing nvidia or mesa components. So I installed some of these components on the Debian server doing (as root):



aptitude install libgl1-mesa-glx libgl1-glvnd-nvidia-glx


Indeed, when I then ran the batch file mentioned above, the libGL errors were not thrown any more. But unfortunately, now the konsole window did not appear on the Windows desktop any more.



After uninstalling the two packages again, the konsole window again appeared when I ran my batch file - of course, this is true for the libGL error messages as well.



I would like to understand both of the phenomena. So what could be the cause of the libGL error messages (given the fact that missing mesa or nvidia drivers or libraries should not play a role when running X applications via SSH), and why does installing the two packages mentioned above keep the konsole windows from appearing?



Once again, all other questions I saw were relating to situations where the OP wanted to start X applications locally, i.e. wanted to run them on the same machine where the X server ran, or did not have a solution which was working in my case.







ssh x11 nvidia mesa






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 8 at 9:09

























asked Dec 8 at 9:03









Binarus

237111




237111











  • In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
    – Rui F Ribeiro
    Dec 8 at 9:50











  • I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
    – Binarus
    Dec 8 at 10:15











  • The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
    – Rui F Ribeiro
    Dec 8 at 10:23










  • TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
    – Rui F Ribeiro
    Dec 8 at 10:34







  • 1




    I have found out by accident how to solve the problem - see my own answer.
    – Binarus
    Dec 13 at 7:24
















  • In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
    – Rui F Ribeiro
    Dec 8 at 9:50











  • I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
    – Binarus
    Dec 8 at 10:15











  • The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
    – Rui F Ribeiro
    Dec 8 at 10:23










  • TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
    – Rui F Ribeiro
    Dec 8 at 10:34







  • 1




    I have found out by accident how to solve the problem - see my own answer.
    – Binarus
    Dec 13 at 7:24















In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
– Rui F Ribeiro
Dec 8 at 9:50





In windows you are dealing with the windows HAL and not with the graphic card. Furthermore, often X servers in windows give you a outdated implementation of the X primitives. Using other shareware or even sometimes commercial implementations will often leave you no better. We are however talking about windows limitations and superuser se would be a better fit for this question.
– Rui F Ribeiro
Dec 8 at 9:50













I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
– Binarus
Dec 8 at 10:15





I am grateful for your comment, but to be honest, I doubt your statement. As I have described, changing the configuration at the Linux side definitely makes the error messages go away. I am pretty sure that those messages are not caused by the X server in Windows or any other Windows component. It seems that X applications started at the server side are searching for some libraries although those libraries are not needed when the applications are started via SSH.
– Binarus
Dec 8 at 10:15













The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
– Rui F Ribeiro
Dec 8 at 10:23




The fact they use the libraries does not invalidate what I am saying. You are dealing with several questions, however without using Linux natively or in a vm, the lack of libraries is the least of your worries
– Rui F Ribeiro
Dec 8 at 10:23












TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
– Rui F Ribeiro
Dec 8 at 10:34





TLDR I would not even try to go via remote X... see NX/NoMachine for having a fulll Linux desktop on your side. Have tried to go down that road in the past, and X in Windows does not deliver. See also this unix.stackexchange.com/questions/462817/…
– Rui F Ribeiro
Dec 8 at 10:34





1




1




I have found out by accident how to solve the problem - see my own answer.
– Binarus
Dec 13 at 7:24




I have found out by accident how to solve the problem - see my own answer.
– Binarus
Dec 13 at 7:24










1 Answer
1






active

oldest

votes

















up vote
0
down vote













The problem went away after installing the following packages (apt has installed them together):



  • dbus-x11

  • libglib2.0-tests

  • libdbus-glib-1-2

  • libgee-0.8-2

  • libmoonshot1

I can't tell for sure which of these packages (or which combination thereof) made the problem go away. I do not plan to do further examinations because this machine has become a production server in the meantime.



However, I think I can give an educated guess:




  • libgee-0.8-2 and libmoonshot1 do not have anything to do directly with the low-level X11 or UI parts, so I am quite sure that they are out of the game.


  • libglib2.0-tests (as the name implies) is just a test suite for GLib, so I am quite sure that this is out of the game as well.

  • I really can't tell which of the remaining two candidates might have solved the problem. I have the feeling that the problem was more related to GLib than to X11, so my favorite is libdbus-glib-1-2. But this is really just a feeling ...

It would be nice if somebody in the same situation (i.e. setting up a Debian stretch server and running X applications via SSH) could confirm this. But even when not, I think this answer is useful because exactly this question has been asked at other places dozens of times without a solution having been given (to my best knowledge).






share|improve this answer




















  • lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
    – Rui F Ribeiro
    Dec 13 at 8:23











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486741%2flibgl-errors-when-starting-x-applications-via-ssh%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













The problem went away after installing the following packages (apt has installed them together):



  • dbus-x11

  • libglib2.0-tests

  • libdbus-glib-1-2

  • libgee-0.8-2

  • libmoonshot1

I can't tell for sure which of these packages (or which combination thereof) made the problem go away. I do not plan to do further examinations because this machine has become a production server in the meantime.



However, I think I can give an educated guess:




  • libgee-0.8-2 and libmoonshot1 do not have anything to do directly with the low-level X11 or UI parts, so I am quite sure that they are out of the game.


  • libglib2.0-tests (as the name implies) is just a test suite for GLib, so I am quite sure that this is out of the game as well.

  • I really can't tell which of the remaining two candidates might have solved the problem. I have the feeling that the problem was more related to GLib than to X11, so my favorite is libdbus-glib-1-2. But this is really just a feeling ...

It would be nice if somebody in the same situation (i.e. setting up a Debian stretch server and running X applications via SSH) could confirm this. But even when not, I think this answer is useful because exactly this question has been asked at other places dozens of times without a solution having been given (to my best knowledge).






share|improve this answer




















  • lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
    – Rui F Ribeiro
    Dec 13 at 8:23















up vote
0
down vote













The problem went away after installing the following packages (apt has installed them together):



  • dbus-x11

  • libglib2.0-tests

  • libdbus-glib-1-2

  • libgee-0.8-2

  • libmoonshot1

I can't tell for sure which of these packages (or which combination thereof) made the problem go away. I do not plan to do further examinations because this machine has become a production server in the meantime.



However, I think I can give an educated guess:




  • libgee-0.8-2 and libmoonshot1 do not have anything to do directly with the low-level X11 or UI parts, so I am quite sure that they are out of the game.


  • libglib2.0-tests (as the name implies) is just a test suite for GLib, so I am quite sure that this is out of the game as well.

  • I really can't tell which of the remaining two candidates might have solved the problem. I have the feeling that the problem was more related to GLib than to X11, so my favorite is libdbus-glib-1-2. But this is really just a feeling ...

It would be nice if somebody in the same situation (i.e. setting up a Debian stretch server and running X applications via SSH) could confirm this. But even when not, I think this answer is useful because exactly this question has been asked at other places dozens of times without a solution having been given (to my best knowledge).






share|improve this answer




















  • lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
    – Rui F Ribeiro
    Dec 13 at 8:23













up vote
0
down vote










up vote
0
down vote









The problem went away after installing the following packages (apt has installed them together):



  • dbus-x11

  • libglib2.0-tests

  • libdbus-glib-1-2

  • libgee-0.8-2

  • libmoonshot1

I can't tell for sure which of these packages (or which combination thereof) made the problem go away. I do not plan to do further examinations because this machine has become a production server in the meantime.



However, I think I can give an educated guess:




  • libgee-0.8-2 and libmoonshot1 do not have anything to do directly with the low-level X11 or UI parts, so I am quite sure that they are out of the game.


  • libglib2.0-tests (as the name implies) is just a test suite for GLib, so I am quite sure that this is out of the game as well.

  • I really can't tell which of the remaining two candidates might have solved the problem. I have the feeling that the problem was more related to GLib than to X11, so my favorite is libdbus-glib-1-2. But this is really just a feeling ...

It would be nice if somebody in the same situation (i.e. setting up a Debian stretch server and running X applications via SSH) could confirm this. But even when not, I think this answer is useful because exactly this question has been asked at other places dozens of times without a solution having been given (to my best knowledge).






share|improve this answer












The problem went away after installing the following packages (apt has installed them together):



  • dbus-x11

  • libglib2.0-tests

  • libdbus-glib-1-2

  • libgee-0.8-2

  • libmoonshot1

I can't tell for sure which of these packages (or which combination thereof) made the problem go away. I do not plan to do further examinations because this machine has become a production server in the meantime.



However, I think I can give an educated guess:




  • libgee-0.8-2 and libmoonshot1 do not have anything to do directly with the low-level X11 or UI parts, so I am quite sure that they are out of the game.


  • libglib2.0-tests (as the name implies) is just a test suite for GLib, so I am quite sure that this is out of the game as well.

  • I really can't tell which of the remaining two candidates might have solved the problem. I have the feeling that the problem was more related to GLib than to X11, so my favorite is libdbus-glib-1-2. But this is really just a feeling ...

It would be nice if somebody in the same situation (i.e. setting up a Debian stretch server and running X applications via SSH) could confirm this. But even when not, I think this answer is useful because exactly this question has been asked at other places dozens of times without a solution having been given (to my best knowledge).







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 13 at 7:49









Binarus

237111




237111











  • lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
    – Rui F Ribeiro
    Dec 13 at 8:23

















  • lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
    – Rui F Ribeiro
    Dec 13 at 8:23
















lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
– Rui F Ribeiro
Dec 13 at 8:23





lidbdbus-glib seems an unlikely candidate, though in the sea of dependencies who knows. Many apps are happier if dbus (and dependencies) are installed though.
– Rui F Ribeiro
Dec 13 at 8:23


















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486741%2flibgl-errors-when-starting-x-applications-via-ssh%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?