Opened 5 years ago
Last modified 3 years ago
#16110 new bug
Telegram silently fail to start from Live CD
Reported by: | diver | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
haiku-master-hrev54249-x86_64-anyboot.iso
Booted in vbox and installed telegram using pkgman i telegram_desktop
Running Telegram would briefly show it in the Deskbar and quit. There are no messages in the Terminal or in syslog.
I'm guessing it could be a problem in write_overlay file system or atapi driver.
Attachments (1)
Change History (7)
comment:1 by , 5 years ago
by , 5 years ago
Attachment: | telegram_strace.log added |
---|
comment:3 by , 5 years ago
Well it seems to be loaded and start running, and then exits cleanly (exiting starts at 6252 where it deletes a lot of areas as it releases all its memory apprarently).
So I guess extra logging in Telegram itself or in Qt is needed to see why it decided to quit.
I also see various "no such file or directory" errors but I don't know if they are normal or not (checking that a file doesn't exist is fine and would result in this).
comment:4 by , 5 years ago
Telegram creates log file log_start0.txt
in curent directory:
[2020.05.24 09:41:55] Connecting local socket to /boot/system/cache/tmp/3035f1837f0aa4e92fd37a134dd4fba8-{87A94AB0-E370-4cde-98D3-ACC110C5967D}... [2020.05.24 09:41:55] This is the only instance of Telegram, starting server and app... [2020.05.24 09:41:55] Failed to start listening to /boot/system/cache/tmp/3035f1837f0aa4e92fd37a134dd4fba8-{87A94AB0-E370-4cde-98D3-ACC110C5967D} server: QLocalServer::listen: Name error
Looks like it failed to create socket file in /system/cache/tmp/
.
~> mkfifo /boot/system/cache/tmp/temp mkfifo: cannot create fifo '/boot/system/cache/tmp/temp': Read-only file system
comment:5 by , 5 years ago
mh... the write_overlay makes it possible to write there, but I guess mkfifo does not go through it?
comment:6 by , 3 years ago
The write_overlay does not seem to support "special nodes" (of which FIFOs are one), it just passes through to the next layer down: https://xref.landonf.org/source/xref/haiku/src/add-ons/kernel/file_systems/layers/write_overlay/write_overlay.cpp#2194
So, that would probably have to be amended.
Could a a problem with the binary size which is ~50MB.