Arch Linux

geo909

Member

Registered: 2008-09-07

Posts: 309

[SOLVED] Closed bug but I'm still affected.

Hi all,

I was affected by this bug. It is considered to be fixed and it is closed but it wasn't for me.
There is already a request by somebody to reopen. What do I do in such a situation? I don't see an option for voting up this request or something so I'm a bit worried that I may get stuck with this bug.

I'm new to bug reporting, any advice would be appreciated.

Last edited by geo909 (2014-07-12 18:57:57)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,560

Re: [SOLVED] Closed bug but I'm still affected.

The correct thing to do is just what you've done, request that it be reopened.

This doesn't look like an packaging bug, though, so not much will happen there anyway. You're waiting for an upstream fix.

geo909

Member

Registered: 2008-09-07

Posts: 309

Re: [SOLVED] Closed bug but I'm still affected.

The correct thing to do is just what you've done, request that it be reopened.

It wasn't me, but somebody did.

This doesn't look like an packaging bug, though, so not much will happen there anyway. You're waiting for an upstream fix.

I see, thanks. I am still a bit worried though, the last comment in the bug page was:

Good news, 3.15.5, already in testing, fixes this issue for me (Intel GM965 GPU). I consider this bug report closed as far as I'm concerned.

So it seems that this was fixed for some people but for me 3.15.5 is still buggy.

I guess this is the "upstream" bug report? But the arch linux bug report says it is fixed? I'm a bit lost here..

Last edited by geo909 (2014-07-12 17:40:51)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,560

Re: [SOLVED] Closed bug but I'm still affected.

Not closed anymore

geo909

Member

Registered: 2008-09-07

Posts: 309

Re: [SOLVED] Closed bug but I'm still affected.

Not closed anymore

Indeed, so I'm closing this thread Thanks.