Subject: bug#13299: 24.3.50; Tramp adb and device not found

From: [email-masked]
Date: Tue, 26 Mar 2013 00:56:42 -0400

Michael Albinus <[email-masked]> writes:
Hi Michael,

> [email-masked] writes:
>
> Hi,
>
>> Now with Bzr 111425 when doing:
>>
>>   ^X^F/adb::/?
>>
>> you see in the echo area:
>>
>> Making completion list...
>>
>> but nothing else happens and Emacs is locked up.
>>
>> Not even ^G (keyboard-quit) or ^G^G^G unlocks Emacs.
>>
>> You can only kill emacs from the command line prompt.
>>
>> However, if adb is already started:
>>
>>    adb fork-server server
>>
>> then Emacs displays:
>>
>> Making completion list...
>> Find file: /adb::/ [No completions]
>
> Thare have been some very recent changes in tramp-adb.el, which should
> improve handling of "/adb::". Bzr revision 111433. With that patch
> level, I'm not able to reproduce the problem.
>
> Could you, please, check?

Sill having the same problems with Bzr revision: 111604.

I have to kill adb from the command line in order to get Emacs to
respond.

Killing adb and then ^X^F/adb::/? a times finally gets Emacs to
list the files.  But a subsequent ^X^F/adb::/? gets back to the
same problem.

(Of course, eventually getting it to works only happens if the
drivers are loaded first.  Without the drivers, Emacs just locks up
until adb is killed -- ^G or ^G^G^G doesn't work). 
>> Thanks.
> Best regards, Michael.