[Bug 1307265] Re: installation hangs if postgres is not listening on default port

[Ubfan]

The Postgresql 9.3 update to Ubuntu 14.04 improperly changed the default
port from 5432 to 5433.

Historically, port 5432 has been the default Postgresql port.  Some update in 
14.04 of Postgresql to 9.3.4-1 apparently decided to use 5433 as the default 
port.  This change breaks things because header files like postgresql.conf have 
the default,5432, wired into them as both strings and numbers, so while psql 
will work on the new default port, existing compiled programs using
ecpg preprocessing fail and recompiling/reinking does not fix the problem 
either (because of the header files with the old default).
(Assuming everything was using the default, when no PGPORT environment variable 
has been explicitly set).

If you are going to change the port default, you have to do a complete
job of altering all the header files, and at least warn users that the
new Postgresql upgrade may require a recompile/relink of existing
programs.

  A workaround to the ecpg programs (and anything else relying on the
headers) is to explicitly set the environment variable PGPORT to 5433,
just as if a non-default port is being used.   The whole point of a
default is that's what you get when you don't specify anything.   A
better workaround is to edit the 5433 back to 5432 in the
postgresql.conf file, and restart.

The suggested fix is to NOT change the default port from 5432  in the
first place.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1307265

Title:
  installation hangs if postgres is not listening on default port

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1307265/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1307265] Re: installation hangs if postgres is not listening on default port

[Ubfan]

** Also affects: postgresql (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1307265

Title:
  installation hangs if postgres is not listening on default port

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1307265/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 46520] Re: Grub installs to wrong drive's MBR in default install. No way to change in standard installer.

[Ubfan]

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 USB partition.  Select the default 
(not advanced)
option and the result of the successful install will boot neither Linux nor 
Windows, with
or without the USB disk attached.

The Cause:
The Grub files are put on the USB /boot/grub, but the Grub bootloader is put 
on the laptop harddisk master boot block.  The menu.lst disk identifications 
are the USB UUID for
the Linux roots and (hd0... for Windows!  Without the USB drive attached, the 
Grub bootloader
cannot find its files, so it fails.  With the USB drive attached, the windows 
disk is wrong in
the menu.lst (It is not hd0, as menu.lst identifies it). Not sure why the 
Ubuntu boots fail,
unless since there is no bootloader on the USB disk, the disk is not even seen, 
and the UUID
is not found. 

Workarounds:  
  1) Windows boot works (only with USB attached) when you change the boot order 
to hard-disk first, then
the Grub hd0 is accurate for the Windows sections.  I thought I tried editing 
menu.lst, changing the hd0 to hd1
for the windows sections, and even trying to map (hd0) (hd1) ...  all failed 
(before fixing the USB boot, then just
changing the hd0 to hd1 worked).
  2) Linux boot may be fixed by booting the CD-ROM, and doing the Grub install 
again to the 
USB disk (needed the --recheck and the explicit root-directory flag to get 
beyond the disk not
 supported by bios complaint).  Then replace the menu.lst file, which 
disappeared! (I had a backup called menu.lst~).
  3) To use the laptop without the USB disk, either:
a) Restore the MBR with the Windows Recovery Console's FIXMBR (good luck, 
finding the Recovery Console is the hard part!).
b) Find a (Windows) fdisk on a bootable media, and fdisk /mbr
c) Do a complete Grub install to a FAT partition (like the recovery 
partition found on many laptops these days).  I
   finally did this, since I have messed up a system before looking for the 
Recovery Console on the
   vendor supplied recovery disks.

Other (hopefully) irrelevant details:
 * AMD cpu laptop, NTFS primary partition, FAT recovery partition
 * MAXTOR 200G USB disk, 9 partitions, first partition 50G for the Ubuntu 
install, preformatted ext2. No swap. No boot.
 * Before repair, Grub console found the /ntldr on (hd1,1), but nothing was 
found  on hd0 (?).  
 * Visible devices were fd1-fd7, hd0 and hd1.  I thought the 7 floppy disks 
were probably the  misidentified usb disk partitions.
 * kernel is whatever the 8.10 live cd installs

-- 
Grub installs to wrong drive's MBR in default install. No way to change in 
standard installer.
https://bugs.launchpad.net/bugs/46520
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 46520] Re: Grub installs to wrong drive's MBR in default install. No way to change in standard installer.

[Ubfan]

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 and look, sorry.  I'm all set up and running the
way I wanted, now, thanks.

-- 
Grub installs to wrong drive's MBR in default install. No way to change in 
standard installer.
https://bugs.launchpad.net/bugs/46520
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414996] Re: [karmic] grub re-writes boot sector on wrong drive on fresh install

[Ubfan]

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/sdb).
I retyped the correct device (/dev/sdb) and avoided wiping out the Windows
mbr (which was on /dev/sda, and which the device.map was mapping to hd0).

Regardless of the install media (usb stick or CDROM), grub-install gets all
the devices wrong in device.map (in this situation).
As a result of the device.map file mapping the Windows sda to hd0, every
device mentioned in the grub.cfg (or menu.lst) is wrong too, even when the
mbr goes to the right location.  The boots only work  because of the use of
UUIDs.  To fix the grub.cfg file, correct the device.map, and rerun update-grub.
e.g. Make hd0 the actual boot device (/dev/sdb), and put the windows /dev/sda 
on hd1,

if you want to allow the usb stick to boot windows when used on another 
computer,
edit the grub.cfg to remove the UUID lines for the windows menu items.

See bugs 45989, 46520, and 384633 for some history of using the wrong   
   
device for the mbr.

-- 
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

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 writes to flash, which has a limited number of 
write cycles.  From the docs, it looked like ramfs would be better for this 
than tmpfs (I have no swap either), but since I can successfully run 
update-manager with the tmpfs, this fix should be low priority.

-- 
update-manager cannot find space on /tmp ramdisk
https://bugs.launchpad.net/bugs/495131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] [NEW] update-manager cannot find space on /tmp ramdisk

[Ubfan]

Public bug reported:

Binary package hint: update-manager

 In 32 Bit Karmic Koala (9.10), running off a 4G usb stick, when
mounting a 256M ramdisk for /tmp from fstab, update-manager claims
not enough space is available on /tmp.  The /tmp  ramdisk works fine,
able to hold a 70M zip and unpack it, and there is lots  of space
left on /.  Note that a 64 bit Karmic on a 4G stick with an 
identical ramdisk, update-manager works fine.  However, even on the
64 bit version, df shows 0 avail for /tmp.

Update-manager can download the package information, but fails to
download any actual packages.  The first time update-manager was run,
11 packages of 5.2M found, soon after, 12 packages of 5.3 meg were
found.  Not sure if the 5.234k changed when 12 packages found.  No
later changes of the 5.234 were seen, regardless of the size of the
download (larger or smaller).

Example:
 Update Manager finds 12 packages needing 5.3m, but selecting the
Install button leads to a popup error window:
Not Enough Free Disk Space
The upgrade needs a total of 5,243k free space on disk '/tmp'. Please free at
least an additional 5,243k of disk space on '/tmp'. Empty your trash and
remove temporary packages of former installations using 'sudo apt-get clean'.

Removal of the /tmp line in /etc/fstab, reboot, and update-manager
works fine. Restore the /tmp line in fstab, (wait a bit) and next
time two packages sized 1.2M are avail, the original error window
complaining of needing 5.234k reappears.  Even later, when the
packages to download total 39.9M, the message remains the same --
5,234k needed.  This bug may be related to 285096.  Firefox has no
trouble downloading files.  Cannot find any other program having
problems, even the Synaptic Package Manager works fine.
df -a output is all zeros for /tmp, even on the 64 bit system
which seems to have no problems with update-manager.

The below system info is from the time when update-manager
finds 12 packages.

System info:
Presario V3000
 AMD Turion 64, 2G mem, an ext2 filesystem on a 4G usb stick for
root, no swap, no proprietary drivers in use.  Karmic 9.10, both
32 and 64 bit versions, patched to date 12/8/2009.

The line in /etc/fstab creating the /tmp ramdisk:
$ fgrep ramfs /etc/fstab
ramfs   /tmpramfs   size=256M,mode=1777 0   0

mount shows the /tmp ramdisk.
$ mount
/dev/sdb1 on / type ext2 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
ramfs on /tmp type ramfs (rw,size=256M,mode=1777)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/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.
$ df -a
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sdb1  3850176   2897432757160  80% /
proc 0 0 0   -  /proc
none 0 0 0   -  /sys
none 0 0 0   -  /sys/fs/fuse/connections
none 0 0 0   -  /sys/kernel/debug
none 0 0 0   -  /sys/kernel/security
udev998080   260997820   1% /dev
none 0 0 0   -  /dev/pts
none998080   388997692   1% /dev/shm
ramfs0 0 0   -  /tmp
none998080   196997884   1% /var/run
none998080 4998076   1% /var/lock
none998080 0998080   0% /lib/init/rw
binfmt_misc  0 0 0   -  /proc/sys/fs/binfmt_misc
gvfs-fuse-daemon 0 0 0   -  /home/ubfan/.gvfs


$ free
 total   used   free sharedbuffers cached
Mem:   1996160 4734001522760  0  57740 240276
-/+ buffers/cache: 1753841820776
Swap:0  0  0


cd /proc/self
$ cat mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev tmpfs rw,relatime,mode=755 0 0
/dev/disk/by-uuid/0c9a28f4-ff16-433f-95c2-dca95354146b / ext2 
rw,noatime,errors=remount-ro 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

** 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-manager cannot find space on /tmp ramdisk
https://bugs.launchpad.net/bugs/495131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

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 device.map file to make hd0 the actual root
device, and rerun update-grub.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

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), and the /tmp directory, with the
same 5.234M additional space needed.  Removing the ...archives
ramdisk removed the associated error message, but the /tmp message
presisted, just like on the 32 bit Karmic system.  Removing the /tmp
ramdisk allowed the update to proceed normally.  All updates
were attempted via the System/Administration/Update Manager
menu entry.

-- 
update-manager cannot find space on /tmp ramdisk
https://bugs.launchpad.net/bugs/495131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 367766] Re: live USB disk not bootable

[Ubfan]

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 entered for a kernel will be found to boot.  From Jaunty (32 or
64), the usb creator will succeed in creating a live Jaunty (32 or 64)
usb stick.  All usb creations which succeeded were using the default (no
explicit iso given).  It would be nice to fix the Intrepid creator
command to successfully use a Jaunty iso.  Currently, I still have to
burn a live CD-ROM of a new system to create the live usb startup disk.

-- 
live USB disk not bootable
https://bugs.launchpad.net/bugs/367766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] [NEW] Grub Installer gets devices wrong when running from live USB

