Using Signal on PinePhone in mid-2023?

[dragonhospital]

Problem persists in version 6.27.  All attachments are downloaded and not rendered.  Can not send attachments.

it seems that you use desktop app? do you use arm64 or x86-64 version?

i use x86_64 version and desktop app with 6.28.0 version and attachments and images work fine.

arm64
https://github.com/dennisameling/Signal-Desktop/

[dragonhospital]

Appears to be the same problem https://github.com/signalapp/Signal-Desktop/issues/6481 A signal developer wrote on June 18 they won't be able to fix it for some weeks.

[dragonhospital]

Appears to be the same problem https://github.com/signalapp/Signal-Desktop/issues/6481    A signal developer  wrote on June  18 they won't be able to fix it for some weeks.

Problem  continues in version 6.38.  Any kind of attachments and media can not be  sent or received.  Many have same bug https://github.com/dennisameling/Signal-.../issues/17

[zetabeta]

putting it here:

i heard official rumor, that signal is testing usernames for messaging. so there is probably alternate for phone numbers in the future. however, signal-cli probably comes little behind adding this feature.

just for generic comment, users could use signal-cli if other options do not work.
https://github.com/AsamK/signal-cli

[dragonhospital]

putting it here:

i heard official rumor, that signal is testing usernames for messaging. so there is probably alternate for phone numbers in the future. however, signal-cli probably comes little behind adding this feature.

just for generic comment, users could use signal-cli if other options do not work.
https://github.com/AsamK/signal-cli

Can you  add a link to this thread on the github issues https://github.com/dennisameling/Signal-.../issues/17  ?    Microsoft's Github is shadow banning replies. Microsoft's Github should at no time be used for a software project.

[Kevin Kofler]

The good news is that Flare is now getting some work done to support running as a primary device. The bad news is that it is not finished yet: the first part was merged, but it is still disabled by default because some parts are missing, in particular, linking secondary devices with Flare-as-a-primary-device (and according to the commit messages, for that feature, there seems to be a bug in the libraries Flare uses, which needs to be fixed upstream).

[dragonhospital]

Attachment bug presists. Has anyone  got  the patch working https://github.com/dennisameling/Signal-...1817767085 on version 6.47 and newer?

Code:

.ensureFile() call seems to be causing EFAULT of the write systemcall in arm64 environment.
I am not expert of node.js but I think:

    ensureFile is implemented by fs-extra/lib/ensure/file.js as function createFile (file, callback)
    createFile() is calling fs.write(file, '') in order to create empty file to target path.
    fs.write() is dispatched to write() systemcall, but when 2nd parameter of fs.write() is empty (''), 2nd parameter of write systemcall is pointing invalid address.

My workaround:

    Change fs.write(file, '') => fs.write(file, ' ') on node_modules/fs-extra/lib/ensure/file.js

Then now, I can send/receive attachments without EFAULT in my aarch64 chromebook linux.

I think root cause could be node.js or libuv? (somewhere dispatching to the write systemcall).
When empty buffer parameter passed to fs.WriteFile(), invalid const void *buf address is generated as the write() syscall parameter.

fs.write(file, ''  has been changed to fs.writeFile(file, '' although the patch above no longer works.

What is the full path to  node_modules/fs-extra/lib/ensure/file.js ? The docker contains many copies of node_modules/fs-extra/lib/ensure/file.js

[dragonhospital]

MSFT Github is shadow banning replies. Can a kind community member please post a request asking for an updated fs-extra patch for versions 6.47 and newer? https://github.com/dennisameling/Signal-...1817767085