| Summary: | Install fails immediately in getInputDevices() (and later in libDrakx/ugtk2.pm) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | Installer | Assignee: | Pascal Terjan <pterjan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia, marja11, pterjan, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-kbd-mouse-x11 | CVE: | |
| Status comment: | |||
| Attachments: | Screehshot of the log (posted by ennael on irc) | ||
|
Description
Frank Griffin
2011-03-29 20:27:50 CEST
You set the bug report status to ASSINGED, are you working on a patch/fix? Keywords:
(none) =>
NEEDINFO
Ahmad Samir
2011-03-29 22:21:35 CEST
CC:
(none) =>
mageia, thierry.vignaud Seem the default status has changed somehow... I'll alert the bugzilla maintainer. Status:
ASSIGNED =>
NEW Created attachment 173 [details]
Screehshot of the log (posted by ennael on irc)
(In reply to comment #1) > You set the bug report status to ASSINGED, are you working on a patch/fix? No, as you noticed, that was the status right after I entered it.
Olivier Blin
2011-03-29 23:41:46 CEST
Summary:
Install fails immediately in libDrakx/ugtk2.pm =>
Install fails immediately in getInputDevices() (and later in libDrakx/ugtk2.pm) Can the whole log be attached? What environment was used? Is there an available log this early on ? My environment was an HTTP install of x86_64 from a local cauldron mirror. It was a standard desktop system with a PS/2 mouse and keyboard accessed through a KVM. The install has worked on this hardware since forever. Resolved by Pascal Terjan Status:
NEW =>
RESOLVED
Thierry Vignaud
2011-04-01 11:24:42 CEST
Source RPM:
(none) =>
drakx-kbd-mouse-x11 I would not say this is a fix, this is an ugly workaround as a patch in the package... A proper fix is still needed Keywords:
NEEDINFO =>
(none)
Pascal Terjan
2011-04-01 11:47:36 CEST
Assignee:
bugsquad =>
pterjan (In reply to comment #8) > I would not say this is a fix, this is an ugly workaround as a patch in the > package... > A proper fix is still needed @pterjan Any news? CC:
(none) =>
marja11 pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Pascal Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Pinging, because nothing has happened with this report for more than 3 months, it still has the status REOPENED. Hmm forgot about that one. I'll try to have a look tomorrow. 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:46:26 CEST
Keywords:
NEEDINFO =>
(none) drakx is frozen for mga2 Whiteboard:
MGA2TOO =>
(none) (In reply to comment #14) > drakx is frozen for mga2 That is true. Now putting (MGA2) on the whiteboard, only to make clear this isn't some old cauldron bug that was only valid long before Mageia 2 stable (or in this case even before Mageia 1 stable), but that it was still seen in Mageia 2. It doesn't count as setting version to "2" Whiteboard:
(none) =>
(MGA2) 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 has been effectively fixed for ages, but I'm not sure the solution is the ultimate one desired (based on comments above). It needs a judgment call on where it goes from here. code changed to ugtk3.pm Status:
REOPENED =>
RESOLVED No it's not fixed Status:
RESOLVED =>
REOPENED Pascal please consider a fix? Whiteboard:
(MGA2) =>
(none) Closing Status:
REOPENED =>
RESOLVED |