Steps to reproduce
Have “Automatic updates” setting configured to off.
Restart app some time after new version of Obsidian is available.
No automatic upgrade should happen.
App was automatically upgraded
Obsidian version: v1.2.8
Installer version: v1.1.16
Operating system: #1 SMP PREEMPT_DYNAMIC Wed, 26 Apr 2023 20:50:14 +0000 6.2.13-arch1-1
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Obsidian Nord v0.1.7
Snippets enabled: 3
Restricted mode: off
Plugins installed: 6
Plugins enabled: 6
1: Calendar v1.5.10
2: Emoji Toolbar v0.4.0
3: New Notes Default Template v0.0.13
4: Paste URL into selection v1.7.0
5: Reminder v1.1.15
6: Linter v1.11.0
Update logs from obsidian.log:
2023-05-09 15:34:54 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-09 18:54:17 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-10 05:01:25 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 07:18:51 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 07:19:03 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 08:18:52 Checking for update using Github
2023-05-14 08:18:52 Success.
2023-05-14 08:18:52 Latest version is 1.2.8
2023-05-14 08:18:52 Downloading update from https://github.com/obsidianmd/obsidian-releases/releases/download/v1.2.8/obsidian-1.2.8.asar.gz
2023-05-14 08:18:54 Verifying hash & signature. Size= 6033374
2023-05-14 08:18:54 Saving file
2023-05-14 08:18:54 Update complete.
2023-05-14 09:18:52 Checking for update using Github
2023-05-14 09:18:52 Success.
2023-05-14 09:18:52 Latest version is 1.2.8
2023-05-14 09:18:52 An update is already downloaded.
2023-05-14 10:18:52 Checking for update using Github
2023-05-14 10:18:52 Success.
2023-05-14 13:18:53 Latest version is 1.2.8
2023-05-14 13:18:53 An update is already downloaded.
2023-05-14 14:18:53 Checking for update using Github
2023-05-14 14:18:53 Success.
2023-05-14 14:18:53 Latest version is 1.2.8
2023-05-14 14:18:53 An update is already downloaded.
2023-05-14 14:34:54 Loading updated app package /home/stas/.config/obsidian/obsidian-1.2.8.asar
2023-05-14 15:08:09 Checking for update using Github
2023-05-14 15:08:09 Success.
2023-05-14 15:08:09 Latest version is 1.2.8
2023-05-14 15:08:09 App is up to date.
I’ve read that for Linux you accept bugs only for AppImage installations, while I use package from the regular Arch repo
community/obsidian, but what makes me think that it’s still worth report it:
- I’ve found a very similar bug, which was reported not so long time ago for Windows - Turning off Automatic updates is not working , but was closed without any reply. So I presume that bug is not specific to my environment, still there and I just hit it.
- Issue itself(code ignores some setting) doesn’t look like something specific to a type of installation. I might be wrong of course.
- If it would be something packaging-specific, like Segfault or complain on some files broken, I would debug it myself without bothering authors, but unfortunately it looks like a source code bug which is impossible to fix from my side, so I’m desperately have no choice other than report and hope for your understanding.
I could collect any debug information you might need.
Thanks in advance and hope for your understanding!
I am not convicted that this happens.
It’s possible that 1) you disabled automatic updates after the update was already downloaded or 2) the arch package was updated (which we don’t provide support for).
Install the appimage, turn updates off, and open a new bug report if you still get the update when we release 1.3.x to the public.
Hi, thanks for quick reply.
It’s possible that 1) you disabled automatic updates after the update was already downloaded
No, I’m sure because I’ve installed obsidian more than month or 2 ago (v1.1.16) and configured it at day one. I’m very pedantic in this regard, all customizations I do I always write in my internal “documentation” to be able to “replay” them in case of issues. So I have an explicit record that “auto-updates were disabled as useless”
They are not only useless on Linux, but actually harmful so I disable them for all soft, if possible.
- the arch package was updated (which we don’t provide support for).
This is even more not true, because I didn’t upgrade it even now =)
pacman -Qs obsidian
LANG=C stat /usr/bin/obsidian
Size: 61 Blocks: 9 IO Block: 512 regular file
Device: 0,23 Inode: 566913 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2023-03-31 10:06:14.000000000 +0200
Modify: 2023-03-03 00:29:08.000000000 +0100
Change: 2023-03-31 10:06:14.576915508 +0200
Birth: 2023-03-31 10:06:14.576915508 +0200
I don’t have automatic system-wide upgrades ever, exactly because of similar cases.
That’s okay but I am still don’t take bug reports for the arch package. We don’t make it.
I’ll keep an eye on what the appimage does.
Fortunately I’m able to revert Obsidian folder from the last snapshot, and right at the moment I can easily reproduce a bug, if that might help =)
Obsidian does auto-upgrade if I click “Check Updates” button. Setting “Automatic updates” is turned off as I mentioned.
Looks like it’s a side-effect of checking for upgrades?
Here is a logs:
2023-04-27 17:03:32 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 16:21:46 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 16:22:43 Loading main app package /usr/lib/obsidian/obsidian.asar
2023-05-14 16:23:00 Checking for update using Github
2023-05-14 16:23:00 Success.
2023-05-14 16:23:00 Latest version is 1.2.8
2023-05-14 16:23:00 Downloading update from https://github.com/obsidianmd/obsidian-releases/releases/download/v1.2.8/obsidian-1.2.8.asar.gz
2023-05-14 16:23:01 Verifying hash & signature. Size= 6033374
2023-05-14 16:23:01 Saving file
2023-05-14 16:23:01 Update complete.
2023-05-14 16:23:31 Loading updated app package /home/stas/.config/obsidian/obsidian-1.2.8.asar
Do you need some information collected? E.g. strace it or whatever…
P.S. Archlinux package is trivial, just downloads file from github and do nothing special about it, so I doubt it’s relevant to the way of installation
No, the arch linux package is not trivial at all. As it bundles the arch’s version of electron.
So you clicked the check for update button?
Yes, from what I see now - just restarting app doesn’t trigger auto-upgrade, but clicking “Check for Upgrades” - does, regardless of setting “Automatic updates” turned off.
So looks like it’s either:
- “Check for updates” act as a “Check & Do actual upgrade” and more like documentation/naming issue than a real bug. Maybe it was unexpected from caption just for me
- or if “Check” was intended to just check and nothing more, than it’s a bug that it does upgrade also.
If the only thing I need is just don’t touch this button - I think topic can be closed. But I’d improve button caption to be more explicit)
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.