[Ubfan]

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. The grub menu.lst for the
current Jaunty install is UUID based and boots successfully.  All  
other boot paragraphs (Windows and Linux) fail to boot because they  
refer to wrong devices.  All the other Linux installations on the usb
disk incorrectly refer to hd1 instead of the correct hd0.  The
windows paragraph refers to hd0 (and lacks map commands), instead of
the correct map (hd0) (hd1), map (hd1) (hd0), rootnoverify (hd1,0).

The device.map claims hd0 is /dev/sda, which is also wrong, but makes
no difference after the menu.lst is corrected.

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 729045] Re: [needs-packaging] fltk-1.3.0

[Ubfan]

Ubuntu 11.10 does have some fltk13 packages now.  The ...-dev package
was fine, but the fltk13 package itself seems useless since it does not
have the (four I needed) libfltk... libraries.  The workaround is to add
links to /usr/lib pointing to the necessary libraries in the tarball
download.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729045

Title:
  [needs-packaging] fltk-1.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/729045/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 816062] Re: When opening up FireFox 5 screen goes white

[Ubfan]

I sometimes see a white screen in firefox when running 11.04, but only
with the Unity interface, not the classical.  The whiteness is size
dependent, it comes and goes as the screen is resized (showing the
normal web page when not present).  The resizing may be done with the
corner resizer or by moving the window to the left to get a half screen.
This occurred at the fresh install of Natty, and basically made it
unusable for me.  Since the installation is on a 4G usb stick which
moves between machines, driver confusion may be an issue.  The old
laptop has Nvidia chips, but the Natty is not set to use them and Unity
does not run.  The netbook does not have Nvidia.  At some point, the 2D
Unity was installed, and now I cannot seem to select a Unity interface
on the Netbook (which used to run Unity by default).  I do not recall
seeing the problem with the 2D Unity interface

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816062

Title:
  When opening up FireFox 5 screen goes white

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/816062/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 876734] Re: gnome-terminal scroll position indicator invisible when left scroll is selected

[Ubfan]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876734

Title:
  gnome-terminal scroll position indicator invisible when left scroll is
  selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 876734] [NEW] gnome-terminal scroll position indicator invisible when left scroll is selected

[Ubfan]

Public bug reported:

Under Unity and Unity-2D, selecting left scroll for a gnome-terminal
scroll bar position results in the little red bar, indicating where the
scroll elevator will appear , being invisible, making it difficult to
find, since random clicks must be applied along the left window border
to make the scroll elevator appear.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-terminal 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Mon Oct 17 11:22:25 2011
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 oneiric running-unity

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876734

Title:
  gnome-terminal scroll position indicator invisible when left scroll is
  selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 762203] Re: Computer is not turned off at shutdown

[Ubfan]

After upgrading to kernel 2.6.38-11-generic, shutdown now completes properly on 
my MSI 135 laptop running 11.04 off a 4G usb stick.
An 8G stick with 10.10 will shutdown with a dirty filesystem 25% of the time.  
Never had problems with 10.10 on 4G sticks, so maybe the speed of the root 
media is an issue.  The 8G usb light blinks right up to the fraction of a 
second that power is cut, so maybe a buffer is not getting fully written out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762203

Title:
  Computer is not turned off at shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/762203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 706795] Re: [All releases] Suspend/Resume with rootfs on USB, causes filesystem corruptions and kernel panic on mount attempt, leaving system unbootable with data lost.

[Ubfan]

I started seeing disk checks at boot time 25% of the time on a new 8G
USB Maverick installation, currently running kernel 2.6.35.30.  I
noticed that at shutdown, the usb light blinks right up to the fraction
of a second that power is cut to the laptop, so I assumed that some
fileysystem buffer had not been fully flushed.  On an older 4G USB
Maverick, there is a noticeable time between when the usb light stops
blinking and when the power to the laptop is turned off.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706795

Title:
  [All releases] Suspend/Resume with rootfs on USB, causes filesystem
  corruptions and kernel panic on mount attempt, leaving system
  unbootable with data lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 876734] Re: gnome-terminal scroll position indicator invisible when left scroll is selected

[Ubfan]

This bug also affects Ubuntu 12.04 beta 2.
With all the other window controls on the left by default, the left-scrollbar 
should not be that unusual a choice. Since finding the left scrollbar is so 
difficult (scroll length is set to 2048, so the invisible red indicator is 
pretty small), a workaround is to simply suppress the new scroll bar, and fall 
back to the old one. which is always visible.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876734

Title:
  gnome-terminal scroll position indicator invisible when left scroll is
  selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

I just confirmed that this is still a problem in 10.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495131

Title:
  update-manager cannot find space on /tmp ramdisk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/495131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

This is still an issue with 10.04 and 11.04.  Probably 10.10 too, but I'll have 
to wait until some more updates are available to test.
Suggested fix:
Use the size= option in the fstab line, which the mount command will report.
Use the amount of free space in ram.
Use the needed download size.
Figure out some amount of ram not to use to keep the system running, and
if the device free space comes back zero (which is what the system function 
reports for ramfs devices),
calculate using the above to see if there is really enough space.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495131

Title:
  update-manager cannot find space on /tmp ramdisk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/495131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495131] Re: update-manager cannot find space on /tmp ramdisk

[Ubfan]

Edit your /etc/fstab to add a line putting /tmp into a ramfs device. See the 
below excerpt of fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# file system mount point   type  options   dump  pass
proc/proc   procnodev,noexec,nosuid 0   0

# update-manager cannot see any space in /tmp when ramfs used
ramfs   /tmpramfs   size=256M,mode=1777 0   0
---snip--

Reboot, and /tmp will be in a mounted ramdisk.  The size=256M is unused, but 
will be reported by mount.
Most things will run fine if you really do have free ram, but update-manager 
will die with insufficient space errors
for any size (greater than zero) update.

Change the two ramfss in the line to tmpfs, and things work with
update-manager.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495131

Title:
  update-manager cannot find space on /tmp ramdisk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/495131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 879120] [NEW] 11.10 shutdown delay of 1 min when using the open source Broadcom firmware

[Ubfan]

Public bug reported:

The Broadcom 4311/12 wireless chips require firmware when using the b43 driver.
This firmware is available from Broadcom (which is put into /lib/firmware/b43)
or as open source (which is put into /lib/firmware/b43-open).  Either firmware
works, but when the proprietary Broadcom firmware is not present in .../b43,
shutdown takes an extra minute, after the log file line could not find
.../b43/ucode5.fw.  After a minute, shutdown completes normally.
Adding in the Broadcom firmware lets shutdown proceed without the minute
delay.  This behavior is new with the 11.10 release.

Note the below udev items from /var/log/udev are probably the cause of this
problem. 
...
KERNEL[18.445953] remove   /devices/pci:00/:00:02.0/:01:00.0/ssb0:0$
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/pci:00/:00:02.0/:01:00.0/ssb0:0/firmware/ssb0:0
SUBSYSTEM=firmware
FIRMWARE=b43/ucode5.fw
TIMEOUT=60
ASYNC=0
SEQNUM=1822
.
and many other FIRMWARE=b43/...fw  paragraphs

** Affects: b43-fwcutter (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubuntu = b43-fwcutter (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879120

Title:
  11.10 shutdown delay of 1 min when using the open source Broadcom
  firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/879120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 879120] Re: 11.10 shutdown delay of 1 min when using the open source Broadcom firmware

[Ubfan]

The open source firmware is available in packages firmware-b43-installer
and firmware-b43-lpphy-installer.  It is not certain that the system
with the problem had used those packages, however.  The firmware may
have been compiled directly, or copied from another system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879120

Title:
  11.10 shutdown delay of 1 min when using the open source Broadcom
  firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/879120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 762203] Re: Computer is not turned off at shutdown

[Ubfan]

Further testing with a fresh Maverick install to an 8G stick and
updated, displayed the improper shutdown problem -- it's as if the usb
gets turned off before the filesystem is dismounted, leaving it dirty
and in need of checking next boot.  Looks like Lucid is the last release
that worked properly on the MSI 135 netbook.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762203

Title:
  Computer is not turned off at shutdown

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 762203] Re: Computer is not turned off at shutdown

[Ubfan]

Running off a 4G usb stick, I get a hang at shutdown (Checking for
unattended upgrades) on an MSI 135 (Micro Star International) netbook,
but not on an Compaq Presario V3000 laptop.  First time I have seen such
a problem, going back to Jaunty.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762203

Title:
  Computer is not turned off at shutdown

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

This problem goes back to grub1, and grub 2 did not fix it entirely.  UUIDs 
helped, but they are not used for every disk reference.  I use the normal 
desktop gui install, from a 2G live usb, to a 4G usb target on a standard 
Windows laptop,  The created grub.cfg still has wrong device references for 
things like root=(hd2   instead of hd1 even though the UUID is used on the 
kernel line -- so it does not boot. At the first target reboot after 
installation, I edit the boot command to reduce the hd2 to hd1, and after 
successful boot, run update-grub to get the whole grub.cfg fixed.
   UUIDs are NOT used 100% of the time, Within the last 24 hrs, a Maverick 
install from a Maverick created live usb to a 4G pqi smart stick created 
fstab with /dev/sdc as /.  (how can this even boot?)  The grub.cfg file had the 
hd2 to hd1 edit to boot, and the kernel line did have the UUID.
  My first Maverick install was from a Lucid created live usb to a 4G hp 
(older) stick, and had to do the F6 ... text install.  This created an fstab 
with a UUID, but the grub.cfg had /sdc on the kernel line, as well as the usual 
wrong hd2 references.  Maybe this install was an odd ball given the manual 
intervention necessary to get the install to work.
  The cause is obvious, grub2 writes its first install configuration with all 
the devices, including the install media, which is not going to be present at 
the first reboot.  hd0 is windows on the hard disk, hd1 is the usb install 
media, and hd2 is the target.  Remove the install media, and hd0 is still 
windows, but hd2 does not exist, since the target is now hd1. I haven't been 
saving bad grob.cfg files for awhile, but I could do another install and grab 
one.  As I recall, there were comments about the devices that were also 
referring to the sdc device for the linux boot paragraphs.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608508] Re: usb stick will not stay unmounted with safely remove

[Ubfan]

Maverick remounts the Safely removed usb device before it can be pulled out 
( 1/2 sec)
at the first remove.  The second remove attempt works properly on the usb
device.
Fully patched 32 bit Maverick to 20-Oct-2010, Running
Linux Maverick 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 
i686 GNU/Linux
HP Presario V3000 laptop, running root off another USB device (not the one 
removed).

