I commented out the XDrawLine() xlib calls and the lockups stopped. The
code for XDrawLine doesn't look suspicious, and other screensavers using
that call (like crystal) seem to be working okay, so it must be
something with the way that braid is making the call. I verified that
interaggregate also
Profile data. unsurprisingly it's spending nearly 100% of its time in
the draw function.
Flat profile:
Each sample counts as 0.01 seconds.
% cumulative self self total
time seconds secondscalls us/call us/call name
100.00 0.01 0.01
I can reproduce this easily on a i965 laptop with Compiz turned on so am
marking it Triaged.
I tried running 'strace braid' but it didn't lock up at all - presumably
strace slows it down enough to not get into the locked up state.
In reading the man page for xscreensaver, I noted this passage whi
miguelquiros : You seem to hit a specific bug since a lot of
screensavers have the problem in your case. Can you open a new bug
report for linux-restricted-modules and attach the resulting file from
that command in a terminal : sudo lspci -nnvv > lspci-nnvv.txt ?
--
braid screensaver crashes syst
Just confirm that I've been hited by this bug, "nvidia" driver and it does not
happen if visual effects are not enabled. I have tested all the screensavers
(from a terminal, just keying /usr/lib/xscreensavers/whatever) and the
following ones display the bug:
xrayswarm
interaggregate
braid
whirlw
This problem is a lot less severe for me since I upgraded to Hardy. The
hacks don't lock up the system for nearly as long time at a time, so
after 5-10 seconds or something like that it's possible to terminate
them.
Braid is actually still present on my system after the upgrade. It
doesn't matter
Now braid is not anymore included in Hardy, until fixes are released for
the problematics drivers.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This has nothing to do with the GL crashers in 181121 AFAIK. braid
doesn't even use GL. BTW, I submitted a xscreensaver package to the
sponsoring queue a month ago that works around this issue.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You re
lör 2008-04-05 klockan 01:30 + skrev Noel J. Bergman:
> I don't see this with all GL screensavers, and I am using an Intel Core
> 2 Duo, not an AMD. I am, however, running 64 bit.
I don't see it with any GL screensavers either.
--
Vincent Lönngren <[EMAIL PROTECTED]>
--
braid screensaver c
I don't see this with all GL screensavers, and I am using an Intel Core
2 Duo, not an AMD. I am, however, running 64 bit.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, w
I wonder if this has anything to do with bug 181121? Symptoms are
different and of course it's a different video card, but the fact that
we're seeing sooo many xscreensaver issues is notable.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You rec
Curiously, "Zoom" doesn't hang my machine. This is so vague. I can't
find an error message anywhere... When i run braid or interaggregate on
a terminal window, then press Ctrl-C after a while this is what happens:
~$ /usr/lib/xscreensaver/interaggregate
interaggregate: warning: only 4% idle over
I've had Compiz disabled as a workaround, so I didn't notice. Now I
tried it with the screensavers Mauro Torrez mentions, a sure enough - it
leads to the same bitter end. I can add 'zoom' to the list, which is of
special interest since it always seems to end up as the screensaver in
the preview win
I'm using Debian etch/sid, and all this thing with Braid and Compiz happens to
me too.
I'm not sure i should report this here or not... anyways, this happens to me
not only with Braid but also with "Interaggregate", "Vermiculate" and
"Whirlwindwrap" screensavers. I'm sure there were even more,
pingnak, nearly all X video driver bugs result in systems that become
unusable; so obviously it wouldn't make sense to list them all as
critical! :-)
For video driver bugs, 'High' is sufficient. We reserve this priority
for bugs that cause serious system crashes, data loss, affect a lot of
users
I just discovered this for myself, and deleted the braid screensaver
myself, then came here to log the bug.
For me, on my Vostro 1700 with 'nVidia Corporation GeForce 8600M GT',
and Compiz, the keyboard is completely locked out. Press caps-lock, no
light. The mouse cursor moves, and I suspect th
Saïvann, I submitted the merge request and debdiff for the new version a
long time ago in bug #201626. That's all I can do. Some core developer
has to upload it.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification bec
Tormod : Since Hardy RC is in few weeks, can you remove braid as you
suggested before?
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Just to add, I also have this problem, so it's not an nVidia problem.
i945GM, and the description exactly matches what goes on on my Acer
laptop (5630) when I run the braid screensaver.
Bug continues as of today (April 1st) on an updated Hardy Beta.
--
braid screensaver crashes system with comp
I'm still getting hard-locks from this in Hardy as of today. Will there
be a fix?
Ti4600
512MB RAM
XP 2000+ CPU
Running nvidia-glx and Compiz. I've had to Kill the power to my PC 3
times since it completely hard locks the system. You have to turn off
Compiz in order to be able to go into the scre
khensucat : This bug does not happen with compiz and intel/ATI cards,
except one intel card so compiz can't be the complete cause of that
problem. However since compiz is directly associated with that bug, I
will add the package at least to make it more visible for compiz
developers, they will be a
Compiz cannot cause a screensaver to freeze your system. Only the driver
can do that. I've left the compiz task on here for tracking but lowered
the priority so it doesn't mess with our workflow.
** Changed in: compiz (Ubuntu)
Importance: High => Low
--
braid screensaver crashes system with c
> Compiz cannot cause a screensaver to freeze your system
Several of us have reported that we see the compiz.real process expand
to fill available memory, which would lead to at the least the
perception of a freeze. We can test this just using the preview window.
The relationship appears to be e
I had this same problem on Gutsy.
Now, on a fresh install of Hardy Alpha 5, both updates in update manager
applied, nvidia-glx-new drivers (169) from the restricted drivers
manager. No other software installed.
Intel E2140
2GB Kingston Ram
Asrok 775DUAL-VSTA
GeForceFX 5500 AGP
With "desktop eff
I can confirm this bug on Gutsy with an nVidia Geforce Go 7400. I
upgraded to 169 of the nVidia driver...no difference. Upgraded to Hardy
kernel (2.6.24), no difference.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notifi
I've been spending some time with the code today, and the problem seems
related and proportional to the "cycles" option.
Running braid from the command line:
$ ./braid [the default is 100 cycles]
braid: warning: only 4% idle over the last 10 secs (at 41.5 FPS)
braid: warning: only 6% idle over
This is from /var/log/Xorg.0.log:
(II) intel(0): Memory allocation layout:
(II) intel(0): 0x-0x0001: ring buffer (128 kB)
(II) intel(0): 0x0002-0x00029fff: HW cursors (40 kB, 0x7f82
physical)
(II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
(II) intel(0
I did not look the memory/CPU use through ssh but the latest 169.12 in
Hardy did not change anything to the symptoms, I still get a unusable
system after running braid preview during 4 seconds.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You re
** Changed in: compiz (Ubuntu)
Status: New => Invalid
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Well, with 169.12, I still saw compiz.real go from ~200M to 1.4GB in a
few minutes, during which braid caused compiz.real and XOrg to consume
99%+ CPU, but (still) unlike others such as Helios, in %us not %ni. On
the other hand, there were more braid images displayed, and the system
seemed more st
> This seems to be a generic texture_from_pixmap problem
Please see http://www.nvidia.com/object/linux_display_amd64_169.12.html:
"- Further improved GLX_EXT_texture_from_pixmap out-of-memory
handling."
Let's get that pulled into Hardy. I have posted Bug 197182 for this
issue.
--
braid scr
>From the workaround dept.: braid will be demoted to -data-extra (and
thus not be installed by default) in xscreensaver 5.04-3.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bu
> This screensaver seems to be a bit like glxgears, it just runs as fast
as possible all the while melting your system.
:-)
For what it is worth, this is typical from glxgears on my system:
Cpu0 : 44.8%us, 32.8%sy, 0.0%ni, 12.0%id, 0.0%wa, 0.0%hi, 10.4%si, 0.0%st
Cpu1 : 41.2%us, 25.2%s
This seems to be a generic texture_from_pixmap problem. If I run
metacity w/compositor it works fine, same with metacity w/xcompmgr. When
I try kwin with 2D (Render) compositing it works too.
Now the fun parts. Using kwin with OpenGL texture_from_pixmap
compositing dies, same as compiz. Using kwin
** Description changed:
Selecting Braid screensaver when Desktop effects are activated runs my
system unusable. I'm running Fiesty on a dual core amd64, but i guess
these kind of details are now included automatically in the report,
right?
So what happens is that the screen freezes an
Travis Watkins : It makes a lot of sense. However, it has been
reproduced on several nvidia cards, but also one Intel integrated card
and I just got to reproduce this also on a ATI card with the opensource
ati driver (I added the card to the list in the description) on a
computer I had access today
** Description changed:
Selecting Braid screensaver when Desktop effects are activated runs my
system unusable. I'm running Fiesty on a dual core amd64, but i guess
these kind of details are now included automatically in the report,
right?
So what happens is that the screen freezes an
I may have misunderstood something, but it seems weird to me that this
rather simple screensaver should consume all the video memory of these
cards.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are
> Do you have Unredirect Fullscreen Windows enabled? If so, does
enabling Sync to VBlank help?
I did have the former enabled, not the latter. I've now tried with both
off and both on. Not noticed a beneficial effect vis-a-vis this defect.
> These are in ccsm ...
Please note: Ubuntu does not in
If the nvidia driver is dumping textures into compiz.real's memory space
(which it does) and not freeing them (and it doesn't) then yes, unless
you look closely it will look like compiz.real is taking more and more
memory.
--
braid screensaver crashes system with compiz activated
https://bugs.lau
> There is no way that code path in compiz leaks
Is it normal that compiz.real shows the rising memory usage, like
Saïvann and Rob have reported?
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a
Oh, and the rapidly rising memory usage is almost certainly the same old
problem we've had with nvidia when you run out of Video RAM. There is no
way that code path in compiz leaks, we would have noticed since it gets
called every single time your screen updates on every single machine
using compiz
That looks about like what I expected, it is damaging the screen every
time the screensaver updates (as it should). Do you have Unredirect
Fullscreen Windows enabled? If so, does enabling Sync to VBlank help?
These are in ccsm in the General Options inder the General and Display
Settings tabs, resp
That's great Saïvann, some compiz developer should be able to get
something out of this. You can maybe try to narrow down what's looping
by standing in the right "frame" and going "next" repetitively. If
you're a frame too high, "next" will not return when it hits the loop.
In the right frame you w
** Attachment added: "gdb where #5"
http://launchpadlibrarian.net/12224750/gdb-compiz5.txt
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "gdb where #4"
http://launchpadlibrarian.net/12224748/gdb-compiz4.txt
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "gdb where #3"
http://launchpadlibrarian.net/12224741/gdb-compiz3.txt
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "gdb where #2"
http://launchpadlibrarian.net/12224739/gdb-compiz2.txt
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I did it 5 times during the time compiz was over-loading the computer
memory. the 3 first look very similar, but the 4 and 5 are different.
compiz and Xorg dbg/dbgsym packages were installed.
** Attachment added: "gdb where #1"
http://launchpadlibrarian.net/12224738/gdb-compiz1.txt
--
braid s
There is no -dbg packages for compiz in repository. Where to get them?
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
You should run `gdb -p ` to attach to the running compiz.real
when it gets in this state and then type 'where' to see what it is
doing. You need to have the dbgsym packages installed for compiz and
Xorg.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101
** Attachment added: "ps aux during ssh session"
http://launchpadlibrarian.net/12223509/ps.txt
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Tormod Volden : Doing a backtrace on compiz over SSH does not give
result, compiz won't crash. However, after 2 minutes, compiz use 65% of
all the computer memory and 31% of the CPU ressources. After 5 minutes,
the computer hard drive is working hard and commands over ssh are VERY
slow to achieve,
There is some info that should be of help at
https://wiki.ubuntu.com/DebuggingProgramCrash
https://wiki.ubuntu.com/Backtrace
https://help.ubuntu.com/community/DebuggingSystemCrash
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bu
Tormod, I can do that, but I need some instructions...
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Is anyone able to do some debugging of Compiz when it explodes in RAM
usage? Running gdb on it from a remote computer would maybe be the best
way.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a
By the way, I've seen entire multi-page threads on the forums about how
to selectively disable screensavers with gnome-screensaver. I don't
know why the obvious hasn't been pointed out:
chmod -x /usr/lib/xscreensaver/${screensaver-to-disable}
Hope that helps some of you while we wait for this
Hardy Alpha 4 with all updates applied as of posting date.
$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro FX 570M
[10de:040c] (rev a1)
$ sed -ne '/Section "Device"/,/EndSection/p' /etc/X11/xorg.conf
Section "Device"
Identifier "Videocar
I have similar problems with an Nvidia 7300 GT graphics card. Nvidia
driver is 100.14.19. Sometimes if I walk away for a few minutes I come
back and the screen saver has not activated but the screen is black and
the keyboard is unresponsive. My only recourse it to power cycle the
PC. This machi
Hi, also happen here, not only with spraid screensaver, but randomly with GL
ones:
Ubuntu 7.10 64 bits
Dual Core Xeon 5110
Nvidia Quadro 4500 (dual screen)
07:00.0 VGA compatible controller [0300]: nVidia Corporation G70GL [Quadro FX
4500] [10de:009d] (rev a1)
dSection/p' /etc/X11/xorg.conf
Sect
I seen that huge memory leak. It persists even after killing compiz. And no
processes use more memory than usual.
So leak must be somewhere in video driver.
Can anyone tell, how to determine memory usage by kernel and all it's
modules?
--
braid screensaver crashes system with compiz activated
h
Nando, your screenshot shows known nvidia driver bug, fixed in 169.xx
version.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
This may actually be a Compiz problem, because when the Braid
screensaver kicks in, the machine doesn't quite crash fully, it just
runs out of RAM and becomes terribly slow.
pressing CTRL+ALT+F1 and opening a terminal (or logging in remoely via
SSH) shows compiz.real using all of my 1GB of RAM and
According to Tormod comment, I change xscreensaver package to xserver-
xorg-video-intel which has been confirmed to have problems by two
persons. Thanks to Tormod for these clear informations.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Sourcepackagename: xscreensaver => xserver-xorg-video-in
Sorry for the noise, I think this has been pointed out earlier by
Vincent and myself: There is no reason to suspect the quality of the
screensaver hack. It has worked well with all cards and if your obscure
closed-source proprietary graphics driver crashes with the problem-child
that is compiz, the
This bug does not happen with all intel cards and it does not happen
with ATI cards that I tested so far, it seems to happen with all nvidia
cards. That's why drivers should be fixed, this is clear. However, I
also think that we should suspect the quality of the screensaver, I
don't have sufficient
If I understand this correctly, the problem is that when Compiz is some
applications crash, among them braid and some other screensavers. So far
it has only been reported with the proprietary NVIDIA driver ("nvidia")
and the Intel driver ("intel"). Does anyone have solid information that
this bug d
I apologize, I didn't mean to clutter things. However the screen saver
relates to the desktop effects issue and that relates to driver and all
of those issues just prove that the thing needs to be fixed, so in my
opinion it does relate, its not that I was talking about the keyboard or
fish and chip
Nando: those issues have nothing to do with this bug report. Let's keep
one issue per bug please.
--
braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
To clarify what I mean by the "pink and bluish scribbles" here is a
screen shot -- yes it just happened again.
The interesting thing is that when I choose to capture the screen shot
from the movie player menu the image comes out okay :? I think it
happens when I change from desktop without effects
That is an excellent idea Tormod, It is one of the less attractive
screen savers anyway, no one will miss it.
I use an nVidia geforce go 7600 and my computer turns into a freak show
when I use desktop effects for a while. Some problems I could not
correct:
- The screen flickers black from time to
The screensaver just draws to the screen, so if that makes the machine
crash, it is a graphics driver problem. Anyway, to reduce the damage, we
can demote the braid hack to the -data-extra package, so that it is not
installed by default.
--
braid screensaver crashes system with compiz activated
h
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sourcepackagename: xscreensaver => linux-restricted-modules-2.6.22
Assignee: Tormod Volden (tormodvolden) => (unassigned)
Status: Incomplete => Confirmed
** Summary changed:
- Braid screensaver crashes system with compiz activate
Does NOT happen with this configuration :
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon
RV100 QY [Radeon 7000/VE] [1002:5159]
Section "Device"
Identifier "ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]"
Driver "ati"
BusID
Hi,
It happens too here :
01:00.0 VGA compatible controller [0300]: nVidia Corporation G70
[GeForce Go 7600] [10de:0398] (rev a1)
Section "Device"
Identifier "nVidia Corporation G70 [GeForce Go 7600]"
Driver "nvidia"
Busid "PCI:1:0:0"
EndSection
C
It happens on :
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce
8300 GS [10de:0423] (rev a1)
Section "Device"
Identifier "nVidia Corporation G80 [GeForce 8300 GS]"
Driver "nvidia"
Busid "PCI:1:0:0"
Option "AddAR
Can all of you who have problems with "braid" (and not general problems) please
report what kind of video card you have:
lspci -nn|grep VGA
and which driver you are using:
sed -ne '/Section "Device"/,/EndSection/p' /etc/X11/xorg.conf
Please also attach as a separate file Xorg.0.log from the cra
Confirmed on gutsy.
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Braid can be easily removed with
sudo rm `locate braid`
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
That would be it then. Sorry for the newb comment :). I ended up
deleting the braid screensaver, and now all is well.
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for your comment.
What you say is right, the package that contains braid screensaver is
xscreensaver-data which is installed by default. However, Launchpad
works with source package names, so the source package name for
xscreensaver-data is xscreensaver.
--
Braid screensaver crashes syste
Hi all. This is my first time reporting on a bug. Just wanted to point
out that I do not think the package is Xscreensaver, since I don't have
that one installed. I have a stock Xubuntu installation, with Compiz
enabled and the gtk-window-decorator. All of the screensavers installed
by default work
increase importance to high
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: xscreensaver (Ubuntu)
Importance: Medium => High
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
As this bug can be reproduced with core components of Linux Ubuntu
Gutsy, I set the importance of this bug to Medium and I set the package
to xscreensaver.
** Changed in: xscreensaver (Ubuntu)
Sourcepackagename: None => xscreensaver
Importance: Undecided => Medium
--
Braid screensaver crashes
The WhirlwindWarp screensaver, viewed in the screensaver selection
window, also crashes my system when compiz is enabled. Braid has the
same effect.
ctrl-alt-backspc works, but only a few minutes after I hit it. Until
then it looks like a hard freeze.
I'm running Feisty on a Pentium-D in 32 bit
** Changed in: Ubuntu
Status: Unconfirmed => Confirmed
--
Braid screensaver crashes system with compiz activated
https://bugs.launchpad.net/bugs/101943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Have the same issue running Beryl, although I have been able to "escape" when
previewing in Screensaver Preferences, but not when the screensaver is running
full-screen.
All other screensavers work fine.
Alt-Ctrl-Backspace doesn't work, have to reset.
As a workaround, how do I disable the specif
I have several issues with screensavers and compiz enabled. Almost al GL
screensavers don't work with desktop effects enabled, and they also
looks X, and I have to make a ctrl+alt+backspc.
Running on P4 with ait oss drivers
--
Braid screensaver crashes system with compiz activated
https://bugs.l
I have several issues with screensavers and compiz enabled. Almost al GL
screensavers don't work with desktop effects enabled, and they also
looks X, and I have to make a ctrl+alt+backspc.
Running on P4 with ait oss drivers
--
Braid screensaver crashes system with compiz activated
https://bugs.l
90 matches
Mail list logo
