I tried a fresh network HTTP install today, and ran into an odd problem. I had a local MGA4 cauldron tree on one of the system's partitions, and had it mounted by the install diskdrake as /mga4. In spite of the fact that this was a network install, the install got horribly confused during package selection. When I switched to VC3, messages were flying by about packages being placed in the rejected list. On a hunch, I aborted the install and restarted it, but this time did not mount the /mga4 partition, and the install went fine. I couldn't find any of the usual /root/drakx or /root/tmp report files, so there was really nothing to collect. It seems the presence of the unrelated mga4 tree caused mga4 packages to somehow get inserted into the mix. If someone can recommend a diagnostic procedure, I can probably recreate this. Reproducible: Steps to Reproduce:
/root/drakx/report.bug.xz is generated at end of install /root/drakx/ddebug.log is updated regularly as soon as / is mounted. When you'll try again, just run the "bug" command once you've encountered the bug: - plug a USB key - got to tty2 - type the "bug" command - attach to this bug report the report.bug file you'll found on your key (you can compress it)
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
I'll try it today. I may have been looking on the wrong /. But, fair warning, I can't be sure whether the install ever would have ended. I usually select all package categories, so it's not clear whether this was just a lot of activity for each package or a loop.
It won't reproduce. I tried the exact selection of partitions that failed before, as well as some other configurations including the mirror partition. The only possibility I can think of is language selection. All of the packages I saw mentioned on VC3 were libreoffice i18n or i10n packages. I select multiple languages (English, Francais, Espanol, Italiano, Deutch), but since the window behavior has changed (click on scrollbar no longer does page up/down, but relocates display to the clicked location), I had to go back to the top, click on the display to give it focus, and use page up/down to get to my selections. The language selections seem to extend all the way across the display, so that if you click anywhere on the line it selects that language (I've always found that very convenient), so it's possible that in giving the top page of the language display the focus, I inadvertently selected some language which caused the problem. The second time around, I probably didn't. I'll try that combination later today, and enter a different report if I can cause the problem that way.
Status: NEW => RESOLVEDResolution: (none) => INVALID