[  119.929129] sd 6:0:0:0: [sdd] Write Protect is off
[  119.929139] sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
[  119.929147] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[  119.932144] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[  119.932172]  sdd: sdd1
[  120.732564] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[  120.732582] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[  490.756726] WARNING! power/level is deprecated; use power/control instead
[  490.908311] usb 1-5: USB disconnect, address 5
[  491.368076] usb 2-5: new full speed USB device using ohci_hcd and address 3
[  491.568933] usb 2-5: not running at top speed; connect to a high speed hub
[  491.590373] scsi7 : usb-storage 2-5:1.0
[  492.594000] scsi 7:0:0:0: Direct-Access JetFlash Transcend 2GB8.07 
PQ: 0 ANSI: 2
[  492.595467] sd 7:0:0:0: Attached scsi generic sg3 type 0
[  492.608970] sd 7:0:0:0: [sdd] 398 512-byte logical blocks: (2.01 GB/1.88 
GiB)
[  492.612957] sd 7:0:0:0: [sdd] Write Protect is off
[  492.612966] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00
[  492.612974] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[  492.630955] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[  492.630981]  sdd: sdd1
[  493.622995] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[  493.623013] sd 7:0:0:0: [sdd] Attached SCSI removable disk
[  506.676069] usb 2-5: USB disconnect, address 3

I waited 5 seconds and pulled out the stick.
I haven't waited longer to see if it eventually remounts.

-- 
usb stick will not stay unmounted with safely remove
https://bugs.launchpad.net/bugs/608508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 655111] Re: BCM4312 not supported by Additional drivers. B43 is proposed, fails w/o useful message, Not supported low-power chip

[Ubfan]

Has anyone tried the b43-open firmware with this LP chip?  
http://wireless.kernel.org/en/users/Drivers/b43 claims it's partially supported:

14e4:4315partially supported 2.6.33 and later (PIO mode)BCM4312
b/gLP  b43/wl

I just copy in a b43-open directory to /lib/firmware with the 3 files in it and 
my 14e4:4312 wireless works with the b43 driver.
I don't enable any additional hardware drivers for Broadcom.

-- 
BCM4312 not supported by Additional drivers. B43 is proposed, fails w/o 
useful message, Not supported low-power chip
https://bugs.launchpad.net/bugs/655111
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

Maverick usb install media, whether created from Lucid or Maverick will still   
create a non-booting target usb device (thumbdrive or usb hdd) because the
wrong device (sdc instead of sdb) is used.  To recap, at install time, the 
Windows internal hard disk gets sda, the boot media gets sdb, and the target
usb gets sdc.  The grub paragraphs all are written to the target with these
device assignments, even though it is certain that the boot media will not be
present when you boot the target.  Using a CDROM install media avoids this   
problem since the drive is not given an interferring sdx device.  The usual
fix is necessary:  At target boot, edit the grub paragraph to reduce the 
device  references by one (hd2 - hd1, and sdc - sdb), for the first boot,
then after a successful boot, immediately sudo update-grub.  Without the boot  
media, the devices will be correct for the next reboot.  fstab uses UUID, so is 
ok.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 70317] Re: constant kernel errors about unknown multimedia keys

[Ubfan]

Running Maverick
Linux Maverick 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 
i686 GNU/Linux
on an Compaq Presario v3000 lsptop, I saw this message in my dmesg output:
[   12.793811] ppdev: user-space parallel port driver
[   34.742043] atkbd serio0: Unknown key pressed (translated set 2, code 0xd9 
on isa0060/serio0).
[   34.742049] atkbd serio0: Use 'setkeycodes e059 keycode' to make it known.
[   34.742716] atkbd serio0: Unknown key released (translated set 2, code 0xd9 
on isa0060/serio0).
[   34.742719] atkbd serio0: Use 'setkeycodes e059 keycode' to make it known.
[   63.928333] wlan0: authenticate with 00:0c:41:81:ce:9f (try 1)
[   63.943628] wlan0: authenticated
..
The message appeared once, and I have been running Maverick a couple of days 
without noticing
any problems.

-- 
constant kernel errors about unknown multimedia keys
https://bugs.launchpad.net/bugs/70317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

Certainly not the case with me.  The root=/dev/sdc1 on the linux line overrides 
whatever the search UUID did.  I just did a fresh install from a 2G usb stick 
created on a Maverick system with the normal desktop iso, to a 4G new pqi 
stick.  I captured the grub.cfg (bad), fstab (OK), and the /var/log files in 
case you needed them.  The first boot attempt fell into BusyBox after about a 
minute with the following error:
Gave up waiting for  root device.  Common problems:
-Boot args (cat /proc/cmdline)
  -check rootdelay= (did the system wait long enough?)
  -check root= (did the system wait for the right device?)   NO IT DIDN'T
-Missing modules (cat /proc/modules; ls /dev
ALERT! /dev/sdc1 does not exist - Dropping to a shell
BusyBox v1.15.3 (ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs)_

cat /proc/cmdline gives:
BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro quiet splash

The modules were:
usb_storage firewire_ohci, firesire_core, pata_amd, forcedeth, sdhci_pci, 
ac_itu_t, sdhci, sata_nv, led_class, ssb

The /dev directory contained sg0, sda, sda1, sda2, sda3 (the Windows disk), 
sg1, sdb, sdb1 (the 4G stick failing to boot)
and no sdc.

I select manual partition selection, select the sdc1, format an ext2 fs,
no swap, the grub boot goes to the 4G stick on sdc (default after I
select the sdc disk).  The only disks shown are sda( the windows disk),
and sdc(the target).  sdb is the 2G install usb, and correctly is not a
choice.

The original grub.cfg file created on the target, before any boot attempt is:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env 
recordfail; fi; fi
}

