Sorry to revive this thread, but shouldn't builddeb honor the
`DEBSIGN_KEYID` environment variable and use the provided ID?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328281
Title:
bzr-buildpack
Public bug reported:
This happened, I think, because I have installed a key using the MOK
UEFI utility on my first installation attempt, and then tried installing
again because I had AHCI disabled the first time. I didn't check the
"Configure secure boot" checkbox the second time, but I did check
I seem to be affected by the same bug, here are the latest syslog
entries before the new boot. I'd be glad to use ubuntu-bug, but it only
reports current dmesg, which have nothing related to the previous boot.
-- There is a lot of these kind of messages about resume errors, I have to hold
page d
*** This bug is a duplicate of bug 1629870 ***
https://bugs.launchpad.net/bugs/1629870
The ppa:costamagnagianfranco/virtualbox-ppa PPA fixes the problem for
me, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I did as Alberto said, and nothing has changed. For the sake of purity I
have creted a new user and tried to log in. In this case X just
restarts, I am attaching a log file with the crash backtrace in the end.
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg
I have installed it using apt-get:
sudo apt-get install nvidia-319-updates
Right now when I run dpkg -l and grep for nvidia, I get only two
packages with 'ii' flag:
ii nvidia-319-updates319.60-0ubuntu1 amd64
ii nvidia-settings-319-updates319.60-0ubu
Public bug reported:
I have an Acer V3-772G laptop with an NVIDIA GeForce 760M video adapter
that is combined with a built-in Intel HD Graphics 4600 using the
Optimus technology.
I am running Ubuntu Saucy with the latest updates from the official
repos (nothing like xorg-edgers or swat):
$ lsb_r
Is there maybe a newer version of this bug? I have had a similar episode
on my machine running 64-bit Precise on Linux 3.2.0-32-generic kernel.
I had been dragging and dropping files from Nautilus to Totem when this
had happened.
--
You received this bug notification because you are a member of
I tried to do what David said about the "Analog mix" setting, and did
not find one in my alsamixer. However, when I played with the "Mic
boost" setting, I noticed that it doesn't correspond correctly to the
setting in the "Sound preferences" GUI menu.
When you lower it all the way down and get it