https://bugzilla.novell.com/show_bug.cgi?id=738951
There isn’t even a response from any develloper or investigator at all in 5 months since the bug was first reported.
I know they are mostly vollunteers, and you can’t force anyone to do anything. But still some of them should be proud of their product, and wanting to make it as bug free as possible!? 
Since the kernel is where basic graphic support comes, why not give a newer kernel a try and see what it does.
Kernel 3.4: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.tar.bz2 Kernel 3.3.7: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.3.7.tar.bz2
The SAKC Kernel Compile: S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.71 - Blogs - openSUSE Forums
Get ANY Kernel back to 2005: S.G.T.B. - SuSE Git Kernel Tarball Creator - Version 1.80 - Blogs - openSUSE Forums
Just some more options to consider. I think, and its only my opinion, that this issue is considered to be a graphic display problem, that the openSUSE distro can do little to fix.
Thank You,
On Wed, 23 May 2012 21:36:02 +0000, wvv wrote:
> https://bugzilla.novell.com/show_bug.cgi?id=738951
>
> There isn’t even a response from any develloper or investigator at all
> in 5 months since the bug was first reported.
>
> I know they are mostly vollunteers, and you can’t force anyone to do
> anything. But still some of them should be proud of their product, and
> wanting to make it as bug free as possible!?
As it happens, I’m just starting to do some work on a project within the
project to try to see if we can improve responsiveness on bugs. Let me
see if I can track down some assistance on this - I see the bug’s
assignment is to a mailing list of xorg developers.
It may be that this has to be handled upstream, but if that’s the case,
then the bug should be updated by the assignee to reflect that.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Thu, 24 May 2012 00:37:51 +0000, Jim Henderson wrote:
> I see the bug’s assignment is to a mailing list of xorg developers.
I’ve sent a message to the assignee and will let you know what I hear
back. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Ok, if this is the case, someone with knowledge about this, should report this in bugzilla, and close the bug. So me and the reporter can move on to a different place to get help…
I think there in lies the problem. A bug should never be assigned to a mailing list. It could easily be ignored if no one on the list feels responsible, or if it’s a busy list, it might just be overlooked.
Maybe it’s a good idea to have bugzilla send automatic reminders if a bug doesn’t get a response from the assignee within a certain period of time (let’s say a week)?
Indeed!
I hope you are not going to wait another five months on this!? 
On 05/24/2012 09:36 AM, wvv wrote:
>
> Ok, if this is the case, someone with knowledge about this, should
> report this in bugzilla, and close the bug. So me and the reporter can
> move on to a different place to get help…
since no one has actually answered you (in bugzilla) i can only guess,
but i do guess that it was kicked to the most likely bug spot (the
kernel krunchers or the graphics driver builders, or both)…
and, i also guess that yours (and the other openSUSE user who joined
your bug report) are not the only two instances of this bugs
appearance…so, i further guess that it has been reported by the
users of Red Hat, Fedora, Mint, etc etc etc etc etc…
and, therefore the folks who must fix it are well aware of the problem…
AND, whoever in the openSUSE ecosystem who is supposed to mark your bug
with something like “forwarded to appropriate fixer” has done all of her
job, except actually mark 738951 correctly…
i think he/she should be flogged, what about you?
by the way: the forum’s active members/helpers are over 95% “just users”
(plus some professional administrators and precious few ‘developers’)
trying to help other users…the “fixers” you are apparently angry with
are not here…
–
dd
I’m not angry, just a little bit annoyed.
So I was asking how to get things moving, when contacting the developers “directly” through bugzilla doesn’t work. And apparently this was enough, because someone with inner knowledge of bugzilla already picked up on this. So I’m happy for now…
On 2012-05-24 02:37, Jim Henderson wrote:
> As it happens, I’m just starting to do some work on a project within the
> project to try to see if we can improve responsiveness on bugs. Let me
> see if I can track down some assistance on this - I see the bug’s
> assignment is to a mailing list of xorg developers.
I have dozens of bugs in “new” state, nothing happening for years, it is
discouraging. And then some one comes and closes it as obsolete without
ever doing any real work on it, which is even more discouraging :-/
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
When a bug is reported against a version that is no longer supported that is understandable. When it still occurs in a newer version, you can update the bug and reopen it against the newer version… I suspect this is even the intention of the one who closes the bug: Get some response if it still needs to be open.
The problem is we are talking about specially difficult bugs, there are 86 bugs assigned to them and only 24 hours a day…
It does.
On 2012-05-24 11:06, wvv wrote:
>
> dd@home.dk;2464792 Wrote:
>> by the way: the forum’s active members/helpers are over 95% “just users”
>> (plus some professional administrators and precious few ‘developers’)
>> trying to help other users…the “fixers” you are apparently angry with
>> are not here…
>
> I’m not angry, just a little bit annoyed.
Sometimes I nag on one of the mail lists.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I understand there are priorities and limited time. My annoyance wasn’t with the fact there isn’t a bug fix or someone working on it, but with the fact there is no response whatsoever in bugzilla…
On 2012-05-24 11:36, wvv wrote:
>
> robin_listas;2464794 Wrote:
>>
>> I have dozens of bugs in “new” state, nothing happening for years, it is
>> discouraging. And then some one comes and closes it as obsolete without
>> ever doing any real work on it, which is even more discouraging :-/
>>
>
> When a bug is reported against a version that is no longer supported
> that is understandable.
No, it was reported for a then supported version. Nobody does anything
until it is obsolete, and then they use that excuse to close it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-05-24 11:36, RedDwarf wrote:
> The problem is we are talking about specially difficult bugs, there are
> 86 bugs assigned to them and only 24 hours a day…
Well, stop adding new features and start solving bugs, one after another,
until there is none left. And I’m serious.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 05/24/2012 11:06 AM, wvv wrote:
> I’m not angry, just a little bit annoyed.
i well understand! i’m often annoyed by stuff around here that i think
‘should’ or ‘could’ go smoooother…and, often when i voice that i’m
judged and shot down for being “over the top”, or “angry” or “worked
up”…etc…
angry, annoyed or just amused by the circus, i’m happy you got the
attention you wanted and deserve!
–
dd
Carlos E. R. wrote:
> On 2012-05-24 11:36, RedDwarf wrote:
>
>> The problem is we are talking about specially difficult bugs, there are
>> 86 bugs assigned to them and only 24 hours a day…
>
> Well, stop adding new features and start solving bugs, one after another,
> until there is none left. And I’m serious.
Been there, done that, got the blood-stained T-shirt.
I wouldn’t wish it on anyone. Trying to eliminate all bugs in a piece of
software of any size (i.e. having a large size) is a terrible idea.
Reread “The Mythical Man-month”. A better scheme is to have targets for
the number of bugs, for clear-up rate and for rate of finding new bugs.
But you’re right that the rate of introduction of new features does need
to be balanced against the rate of change of the number of outstanding
bugs. Unfortunately, I suspect the commercial realities don’t allow it
without some major change in process.
On Thu, 24 May 2012 07:56:02 +0000, wvv wrote:
> hendersj;2464771 Wrote:
>> On Thu, 24 May 2012 00:37:51 +0000, Jim Henderson wrote:
>>
>> > I see the bug’s assignment is to a mailing list of xorg developers.
>>
>> I’ve sent a message to the assignee and will let you know what I hear
>> back.
>
> I hope you are not going to wait another five months on this!?
Not planning to, no. I’m not actually involved in the bug itself, but
since I’m starting a project to improve the bug process, this seemed
relevant to what I’m trying to do.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Thu, 24 May 2012 07:46:03 +0000, wvv wrote:
> hendersj;2464738 Wrote:
>>
>> As it happens, I’m just starting to do some work on a project within
>> the project to try to see if we can improve responsiveness on bugs.
>> Let me see if I can track down some assistance on this - I see the
>> bug’s assignment is to a mailing list of xorg developers.
>
> I think there in lies the problem. A bug should never be assigned to a
> mailing list. It could easily be ignored if no one on the list feels
> responsible, or if it’s a busy list, it might just be overlooked.
Actually, in my research on how bugzilla is used in the project, that’s a
fairly typical way to handle these things. Bugs go through a first
“triage” team that check for duplicates and that the necessary
information is there before the developers get their hands on it.
In this case, the list consists of two developers who (from what I
understand so far) do both the triage and the bug fixes.
But assigning to a list allows the bug to go to a triage team so it can
be “vetted” before it moves on.
That also means that if people want to get involved in that initial
screening process, they can subscribe to the list and will be added to
the bugs that are assigned by default to that list - and when someone
leaves the project, they can unsub from the list and the bug’s assignment
will still be valid.
> Maybe it’s a good idea to have bugzilla send automatic reminders if a
> bug doesn’t get a response from the assignee within a certain period of
> time (let’s say a week)?
That may be a possibility - I’ve not yet dug into how far we can go with
customization (this project I’m working on is about a week old or so, and
I’m not working on it “full time” as it were - so it’s just kicking off
and we’re just in the planning phase for the project at the moment).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C