Public bug reported:
I need to build certain X11 software for an i386 target on my amd64 box.
The following packages do not support multi-arch installation:
libice-dev libsm-dev libxext-dev libxmu-dev libxrandr-dev libxrender-dev
libxt-dev
However, a quick check after installing the i386
I started getting proper kernel crash dumps last week. Congratulations
and thanks to whoever made that work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec
Given that the Linux kernel doesn't maintain a stable ABI for modules I
don't think it can really be considered a VirtualBox bug that a given
version doesn't support Linux kernels which weren't written at the time
of its release. I would say it is more a sad fact of life.
--
You received this
Nice little workaround for IRC, and hence for idle (at least it does the
job at a pinch): http://wiki.tcl.tk/3125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/304889
Title:
Does not use system
True, but casting this as an upstream VirtualBox bug is a bit hard,
particularly as Ubuntu packages version 3.2.8 whereas we are already at
version 3.2.14 upstream which should support all kernels currently
released.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
VirtualBox 3.1.x is no longer maintained. If you need support for
current Linux kernel versions please consider running a newer version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907667
Title:
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-needs-upstream-bug-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Title:
Hard hang on resume
Fixed upstream on Nov 8 2011
(https://www.virtualbox.org/changeset/39224), the fix will be in any
future 4.0 releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899759
Title:
package
Finally had the problem with my self-built kernel, and ran into the
error shown here [1]. Perhaps you should work on making this a bit
easier (as in the lockup detector enabled by default and the crash
kernel correctly (!) installed), so that it works automatically when
Apport is enabled.
[1]
I tried applying the workaround from this comment [1] and will see if I
get a core next time.
[1] https://bugs.launchpad.net/ubuntu/+source/kexec-
tools/+bug/785425/comments/13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By the way, I take it that I shouldn't need to enable Apport to get the
crash dump, should I? Apport just automatically reports it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Title:
Hard
Kirill: I am commenting as the member of the VirtualBox development team
in charge of keyboard handling in Linux. My guess is that the locate
pointer tool places a passive grab [1] on the control key. What this
means if it is correct is that as of the point when the grab is placed
no other
I wouldn't have thought that the keyboard issue is related to
VirtualBox, as we simply emulate a standard PS/2 keyboard which should
be handled in the kernel and transparent to the layers above. The X
server crash might be - I assume that you have vboxvideo loaded into
both servers, and having it
That line will always be present in Xorg.*.log when VirtualBox's 3D
passthrough is in use. The reason is that our DRI driver implementation
is not complete, and that is not likely to change in the near future,
due to lack of developer time and more pressing issues. We have
actually had one or
Might it be the same issue as this [1][2]?
[1] https://forums.virtualbox.org/viewtopic.php?f=6t=45549p=205449#p205408
[2] https://www.virtualbox.org/ticket/9799
** Bug watch added: Virtualbox Trac #9799
http://www.virtualbox.org/ticket/9799
--
You received this bug notification because you
I didn't realise that the Ubuntu kernels don't enable the lockup
detectors. I have recompiled a kernel with the detectors enabled and no
other changes (I hope) and will see if that produces more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
CurrentDmesg.txt shows a segfault in unity_support_t. May or may not be
caused by the VirtualBox Guest Additions, and if so most likely by the
3D support.
The bit
DkmsStatus:
vboxguest, 4.1.2, 3.0.0-10-generic, i686: installed
virtualbox-guest, 4.1.2, 3.0.0-10-generic, i686: installed
Just tested again. I no longer see this on bare metal (I think I did
before, but it was so long ago...) I do see it in VirtualBox (Oneiric
VM) with and without Guest Additions installed. I will take fifteen
minutes to see if I can debug it.
--
You received this bug notification because you
I note that in
(gdb) p handlers[i]
$2 = {BlockHandler = 0x9604b0, WakeupHandler = 0x9605e0,
blockData = 0x8fd06f8, deleted = 1}
the value of deleted is 1. WakeupHandler() actually checks that - some
concurrency issue?
--
You received this bug notification because you are a member of Ubuntu
pInfo-read_input - EvdevReadInput - EvdevMBEmuFinalize -
RemoveBlockAndWakeupHandlers - handlers[i].deleted = TRUE;
Do I recall correctly that read_input is called from the SIGIO handler
in the X server?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My first instinct would be to try the following patch. Looking at the
server source code I don't think that read_input will be called in a
loop if it returns without doing anything, and I would assume that the
server will get notification from udev on a separate path to trigger
device removal
I intercepted this in gdb, with the following result (unfortunately I
couldn't find a debug symbol package for the evdev driver):
Program received signal SIGSEGV, Segmentation fault.
0x00960600 in ?? () from /usr/lib/xorg/modules/input/evdev_drv.so
(gdb) bt
#0 0x00960600 in ?? () from
Public bug reported:
Every so often, I will suspend my laptop and get a hard hang with a
blank screen when I resume. Last time but one Alt-Sysrq-C worked
(judging by the flashing keyboard LEDs), last time (a few minutes ago)
it didn't. So far I have failed to get any information on the hang. I
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Title:
Hard hang on resume from suspend
To manage notifications about this bug go to:
Certainly, I will do that, though it may take a while as the problem is
rather irregular, so I won't just be able to say straight off that it is
solved or not (plus there is always the Heisenbug factor). And as I
said, if you can think of any ways I could get more information about
this to debug
That went a bit faster than I expected - I had a hang with at least what
looked like the same symptoms within an hour of trying out 3.2.0rc1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Afraid I can't seem to add or remove tags myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Title:
Hard hang on resume from suspend
To manage notifications about this bug go to:
** 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
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:
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:
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
Public bug reported:
With current Natty, doing udevadm trigger --action=change --subsystem-
match=input inside a terminal crashes X.Org. Reverting commit
c5602d16399b5abb9d67365144134728a27e1cc5
--
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
Fixed upstream in VirtualBox 4.0.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776535
Title:
virtualbox udev rules should use RUN+= rather than RUN=
--
ubuntu-bugs mailing list
http://www.virtualbox.org/changeset/37104 and
http://www.virtualbox.org/changeset/37105 were the two relevant
changesets that I am aware of (they are packaging fixes, but there may
have been actual code fixes too that I missed.) 4.0.8 is supposed to
contain nothing butcherry picked bug fixes over
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.
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 [
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
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
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
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
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 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
Just got a hang after resume on 3.5.0-17-generic on Precise. Rather
unfortunate that CONFIG_BOOTPARAM_*LOCKUP_PANIC are not set in the
default kernel configuration - is there a reason why you consider it
better to hang the machine than to panic it? It seems to me that
enabling those options and
Any chances of getting this back-ported to 12.04 (or 13.04 for that
matter)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193492
Title:
[udev] Network devices with a MAC with prefix 08:00:27
Public bug reported:
In Raring, when pidgin is running with an IRC chat window open and all
others closed, I find no way to get to the main window (Buddy List)
except re-launching the pidgin executable, e.g. via the Dash. Until a
couple of weeks ago this could be done by clicking on the Pidgin
Public bug reported:
When I execute xdg-open from the command line on a C++ source file
that file gets opened in a new instance of qtcreator, even if one is
already running. It might make sense to open the file in an existing
instance (qtcreator -client). Feel free to close this as won't fix
if
Public bug reported:
When I suspend and resume my laptop with Qt Creator running I get a
crash. I originally automatically filed bug 119 for this and was
told that the uploaded data was not valid and I should file another one.
So I have installed relevant debug symbols and caught it in gdb.
Created bug #1090488 for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888762
Title:
Hard hang on resume from suspend
To manage notifications about this bug go to:
Public bug reported:
It would be nice if you could enable CONFIG_BOOTPARAM_*LOCKUP_PANIC in
the Ubuntu kernel configurations. This should allow you to get valuable
information about various sorts of kernel lock-ups. It would be nice
for me as a user as I do see lock-ups from time to time which
Log files are not relevant here.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090488
Title:
Please enable
era, Phil, please let's continue this on
https://www.virtualbox.org/ticket/8234.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/351518
Title:
Video mode change in client should not create a new
Thank you. Is there also a test build for Quantal? I will not upgrade
before the beta cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1107598
Title:
Blank screen on resume from suspend
To
Public bug reported:
This ticket is analogue to bug #1099278 for VirtualBox MAC addresses,
namely that /etc/udev/rules.d/70-persistent-net.rules should skip
VirtualBox guest network devices.
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Patch added: Skip
Public bug reported:
I was previously reporting this on bug 966744, which is however now
marked as fixed and we are requested to open new reports. This is an
issue which I get very sporadically on resuming my Dell Latitude E6410
whereby the keyboard is still active (I was able to switch to a
I would like to draw attention to this issue again. The fix which was
created is somewhat problematic, as it causes clipboard content to be
lost when the screensaver password screen is shown. Relevant to me is
that when that screen is shown in an Ubuntu guest in VirtualBox using
clipboard
Any estimate as to how long this will take to get into Ubuntu, and which
versions it will get into? We have to know whether to provide a work-
around in our software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You might want to try a recent test build of VirtualBox1. We are
reworking full-screen mode to use the official freedesktop/EWMH APIs and
having a hard time writing code which all the different window managers
like. The specifications leave quite a bit open to interpretation...
1
By the way, I am not (of course!) saying that it is a bug in VirtualBox.
Realistically there are probably equal chances of it being a problem
with VirtualBox, a problem with Unity or a misunderstanding between the
two.
--
You received this bug notification because you are a member of Ubuntu
Thank you. I wonder whether your flickering issue will stay fixed, as
I can't think why a reboot would make a difference for VirtualBox
(perhaps for Unity...) I suspect that the menu bar issue is because
this is a generic Linux and not a specific Ubuntu build, but I suggest
that that discussion
We are re-working multi-monitor full-screen support in VirtualBox, and
the new code, which should be part of the next fails in Compiz because
of this bug. Specifically the top left-hand corners of guest screens
is offset from that of the host screen by an amount related to the
position of the
Public bug reported:
PrivateWindow::setFullscreenMonitors() contains the following:
CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (),
screen-outputDevs ()[monitors-top].y1 (),
screen-outputDevs ()[monitors-right].x2 (),
I no longer run a Trusty system myself - I run Utopic, which already
contains the fix (which I can and have confirmed). I have however added
a note onto the VirtualBox bug tickets, in which this was reported as a
bug in VirtualBox, asking the users to test the fixed Ubuntu package.
--
You
[Impact]
* VirtualBox and other multi-monitor full-screen applications using the
freedesktop.org standard are not displayed in a usable way when running
multi-monitor full-screen in Unity without this fix.
* The bug makes the above set-up unusable. Low regression potential as
this is an
Got a colleague to test 1:0.9.11.3+14.04.20150122-0ubuntu1 and confirm
that the fix works. Once again, I am unpleasantly surprised at how much
work you offload onto someone who points out an obvious typing mistake
in a line of source code.
** Tags removed: verification-needed
** Tags added:
Public bug reported:
Happens during a build of VirtualBox. I think that the make output
describes the problem best:
kBuild: Generating
/home/michael/vbox/trunk/out/linux.amd64/debug/obj/vboxjws-gen/jwsgen/jwsglue.list
/home/michael/vbox/trunk/tools/linux.x86/jdk1.6.0_27/bin/wsimport
Note that this is a 32-bit jdk1.6.0 on a 64-bit host in case it is
relevant. (I suspect the problem is 1.6 vs 1.7 though.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430429
Title:
jayatana
Just seen this again with Vivid.
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364539
Title:
[Dell Latitude E7440] suspend/resume
For information, I am the original reporter. I set this to confirmed
because I am still seeing the problem (not reproducible on demand, in
fact only extremely sporadic) and one other person (mr-ghettoblaster)
confirmed it. Is a new bug report still useful? If so, for my help in
filing it, what
Sorry about that. This was one of about twenty automatic reports by
Apport when I upgraded to Vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364539
Title:
[Dell Latitude E7440]
Please see comment 1[1] and 14[2] on that ticket. We believe that this
is a problem in setfont, not in VirtualBox (or Ubuntu for that matter).
[1] https://www.virtualbox.org/ticket/13615#comment:1
[2] https://www.virtualbox.org/ticket/13615#comment:14
--
You received this bug notification
Update: I noticed that I was unable to select and paste URLs and parts
of URLs from Firefox to Pidgin this morning. I naively assume that it
is the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Quite often (subjectively nearly always) when I am using my laptop -
Dell Latitude E7440 - undocked with the internal touch pad, after a
while middle click paste stops working in gnome-terminal. I can middle-
click paste in e.g. Firefox, but neither from nor to
Sorry, got distracted from this since I didn't have enough spare time to
get the Qemu set-up with the device running just now. Fortunately I
still have my original e-mail to Maarten with the device path in it:
/sys/devices/pci:00/:00:03.0/virtio1/drm/card0
--
You received this bug
Seems to be fixed here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT in g_assertion_message()
To manage notifications about this bug go to:
Looks like a case of Problem between Keyboard and Chair. I notice that
middle clicks work when I release the button very quickly. It is hard
to say now of course, I think that that was not necessary previously,
which is what mislead me. I will leave it up to others whether to keep
this open or
Might this be related to bug 1499747<1>?
<1> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499133
Title:
unity-panel-service crashed
Public bug reported:
I pointed this out to Maarten half a year ago, and he seemed concerned
but didn't actually do anything. Your "drm_device_keep_trying.patch" X
server patch crashes the X server with Dave Airlie's virtio GPU device
and driver, and probably with any driver on a non-USB bus
Public bug reported:
After upgrading to Wily, when I change the configuration of screens
attached (specifically: dock the laptop to a docking station with a
vertically larger external screen or open the laptop to activate the
internal screen while correctly running with said external screen) this
By the way, this applies to at least Wily and Vivid, probably several
more releases. The bug happens if the device is present, even if it is
not used because no driver is present.
** Patch added: "Modified version of drm_device_keep_trying.patch with does not
crash with virtio-gpu"
I am now no longer seeing the flicker and resolution issues much (and
poking the hardware, e.g. by opening the Display control panel usually
gets rid of it). I have a suspicion there might be hardware issues too.
The mouse cursor issue is still present with kernel 4.2.0-7-generic, and
still not
Sorry, "systemctl daemon-reexec".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456789
Title:
restarting services hangs on systemd-tty-ask-password-agent
To manage notifications about this bug go
Ran into something similar just now. A bit of internet searching
suggested<1><2> that it was due to systemd's internal state getting out
of sync, and indeed running "systemctl daemon-reload" made it go away.
<1> https://github.com/NixOS/nixpkgs/issues/2584
<2>
Is this alright?
** Patch added: "Fix timing issues on USB3 or fast recent hardware. Back-port
from upstream."
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+attachment/4465857/+files/usb3_timing_fix.debdiff
--
You received this bug notification because you are a
I can't test immediately in any case, as I am travelling and do not have
access to an external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492170
Title:
Screen flicker and resolution
As I said, display was so badly broken with that kernel that I was
unable to test, though it might have been co-incidence - it has always
been rather temperamental with all the 4.1 and 4.2 kernels I have
tested. In my few short tests I was unable to get the external monitor
to display anything at
I get the following building VirtualBox (the problematic command is
"javac vboxjxpcom.jar", can't immediately see the full command line).
Using Unity and a pretty standard Ubuntu Wily.
Could not find agent library instrument on the library path, with error:
libinstrument.so: cannot open shared
Seems to work for me (see comment 35).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441487
Title:
Running any Java program produces messages in the terminal, while
rendering many Java
Current status: with BIOS A15 and kernel 4.2.0-11-generic I was unable
to get the external screen to connect at all in an X session (a VT
worked more or less fine). Now using kernel 4.3.0-040300rc3-generic and
so far no visible graphical problems at all. I will keep you updated.
--
You
I can also reproduce this as described in comment 14, and get it
whenever I start Pidgin and log in to my Jabber account:
$ pidgin
**
GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed:
assertion failed: (position + removed <=
Note that I cannot confirm that this was due to the BIOS update, since I
tested with the new kernel too. This was not an issue with the old BIOS
and a 4.1 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Martin, it might be good to wait for more feedback before closing this.
I suspect that different people may be seeing different issues, and that
some might still have problems. And in defence of upstream, a short
sleep does seem reasonable to me when dealing with timing issues in
black box
1 - 100 of 221 matches
Mail list logo
