On Thursday 19 April 2012 15:01:59 Alberto Villa wrote:
> On Monday 12 March 2012 12:57:07 Alberto Villa wrote:
> > I still have some repaint problems (window
> > titles lag a bit when changing), but I won't give up until they're
> > fixed.
>
> Just to note that with Qt 4.8.1 + KDE SC 4.8.2 this p
On Monday 12 March 2012 12:57:07 Alberto Villa wrote:
> I still have some repaint problems (window
> titles lag a bit when changing), but I won't give up until they're
> fixed.
Just to note that with Qt 4.8.1 + KDE SC 4.8.2 this problem disappeared.
--
Alberto Villa, FreeBSD committer
http://peo
On Tue, Mar 13, 2012 at 10:03 AM, Alberto Villa wrote:
> On Mon, Mar 12, 2012 at 8:45 PM, Oliver Heesakkers
> wrote:
>> I hope you get the remaining 4.8 issue(s) fixed, but until then I can
>> recommend fixing the 'blank window'-problem by patching in that commit.
>>
>> Putting the attached file
On Mon, Mar 12, 2012 at 8:45 PM, Oliver Heesakkers wrote:
> I'm still on 4.7.4 (and will stay there until 4.8 hits the ports proper, due
> to time constraints).
>
> Setting shmmni and shmseg doesn't make a difference here.
It's not expected to make any with Qt 4.7.
> I hope you get the remaining
Op ma 12 mrt 2012 12:57:07 schreef Alberto Villa:
> On Fri, Mar 9, 2012 at 10:02 PM, Alberto Villa wrote:
> > Thanks. I think that LooX's patch is part of the solution, but we also
> > need to increase those two limits.
>
> OK, I figured out what was the problem with Qt 4.7. LooX's patches
> don'
On Fri, Mar 9, 2012 at 10:02 PM, Alberto Villa wrote:
> Thanks. I think that LooX's patch is part of the solution, but we also
> need to increase those two limits.
OK, I figured out what was the problem with Qt 4.7. LooX's patches
don't work (also, one patches unused code). His problems went away
On Fri, Mar 9, 2012 at 5:09 PM, Oliver Heesakkers
wrote:
> Starting marble was OK, , just a few errors but after starting kmahjongg the
> terminal got spammed continuously with similar kind of errors:
> X Error: BadShmSeg (invalid shared segment parameter) 159
> Extension: 142 (MIT-SHM)
> Min
On Fri, Mar 9, 2012 at 9:54 PM, Mel Flynn wrote:
> Attached, though I think the more interesting part is what you get on
> stderr (see marble.{dis,}allowed.txt).
You're on 8.2, right? Then that is expected.
--
Alberto Villa, FreeBSD committer
http://people.FreeBSD.org/~avilla
__
On 3/9/2012 16:20, Alberto Villa wrote:
> On Fri, Mar 9, 2012 at 1:57 PM, Alberto Villa wrote:
>> Then: we *must* fix raster graphics system. LooX, did you get any
>> interesting result with your sysctl tweaking (I remember you said on
>> IRC you have the same problem)? Can you paste the output of
On Fri, Mar 9, 2012 at 9:17 PM, Mel Flynn wrote:
> Yet, in the log at http://seibercom.net/logs/.xsession-errors the lock
> not supported message appears and he's supposedly on 9.0, so I wonder if
> that is the cause of his phonon problems or that semaphore locks still
> don't work on 9.0.
By the
On Fri, Mar 9, 2012 at 9:17 PM, Mel Flynn wrote:
> Yet, in the log at http://seibercom.net/logs/.xsession-errors the lock
> not supported message appears and he's supposedly on 9.0, so I wonder if
> that is the cause of his phonon problems or that semaphore locks still
> don't work on 9.0. Either
On 3/9/2012 20:32, Alberto Villa wrote:
> On Fri, Mar 9, 2012 at 5:55 PM, Mel Flynn wrote:
>> I'm wondering two different things:
>> 1) Why are we using semaphore locks?
>> Traced this down to missing POSIX_THREAD_PROCESS_SHARED support
>> (basically, the pthread_mutexattr_setpshared POSIX functio
On Fri, Mar 9, 2012 at 5:55 PM, Mel Flynn wrote:
> I'm wondering two different things:
> 1) Why are we using semaphore locks?
> Traced this down to missing POSIX_THREAD_PROCESS_SHARED support
> (basically, the pthread_mutexattr_setpshared POSIX function).
>
> 2) Could missing support of anonymous
On 3/9/2012 16:20, Alberto Villa wrote:
> The problem is with the limit to shared memory segments: shmmni, which
> is the maximum allowed number of memory identifiers (i.e., segments on
> the system), and shmseg, which is the same thing, but per-process.
> These were set to about 1xx (I don't reme
On Fri, Mar 9, 2012 at 4:20 PM, Alberto Villa wrote:
> All of this is with kern.ipc.shm_allow_removed=0, and raster graphics
> system is running smoothly.
Oh, and without LooX's patches.
--
Alberto Villa, FreeBSD committer
http://people.FreeBSD.org/~avilla
__
On Fri, Mar 9, 2012 at 1:57 PM, Alberto Villa wrote:
> Then: we *must* fix raster graphics system. LooX, did you get any
> interesting result with your sysctl tweaking (I remember you said on
> IRC you have the same problem)? Can you paste the output of `ipcs -m`
> and `sysctl kern.ipc` after bein
On Fri, Mar 9, 2012 at 1:57 PM, Alberto Villa wrote:
> It might fix Qt 4.7 maybe, but Qt 4.8 switched to raster graphics
> system by default, and thus relies heavily on shared memory. With or
> without the patches (I even tried forcing deletion of memory segments)
> the size of used shared memory
On Thu, Feb 16, 2012 at 10:10 PM, Axel Gonzalez wrote:
> This little patches fix the problems in kde-games without tweaking the sysctl
> kern.ipc.shm_allow_removed
No, it doesn't. :(
It might fix Qt 4.7 maybe, but Qt 4.8 switched to raster graphics
system by default, and thus relies heavily on s
This little patches fix the problems in kde-games without tweaking the sysctl
kern.ipc.shm_allow_removed
The problem is described here:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164742
The patches are for x11-toolkits/qt4-gui , and for qt 4.8, in qt 4.7.4 shuould
be similar fix. YMMV.
I was
19 matches
Mail list logo
