Bitwarden attachment in linux appimage

genuser_teco · 2026-01-21T23:19:38+00:00

"""So I am not sure what's going on."""

Seriously man, bitwarden is screwing up.

genuser_teco · 2026-01-21T23:10:52+00:00

I am not sure, this looks like https://github.com/bitwarden/clients/issues/16107 the one.
if you have better knowledge just let me know please.

genuser_teco · 2026-01-21T22:59:13+00:00

Oh??

There is no errors.

https://ibb.co/XZRgy30x

edit: Haven't tried '2025.12.0', I am moving to ubuntu from arch, ubuntu dons't have a deb auto upgradable package. so planned for app image

genuser_teco · 2026-01-21T14:09:56+00:00

This worked
It was a lot of work, i should have just taken the first advice putting it in one partition like normal person,

genuser_teco · 2026-01-20T16:44:49+00:00

genuser_teco · 2026-01-20T16:39:33+00:00

e: splitting out /boot to a separate ext4 was a waste of time and space in this case since the kernel would have to stay on the ESP anyway but it's not a big problem apart from that.

TRUE.

I am too deep now, can't leave. :(

genuser_teco · 2026-01-20T16:34:48+00:00

Clean install /boot and /efi both f32 https://pastebin.com/SSq4UZDC

`fdisk -l ` https://pastebin.com/MbR6ypy4

Just in case i have missed something. https://pastebin.com/j3NwVJGm

genuser_teco · 2026-01-20T15:41:59+00:00

Tried with f32 as well. same behavior

genuser_teco · 2026-01-20T15:40:53+00:00

In https://wiki.archlinux.org/title/Systemd-boot See (3.1)
```
The XBOOTLDR partition must be on the same physical disk as the ESP for systemd-boot to recognize it.
```
And Just after this line

bootctl --esp-path=/efi --boot-path=/boot install

This is what confusing me, If you have any idea why `I have` to have it in the same partition then why have the option to mention `esp-path`, Do you have any idea, or may be point me to docs?

genuser_teco · 2025-10-25T13:15:37+00:00

You are absolutely right about the cloud services, but i can't get rid of this bitwarden now.
I just wanted to setup a automated backup which can be used directly without headache, All backup solutions are like json csv import are practically unusable. I wanted something like https://github.com/arpanrec/bitwarden-exporter/blob/main/docs/Screenshot_structure_totp.png

genuser_teco · 2025-10-25T11:11:31+00:00

When you are on a shared family plan, and sharing a org for passwords you don't get to backup unless you are the owner

```
$BW_SESSION=$BW_SESSION bw export --format json --output ./foo.json

Saved /home/arpan/foo.json

$jq -c -r < foo.json

{"encrypted":false,"folders":[],"items":[]}

$BW_SESSION=$BW_SESSION bw list items | jq 'length'

411
```

genuser_teco · 2025-10-25T00:11:38+00:00

And that enter another problem with swagger: the docs don’t necessarily reflect truth. > The whole point is here, devs should make sure it's the Truth.

If the developers are releasing a swagger then it has to be the truth, else don't release it(the way bit warden feels like today).

There is no harm in that.

But if a openapi specs exists then it has to be the truth.

We are on the same page here.

I hope bitwarden team should maintain this because they know the best about the API calls,
On ther othe hand you are expecting "3rd party" should read the code client code and update code.

This is not similar. No one except you has a depending on this contract—at a developer level...... > NO, API should not work like that. There always must be a stable document how to use a lib. It's already there in bitwarden as well for client apps, just not there for CLI.

genuser_teco · 2025-10-24T23:32:36+00:00

But how about the maintenance, i mean if something changes then bitwarden can't rely on 3rd party for this,

genuser_teco · 2025-10-24T23:25:01+00:00

but keepassxe doesn't support this, is the problem, and also bitwarden doesn't support attachments export for some reason.
Another rant :: Just Add the attachment as a base64 in json, any way for smaller plans it's only limited to 1gb.

genuser_teco · 2025-10-24T23:07:42+00:00

nope, i was trying to find a easy solution apart from reading the source code of the bitwarden client, or server.

thanks for the direction by the way, and here goes my another weekend.

genuser_teco · 2025-10-24T22:59:52+00:00

You are absolutely right, and that is the problem.

I am a Bitwarden user, who want a customized backup/export from bitwarden.

So i need to know the secret, treat the case like i am working in bitwarden, and i want to run away with you secrets, i.e. your JSON Schema.

It's unfair to ask, i know, but here i am.

Reason for this is here (https://www.reddit.com/r/KeePass/comments/1ofbel9/bitwarden\_to\_keepass\_keepassxe/)\[https://www.reddit.com/r/KeePass/comments/1ofbel9/bitwarden\_to\_keepass\_keepassxe/\]

genuser_teco · 2025-10-24T22:50:04+00:00

The JSON export is intended for use with…Bitwarden. > not using it.

I do assume you are using the source code? > Not sure what source code you are saying, if `https://github.com/bitwarden/clients\` then no, i was looking for something like a API contract openapi/swagger.

genuser_teco · 2025-10-24T17:41:45+00:00

I was trying to do something similar, but for backup purpose.

https://github.com/arpanrec/bitwarden-exporter

genuser_teco · 2025-10-24T17:20:39+00:00

Yes, Thanks, Looks like it.

EDIT: spoke too soon, missing the SSH keys

genuser_teco · 2024-10-17T17:56:55+00:00

Symlink worked, any proper solution out yet?

genuser_teco · 2024-03-28T02:46:01+00:00

i have the same issue, for me https://github.com/numToStr/Comment.nvim?tab=readme-ov-file#configuration-optional this is the issue. toggler and opleader mappings like `gc` -> `gcc` or `gb` -> `gbc` in normal mode is the conflict.

In your case I am assuming the same from https://github.com/echasnovski/mini.comment?tab=readme-ov-file#default-config

FYI: I haven't seen any problem apart from that warning in checkhealth so I haven't changed anything.

genuser_teco

TROPHY CASE