Description of problem: Djl game manager is no longer working. It displays the error: QWidget: Must construct a QApplication before a QPaintDevice /usr/games/djl: line 4: 28192 Aborted python -O djl.py $* The application itself is abandoned by its author. The latest release is from 15 Jan 2010 and the latest entry in the changelog is from 2009/10/18. ""This is what the author himself said on February 2011: Hi, You know, I've been the main djl's developper and I don't work on it anymore, so djl is out of date himself ^^ I think about a new software based on Qt/C++ more likelly as Valve's Steam, but it's just a project on the box for now. I'm sorry if you use djl, but for the moment i can't update it :/ bye"" Even if you manage to start it, it doesn't quite work properly since is unmaintained (some links are now dead). It is not totally useless but crippled. Version-Release number of selected component: 1.2.20-3.mga1 How reproducible: Every time Steps to Reproduce: 1. Just start the application from console 2. Read the error 3.
Keywords: (none) => UPSTREAM
CC: (none) => stormi
Assignee: bugsquad => stormi
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Samuel Did anything happen upstream? (I didn't look, you'll be faster to find the required information :) 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.
CC: (none) => marja11
Unfortunately, upstream still seems dead. However, djl works here on x86_64. dubigrasu, does it fail even after removing the ~/.djl directory ?
Status: NEW => ASSIGNED
I'll try again asap and report back.
Still the same error regardless: QWidget: Must construct a QApplication before a QPaintDevice /usr/games/djl: line 4: 6322 Aborted python -O djl.py $* I can start it however directly from "/usr/share/games/djl/" using: "python djl_main.py" but only if ~/.djl directory is already created, so the application itself is still able to run. The above error appears when the starting "djl.py" is executed. There is gotta be some simple fix for this error. I've googled the error and seems to be a common one, and possible to fix, but I can't make head or tail of it.
btw, maybe we can obsolete the package in mga3 ?
I guess we'll have to, unless an upstream revives
You mean...this app is in Mageia2 repos although it was reported dead a year ago?
(In reply to comment #7) > You mean...this app is in Mageia2 repos although it was reported dead a year > ago? Yes. Any package that was in Mageia 1, that didn't get obsoleted in Mageia 2, or updated, is in the Mageia 2 repositories. Both Mageia 1 and 2 have the djl-1.2.20-3.mga1.src.rpm.
CC: (none) => davidwhodgins
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
I do not understand how this works so I apologize up front. So, djl is not fixed and most likely will never be. Still is in Mageia 2 repos and I see it in Cauldron repos also. If I understand correctly that means Mageia 3 also will carry a dead djl in its repos and if nothing change probably will go on to Mageia 4/5/6 and so on. So what needs to be done in order to fix it or get rid of it? I just do not understand how Mageia got rid of some still useful (for some) libraries to decrease the amount of unnecessary work, but still keep this dead obsolete package. Or by chance, is djl fixed in Mageia 2/Cauldron?
you are I will reassign thanks. (my comment 9 was an automatic message to 314bugs)
Keywords: UPSTREAM => (none)Version: 1 => CauldronAssignee: stormi => sysadmin-bugsTarget Milestone: --- => Mageia 3Summary: Djl game manager not working (and abandoned by its author) => Remove Djl from repositories (abandoned by its author)
Priority: Normal => release_blocker
Priority: release_blocker => NormalBlocks: (none) => 8888
hi, From Mageia 3 (cauldron) DJL is dead webiste is 2009, software bug... my bug was reported since 2010 not fixed: http://forum.djl-linux.org/viewtopic.php?f=12&t=327 I can't use ! Last news 2009 ! http://fr.djl-linux.org/ please remove thank you
CC: (none) => inster.css
Created attachment 3563 [details] Still bug from 2010 in mageia3
Ok. I added it to task-obsolete so that it's removed from mirrors and from user machines (since it does not work anymore).
CC: (none) => pierre-malo.denielou
thanks (I saw it was deleted after my repo sync) closing.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED