libGL errors when starting X applications via SSH











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
    2 days ago












  • 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
    2 days ago












  • 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
    2 days ago










  • 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
    2 days ago












  • In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
    – Binarus
    2 days ago















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
    2 days ago












  • 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
    2 days ago












  • 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
    2 days ago










  • 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
    2 days ago












  • In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
    – Binarus
    2 days ago













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 2 days ago

























asked 2 days ago









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
    2 days ago












  • 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
    2 days ago












  • 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
    2 days ago










  • 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
    2 days ago












  • In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
    – Binarus
    2 days ago


















  • 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
    2 days ago












  • 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
    2 days ago












  • 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
    2 days ago










  • 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
    2 days ago












  • In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
    – Binarus
    2 days ago
















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
2 days ago






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
2 days ago














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
2 days ago






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
2 days ago














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
2 days ago




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
2 days ago












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
2 days ago






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
2 days ago














In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
– Binarus
2 days ago




In fact, I am doing this for over 5 years now, and it works like a charm. This is really the first "problem" I came across. According to my experience, the Cygwin X server is working absolutely reliably. I am continuously running "big" applications (like Eclipse with a load of plugins) as well as simple ones (like konsole) that way. And in fact, the new setup also works without any problems, except that those error messages disturb me. I'll just ignore them if I can't find another solution ...
– Binarus
2 days ago















active

oldest

votes











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






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















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

Accessing regular linux commands in Huawei's Dopra Linux

Can't connect RFCOMM socket: Host is down

Kernel panic - not syncing: Fatal Exception in Interrupt