function load_video {
  insmod vbe
  insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class 
gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro   quiet splash
initrd  /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu 
--class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
echo'Loading Linux 2.6.35-22-generic ...'
linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro single 
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
linux16 /boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry Microsoft Windows XP Professional (on /dev/sda1) {
insmod part_msdos
insmod ntfs#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d 

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

I do agree that if the UUID is used on the linux line, the set root= line to 
the wrong hd2 will not stop the boot.
I have just done 4 quick Maverick USB installs, and I think I recall that not 
all have had the sdc1 on the linux line.  The install to a USB hard disk seemed 
to only have the set root=(hd2 problem, which I automatically corrected at 
first boot.  I don't plan on doing another USB/hdd install any time soon, but 
if you need me to, I will reinstall it to see exactly what happens.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

No, I have never edited any default files to produce the sdc on the
linux line.  The problem is created by a pretty standard install, just
doing a manual partition because I am afraid if I answer yes to use the
whole disk the windows internal disk would be wiped out.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

I found the original grub.cfg file from a USB hard disk install.  It does use 
UUIDs on the linux line, just the hdx references are wrong.  This probably 
would have booted Maverick successfully, but maybe not Windows, which does the 
search with UUID, but used the bad hd1 for the drvemap.  The fstab file also 
used UUID for the root and swap, just having the leftover comments about the 
devices being on /dev/sdcx at install (comments which no longer appear in the 
grub.cfg file).
grub.cfg from a maverick created 2G USB installer to a USB hard disk target -- 
only hx? references are wrong but may still boot linux.but probably not Windows:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env 
recordfail; fi; fi
}

function load_video {
  insmod vbe
  insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class 
gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
linux   /boot/vmlinuz-2.6.35-22-generic 
root=UUID=158ce293-1d71-4883-b2e9-8a0d5dfc0170 ro   quiet splash
initrd  /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu 
--class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
echo'Loading Linux 2.6.35-22-generic ...'
linux   /boot/vmlinuz-2.6.35-22-generic 
root=UUID=158ce293-1d71-4883-b2e9-8a0d5dfc0170 ro single 
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
linux16 /boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 158ce293-1d71-4883-b2e9-8a0d5dfc0170
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry Microsoft Windows XP Professional (on /dev/sdb1) {
insmod part_msdos
insmod ntfs
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set 637d775958635993
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry Windows NT/2000/XP (on /dev/sdb2) {
insmod part_msdos
insmod fat
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set 3ec6-2e70
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry Microsoft Windows XP Embedded (on /dev/sdb3) {
insmod part_msdos
insmod ntfs
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set 60d45d0ed45ce834
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry Ubuntu, with Linux 2.6.32-25-generic (on /dev/sdc2) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos2)'
search --no-floppy --fs-uuid --set d3a61730-532b-4d7d-a87a-df9ce2b1f325
linux /boot/vmlinuz-2.6.32-25-generic 
root=UUID=d3a61730-532b-4d7d-a87a-df9ce2b1f325 ro quiet splash
initrd 

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

 We both agree the second grub file will boot linux.  I doubt it will boot 
windows, but don't care.
Look at the LINUX line from first grub.cfg file from a 4G stick install, four 
lines cut out below:

set root='(hd2,msdos1)'
 search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af
 echo 'Loading Linux 2.6.35-22-generic ...'
 linux /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro single

It's the root=/dev/sdc1 part which makes boot fail, EVERY TIME.  Surely
you will admit that this overrides the search UUID business?

I do nothing to cause the device to be used instead of the UUID.

Installs to 4G sticks seem to get the device and will not boot without editing 
the grub commands.
Installs to a USB hard disk seem to get the UUID and will work for the first 
linux boot.

After so many bad installs to non-booting sticks, I tend to edit the
grub commands at first boot and fix the obvious wrong items, and not to
even try to see if the boot works.  In addressing this bug, it is of
interest that the problem is not consistently a problem with USB
installs, since the USB hard disks will actually boot.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

Yes, I can recreate it.
I'll run a couple of Maverick installs tonight to some 4G sticks.
I'll use a Maverick created installer, and capture the grub.cfg, and fstab.
If I can, I'll grab the log files off the install media too.

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

Recreated the problem of the sdc appearing on the linux lines in grub.cfg on an 
install to a 4G Patriot xmini usb stick.
fstab was OK with the UUID used for /, sdc1 only appearing in a comment.
I did copy the /var/log files off the install media in case they might be of 
interest.
Install sequence of events:
Booted the Maverick install media, at the Try/Install screen, i inserted 
the target 4G usb.
I was Not connected to the internet, and did not check off third party sw.
Selected Specify partitions manually instead of use whole disk.
(I had previously taken the new 4G stick, and made one partition, starting at 
sector 8192, with h=4 and s/t=16.)
Selected sdc1, then the change button.
use as ext2, format, /  selected
Boot loader automatically switched to the 4G stick on sdc from the windows sda 
disk.
selected install now
selected continue on the no swap warning
Set time zone to LA
selected USA keyboard
Filled out the name, user, etc, require pw to boot.
When install finished, I switched to a virtual terminal, and tared up the 
/var/log files.
unmounted the target. Rebooted to my normal linux environment (on a 4G stick), 
and copied off the grub.cfg and fstab from the just created target usb.

This result is the same as the previous install to a 4G PQI usb stick,
which did not boot because of the sdc1 on the linux line.

The bad grub.cfg file with the sdc on the linux lines:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env 
recordfail; fi; fi
}

function load_video {
  insmod vbe
  insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class 
gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro   quiet splash
initrd  /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu 
--class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
echo'Loading Linux 2.6.35-22-generic ...'
linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro single 
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
linux16 /boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set 27731a50-39e4-41ad-92e8-52048248792a
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry Microsoft Windows XP Professional (on /dev/sda1) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 637d775958635993
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry Windows NT/2000/XP (on /dev/sda2) {
insmod part_msdos
insmod fat
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid 

[Bug 631494] Re: [Maverick béta ] Invisib le mouse

[Ubfan]

Sometimes after the screensaver, the mouse pointer becomes invisible on
a current to 11/6 Maverick 10.10 system. I am running the Nvidia
graphics 6150, without the proprietary drivers. I don't recall seeing
this problem in any earlier release. The hardware did not have problems
with the 10.04 black screen of death. Going to a virtual terminal and
returning did not restore the pointer. I usually just reboot.

-- 
[Maverick béta ] Invisible mouse
https://bugs.launchpad.net/bugs/631494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 615938] Re: mousepointer invisible, but seems to be there

[Ubfan]

Sometimes after the screensaver, the mouse pointer becomes invisible on
a current to 11/6 Maverick 10.10 system.  I am running the Nvidia
graphics 6150, without the proprietary drivers.  I don't recall seeing
this problem in any earlier release.  The hardware did not have problems
with the 10.04 black screen of death.  Going to a virtual terminal and
returning did not restore the pointer.  I usually just reboot.

-- 
mousepointer invisible, but seems to be there
https://bugs.launchpad.net/bugs/615938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

Correct.
It just occurred to me that a significant difference between the two installs 
is that the usb flash sticks only have one partition.  I have always had at 
least two partitions on a hard disk (one for swap, plus the install partition, 
plus any others).

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

grub edited just the sdc to sdb to boot, no other changes made.
Copied fstab and grub.cfg to desktop
sudo update-grub
The fstab was unchanged (OK), and the grub.cfg had the UUIDs used instead of 
the sdc devices, and the hd2 s were changed to hd1 s., correcting all the 
problems.
diff below from the above grub.cfg file:

$ ls
fstab  fstab-orig  grub.cfg  grub-orig.cfg

$ diff grub*
41c41
 set root='(hd1,msdos1)'
---
 set root='(hd2,msdos1)'
51c51
 set root='(hd1,msdos1)'
---
 set root='(hd2,msdos1)'
73c73
   set root='(hd1,msdos1)'
---
   set root='(hd2,msdos1)'
75c75
   linux   /boot/vmlinuz-2.6.35-22-generic 
root=UUID=27731a50-39e4-41ad-92e8-52048248792a ro   quiet splash
---
   linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro   quiet splash
82c82
   set root='(hd1,msdos1)'
---
   set root='(hd2,msdos1)'
85c85
   linux   /boot/vmlinuz-2.6.35-22-generic 
root=UUID=27731a50-39e4-41ad-92e8-52048248792a ro single 
---
   linux   /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro single 
98c98
   set root='(hd1,msdos1)'
---
   set root='(hd2,msdos1)'
105c105
   set root='(hd1,msdos1)'
---
   set root='(hd2,msdos1)'

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608508] Re: usb stick will not stay unmounted with safely remove

[Ubfan]

The remount does not occur until after the first time update-manager is
run on a new Maverick install.

-- 
usb stick will not stay unmounted with safely remove
https://bugs.launchpad.net/bugs/608508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 615938] Re: mousepointer invisible, but seems to be there

[Ubfan]

Problem solved by using the Nvidia drivers.  I would prefer to use the
open drivers however, since I boot off a USB thumbdrive, and now I
cannot successfully boot on a machine without Nvidia chips.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615938

Title:
  mousepointer invisible, but seems to be there

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 156477] Re: Installer fails if windows on another partition is hibernated

[Ubfan]

The Maverick installer was a 2G SD card, created on a fully patched
Lucid system on Nov 15, 2010.  The workaround to the error was to type
F6 early on, which seemed to skip some checking and got me to the
language selection screen, from which I installed Maverick to a 4G
stick.  The error was consistent.  If I let the install run without
keyboard entry, it would always hang at the error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/156477

Title:
  Installer fails if windows on another partition is hibernated

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 156477] Re: Installer fails if windows on another partition is hibernated

[Ubfan]

The Maverick (10.10) live usb media (32 bit desktop)  displayed this
problem, refusing to get past a hibernated embedded windows which did
not affect previous installations back to Intrepid.  I believe the
hibernated Windows partition was for a quick start of media player for
DVDs or CDs but has never been used to my knowledge.  The installer
stalled on the Ubuntu screen with the colored dots.  Typing ESC got to
the underlying error screen.

The (manually copied) error was:
Windows is hibernated, refused to mount.
Failed to mount /dev/sda3: Operation not permitted.
The NTFS partition is hibernated. Please resume and shutdown Windows properly,
or mount the volume read-only with the 'ro' mount options, or mount the volume
read-write with the 'remove_hiberfile' mount option.
For example type on the command line:
  mount -t ntfs-3g -o remove_hiberfile /dev/sda3 /cdrom

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/156477

Title:
  Installer fails if windows on another partition is hibernated

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 712292] [NEW] update-manager progress bar windows for download and applying changes sometimes do not appear.

[Ubfan]

Public bug reported:

Binary package hint: update-manager

Ubuntu 10.10 update-manager can get into a state which will not show theUbuntu 
10.10 update-manager can get into a state which will not show the progress 
windows for downloading, or for applying changes.  The update completes and is  
normal otherwise.  This state will presist across reboots.  Running 
update-manager from a termninal with sudo will always
make the progress windows appear, and then the next gui invocation of 
update-manager will have the progress windows, but the next login/reboot, the 
windows may be absent from the gui again.  The check button from the sudo 
invocation is enough to fix the problem for the next gui invocation.

I believe, but am not sure the initial problem was caused by invoking
update-manager from a non-sudo user (even just to check, since the
installation could not work).  I had two identical thumbdrives, with
nothing but updates applied to the default applications, one had the
problem,  and the other did not.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.22
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Feb  2 22:30:58 2011
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 maverick

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712292

Title:
  update-manager progress bar windows for download and applying changes
  sometimes do not appear.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 712292] Re: update-manager progress bar windows for download and applying changes sometimes do not appear.

[Ubfan]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712292

Title:
  update-manager progress bar windows for download and applying changes
  sometimes do not appear.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 510318] Re: Ubuntu - Linux for Human Beings! (About Ubuntu) page contains encoding error

[Ubfan]

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
 2)line 46 col 62 invalid character
 4)line 46 col 63 invalid character   

The page appears to be complete, but the navigation box at the bottom
(previous..., next...) is missing.

There is no nav box on the first page either, Ubuntu -- Linux for Human
Beings either.

-- 
Ubuntu - Linux for Human Beings! (About Ubuntu) page contains encoding error
https://bugs.launchpad.net/bugs/510318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] [NEW] apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

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 `apt-cache pkgnames |fgrep 32-10`
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libnunit2.4-cil libappindicator0-cil libmono-system-runtime2.0-cil
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  linux-headers-2.6.32-10* linux-headers-2.6.32-10-generic* 
linux-image-2.6.32-10-generic*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 207MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 155387 files and directories currently installed.)
Removing linux-headers-2.6.32-10-generic ...
Removing linux-headers-2.6.32-10 ...
Removing linux-image-2.6.32-10-generic ...
Running postrm hook script /usr/sbin/update-grub.
snip...

Found initrd image: /boot/initrd.img-2.6.32-11-generic
Found memtest86+ image: /boot/memtest86+.bin
done
dpkg: warning: while removing linux-image-2.6.32-10-generic, directory 
'/lib/modules/2.6.32-10-generic' not empty so not removed.
Segmentation fault (core dumped)

