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

Bug#700598: marked as done (scrambled/torn display, booting wheezy weekly amd64 CD on L850/046)

Your message dated Sun, 1 Sep 2013 19:23:42 +0200
with message-id <201309011924.00219.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #700598,
regarding scrambled/torn display, booting wheezy weekly amd64 CD on L850/046
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.)


-- 
700598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700598
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Attempting to boot the Wheezy weekly amd64 CD of 2013/2/11 on  a new
Toshiba L850/046 (in EFI mode, secure boot disabled) results in
scrambled display.

The machine initiates boot from the CD, displays 'Welcome to GRUB!'
then 'Warning: "prefix is not set'.

Then the display is scrambled (like video "tearing") and confined to the
upper approx 40% of the screen.

Using the up and down arows causes small changes in this scrambled/torn
display, which are consistent with small changes to a menu - i.e. it
appears the insaller may have booted OK, but just not displaying
correctly.

In the system settings, there is no obvious item for changing the
display setting(s).

Thanks,
Neale.

--- End Message ---
--- Begin Message --- 
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: