X2Go Bug report logs - #129
X Error: BadAccess (attempt to access private resource denied) 10 - Extension: 129 (MIT-SHM)

Full log

Message #15 received at submit@bugs.x2go.org (full text, mbox, reply):

Received: (at submit) by bugs.x2go.org; 12 Mar 2013 07:41:55 +0000
From oceanosoftlapalma@gmail.com  Tue Mar 12 08:41:55 2013
Received: from mail-ia0-f173.google.com (mail-ia0-f173.google.com [209.85.210.173])
	by ymir (Postfix) with ESMTPS id DCB4F5DB17
	for <submit@bugs.x2go.org>; Tue, 12 Mar 2013 08:41:54 +0100 (CET)
Received: by mail-ia0-f173.google.com with SMTP id h37so4567607iak.4
        for <submit@bugs.x2go.org>; Tue, 12 Mar 2013 00:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        bh=JMZiTEQUzw05usnb0fiPXCPjqExUUUAOHoQn3p5iHwg=;
        b=ORn1nBZmMn2vlXZ1LXQkfp/WlLb7DnKkw45TuRDAv64Tq1uf/O8H4FfvrwaFG21MST
         /JGKZtzgLXAPwXQcK3KB4ybswPevwSD1uBk55Xklolrcy1gBrLOfR1yRYF+7jeJRCvsX
         rNAHmpDbjL1U8AfNY6rT/xqKCurjVO9qo40qOpubxcXQ1HhZ1xdOAWLnMsjMTonPIIb6
         lOiHnBVDDtYdYOOHSabDLnnEQKL+lUdJM/Q1He6R6hkuuEAqwwRiglX00Oxs1TrIH56r
         c+N/Aam3FZYg+348QW5VVcl9yvdabFtQrZqcIqmUPN6Z9GjfcuaysfJ/xwZB51/2oTVc
         q0xQ==
MIME-Version: 1.0
X-Received: by 10.50.12.201 with SMTP id a9mr10894140igc.10.1363074113100;
 Tue, 12 Mar 2013 00:41:53 -0700 (PDT)
Received: by 10.231.226.70 with HTTP; Tue, 12 Mar 2013 00:41:53 -0700 (PDT)
In-Reply-To: <CAPWth0KKkMnovz_6QbjrkX6ULS5pCrcnM1HEeTtUF9bf9rUPJg@mail.gmail.com>
References: <CAPWth0+Ob9n4UVQoYsjN_5Sy2o+BtBTvKFNWng_D5jnSGoDTGw@mail.gmail.com>
	<CAPWth0KKkMnovz_6QbjrkX6ULS5pCrcnM1HEeTtUF9bf9rUPJg@mail.gmail.com>
Date: Tue, 12 Mar 2013 08:41:53 +0100
Message-ID: <CAPWth0KzCgCUGYt=bXFrYX_YTRa=SKFag1EPQ3LSq8W4TPBtug@mail.gmail.com>
Subject: Re: [X2Go-Dev] Bug#129: X Error: BadAccess (attempt to access private
 resource denied) 10 - Extension: 129 (MIT-SHM)
From: Ricardo Díaz Martín <oceanosoftlapalma@gmail.com>
To: submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary=14dae93409b550769704d7b56ca0

[Message part 1 (text/plain, inline)]

Hi,

I found that if you set enviromental LD_LIBRARY_PATH= and run qt4 based app
I got the problem on before, these apps work.

Other behaviour I found is if you set password to root user and login with
root user then you can run apps like root and see windows as expected.

I also can confirm it habppens in kubuntu 12.04.2 (fresh install)

Regards,

2013/3/3 Ricardo Díaz Martín <oceanosoftlapalma@gmail.com>

> Hi,
>
> In addition I got also problem running some qt4 based app. Using gdb to
> debug these apps looks like the problem is in /usr/lib/nx/X11/libNX_X11.so.6
>
> Hope it helps to you to find the bug.
>
> Regards,
> Ricardo
>
> 2013/3/1 Ricardo Díaz Martín <oceanosoftlapalma@gmail.com>
>
>> Package: x2goagent
>> Version: 3.5.0.17
>>
>> I just installed x2go server in kubuntu 12.10 x64 and can connect without
>> problems.
>>
>> Problem is when I tryed to run something app using kdesudo o sudo I
>> allways get:
>>
>> X Error: BadAccess (attempt to access private resource denied) 10
>>   Extension:    129 (MIT-SHM)
>>   Minor opcode: 1 (X_ShmAttach)
>>   Resource id:  0x4000010
>> X Error: BadShmSeg (invalid shared segment parameter) 128
>>   Extension:    129 (MIT-SHM)
>>   Minor opcode: 5 (X_ShmCreatePixmap)
>>   Resource id:  0x40000ab
>> X Error: BadDrawable (invalid Pixmap or Window parameter) 9
>> ...
>> ...
>> ...
>>
>> And only can see the app's windows with a full grey color inside. If the
>> app background got more than one colour I can see them but no controls
>>
>> I can confirm the same issue in other kubuntu 12.10 server updated from
>> 12.04
>>
>> I'm using x2goserver from stable x2go ppa and system are full update.
>>
>> _______________________________________________
>> X2Go-Dev mailing list
>> X2Go-Dev@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/x2go-dev
>>
>
>

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.