Re: [Bug 485636] [NEW] Can not disable GRUB2 background image
Am Freitag, den 20.11.2009, 03:23 + schrieb evfool:
Public bug reported:
Binary package hint: grub2
After setting a grub2 background in /etc/grub.d/05_debian_theme by
setting the use_bg=true, and setting the image name, running
update-grub2 sets the background, at next reboot it is displayed. If i
set a non-existent image file name, update-grub2 throws an interesting
error message Generating grub.cfg ...
No path or device is specified.
Try ``grub-probe --help'' for more information.
No path or device is specified.
Try ``grub-probe --help'' for more information. This message is not
very friendly, and gives no meaningful information.
This of course shouldn't happen.
The other, and more serious problem is that after setting the use_bg
to false with an existent and working background image, update-grub2
and restart, the image is still shown. The only way to set grub2 back
to console-only mode is to set use_bg to false, and the imagename to a
non-existent image filename. This way after update-grub2 and restart,
I get the console grub2 menu again.
Uhm I'm a bit unsure if you understand basic shell scripting.
If you change
if ${use_bg} ; then
to
if false ; then
or
echo Found Debian background: `basename ${bg}` 2
use_bg=true
if you change this use_bg= to false it has the same effect.
And I just tested both now to be sure.
Note that it doestn't count what update-grub outputs or 00_header says
for the real GRUB. Only /boot/grub/grub.cfg counts for it.
If there's no background_image line in it, it will never use one.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
--
Can not disable GRUB2 background image
https://bugs.launchpad.net/bugs/485636
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485636] [NEW] Can not disable GRUB2 background image
Public bug reported: Binary package hint: grub2 After setting a grub2 background in /etc/grub.d/05_debian_theme by setting the use_bg=true, and setting the image name, running update-grub2 sets the background, at next reboot it is displayed. If i set a non-existent image file name, update-grub2 throws an interesting error message Generating grub.cfg ... No path or device is specified. Try ``grub-probe --help'' for more information. No path or device is specified. Try ``grub-probe --help'' for more information. This message is not very friendly, and gives no meaningful information. The other, and more serious problem is that after setting the use_bg to false with an existent and working background image, update-grub2 and restart, the image is still shown. The only way to set grub2 back to console-only mode is to set use_bg to false, and the imagename to a non-existent image filename. This way after update-grub2 and restart, I get the console grub2 menu again. ProblemType: Bug Architecture: i386 Date: Fri Nov 20 04:13:12 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx wl Package: grub2 (not installed) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic SourcePackage: grub2 Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:2257): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2257): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:2408): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:2420): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:2373): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Can not disable GRUB2 background image https://bugs.launchpad.net/bugs/485636 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
