Gc reboots lucid after root password

Asked by Stanz

After giving root password, the system seems to freeze & simply reboots!
I've been trying to run it using gdb {no dbg from synaptic?}, but can't get anything into the file after entering 'run'.
Only when forgetting to 'sudo gdb...' did I have GC window come up and see it.
It was shaded and I got another window reminding me: 'needs root privy'.

This is fresh install 10.04.1, and updated as they come in.
GC has worked for me on 10.04-2, so I'm wondering why.
What can I do to collect & offer some info?

Update:: This finally got a bug report.
Also this is still present in Lucid 10.04-3

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu hwinfo Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Daniel Richter (danielrichter2007) said :
#1

What happens, if you run other applications using su-to-root, eg. "su-to-root -X -c gedit"

Also you could try these commands (they'll be executed when starting grub customizer):

sudo grub-mkconfig
sudo hwinfo --framebuffer

Revision history for this message
Stanz (stanz) said :
#2

su-to-root -X -c gedit, gedit opens- no problem.

$ sudo grub-mkconfig
[sudo] password for stanz:
Generating grub.cfg ...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set a04b8229-a028-4b9a-a958-aa129d47c837
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=800x600
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set a04b8229-a028-4b9a-a958-aa129d47c837
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
Found linux image: /boot/vmlinuz-2.6.32-31-generic
Found initrd image: /boot/initrd.img-2.6.32-31-generic
menuentry 'Ubuntu, with Linux 2.6.32-31-generic' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set a04b8229-a028-4b9a-a958-aa129d47c837
 linux /boot/vmlinuz-2.6.32-31-generic root=/dev/sda1 ro splash vga=788 quiet splash
 initrd /boot/initrd.img-2.6.32-31-generic
}
Found linux image: /boot/vmlinuz-2.6.32-30-generic
Found initrd image: /boot/initrd.img-2.6.32-30-generic
menuentry 'Ubuntu, with Linux 2.6.32-30-generic' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set a04b8229-a028-4b9a-a958-aa129d47c837
 linux /boot/vmlinuz-2.6.32-30-generic root=/dev/sda1 ro splash vga=788 quiet splash
 initrd /boot/initrd.img-2.6.32-30-generic
}
Found linux image: /boot/vmlinuz-2.6.32-24-generic
Found initrd image: /boot/initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set a04b8229-a028-4b9a-a958-aa129d47c837
 linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda1 ro splash vga=788 quiet splash
 initrd /boot/initrd.img-2.6.32-24-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
Found Ubuntu Natty (development branch) (11.04) on /dev/sda5
menuentry "Ubuntu, with Linux 2.6.38-8-generic (on /dev/sda5)" {
 insmod ext2
 set root='(hd0,5)'
 search --no-floppy --fs-uuid --set 997af238-7923-4a1f-af76-5125faabf8e0
 linux /boot/vmlinuz-2.6.38-8-generic root=UUID=997af238-7923-4a1f-af76-5125faabf8e0 ro splash vga=788 quiet splash vt.handoff=7
 initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry "Ubuntu, with Linux 2.6.38-8-generic (recovery mode) (on /dev/sda5)" {
 insmod ext2
 set root='(hd0,5)'
 search --no-floppy --fs-uuid --set 997af238-7923-4a1f-af76-5125faabf8e0
 linux /boot/vmlinuz-2.6.38-8-generic root=UUID=997af238-7923-4a1f-af76-5125faabf8e0 ro single splash vga=788
 initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry "Ubuntu, with Linux 2.6.38-7-generic (on /dev/sda5)" {
 insmod ext2
 set root='(hd0,5)'
 search --no-floppy --fs-uuid --set 997af238-7923-4a1f-af76-5125faabf8e0
 linux /boot/vmlinuz-2.6.38-7-generic root=UUID=997af238-7923-4a1f-af76-5125faabf8e0 ro splash vga=788 quiet splash vt.handoff=7
 initrd /boot/initrd.img-2.6.38-7-generic
}
menuentry "Ubuntu, with Linux 2.6.38-7-generic (recovery mode) (on /dev/sda5)" {
 insmod ext2
 set root='(hd0,5)'
 search --no-floppy --fs-uuid --set 997af238-7923-4a1f-af76-5125faabf8e0
 linux /boot/vmlinuz-2.6.38-7-generic root=UUID=997af238-7923-4a1f-af76-5125faabf8e0 ro single splash vga=788
 initrd /boot/initrd.img-2.6.38-7-generic
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
done

sudo hwinfo --framebuffer
--That made the system reboot--

Revision history for this message
Stanz (stanz) said :
#3

I'll try again with the hwinfo, because info kinda flashes by, before rebooting.
I believe the last output is like:
>bios: 4. vbe

Revision history for this message
Stanz (stanz) said :
#4

Different this time:
>bios: 2. rom
anything else I can do? : (

Revision history for this message
Stanz (stanz) said :
#5

Using my root terminal, I type: # grub-customizer
{I see 4 or 5 lines like this}

checking for the grub install command {last I can see & read}
(looks like a folder location here) /usr/ ? / {reboots to quick!}

Revision history for this message
Daniel Richter (danielrichter2007) said :
#6

The problem is, that Grub Customizer starts hwinfo to fetch the available grub resolutions (will be displayed in the setting dialog). If you run Grub Customizer without root privileges, hwinfo fails - so nothing happens.

But hwinfo is only a recommend of grub customizer - not a dependency. So you could uninstall this package - after doing this, the only difference in gc is, that you cannot choose the resolution from a list.

Alternatively you could try to find out, why hwinfo crashes by asking its developers.

Revision history for this message
Stanz (stanz) said :
#7

Thanks for your swift attention here! I used Gc on my last lucid install with no ill effects and I thank ya for your time into this fine program.
I'll uninstall hwinfo and post result. Then do a bug report for hwinfo, linking this question and giving somekind of info to them.

stanz

Revision history for this message
Stanz (stanz) said :
#8

Thanks Daniel Richter, that solved my question.

Revision history for this message
Stanz (stanz) said :
#9

linked to bug report!

Revision history for this message
Stanz (stanz) said :
#10

Daniel Richter, solved my question.
I thought to re-open the question, with the bug report.

Revision history for this message
Launchpad Janitor (janitor) said :
#11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.