$ ls /lib/modules/*10*
modules.builtin.bin

ProblemType: Crash
Architecture: amd64
Date: Wed Feb 10 16:01:30 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/apt-get
Package: apt 0.7.25ubuntu4
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: apt-get purge linux-headers-2.6.32-10-generic 
linux-headers-2.6.32-10 linux-image-2.6.32-10-generic
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SegvAnalysis:
 Segfault happened at: 0x7f77542cc56f __fprintf_chk+95:   cmpw   
$0x0,(%rdi)
 PC (0x7f77542cc56f) ok
 source $0x0 ok
 destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: apt
StacktraceTop:
 __fprintf_chk () from /lib/libc.so.6
 pkgDPkgPM::CloseLog() ()
 pkgDPkgPM::Go(int) ()
 pkgPackageManager::DoInstallPostFork(int) ()
 ?? ()
Title: apt-get crashed with SIGSEGV in __fprintf_chk()
Uname: Linux 2.6.32-12-generic x86_64
UserGroups:

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash lucid

-- 
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

** 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

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/39037120/ProcStatus.txt

** Attachment added: Registers.txt
   http://launchpadlibrarian.net/39037121/Registers.txt

** Attachment added: Stacktrace.txt
   http://launchpadlibrarian.net/39037122/Stacktrace.txt

** Attachment added: ThreadStacktrace.txt
   http://launchpadlibrarian.net/39037123/ThreadStacktrace.txt

-- 
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520207] [NEW] Kernel update to ...32-12 fails because /lib/udev/firmware.sh does not exist

[Ubfan]

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 problem.  Prevents the
dpkg --configure -a from running too.

$ sudo dpkg --configure -a
Setting up initramfs-tools (0.92bubuntu64) ...
update-initramfs: deferring update (trigger activated)

Setting up linux-image-2.6.32-12-generic (2.6.32-12.17) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-12-generic
cpio: ./lib/udev/firmware.sh: Cannot stat: No such file or directory
  ^
  The file /lib/udev/firmware does exist, maybe that is the one to be used?

update-initramfs: failed for /boot/initrd.img-2.6.32-12-generic Failed to 
create initrd image.
dpkg: error processing linux-image-2.6.32-12-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-12-generic
cpio: ./lib/udev/firmware.sh: Cannot stat: No such file or directory
update-initramfs: failed for /boot/initrd.img-2.6.32-12-generic
dpkg: subprocess installed post-installation script returned error exit status 1

created a link in the /lib/udev directory from firmware.sh to firmware
and the dpkg --configure -a succeeded.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Kernel update to ...32-12 fails because /lib/udev/firmware.sh does not exist
https://bugs.launchpad.net/bugs/520207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 367766] Re: live USB disk not bootable

[Ubfan]

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 bandwidth limited, and don't have a 
Jaunty iso anymore.

-- 
live USB disk not bootable
https://bugs.launchpad.net/bugs/367766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 463920] Re: evolution crashes when composing a message pressing space

[Ubfan]

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 been reported upstream as a Debian bug (568129) on
libenchant1c2a.  Lets hope it's fixed for Lucid.

-- 
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer gets devices wrong when running from live USB

[Ubfan]

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 no sdc 
after the install media has been removed, this is certainly wrong.  mtab is OK, 
using the correct sdbx mounts.
  Same procedure -- download iso, (on Jaunty) system/administrator/create USB 
startup disk, reboot from usb startup disk, install to USB hard drive.  Avoid 
messing up the Windows MBR with the advanced button to fix where grub is 
installed.  After the first package update, which got a new kernel, I think the 
grub.cfg file is now OK with all the correct devices.  Only wrong device I can 
find is in the fstab for / (root).

-- 
Grub Installer gets devices wrong when running from live USB
https://bugs.launchpad.net/bugs/384633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 361461] Re: (Jaunty) Wicd No Longer Allows Me To Connect

[Ubfan]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 577508] Re: gui crashes after screensaver changed (lucid)

[Ubfan]

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 due to unknown user id (0   
 (cut off)

-- 
gui crashes after screensaver changed (lucid)
https://bugs.launchpad.net/bugs/577508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 463920] Re: evolution crashes when composing a message pressing space

[Ubfan]

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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 120829] Re: /dev/sda3 is mounted despite the 'noauto' option in fstab

[Ubfan]

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 a click, 
but that feature seemed to go away.  gconf-editor apps/nautilus/preferences has
a medianoautomount option which may help your situation.

-- 
/dev/sda3 is mounted despite the 'noauto' option in fstab
https://bugs.launchpad.net/bugs/120829
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

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 was on a 
4G usb stick, so maybe a slow file system exposed a race condition, but
I have not seen this type of error on the many other usb sticks with Intrepid, 
Jaunty, and Karmic.

-- 
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520738] Re: nm-applet freezes xorg/system

[Ubfan]

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 windows open, so could not change focus, and found even
ctrl-alt-del did nothing.  Tried unsuccessfully to change to a virtual
terminal.  Everything appeared dead, so just powered off.  I do not ever
see these freezups doing anything else.  If a freezup happens again, is
there anything I can check to provide more information?

-- 
nm-applet freezes xorg/system
https://bugs.launchpad.net/bugs/520738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520738] Re: nm-applet freezes xorg/system

[Ubfan]

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/520738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

*** 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/520194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

** 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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 367766] Re: live USB disk not bootable

[Ubfan]

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, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 367766] Re: live USB disk not bootable

[Ubfan]

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, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 510318] Re: Ubuntu - Linux for Human Beings! (About Ubuntu) page contains encoding error

[Ubfan]

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 the following errors:
error on line 448 at column 725: Encoding error
Below is a rendering of the page up to the first error.

xmllint --noout --xinclude --noent --postvalid 
/usr/share/gnome/help/about-ubuntu/C/about-ubuntu.xml
no output

-- 
Ubuntu - Linux for Human Beings! (About Ubuntu) page contains encoding error
https://bugs.launchpad.net/bugs/510318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 510318] Re: Ubuntu - Linux for Human Beings! (About Ubuntu) page contains encoding error

[Ubfan]

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! (About Ubuntu) page contains encoding error
https://bugs.launchpad.net/bugs/510318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520194] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

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 was left.
No proprietary drivers in use.

$ uname -a
Linux laptop 2.6.27-17-generic #1 SMP Wed Jan 27 23:14:44 UTC 2010 i686 
GNU/Linux


sudo apt-get purge `apt-cache pkgnames |fgrep 27-15`
[sudo] password for xxx: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package linux-headers-lbm-2.6.27-15-server is not installed, so not removed
Package linux-backports-modules-2.6.27-15-generic is not installed, so not 
removed
Package linux-backports-modules-2.6.27-15-server is not installed, so not 
removed
Package linux-image-2.6.27-15-virtual is not installed, so not removed
Package linux-restricted-modules-2.6.27-15-server is not installed, so not 
removed
Package linux-headers-lbm-2.6.27-15-generic is not installed, so not removed
Package linux-headers-2.6.27-15-server is not installed, so not removed
Package linux-image-2.6.27-15-server is not installed, so not removed
The following packages will be REMOVED:
  linux-headers-2.6.27-15* linux-headers-2.6.27-15-generic* 
linux-image-2.6.27-15-generic* linux-restricted-modules-2.6.27-15-generic*
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 150MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 156348 files and directories currently installed.)
Removing linux-headers-2.6.27-15-generic ...
Removing linux-headers-2.6.27-15 ...
Removing linux-restricted-modules-2.6.27-15-generic ...
update-initramfs: Generating /boot/initrd.img-2.6.27-15-generic
Purging configuration files for linux-restricted-modules-2.6.27-15-generic ...
Removing linux-image-2.6.27-15-generic ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms
run-parts: executing /etc/kernel/prerm.d/last-good-boot
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... found but preserving previous setting: 
splashimage=/boot/grub/digging.xpm.gz
Found kernel: /boot/vmlinuz-2.6.27-17-generic
Found kernel: /boot/vmlinuz-2.6.27-16-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

Purging configuration files for linux-image-2.6.27-15-generic ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... found but preserving previous setting: 
splashimage=/boot/grub/digging.xpm.gz
Found kernel: /boot/vmlinuz-2.6.27-17-generic
Found kernel: /boot/vmlinuz-2.6.27-16-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

rmdir: failed to remove `/lib/modules/2.6.27-15-generic': Directory not empty
dpkg - warning: while removing linux-image-2.6.27-15-generic, directory 
`/lib/modules/2.6.27-15-generic' not empty so not removed.

$ ls /lib/modules
2.6.27-15-generic  2.6.27-16-generic  2.6.27-17-generic

$ ls /lib/modules/*15*
modules.seriomap

$ locate modules.seriomap
/lib/modules/2.6.27-15-generic/modules.seriomap
/lib/modules/2.6.27-16-generic/modules.seriomap
/lib/modules/2.6.27-17-generic/modules.seriomap


$ cat /lib/modules/*15*/m*
# serio module   type extra id   proto
touchwin 0x02 0xff  0xff 0x33
touchright   0x02 0xff  0xff 0x32
penmount 0x02 0xff  0xff 0x31
mtouch   0x02 0xff  0xff 0x30
inexio   0x02 0xff  0xff 0x37
gunze0x02 0xff  0xff 0x1c
touchit213   0x02 0xff  0xff 0x37
elo  0x02 0xff  0xff 0x29
fujitsu_ts   0x02 0xff  0xff 0x35
serio_raw0x01 0xff  0xff 0xff
vsxxxaa  0x02 0xff  0xff 0x08
sermouse 0x02 0xff  0xff 0x01
sermouse 0x02 0xff  0xff 0x02
sermouse 0x02 0xff  0xff 0x03
sermouse 0x02 0xff  0xff 0x04
sermouse 0x02 0xff  0xff 0x05
sermouse 0x02 0xff  0xff 0x06
sermouse 0x02 0xff  0xff 0x07
psmouse  0x01 0xff  0xff 0xff
psmouse  0x05 0xff  0xff 0xff
xtkbd0x00 0xff  0xff 0xff
sunkbd   0x02 0xff  0xff 0x10
sunkbd   0x02 0xff  0xff 0x00
stowaway 0x02 0xff  0xff 0x20
newtonkbd0x02 0xff  0xff 0x1f
lkkbd0x02 0xff  0xff 0x28
zhenhua  0x02 0xff  0xff 0x36
warrior  0x02 0xff  0xff 0x18
twidjoy  0x02 0xff  0xff 0x24
stinger  0x02 

[Bug 577508] Re: gui crashes after screensaver changed (lucid)

[Ubfan]

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, an error message I also saw on my system after a
crash.

-- 
gui crashes after screensaver changed (lucid)
https://bugs.launchpad.net/bugs/577508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 361461] Re: (Jaunty) Wicd No Longer Allows Me To Connect

[Ubfan]

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 strengths 
around -75db and quality of both in 30s where one shoud be qual = 78/100, 
strength= -59db and other is 2/100, -89 Db.  The laptop having problems has 
been failing, and this looks like the latest failure symptom.  Your probems may 
be as simple as a bad antenna connection.
Good Luck

-- 
(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 Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 577508] Re: gui crashes after screensaver changed (lucid)

[Ubfan]

Just got the crash again after a day of no problems.  It was a /tmp/dbusxxx 
socket that the bonobo-activation-server couldn't access.
After fixing the screensaver to use a non GL, no crashes until
just after installing an Skype 2.1 (Claimed to be for Intrepid)
Maybe a pulseaudio problem?  
messages file:
May 12 20:07:46 dtop pulseaudio[2302]: pid.c: Stale PID file, overwriting.
May 12 20:07:48 dtop pulseaudio[2302]: main.c: Unable to contact D-Bus: 
org.freedesktop.DBus.Error.NoServer: Failed to c
onnect to socket /tmp/dbus-cU04aUTdF2: Connection refused
May 12 20:07:50 dtop bonobo-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 
x-pid=617 x-info=http://www.rsyslog.com;
] exiting on signal 15.
May 12 20:16:04 dtop kernel: imklog 4.2.0, log source = /proc/kmsg started.


Here's the lspci -vvnn for video and audio:

00:02.0 VGA compatible controller [0300]: Intel Corporation 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 
03)
Subsystem: ASUSTeK Computer Inc. Device [1043:8093]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e800 (32-bit, prefetchable) [size=128M]
Region 1: Memory at e780 (32-bit, non-prefetchable) [size=512K]
Capabilities: access denied
Kernel modules: i915

00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:8098]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at e000 [size=256]
Region 1: I/O ports at e100 [size=64]
Region 2: Memory at 3000 (32-bit, non-prefetchable) [size=512]
Region 3: Memory at 3200 (32-bit, non-prefetchable) [size=256]
Capabilities: access denied
Kernel driver in use: Intel ICH
Kernel modules: snd-intel8x0

-- 
gui crashes after screensaver changed (lucid)
https://bugs.launchpad.net/bugs/577508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 506342] Re: apt-get crashed with SIGSEGV in __fprintf_chk()

[Ubfan]

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).  Postgres also needs a directory.  This setup puts
some of the most active write locations into ram, instead of (slow)
flash, which has a limited lifespan.

-- 
apt-get crashed with SIGSEGV in __fprintf_chk()
https://bugs.launchpad.net/bugs/506342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 463920] Re: evolution crashes when composing a message pressing space

[Ubfan]

