--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767159
Title:
udevadm trigger --action=change crashes X.Org Server
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As the upstream maintainer of the Guest Additions I would like to
relativise this somewhat. I certainly quite agree in the context that
Felix made his comment in - since the development version of Ubuntu
(currently Natty) is a moving target, Guest Additions from VirtualBox
releases are unlikely
whereas Felix keeps the Guest Additions package in Ubuntu up to date
with not-yet-released fixes from upstream
Not to mention that Felix does much more testing of the Additions in
development versions of Ubuntu than we do, since we mainly focus on
released distributions.
--
You received this
This should be fixed by upstream patches [
http://www.virtualbox.org/changeset/36350 ] and [
http://www.virtualbox.org/changeset/36417 ].
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/747065
Title:
Please see [ https://bugs.launchpad.net/ubuntu/+source/nux/+bug/737610
Unity doesn't run in VirtualBox: compiz crashed with SIGABRT in
__kernel_vsyscall() ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The SIGABRT is just the result of the assertion when the memory
allocation fails. I would say that frames 11/12 of the stack trace is
closer to the problem, where it tries to allocate a texture surface with
a width of (in my trace) 1279729667.
--
You received this bug notification because you
Looking at Jean-Baptiste's more detailed trace I see that width in the
geo.width local variable in frame 14 (PanelMenuView::Refresh).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737610
Title:
** Attachment added: gdb output and backtrace for Unity crash
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/737610/+attachment/1931564/+files/unity.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hope that is of some interest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737610
Title:
Unity doesn't run in VirtualBox
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Would you be able to provide a bit more background information? Things that
might be interesting include:
* Are you using VirtualBox 4.0.4?
* What guest systems are you using, and does this affect all VMs you use?
* Does this happen as soon as the VMs start?
* Do the guest systems have Guest
This is not the same as the public ticket you mentioned. It is
reproducible with the current development version of VirtualBox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675307
Title:
compiz
Sorry, public ticket == http://www.virtualbox.org/ticket/8122...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675307
Title:
compiz can't load plugins and won't run in VirtualBox
--
ubuntu-bugs
Correction, this is not reproducible with the current development
version with correctly installed Additions :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675307
Title:
compiz can't load plugins
The Guest Additions in VirtualBox 4.0.4 also contain a fix for this -
the problem was that the Additions were sometimes setting graphics modes
that some versions of VirtualBox could not handle - so upgrading to them
once they are available in the repository (or just grabbing them from [
That sounds like the issue fixed by [
http://www.virtualbox.org/changeset/34667 ] in trunk. It has been
backported to the 3.2 line and any future 3.2 releases will contain the
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jürgen, could you be more specific about what you mean by crashes?
For example does the VirtualBox application on the host crash, or does
the guest have a kernel panic (that you can see) or does the graphical
interface/X crash?
--
You received this bug notification because you are a member of
Unchanged in a recently updated 10.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/641209
Title:
With appmenu-gtk some menus are blacked out in VirtualBox
--
ubuntu-bugs mailing list
Assuming for now that this is still relevant, although the last comment
by the reporter was a year and a half ago.
Bryce, I'm not quite sure if I understand your comment above. You
mention that this is not an issue with -radeon, as it only occurs when
VirtualBox is running, and VirtualBox uses a
This will happen sometime soon, but the X.Org Server 1.10 ABI doesn't
seem to have settled yet - there were incompatible changes between the
most recent release candidate and the (more recent) snapshot that Ubuntu
Natty is using.
--
You received this bug notification because you are a member of
This experimental Additions build (see
[http://www.virtualbox.org/wiki/Testbuilds]) worked for me with a Natty
guest updated this morning. It is from the development branch but
should work with 4.0. Note though that you will want to disable DPMS in
the guest due to a bug in the host code that
Better than disabling DPMS, here are a couple of links to current builds
from the stable branch (that is, 4.0.2 plus a few fixes, including the
one I mentioned). The links should be valid at least as long as the
Additions one above. They are shell script installers, not Debian
packages, but
201 - 221 of 221 matches
Mail list logo
