Public bug reported:
PROBLEM:
Phpvirtualbox depends on having vboxweb starup and listening properly.
I installed the virtualbox 5.2.18-dfsg-2~ubuntu18.04.3 package on a
default server install of 18.04, and had trouble getting the
vboxweb.service unit file to accept my environment changes to
/etc
Also affects me.
I cannot believe that this is still set to low. This is yet another
case of the systemd circus-tools causing unexpected behavior for long-
time linux users.
This breaks local DNS resolution in my homelab. I should NOT have to do
a Google search to fix this, it should just work
I am also having this problem on two machines. One is a laptop with an
s3 unichrome adapter, one is a desktop machine with an Nvidia 8400GS. I
don't think the gfx card is the problem, but something with the open()
call that xscreensaver-getimage is doing. I can list the directories
from the she
How serendipitous! I try again moments ago, and I hit it right on the
nose!
I've attached my trace, but the stuff at the very end is the most relevant:
[0x7fe517bab700:] EXCEPTION handling: NullReferenceException
Read with:
gunzip -c huge-debug-spew.gz | tail -n 1000 | less
** Attachment added:
I have also had this happen when I have a network disconnect and
reconnect. I suppose by definition, a suspend-resume willl
automatically cause a network disconnect-reconnect, hence I notice the
bug at that time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Hey, has there been any progress on this?
I first noticed this in Lucid, and it continues in Meerkat on my Dell
Vostro Laptop with Intel HDA:
snd_pcm89104 3 snd_hda_intel,snd_hda_codec
The specifics of this bug for me are as follows:
Start any sound (for me it would be launchin
I have the same problem, and it's been bugging me for at least 6+ months
(since at least 10.04).
This consistently happens after suspend to RAM (I have a notebook).
Upon waking, Gnome-Do consumes 100%-400% CPU (all cores)
Ubuntu 10.10 x86_64
gnome-do:
Installed: 0.8.3.1+dfsg-2ubuntu1
Candida
Actually, the REAL problem here is that fundamental, documented behavior
has been changed in an LTS release.
The is a symptom of a larger problem: established norms randomly
changing with every new release, completely breaking backwards
compatibility.
Where in the world did the "fromdos" and "tod