** Changed in: enchant (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/463920

Title:
  evolution crashes when composing a message pressing space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/463920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 970040] Re: When set to autohide, launcher often won't show

[Ubfan]

@om26er -- I'm not running Unit 3D.  Nvidia 304.60 fixed the problem for
me, but it takes 2 sec for the launch bar to appear -- too slow for me,
so I leave it visible now.  Driver 304.63 worked too, after some initial
problem which had the GUI login stuck in a loop -- looked like some old
.X* files in my home directory caused some issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970040

Title:
  When set to autohide, launcher often won't show

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/970040/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1170150] Re: vmlinuz/initrd.img symlinks do not point to signed versions on kernel updates of secure boot UEFI machines

[Ubfan]

Downloaded the Sept 20 desktop 64 bit ISO, and on a Secure Boot UEFI
laptop running 13.04, created USB install media, and installed to
another USB set up with gpt and an EFI partition.  Booting the target
USB worked in secure mode, with the signed kernel being used, but the
symlink for the kernel is still to the unsigned kernel.As an aside
here, to be entered into another bug, note that the above
straightforward procedure left the laptop unbootable, with the grub.cfg
file on the hard disk's EFI reset to the uuid of the USB stick, (and an
additional unnecessary NVRAM boot entry added).

** Changed in: linux (Ubuntu Saucy)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170150

Title:
  vmlinuz/initrd.img symlinks do not point to signed versions on kernel
  updates of secure boot UEFI machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1170150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1229488] [NEW] 13.10 USB to USB Install on UEFI Secure Boot Machine Left Host Unbootable

[Ubfan]

Public bug reported:

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 EFI partition set
up on it, and bootloader target was the UEB's EFI partition.  The USB
installation boots successfully, but the laptop no longer boots from its
hard disk, leaving you at the grub prompt.  The cause was the installation
improperly changed the hard disk's grub.cfg

Expected change to hard disk's /EFI/ubuntu/grub.cfg -- None.
Actual change to hard disk's /EFI/ubuntu.grub.cfg -- The uuid in the
set root just before the configfile command was reset from the hard
disk to the (no longer present) target USB.

Additionally, no NVRAM changes were expected from installing to a USB
stick, but a new boot entry was created.  This boot entry was a correct
(for secure boot) -- /EFI/ubuntu/shimx64.efi.  NVRAM is a finite
resource, which when used up leaves your machine bricked, or relying on an
untested vendor supplied reset, so any unnecessary additions are highly
undesirable.

Editing the hard disk's improper grub.cfg file by putting in the correct
UUID allowed the laptop to boot successfully.  The EFI menu now has an
additional ubuntu entry, which also boots successfully.  To summarize,
creating or updating a USB installation should not change anything in
NVRAM nor on the hard disk's EFI partition.  This 13.10 installation did both.
(The update reference was to a 12.10 USB update, which changed the NVRAM
shim boot entry's disk code and removed it from the boot order (no bug
filed), so these issues are not new to 13.10.)

Hardware: Toshiba Satellite S855-5378, Insydh20 firmware version 6.60,
8G memory, 750G hard disk, Intel HD4000 video, running dual boot W8 and
fully patched 64 bit 13.04 Ubuntu desktop with secure boot enabled. The only
secure boot issue with this machine is the inability to boot Windows
from grub (bug 1091464), so Windows is the default, and the EFI menu is used
to select Ubuntu to run shim/grub.  The original Ubuntu selection's path is
actually grubx64.efi, which is incorrect for secure boot, but
in /EFI/Boot is a copy of shim.efi named bootx64.efi and grubx64.efi, which 
must be a
fallback, because the boot succeeds anyway. The original shim Ubuntu
selection was improperly changed/removed from boot order and the EFI
menu by a USB 12.10 update (and never added back since a working EFI choice
existed).

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229488

Title:
  13.10 USB to USB Install on UEFI Secure Boot Machine Left Host
  Unbootable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229488/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1229488] Re: 13.10 USB to USB Install on UEFI Secure Boot Machine Left Host Unbootable

[Ubfan]

Oops, just checked the USB target again after fixing the host machine
and found that it had nothing in its EFI partition, so It would not boot
either.  I thought that specifying the explicit paritition /dev/sdc1 (vs
the device /dev/sdc) would work for removable media bootlaoder
locations on an EFI partitions, but that did not work in this case.  The
EFI updates went to the hard disk's EFI partition as well, as evidenced
by their different size from the 13.04 versions of the signed grubx64
and shim.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229488

Title:
  13.10 USB to USB Install on UEFI Secure Boot Machine Left Host
  Unbootable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229488/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled

[Ubfan]

On a just updated 13.10 (Nov 15) getting shim-signed 1.5 and a new signed 
grubx64.efi 2.00..-19 I see no change in the error.
The UnknownMessage (hex 12)  or decimal 18 is indeed an invalid subtype for the 
messaging type (last valid subtype is decimal 15), so looks like leftover 
garbage in the path buffer?  Why is grub even in the messaging type anyway for 
a hard disk boot?  The beginning of the reported path looks just like a network 
boot looks from efibootmgr -v output.  Should the valid path start at the 
/HD...?  If someone without the problem could look at what the actual path 
chainloader is using could confirm that the /ACPI is present and working on 
their system we could eliminate leftover garbage in the grub path buffer as the 
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464

Title:
  Unable to chainload Windows 8 with Secure Boot enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 840146] Re: colord crashed with SIGABRT in raise()

[Ubfan]

Happens regularly on 12.04, colord0.1.16-2ubuntu0.1, i386, nonfree=nvidia, 
/usr/lib/i386-linux-gnu/colord/colord,
kernel 3.2.0-39.62-generic-pae 3.2.39, signal =6.  fully updated system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840146

Title:
  colord crashed with SIGABRT in raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/840146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1086289] Re: Wrong grub-efi resolution during OS boot menu selection

[Ubfan]

I have seen the reduced grub resolution, but only after an EFI boot failure and 
its subsequent fallback to the /Boot/bootx64.efi.
My machine is a Toshiba Satellite S855, and it boots off USB with a correctly 
set up ESP at full resolution, but when I select the hard disk's ubuntu choice, 
I got the reduced resolution.  Examining the actual hard disk ubuntu boot path, 
it was ...ubuntu/grubx674.efi, which is wrong for a secure boot (which I use).  
It should be ...ubuntu/shim.efi.  The ...Boot/bootx64.efi contained a copy of 
the shim.efi, and when the bootx64 file was removed, the boot failed.  I 
conclude that the first boot attempt to grubx64 directly silently failed, then 
EFI tried the Boot/bootx64 and succeeded in starting shim, which started grub 
-- at the wrong resolution.
  I'd suggest checking your boot path with 
sudo efibootmgr -v
and confirm that it is what you think it is.  So much renaming of these files 
can occur that  looking at the sizes is necessary to confirm their identity.  
There are signed and unsigned versions  of grubx64, and only the correct one 
will work.  As an example of this sequence of errors on a non-secure boot 
machine, suppose the bootx64 contains  copy of the non-signed grubx64 (which 
will work), but the boot path is to ubuntu/grubx64 which is the signed version. 
 
  I have not bothered to correct the boot path, since I don't notice any 
delays, and the resolution doesn't bother me, so I may be totally wrong that 
correcting the initial boot path will fix things.  Also I feel I need to learn 
more about NVRAM and how to determine how much free space is available before 
adding things to it like new boot choices -- the Samsung situation of too 
little NVRAM makes me cautious, afraid I'll brick my machine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086289

Title:
  Wrong grub-efi resolution during OS boot menu selection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1086289/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1170150] [NEW] vmlinuz/initrd.img symlinks do not point to signed versions on kernel updates of secure boot UEFI machines

[Ubfan]

Public bug reported:

Kernel updates on a UEFI pc with secure boot enabled have the vmlinuz
and initrd.img symlinks updated, but they point to the unsigned versions
of the kernel instead of the signed ones.  The pc was set up with secure
boot on, has never been booted with secure boot off, and no runtime
problems have been noted from the wrong symlinks.  Having the links to
the signed versions is highly desirable, in order to set up a USB stick
with its own EFI directory to boot Ubuntu, and not have to worry about
changing the USB stick's grub.cfg files.

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170150

Title:
  vmlinuz/initrd.img symlinks do not point to signed versions on kernel
  updates of secure boot UEFI machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1170150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1170150] Re: vmlinuz/initrd.img symlinks do not point to signed versions on kernel updates of secure boot UEFI machines

[Ubfan]

Ubuntu 12.10, updated several times, getting kernels ...17, ...26, and ...27.  
The symlinks in / were examined with ls -l and  the output  indicated that 
the link was to the /boot/vmlinuz-generic file, NOT the 
/boot/vmlinuz...-generic.efi.signed file.
Applying the sbattach command to the /vmlinuz (and to the actual 
/boot/vmlinuz-3.5.0-27-generic file) produced a zero length output with the 
warnings:
warning: file-aligned section of .text extends beyond  end of the file
warning: checksum areas are greater than image size. invalid section table?

Applying the sbattach command to the /boot/vmlinuz...-generic.efi.signed file 
produced no errors, and output of length 1911.
I conclude that the kernels in /boot ending in .efi.signed are the signed 
versions, and the ones ending in .generic are not -- with the symlinks in / 
pointing to the unsigned versions.

The file /etc/kernel-img.conf contains symlinks=yes, and bootloader=no

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170150

Title:
  vmlinuz/initrd.img symlinks do not point to signed versions on kernel
  updates of secure boot UEFI machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1170150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1170150] Re: vmlinuz/initrd.img symlinks do not point to signed versions on kernel updates of secure boot UEFI machines

[Ubfan]

Bug 1091464 affects me (grub unable to chainload Windows), so as a workaround, 
I have a separate ESP on a USB stick.  The stick boots Ubuntu 12.10 off the 
hard disk, and the stick is not mounted in the filesystem.  I had been updating 
the stick's EFI/ubuntu/grub.cfg as each kernel update occurred, but thought I 
would instead just use the root symlinks, and avoid future grub updates to the 
stick.  That is when I noticed that the symlinks' targets were the unsigned 
versions of the kernel, and reported the bug.
  Now grub WILL boot the unsigned kernels off the existing symlinks, and I can 
see no differences when signed vs. unsigned kernel is used, but I don't know 
how the symlinks are used by other programs, so something may break if the 
symlinks don't target the running kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170150

Title:
  vmlinuz/initrd.img symlinks do not point to signed versions on kernel
  updates of secure boot UEFI machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1170150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1090829] Re: grub-efi fails to install with Input/output error

[Ubfan]

