[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#612506: marked as done (support handing through i/o errors to X)

Your message dated Wed, 19 Jun 2013 07:30:02 +0200
with message-id <51C141DA.5050305@progress-technologies.net>
and subject line Re: support handing through i/o errors to X
has caused the Debian Bug report #612506,
regarding support handing through i/o errors to X
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
612506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612506
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: live-boot
Version: 2.0.15-1
Severity: wishlist

Steps to reproduce:
1) script -c 'set -x; ls -a; sudo lb config --packages "gnome wireless-tools wpasupplicant" -d squeeze -b usb-hdd -p standard-x11 -m http://apt-proxy:9999/debian --bootappend-live "live-config.keyboard-layouts=fi" --linux-flavours 486 --binary-indices false --apt apt --memtest memtest86+ --debian-installer live --debian-installer-gui true --win32-loader false && sudo lb build'
2) write the resulting binary.img to an USB drive
3) boot the USB drive

Expected results:
3) the live system either boots or informs the user about an error

Actual results:
3) At a low probability the boot fails. User sees just a green
background and a mouse cursor that can be moved. Screenshot is
attached as gnome_green_background1.jpg

More info:
1) This happens quite rarely, rebooting the computer was enough to
make it boot successfully. The cause of the failure is not important
here. This wishlist bug is about improving error reporting so that
people can detect and report such failures in the first place.
2) When I told the user that he should try ctrl-alt-f1 he was able to
see squashfs read errors. Attached as squash_error_unable_to_read_page1.png
3) md5sum -c md5sums.txt says "OK" for all files
4) Would it be possible to switch out of X if read errors are
detected? Would KMS make it possible for kernel to print the errors on
top of X?

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Attachment: gnome_green_background1.jpg
Description: JPEG image

Attachment: squash_error_unable_to_read_page1.png
Description: PNG image


--- End Message ---
--- Begin Message --- 
Thinking about this again, I'm afraid this is not fixable at all in a
generic way and the only thing you can rely on is to educate people to
look at the logs (as in 'switch to tty1 and read the messages shown there).

-- 
Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:          daniel.baumann@progress-technologies.net
Internet:       http://people.progress-technologies.net/~daniel.baumann/

--- End Message ---
Reply to: