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

Bug#650239: marked as done (Installation Failure)

Your message dated Sat, 20 Jul 2013 14:01:13 +0200
with message-id <201307201401.32133.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #650239,
regarding Installation Failure
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.)


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

Boot method: <How did you boot the installer? CD? floppy?
network?>"DVD" from On-Disk ("GNU/Linux 6.0 "Squeeze" - 32 bit")
Image version: <Full URL to image you downloaded is best>ditto
Date: <Date and time of the install>27 Nov, afternoon

Machine: <Description of machine (eg, IBM Thinkpad R32)>Toshiba laptop
2415-5205 (very reliable)
Processor:Pent4-M
Memory:1GB
Partitions: <df -Tl will do; the raw partition table is preferred>one
only -- no other systems present.  replaced Ubuntu, which previously
replaced Win XP

Output of lspci -knn (or lspci -nn):huh?

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [o ]
Detect network card:    [o ]
Configure network:      [ o]
Detect CD:              [o ]
Load installer modules: [o ]
Detect hard drives:     [o ]
Partition hard drives:  [ ]
Install base system:    [o ]
Clock/timezone setup:   [o ]
User/password setup:    [o ]
Install tasks:          [o ]
Install boot loader:    [o ]
Overall install:        [o ]
(The "configure the package manager" was suspiciously instantanious
and didn't clearly indicate being finished.)
Comments/Problems:Everything seemed great, and I had set some
preferences and settings.  As a last step I went for updates and
downloaded a LARGE quantity.  Upon completion I was told to restart
and did so, but the sign-in box contents were incomplete.  I got past
that with keyboard and enter's, but the desktop was unusable.  It
responded promptly to clicks with the white boxes for programs but
their contents were fragmented, very incomplete, and very slow to show
up.  Extensive hovering with the trackball encouraged some fragments
to appear, but never enough to be useful.  Ctrl+F4 worked properly.
Rebooted several times with identical results.  Shut-downs required
Ctrl+Alt+Del's.
I've done a complete re-installation in order to get online and it
again came up fast and crisp, but I prevented any updates from being
downloaded and got online with Iceweasel to send this report.  I'm
going to try to download Chrome, but no further "installation work"
until I hear from you (please!)

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>One or more of the
numerous updates screwed things up!
 --Pete Betz, Vista, CA
(Ignore vacation response you'll get from Gmail when you email me.)

--- End Message ---
--- Begin Message --- 
reassign 659211 finish-install
reassign 645757 partman-target
severity 630380 wishlist
reassign 705971 console-setup
reassign 689975 partman-partioning
reassign 675413 pkgsel
reassign 642159 apt-cacher-ng
affects 642159 debian-installer
reassign 496068 apt-setup
thanks

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 have been from a development phase where things were not stable.

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: