Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1983 - Arch instalattion freeze
Attached to Project:
Arch Linux
Opened by BlackFenix (BlackFenix) - Wednesday, 05 January 2005, 17:47 GMT
Last edited by Judd Vinet (judd) - Wednesday, 05 January 2005, 18:38 GMT
Opened by BlackFenix (BlackFenix) - Wednesday, 05 January 2005, 17:47 GMT
Last edited by Judd Vinet (judd) - Wednesday, 05 January 2005, 18:38 GMT
|
DetailsSelected groups to install: base, office, X11.
Packages removed from expert menu: reiserfs tools perl wireles-tooll raidtools lilo slocate pacakges added: aterm xorg After download xorg (100%), installation freeze. No error messages. |
This task depends upon
Comment by dorphell (dorphell) -
Sunday, 09 January 2005, 17:52 GMT
Anyone able to reproduce this?
Comment by Judd Vinet (judd) -
Thursday, 10 February 2005, 21:42 GMT
Are you sure it froze? After downloading packages, pacman can take a long time (10 minutes, even) to check package integrity and file conflicts. Because of the installation dialog's textbox only receives output lines when they're terminated with a newline, it doesn't see the "checking conflicts..." message until the check is complete, making it appear as though the system has locked up.