KickassWomen

joined 8 months ago
[–] [email protected] 1 points 1 week ago

Interesting, I have never tried this before.

I'll try out your solution and get back to you.

[–] [email protected] 1 points 1 week ago

For me sites like YouTube, Rumble, Odysee, and Bitchute work but unfortunately this version of flatpak Firefox is giving me problems.

[–] [email protected] 7 points 1 week ago (2 children)

It uses Google's Chromium engine, that's the problem.

[–] [email protected] 3 points 1 week ago (4 children)

I appreciate your recommendation but I'm boycotting Google and as much of its tech as possible—that's why I was using Firefox.

 

I'm going to use this guide to downgrade Firefox to something around version 127 or below because I did not have this issue with earlier versions of FF.

Btw where does Firefox store crash logs? I typed "about:crashes" in the URL bar but it says that "No crash reports have been submitted". I have also used journalctl to find these errors but I'm not sure how relevant they are:

org.mozilla.firefox.desktop[15004]: Exiting due to channel error.

org.mozilla.firefox.desktop[49355]: [Parent 2, Main Thread] WARNING: g_strv_length: assertion 'str_array != NULL' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:187

firefox-bin[49355]: g_strv_length: assertion 'str_array != NULL' failed

[–] [email protected] 2 points 2 months ago (1 children)

I get that but up until this week, this wasn't a problem—posts used to show up at the top of the page within 3-5 minutes. Today it took two hours.

[–] [email protected] 3 points 2 months ago

The posts eventually did show up at the top after two hours and receiving 8 or 9 upvotes.

This delay wasn't always there. Just last week, the posts would show up at the top after 3-5 minutes.

 

In case people might get the wrong idea, I only post pics/clips of female martial artists who who have given me their permission. I do not steal content from Instagram.

[–] [email protected] 2 points 3 months ago

In case anyone here disagrees with the content that's posted on c/kickasswomen, I only post pics/clips of women who have given me their consent; I don't steal anyone's content and post it against their will.

 

...it has the same amount of upvotes as one of the posts I made today.

What's the issue here? Why won't the last post show up at or near the top of the page?

*The posts I made today are marked by green rounded squares

[–] [email protected] 5 points 5 months ago* (last edited 5 months ago)

Thank you, this resolved my issue.

I read the wiki and changed "Hardware-accelerated decoding" to "VA-API video decoder".

My original problem was caused by the fact that this was set to automatic, now that it's set to "VA-API video decoder" VLC is able to play mp4 files again without any issues.

[–] [email protected] 10 points 5 months ago* (last edited 5 months ago) (1 children)

I disabled hardware acceleration and VLC is able to play mp4 files again; however, is there a way to turn on hardware acceleration without getting these errors?

Update:

Changing “Hardware-accelerated decoding” to “VA-API video decoder” fixed the issue. Now VLC is able to play mp4 files with hardware acceleration without any issues.

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

Tried it. I don't think there's anything to upgrade:

Jean-Luc@Enterprise:~$ sudo apt dist-upgrade
[sudo] password for Jean-Luc: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 

I'm using Debian 12, Ryzen 7 5700X processor, and Radeon HD 5450 graphics card. I have tried uninstalling and reinstalling VLC but it didn't resolve the issue. Here's an excerpt from the VLC's log file:

glconv_vaapi_x11 error: vaDeriveImage: operation failed

main error: video output creation failed

main error: failed to create video output

avcodec info: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding

How do I resolve this issue?

 
view more: next ›