I hope this upstream change set will do the trick:
https://www.virtualbox.org/changeset/62242
Re comment 11, I looked at Mesa to see how they were distinguishing
client and server GL and applied that to my code (see comments in change
set).
To summarise the issue: the tricks that we were
Sorry, that doesn't do it yet. (Shame I didn't manage to fix this for
5.0.0.) However I realised that Mesa has exactly the same problem, so I
have taken a look at their code to see what they do. Also looks like a
bit of a hack, but since nothing relevant can afford not to work with
Mesa it
This changeset was applied upstream:
https://www.virtualbox.org/changeset/62201/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Further discussion at:
https://irclogs.ubuntu.com/2016/07/12/%23ubuntu-devel.html#t15:20
with a pointer to:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c#L136
And side-discussion of possible better ways of how to detect client GL
vs. server GL, which
My apologies, I missed that one, so this is probably my bug! I will fix
that and then get back to you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1599775
Title:
The initial log contains the following:
[+2.89s] DEBUG: Launching process 888: /usr/bin/X -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+5.70s] DEBUG: Process 888 exited with return value 127
And the X log shows:
/usr/lib/xorg/Xorg: symbol lookup error:
@ellisistfroh: I cannot see anything in the lightdm (1.18.2-0ubuntu1)
changelog to suggest that it might have addressed this issue.
@michael-thayer: thank you for spending the extra time to confirm that
lightdm (1.18.2-0ubuntu1) is still affected.
--
You received this bug notification because
I was able to reproduce this with the lightdm deb file from that package
installed. I did not install the other deb files built from the
package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Various bugfixes were implemented in LightDM V. 1.18.2-0ubuntu1 [1]
This package is still awaiting approval as it covers a few issues...
The bugs are referenced there. Hope this helps.
[1] https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1
found via Pending Ubuntu SRU's:
Added to Trello: https://trello.com/c/Un8N5Pfs/16-bug-1599775-low-
graphics-mode-in-virtualbox-guest-but-x-server-running
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Description changed:
I sometimes get the "low-graphics mode" message when starting an Ubuntu
16.04 virtual machine inside of VirtualBox (current development code
trunk, somewhere past version 5.1 beta 3 and a debug build). When I
switch to VT-7 I find the X server running without any
Actually, perhaps I misunderstand the lightdm log rotation and the .1
logfile does contain the relevant log. I assume the lightdm developers
will know.
My uneducated guess is that there is some sort of race here between
lightdm and logind which needs better dependency specification.
And I just
Just checked, I do not have that message in the current log file,
attached the file from yesterday containing the message.
I asked about this on #ubuntu-devel, here are the relevant logs:
(17:09:06) michael-vb: Afternoon. Not sure if this is the right place to ask,
but someone will probably
** Attachment added: "The log file from yesterday."
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+attachment/4696780/+files/lightdm.log.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
14 matches
Mail list logo
