This seems to be a duplicate of 1242417. However the fix applied for
that bug didn't fix the underlying problem but instead created a
workaround that was sufficient for the case that led to the bug. It
does not fix the situation reported here.
--
You received this bug notification because you
Public bug reported:
An ubuntu system has files in a folder within /boot/efi/EFI and an EFI
variable both of whose names are given by the GRUB_DISTRIBUTOR variable
in /etc/default/grub. By default this is set to "ubuntu".
I wish to have two ubuntu systems on the same machine so on one of them
This should probably be closed now. I am currently running 22.04 guests
on 20.04 host and everything working OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893957
Title:
Ubuntu 20.04 guest
Just experimented with a "clean" Ubuntu system that had grub-efi-
amd64-signed. To get the prompt for the efi partitions I had to call
dpkg-reconfigure shim-signed. After that it seemed to work OK.
I wish I knew where all this was documented.
--
You received this bug notification because you
I've now managed to recreate this in a checkpointed virtual machine.
The last few lines from do-release-upgrade are:
Updating repository information
Hit http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Public bug reported:
I recently upgraded a Ubuntu Budgie system from 20.04 to 22.04 the
upgrade worked fine apart from one problem.
The original system had two EFI partitions mounted at /boot/efia &
/boot/efib. Grub is quite happy with this and updates both. However
do-release-upgrade failed
I had some problems when using grub-efi-amd64-signed rather than grub-
efi-amd64. Unfortunately not consistent enough to create a coherent bug
report. A number of times I ended up dropping into grub command line.
That seemed not to happen with the unsigned version.
--
You received this bug
Since focal the change I originally asked for at the beginning of this
thread has now been made. If you set up multi efi partitions, not
raided, when you run "dpkg-reconfigure grub-efi-amd64" the system asks
which efi partitions you wish to use. You can specify more than one and
it then
I have now upgraded the guest to 20.10, version 6.1.14, and things have
changed. I can log into a graphical session. I briefly get the desktop
and then the screen goes black.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I strongly disagree. If you have a machine that has boot problems,
knowing which entry is which could be very helpful when trying to
resolve.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877861
I've tried using Virtualbox 6.1.14 from this PPA -
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-
ppa in both host and guest.
This seems to fix the problem.
I did experience another problem but not sure if appropriate to bug as
running from the PPA.
--
You received
I'm now running virtualbox 6.1.10 on Kubuntu 20.04 and the problem seems
to have been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731495
Title:
After minimising full screen VM, on
This has also happened with a Debian guest where the additions have been
loaded from the Guest Additions CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893957
Title:
Ubuntu 20.04 guest aborts
On further experimentation the problem seems to be with guest-x11. If I
just have guest-utils installed the system is OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893957
Title:
Ubuntu 20.04
The guest is running the same version of virtualbox - guest-utils and
guest-x11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893957
Title:
Ubuntu 20.04 guest aborts on graphical login following
Public bug reported:
I recently did apt update on a virtual box guest - Ubuntu 20.04.1
running under a Kubuntu 20.04.1 host. After the update the guest boots
up and I can log into a console session but as soon as I log into a
graphical session the vm aborts. This also applies to guests running
Sorry, I started a red herring with the previous post. After some
digging it appears that at some point in the past I set up an
environment variable to put the config in ~/gtk-gnutella. Before
testing 1.2.0 I cleared everything out so I had a clean set up, not
realising that that would cause a
I've not had time to test it fully but it does seem to work apart from
one thing. The program expects folder ~/gtk-gnutella to exist and
doesn't start if it doesn't. If I create the folder manually it works
OK.
I created a .deb package by running "debian/rules binary"
--
You received this bug
I've now experimented with VMs I have of different Ubuntu flavours.
gtk-gnutella starts OK in Lubuntu and Xubuntu but not in Ubuntu,
Kubuntu, Ubuntu Mate and Ubuntu Budgie.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tried again and realised that there were messages in apport.log. Also a
crash report, attached.
ERROR: apport (pid 5620) Sat May 23 09:38:36 2020: called for pid 5129, signal
11, core limit 0, dump mode 1
ERROR: apport (pid 5620) Sat May 23 09:38:36 2020: executable:
/usr/bin/gtk-gnutella
Public bug reported:
Since upgrading to Kubuntu 20.04 and installing the package from the
ubuntu repository gtk-gnutella does not start. I click on it in the
menu and nothing appears to happen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gtk-gnutella 1.1.15-1
ProcVersionSignature:
Public bug reported:
I have been trying out the new facility to install grub to multiple efi
partitions. Both of the efi entries shown in efibootmgr have the same
label and these are all that is shown in the boot selection menu on my
systems making it impossible to distinguish between them.
This seems to have been fixed for 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875166
Title:
grub-efi-amd64.postinst not running grub-install when GRUB_DISTRIBUTOR
changed
To manage
Public bug reported:
I wished to change the label of the EFI entry created by grub-install.
I did this by amending the GRUB_DISTRIBUTOR entry in /etc/default/grub.
I then ran "dpkg-reconfigure grub-efi-amd64" expecting this to create a
folder in /boot/efi/EFI and create an EFI entry under the
** Changed in: virtualbox (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816383
Title:
Unable to install virtualbox-guest-x11 on 18.04.2 LTS with HWE
To
Same problem. Clean install of Ubuntu Mate 18.04.2. Installed
virtualbox-guest-dkms-hwe and virtualbox-guest-utils-hwe OK. When I
tried to install virtualbox-guest-x11-hwe this failed, log attached.
** Attachment added: "xxyyzz3"
*** This bug is a duplicate of bug 1466150 ***
https://bugs.launchpad.net/bugs/1466150
** This bug has been marked a duplicate of bug 1466150
grub-install breaks when ESP is on raid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This problem now seems to have arisen in a recently updated 16.04
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683043
Title:
Black screen after installing virtualbox-guest-x11
To manage
Just did a fresh upgrade of Ubuntu Mate from Xenial to Bionic. The
guest packages were installed on the Xenial system prior to upgrade.
During the upgrade the guest packages were upgraded, NOT removed.
However, on the upgraded system the virtualbox-guest-utils.service was
NOT started but could
Raised upstream as https://www.virtualbox.org/ticket/17636.
** Bug watch added: Virtualbox Trac #17636
http://www.virtualbox.org/ticket/17636
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731495
Sorry, not sure what you mean by an upstream bug report. Do you mean
via the Oracle website or somewhere else on Launchpad?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731495
Title:
After
Regarding the original service not starting problem.
If I do a clean 18.04 install everything works OK. (Apart from Lubuntu
where I couldn't get the installer to work.)
If I do a clean 17.10 install without the guest packages because of bug
#1683043, upgrade to 18.04, install dpkg-dev, install
Had a look at your PPA and realised that you had got hwe versions of the
guest packages as well as virtualbox-hwe.
So, added your PPA to 16.04 Kubuntu guest and tried to upgrade to
18.04. However do-release-upgrade disabled the entry before it
upgraded. In that case I don't know how to test
I thought virtualbox-hwe was a host package. My problem was when
upgrading guest systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753430
Title:
virtualbox-guest-utils.service not starting
Slightly confused by this response and the move to "Fix released".
The fix referred to fixes the compilation error. However there are two
other problems - the service not starting even when the module compiled
and the packages being uninstalled during the upgrade. Do I need to
raise those as
Sorry, 5.2.8 doesn't fix it.
Something I hadn't noticed before, both with the original version and
5.2.8.
If I alternately minimise/maximise/minimise/maximise/ on the
maximise it alternately fails/works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've tried with 5.2.6 from your PPA and the problem is still there.
Wasn't sure where to get 5.2.8 from as I'm running 17.10. Is there an
Ubuntu source or should I use the Oracle site?
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
Installing dpkg-dev solved the compilation problem. The DKMS modules
now seem to compile on all systems.
However on Lubuntu and Ubuntu Mate, even though modules now compile, the
service is not started automatically even though it is shown as enabled.
This matches the situation reported at the
Here is the Lubuntu log
** Attachment added: "lubuntu.make.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1753430/+attachment/5081202/+files/lubuntu.make.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the Xubuntu log
** Attachment added: "xubuntu.make.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1753430/+attachment/5081204/+files/xubuntu.make.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have now done clean installs of 16.04, installed the virtualbox-guest
packages then upgraded to 18.04.
In all cases the 16.04 install worked. When adding the guest packages I
received the messages similar to:
vboxguest:
Running module version sanity check.
Error! Module version 5.0.40_Ubuntu
I've been trying various things - not sure if they help or confuse!
Firstly I should clarify one thing. For these trials Xubuntu and
Lubuntu are 32 bit, the rest all 64 bit. I did not think this relevant
as originally one 32bit worked, one didn't, one 64bit worked, one
didn't.
I have tried to
Public bug reported:
Installing Lubuntu 386 daily build downloaded today to a Virtualbox VM
running on Kubuntu 17.10 host. Crashed partway through installation.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname:
I will try clean installs but it may be a day or so. In the meantime I
also have a couple of 18.04 VMs running on a Windows 10 host. In an
Ubuntu Mate guest the service isn't started. In a Kubuntu guest it is
started.
--
You received this bug notification because you are a member of Ubuntu
On Ubuntu Mate purged and reinstalled. Service still not started.
On Lubuntu reinstall failed - will investigate further.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I am trialing various flavours of Ubuntu in Virtualbox virtual machines
- Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate. All version 18.04, running
on Kubuntu 17.10 host. All set up identically as far as I can tell,
with virtualbox-guest-dkms, virtualbox-guest-utils and
This problem seems to have gone away on 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683043
Title:
Black screen after installing virtualbox-guest-x11
To manage notifications about this
** Bug watch added: Debian Bug tracker #889977
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889977
** Also affects: mdadm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889977
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #889978
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889978
** Also affects: mdadm (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889978
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
When using File->New to create a torrent, although the prompt says "file
or directory to create torrent from" only directories are shown, no
files.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ktorrent 5.1.0-2
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic
I agree that the severity is incorrect. Whenever grub-install is run -
ie when the version of grub is upgraded - I end up with an unbootable
system. Yes, my trusty rescue disk sorts it out but that's not a
solution.
Referring to the comment above, I have two EFI entries, one for each
disk.
Public bug reported:
When running a VM full screen, if I minimise the VM and then restore
it, the VM stays in full screen mode but only about a quarter of it is
shown.
In the attached screen shot you can see a Xubuntu guest part showing top
left on a Kubuntu host.
The problem occurs both with
I have tried the PPA version and it seems to fix the problem, thanks.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691138
Title:
Public bug reported:
mdadm schedules a run of checkarray once a month using an entry in
/etc/cron.d
However, if the machine is not running at the time this is scheduled it
will not be run, even when the machine is reloaded.
Perhaps this should be moved to /etc/cron.monthly so that anacron can
Should have said - this applies to both Windows 10 and Linux guests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691138
Title:
Toolbar unresponsive in full screen mode
To manage notifications
Public bug reported:
Since upgrading to zesty I cannot use the toolbar in fullscreen mode.
When I hover the mouse at the bottom of the screen the toolbar appears
as expected but none of the menu items respond to clicking. When I move
the mouse away the toolbar disappears as expected. When I
I've only noticed this recently but I don't look in the journal often so
can't say how long the issue has been there.
I tried the 4.8 kernel. The messages were still there but lower
frequency 2 or 3 per minute.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Public bug reported:
I have a USB multi-card reader. When it is plugged in I get continuous
messages in the journal
eg
Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6
using xhci_hcd
Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about
Just tried with Ubuntu 16.04 and problem seems to have gone away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about
I think there might be two separate things here.
I've just had the same problem with a Debian system with spamassassin
not loading at boot time. My "systemctl status" was similar to the
above ie "disabled". "systemctl enable" didn't start the service but
changed the status to enabled and gave
I think there might be two separate things here.
I've just had the same problem with a Debian system with spamassassin
not loading at boot time. My "systemctl status" was similar to the
above ie "disabled". "systemctl enable" didn't start the service but
changed the status to enabled and gave
I recently removed an LVM snapshot that had been in place for some time.
When I next rebooted the delay problem had gone away.
It seems this is a known problem. There are a number of bugs where root
is on LVM and the delay causes boot to fail. I don't have root on LVM
so boot did not fail but
I will update BIOS as requested but I won't be able to do that for a
couple of days.
In the meantime I must apologise as I haven't mentioned that there is
another delay of about 40s as shown here
[ 122.281863] md: raid4 personality registered for level 4
[ 122.287699] md: raid10 personality
Managed to try updating after all. I tried both the F3 and F4 BIOS and
both still had both of the delays mentioned above. Here is the output
requested on the F3
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F3
02/05/2013
I'm currently on F3 but both F3 & F4 cause a new
Maybe same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500046
Title:
Boot pauses for 2 minutes after upgrade to wily
To manage
Maybe same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264
however the tpm_tis.force=1 fix mentioned has no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500046
Title:
CurrentDmesg.txt shows where the problem occurs.
[3.031482] random: nonblocking pool is initialized
[3.055042] clocksource: Switched to clocksource tsc
[ 121.818788] md: linear personality registered for level -1
[ 121.821422] md: multipath personality registered for level -4
[
Public bug reported:
Since upgrade to wily the boot process pauses for two minutes before
continuing.
systemd-analyse shows
Startup finished in 16.356s (firmware) + 2.898s (loader) + 2min 46.836s
(kernel) + 16.298s (userspace) = 3min 22.389s
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Public bug reported:
If --all given but no scheduling class specified only one array is
checked. This appears to be because at lines 194-200 the variable
ionice is checked. If no class is given then this is blank and the
script exits.
Either a default should be used or validation included to
Reviewing the documentation, not specifying the scheduling class seems
valid. In that case I thing the correction is to change 'break' on line
199 to 'continue'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have seen this behaviour a number of times on Ubuntu and Debian.
After you create the array you need to update mdadm.conf. However, this
is not enough as you also need to update the version in initrd.img.
This might happen automatically if you subsequently do some updates. I
find the easiest
I've now done a clean install of Kubuntu 15.04 and Kate now works fine
over ftp without any special action.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449731
Title:
Kate cannot edit files over
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about
And here's the screen with the warning message. I pressed continue
which the text implies to me will continue with UEFI install.
** Attachment added: GUEFI3.png
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418696/+files/GUEFI3.png
--
You received this bug
Mathieu
I did get the popup about a non-UEFI system and thought I had chosen the
correct option for UEFI. Will include when I create screen shots for
Phillip.
I believe I created an ESP. Screen shots to follow.
I've tried Ubuntu and Ubuntu-Gnome with the same result. Debian 8
seemed to work
Philip
I agree the partman log seems to show no EFI partition yet the parted
list shows one their and it is mounted.
I've now done an Ubuntu build with screenshots for you.
Here is the partitioning screen.
** Attachment added: GUEFI1.png
When the install completed grub-pc was installed, not grub-efi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about this
Here's the screen just before committing the changes.
** Attachment added: GUEFI2.png
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418695/+files/GUEFI2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Evidence that installer run in EFI
root@kubuntu:~# ls /sys/firmware/
acpi efi memmap
Evidence that grub-pc installed
root@kubuntu:~# ls
Parted listing
** Attachment added: parted.out
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418341/+files/parted.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evidence that installer run in EFI
root@kubuntu:~# ls /sys/firmware/
acpi efi memmap
Evidence that grub-pc installed
root@kubuntu:~# cd /target/var/lib/dpkg/info/
root@kubuntu:/target/var/lib/dpkg/info# ls -l grub*
-rw-r--r-- 1 root root713 Apr 22 13:06 grub2-common.list
-rw-r--r-- 1 root
Yesterday I ran 6 installs in VirtualBox. If I used automatic
partitioning I got grub-efi. If I used manual partitioning I got grub-
pc. I was rather surprised when I realised my real machine had booted
with grub-pc on a GPT disk without a bios_grub partition but it did.
The grub installer
partman log
** Attachment added: /var/log/partman
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418340/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I only created one disk. Could the DVD cause a problem? I'm sure I
picked Continue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage
Just spotted a difference between auto and manual partition installs.
The log for a manual install includes the line
Jun 21 17:53:54 kubuntu grub-installer: info: architecture:
amd64/generic
The log for an automatic install says amd64/efi
This value drives which grub is installed and comes from
Thank you for the reply. I had read a number of articles on this which
put me off trying that option and implied rather clumsy solutions which
was why I raised the request. However, I have now tried it and barring
one problem it works and I can boot off either disk.
The problem occurred when I
The original install where the problem was experienced was done with
only one disk in place, with root in sda4 and EFI in sda1, swap sda2.
These were set up with manual partitioning. No RAID.
After I had removed grub-pc and installed grub-efi I added the extra
disk and raided sda3/sdb3 and moved
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about
parted output attached. The original install had root in sda4. After
install moved to RAID1 on sda3 + 2nd disc.
Regards
Tony
** Attachment added: parted.out
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4416510/+files/parted.out
--
You received this bug
Just tried this in a clean VirtualBox VM. If I use automatic
partitioning everything seems to work as it should. If I manual
partition I get the same fault as reported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Installing Kubuntu 15.04 to a self built machine with Gigabyte GA-
F2A85X-UP4 motherboard with new 4TB disk.
Got machine to boot DVD in UEFI mode and when into Try Ubuntu mode so
that I could check it was running in UEFI. Then hit Install Kubuntu.
Used manual partitioning,
** Attachment added: partman
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4416266/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Sorry, should have made clear I am using AMD64 version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466047
Title:
Install in UEFI mode installs grub-pc
To manage notifications about this bug go
Public bug reported:
I run a server with mirrored (RAID1) disks using grub-efi.
Root and /boot and /boot/grub are on mirrored partitions.
I have EFI partitions on both disks but it is not possible to RAID1
these as they are FAT32. On an EFI system grub-install will only
install to one of the
Public bug reported:
Since upgrading to 15.04 I cannot edit files accessed over ftp. The
file appears to open but I end up with a blank file. This worked fine
on earlier releases.
There are a number of reports of this on the Internet. As documented
elsewhere I can get round the problem by
Just installed new version. Seems to solve problem in both Calc and
Base.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856210
Title:
Horizontal Scrollbar in kde dont work (default theme)
To
Public bug reported:
Binary package hint: grub2
Attempting to upgrade to Grub2 on Maverick system following these
instructions:
https://help.ubuntu.com/community/Grub2#Upgrading%20to%20GRUB%202
When I try to install grub-pc I receive the following:
grub-pc: Conflicts: grub ( 0.97-54) but
Happened again but the traceback is a little different
EXCEPTION:
Traceback (most recent call last):
File /var/lib/python-support/python2.5/BitTornado/RawServer.py, line 144,
in listen_forever
File /var/lib/python-support/python2.5/BitTornado/SocketHandler.py, line
319, in handle_events
Public bug reported:
Binary package hint: bittornado
When running btlaunchmanycurses it runs for some time but then crashes.
EXCEPTION:
Traceback (most recent call last):
File /var/lib/python-support/python2.5/BitTornado/RawServer.py, line 144,
in listen_forever
File
1 - 100 of 110 matches
Mail list logo
