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
** 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
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
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
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.
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
)
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
** 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
--
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
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),
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
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.
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.
--
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
--
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:
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
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
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
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
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 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.
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
#
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 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
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
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
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
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
--
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
Navigation box appears to have a sporadic problem.
There is another page with this problem which causes a pink error box at the
top of the page:
How Can I Upgrade to the latest version of Ubuntu?
The error is not consistent -- it's either:
1)Not present (rare).
2)line 467 col 46 Encoding error
Public bug reported:
Binary package hint: apt
Manual purge of an old set of kernel files did not totally clean out the
/lib/modules/2.6.32-10-generic directory, leaving file
modules.builtin.bin. Noticed that a previous kernel ...9 removal left
the same file and directory.
sudo apt-get purge
** 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
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
As I recall, the stick did not work on a second laptop either. The problem was
fixed in Jaunty, since
a create startup usb command succeeded with a Karmic iso. I still have an
Intrepid installation which I can use to see if it can successfully create a
Karmic usb if that is of interest. I'm
Karmic/AMD64 after adding the spell, ispell, American dict packages,
evolution exhibits the crash in composing when a word break is first
typed. Removing the spelling packages is a workaround for the problem.
Maybe turning off spell checking as you type will also workaround the
problem. This has
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
Another possibility is that your access point has run out of ip address
leases. I upped the number from 3 to 10 and things started working
again.
--
(Jaunty) Wicd No Longer Allows Me To Connect
https://bugs.launchpad.net/bugs/361461
You received this bug notification because you are a member of
Burned a live Lucid CD and booted up the HP Pavilion a210n. It experienced
the GL crash/hang too with the antSpotlight, so I guess the upgrade was not an
issue. I did find a warning at the top of one text screen which might be of
interest:
(Process:256): GLibWARNING **: getpwuid_r(): failed
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.
--
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
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
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
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
*** 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()
** 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
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,
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,
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
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
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
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,
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
-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
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
** 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
@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*
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
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
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
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
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
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
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
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
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
@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
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
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.
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
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
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
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
** 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
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
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
@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
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
@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.
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
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
** 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
1 - 100 of 228 matches
Mail list logo
