Other than this patience or install something that isn’t a rolliing release to save headaches you can’t work around
1 Like
-
You are assuming the this is a wide spread issue, that others are facing it and reporting it to the proper authorities. But apart from that one reddit thread I found where only a couple of people were complaining of problems after the tinysparql rename(or replacement or whatever it is) I haven’t seen anyone else/any other places mention this.
So if I am one of only a handful of people that have problems doesn’t that significantly increase the chance that it will take forever for this to get noticed/fixed?
-
Also I was talking about what @nadb said and I quote
emphasis on the words “start by” so I am wondering what should come next now that I have have done the config file part.
What else could I do/provide to help you nice people help me narrow this down? Cause if there is anything else I can do I’d rather do it now while I am still on the latest updates so that I don’t keep rolling back and forth a million times…
- Despite the fact that I have been warned about this before, I admit it, I do like the idea of a rolling distro and would honestly like to give it more of a shot before I decide to switch to something else.
As for the i3 and openbox things you mentioned I googled to learn that those are window managers and they seem to be way beyond me for now, though admittedly that is just based on this quick 5 minutes preliminary search and will require that I look into them further.
How were you doing this, because the way it’s written it sounds like you may have just been adding in #'s and expecting things to change without saving and reloading the configs, and ultimately rebooted without ever actually saving the amended config file so didn’t actually get to test anything.
Whether 1000 people or 1 person has an issue, if there is no bug report sent to the devs, and the devs don’t also run into the issue, then the issue may take forever to be fixed.
1 Like
Well mention it and report the bug, I can’t do it as I do not have the bug. If no one reports no one will fix
they are very easy to install, read the wiki that is how i found out how to do it after install. If you aren’t prepared to do the extra leg work I am sorryy and not trying to be mean or demeaning but linux (especially a rolling release) is not for you.
1 Like
Oh, my bad, let me try to be clearer:
- I opened the document and added # at the begining of the last line then saved and closed it;
- then I tried to open the apps again, nothing;
- I opened the document again and added another # at the begining of the line before the last line, saved and closed;
- tried to open the apps again, nothing.
- rinse and repeat until every single line in the document had a # before it, still nothing.
- lastly removed all the #'s apart from the one before the last line, saved the document, restarted the pc and after the restard tried to launch the apps again nothing;
- so I opened the document to add another # and keep repeating the restart process only to find out that the # I left for the last line was no longer there aka the document had reverted to it’s original form during the restart…
Was that not the correct way of going about it?
Well, no offence please, really, but how am I supposed to report it if I don’t know what’s wrong? Or to be more specific where am I supposed to report it? Is this a gtk issue, a kde plasma issue, a EndeavorOS issue, a wider arch issue, or what?
Sorry, this kind of thing might seem trivial for you guys but I really don’t get it. Specially after so much time on windows where usually you only had 2 avenues: report the bug to that specific programs developer or complain to microsoft. But on linux where there are so many systems that interact with each other in the same enviroment each of them with it’s own developer/mentainer/whatever you call it, who the heck knows… 
Installing them is not what I am worried about, it’s what comes after. 
But yeah, will surely give the wiki a read, like I said that was just my initial impression after a fast and lazy google search.
As for leg work no worries, you’re not mean, makes sense. I will however be picking my battles because I have a tendency to obsess over things(if that wasn’t obvious 
) and I’m afraid that if I let loose with that on linux I’m done, loool. So I am trying to learn to be a bit more selective with my time and what/how much I tackle and to try to accept the things I can’t change/do, like you saw in my other topic.
nothing much comes after, login to it once every now and then just to check it works if you are using them like me you will almost never use them and they will update with the system, you can log into them from your DM.
I can’t figure it out either (very tired and was re reading this trying to find a clue).
It’s a matter of using the process of deduction/elimination. Pick the thing most likely to be causing the issue, then report it to the devs.
If it only happens on X11 or only in Wayland, and you use Plasma or Gnome (or whatever), report it to the DE devs. If it happens in both sessions, report it to the app developer.
What to report comes from a copy-paste from the terminal and what you see when you try to launch the app.
Also, using a search engine for “how to file a bug report to X developer” works wonders.
2 Likes
Sigh, here we go again, gonna be sent from place to place like what happened with keepassxc… 
Fine, whatever, I’ll deal with it tomorrow, gonna try to watch a movie before I turn in, with crappy this crappy audio… 
Good night everyone.
It the price of freedom and it ain’t much, pretty sure when your on the net normally you go from place to place.
Have a good night mate, sleep well.
2 Likes
I don’t think anyone is trying to rag on you here, but here’s the thing - with Linux, you’re using an OS that’s built out of hundreds if not thousands of different components made by completely different developers with completely different methodologies and philosophies.
It’s not a monolothic piece of software built to a singular overarching development vision with a specific, definitive set of standards that any compatible software has to adhere to like Windows or MacOS.
Frankly, it’s something of a minor miracle that any of it works together at all 
You aren’t going to find a one-stop solution to virtually any problem you come across with Linux, because all of the pieces come from all over the place - it’s like expecting the dude who delivers your packages from Amazon to help you work out how to use whatever it is you bought.
The answer is regularly going to be “I don’t know man, ask the person who made it” and that’s the part that makes the whole thing work - you have the freedom and ability to do just that, because the developers aren’t just faceless drones behind the scenes at some megacorp
4 Likes
Morning everyone.
I know and I understand/respect that, said something similar myself in a post above, only not so eloquent/detailed.
My issue is when I can’t even figure out which component is to blame so I don’t know what the proper place to go and ask for help is. Thus you end up with the runaround, and that never feels good… 
Wish there was an easy to use diagnostic tool that could point you in the right direction when there was a problem. Something like the windows troubleshooter only that actually works, cause that shit never did, looool. 
Though I assume your answer to that is gonna be something like "Well if that doesn’t work in a simpler enviroment like windows, how the heck do you expect it could ever work in linux?!".
Anyway, back to the matter at hand, based on what @ddnn said yesterday I figured out this morning how to switch between x11 and wayland and gave it a shot and indeed it seems things work just fine under x11. So I guess I’m gonna go report this to the wayland people…?
Wish me luck, I’ll be back to update this thread when/if a solution is found. Till then thank you for trying to help everyone.
1 Like
Good to see you sticking at it, for now then keep using X11 and check back in with wayland every now and then to see if the issue is resoved. Once you get used to reporting bugs it will get easier, have patience with yourself and the devs and if you do feel overwhelmed put it aside and come back to it (I will often go for a walk or just sit with my cat)
1 Like
Sigh, I hate you(for the next minute or so) you just remined me of my poor old doggy…
Anyway, I don’t really like x11, can’t really put my finger on what it is exactly, maybe it’s not as “smooth” as wayland? Anyway, I’m just gonna keep switching to it whenever I wanna watch a movie or listen to some music with the headphones on. Other then that gonna stay on wayland and hope for the best… 
1 Like
I forgive you, remember the good times
Report it to KDE / Gnome depending on which DE you are using. Not Wayland.
1 Like
Right, after a google search I couldn’t figure out how to report to wayland, except a place to report libinput bugs, but I didn’t think that was it. So for now I ended up here https://discuss.kde.org/c/help/6 we’ll see how it goes.
2 Likes
Hey VIKINGS, I am experiencing the exact same issue with easyeffects.
Looking at this thread sheds some light on the situation but not a lot: https://github.com/wwmm/easyeffects/issues/3437
1 Like
Thank you very much for posting that mate, indeed if I try to open easyeffects from the terminal adding the GSK_RENDERER=gl argument it does launch, but the audio effects only work while the window is active. When I close the window the applied effects don’t persist like they should.
Regardless, reading that link gave me the idea to google “report gtk4 bug” which eventually led me to this forum/thread.
So after reading that I did the following in the console:
[vikings@VIKINGSKINGDOM ~]$ yay amdvlk
13 aur/lib32-amdvlk-bin 2024.Q2.3-1 (+0 0.00)
AMD's standalone Vulkan driver (32-bit) (Stable DEB Release)
12 aur/lib32-amdvlk-2021q2.5 2021.Q2.5-1 (+1 0.00)
AMD's standalone Vulkan driver for pre-Raven (GCN 5.0 APU) and pre-Polaris (GCN 4.0) GPUs. lib32 version.
11 aur/lib32-amdvlk-2023q3.3 2023.Q3.3-2 (+1 0.00)
AMD's standalone Vulkan driver for Pre-GFX10 GPUs (Vega, Polaris)
10 aur/amdgpu-vulkan-switcher-git r1.fadfff5-1 (+0 0.00)
Select needed vulkan implementation with vk_radv, vk_amdvlk or vk_pro prefix
9 aur/lib32-amdvlk-git 2024.Q2.3.r0.10c37d4-1 (+22 0.00)
AMD's standalone Vulkan driver
8 aur/amd-vulkan-prefixes 2-1 (+10 0.10)
Select needed vulkan implementation with vk_radv, vk_amdvlk or vk_pro prefix
7 aur/amdvlk-2021q2.5 2021.Q2.5-2 (+1 0.00) (Orphaned)
AMD's standalone Vulkan driver for pre-Raven (GCN 5.0 APU) and pre-Polaris (GCN 4.0) GPUs.
6 aur/amdvlk-bin 2024.Q2.3-1 (+0 0.00)
AMD's standalone Vulkan driver (Stable DEB Release)
5 aur/amdvlk-debug 2023.Q2.3-1 (+0 0.00) (Out-of-date: 2023-08-26)
AMD's standalone Vulkan driver, debug build
4 aur/amdvlk-2023q3.3 2023.Q3.3-2 (+1 0.00)
AMD's standalone Vulkan driver for Pre-GFX10 GPUs (Vega, Polaris)
3 aur/amdvlk-git 2024.Q2.3.r0.10c37d4-1 (+22 0.00)
AMD's standalone Vulkan driver
2 multilib/lib32-amdvlk 2024.Q3.2-1 (20.0 MiB 79.7 MiB) (Installed)
AMD's standalone Vulkan driver
1 extra/amdvlk 2024.Q3.2-1 (18.3 MiB 73.0 MiB) (Installed)
AMD's standalone Vulkan driver
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> ^[
there is nothing to do
[vikings@VIKINGSKINGDOM ~]$ yay vulkan-radeon
6 aur/lib32-vulkan-radeon-amd-bc250 1:24.2.3-1 (+0 0.00)
Open-source Vulkan driver for AMD GPUs with fixes for the AMD BC-250 - 32-bit
5 aur/lib32-amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 (+8 0.02) (Installed)
Radeon's Vulkan mesa driver (32-bit)
4 aur/vulkan-radeon-amd-bc250 1:24.2.3-1 (+0 0.00)
Open-source Vulkan driver for AMD GPUs with fixes for the AMD BC-250
3 aur/amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 (+16 0.40) (Installed)
Radeon's Vulkan mesa driver
2 multilib/lib32-vulkan-radeon 1:24.2.4-1 (2.6 MiB 11.8 MiB)
Open-source Vulkan driver for AMD GPUs - 32-bit
1 extra/vulkan-radeon 1:24.2.4-1 (2.5 MiB 11.7 MiB)
Open-source Vulkan driver for AMD GPUs
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> ^[
there is nothing to do
[vikings@VIKINGSKINGDOM ~]$ yay -R lib32-amdvlk
[sudo] password for vikings:
checking dependencies...
:: lib32-vulkan-icd-loader optionally requires lib32-vulkan-driver: packaged vulkan driver
Package (1) Old Version Net Change
lib32-amdvlk 2024.Q3.2-1 -79,73 MiB
Total Removed Size: 79,73 MiB
:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/1) removing lib32-amdvlk [------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[vikings@VIKINGSKINGDOM ~]$ yay -R amdvlk
checking dependencies...
:: vulkan-icd-loader optionally requires vulkan-driver: packaged vulkan driver
Package (1) Old Version Net Change
amdvlk 2024.Q3.2-1 -72,97 MiB
Total Removed Size: 72,97 MiB
:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/1) removing amdvlk [------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[vikings@VIKINGSKINGDOM ~]$ yay vulkan-radeon
6 aur/lib32-vulkan-radeon-amd-bc250 1:24.2.3-1 (+0 0.00)
Open-source Vulkan driver for AMD GPUs with fixes for the AMD BC-250 - 32-bit
5 aur/lib32-amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 (+8 0.02) (Installed)
Radeon's Vulkan mesa driver (32-bit)
4 aur/vulkan-radeon-amd-bc250 1:24.2.3-1 (+0 0.00)
Open-source Vulkan driver for AMD GPUs with fixes for the AMD BC-250
3 aur/amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 (+16 0.40) (Installed)
Radeon's Vulkan mesa driver
2 multilib/lib32-vulkan-radeon 1:24.2.4-1 (2.6 MiB 11.8 MiB)
Open-source Vulkan driver for AMD GPUs - 32-bit
1 extra/vulkan-radeon 1:24.2.4-1 (2.5 MiB 11.7 MiB)
Open-source Vulkan driver for AMD GPUs
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1 2
Sync Explicit (2): vulkan-radeon-1:24.2.4-1, lib32-vulkan-radeon-1:24.2.4-1
resolving dependencies...
looking for conflicting packages...
:: vulkan-radeon-1:24.2.4-1 and amdonly-gaming-vulkan-radeon-git-24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 are in conflict. Remove amdonly-gaming-vulkan-radeon-git? [y/N] y
:: lib32-vulkan-radeon-1:24.2.4-1 and lib32-amdonly-gaming-vulkan-radeon-git-24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 are in conflict. Remove lib32-amdonly-gaming-vulkan-radeon-git? [y/N] y
Package (4) Old Version New Version Net Change Download Size
amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 -11,83 MiB
lib32-amdonly-gaming-vulkan-radeon-git 24.3.0_devel.195384.fd11bbbb90e.d41d8cd-1 -11,96 MiB
multilib/lib32-vulkan-radeon 1:24.2.4-1 11,79 MiB 2,60 MiB
extra/vulkan-radeon 1:24.2.4-1 11,67 MiB 2,52 MiB
Total Download Size: 5,12 MiB
Total Installed Size: 23,47 MiB
Net Upgrade Size: -0,33 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
vulkan-radeon-1:24.2.4-1-x86_64 2,5 MiB 14,6 MiB/s 00:00 [------------------------------------------------] 100%
lib32-vulkan-radeon-1:24.2.4-1-x86_64 2,6 MiB 13,3 MiB/s 00:00 [------------------------------------------------] 100%
Total (2/2) 5,1 MiB 24,4 MiB/s 00:00 [------------------------------------------------] 100%
(2/2) checking keys in keyring [------------------------------------------------] 100%
(2/2) checking package integrity [------------------------------------------------] 100%
(2/2) loading package files [------------------------------------------------] 100%
(2/2) checking for file conflicts [------------------------------------------------] 100%
:: Processing package changes...
(1/2) removing lib32-amdonly-gaming-vulkan-radeon-git [------------------------------------------------] 100%
(2/2) removing amdonly-gaming-vulkan-radeon-git [------------------------------------------------] 100%
(1/2) installing vulkan-radeon [------------------------------------------------] 100%
Optional dependencies for vulkan-radeon
vulkan-mesa-layers: additional vulkan layers [installed]
(2/2) installing lib32-vulkan-radeon [------------------------------------------------] 100%
Optional dependencies for lib32-vulkan-radeon
lib32-vulkan-mesa-layers: additional vulkan layers [installed]
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[vikings@VIKINGSKINGDOM ~]$
And now gtk4 apps “work” again, yaaay, however:
- Remains to be seen if other stuff still works, like games…
- The sound is nowhere near as good, will play with easyeffects to see if I can get it back to where it was, but I still don’t understand how any of this should effect sound quality.
- And last but definitely not least(here come the “” in work) can some please please check out this short video I made without giving me any grief that I’m using dropbox(you do not! have to register, just ignore that if it asks you, heck you don’t even have to download anything I don’t think, it should just take you to a page where you can just click play and view the video, it’s way way easier for me to use dropbox instead of some random pastebin site) and tell me WTF is wrong with mangohud and how I can stop it doing that?
Apart from uninstalling mangohud which:
a) wouldn’t really help me as I still would like to use it in games;
b) just to make sure I’m not wasting peoples time I tried and it seems I can’t do it anyway, cause when I try to remove it I get
[vikings@VIKINGSKINGDOM ~]$ yay -R mangohud
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing mangohud breaks dependency 'mangohud' required by goverlay
-> exit status 1
[vikings@VIKINGSKINGDOM ~]$
And maybe are there any other commands I can run to check if other stuff is going wrong under the hood now? Cause that shit just ain’t normal…
[Least the cursor goes to a nice big size in gtk4 apps now as you can see in the video, would be nice if I could somehow apply that to the entire system.]
LE: Like I said been playing with easyeffects to try and get the sound quality back up(without any success so far) and if I Shift+F12 to make mangohud dissapear(it doesn’t make it dissapear aynmore but at least it makes the buttons/stuff beneath it clip through a bit and come to the foreground more to make it easier to see/use them) easyeffects will crash after a minute or two. If I don’t use Shift+F12 it doesn’t seem to crash, so far…
LLE: Just tried the game I had installed and it seems to still work, and mangohud behaves properly in/with it just like it did before aka it does launch along with the game(just like it does with those apps in the video) but there are no weird clipping issues, it displays the correct info, and it does dissapear/appear when I use Shift+F12.
However the game does present some artifact bars at least in the menus and loading screen(they seem to go away, I think but hard to tell, once I am ingame) at the bottom and top of the screen, see for yourselves I’ve marked them in the pic below…
What does “LE:” mean? Is this another/new way of writing “PS:”?