This bug comes up again and again on Askubuntu:
http://askubuntu.com/questions/171209/my-boot-partition-hit-100-and-now-i-cant-upgrade-cant-remove-old-kernels-to
http://askubuntu.com/questions/345588/what-is-the-safest-way-to-clean-up-boot-partition
http://askubuntu.com/questions/89710/how-do-i-fr
Additional information: I deleted the pre-existing "maas" user on the
server and tried again. This time the enlistment succeeded. I've been
unable to get the bug to recur, even by resetting the "maas" user's
password to its original value ("maas12345"). Thus, I suspect there was
something wonky abo
Importance: Undecided
Assignee: Roderick Smith (rodsmith)
Status: New
** Changed in: plainbox-provider-checkbox (Ubuntu)
Assignee: (unassigned) => Roderick Smith (rodsmith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
*** This bug is a duplicate of bug 1357093 ***
https://bugs.launchpad.net/bugs/1357093
** This bug has been marked a duplicate of bug 1357093
LVM or Encrypted install creates too small /boot partition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When using a partitioning option that requires the use of a /boot
partition (such as LVM), Ubiquity (in Ubuntu 15.04) creates a rather
small /boot partition -- 244MiB in my test:
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
AP
I encountered the same bug when I performed an installation that used
LVM (I selected the "Use LVM with the new Ubuntu installation" option).
When I opened a shell and examined the partition table, it appears that
it had already been created. (The disk was empty when I began.) The
partition table r
Paul,
I'm attaching the backtrace you wanted.
Note, however, that the problem has disappeared on the original system
(a VirtualBox VM) that exhibited it. I had to do a fresh installation to
re-create it. The problem disappeared after I rebooted the new
installation. Deleting the ~/.nedit director
Public bug reported:
I've tried to use ipmitool to change a server's configuration from
local-disk booting to PXE-booting using ipmitool, thus:
ipmitool -H 172.24.25.53 -U ubuntu -P passwd chassis bootdev pxe
The man page suggests this should work, although it doesn't explicitly
mention EFI/UEFI
Public bug reported:
On a fresh install of Ubuntu Desktop 15.04 with the "nedit" package and
a few others added, nedit crashes (segfaults) on startup. I'm attaching
the /var/crash/_usr_bin_nedit.1000.crash file from such a crash. Further
version information from this system:
$ lsb_release -rd
Des
I'm the upstream author of GPT fdisk.
The intent of the "3" return code is to signal when sgdisk failed to
operate because the disk was a non-GPT disk -- for instance, a "-d"
operation to delete a partition, which sgdisk will refuse to do on an
MBR disk unless "-g" is also included, to make it cle
Yes, we can give you access, but that may have to wait until next week.
(I'm running certification tests on it now, and they'll go on until
sometime mid-afternoon.) If you'll want to change the MAAS
configuration, we'll probably want to move it from maaster to landmaas.
--
You received this bug n
Examining the code, there are several sgdisk calls, but two are relevant
for this discussion. The first is the one reproduced in this initial bug
report:
sgdisk --zap-all --clear --mbrtogpt
This call does not seem to have been changed as a result of bug
#1257491. Upon further review, I think I se
GPT fdisk relies on OS calls to determine the sector size, which is
vitally important for interpreting GPT data structures. It appears that
the NTFS-3g driver that Ubuntu uses is not returning that data, which
means that sgdisk can only make a guess that the sector size is 512. (In
fact, when deali
Please post example output; it's unclear to me what you mean by "showing
opposite labels for my 9th and 10th partitions (GPT)." Also, be aware
that the versions of fdisk and cfdisk delivered with Ubuntu through
version 14.04 don't support GPT, although 14.10's fdisk and cfdisk add
GPT support. Iden
This is not a bug. From the gdisk man page's description of the backup
option:
b Save partition data to a backup file. You can back up your cur‐
rent in-memory partition table to a disk file using this option.
The resulting file is a binary file consisting
This is not a bug in sgdisk; it's either a bug in the charm or an
incorrect use of same. Specifically, the sgdisk command shown is:
sgdisk --zap-all --clear --mbrtogpt /dev/vdb
This command does four things, in sequence:
- It zaps all GPT and MBR data structures (--zap-all).
- It creates an empt
I bumped gdisk out of beta status yesterday; version 1.0.0 is now
available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281306
Title:
version bump request
To manage notifications about this bug
Yes, Brian; AFAIK the SRU is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383727
Title:
[SRU] Fast installer - failure to install grub (UEFI mode)
To manage notifications about this bug go
It was the curtin-common package at fault. I had been under the mistaken
impression that it was the ephemerals that needed to be updated, and we
hadn't updated the packages on the server in a while. Once we did, it
started working.
--
You received this bug notification because you are a member of
We're still having problems with one MAAS server. We suspect an
ephemeral isn't being updated correctly. What's the best procedure to
ensure that the fix gets onto a working MAAS server without wiping out
the existing node list?
--
You received this bug notification because you are a member of Ub
This is an extremely critical bug for installations with EFI-mode
systems. When will the fix work its way into earlier distributions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383727
Title:
Fas
This bug still exists in Ubuntu 14.04. It can be fixed by installing the
gsfonts-x11 package. Currently, that package is marked as "suggested" in
the xfonts Debian package. I strongly recommend making gsfonts-x11 a
full dependency. Although xfig is useful for some purposes without
working fonts, I
Just to note: This problem still exists in Ubuntu 14.04LTS and 14.10.
It's annoying because I have to make changes to every new installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424371
Title
I just tested with Utopic, and it seems to be fixed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260893
Title:
iperf forks and loops endlessly in daemon mode
To manage notifications about
** Attachment added: "/var/log/syslog file from installation showing problem
(delayed a few hours)"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1351071/+attachment/4167413/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
When a GUID Partition Table (GPT) disk is partitioned with fdisk
(without GPT support), with Microsoft's default partitioning tools, or
with certain other GPT-unaware tools, the result is a valid MBR
partition table and leftover GPT data. The GPT spec (part of the
EFI/UEFI spe
*** This bug is a duplicate of bug 1330021 ***
https://bugs.launchpad.net/bugs/1330021
** This bug has been marked a duplicate of bug 1330021
custom installation on GPT partitioned disks refers to Primary & Logical
partitions
--
You received this bug notification because you are a member
DavidEscott (david-escott) wrote:
> As a practical matter there really should be an override for the
installer.
+1. I've seen a LOT of online problems reported because Ubuntu installs
in one mode on a computer with another OS installed in another mode.
Usually the existing install in EFI mode and
I've submitted this patch upstream:
https://sourceforge.net/p/iperf/patches/28/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260893
Title:
iperf forks and loops endlessly in daemon mode
To manag
The problem was caused by starting a thread and then forking the program
as part of daemonizing it. This resulted in the thread no longer
communicating correctly with the forked main program. See here for more
information:
http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-
us
Public bug reported:
I'm unable to install kdevelop in Ubuntu 14.04LTS Desktop. The attempt
yields the following:
$ sudo apt-get install kdevelop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean tha
*** This bug is a duplicate of bug 1260893 ***
https://bugs.launchpad.net/bugs/1260893
** This bug has been marked a duplicate of bug 1260893
iperf forks and loops endlessly in daemon mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I've seen another report of this problem on a real Cisco server, on IRC
in #maas:
have you guys tested maas (in 14.04) with disks > 2TB?
with GPT partition table
something is not right on Cisco UCS servers
ivoks: Would you happen to be seeing
https://bugs.launchpad.net/ubuntu/+source/ubiquity
The official Ubuntu system requirements include 5GB of disk space
(https://help.ubuntu.com/community/Installation/SystemRequirements), so
installing to a 2GB disk is just plain wrong.
This bug report was just bumped in priority because it's similar to
problems being experienced with other configur
I've seen this too. Sometimes the names seem to change with the kernel
-- kernel version A brings up Ethernet interfaces with sensible names
but kernel version B brings up one interface OK and another with a
"rename" name.
--
You received this bug notification because you are a member of Ubuntu
B
I'm rEFInd's maintainer, and I've just prepared a rEFInd PPA:
https://launchpad.net/~rodsmith/+archive/refind
It's still a little rough around the edges, but it gets the job done,
and it should improve in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I read Julian's comment as meaning that specifying the MAC address can
be more reliable if DHCP *IS* used to assign BMC IP addresses on a
crowded LAN. If this is correct, I recommend something more like the
following:
MAC Address -- Enter the BMC's MAC address if its IP address is likely
to change
I can confirm that this has worked much better with recent kernels, so
my comment in #16 can be ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154749
Title:
reboot does a shutdown instead o
*** This bug is a duplicate of bug 1306704 ***
https://bugs.launchpad.net/bugs/1306704
I agree it's a duplicate. I've done further testing, and FAT16, NTFS,
and ext2fs partitions all seem fine; it's only FAT32 that causes the
problem.
--
You received this bug notification because you are a m
FWIW, the problem also occurs on BIOS boots and with MBR partition
tables, not just EFI boot with GPT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306704
Title:
daily image launched from usb has
I've done some more testing, and it seems that Ubiquity, at least when
run in EFI mode on a GPT disk, wants to see a COMPLETELY BLANK disk; if
ANY partition is present, this bug occurs, which prevents installation.
Needless to say, this is an EXTREMELY serious bug.
--
You received this bug notifi
** Attachment added: "/var/log/installer/debug file from debug run"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1307134/+attachment/4082594/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
Ubiquity is producing an unhelpful error message (see attachment) on one
of my test systems after I select "Continue" in the "Preparing to
Install Ubuntu" screen. After dismissing this dialog box, nothing
happens; the mouse pointer changes to a rotating circle of dots and the
I've verified that the 3.13-23-gneric kernel does indeed fix the problem
on the systems I'd been using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300416
Title:
Install of 14.04 fails with 3.13.
I'm not sure if this is exactly the same issue that the original bug
report is about, but for me, the question is posed with no obvious way
to answer it -- see the screen shot, taken from VirtualBox. There are no
"Yes" or "No" buttons or any other obvious way to answer the question.
To shut down th
This bug has recurred with the 14.04 beta-2, as of April 3-4, 2014.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838792
Title:
"Restart" logs out, even when there are no other people logged in
To
This bug seems to be back. I initially overlooked this report, so I
filed another one:
https://bugs.launchpad.net/maas/+bug/1302604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300026
Title:
Enli
Tim, disabling the Wi-Fi radio in the firmware did not resolve the
problem. (I didn't see any other options related to Wi-Fi.) Of course,
that's moot if Seth's fix works, so I look forward to testing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
No, an Ethernet cable doesn't seem to have any effect. My initial report
was with Ethernet connected. I've since tried with it disconnected, and
the symptoms look the same. I'm attaching /var/log/syslog from the
cable-disconnected case, though, in case that gives you any more clues.
** Attachment
The installation fails and apport-collect is unavailable in the
installation environment. Therefore, I'm unable to run this command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "Output of "lspci -vnvn" on an affected machine"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056365/+files/lspci-vnvn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Attachment added: "output of "cat /proc/version_signature" on an affected
machine"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056366/+files/version_signature.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "/var/log/syslog from hung system."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300416/+attachment/4056313/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
I've tried installing the latest daily build of Trusty server, with a
3.13.0-20-generic kernel, on several Lenovo ThinkPad models (X121e,
X131e, and L330). It's failed on every one of them. The installer hangs
on an empty purple screen (see screen shot). Switching to VT4 revea
This does seem to help, but with some very big caveats:
First, I was unable to test the -generic kernel because it lacked the
mei and mei_me modules. I therefore did my testing with the -lowlatency
version of the kernel.
Second, whether the disable_msi=1 kernel option was used or not, the
system
I'm not 100% positive I'm seeing the exact same issue, but I think I am.
In my case, the xorg-edgers PPA is not installed, though. I've got a
12.04.3 installation on a Lenovo Ideapad laptop with an encrypted root
filesystem. When I boot with a stock kernel, I'm able to type my
encrypted filesystem
Upon further investigation, it seems to be the placement of the grub.cfg
file, not of the kernel, that's causing GRUB to flake out. Using
debugfs, I found that grub.cfg resides at blocks 748716118 and
748716119. Given a 4KiB block size, that works out to about the 2.79TiB
mark on the disk, which is
Public bug reported:
I performed a test installation of Trusty server to a VirtualBox
installation with a 3TiB virtual disk. I chose default options for the
most part, although I opted for a non-LVM partition layout. Ubiquity
seemed to successfully install Ubuntu, but on reboot, I got the
followin
It's referred to as an "EFI System Partition" (or sometimes a "UEFI
System Partition") in the EFI spec, so IMHO that's the name that should
be used when referring to it in any "official" way within Ubuntu.
Although there are, AFAIK, no other EFI partitions, IMHO it's important
to use the name as it
This bug still exists in the current (2/22/2014) Trusty images. The
presence of a meaningless option is likely to confuse users, or make
more knowledgeable users wonder if the tool is actually using GPT or has
created an MBR partition table by mistake.
--
You received this bug notification becaus
Public bug reported:
Ubiquity refers to the EFI System Partition (ESP) as an "EFI boot
partition." The latter name is non-standard; AFAIK, it's used *only* in
ubiquity. It's therefore potentially confusing to users, who may wonder
how (or even if) the "EFI boot partition" relates to the ESP.
Unfo
Public bug reported:
I just want to flag that I've released a new version of GPT fdisk
(gdisk) today: 0.8.9. This version optionally breaks the ties to the
libicu library; by default, it now compiles without needing that library
but still providing UTF-16LE partition name support. Thus, you might
I've traced this bug to changes introduced with the 3.2.0 kernel;
kernels up to the 3.1.9 kernel reboot just fine.
The driver provided by Samantha earlier is very similar to the 3.0.x
drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Update: I've verified this bug in a BIOS-mode boot in trusty, with a
twist: BOTH the mei AND the mei_me modules must be blacklisted in order
to cause a reboot to work. When both are blacklisted, rebooting also
works when the system is booted in EFI mode -- I suspect a failure to
blacklist mei_me ca
This bug still exists in Trusty, at least when the OCPv2 Windmill is
booted in EFI mode. Blacklisting the mei module does *NOT* work around
the problem with Trusty in EFI mode. Testing in BIOS mode will have to
wait a few more days
--
You received this bug notification because you are a membe
I'm speculating, but I suspect that this problem may have to do with the
Windows "fast startup" feature. This feature essentially turns the
"shutdown" option in Windows into something more akin to a suspend-to-
disk operation. As such, any filesystems that are mounted at the time of
"shutdown" (per
I don't have a fix for GRUB, but you *should* be able to work around the
problem by using my rEFInd boot manager
(http://www.rodsbooks.com/refind/):
1. In Linux, install the rEFInd Debian package.
2. Check the /boot/efi/EFI/refind directory. It should contain *either* a
refind_x64.efi file *or* a
Since you're using rEFInd, if you're using recent enough Linux kernels
(3.3.0 or later), you can bypass GRUB entirely. To have it pick up your
kernels automatically you may have to do some reconfiguration:
1. Set up separate /boot partitions for each distribution. Use FAT (not
supported by most
Psusi wrote: "This points to gdisk comparing the disk size to the MBR
size, rather than the GPT size."
I assure you that this is **NOT** the case! The code that computes the
disk size does **NOT** refer to MBR data structures. GPT fdisk works
fine on over-2TiB disks, for which MBR data structures
I'm the author of gdisk; psusi e-mailed me suggesting I look at this bug
report.
I believe the problem stems from an inconsistency in motherboard-based
RAID configuration or kernel drivers. Note that fdisk is reporting a
disk size of 312579695 sectors. This is an odd number, both in the
mathematic
I've verified Przemyslaw Kulczycki's report that this problem is still
present in 12.04 alpha 2. Do the developers REALLY want this bug to be
present in a long-term support release? It's only going to become more
of an issue with time. Since UEFI-based computers are now shipping in
droves, more and
Public bug reported:
Description of problem:
When creating GPT partitions for Linux filesystems, libparted uses the
Microsoft Basic Data partition type code GUID
(EBD0A0A2-B9E5-4433-87C0-68B6B72699C7). This is fine as far as Linux is
concerned, since Linux ignores partition type codes for the mos
Here's the patch to fix the problem
** Patch added: "The patch against parted 3.0 to fix this problem"
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/936661/+attachment/2760339/+files/parted-patch.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "A screen shot of Windows, showing how easy it is to trash
a Linux installation."
https://bugs.launchpad.net/bugs/936661/+attachment/2760334/+files/windows.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Adam, you've misread my comment about Windows and MBR. Allow me to
rephrase: When booted in BIOS mode, Windows will only install to or boot
from an MBR partition table (normally without a GPT, although Windows
treats hybrid MBR disks as MBR disks); and when booted in EFI mode,
Windows will only ins
Allen, Windows ties its boot support to the partition table type, so if
you have an MBR partition table, then Windows is booting in BIOS mode,
not in EFI mode. It's entirely possible that the Ubuntu installer
started up in EFI mode despite this, though, which could cause problems.
The best (or at l
I recommend that the ESP's size exceed 200 MiB. The reason is that some
boot loaders, such as ELILO, effectively require kernels to reside on
the ESP. There's also a patch to effectively make the Linux kernel its
own EFI boot loader, which would also require the kernel to reside on
the ESP. If kern
This bug's title is misleading. The BIOS Boot Partition is required (or
at least recommended), as the partition's name suggests, on *BIOS-based*
systems. On UEFI-based systems, this partition is NOT required.
The bug reported seems to be that a proper installation of grub-efi
(GRUB for EFI/UEFI sy
I've just checked Ubuntu 11.10 final release, and this bug is STILL
present! I cannot recommend Ubuntu for EFI users; working around this
bug is just too awkward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
This bug still exists in 11.10 beta 2 -- or at least, it still creates a
FAT16 ESP. (I pre-partitioned the disk on my test install, so I don't
know if the partition size issue still exists.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I'm appalled that this bug is still present in the Ubuntu 11.10 beta 2.
ERASING EXISTING OSes' BOOT LOADERS IS NOT ACCEPTABLE! Since many
(perhaps most) new computers shipping today are UEFI-based, this bug is
rapidly increasing in importance. PLEASE fix it before 11.10 goes final!
--
You rec
Public bug reported:
gdisk 0.6.14 is getting a bit long in the tooth; the current version is
0.8.0. This version includes two new programs (fixparts and cgdisk),
although I encourage splitting fixparts into a separate package, since
it's used for fixing MBR problems, vs. the other three programs i
It's possible that the bug is caused by buggy firmware, but if so it's
NOT restricted to Sandy Bridge systems. My own computer uses an Intel
DG43NB motherboard (Intel G43 Express chipset with AMI EFI 2.00) with a
Celeron E3300 CPU, which predates Sandy Bridge by quite a while. As
noted earlier, I'v
The FAT32 language exists in the EFI 1.10 spec (section 11.2, p. 11-4).
The critical first sentence you quoted is identical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769669
Title:
Installer sho
Oh, one more thing: Windows is fussy about the ESP; if it's FAT16,
Windows won't accept it as a valid ESP (although it displays as one in
the partitioning screen), and will insist on creating a new FAT32 ESP.
It will then get confused and be unable to complete its own
installation. Thus, if you ins
This bug is extremely serious. If you don't happen to have your ESP
backed up, you'll have a hard time recovering when it bites. Beyond the
obvious problem of trashing other OSs' files, even after restoring the
trashed boot loaders, if another Linux distribution referenced the ESP
via a "UUID=" ent
Another report on this: I'm using an Intel DG43NB motherboard (Intel G43
Express chipset, AMI EFI 2.00) with a Celeron E3300 CPU. I'd previously
been booting in BIOS mode with no problems, but I tried UEFI mode for
Ubuntu 11.04. I had the kernel panic on reboot, but not on shutdown.
I've tried this
I'm the author of GPT fdisk (gdisk, sgdisk). Some comments:
* There's no such thing as a "fake protective partition." The 0xEE
partition in the MBR does not correspond to any real partition in the
GPT. The purpose of the 0xEE partition is to keep GPT-unaware utilities
from messing with the disk. I
I've just heard from somebody who's destroyed the partition table on a
USB disk because of one of the bugs in this version of GPT fdisk! (The
GPT-to-MBR function in this version is broken.) The current version is
0.6.13; 0.5.1 was released OVER A YEAR AGO! *PLEASE*, either upgrade to
the latest ver
Public bug reported:
Binary package hint: gdisk
Version 0.5.1 of gdisk is woefully out of date; it was released in
December of 2009. The current version, 0.6.11, adds quite a few features
and fixes a number of bugs. (See
http://www.rodsbooks.com/gdisk/revisions.html for details.)
** Affects: gdi
Tested in Ubuntu 8.04.3 for x86-64, and it works fine there. I had to
log out and back in again to activate the updated code. (I thought I'd
try that since Charlie Kravetz reported trying removing and re-adding
the applet to the panel. Apparently either approach works.)
--
Xfce4-weather-plugin st
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28940244/Dependencies.txt
--
Weather applet displays "No Data"
https://bugs.launchpad.net/bugs/398498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Public bug reported:
Binary package hint: xfce4-weather-plugin
This bug is in xfce4-weather-plugin 0.6.2 for Ubuntu 8.04.3 LTS:
$ lsb_release -rd
Description:Ubuntu 8.04.3 LTS
Release:8.04
$ apt-cache policy xfce4-weather-plugin
xfce4-weather-plugin:
Installed: 0.6.2-1ubuntu1.1
C
93 matches
Mail list logo
