Bug 146520 - Update from 10.0 to 10.1 over network can be very slow and lacks a progress indicator immediately after starting YaST and before the download of the rpms starts
Summary: Update from 10.0 to 10.1 over network can be very slow and lacks a progress i...
Status: RESOLVED DUPLICATE of bug 141154
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 2
Hardware: 32bit Other
: P4 - Low : Enhancement (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-29 18:51 UTC by Forgotten User RJc1X_JQ_W
Modified: 2006-07-17 13:43 UTC (History)
3 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User RJc1X_JQ_W 2006-01-29 18:51:07 UTC 
When choosing update (not new install) the installer hangs indefinetly.

On a console I can see that it tried to launch X11 with /etc/X11/xorg.conf
and fails to load the glx module (EE).

Is the update procedure using the original xorg.conf from the installed 10.0 system?

On my test system this means that the xorg.conf is configured for the proprietary ATI driver and glx.

Making the update procedure dependent on the old xorg.conf would imho be wrong because the upgrade procedure cannot make sane assumptions about it.
Comment 1 Martin Lasarsch 2006-01-30 10:14:52 UTC 
when does it start to hang? what is the last thing you see on the screen?

please provide /var/log/YaST/*
Comment 2 Forgotten User RJc1X_JQ_W 2006-01-30 13:28:11 UTC 
> when does it start to hang? 

The image is correctly downloaded via ftp. Then the ncurses based linuxrc is changed to the X11 based YaST. YaST shows the selection of either "update" or "new install".

When choosing "new installation" a busy cursor (little blue clock) appears and nothing happens.

> what is the last thing you see on the screen?

Busy cursor.

When switching to a console using Ctrl-Alt-F? I can see errors from X which claim that the fglx driver and the glx module cannot be loaded/found.

Please answer my question: "Is the update procedure using the original xorg.conf from the installed 10.0 system?"

> please provide /var/log/YaST/*

How to provide /var/log/YaST/*? 

How am supposed to transfer this file from the system to Bugzilla? 

IMHO providing some simple tool in the installation image 
like a command line ftp client would be more than helpful.
Comment 3 Michael Gross 2006-01-30 14:51:06 UTC 
Martin: You can use a floppy, a memory stick or just any harddisk and mount it during the installation, if the system does not freeze completely (try chaning the consoles with Alt+F1, Alt+F2, ...). You can find the logs under /var/log/YaST/*, pack them into a tar file and store it on your media or your harddisk and attach them here using the attachment-feature (see further below on this page). Are you using the network installation image or the normal version?
Comment 4 Forgotten User RJc1X_JQ_W 2006-01-30 21:52:56 UTC 
Thanks for you detailed explaination. Maybe the hints should be put in the opensuse wiki?

I am using the network installation image.

I checked the logs in /var/log/YaST/ and detected that it was just taking _very_ long to download the required files from ftp.gwdg.de. 

So the original bug description is wrong. It is indeed working but the user is lacking feedback. (For a very long time only a busy cursor is shown).

Proposed usability improvement:
1. Warn user that it can take very long over slow links. Maybe doing an educated guess with the download time required for the image. This time is already available.

2. Show some kind of progress to the user

3. Avoid the downloading of unnecessary data. E.g. the user has already chosen a language long before so there is no need to download chinese language slides...

I changed the severity from blocker to enhancment because basic functionality is working.
Comment 5 Christian Boltz 2006-01-31 00:00:20 UTC 
sounds like bug 146521, but I'm not really sure.
Comment 6 Michael Gross 2006-01-31 10:49:16 UTC 
Sounds reasonable. There should really be some information about what's currently done and some kind of progess that shows to the user that something is done, even if it is poorly slow. It wouldn't be to bad to add the possibility to cancel the download.

As for the Wiki: I'm quite sure it is described there ;)
Comment 7 Dirk Stoecker 2006-05-18 14:28:48 UTC 
I would think this is equal to bug 141154.
Comment 8 Jiri Srain 2006-07-17 13:43:34 UTC 
Right, this is duplicate, and not the only one ;-)

*** This bug has been marked as a duplicate of 141154 ***