| Summary: | Summary -> Graphical gives bogus error for task-x11 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | Installer | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | feth+mageia, lovaren, mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MGA2TOO | ||
| Source RPM: | drakx-kbd-mouse-x11 | CVE: | |
| Status comment: | |||
| Attachments: |
report.bug.gz post-install
install.log |
||
|
Description
Frank Griffin
2011-05-03 22:49:13 CEST
That's with beta1, beta2 or boot.iso? Keywords:
(none) =>
NEEDINFO As I said, a fresh cauldron install - as of updates about midday today (EST).
Ahmad Samir
2011-05-04 02:06:05 CEST
CC:
(none) =>
mageia
Ahmad Samir
2011-05-04 02:06:10 CEST
Keywords:
NEEDINFO =>
(none) FWIW, this is not new. I haven;t done a fresh install for several weeks, and this happened the last time as well. I just didn't get around to reporting it. Still present in last week's Cauldron.
Manuel Hiebel
2011-10-05 14:26:30 CEST
Keywords:
NEEDINFO =>
(none) Never seen this. So I guess you're not really doing a fresh install but an update? Keywords:
(none) =>
NEEDINFO No, it's a fresh install. Moreover, it happens consistently, whether stage 2 configures graphical on its own, or leaves it until Summary (in the former case, the popup occurs during the auto-configuration). The exact scenario is a fresh install, multi-language selection English-American, Deutsch, Espanol, Francais, Italiano. Package selection is Custom with everything except Individual Packages --- all Client categories, all Server categories, and all Desktop categories. Now I think of it, the omnibus Package Selection criteria is probably pulling it in, but regardless of how it gets installed, there's no reason to pause the install just because it's already there... pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Frank Bug stil valid with Mga2A2? CC:
(none) =>
marja11 (In reply to comment #8) > pinging. because nothing happened to this report since more than 3 months ago, > and it still has the status NEW or REOPENED > > @ Frank > > Bug stil valid with Mga2A2? Ping (Mga2a3 is even better, of course ;) ) @ Frank Closing as old Please, next times you install Mageia, plug a USB stick without a report.bug on it into your computer, switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation and type: 'bug' then press Enter. It will put report.bug on the USB key. Please reopen this report if you run into the same bug again and attach report.bug Status:
NEW =>
RESOLVED Sorry, I'm not sure why I missed your posts here. It's been a while since I did a fresh install, and I really can't remember whether this happened last time. I'll keep a lokkout for it in the future. Created attachment 1769 [details]
report.bug.gz post-install
Still happening. Attaching the install files.
Created attachment 1770 [details]
install.log
Reopening. Keywords:
NEEDINFO =>
(none) you get that if select all checkbox in the package group selection ? I will try to reproduce Yes, everything but LSB, including all of the desktop choices (this is "custom", not KDE or GNOME). I get the same error, but in Mageia 1. Using boot.iso & ftp.acc.umu.se as mirror & choosing advanced installation & GNOME as only DE. No other errors during installation. CC:
(none) =>
kristoffer.grundstrom1983 Reproduced with beta 2 network installer as of April 15, 2012. Chose KDE. Install context: in KVM with a simulated Cirrus. Story: * Video was marked not configured. * Clicking on "configure" triggers the installation of 63 packages (among them, xorg drivers). * Then, a Cirrus / GD54xx-bases cards is preselected. * Error(in french): "Une erreur est survenue: Undefined subroutine &Xconfig::proprietary::handle_FIRMWARE called." * Video still marked not configured. * -> Installation transaction failed Installation of packages failed package task-x11-1:1-2.mga1.noarch is already installed Ok -> back to "Cirrus / GD54xx-bases cards" preselection. From there, loop. CC:
(none) =>
feth+mageia (In reply to comment #18) > Ok -> back to "Cirrus / GD54xx-bases cards" preselection. Same "Xconfig::proprietary::handle_FIRMWARE" if I select another driver, instead of by vendor. * cirrus * vesa * fbdev @Feth I think this is a different error, The one I reported didn't hang the install or loop. @Thierry and others In a fresh install this morning, using Anssi's new patch for Radeon, I no longer get this. I don't know if the two are related or not, since the fact that I have a Radeon chip may now be suppressing whatever tried to install task-X11 and complained about finding it there. (In reply to comment #17) > I get the same error, but in Mageia 1. > > Using boot.iso & ftp.acc.umu.se as mirror & choosing advanced installation & > GNOME as only DE. > No other errors during installation. Have to mention that MY graphicscard is this one: 82G33/G31 Express Integrated Graphics Controller This is still happening in current cauldron. I did a fresh install into a VirtualBox VM whose simulated graphics card doesn't trigger Anssi's patch, and got the same popup as before. Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO
Frank Griffin
2012-06-12 21:48:30 CEST
Keywords:
NEEDINFO =>
(none) Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D This is no longer happening in VBox, so I'm guessing it got fixed... Status:
REOPENED =>
RESOLVED |