On Thu, Oct 24, 2013 at 12:48:06AM +0100, Stuart Henderson wrote:
Nothing was committed for this yet, did we settle on a fix for it?
I said I was completely happy with the shared memory rights change...
On Thu, Oct 24, 2013 at 10:12 AM, Marc Espie es...@nerim.net wrote:
On Thu, Oct 24, 2013 at 12:48:06AM +0100, Stuart Henderson wrote:
Nothing was committed for this yet, did we settle on a fix for it?
I said I was completely happy with the shared memory rights change...
You can go ahead an
Nothing was committed for this yet, did we settle on a fix for it?
On 2013-10-10, Lars Engblom lars.engb...@kimitotelefon.fi wrote:
This problem is affecting Minitube. Before the workaround, all you get
is an empty window. This workaround makes it possible to search for
clip, but you are still not able to watch them. You only hear the sound.
On 10/09/13
I using two identically installed computers with different hardware and
at different locations.
I happened at this moment to be infront of the one with radeon
framebuffer and here I get Minitube to play by using the workaround.
The other one is using intel framebuffer and there I was not
On Wed, Oct 09, 2013 at 08:51:54PM +0100, Stuart Henderson wrote:
- Change all shmget calls to user-only memory (security)
So yes, the problem is due to qt4, which use more strict permissions
for shmget.
The aforementioned change was done to fix
On Thu, 10 Oct 2013, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 08:51:54PM +0100, Stuart Henderson wrote:
- Change all shmget calls to user-only memory (security)
So yes, the problem is due to qt4, which use more strict permissions
for shmget.
On Thu, Oct 10, 2013 at 02:55:39PM +0200, David Coppa wrote:
On Thu, 10 Oct 2013, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 08:51:54PM +0100, Stuart Henderson wrote:
- Change all shmget calls to user-only memory (security)
So yes, the problem is
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4 (which is packaged in qt4-4.8.5) result
of X11 error:
$ qtconfig4
X Error: BadAccess (attempt to access private resource denied) 10
Extension:130 (MIT-SHM)
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4 (which is packaged in qt4-4.8.5) result
of X11 error:
Confirmed (and on amd64 here, so it's not just a problem
On Wed, Oct 9, 2013 at 4:32 PM, Stuart Henderson st...@openbsd.org wrote:
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4 (which is packaged in qt4-4.8.5) result
of
On Wed, Oct 09, 2013 at 04:03:01PM +0200, Sébastien Marie wrote:
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4 (which is packaged in qt4-4.8.5) result
of X11 error:
$ qtconfig4
X Error: BadAccess
On 10/09/13 16:32, Stuart Henderson wrote:
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4 (which is packaged in qt4-4.8.5) result
of X11 error:
Confirmed (and
On Wed, Oct 09, 2013 at 04:47:41PM +0200, Giovanni Bechis wrote:
On 10/09/13 16:32, Stuart Henderson wrote:
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just upgrade my ports to -current (dmesg below), but I have problems
with qt4 applications.
For example, starting qtconfig4
On Wed, Oct 09, 2013 at 04:43:09PM +0200, Marc Espie wrote:
On Wed, Oct 09, 2013 at 04:03:01PM +0200, Sébastien Marie wrote:
Same problem occurs for others qt4 applications (as vlc or keepassx).
vlc and keepassx are NOT qt4 apps.
not agreed.
keepassx is linked to qt4
$ ldd
On Wed, Oct 09, 2013 at 05:57:13PM +0200, Giovanni Bechis wrote:
On 10/09/13 17:54, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 04:47:41PM +0200, Giovanni Bechis wrote:
On 10/09/13 16:32, Stuart Henderson wrote:
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just upgrade my ports
I'm using xdm, wm is cwm, new mesa, packages built against new mesa, inteldrm
Matthieu Herrb matthieu.he...@laas.fr wrote:
On Wed, Oct 09, 2013 at 04:47:41PM +0200, Giovanni Bechis wrote:
On 10/09/13 16:32, Stuart Henderson wrote:
On 2013/10/09 16:03, Sébastien Marie wrote:
Hi,
I just
On Wed, Oct 09, 2013 at 06:08:28PM +0200, Sébastien Marie wrote:
On Wed, Oct 09, 2013 at 05:57:13PM +0200, Giovanni Bechis wrote:
On 10/09/13 17:54, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 04:47:41PM +0200, Giovanni Bechis wrote:
On 10/09/13 16:32, Stuart Henderson wrote:
On
On 10/09/13 18:16, Stuart Henderson wrote:
I'm using xdm, wm is cwm, new mesa, packages built against new mesa, inteldrm
My qt4 version is qt4-4.8.2p7, maybe the problem is related to the qt4 packages
update.
Cheers
Giovanni
On Wed, Oct 09, 2013 at 07:01:46PM +0200, Sébastien Marie wrote:
On Wed, Oct 09, 2013 at 06:25:32PM +0200, Giovanni Bechis wrote:
On 10/09/13 18:16, Stuart Henderson wrote:
I'm using xdm, wm is cwm, new mesa, packages built against new mesa,
inteldrm
My qt4 version is qt4-4.8.2p7,
On Wed, Oct 09, 2013 at 06:25:32PM +0200, Giovanni Bechis wrote:
On 10/09/13 18:16, Stuart Henderson wrote:
I'm using xdm, wm is cwm, new mesa, packages built against new mesa,
inteldrm
My qt4 version is qt4-4.8.2p7, maybe the problem is related to the qt4
packages update.
Cheers
On Wed, Oct 9, 2013 at 7:15 PM, Matthieu Herrb matthieu.he...@laas.fr wrote:
On Wed, Oct 09, 2013 at 07:01:46PM +0200, Sébastien Marie wrote:
On Wed, Oct 09, 2013 at 06:25:32PM +0200, Giovanni Bechis wrote:
On 10/09/13 18:16, Stuart Henderson wrote:
I'm using xdm, wm is cwm, new mesa,
On Wed, Oct 09, 2013 at 07:15:10PM +0200, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 07:01:46PM +0200, Sébastien Marie wrote:
On Wed, Oct 09, 2013 at 06:25:32PM +0200, Giovanni Bechis wrote:
On 10/09/13 18:16, Stuart Henderson wrote:
I'm using xdm, wm is cwm, new mesa, packages built
On Wed, Oct 9, 2013 at 8:00 PM, Sébastien Marie semarie-open...@latrappe.fr
wrote:
On Wed, Oct 09, 2013 at 07:15:10PM +0200, Matthieu Herrb wrote:
On Wed, Oct 09, 2013 at 07:01:46PM +0200, Sébastien Marie wrote:
On Wed, Oct 09, 2013 at 06:25:32PM +0200, Giovanni Bechis wrote:
On 10/09/13
On Wed, 09 Oct 2013, David Coppa wrote:
On Wed, Oct 9, 2013 at 8:00 PM, Sébastien Marie semarie-open...@latrappe.fr
It means a new patch for qt4...
From changes-4.8.5 (in qt-everywhere-opensource-src-4.8.5):
General Improvements
- Change all shmget calls to
Temporary workaround until we can fix this:
Set QT_X11_NO_MITSHM=1 in the environment
- Change all shmget calls to user-only memory (security)
So yes, the problem is due to qt4, which use more strict permissions
for shmget.
The aforementioned change was done to fix CVE-2013-0254.
Here's the commit:
This problem is affecting Minitube. Before the workaround, all you get
is an empty window. This workaround makes it possible to search for
clip, but you are still not able to watch them. You only hear the sound.
On 10/09/13 22:50, Stuart Henderson wrote:
Temporary workaround until we can fix
28 matches
Mail list logo
