Closed xu3s closed 1 year ago
I need to know what application prints in debug mode when you try to make a right click.
I already wrote all necessary code to handle right click. But some devices simply do not let intercept it. There is no fix for this.
Here is the log termux-x11.log
Is it the whole log? I do not see any click attempts or even Termux:X11 app connection...
Thats the only log that i get by running env TERMUX_X11_DEBUG=1 termux-x11 :0 > tmx11.log &
is this wrong?
Did you interact with the program after running this?
Yes, i run xfce4-session on another tab. Then i tried opening some apps and click and right click there.
It is pretty weird, program must show much more lines...
I'll try again later, i need to go now
can this be a reason why the logs is incomplete???
~ $ env TERMUX_X11_DEBUG=1 termux-x11 :0 > tmx11.log
logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
Unknown...
so , there is nothing i coud do here???
I can not reproduce this and do not know what to do.
So can you try again with TERMUX_X11_DEBUG to catch this?
Unfortunately no, i have tried to restart my phone, and even upgraded my os to android 13 that i push back againts still same error:
logcat: Unexpected EOF! This means that either the device shut down, logd crashed, or this instance of logcat was unable to read logmessages as quickly as they were being produced.If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
I even increases the log buffer size to 100M still the same.
Searching on google still no luck
@xu3s try clearing data of termux x11
Termux:X11 does not keep any data, nothing to be cleared. But it is possible to obtain logs via ADB.
Termux:X11 does not keep any data, nothing to be cleared. But it is possible to obtain logs via ADB.
Can you tell me how to do that?
Just google how to use ADB.
Any news on this?
Any news on this?
everything is working fine
I was asking @xu3s.
I was asking @xu3s.
okay
sorry, been trying to figure out how to use logcat
trying this command: adb logcat ActivityManager:I com.termux.x11:D *:S
but it give no info can someone guide me or just link me to some article about this if possible
adb logcat -c
to clear log, start termux-x11 :0 & echo pid is $!
and after having aborted
message use adb logcat <pid>
with pid number you see after starting termux-x11...
this is the only thing i got running the command suggested:
~ $ adb logcat -c
~ $ termux-x11 :0 & echo pid is $!
[1] 14004
pid is 14004
~ $ adb logcat 14004
--------- beginning of main
06-25 23:08:42.556 18252 8076 E BufferQueueProducer: [SurfaceView[com.termux.x11/com.termux.x11.MainActivity]#18(BLAST Consumer)18](id:474c00000012,api:1,p:14004,c:18252) query: BufferQueue has been abandoned
06-25 23:08:42.556 18252 8076 E BufferQueueProducer: [SurfaceView[com.termux.x11/com.termux.x11.MainActivity]#18(BLAST Consumer)18](id:474c00000012,api:1,p:14004,c:18252) query: BufferQueue has been abandoned
06-25 23:08:42.573 18252 8076 E BufferQueueProducer: [SurfaceView[com.termux.x11/com.termux.x11.MainActivity]#18(BLAST Consumer)18](id:474c00000012,api:1,p:14004,c:18252) connect: BufferQueue has been abandoned
i run xfce on another session and open termux:X11 app and clicking on it with my mouse, that is the only output.
i'm starting to think that this problem only occur on my device which is vivo t1 5g (anyone with this specific device please help)
Sorry, I was wrong, adb logcat --pid=<pid>
now there is no output
~ $ adb logcat -c
~ $ env TERMUX_X11_DEBUG=1 termux-x11 :0 &
[1] 18884
~ $ logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
pidof logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes.
env TERMUXadb logcat --pid=18884
logcat: Unexpected EOF!
This means that either the device shut down, logd crashed, or this instance of logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase log buffer sizes. ^C
~ $
adb logcat --pid=<pid>
...
maybe my logcat is faulty? it seems like the logcat is crashing when trying to output the log.
You have started env TERMUXadb logcat --pid=18884
, not adb logcat --pid=18884
...
adb logcat --pid=<pid>
...
yeah i have run it there but it got buried by the error log of logcat instead, you can see that i run the logcat --pid=pid
after i run termux-x11 in the background
logcat --pid
does not fit here. That was a reason I adviced you to use ADB and not logcat directly.
You have started
env TERMUXadb logcat --pid=18884
, notadb logcat --pid=18884
...
that is because i scroll through my recent command, and that does not have a side effect on the command that i run, you can try yourself when you run comand in bg that throw stuff and scroll though history and running it
Start it in another session.
ok, sorry this is midnight here need to sleep, i have to work tomorrow.
Tomorrow I'll attach a video o you can see what i see, or i can do sharescreen on discord my handle is exelroad
Ola poderia falar comigo em português
Em dom., 25 de jun. de 2023 12:49, xu3s @.***> escreveu:
ok, sorry this is midnight here need to sleep, i have to work tomorrow.
Tomorrow I'll attach a video o you can see what i see, or i can do sharescreen on discord my handle is exelroad
— Reply to this email directly, view it on GitHub https://github.com/termux/termux-x11/issues/355#issuecomment-1606155064, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAZZKHAHFE2LP52DUBCZTWTXNBT2VANCNFSM6AAAAAAZMDTXCY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Official language of this repo is English.
this is the screen recording of what i get , please enlighten me.
sorry been busy irl lately
It looks like I should connect your phone directly and check what exactly happens here...
I don't mind. How should i help you to do that?
Contact me in Discord. .twaik
Ok, mine is exelroad
Middle (scroll) and right click do not work for me either. TERMUX_X11_DEBUG=1 termux-x11 :0
registers left click, but neither middle nor right click. Now I'm making right click with double tap or VNC as a solution.
It looks like there is no way to intercept middle and right clicks on such devices. Or I failed to find such a way.
While using the app when trying to right click it does not get registered, is this can be fixed or is there currently no work around this?
And also middle click just go to home
My devices running android 11 aarch64 if that matter.