Installed sddm proposed sddm proposed 0.20.0-2ubuntu4.1 and the issue
persists, but adding the changes shown in
https://github.com/sddm/sddm/pull/1924/files to sddm.service file the
issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've just installed and tested the vagrant version uploaded to the -proposed
repo (vagrant/xenial-proposed,xenial-proposed,now 1.8.1+dfsg-1ubuntu0.2) and I
didn't find any issues so far.
Basically I up'ed a VM, checked that I can access it without problems, then
suspend/resume halt and up again.
I've just installed and tested the vagrant version uploaded to the -proposed
repo and I didn't find any issue so far.
Basically I up'ed a VM, checked that I can access it without problems, then
suspend/resume halt and up again.
Please find the log I got attached.
Thanks!
** Attachment added:
Sorry sil2100, I didn't find how to change the tag from verification-
needed-xenial to verification-done-xenial, could you please or
costamagnagianfranco manage that?.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
@LocutusOfBorg it worked now.
I was able to bring a VM up, access it via SSH, suspend it, resume it and
finally halt it without any issues (I'm pasting the log below). Just tell me if
you want me to test anything else.
Thanks!
vagrant up
Bringing machine 'default' up with 'virtualbox' provide
Hi @LocutusOfBorg,
I tried the build you uploaded and it threw the next error when running
"vagrant up":
/usr/share/vagrant/plugins/providers/virtualbox/driver/meta.rb:64:in
`initialize': uninitialized constant
VagrantPlugins::ProviderVirtualBox::Driver::Meta::Version_5_1 (NameError)
Did you me
Filled a bug report for Vagrant to be updated:
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1759829
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Title:
[SRU] Host with kernel 4.13
Public bug reported:
After Virtualbox packages were upgraded to version 5.1.34 in order to fix and
issue with newer Xenial kernels (see
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116) vagrant
package became outdated.
Current vagrant version on Xenial is 1.8.1 which supports V
As stated on comment #100 the current vagrant version on Xenial does not
support the updated Virtualbox version. Is it planned to update
Vagrant?.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736116
Fix on comment #7 worked for me on a Dell Latitude 3150,
4.8.0-36-generic kernel.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on
*** This bug is a duplicate of bug 1597415 ***
https://bugs.launchpad.net/bugs/1597415
Fix described on Comment #2 is working for me too on a Dell Latitude
3150.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I upgraded BIOS to the last available versión (2.12) and brightness
control seems to work now using Ubuntu 14.04.1 x64 live media and Radeon
driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131583
I've solved the no sound problem on my HP 2133 with Lucid by installing
Alsa 1.0.24, but the "spurious response" messages are still there. No
chance to change AGP aperture size to 256MB as the BIOS does not have
the option.
--
You received this bug notification because you are a member of Ubuntu
Just added "options snd-hda-intel position_fix=1" (without the quotes)
to /etc/modprobe.d/alsa-base.conf and the problem seems to be corrected
altough "hda-intel: spurious response 0x0:0x0, last cmd=0x00" log
entries keep appearing in the messages file. The idea was taken from
http://www.alsa-
I can confirm it too. Using an HP 2133 Mini Note with Via based
motherboard and CPU.
--
"hda-intel spurious response" messages and intermittent GDM startup with Intel
D945GCLF Motherboard
https://bugs.launchpad.net/bugs/536699
You received this bug notification because you are a member of Ubuntu
15 matches
Mail list logo
