OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Software => Topic started by: starkruzr on May 21, 2006, 02:25:40 am
-
Does this work for anyone else? Because it sure doesn't for me.
When I try to open a ROM, I get "Xlib: extension "XFree86-DGA" missing on display ":0.0".
Ideas?
-
Bumping this, because it would be really nice if it worked
-
It would be nice to get it in OE bugtracker too..
-
openzaurus for the c-3200? i wanna see whats going on. were is the link to try it out.
-
It would be nice to get it in OE bugtracker too..
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128420\"][{POST_SNAPBACK}][/a][/div]
I would have, but I wasn't sure if I was doing something wrong or if it was just broken. That's why I was hoping someone who was already familiar with it could help me out.
If the consensus is, "it's broken," though, I'd be happy to put it in the OE bugtracker.
Cresho: There's no link per se, this is the version in the OZ feeds. No link, you just ipkg install snes9x
-
It would be nice to get it in OE bugtracker too..
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128420\"][{POST_SNAPBACK}][/a][/div]
I would have, but I wasn't sure if I was doing something wrong or if it was just broken. That's why I was hoping someone who was already familiar with it could help me out.
If the consensus is, "it's broken," though, I'd be happy to put it in the OE bugtracker.
Cresho: There's no link per se, this is the version in the OZ feeds. No link, you just ipkg install snes9x
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128444\"][{POST_SNAPBACK}][/a][/div]
If you're not sure if something is a bug, it should be okay to ask about it here;
but these sorts of queries are not as helpful to developers who are trying to
locate and squash actual bugs.
What I believe the OE/OZ developers want us to do is:
if you think it might be a bug report it to the tracker.
If you think it might be a bug, but it might not be a bug, report it to the tracker.
If you think it might be a bug, reported it to the tracker, but discovered later that it wasn't a bug-
report THAT CONDITION to the tracker.
hrw/etc tell me if I've got it wrong
-
What I believe the OE/OZ developers want us to do is:
if you think it might be a bug report it to the tracker.
If you think it might be a bug, but it might not be a bug, report it to the tracker.
If you think it might be a bug, reported it to the tracker, but discovered later that it wasn't a bug - report THAT CONDITION to the tracker.
Raduga: I cannot say that better :D
When bug is reported then OE developers are noticed and can look at it (only subset of them use OESF forum).
If bug is already solved we close it (you got info by mail).
If bug was already reported we mark it as duplicate (you got info by mail).
When bug will be resolved we will close it (you will... yes - you will get info by mail). then you check does it really fixed for you and if not then you reopen it (and we will get info by mail).
-
What I believe the OE/OZ developers want us to do is:
if you think it might be a bug report it to the tracker.
If you think it might be a bug, but it might not be a bug, report it to the tracker.
If you think it might be a bug, reported it to the tracker, but discovered later that it wasn't a bug - report THAT CONDITION to the tracker.
Raduga: I cannot say that better
When bug is reported then OE developers are noticed and can look at it (only subset of them use OESF forum).
If bug is already solved we close it (you got info by mail).
If bug was already reported we mark it as duplicate (you got info by mail).
When bug will be resolved we will close it (you will... yes - you will get info by mail). then you check does it really fixed for you and if not then you reopen it (and we will get info by mail).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128446\"][{POST_SNAPBACK}][/a][/div]
I have observed that some users find it frustrating, that the OZ/OE developers want discussion of problems to be focused in a place designed for bug-repairing,
rather than a place for general chitchat, like the forums or IRC.
What might be helpful to users who do find it frustrating (including sometimes myself) would be to remember that OpenZaurus releases, in general, are works in progress-
and this work is vitally dependent on people reporting bugs, and having those bugs fixed.
Meaning... if you use it, you ought to consider yourself part of the quality assurance/beta test group, and if you gain any value from using the software,
you should report your experiences, as they are, to the core developers.
If you don't want the burden of responsibility for helping fix OpenZaurus,
it might be better not to use it; at least, until a stable release is out.
I still send out "feelers" to devs outside the tracker, when I suspect something is a bug, but am not sure; but its becoming more and more clear that proper reporting is an ethical necessity.
thanks - everyone
-
This info needs to be in the OpenZaurus wiki! If someone else does not beat me to it, then I will attempt to add it this weekend.
If I had a nickel for every time I debated with myself submiting a bug report, well then, you know....
-
If bug was already reported we mark it as duplicate (you got info by mail).
But do please try searching the bugtracker first to see if the bug (or something similar) has already been reported.
Thanks,
Si
-
Okay. I will go ahead and submit for it today. Thanks for clearing up the reporting procedure.
-
Just wanted to see if anyone has made any headway with this. I reported the bug and discussed exactly what I think the problem is (for some reason the presence of this XFree86-DGA library is not being reported to the X server), but so far no response.
-
Just wanted to see if anyone has made any headway with this. I reported the bug and discussed exactly what I think the problem is (for some reason the presence of this XFree86-DGA library is not being reported to the X server), but so far no response.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=129409\")
I have exactly the same problem with Snes9x, is there any solution? I didn't find the bug in [a href=\"http://bugs.linuxtogo.org/]GPE bug trucker[/url] and in OE Bug trucker (http://bugs.treke.net/). Can anyone give me a hint where it hides?
btw, starkruzr,
Looking for advice as to how to get snes9x and dgen-sdl running!
I had no problem starting dgen-sdl, other than it runs really slow...
YoG.