Thanks - looks to be the same as
https://bugs.launchpad.net/bugs/1813663. Can confirm that the given test
kernel (https://people.canonical.com/~khfeng/lp1813663/) works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Public bug reported:
I had to roll back - since the kernel was not working on these number of issues:
* could not connect to ThunderBolt dock (Dell TB16) and external monitor - Both
internal and external screen went totally black. And nothing I did (except of
hard reboot) could bring the screen
Final error message before things failed:
The `grub-efi-amd64-signed` package failed to install into /target/. Without
the GRUB boot loader, the installed system will not boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
I have done the following:
1) partitioned the disk
2) created an luks encrypted partition
3) decrypted the partition
4) configured lvm etc, created / /home /boot partitions
5) when installing selecting / /home /boot and the same partition as EFI is
installed on for windows fo
I get this behaviour almost every time Unity crashes for some reason -
or I manually kill gnome-session. It does not happen on re-boot for me.
(Although it did do that a couple of months ago.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
for me - manually running 'sudo apt-get autoremove' removed the old and
unused kernels - enabling the system to do a proper kernel upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184380
Title:
I had a very similar problem. I solved it with the help from this post:
http://askubuntu.com/questions/38083/initramfs-problem-when-out-of-disk-space
my /boot partition was almost full (it is 228MB) - so I uninstalled
three previous versions of the kernel - and then the install succeeded.
--
You
Ups: Ignore my last comment. I forgot which machine that was. I'm
running headless on that one, so I've not tried it for a while. You are
probably right, could very well be hardware issues. Sorry about that,
and thanks for the reply! :-)
--
You received this bug notification because you are a mem
Strange that the same hardware works flawlessly when running windows,
then? (i.e. 2560x1440 resolution in 60Hz). Unfortunately I've not been
able to run on that computer lately, so I don't know if it has been
fixed or not.
--
You received this bug notification because you are a member of Ubuntu
B
You have a point, but it's not related to my primary issue.
I'm using a dual-DVI cable, however the mobo (Asus P8H61I /
http://www.asus.com/Motherboards/Intel_Socket_1155/P8H61I/ ) only
supports DVI with Max. Resolution 1920 x 1200 @60Hz. The highest
available for me was 1600x1200 and 1680x1050. I
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949434
Title:
Problems with resolution
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/949434/+subscri
Public bug reported:
My screen is a Dell 27" Ultrasharp display with 2560 x 1440 in native
resolution.
When starting the installer {and also the installed OS for the first time}, the
resolution is 740(?)x400. Most config-applications have more information than
what fits on 400 pixels in height.
I found somewhere on the web a note that this could be due to problems
with google-talk. I tried un-installing google-talk, and have not
experienced this bug after that.
here is a listing from that log dir, any logs in particular which are
interesting (or still needed?)?
daffyd@laptop:~$ ls -al /
13 matches
Mail list logo
