| Summary: | choqok startup splash displayed as blank | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Neil Darlow <neil> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | juan.baptiste, rverschelde |
| Version: | 3 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | qt4-4.8.1-2.mga2.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Neil Darlow
2012-05-16 21:40:32 CEST
do you know the upstream bug if they have make one ? :) Keywords:
(none) =>
PATCH, UPSTREAM do you know the upstream bug if they have make one ? :) Keywords:
PATCH =>
(none) I have no idea. I raised this bug report so that the breakage is documented before the, inevitable, complaints come flooding in. For me it's not a big issue, the upstream developer is aware of the situation and a future update of Qt will hopefully fix it. It's just a case of monitoring future Qt releases and backporting the fix when it arrives. 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
Manuel Hiebel
2012-06-12 21:10:59 CEST
Keywords:
NEEDINFO =>
(none)
Manuel Hiebel
2012-06-12 21:11:16 CEST
Whiteboard:
(none) =>
MGA2TOO There's a new choqok version 1.4 already available in cauldron, and probably will also be pushed to mga 3 and 2. http://choqok.gnufolks.org/2013/09/choqok-1-4-released/ CC:
(none) =>
juan.baptiste What is the status about this bug? I see that choqok 1.4 is available in core/updates_testing in Mageia 3. CC:
(none) =>
remi
Rémi Verschelde
2014-08-20 09:23:32 CEST
Hardware:
i586 =>
All Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |