[oe] devshell "No protocol specified"

[Douglas Royds]

Marco Cavallini wrote:
> Douglas Royds ha scritto:
>   
>> Failing to get a devshell console. Fails for both XTERM and KONSOLE:
>>
>> | No protocol specified
>> | xterm Xt error: Can't open display: :0
>>
>> The failure is unique to one box (ie. it works fine on a different
>> computer).
>>
>> Invoking run.do_devshell.15108 directly succeeds, so the problem only
>> occurs when we try to launch the devshell from within bitbake.
>>
>> I used bitbake -D to see the list of environment variables that bitbake
>> was unsetting. I tried listing the whole lot in BB_ENV_EXTRAWHITE, but
>> still no joy.
>>
>> Suggestions?
>> Douglas.
>>
>>
>> $ bitbake zlib -c devshell
>> NOTE: Handling BitBake files: \ (6591/6591) [100 %]
>> NOTE: Parsing finished. 6305 cached, 0 parsed, 286 skipped, 0 masked.
>> NOTE: Cache is clean, not saving.
>> NOTE: build 200904211325: started
>> fatal: Not a git repository
>>
>> OE Build Configuration:
>> BB_VERSION        = "1.8.12"
>> METADATA_BRANCH   = "<unknown>"
>> METADATA_REVISION = "25344"
>> TARGET_ARCH       = "arm"
>> TARGET_OS         = "linux-gnueabi"
>> MACHINE           = "davinci-dcb"
>> DISTRO            = "tait"
>> DISTRO_VERSION    = "trunk-20090421"
>> TARGET_FPU        = "soft"
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: Preparing runqueue
>> NOTE: Executing runqueue
>> NOTE: Running task 32 of 32 (ID: 4,
>> /media/storage/workspace/DBS/org.openembedded.dev/vendor/2009-02-21_dcbeaf393bed4d0b7071c100bf9e5d92ad3c20c5/packages/zlib/zlib_1.2.3.bb,
>>
>> do_devshell)
>> NOTE: package zlib-1.2.3: started
>> NOTE: package zlib-1.2.3-r5: task do_devshell: started
>> ERROR: function do_devshell failed
>> ERROR: log data follows
>> (/media/storage/workspace/DBS/build/tmp/work/armv5te-tait-linux-gnueabi/zlib-1.2.3-r5/temp/log.do_devshell.15108)
>>
>> | No protocol specified
>> | xterm Xt error: Can't open display: :0
>> NOTE: Task failed:
>> /media/storage/workspace/DBS/build/tmp/work/armv5te-tait-linux-gnueabi/zlib-1.2.3-r5/temp/log.do_devshell.15108
>>
>> NOTE: package zlib-1.2.3-r5: task do_devshell: failed
>> ERROR: TaskFailed event exception, aborting
>> NOTE: package zlib-1.2.3: failed
>> ERROR: Build of
>> /media/storage/workspace/DBS/org.openembedded.dev/vendor/2009-02-21_dcbeaf393bed4d0b7071c100bf9e5d92ad3c20c5/packages/zlib/zlib_1.2.3.bb
>>
>> do_devshell failed
>> ERROR: Task 4
>> (/media/storage/workspace/DBS/org.openembedded.dev/vendor/2009-02-21_dcbeaf393bed4d0b7071c100bf9e5d92ad3c20c5/packages/zlib/zlib_1.2.3.bb,
>>
>> do_devshell) failed
>> NOTE: Tasks Summary: Attempted 31 tasks of which 31 didn't need to be
>> rerun and 1 failed.
>> ERROR:
>> '/media/storage/workspace/DBS/org.openembedded.dev/vendor/2009-02-21_dcbeaf393bed4d0b7071c100bf9e5d92ad3c20c5/packages/zlib/zlib_1.2.3.bb'
>>
>> failed
>> NOTE: build 200904211325: completedmailman/listinfo/openembedded-devel
>>     
>
>
> we recently solved an identical issue
> see thread 20/04/2009 "[oe] devshell not working with screen remote shell"
>
> BTW could you descrive better what are you doing?
> are you on local or remote machine?
>
> Can you try calling xterm in your console?
> What happens?
>
> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
>   

Well, perhaps not identical: a different error message, no SSH, and no 
"screen". This is happening locally.

xterm and konsole both open fine when you call them directly from the 
command line. As I mentioned, invoking the bash script in 
build/tmp/work/.../temp/run.do_devshell.12345 works fine. The problem 
only occurs when BitBake tries to do it, and only on that machine:

    | No protocol specified
    | xterm Xt error: Can't open display: :0

I have yet to try it on a different KDE box - mine is opening Gnome 
Terminal OK.

Thanks,
Douglas.

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================