Errors when startiing appimage after crash

English Applications
1

OS 15.6 with KDE/plasma crashed while copying a large directory from SD card to home directory.
When that happened I had an appimage of obsidian running.

after reboot, obsidian is starting with black screen.

I renamed the config and content directories of obsidian and downloaded the latest version of the appimage:
this produces an endless list of error messages:

[25826:0719/164335.734021:ERROR:shared_image_representation.cc(498)] Attempt to read from an uninitialized SharedImage. Initialized region: (0, 0, 0, 0) Size: (832, 256)

and

[25826:0719/164335.748441:ERROR:shared_image_manager.cc(249)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.

no change

what could have happened (to plasma/KDE/…?) to cause that?
what can I do to start obsidian again?

2

Can you be more specific what is meant by “appimage of Obsidian”?

I know Obsidian is available as a Flatpak using Discover. Is that it?

Or installed in some other way?

3

there is a well an appimage on their website, that can be downloaded and started directly

4

in case it is relevant: it is a dual GPU system

5

when starting obsidian “on dedicated GPU” there is not even a black window, but just a flickering on the screen and journal says:

Jul 19 19:41:57 legion systemd[7651]: Started obsidian - obsidian.
Jul 19 19:41:59 legion kernel: traps: Compositor[29039] trap int3 ip:5649107be62d sp:7fe116decec0 error:0 in obsidian[56490c641000+8976000]
Jul 19 19:41:59 legion kernel: traps: obsidian[28938] trap int3 ip:56522103162d sp:7ffdeeabea50 error:0 in obsidian[56521ceb4000+8976000]
Jul 19 19:41:59 legion systemd[1]: tmp-.mount_obsidiKwacx0.mount: Deactivated successfully.
Jul 19 19:41:59 legion systemd[7651]: app-obsidian-25f3b1c52a64426294a36f48944a6efc.scope: Consumed 2.271s CPU time.
6

We don’t use Obsidian, so I can’t offer troubleshooting.

But a couple of suggestions

  1. Post your issue over at the Obsidian forum help. There’s (I assume) more folks there with Obsidian knowledge and with Linux (compared to Obsidian users here)
  2. If it were us, we would use the Flatpak, installed via Discover. (probably less potential issues).

I’m sure you could install the Flatpak until you fix the “appimage” … no doubt they can coexist without clashing with the other.

7

my reason for posting here was that obsidian worked well until the crash.

I therefore assumed that the problem is caused by KDE/plasma/GPU/whatever/… configuration being affected by the crash.

8

… two more reboots and it is working again…

9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.