TiddlyDesktop problems on Pixelbook

[Filippo Salustri]

Hi,

I'm trying to run TiddlyDesktop 0.0.14 on my Pixelbook, in the linux container.

I'm getting the following error when I run the 64-bit linux version TD:

% TiddlyDesktop-linux64-v0.0.14/nw

[2615:2615:0602/081712.999489:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id

[2615:2649:0602/081713.131424:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files

[2615:2649:0602/081713.131859:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files

[2615:2649:0602/081713.138788:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files

[2657:2657:0602/081713.240478:FATAL:nw_content_renderer_hooks.cc(53)] Failed to load node library (error: libatomic.so.1: cannot open shared object file: No such file or directory)

#0 0x7aba791dbe89 (/home/filsalustri/TiddlyDesktop-linux64-v0.0.14/lib/libnw.so+0x462ee88)

[2644:2661:0602/081713.349885:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: No such file or directory (2)

...

I recognize that this might be a problem in the beta linux container in the Pixelbook, but I thought I'd report it here too. 

[TonyM]

Filippo,

I am afraid the Author of TiddlyDesktop is Jeremy, who is recovering from Covid-19 at this time. A Reply may be a while incoming.

It it provides any guidance, I am no expert in this, but your error messages are not implicating tiddly desktop but some other aspect of your devices operation. Unless perhaps it relates to the browser component of TiddlyDesktop which I believe in Chromium or another standard based browser.

Best of Luck

tony

[Filippo Salustri]

No worries. I figured it was no more than 50/50 that the problem was in TiddlyDesktop.

And I certainly hope Jeremy recovers quickly.