Public bug reported:
Err:6 http://ftp.jp.debian.org/debian unstable InRelease
The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY
04EE7237B7D453EC
** Affects: debian-archive-keyring (Ubunt
This feature is in e2fsprogs 1.43, which is in yakkety (16.10). The bug
can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348431
Title:
-O inline_data not supported by Ubuntu e2fsprogs
Have verified that `mkfs.ext4 -O inline_data` works with the yakkety
e2fsprogs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348431
Title:
-O inline_data not supported by Ubuntu e2fsprogs
To mana
Still getting this when going 14.04->16.04. It complained about my
kernel image package. I upgraded to the latest kernel, removed all older
kernel packages, now it complained about my fresh installed kernel
package.
What does this even mean? What is it authenticating?
Trying the disabling config
Yep, still getting this tty spam multiple times every time update-grub
runs from apt. Not when running update-grub, not when running dpkg-
reconfigure linux-image-*, only when running apt install. So probably
this should be a bug on apt.
Suppressing it by setting LVM_SUPPRESS_FD_WARNINGS works, of
Thank you Daniel and Theodore for your feedback!
I tried merging pu into maint the other day, but it didn't apply
cleanly. I will try again later.
When I get around to trying it out, I will go with your recommendation
and use the latest mainline.
--
You received this bug notification because yo
The bug has been fixed in -proposed.
Performed the test in the bug description. The `128` file accurately
points to a 128 bytes long filename. Double-checked that the file system
was actually using -O inline_data. Disk usage reflects it as well:
# du ext4{,_inline}/test{/*,}
4 ext4/test/128
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349020
Title:
inline_data option on ext4 truncates symlinks
To man
That fixes the bug. Even symlinks created by the faulty kernel will be
interpreted correctly by the fixed kernel, as the fault is in reading,
not in writing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
To replicate the bug, create two filesystems, one with `mkfs.ext4 -I
256`, one with `mkfs.ext4 -I 256 -O inline_data`. An inode size of 256
bytes is the default, but included here for clarity. To do this, you are
going to need an `e2fsprogs` from trunk, or version 1
Public bug reported:
To replicate the bug, create two filesystems, one with `mkfs.ext4 -I
256`, one with `mkfs.ext4 -I 256 -O inline_data`. An inode size of 256
bytes is the default, but included here for clarity. To do this, you are
going to need an `e2fsprogs` from trunk, or version 1.43 if it h
... so this will be fixed whenever 1.43 is released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348431
Title:
-O inline_data not supported by Ubuntu e2fsprogs
To manage notifications about this
`pu` was merged into `next`/`master` early March 2014.
** Branch linked: lp:~vcs-imports/e2fsprogs/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348431
Title:
-O inline_data not supported by
Public bug reported:
Since kernel version 3.8, ext4 supports the file system option
inline_data to put file content into the inode itself as an extended
attribute. However, this feature cannot be enabled using the included
e2fsprogs in Trusty Tahr. If it has been enabled for a file system, boot
e2
Public bug reported:
I have both precise and quantal in my sources.list.
Whenever I do an `apt-get install linux-image-generic/quantal` and there
is a ~precise version similar to the version linux-image-generic depends
on, apt-get always picks the precise version first, which contains all
the fil
I confirm that 2.6.37-rc8 works on my Lenovo U160 with an U5400.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608907
Title:
[lucid][maverick][i915] Lenovo U160 Intel i7 620UM blank screen
--
ubun
** Bug watch added: Red Hat Bugzilla #596557
https://bugzilla.redhat.com/show_bug.cgi?id=596557
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=596557
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
Latest drm-intel-fixes solves the problem for my i5 U160! Big hug to
Chris Wilson and happy holidays to all the hard-working übergeeks making
our lives better every day!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I have a U160 with a 8086:0046 chip and Xorg reports the display as EDID
vendor "AUO", prod id 12380.
Tried running 2.6.37-rc5, which as far as I understand is up-to-date
with intel-drm. Problem persists.
If I boot without "nomodeset" the machine boots with the screen lit, but
black. Also, it doe
19 matches
Mail list logo