@yannubuntu re: #34:  Yes, I too see the efi firmware path
ubuntu/grubx64.efi when it should be ...shim.efi .  Looks like grub-
install defaulted to that when the path test for shim failed.  I haven't
done much except get rid of the usb boot for Ubuntu -- I was surprised
the F12/select HDD/select ubuntu worked for booting Ubuntu, since secure
boot rejects grubx64.efi, but it turned out the grubx64 silently failed,
then the fallback was to try EFI/Boot/bootx64.efi, which was a copy of
shim (and grubx64 was present in Boot also), so it worked.  If you think
a copy of my efivars would help, I could post them.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090829

Title:
  grub-efi fails to install with Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1090829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1173457] [NEW] Ubuntu 13.04 Desktop 64 bit install uses wrong ESP for secure boot laptop

[Ubfan]

Public bug reported:

On a secure boot pc (secure boot enabled, Ubuntu Desktop 12.10 64bit installed 
with Win 8), installing from live media Ubuntu 13.04 64 bit desktop to a target 
thumbdrive (pre partitioned with gpt, and a bootable FAT32 partition 1 of 250M 
labeled EFI) properly identifies the target's first partition as an EFI 
bootable partition (when do something else is selected), but the install
will then mount the ESP off the laptop's hard drive (at /target/boot/efi).  
The install creates a grub.cfg file under /target/boot/efi/EFI/ubuntu pointing 
to the target's(uuid) /boot/grub/grub.cfg.  This wrong grub.cfg will prevent 
the laptop from booting Ubuntu without the thumbdrive, throwing the boot into a 
grub  prompt (since the configfile points to the usb and is no longer present).

The install should use the identified EFI boot partition on the
target, so the target may boot when first in boot priority, and not
touch the hard disk's EFI files.  If for any reason a permanent
installation is to be made to a USB device, simply select the hard
disk's ESP instead of one on the target.

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173457

Title:
  Ubuntu 13.04 Desktop 64 bit install uses wrong ESP for secure boot
  laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1159016] Re: 12.10 64bit live-USB successfully boots, but without persistence on UEFI pc

[Ubfan]

Thanks Fred. Yes the fix is simple enough, add the word persistent to the 
/boot/grub/grub.cfg  vmlinuz kernel lines.  This bug still affects 13.04 also.  
  I find persistence useful for  setting up my install media with additional 
wireless/ethernet packages which may be needed on some machines.  A Toshiba 
Satellite under 12.10 had neither working wireless nor ethernet (until the 
first kernel upgrade), so I set up the wireless  rt8723 module build and the 
boot-repair deb on another machine, to make the Toshiba installation easier -- 
Ha.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159016

Title:
  12.10 64bit live-USB successfully boots, but without persistence on
  UEFI pc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1159016/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled

[Ubfan]

I have the same error on a Toshiba Satellite S855 S5378 with Windows 8
preinstalled. My workaround is to use a (full install) thumbdrive to
boot Ubuntu 12.10 on the hard disk, and to pull the thumbdrive to boot
windows -- all in secure mode.  Windows boots attempted from the
thumbdrive, give the error message.  The grub command ls will find the
files, but chainloader will not succeed in running them.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464

Title:
  Unable to chainload Windows 8 with Secure Boot enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled

[Ubfan]

A second workaround, more convienent than the USB boot is to invoke the EFI 
device select menu, select HDD, then select ubuntu or Windows (both of which 
work).  The ubuntu selection starts grub, but from grub, the Windows boot still 
fails with the above chainloader error.  
  With the number of different brands mentioned in this bug, I begin to doubt 
the problem is vendor related.  Maybe something we did caused this, so here's 
what I did:
  My first install was to a USB stick without ann EFI partition( used HD EFI, 
booted Ubuntu OK, did not boot Windows, and killed the Windows boot off the 
hard disk when not present).  Installed to (prepared HD) in this condition, 
worked, but got a grub install error (Windows boot worked again). Installed to 
USB again after putting on a EFI partition, the install still mounted the HD 
EFI, which I manually unmounted and replaced with the USB EFI (this worked).  
At this point, the HD /EFI/ubuntu directory was corrupted, so had to manually 
delete it and replace the signed binaries.  The USB would boot Ubuntu, but not 
Windows, and the HD would boot Windows (default).  Using efibootmgr -v, I could 
see that the ubuntu boot was set up wrong, trying to boot grub instead of shim 
-- but much to my surprise, it still booted, so I surmise a silent failure, 
then a fallback to the /EFI/Boot/bootx64.efi (which was a copy of shim) which 
succeeded.  I manually added (grub-install --uefi-secure-boot /dev/sda) a 
correct shim boot path, which worked too.  I normally now enter F12 to select 
ubuntu or Windows.  Not a totally clean history, but on the other hand, the 
machine has never been out of secure boot, I have never run boot-repair, and 
the only EFI variable manipulation I have done is through grub-install.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464

Title:
  Unable to chainload Windows 8 with Secure Boot enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves

[Ubfan]

Running system is a 4G USB, booted with bluetooth off, no battery indicator 
displayed,  killed the upowerd process, then turned bluetooth on, then turned 
on the mouse, which immediately worked,  resulting in the following dmesg 
messages:
[ 1542.188059] usb 2-4: new full-speed USB device number 4 using ohci_hcd
[ 1542.418559] usb 2-4: New USB device found, idVendor=03f0, idProduct=171d
[ 1542.418574] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1542.418582] usb 2-4: Product: HP Integrated Module
[ 1542.418589] usb 2-4: Manufacturer: Broadcom Corp
[ 1542.515610] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1544.470504] hid-generic 0005:0A5C:0001.0003: unknown main item tag 0x0
[ 1544.480876] input: Bluetooth Mouse as 
/devices/pci:00/:00:0b.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:11/input11
[ 1544.481419] hid-generic 0005:0A5C:0001.0003: input,hidraw2: BLUETOOTH HID 
v0.1e Keyboard [Bluetooth Mouse] on 00:16:41:D4:B1:1F

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098959

Title:
  12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse
  Moves

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1098959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves

[Ubfan]

Cycling mouse and/or bluetooth never crashes the upowerd for me.  I do get some 
null pointer stack dump from the bluetoothd at some point.  Closest complaint 
was :
quanta4g kernel: [  211.852064] power_supply hid-00:60:D1:00:C3:15-battery: 
driver failed to report `capacity' property: 4294967291

Here's the null pointer log:
Jan 19 14:25:50 quanta4g kernel: [  213.560251] [ cut here 
]
Jan 19 14:25:50 quanta4g kernel: [  213.560261] WARNING: at 
/build/buildd/linux-3.5.0/lib/kobject.c:196 kobject_add_internal+0x1ea/0x200()
Jan 19 14:25:50 quanta4g kernel: [  213.560264] Hardware name: Presario V3000 
(RD462PA#AB0)
Jan 19 14:25:50 quanta4g kernel: [  213.560269] kobject_add_internal failed for 
hci0:11 with -EEXIST, don't try to register things with the same name in the 
same directory.
Jan 19 14:25:50 quanta4g kernel: [  213.560272] Modules linked in: hidp bnep 
rfcomm parport_pc ppdev vesafb lp parport snd_hda_codec_conexant arc4 
nvidia(PO) hp_wmi sparse_keymap kvm_amd kvm snd_hda_intel snd_hda_codec 
snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer 
snd_seq_device psmouse serio_raw r852 sm_common nand r592 nand_ids mtd nand_bch 
bch memstick joydev nand_ecc snd btusb k8temp soundcore bluetooth 
snd_page_alloc b43 mac80211 nv_tco cfg80211 i2c_nforce2 bcma ssb_hcd wmi video 
mac_hid ext2 hid_generic usbhid hid firewire_ohci sdhci_pci uas usb_storage 
sdhci firewire_core crc_itu_t pata_amd forcedeth sata_nv ssb
Jan 19 14:25:50 quanta4g kernel: [  213.560377] Pid: 5, comm: kworker/u:0 
Tainted: PW  O 3.5.0-21-generic #32-Ubuntu
Jan 19 14:25:50 quanta4g kernel: [  213.560380] Call Trace:
Jan 19 14:25:50 quanta4g kernel: [  213.560391]  [c1044802] 
warn_slowpath_common+0x72/0xa0
Jan 19 14:25:50 quanta4g kernel: [  213.560400]  [c12c9dba] ? 
kobject_add_internal+0x1ea/0x200
Jan 19 14:25:50 quanta4g kernel: [  213.560409]  [c12c9dba] ? 
kobject_add_internal+0x1ea/0x200
Jan 19 14:25:50 quanta4g kernel: [  213.560419]  [c10448d3] 
warn_slowpath_fmt+0x33/0x40
Jan 19 14:25:50 quanta4g kernel: [  213.560428]  [c12c9dba] 
kobject_add_internal+0x1ea/0x200
Jan 19 14:25:50 quanta4g kernel: [  213.560438]  [c113e293] ? 
kmem_cache_alloc_trace+0x103/0x110
Jan 19 14:25:50 quanta4g kernel: [  213.560448]  [c12ca075] 
kobject_add+0x35/0x80
Jan 19 14:25:50 quanta4g kernel: [  213.560457]  [c13aad36] 
device_add+0xe6/0x620
Jan 19 14:25:50 quanta4g kernel: [  213.560469]  [c12d5543] ? 
kvasprintf+0x43/0x60
Jan 19 14:25:50 quanta4g kernel: [  213.560479]  [c12ca022] ? 
kobject_set_name_vargs+0x42/0x60
Jan 19 14:25:50 quanta4g kernel: [  213.560503]  [f9ec53a3] 
hci_conn_add_sysfs+0x43/0x80 [bluetooth]
Jan 19 14:25:50 quanta4g kernel: [  213.560527]  [f9eb9695] 
hci_conn_complete_evt.isra.47+0xb5/0x360 [bluetooth]
Jan 19 14:25:50 quanta4g kernel: [  213.560575]  [f9ebb370] 
hci_event_packet+0x8f0/0x2170 [bluetooth]
Jan 19 14:25:50 quanta4g kernel: [  213.560644]  [f9d80cae] ? 
__ieee80211_recalc_idle+0x13e/0x290 [mac80211]
Jan 19 14:25:50 quanta4g kernel: [  213.560674]  [c101003c] ? 
__switch_to+0xbc/0x260
Jan 19 14:25:50 quanta4g kernel: [  213.560683]  [c107d53a] ? 
idle_balance+0x10a/0x150
Jan 19 14:25:50 quanta4g kernel: [  213.560692]  [c1037b08] ? 
default_spin_lock_flags+0x8/0x10
Jan 19 14:25:50 quanta4g kernel: [  213.560702]  [c15ca9dd] ? 
_raw_spin_lock_irqsave+0x2d/0x40
Jan 19 14:25:50 quanta4g kernel: [  213.560723]  [f9eb1502] 
hci_rx_work+0x222/0x2e0 [bluetooth]
Jan 19 14:25:50 quanta4g kernel: [  213.560731]  [c105fa8f] 
process_one_work+0x10f/0x380
Jan 19 14:25:50 quanta4g kernel: [  213.560751]  [f9eb12e0] ? 
le_scan_work+0xd0/0xd0 [bluetooth]
Jan 19 14:25:50 quanta4g kernel: [  213.560759]  [c1060cd9] 
worker_thread+0xf9/0x290
Jan 19 14:25:50 quanta4g kernel: [  213.560767]  [c10707de] ? 
complete+0x4e/0x60
Jan 19 14:25:50 quanta4g kernel: [  213.560775]  [c1060be0] ? 
manage_workers.isra.25+0x1d0/0x1d0
Jan 19 14:25:50 quanta4g kernel: [  213.560784]  [c1064e72] kthread+0x72/0x80
Jan 19 14:25:50 quanta4g kernel: [  213.560794]  [c1064e00] ? 
kthread_freezable_should_stop+0x60/0x60
Jan 19 14:25:50 quanta4g kernel: [  213.560804]  [c15d1c7e] 
kernel_thread_helper+0x6/0x10
Jan 19 14:25:50 quanta4g kernel: [  213.560808] ---[ end trace 130847ee8b7fb170 
]---
Jan 19 14:25:50 quanta4g kernel: [  213.560814] Bluetooth: Failed to register 
connection device
Jan 19 14:25:53 quanta4g kernel: [  216.852108] power_supply 
hid-00:60:D1:00:C3:15-battery: driver failed to report `capacity' property: 
4294967291
Jan 19 14:25:53 quanta4g kernel: [  216.897600] [ cut here 
]
Jan 19 14:25:53 quanta4g kernel: [  216.897629] WARNING: at 
/build/buildd/linux-3.5.0/lib/kobject.c:200 kobject_add_internal+0xef/0x200()
Jan 19 14:25:53 quanta4g kernel: [  216.897634] Hardware name: Presario V3000 
(RD462PA#AB0)
Jan 19 14:25:53 quanta4g kernel: [  216.897641] kobject_add_internal failed for 
0005:0A5C:0001.0004 (error: -2 parent: hci0:11)
Jan 19 

[Bug 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves

[Ubfan]

** Also affects: gnome-power
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098959

Title:
  12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse
  Moves

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1098959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1159016] [NEW] 12.10 64bit live-USB successfully boots, but without persistence on UEFI pc

[Ubfan]

Public bug reported:

The 64but 12.10 2G live USB was set up on a 32bit 12.04.1 non-UEFI host with 1G 
persistence.
The USB boots and persistence works on the non-UEFI host.
The USB boots in Secure boot mode but without persistence on a UEFI host.
The /proc/cmdline on the running live media shows the running kernel to be 
vmlinuz.efi.signed, which of
course does not appear in any syslinux config files.
Looks like something got left out in the secure boot procedure to have 
persistence.

Live media created with the following iso:
800063488 Mar 18 11:14 ubuntu-12.10-desktop-amd64.iso
md5sum
7ad57cadae955bd04019389d4b9c1dcb  ubuntu-12.10-desktop-amd64.iso

The UEFI host is a Toshiba Satellite S855-5378 and has Windows 8 preinstalled,
so no legacy BIOS is present.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: usb-creator-gtk 0.2.38
ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39
Uname: Linux 3.2.0-39-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Date: Fri Mar 22 16:48:52 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: usb-creator
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: usb-creator (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise running-unity third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159016

Title:
  12.10 64bit live-USB successfully boots, but without persistence on
  UEFI pc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1159016/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1090829] Re: grub-efi fails to install with Input/output error

[Ubfan]

How I corrupted the ubuntu directory:
On a Toshiba Satellite S855 with Windows 8 preinstalled and Secure boot 
enabled, successfully installed 12.10 64b to a 4G stick, without making a efi 
partition on it.  This created a good EFI/ubuntu directory on the hard disk, 
but left the EFI/Boot directory containing ony a grub.cfg file to boot the 
stick (so Windows would no longer boot), (although the 4G stick would boot).
  In this condition, I then installed 12.10 to a previously freed up space on 
the hard disk, which failed at the bootloader part, but
did end up in a condition which Windows booted.Tried again to install to 
the 4G stick, this time with an efi partition on the stick, which failed with 
the grub-install dummy error. Looking at the EFI with ls -l, the ubuntu 
directory just showed a name the d for directory, and all else appeared as 
?s.  Apparently, the second (or maybe third) install of Ubuntu corrupted the 
ubuntu directory in the Windows EFI directory,.  Examining the failed stick, 
the /etc/fstab file refers to the hard disk's EFI partition (by UUID), not the 
one on the stick (which was empty).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090829

Title:
  grub-efi fails to install with Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1090829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1090829] Re: grub-efi fails to install with Input/output error

