The System/Startup USB disk creator command in 32 bit Intrepid will
successfully create an Intrepid live usb stick, but will fail when given
the jaunty 32bit iso. The created usb stick will only have a syslinux 2
line text header and a "boot:" prompt. No splash, no menu choices, and
nothing enter
Public bug reported:
Binary package hint: grub-installer
System: laptop hd has WinXP, usb disk has several Linux distros.
Boot order is usb thumbdrive, usb hard disk, and laptop hard disk.
Using a Jaunty live usb thumbdrive, install to an USB partition.
Remove the usb thumbdrive and reboot. Th
This problem is present in Intrepid and easy to duplicate with a laptop and a
USB disk.
Installating Ubuntu to a USB disk is likely to be a common scenario.
Set the laptop boot order to be: USB/CDROM/harddisk. Boot the standared live
Ubuntu CD-ROM, plug
in the USB disk, and install to the first
The laptop is an HP Presario v3100 with an 80G Seagate ST98823as drive.
Always thought it was IDE. From the interrupts, it looks like the
harddisk is on the secondary slot, with the dvd/cdrom on the primary (or
nothing since the number of primary interrupts is 0). No tools to
actually open things
Navigation box appears to have a sporadic problem.
There is another page with this problem which causes a pink error box at the
top of the page:
How Can I Upgrade to the latest version of Ubuntu?
The error is not consistent -- it's either:
1)Not present (rare).
2)line 467 col 46 Encoding error
Public bug reported:
Binary package hint: apt
Manual purge of an old set of kernel files did not totally clean out the
/lib/modules/2.6.32-10-generic directory, leaving file
modules.builtin.bin. Noticed that a previous kernel ...9 removal left
the same file and directory.
sudo apt-get purge `ap
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39037117/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/39037118/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/39037119/ProcMaps.txt
** Attac
Public bug reported:
Binary package hint: linux-image-2.6.32-12-generic
Update-manager run Feb 10 had a problem with updating the kernel to 32-12.
A window claimed that dpkg --configure -a would be run, but that failed too.
Manual run below.
Wrong file name for firmware.sh appears to be the pr
As I recall, the stick did not work on a second laptop either. The problem was
fixed in Jaunty, since
a "create startup usb" command succeeded with a Karmic iso. I still have an
Intrepid installation which I can use to see if it can successfully create a
Karmic usb if that is of interest. I'm
Karmic/AMD64 after adding the spell, ispell, American dict packages,
evolution exhibits the crash in composing when a word break is first
typed. Removing the spelling packages is a workaround for the problem.
Maybe turning off spell checking as you type will also workaround the
problem. This has
I have seen my AMD/64 i386 9.10 system mouse (touchpad) freeze when I
move it when a network-manager popup message is displaying. If I have
another window open, I can still shift focus with Alt Tab, then the
mouse works again.
--
nm-applet freezes xorg/system
https://bugs.launchpad.net/bugs/52073
Lucid (10.04) has fixed the bad device.map (got rid of it), fixed the comments
mentioning devices on the other oses, and generally has rationalized the hd0 is
sda, hd1 is sdb. Unfortunately, the /etc/fstab file now puts / on
/dev/sdcx instead of /dev/sdbx (or UUID as in Karmic). Since there is
I use only released kernels, and see sporadic mouse freezeups when the
network-manager is doing something. Yesterday, my Jaunty system froze
when accessing the nm menu. I have wireless turned off with a manual
switch, but use network-manger for my usb mobile/modem connection. I
had no other wind
I just patched my Intrepid system to date Feb 20, 2010, and successfully
created a Karmic startup usb stick. The problem appears to have been
fixed.
--
live USB disk not bootable
https://bugs.launchpad.net/bugs/367766
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I just patched my Intrepid system to date Feb 20, 2010, and successfully
created a Karmic startup usb stick. The problem appears to have been
fixed.
--
live USB disk not bootable
https://bugs.launchpad.net/bugs/367766
You received this bug notification because you are a member of Ubuntu
Bugs, wh
The error appears on my Lucid system, AMD64 alternates between the below
two errors(in a pink box at top of page).
This page contains the following errors:
error on line 448 at column 737: AttValue: " or ' expected
Below is a rendering of the page up to the first error.
or
This page contains t
My locale is C, by the way, fully patched on Feb 1.
$ locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=
--
"Ubuntu - Linux for Human Beings!
/init/rw type tmpfs (rw,nosuid,mode=0755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/ubfan/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=ubfan)
df may indicate a /tmp space issue, but the working 64 bit output is the same
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36664091/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/36664092/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/36664093/ProcStatus.txt
--
update
As of Karmic (9.10), grub's use of UUIDs fixed the problem of being
unable to boot the other operating systems. The devices are still
wrong, but will make no difference unless the install is to a portable
device like a usb stick which should be able to boot windows on any PC.
In that case, fix the
Further testing with a 64 bit Karmic system now shows this problem.
With ramdisks mounted on /tmp and /var/cache/apt/archives (with
a directory "partial" created), the no space message appeared for
a 40M download for both the ...archives directory (possibly valid, but
I thought the default was 64M)
Another possibility is that your access point has run out of ip address
leases. I upped the number from 3 to 10 and things started working
again.
--
(Jaunty) Wicd No Longer Allows Me To Connect
https://bugs.launchpad.net/bugs/361461
You received this bug notification because you are a member of
Burned a live Lucid CD and booted up the HP Pavilion a210n. It experienced
the GL crash/hang too with the antSpotlight, so I guess the upgrade was not an
issue. I did find a warning at the top of one text screen which might be of
interest:
(Process:256): GLibWARNING **: getpwuid_r(): failed d
32 bit Lucid is OK for me. The spell packages no longer kill
composition.
--
evolution crashes when composing a message pressing space
https://bugs.launchpad.net/bugs/463920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I've been dancing around this problem for the last few releases too. My
workaround is to use /mnt instead of /media in fstab and then Gnome will obey
the noauto. Ideally, I would still get these noauto partitions listed in
Places/Other Removable Media menu so I could choose to mount them with
I mount my /var/log on a ramfs (since I run off a 4G thumbdrive), and
worked around the problem by creating any necessary directories in
rc.local. I've also created in rc.local a link from /var/cache/apt to a
/tmp/debs (with /tmp mounted as tmpfs) and create the /archives/partial
directory (path).
Upgraded from 8.04 to 10.04, and had the screensaver crash when using GL
screensavers. A quick click before the preview screensaver runs to
select a non GL screensaver stopped the crashes. The crash may be
related to the bonobo-activation server crash because of a missing
bonono socket in /tmp, a
I just saw the "disassociation by local choice (reason 3)" on Karmic & Jaunty
USB based systems which previously worked fine. I'm using the b43 Broadcom
open driver and the opensource Broadcom firmware. I think this is a hardware
problem, since iwlist scan will show the two available aps with
onobo-activation-server (ubfan-2327): could not associate
with desktop session: Failed to connect
to socket /tmp/dbus-cU04aUTdF2: Connection refused
May 12 20:08:23 dtop kernel: Kernel logging (proc) stopped.
May 12 20:08:23 dtop rsyslogd: [origin software="rsyslogd" swVersion="4.2.0"
The crash apparently happened on the 32-9 manual remove too. The 32-9 and
32-10 removals were the only ones I have seen with the error. I do not even
see the modules.buildin.bin in my 9.10 system. At some point, I lost the
graphics on the Lucid alpha, so I deleted it. The Lucid installation
*** This bug is a duplicate of bug 519855 ***
https://bugs.launchpad.net/bugs/519855
** This bug has been marked a duplicate of bug 519855
update-initramfs fails: ./lib/udev/firmware.sh does not exist
--
apt-get crashed with SIGSEGV in __fprintf_chk()
https://bugs.launchpad.net/bugs/52019
** This bug is no longer a duplicate of bug 519855
update-initramfs fails: ./lib/udev/firmware.sh does not exist
--
apt-get crashed with SIGSEGV in __fprintf_chk()
https://bugs.launchpad.net/bugs/520194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Here's another incomplete purge of kernel files, which did not cause a crash
(different file this time, modules.seriomap).
This installation was on a hard disk, in a usb 2.0 enclosure.
Intrepid patched to date March 10, 2010 showed the manual kernel cleanup
problem. Same file, modules.seriomap w
The root of this problem is the inability of python's os.statvfs to handle
ramfs file systems. A workaround
is to use tmpfs instead, then everything works. ...DistUpgradeCache.py has the
checkFreeSpace function which utilizes the os.statvfs. The purpose of using a
ram disk here is to minimize
After many successful 32 bit Karmic installs from a live usb stick to usb
sticks and usb hard disks, I installed a 64bit Karmic from a CDROM (to a usb
stick) and clicking on the Advanced button, noticed the difference in the use
of (hd0) for the boot location instead of an actual device (e.g. /dev/
After a few weeks running the 4.15.0-33 kernel, I have seen the hbm...
message twice, much less frequently than before turning off the security
chip, but it's not totally gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Ubuntu 18.04 Wayland, Select a desktop file icon and drag it to the
nautilus window. When the icon touches the window, it jumps back to the
original starting point, the cursor remains a hand, and can no longer
move the icon, which is still highlighted. No other icon may be
highlighlited, clicking
The necessary (for systemd-resolvd to work properly) package libnss-
resolve is still not included with Ubuntu 18.04 nor Ubuntu 18.10
installs. Manually adding the package fixed the name resolution
problems on an otherwise unaltered installation using DHCP from a
gateway.
--
You received this bu
The link target, stub-resolv.conf is the correct file for enabling
systemd-resolvd. Various problems with the systemd-resolvd may be fixed
by installing the libnss-resolve package (bug 1769016). Blank local
domain problems have their own bug, 1699660 (fix is to use ~.). This
report probably should
Did you scan the dmesg output for firmware loading errors? Try dmesg
|grep -i firm and dmesg | grep 8821 and report results here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853665
Title:
Bluet
===As requested ===
$ dpkg -S libzstd.so.1
libzstd1:amd64: /usr/lib/x86_64-linux-gnu/libzstd.so.1.3.3
libzstd1:amd64: /usr/lib/x86_64-linux-gnu/libzstd.so.1
$ ls -l /usr/lib/x86_64-linux-gnu/libzstd.so*
ls: cannot access '/usr/lib/x86_64-linux-gnu/libzstd.so*': No such file or
directory
===Plus
Note that litzstd is typically the last library in alphabetical order,
and this is the third different package reported (see bug 1766046) with
this error.
What exact log are you requesting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
*** This bug is a duplicate of bug 1765803 ***
https://bugs.launchpad.net/bugs/1765803
Note that libzstd is typically the last library in alphabetical order,
and this is the third different package reported (see bug 1766046) with
this error.
What exact log are you requesting?
--
You receive
*** This bug is a duplicate of bug 1765803 ***
https://bugs.launchpad.net/bugs/1765803
Here's the fail in /var/log/apt/term.log
Log ended: 2018-04-15 15:56:00 (ok this far)
Log started: 2018-04-20 16:51:35
(Reading database ... 95%
(Reading database ... 187309 files and directories curren
Here's my log requested in the duplicate:
Log ended: 2018-04-15 15:56:00 (ok this far)
Log started: 2018-04-20 16:51:35
(Reading database ... 95%
(Reading database ... 187309 files and directories currently installed.)
Preparing to unpack .../dpkg_1.19.0.5ubuntu2_amd64.deb ...
Unpacking dpkg (
My situation breaking the install was a legacy install, to a disk
partition with another Ubuntu installation (16.04) maintaining the
bootloader files. The install was done without a bootloader (select an
empty USB, and the error dialog allows you to procede without a
bootloader). The update (afte
Public bug reported:
With kernel 4.4, HDMI audio code, e.g. intel_audio.c, cannot build because of
the compiler error of a wrong number of arguments for function pin_eld_notify.
The Ubuntu kernel headers for the kernel 4.4 series have a file,
.../drm/i915_component.h which contains a wrong proto
See bug Bug #1755309 for the mismatched prototype in the 4.4 linux
headers for i915_component.h -- preventing building the HDMI audio code.
The 4.10 kernel code finally matched the prototype, and the
intel_audio.c file compiles.
--
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 1385113 ***
https://bugs.launchpad.net/bugs/1385113
** This bug has been marked a duplicate of bug 1385113
hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ubuntu 18.04 still has the "unknown main item tag", occurring on a Thinkpad
W520 after a suspend, but the Bluetooth Microsoft Sculpt Comfort Mouse now
reconnects successfully.
dmesg grep ...
[34731.172621] hid-generic 0005:045E:07A2.0013: unknown main item tag 0x0
[34731.172743] input: Microsoft
Ubuntu 18.04 running bluez 5.37-0ubuntu5.1 has fixed the 16.04 problem
of bluetooth not running after a suspend. My mouse has successfully
reconnected 100+ times. The USB inputxx is still incrementing at each
resume, so that may not have been related to the problem.
--
You received this bug not
For nautilus, neither position nor size works for either user or sudo in
the Ubuntu 18.04 release, nautilus package 1:3.26.3-0ubuntu4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543345
Title:
na
Ubuntu 18.04, Firefox 59.02 64 bit has the same problem. Nvidia driver
390.48 in use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730410
Title:
Window full-screen size when Firefox starts
To man
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the
8723bs drivers in the
trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/
trusty-chestersmill public)
These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API
change broke many
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the
8723bs drivers in the
trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/
trusty-chestersmill public)
These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API
change broke many
The fix that worked for me is to add the libnss-resolve package. This changes
the /etc/nsswitch.conf file to actually attempt the dns lookup after the other
conditions have started the UDB fallback mode.
Bug 1727237 had a comment requesting if libnss-resolve were installed, answered
"no", but n
I found the addition of the 18.04 libnss-resolve package fixed my
(intermittent) problems with name-resolution failures. Earlier comments
indicate this package was not installed. The installation alters the
nsswitch.conf file's hosts line to add "resolve [!UNAVAIL=return]"
before "dns".
--
You
This documentation problem still present after two years in 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/1728709
Title:
bash man page has a typo, repeating .bashrc when one should be
/etc/
The wrong behavior is no longer present in Firefox 85.0.1 on the Ubuntu
20.04 system. The Firefox titlebar now changes color with focus as
expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191365
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
$ apt-cache policy firefox
firefox:
Installed: 84.0.2+build1-0ubuntu0.20.04.1
Candidate: 84.0.2+build1-0ubuntu0.20.04.1
Oct 23, on an ubuntu 18.04 system, the Ubuntu 20.10 zsync download
displays the above errors when an https download is attempted. Using
http succeeds.
The failure (local iso is a renamed beta):
$ zsync -i ubuntu-20.10-desktop-amd64.iso
https://releases.ubuntu.com/20.10/ubuntu-20.10-desktop-am
Public bug reported:
Default Gnome desktop, the taskbar touches the desktop icon highlight
square. If the mouse cursor over the icon leaves the icon by moving over
the taskbar, the icon remains highlighted. The highlight remains when
another icon is highlighted or a window activated. Multiple ic
OK reported on
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/193
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870956
Title:
Desktop Icons Remain Highlighted when Mouse Curs
OK reported there and it's bug #193.
** Bug watch added:
gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #193
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/193
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The working 5.4 kernel on Lubuntu 20.04, on Intel compute Stick STCK1A8LFC with
the rtl8723bs hw.
$ cat btm-54.dmesg
Lubuntu 20.04
$ uname -a
Linux xleef 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
Previously connected generic Bluetooth 2.4G mouse
I confirm that Bluetooth now works on the Intel Compute Stick STCK1A8LFC
with the rtl8723bs hardware for the 5.7.0-050700 #202005312130 kernel
from the above link. dmesg showed the expected Bluetooth firmware
loading, and all necessary modules were automatically loaded.
--
You received this bug
The bluetooth firmware load (hci0) below from a working device on a 4.19 kernel
is missing from the
above posted dmesg output (firmware versions identical). There are new
firmware versions in 20.04, so that may be contributing cause to the loading
problem.
7.768840] RTL8723BS: rtl8723bs v4.
Delete the above observation of a later version of the firmware being
available, the
rtl8723bs v4.4.1_17245.20160325_BTCOEX20151223-654a is actually the original
Intel version.
on the Ubuntu 14.04 supplied on the Intel Compute Stick.
--
You received this bug notification because you are a memb
On an Intel Compute Stick the Xubuntu 18.04 upgrade to 20.04 resulted in
a working rtl8723bs bluetooth (and wifi) for a 5.4.0-29 kernel. Before
upgrade, a 5.3 kernel was tested and three additional modules needed to
be loaded manually (the first time) to make the Bluetooth work: hidp,
btbcm, and r
I am having trouble loading the rtl8723bs firmware for a 5.5 kernel on
AntiX 19, (a Debian 10 sans systemd/Gnome). This bug on a 20.04
install with the 5.4 kernel may indicate early issues, but I withdrew my
"does this affect me" checkoff since the 5.4 kernel is working for me.
--
You received
For a fresh install of Ubuntu 18.04 I found that libnss-resolve needed to be
installed to fix various systemd-resolvd errors (with a setup like you
describe, gateway does DHCP for a local net and DNS).
Your case may be different because you seem to have a null domain. My ISP sets
up a line like
** Description changed:
system:Ubuntu 16.04.1 LTS
Linux leno 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
package in use: libc-bin 2.23-0ubuntu3
The ldd script comes with wired in paths for the 64 bit and 32 bit loaders,
but other archite
Altered the patch in the description to explicitly save error status to
handle recent bash changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616609
Title:
ldd reports incorrectly "not a dynami
Still a problem in Ubuntu 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/1726545
Title:
Gparted not working in Wayland Ubuntu
To manage notifications about this bug go to:
https://bugs.launch
Tried the developers/proposed checkoff, but the 239systemd.. package is still
not available. In any case, Ubuntu 18.04 has problems connecting with
smtp.comcast.net (through evolution, recommended port 587).
The error trying to send an email is:
An error occurred while sending, how do you want
Public bug reported:
Several updates of Ubuntu 18.04 worked, but yesterday, the update failed
because of some missing file in libc6_2.27-3ubuntu1_amd64.deb and
libc6_2.27-3ubuntu1_i386.deb
While updating Ubuntu 18.04, the update failed with a failure to find
libzstd.so.1 in the libc6_2.27--3ubunt
On a Lenovo W520, kernel 4.15.0-33, changing the UEFI Settings for the
Security Chip to "disabled" from "ignore" eliminated both this mei-me
error, and the tpm error , both of which were appearing on the black
screen which appeared briefly after a resume.BIOS revision 8BET62WW
(1.42 ), Firmware rev
The upgrade probably ran out of space -- the root is only 5G, so unless
care is taken to update incrementally, you will run out of space. I
have successfully updated three of the STCK1A8LFC Intel Compute Sticks,
and used a micro-SD card to provide additional space for the package
downloads. A USB
The comment on the pin_eld_notify got fixed (sometime before 4.4.0-130),
removing the pipe reference, and enumerating the two valid arguments,
but the actual "pipe" argument was left.
===Partial fix of just comments from 4.4.0-130 packages ===
struct i915_audio_component_audio_ops {
void *
Two weeks of running kernel 4.0.15-23 did not produce the error when
returning from suspend. After the kernel update to 4.0.15-29, the error
appears nearly every return from suspend, much more frequent than with
the 4.0.15-24 kernel. Again, no adverse effects are seen from the
error.
--
You rec
If the Firefox windows is larger than some limit when closed, it will
open in full-screen mode next time it is opened. If smaller than this
limit, the size at close will be used as the size when reopened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
In Ubuntu 18.04, the download section does not expand when the window is
made taller, but fortunately, there is a limit on the minimum window
size so that section does not shrink to one line anymore. After the
download finishes, the installer section acts normally, expanding and
shrinking with the
After the 4.15.0-124 kernel update, I started noticing the mei_me error
messages at the initial startup screen (which usually only had tpm errors),
although othing fails to work.
$ dmesg |fgrep mei
[ 2022.278241] mei_me :00:16.0: hbm: properties response: wrong status = 1
CLIENT_NOT_FOUND
Never had this problem on my fully patched Ubuntu 16.04 until just
recently, when I noticed that the Firefox menus do not display after
restoring from a suspend. gnome-terminal and gedit are OK. Iconizing
Firefox, then restoring, restores the menus to working condition. Same
sorts of errors in
Ubuntu 16.04, Nvidia Quadro 1000m, #14 allow the X server to run, applications
may be launched (xterm, then xclock) and they appear in ps, keyboard input to
the xterm works, but the display is totally black. No errors are in the
~/.local/share/xorg/Xorg.1.log file (a failure does show:
xf86Enab
On another 16.04 machine without Nvidia, comment 14 produced a working
display. The Nvidia driver causing the problem on the first machine was
367.57.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/156
Comment 14 works with Nvidia when using the nouveau driver, but not the Nvidia
driver 367.57 (black screen). Starting an xterm allows you to run other
things, even unity.
Using the nouveau driver, login to vt2 and run:
xinit /usr/bin/xterm -- :1 vt2
Result is a white background xterm, fully
** Summary changed:
- 13.10 USB to USB Install on UEFI Secure Boot Machine Left Host Unbootable
+ USB Install Media to USB Target on UEFI Secure Boot Machine Left Host
Unbootable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
No need to ask where to put grub if there's only one disk, but don't
forget, each disk may have an ESP, and if the installer's target is not
sda, then the question not only needs to be asked, but the installer
should use the provided input. It's another bug that this input is just
ignored.
--
Yo
The bluetooth failure to resume after a suspend seems USB related. The failure
happens
about 50% of the time, and when it does, disabling bluetooth and restarting
fixes
it.
On a Lenovo W520, Ubuntu 16.04, 64 bit, kernel 4.4.0-98-generic, Microsoft
Sculpt
Comfort BT mouse.
Looking at dmesg|tail
On Ubuntu 16.04, uefi secure boot enabled, grub-efi package
2.02~beta2-36ubuntu3.15, the original problem has been fixed, like the
suggestion in the original posting (just use shim) , but now the --no-
uefi-secure-boot switch on grub-install does not cause grubx64.efi to be
used as .../EFI/Boot/boo
Today I saw a fresh install of the original Ubuntu 16.04 successfully
boot Windows 10 on an Asus X200CA, 64 bit (Windows patched to date) with
secure boot enabled. This machine had previously been running 14.04,
and could not boot Windows with secure boot enabled. The other
difference is that the
** Summary changed:
- Ubuntu 13.04 Desktop 64 bit install uses wrong ESP for secure boot laptop
+ Ubuntu Installer uses wrong bootloader location for USB UEFI installs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
The Asus still boots Windows with secure boot enabled with the default
bootloader (/EFI/Boot/bootx64.eri) replaced with a copy of shimx64.efi
(and grubx64.efi present).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
The last update of Ubuntu 16.04 (kernel 4.4.0-36 to 4.4.0-38) reduced
the failure to reconnect of my Microsoft Sculpt Comfort BT mouse from
90% to 15%. Something improved a lot. The fix I have been using was to
pull up the settings/bluetooth, turn off bluetooth (it says on when the
window is star
No, the problem still exists on a Toshiba Satellite S855 UEFI firmware
6.60, with Ubuntu 16.04 fully updated and trying to boot Windows 10 with
secure boot enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Brisbane, Australia is just under Brindisi, Italy. Nibiru is pseudo-
science rubbish, so don't expect to find it in Stellarium, you have to
add it yourself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Description changed:
Downloaded Sept. 20 daily build of 13.10, 64 bit, desktop ISO, md5sum
checked it, used "create startup disk" on 13.04 secure boot host to make
USB live media, rebooted from it, and successfully installed 13.10 to
another USB. Target USB had gpt partitioning, had an
This appears to be a duplicate of 1173457.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379
Title:
installer uses first EFI system partition found even when directed
otherwise
To manage noti
Ubuntu 16.10, plain install on UEFI machine, Nvidia Quadro 1000M running
nouveau driver displays this problem. In addition, when the install is
requested, both the downloads output and the subsequent terminal/text
output are reduced to just one line, regardless of the size of the
window -- resizing
1 - 100 of 243 matches
Mail list logo
