You are not logged in.
Hi,
I'm experiencing the following bug:
https://bugzilla.gnome.org/show_bug.cgi?id=594082
It looks like it's now fixed in Fedora. Anyone having the same problem?
Thanks.
Offline
Definitely am- I've had this error for a while on desktop and laptop (nvidia and ati cards respectively). Maybe it's to do with xorg 1.8? I don't remember it happening before that big upgrade.
Arch x86_64
Offline
I noticed this too but I haven't been using gnome for very long so I just assumed it was normal. It is pretty annoying though.
Offline
I've submitted a bug report:
http://bugs.archlinux.org/task/20732
Please vote it so that it gets more attention.
Cheers.
Offline
As you pointed out in your first post, that this is a bug with Gnome and not with Arch. The Arch devs are not going to be able to do anything other than ignore it.
Please make sure where the bug lies before opening one. Opening bugs which have nothing to do with Arch creates a bottleneck for Devs.
On the bug tracker, you mention that they fixed it in Fedora? Can you provide a link as to where it is mentioned that its fixed?? I doubt that a gnome bug would be distro related and fixed in Fedora but not in Arch or others.
Also, voting on bugs does not get it fixed. Bugs in general, are assigned a priority by the Dev team, and then handled as such. A bug might have a few thousand votes, but it's probably not going to be fixed unless
a) All higher priority bugs have been resolved
OR b) the dev is doing something related and doesn't mind solving this bug along with it.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Hi Inxsible,
Thanks for pointing that out, but the bug is no longer affecting Fedora, but still affecting Arch, so I guess it should be already fixed in the upstream, so it might be something that the Arch devs can still fix.
Offline
While you were posting, I edited my above post
On the bug tracker, you mention that they fixed it in Fedora? Can you provide a link as to where it is mentioned that its fixed?? I doubt that a gnome bug would be distro related and fixed in Fedora but not in Arch or others.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Please, look carefully at this bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=594082
The user that reported the bug, Tim Taiwanese Liim, was using Fedora 11. Another user called "Nate" is stating in comment 2 that the problem went away with updates. In comment 3, Tim Taiwanese Liim is confirming this, and so he asks to close the bug in comment 4.
This bug was created as an upstream bug but the fix was only confirmed in Fedora.
Offline
Should I ask to reopen this gnome bug?
Offline
Fair enough but it's not clear from that if it got fixed by a Fedora dev or upstream... either way, bug reports should go to gnome-screensaver bugzilla.
Also see this:
https://bugzilla.redhat.com/show_bug.cgi?id=629419
https://bugzilla.redhat.com/show_bug.cgi?id=626472
Would be nice to know if Fedora applied any patches in F11, but I don't get where to look that up atm (stopped here.
Something else, what graphics are you using? nvidia proprietary here.
typo
Last edited by hokasch (2010-09-03 13:34:12)
Offline
I'm using intel, but this doesn't look related to the graphics card, because o1911 has reported the problem also in nvidia and ati.
Offline
You can open a new bug at gnome bugzilla and link in all the other reports, unfortunately they don't contain much information apart from "its broken!/it suddenly works!". Please post the link back here too.
OT/
Ok, there is a different bug with nvidia which breaks the actual fading. It doesn't fade here, but when I see the pointer pop up in fullscreen I know pacman screensaver will kick in 5 sec later there even is a patched version of gnome-screensaver in AUR.
Offline
hokasch, I followed your advice and opened a new bug report:
Offline
More related reports:
https://bugzilla.redhat.com/show_bug.cgi?id=612620
And from comment 35, Ubuntu fixed this bug like this:
http://git.debian.org/?p=pkg-xorg/xserv … a2a34ca728
Looks like there's a problem in Xorg:
Offline
Someone might want to test this against xorg 1.9, which is currently in testing. Does the same problem exist there?
Offline
xorg 1.9 freezes my desktop at the logon screen, so I can't test it.
Offline
It's been a while since we've discussed this, but I've still got the problem. Does anyone else still have it? Still both ATI and nvidia graphics proprietary drivers, xorg 1.9 (although there is another bug causing nvidia drivers not to "fadeout", but the relevant AUR package fixing this problem still has the effect of not responding to input changes).
Arch x86_64
Offline
This only happens with me when I use Compiz. Metacity isn't affected.
Offline
I'm still experiencing this. Using the intel driver and no compiz, only metacity composition. Maybe it has to do with any kind of composition.
Offline
I get this too with compiz + radeon driver.
Offline
I got this with intel and no compositing at all. But I haven't tested recently as that laptop has now been disqualified.
Offline
There's some discussion and good pointers here:
Offline
Same problem here,
>uname -a
Linux smoreno-arch 2.6.35-ARCH #1 SMP PREEMPT Wed Sep 29 08:45:18 CEST 2010 x86_64 AMD Turion(tm) X2 Dual-Core Mobile RM-75 AuthenticAMD GNU/Linux
---------------------------
X.Org X Server 1.9.0
Release Date: 2010-08-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-ARCH x86_64
Current Operating System: Linux smoreno-arch 2.6.35-ARCH #1 SMP PREEMPT Wed Sep 29 08:45:18 CEST 2010 x86_64
Kernel command line: root=/dev/sda3 ro
Build Date: 24 August 2010 01:44:37PM
Current version of pixman: 0.18.4
---------------------------
Driver Catalyst 10.10 - on ATI radeon HD 3200
Last edited by smoreno (2010-11-01 02:50:45)
Sebastián Moreno
Montevideo | Uruguay
Offline