On 1 Jan 2011, at 1:25 PM, Tom Albers wrote:
> Hi,
>
> These are the top mailinglists with the most amount of moderation requests.
> For most of them we have tried to contact the current moderators without much
> success last year. So now I suggest we get rid of these mailinglists.
>
> Note
Hi Benoit,
> Let's review the possibilities we currently have for
> hardware-accelerated 2D rendering:
> * XRender/OpenGL back-ends to QPainter/Cairo.
> -> problem: the Cairo API is in our experience inherently unsuitable
> for hardware acceleration and my impression is that the same applies
> to
To alpha_one_x86: the crash you posted is a known issue in ktorrent,
as a workaround increase the maximum open file limit, this has nothing
to do with oxygen or nvidia or anything else. It is just a matter of
to many open files, you can easily get into this situation if you have
a torrent with many
Am Monday 03 January 2011 schrieb Sebastian Kügler:
> > or help nvidia fix their crappy drivers :)
>
> In the past, aaronp on Freenode was very helpful, maybe ping him?
For the records: i expect this to not be some sort of "stupid bug, fix this
line and we're done" thing.
The issue has existed a
On Monday, January 03, 2011 16:10:14 Hugo Pereira Da Costa wrote:
> > @Herman
> > If you figure the Oxygen style is slower than others on your system that
> > is for sure because of animations/ARGB pixmaps/you've got an nvidia GPU
> > which hates the QPixmap::fill(Qt:transparent) call... -> use the
On Monday, January 03, 2011 04:01:58 pm Thomas Lübking wrote:
> Am Sunday 02 January 2011 schrieb Cyrille Berger Skott:
> > exiting. I would be more leaning toward a ktorrent bug than anything
> > else.
>
> There's probably none, he set "ulimit -n 1" (that means: max amout of open
> file handles:
Am Sunday 02 January 2011 schrieb Cyrille Berger Skott:
> exiting. I would be more leaning toward a ktorrent bug than anything else.
There's probably none, he set "ulimit -n 1" (that means: max amout of open
file handles: "1" - since _everything_ on unix is a file, this is an instant*
crasher as
On Monday 03 January 2011 10:08:40 you wrote:
> On Monday 03 January 2011, you wrote:
> > I have disk problem (raid5 with hdd with hardware problem). But that's not
> > influance gnome.
> >
> > But it's not connected to sockets. Sockets don't write to disk. ->
> > partially wrong, the inode is wri
I have disk problem (raid5 with hdd with hardware problem). But that's not
influance gnome.
But it's not connected to sockets. Sockets don't write to disk. -> partially
wrong, the inode is writed to the disk, (after hardreboot some socket can be
found on some folder), no disk acces to communica
