-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux/Snap: Support underlying directories moved around at runtime #3793
Comments
Duplicated issue to snapcrafters/signal-desktop#14 as well |
I am not so sure that an upgrade is necessary for the EACCES error on renaming the logs. I received the error this morning on a Linux Mint system that's been up for 4 days, and I cannot find any evidence that snap or signal was upgraded. The error occurred sometime between 5-dec-19 17:40 (local time, -05:00) and 6-dec-19 09:40. My dpkg.log ends at 5-dec-19 15:35. The journal shows that Snappy daemon restarted at 5-dec-19 11:34, and I don't remember restarting Signal since several days ago. I'm attaching journal output for snapd and the Signal logs. This hasn't happened in a while, but I'll be happy to provide any other info if it's useful. |
We don't need logs - we need the structure and permissions of Signal-related directories when this happens. And ideally, what it was before. The theory is that this is due to directories being moved or deleted. |
Same as @bast1aan ; snap made an update from 1.30.1 -> 1.31.0
|
same issue here too. |
Thanks for your input, everyone. I want to be very clear - as of today we don't officially support the Signal Desktop snap packages available now. |
Will you support the Debian package or are you dropping support for that too? |
If this bug is reproducing for you outside the context of a snap package, please enter a new bug. |
It is trying to rotate the log file; (rename "log.log" to "log.log.0" then continue to writing to log.log) however the "home" plug does not have permission to do it. Is the fix just to add the log directory with "write" permission in the |
Bug still there one year later: Unhandled Error
|
FWIW, I've been using the flatpak distribution from Linux Mint 20 for awhile now, and I haven't seen this error any longer. I had to uninstall the snap for it on one of my machines. |
This error is still present on Signal v5.6.1
|
This is the wrong place to report this. Report it directly to the snap maintainers, unless you can reproduce it with the .deb (see #3793 (comment)). https://github.com/snapcrafters/signal-desktop/issues |
It is alreay reported at snapcrafters/signal-desktop some time ago: snapcrafters/signal-desktop#14 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug Description
The Signal Desktop Snap app in Ubuntu 18.04 crashes after a running for a while with following error message:
When looking in the list of Signal snap versions:
it looks like the snap is upgraded in the background and somehow the running instance of Signal does not handle this correctly and keeps trying to use the older config directory.
Steps to Reproduce
Unfortunately not easy, but something like this
Actual Result:
Crash
Expected Result:
Should not crash.
Screenshots
Platform Info
Signal Version:
Operating System:
Ubuntu 18.04
Linked Device Version:
Android: Signal 4.49.18
Link to Debug Log
https://debuglogs.org/604b3bb6f1cc01244899b902643643d3503981433d3377526d5f671b96b89c12
The text was updated successfully, but these errors were encountered: