This bug has also been reported here:
https://savannah.gnu.org/bugs/index.php?56897
I have built and installed grub 2.04 and it still doesn't deal with
metadata_csum_seed.
** Bug watch added: GNU Savannah Bug Tracker #56897
http://savannah.gnu.org/bugs/?56897
--
You received this bug notific
** Description changed:
/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub softwa
** Description changed:
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-g
** Description changed:
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-g
** Summary changed:
- grub2 doesn't recognize ext4 with metadata_csum enabled
+ grub2 doesn't recognize ext4 with metadata_csum_seed enabled
** Description changed:
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2
Public bug reported:
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum set.
This is true in command-line grub, not just the update-grub software.
Attempting
So glad I switched back to Debian years ago...
Chris Coulson wrote:
> Ah, ok. gnome-wm will try to start compiz by default still. That's a low
> importance issue though. Compiz is installed by default and most users
> won't uninstall it.
>
> ** Changed in: gnome-session (Ubuntu)
> Importance:
No idea what happened with that. I switched back to Debian.
Andreas Moog wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
Don't know. I haven't seen the crash in months, but I'm running
Debian.
Risto H. Kurppa wrote:
> Does this possibly have something to do with this:
> https://bugs.launchpad.net/ubuntu/+source/meta-kde4/+bug/246557
>
>
--
x crashes when using kde4.0 not with kde 3.5.8
https://bugs.launchpad.ne
The more recent release of kde4, 4.0.0.1 I think, has options to control
fancy desktop
effects. So far all I know is that enabling these in general causes a sig11;
probably the
actual X functionality in question could be determined by selectively enabling
different
desktop effects.
I'd be mo
They still haven't fixed this? Sad. Haven't been keeping track; I mostly gave
up on Ubuntu and
went back to Debian when they labeled another bug I reported involving compiz
and gnome, again
caused by incompetent scripting, as a 'Wishlist' item.
--
function load_optimized_aes_module broken
htt
I should note that this behavior is seen with:
Ubuntu/Hardy/latest KDE4 with both via and openchrome drivers;
Debian/unstable with via driver (they don't have openchrome) and
latest KDE4.
My understanding is that the acceleration offered by the Unichrome chip is
pretty limited. Probably
** Attachment added: "klauncher gets SIGSEGV"
http://launchpadlibrarian.net/11587652/_usr_lib_kde4_lib_kde4_libexec_klauncher.1000.crash
--
x crashes when using kde4.0 not with kde 3.5.8
https://bugs.launchpad.net/bugs/182599
You received this bug notification because you are a member of Ub
It is definitely a bug in some combination of the KM400 Unichrome hardware
and the X code. I get the
same thing, with either the via or openchrome drivers, unless I do Option
"NoAccel" (painful). Tried lots
of combinations of disabling DRI, GLX, AGPDMA, COMPOSITE, etcetc, and with the
openchro
Public bug reported:
Binary package hint: locales
English UTF-8 once again, with both gutsy and hardy, produces garbage on
screen
when aptitude is run in either Eterm or mrxvt. Aptitude works OK in
gnome-terminal,
which I don't use because it takes forever to start.
The patch for now, as d
The attached patch is simply a diff of the current (Hardy) /usr/bin/gnome-wm
and the current
Debian/unstable /usr/bin/gnome-wm. I've had to fix the Ubuntu version of
/usr/bin/gnome-wm for
some months every time a new version is installed, since it sets one's wm to
compiz whether or
not compiz
** Description changed:
Binary package hint: cryptsetup
I hope you can fix this before the 7-10 release, as it breaks
/etc/init.d/cryptdisks functionality
on any machine without an asm-optimized aes module.
In /lib/cryptsetup/cryptdisks.functions, the load_optimized_aes_module
Public bug reported:
Binary package hint: cryptsetup
I hope you can fix this before the 7-10 release, as it breaks
/etc/init.d/cryptdisks functionality
on any machine without an asm-optimized aes module.
In /lib/cryptsetup/cryptdisks.functions, the load_optimized_aes_module
function
breaks
Quite. Choosing the hex-gibberish option for initial
installations for new users is all well and good, but forcing the adoption of
this for existing installations is another matter, a philosophy of Free
Software incompatible with mine.
--
edgy update-grub destroys kopt
https://launchpad.net/
Thanks for your reply.
1) If I don't want to use UUIDs, but prefer labels or the time-honored way, do
I need to drop Ubuntu in favor of Debian
or is there still a choice in the matter?
2) Kernel doesn't boot when update-grub has mangled my kopts.
"No Root", etcetc. Apparently can't find it.
3)
** Description changed:
Binary package hint: grub
- update-grub in ubuntu has new and, for me, entirely
- unwanted functionality which is broken, incorrect and
+ update-grub in edgy has new and, for me, undesirable functionality which
renders the system unbootable without skilled interventi
Public bug reported:
Binary package hint: grub
update-grub in ubuntu has new and, for me, entirely
unwanted functionality which is broken, incorrect and
renders the system unbootable without skilled intervention.
1) update-grub should not mess with kopt at all, except
in the case of an initial i
22 matches
Mail list logo
