Bug 154090 - if packages fail, the abort button does not work
Summary: if packages fail, the abort button does not work
Status: RESOLVED DUPLICATE of bug 150379
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 5
Hardware: All Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Klaus Kämpf
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-28 12:31 UTC by Olaf Hering
Modified: 2008-07-16 15:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2006-02-28 12:31:46 UTC
the abort button in the 'Installation of package $foo failed.' window has has Abort, Retry, Ignore buttons, but the Abort does not stop the package install.
Comment 1 Michael Gross 2006-02-28 12:45:49 UTC
Do you mean the installation of this specific package or the whole package installation?
Comment 2 Olaf Hering 2006-02-28 13:47:26 UTC
it just continues with installing the remaining packages. I would expext 'Abort' to abort the package install process.
Comment 3 Michael Gross 2006-02-28 14:28:31 UTC
I don't know if this was intended that way, but I think a dialog for a single package would only abort this specific one. Note that the abort button still does not appear to work (bug #153929). Reassigning to Klaus for a comment.
Comment 4 Olaf Hering 2006-03-01 09:18:03 UTC
same is true when the disk is full.

'Disk space nearly exhausted, continue <yes> <no>'

selecting no will not abort.
Comment 5 Bernhard Heibler 2006-03-05 20:31:10 UTC
BETA6: It seams that that the abort function in the installer doesn't work at all. If I just hit the abort button during installation a confirmation dialog will appear but if I confirm to abort the installation will continue
Comment 6 Michael Gross 2006-03-08 12:15:25 UTC
I'd say we reopen bug #150379 for this and marking this one as a duplicate.

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