I believe the primary use case would be when you wish to target the
volume (i.e. grub-install /dev/sda1).
If the concern is size, this has been officially resolved with Boot Area
B's specifications.
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg34016.html
We do leave the first
Tried again lately? It appears OK but if not I'd make note of the IP
address to which it attempts to fetch from. `netstat -tn|grep :80` or
a similar command may help.
** Changed in: vmware-view-client (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you
rubo77: fsck.btrfs at this time can not fix errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619575
Title:
btrfs-tools fsck bug can cause data loss
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: os-prober
In testing Ubuntu-11.04-beta1 (Natty), I configured a 3 GB partition
(sda1) as btrfs. This can boot with minor adjustments (resolved already
in current beta/daily). The default Ubuntu install creates two
subvolumes, @ and @home when using a
1) I'd classify the need to have legacy USB support as a BIOS bug. Any
relatively modern full OS will have USB HID support by default. DOS (by
default) and Syslinux have no USB HID support. Grub2 has optional USB
HID support when set by the configuration.
2) With regards to the Syslinux
Correction: I forgot the mount option subvol=@. Specifying this
resolves all issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757446
Title:
grub2: btrfs: not known to reserve space for
Public bug reported:
Binary package hint: grub2
btrfs reserves the first 64kiB for boot loaders as its CoW (Copy-On-
Write) features mean that a file may change logical blocks. This area
may also be referred to as the embed area, embedded area or
embedding area, depending on the context.
Fails. With the almost untested patch I just got today, it almost
worked. I got to a grub rescue prompt. Using the commands 'set
prefix=(hd0,msdos1)/@/boot/grub; insmod normal; normal' (you noted this
in bug 712029;
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/712029 ),
everything
Public bug reported:
Binary package hint: grub2
# grub-install /dev/sda1
/usr/sbin/grub-setup: error: hd0 appears to contain a btrfs filesystem
which isn't known to reserve space for DOS-style boot. Installing GRUB
there could result in FILESYSTEM DESTRUCTION if valuable data is
overwrittten
A workaround that I discovered while fumbling with things is to not
create it in the more straight forward fashion.
Click KNetworkManager's system tray icon, click Manage Connections.
Under Network Connections on the left, click the Wireless tab on the
right then click Add. At this point,
gcc-mingw32 contains /usr/lib/gcc/i586-mingw32msvc/4.4.2/libgcc.a for
the creation of 32-bit Windows (i586) code but the same does not exist
(along with a bunch of other lib*.a files) for the amd64 target.
--
lack of libgcc.a for amd64-mingw32msvc-gcc
https://bugs.launchpad.net/bugs/640181
You
*** This bug is a duplicate of bug 568028 ***
https://bugs.launchpad.net/bugs/568028
gcc-mingw32 for Maverick (10.10) on amd64 and i386 contains
/usr/lib/gcc/amd64-mingw32msvc/4.4.4/libgcc.a as of 2010-09-19. Is
there any way the changes needed could be incorporated into gcc-mingw32
for
Copying my comments from bug # 640181.
gcc-mingw32 contains /usr/lib/gcc/i586-mingw32msvc/4.4.2/libgcc.a for
the creation of 32-bit Windows (i586) code but the same does not exist
(along with a bunch of other lib*.a files) for the amd64 target.
gcc-mingw32 for Maverick (10.10) on amd64 and i386
PC working is only with wired network. ;-) Nice.
But this bug is not dedicated to the WLAN security! It should solve
the missing ability of connecting to an AP with a hidden SSID. True.
I've had some success with Ubuntu Maverick Merrkat 10.10 Alpha 3 but I
want to do some more testing between
I'm merely a user like you, not really someone in Canonical or working
closely with Ubuntu. I just happen to be affected by it and have the
equipment/resources to test.
There are means by which you can manually configure your WLAN card but
it's all command-line based and easier if you remove it
(Corrected from the off-topic rant I first wrote before submission)
I will agree that connecting to a non-broadcasting SSID would be a
preferred feature when traveling to a network that you don't manage. I
agree on this ability solely for this purpose and not because you want
to use old insecure
Public bug reported:
Binary package hint: bash-completion
_expand() in /etc/bash_completion, a part of bash-completion, does not
acknowledge the readline variable expand-tilde as of version
1.1-3ubuntu2.
Typing 'ls ~/tab' currently results in the command being expanded to
'ls /home/user/', even
If I were to guess, a part of the issue with the bug acting dead is
the lack of a proper package association. I just installed the package
that is the owner of the appropriate file in my distro, (K)Ubuntu 10.04.
The file /usr/include/c++/4.4/cstdio is owned by libstdc++6-4.4-dev
however your
sudo only ever asks for your password. When the prompt says '[sudo]
password for ubuser:', it wants the password for the user ubuser.
So, in a terminal, you entered 'echo options i915 modeset=1 | sudo tee
/etc/modprobe.d/i915-kms.conf' (without the quotes, of course), entered
your password at
I've been trying from the official Lucid Lynx 10.04 x64 CDs, installing
locally to the laptop. I first tried Kubuntu but when I started
experiencing this issue, I also tried Ubuntu, both with current updates
(as of the time that I had it running). Currently, I'm running Kubuntu.
I have,
Separately, I can confirm that Kubuntu 8.04 does have a full workaround.
Many times, I have attempted to store the configuration of the same WLAN
as above to no avail.
Workaround: manually configure it every user session that I want to
connect to the WLAN. This is only effective if you know the
After researching the fact that turning off the SSID broadcast (aka
hidden SSID, SSID cloaking) is against the standard, I feel that any
time a checkbox is included to use a non-broadcasting SSID (at least on
the APs), it should pop-up a warning that it's not a security feature,
breaks the
How about something simple: Clicking the button/text will present a pop-
up acknowledgment that will inform the user that it will attempt to
update the installer but that an internet connection must already be
configured. If proxy information is required, boot to the live CD
session, configure
I just attempted to do a fresh install on a system with a similar
chipset and found this page:
https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
Apparently, this is a known issue. Using the first workaround worked
perfectly. Append the kernel command line parameter 'i915.modeset=1'
and all is
Public bug reported:
install-css.sh (at /usr/doc/libdvdread4/install-css.sh) in package
libdvdread4-4.1.3-5ubuntu2 does not fetch current version of libdvdcss2.
Fetches libdvdcss2_1.2.10-0.2medibuntu1_amd64.deb
The design question is whether to always update the script (and as a
result, the package) when Medibuntu releases a new version (as I think
is the current design) or to design it dynamically with a static fall
back.
By this, I mean fetch the current repository list (I think
I've tested this and so far things work well. It doesn't query the
source list but does query and parse the current Packages list.
** Patch added: Change install-css.sh to use current Packages list.
http://launchpadlibrarian.net/38836907/install-css-100102061332.diff
--
libdvdread:
I personally can confirm the issue. I first noticed it with another
Linux distro (a rescue distro) that loaded menu.c32 by default. From
syslinux 3.53 to 3.61, the bug existed. The last patch (to the syslinux
core/) before 3.62 resolved the issue. 3.62 and later work without any
known issues
28 matches
Mail list logo
