[17:29] <StudioUser83> Not sure if this is the place to post, but I was downvoted on AskUbuntu. I'm transcribing audio/video files using LibreOffice Writer and VLC. I have set the global shortcut in VLC to the media play/pause button and it works in some applications, but not with others, like LibreOffice. Why might the shortcut be blocked?
[18:03] <OvenWerks> StudioUser83: I am not very good at shortcuts because I tend not to use them... mental block I guess. Anyway, With just about everything in linux and probably other OS, there is a hierarchy of things where you have layers of control. There would be a base layer like your global short cuts and then as each layer gets added on it can change what is under it. Just like a window on your screen changes 
[18:03] <OvenWerks> the back ground from what your desktop has to what the window back ground is. So if office uses the same shortcut for it's own use, it wouold not make ot to the global table.
[18:05] <OvenWerks> Office might even just decide that all key presses belong to office when office has focus.
[18:07] <StudioUser83> OvenWerks Thanks for the reply. Yeah, I figured it was something like that, though the same thing is not happening on Windows using LibreOffice and VLC. I can't seem to find anything "official" on this. Maybe if there was a way to make VLC hotkeys above all? Even temporarily.
[18:09] <StudioUser83> Also kind of strange, the global hotkeys work with applications like Firefox and Darktable, but not with LO, Thunderbird, or Dolphin.
[18:19] <StudioUser66> check
[18:27] <StudioUser66> Ubuntu Studio 22.04 kernel upgrades always surpass Nvidia proprietary shim. I have to put a hold on those kernel upgrades to keep the system operational for publishing large layouts. In the beginning I would allow the kernel upgrade, one time I edited the grub and told it to boot up on the former kernel, it worked. Another time I allowed it to
[18:27] <StudioUser66> fully upgrade and it left me with (ONE) low resolution graphics driver, I did a reinstall. This time I allowed a upgrade and the system started stuttering, so I edited the grub, told it to boot up always on the older kernel and put all upgrades on hold. Does anyone know a better solution, or is Nvidia a lost cause?
[18:28] <Eickmeyer> StudioUser66: That's not possible. What you're experiencing is a race condition that affects all Ubuntu users. What you might have to do is just run 'sudo dkms autoinstall' in a terminal to mitigate the problem. Unfortunately, it just means you have to keep your machine updated more frequently.
[18:30]  * Eickmeyer runs Nvidia and doesn't experience that problem because I update daily.
[18:30] <StudioUser66> I have just begun studying dkms. Is there a simple formula to initiate this function, or do you know a education source that is direct and to the point?
[18:32] <Eickmeyer> StudioUser66: You just came to it. That's what support chats are for, or even searching askubuntu.com would've given you this solution.
[18:32] <Eickmeyer> StudioUser66: You don't have to know everything. :)
[18:33] <StudioUser66> thanks, that helps me feel more comfortable. Should I execute sudo dkms autoinstall and see how it goes?
[18:34] <Eickmeyer> Yes. That has helped people in the past, and the chat in #ubuntu is a good resource since this isn't an Ubuntu Studio specific issue. (Ubuntu Studio isn't its own distribution).
[18:39] <StudioUser66> I see, well you have gone above and beyond. much thanks. I will have to reestablish my askubuntu acct as it was toasted in the last fire I had with Nvidia and Kubuntu. (it was running from a old deleted email acct) "I was 1 pt from being able to downvote" =D
[18:40] <StudioUser66> one other thing, should i release the hold on this kernel upgrade and upgrade before or after sudo dkms autoinstall
[18:57] <Eickmeyer> StudioUser66: before. dkms autoinstall does all.
[18:59] <StudioUser66> (y)
[18:59] <Eickmeyer> StudioUser66: Though, at this point, it might surprise you and Just Do It (tm) when your kernel upgrades.
[19:02] <StudioUser66> It is my hope that it boots up on a proprietary driver and not open source.
[19:03] <Eickmeyer> Right.
[19:03] <StudioUser66> i can see the dkms working with it
[19:04] <Eickmeyer> Perfect. That means it's building the kernel module for Nvidia.
[19:05] <StudioUser66> now i will reboot go into grub and tell it to boot onto the proper kernel. Thanks again and if possible I will get back on here and let you know how it went.
[19:05] <Eickmeyer> Sounds good. I'll be here.
[19:17] <StudioUser89> It seems to be working. The new kernel was shimmed to match the nvidia proprietary driver, using sudo dkms autoinstall. Now I assume I update every day and make sure that dkms auto is on, or I suppose it stays on until it is told otherwise?
[19:24] <StudioUser89> After looking at this for over a year off and on, I wonder why something so simple was so hard to find, (I chatted with a lot of people). You get one brownie point Eickmeyer. Your nick will be noted in my Kate file. =D
[19:25] <Eickmeyer> StudioUser89: Nah, it should Just Work (tm) unless a race condition happens again. Just make sure you keep your system updated more often as typically they don't update at the same time.
[19:26] <Eickmeyer> If they do, just "sudo dkms autoinstall" and it should fix it before something goes wrong. Keep an eye on what's updating.