[Ubfan]

@yannbuntu: My issue is the same as yours: the underlying bad EFI/ubuntu
directory.

I think I can narrow the cause to grub-efi itself:
 1) I have never booted the pc with Secure boot disabled.
 2) I have never run any third party tools like your boot-repair.
 3) I have never added, changed or renamed anything in the EFI partition.
 4) First installation of 12.10 did produce a normal ubuntu directory,
which allowed the installation (but not Windows) to run.
 5) Second and third attempts at installation failed at the grub part.

And yes, after the ubuntu directory is corrupted, grub-efi will complain
about it, along with virtually every other tool attempting to access it.

Repeated runs of dosfsck -r did eventually fix the corruption, by
deleting the ubuntu directory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090829

Title:
  grub-efi fails to install with Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1090829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1090829] Re: grub-efi fails to install with Input/output error

[Ubfan]

I see lots of Input/Output errors when accessing the EFI/ubuntu directory, and 
see a (bogus?) read only filesystem message in dmesg:
dmesg lines (probably caused by the ls command):
FAT-fs (sda2); error, fat_get_cluster: invalid cluster chain (i_pos 0)
FAT-fs (sda2): Filesystem has been set read only

But the mount command still lists the sda2 mount as rw.

The Input/Output error appears with any attempted access to the directory:
ls ubuntu, sudo mv ubuntu ..., sudo rm -rf ubuntu all produce the Input/Output 
error.
I forget the error message from the third installation attempt, but it was a 
failure
I expected and might have been the IO error (it was NOT the error window 
produced from
the second installation attempt which apparently caused the corrupted 
directory).

The error window on the second installation (to hard disk) was:
Window title: Unable to install Grub in a dummy
Text: Executing 'grub-install dummy' failed
  This is a fatal error.

Since I fixed the bad directory, and I'm not really working on my own
UEFI machine, I'll hold off on doing anything more, like running the
grub-install.  I hope this helps in improving things.

A guess as to what's wrong:
Looks like an off-by-one error on a loop index in grub install when it 
encounters an existing EFI/ubuntu directory.  The directory is probably 
rewritten with an extra (free) block added at the start. The dosfsck reports 
such in the below terminal capture.  Confirm this by looking at the filesystem 
image posted above.  


The fix to get rid of the corrupted directory (since rm won't work) applying 
Phillip's (comment #25) suggestion:
$ sudo mount -tvfat /dev/sda2 /mnt/sda2
ubuntu@ubuntu:/mnt/sda7/etc$ ls !$
ls /mnt/sda2
EFI

ubuntu@ubuntu:/mnt/sda7/etc$ sudo dosfsck -r /dev/sda2
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
/EFI/ubuntu
  Contains a free cluster (12149). Assuming EOF.
Reclaimed 277 unused clusters (1134592 bytes).
Perform changes ? (y/n) y
/dev/sda2: 326 files, 12146/65536 clusters

ubuntu@ubuntu:/mnt/sda7/etc$ sudo dosfsck -r /dev/sda2
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
/EFI/ubuntu
 Start does point to root directory. Deleting dir. 
Reclaimed 276 unused clusters (1130496 bytes).
Perform changes ? (y/n) y
/dev/sda2: 326 files, 12146/65536 clusters

ubuntu@ubuntu:/mnt/sda7/etc$ sudo dosfsck -r /dev/sda2
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
Orphaned long file name part ubuntu
1: Delete.
2: Leave it.
? 1
Perform changes ? (y/n) y
/dev/sda2: 325 files, 12146/65536 clusters

ubuntu@ubuntu:/mnt/sda7/etc$ sudo dosfsck -r /dev/sda2
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
/dev/sda2: 325 files, 12146/65536 clusters

ubuntu@ubuntu:/mnt/sda7/etc$ ls /mnt/sda2/EFI
Boot  Microsoft  toshiba

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090829

Title:
  grub-efi fails to install with Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1090829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1090829] Re: grub-efi fails to install with Input/output error

[Ubfan]

@yannubuntu: Sorry, bug 1159016 had me running non-persistent on my live
media. At the time I didn't remember to capture any log files on another
usb.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090829

Title:
  grub-efi fails to install with Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1090829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384633] Re: Grub Installer uses device name instead of UUID, leading to unbootable system

[Ubfan]

The problem is still present with the 12.04 release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/384633

Title:
  Grub Installer uses device name instead of UUID, leading to unbootable
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/384633/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled

[Ubfan]

A forums question http://ubuntuforums.org/showthread.php?t=2197141
indicated that the bug could be made to go away in secure boot by
putting the os I wanted to boot on on the top of the list of bootable
drives.  Now my UEFI Settings for devices does NOT contain OSes, just
devices.  When I select the hard disk on the efi menu, I get another
window listing the OSes to boot.  Maybe this second level of choice has
something to do with the source of the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464

Title:
  Unable to chainload Windows 8 with Secure Boot enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 876734] Re: gnome-terminal scroll position indicator invisible when left scroll is selected

[Ubfan]

** Description changed:

- Under Unity and Unity-2D, selecting left scroll for a gnome-terminal
- scroll bar position results in the little red bar, indicating where the
- scroll elevator will appear , being invisible, making it difficult to
- find, since random clicks must be applied along the left window border
- to make the scroll elevator appear.
+ Under Unity and Unity-2D gnome-terminal profiles, selecting right scroll
+ (the default) for a gnome-terminal scroll bar position results in the
+ little red bar on the right edge of the terminal, indicating where the
+ scroll elevator will appear.  Selecting the left scroll in the profile
+ however, does not result in the little red tag appearing, so being
+ invisible, it is difficult to find the position to make the scroll bar
+ appear. Random movement of the cursor along the left window border is
+ necessary to make the scroll elevator appear, which then may be grabbed
+ and used normally.  Still a problem in 12.04.3 and 13.10
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Mon Oct 17 11:22:25 2011
  ProcEnviron:
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876734

Title:
  gnome-terminal scroll position indicator invisible when left scroll is
  selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/876734/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs