I’ll try it as soon as I can, thanks for the suggestion! I don’t think the battery is dying, because while powered on the battery life is very good
I’ll try it as soon as I can, thanks for the suggestion! I don’t think the battery is dying, because while powered on the battery life is very good
As it should be, the battery life while in use it’s even better than my own pc
Probably there are problems with the report to the OS because the battery health is marked as 100%, which is a bit strange for a 4yo pc. Do you think this may have something to do with the battery drain?
The battery health is marked as 100%, which seems strange to me. However, the battery life while powered on is very good, so I don’t think the battery is old or exhausted. Do you think that changing the battery may be the solution?
As usual :|
I’ll have to check it out then, thanks for your help!
Thanks for sharing this kind stranger, I really needed this
What about Penix?
It worked, thank you very much for your help man! Now the only remaining problem is the snapshot 166, that snapper does not let me remove. I assume I should remove in a similar way as timeshift:
$ sudo btrfs subvolume delete /.snapshots/166/snapshot
WARNING: not deleting default subvolume id 2968 '/.snapshots/166/snapshot'
I think there’s something I’m missing about how these snapshot works
Thanks for the answer! I mounted it and removed all the timeshift-btrfs stuff. now, after a reboot, sudo btrfs subvolume list -t /
does not show timeshift stuffs anymore, but if I mount again sudo mount -o subvolid=5 /dev/nvme0n1p2 /mnt
and ls /mnt/
I get:
@ @cache @home @log timeshift-btrfs
how can I remove timeshift-btrfs
from there? can i just rm -rf
it?
In openSUSE
(sorry I forgot to mention, I’m running EndeavourOS)
I’m using windscribe VPN from Italy and it works without issues right now
Uhm this could be a good workaround, I’ll look into it, thanks! It would solve the movies problem, but not any other screen sharing problem
Thank you!
I already have a jellyfin instance, but syncplay didn’t works very reliably for me, some users experienced freezing, jumps and other problems
Thanks for the suggestion anyway!
It would be just me sharing to everybody else on the internet (no more than 6 people)
Jitsi meet works great, the only problem is being able to share only “a portion” of what it currently does
I think the problem is not something related to jitsi, meet, discord or matrix, but rather to the OS screensharing capabilities
Please tell me this is not real
Is this real or just a meme?
Other answer seems to suggest that the problem is that the same podcast can be available, depending on where and who is listening to it, with different length due to different ads injected into. Here’s my probably stupid and completely ignorant suggestion: instead of using timestamps for both begin and end of the ads segment, you could use a timestamp for the beginning, and an hash of the first part of “non-ads” segment. I’ll try to explain better:
|----------------xxxxx--------------------|
^ |___|
The xxx is the ads segment, the ^
is the timestamp of the beginning of the ads, the |___|
is a small duration segment (for example, 0.5 seconds) right after the ads segment. The data of that segment is hashed and used as “end ads segment indicator”.
On the other device, with a different duration of the ads, you should start hashing it to find the corresponding segment.
Is this doable or did I just said a bunch of idiot things?
I checked and yes, there’s no cmos battery in it. Do you think this may have something to do with it?