Problem with X11 remote Connection VirtualBox 5.1.16

Discussions related to using VirtualBox on Solaris hosts.
Post Reply
o55o
Posts: 2
Joined: 3. Mar 2014, 16:53

Problem with X11 remote Connection VirtualBox 5.1.16

Post by o55o »

Solaris Host: SunOS isv4 5.11 11.3 i86pc i386 i86pc

After Installion of VirtualBox 5.1.16 X11 Connecton don't work:

ray: SunRayClient
isv: Solaris Host

Code: Select all

ray $ ssh  -l i_v -X isv

isv $ VirtualBox &
[1]     8457
isv Qt WARNING: failed to get the current screen resources
Qt WARNING: Qt: couldn't get core keyboard device info
Qt WARNING: The X11 connection broke: No error (code 0)
XIO:  fatal IO error 2 (No such file or directory) on X server "ray:8"
      after 211 requests (211 known processed) with 0 events remaining.

isv $ xterm           # This works !!!
Could not set destroy callback to IM
I have deinstalled 5.1.16 and installed Version 5.0.26. This works fine.
edseladap
Posts: 1
Joined: 14. Mar 2017, 19:38

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by edseladap »

I'm having the same issue. Does any one have a solution?
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all
Contact:

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by michaln »

edseladap wrote:I'm having the same issue.
No you're not. There was no VirtualBox 5.0.16 in September 2016, so the original report is nonsense.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by Guyver »

But 5.1.6 was (September 12th, 2016), and typos are common.

https://www.virtualbox.org/wiki/Changelog#v6

Be careful with your call button, before you alienate more Oracle customers.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by socratis »

Be careful with your reaction, because you're not a customer. You're a simple user, like the rest of us. Your message has been edited to clean your comment.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by socratis »

And just because there were several versions mixed up in this thread:
  • 2016-03-04 : 5.0.16
  • 2016-07-18 : 5.0.26
  • 2016-09-12 : 5.1.6
  • 2017-03-08 : 5.1.16
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
ChristianFr
Posts: 7
Joined: 25. Sep 2010, 14:28
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows 2003

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by ChristianFr »

Hello,

I updated today to 5.1.22
My linux is:

Code: Select all

Linux paris1.localdomain 4.1.12-94.3.4.el7uek.x86_64 #2 SMP Mon May 15 13:57:28 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
I did a "yum update" today too and restarted computer


I use Xming 6.9.0.31 on Windows 7 (Windows updated too today).

I do:

Code: Select all

[root@paris1 ~]# export DISPLAY=192.168.0.35:0.0
[root@paris1 ~]# VirtualBox &
[1] 18635
[root@paris1 ~]# Qt WARNING: failed to get the current screen resources
Qt WARNING: QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20
As you can see, I get the same kind of error (this is the only page that google gave to me when I look for "Qt WARNING: failed to get the current screen resources").

But VirtualBox looks to work, It is 5.1.14.
(Oops, not the last version)

I update VirtualBox to last version:

......

Code: Select all

Updated:
  VirtualBox-5.1.x86_64 0:5.1.22_115126_el7-1

Complete!
[2]+  Done                    VirtualBox  (wd: ~)
(wd now: /etc/yum.repos.d)
[root@paris1 yum.repos.d]# VirtualBox &
[1] 22610
[root@paris1 yum.repos.d]# Qt WARNING: failed to get the current screen resources
Qt WARNING: QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20
Still same message.

I restart computer...

Code: Select all

[root@paris1 yum.repos.d]# shutdown -r now
Using username "root".
root@192.168.0.49's password:
Last login: Wed May 17 19:31:15 2017
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1495042275
[root@paris1 ~]#
[root@paris1 ~]# echo $DISPLAY

[root@paris1 ~]# export DISPLAY=192.168.0.35:0.0
[root@paris1 ~]# VirtualBox &
[1] 3226
[root@paris1 ~]# Qt WARNING: failed to get the current screen resources
Qt WARNING: QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20

So, the same...

As VirtualBox looks like it works, I don't complain.

This is just to say that this problem still exists (And I am not smart enough to identify why).

Best regards,

Christian COMMARMOND
ChristianFr
Posts: 7
Joined: 25. Sep 2010, 14:28
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Windows 2003

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by ChristianFr »

Hi all,

three years later, with last versions of everything... No change:
Virtualbox 6.1.14
Server is CentOS Linux release 7.8.2003 (Core)
Client is Xming on Windows 7

[me@xxx ~]$ virtualbox &
[1] 18244
[me@xxx ~]$ Qt WARNING: failed to get the current screen resources

[me@xxx ~]$ Qt WARNING: QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20

And it is VERY slow if the user is not root (even if the client is another Centos machine).

I don't know if it is slow because of these errors, or other things...

If someone knows ho to solve this, please, share.

regards,
Christian COMMARMOND
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by scottgus1 »

I'm definitely not a Solaris expert, but I have some experience in Windows.

It sounds like you installed a Linux X server remote-in software in the Windows VM, and you are trying to remote into the VM using the X client on the Solaris host.

For this you would need a network: Bridged, Host-Only, or NAT/NAT Network using port forwarding, to get the client into the VM. Do you have such a network set up?
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Problem with X11 remote Connection VirtualBox 5.1.16

Post by fth0 »

scottgus1 wrote:It sounds like you installed a Linux X server remote-in software in the Windows VM, and you are trying to remote into the VM using the X client on the Solaris host.
As far as I understand from the posts, the setup is quite different from what you think (but I could be wrong, too ;)):

ChristianFr has a Windows PC with an X11 server and a SSH client. They use an SSH connection with X11 forwarding to connect to a Linux host. (The initial poster o55o had a Solaris guest and a Solaris host instead.) They start the VirtualBox Manager on the Linux host, and the QT warning messages appear.

@ChristianFr: Your description seems to be a little vague at some points:

Is my description above correct?

If yes, does the window of the VirtualBox Manager show up on the Windows PC or not?

If yes, what is the roundtrip delay on the X11 connection (ping)?
Post Reply