Pmbootstrap: weston-terminal does not work

Created on 29 Jun 2017  路  16Comments  路  Source: postmarketOS/pmbootstrap

I can't reproduce this myself right now, but multiple users have reported this.

bug help wanted upstream

All 16 comments

Nutcake wrote in IRC:

Does anyone know why weston-terminal instantly crashes with "wl_display@1: error 0: invalid object 0"? All other demo applications in weston work fine

I have the same issue, but if I start the weston-terminal in fullscreen mode it works:
/usr/bin/weston-terminal -f --shell=/usr/bin/htop

got a different error message trying to start it in windowed mode...
wl_shm_pool@24: error 1: invalid width, height or stride (-1097947836x-1097947800, 3197019532)

Fullscreen also works on my end. Non-fullscreen gives me
wl_display@1: error 0: invalid object 0
again

Great, that you found out more about this! How about someone, who can reproduce this, makes a bug report upstream in Weston about this? (If someone does, please make sure to be extra friendly to our upstream friends - search the tracker for similar bugs, before reporting, do a detailed report with nice log output, link to this issue, and invest enough time to debug this together with the weston developers.)

Weston3 has been released, maybe this fixes the bug. I suggest we do the following:

  • [x] Update our weston package to v3
  • [x] If the bug does not yet get resolved, investigate further and make an upstream bugreport.
  • [x] Upstream the upgrade to Alpine

(This list is obsolete, Weston was updated in Alpine before it was updated in postmarketOS, we adjusted our package then, and it did not solve this issue.)

For me it seems like a problem about no cursor on screen, I could only run it, when I attached a mouse.

@Nutcake or @drebrez, could you try if https://github.com/postmarketOS/pmbootstrap/pull/495 (weston 3.0.0) solves this issue?

@PabloCastellano tried with weston 3.0.0 but weston-terminal still doesn't work in windowed mode

I have this problem on the Flame, getting wl_display@1: error 0: invalid object 0.

Launching XDG_RUNTIME_DIR=/tmp/0-runtime-dir/ /usr/bin/weston-terminal -f --shell=/usr/bin/htop works just fine.

To go forward with this issue, we could figure out how to get a trace where it is failing, and then either figure a patch out ourselves (and upstream that!) or ask weston upstream for help. @ata2001 wrote a helpful clue above already, it seems to be related to a missing mouse input device.

weston-terminal also added a -m argument which starts the window maximized. Tested it on weston 3.0.0 and both (fullscreen and maximized window) works. I tried debugging it with gdb but without success, didn't managed to understand where the issue is.
I will probably try again adding some additional logging in the source code.

I did some tests trying to fix this issue, mainly patching the computation of the width/height/columns/rows in these funtions.
Nothing yet, window looks resized but keeps closing instantly...

It's some progress at least! Do you get the same error message, when it closes?

wl_display@1: error 0: invalid object 0

@ollieparanoid Did you really mean to close this issue?

Uh, no I did not, I meant to post this and close #12. Too many tabs open :sweat_smile:
Thanks for checking! Reopened and deleted my comment.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

craftyguy picture craftyguy  路  7Comments

ata2001 picture ata2001  路  3Comments

ollieparanoid picture ollieparanoid  路  5Comments

pavelmachek picture pavelmachek  路  7Comments

zhuowei picture zhuowei  路  4Comments