Видео

Thank you too! Glad it helped.

You're welcome and thank you for taking the time to leave this message. Good to hear it is also working on Ubuntu for you, thank you for the confirmation!

You're welcome, but what files did you try to move and what folder did you open? Do you mean the different libraries to the directory you've created? It might be there is nothing to be moved, it all depends on your system and what is already installed. But are you absolutely sure when you issue the various mv commands that you are indeed in the directory /opt/resolve/libs? Try to list the contents to check if the files are indeed not there, or use the full path in the mv command. Maybe you can post a screenshot or log? Thanks!

@@TechMimic The files you have mentioned in your video, those files and you also mentioned the folder where those files would be. I am following your video step by step. No deviation. Can it be possible that DR 17 does not have those files? As my computer specs are a bit low, at least the graphics card, I tried to install DR17 instead of DR19. I will test it again tomorrow.

@skywalkdesign2023 You have me confused now. You say no deviation but are using a different version of the software. This is a pretty big deviation ;-) I can't say anything about DR17 unfortunately because I've only tested DR18 and DR19 on this channel. Also on the MakeResolveDeb website there are things mentioned when it comes to DR17 (like Intel on Linux not fully supported, white screen startup libssl issues, etc.).

@@TechMimic Sorry. 😇 I will install 18 tomorrow and then we will see if any problem happens. In Windows I have installed and used a little bit, only the video editing section, in DR18.6. I will install that same version in Mint. I don't use Intel. I use AMD and this is the first time I am using Nvidia. ATI Radeons were my favourites. Then AMD acquired it and made huge improvements. But in AMD also, the first time it showed white screen. I force quit and then ran it again and there was that error.

Haha! Graag gedaan en bedankt voor het kijken. Uw Nederlands is prima hoor. Maar inderdaad, ik klink Nederlands en probeer het niet eens te verbergen, dat heeft toch geen zin :-) BTW, you could also try MACMIMIC, that's where I've started posting short macOS related videos since a few weeks, to keep TECHMIMIC a bit more focused on Linux and FreeBSD (mainly). Have a pleasant day sir!

Thank you!

Thanks for watching! Glad it helped.

Glad I could help!

Hi, thanks for watching! Let’s try to fix this then. If it doesn’t show anything in the GUI, there must be something being reported in the terminal. Try to start DaVinci Resolve (DR) from the terminal and see what it says there (using the command "/opt/resolve/bin/resolve"). Another method I recently came across is this. All the libraries used by DR are in the folder /opt/resolve/libs. Create a directory there called oldlibs and move the libs there, as a backup, with the following commands: sudo mv libglib* oldlibs sudo mv libgio* oldlibs sudo mv libgmodule* oldlibs sudo mv libgobject* oldlibs That method is shown in this video: How to install DAVINCI RESOLVE 19 on LINUX MINT 22 with NVIDIA GPU (Step-by-Step) ruclips.net/video/kMpm9kQfiAI/видео.html

Sorry for the delay friend. I ran DR from the terminal as per your guide and DR quit unexpectedly when loading and in the terminal it showed: Host 'Fusion' Killed FusionScript Server [15179] Terminated

@@skywalkdesign2023 No worries! I've just dropped an updated video. But if you get Fusion errors before even starting DR (so I mean, not clicking the Fusion page but when starting it)....a few questions/comments (maybe not all helpful). What is your Linux distro? Is it Linux Mint 21 or 22? Can you monitor your resources when starting up DR? I take it this is a modern system with enough resources? I've personally never seen this one before yet, try checking your DR logs: /home/resolve/Library/Application Support/Blackmagic Design/DaVinci Resolve/Logs, it maybe outdated or incompatible GPU drivers.

@@TechMimic First, I should let you know that your helping mentality gave you another subscriber, me. 🤗 Now, answers of your questions. 1. What is your Linux Distro? Ans. Linux Mint 22. 2. If you can guide me on how, where and what should I look for because when I ran it from terminal, I saw hundreds of entries were running in the terminal. So, if you can point out what to look for, I will give you the result(s). 3. My system is not a modern system. It is pretty old and as I am learning DR, I haven’t upgraded yet. My machine specs: AMD FX4300 Black Edition; Gigabyte 970A-DS3P full ATX mobo; 12 GB Kingston HyperX Fury 1866 MHz RAM Nvidia GT730 2GB DDR5 which uses the driver 472.12 with CUDA. 2 x 240GB SSD (Kingston & Gigabyte) 1 for Windows 10 Pro & 1 for Linux. No dual boot via bootloader. 4. I couldn’t find /home/<user>/resolve/*.* but I found the 'resolve' folder in /opt but there is no 'Library' folder. I can run and edit videos with DR in Windows under the same specs as I have only one PC.

@@skywalkdesign2023 Happy to help and thank you for the subscription! More people need to know about Linux indeed. 1. Excellent 2. What I meant by that was if you open a terminal and run /opt/resolve/bin/resolve from there, you can normally see if DR throws some errors, like the “undefined symbol” errors 3. Very specific on the specs, thank you. Although the GT730 is older it does support hardware-accelerated video encoding (no NVENC I believe, so it will rely more on your CPU) but OpenCL and CUDA should be supported. To just getting to know DR I would say this should work. I tested some of my videos on a GT710 (even more limited than your GT730) and that works. The fact that it is working on Windows confirms your system should work indeed 4. Completely my mistake, I mentioned the wrong path. I can find my logs here: ~/.local/share/DaVinciResolve/logs/ or the full path /home/<user>/.local/share/DaVinciResolve/logs/ Is the Linux Mint driver manager giving you the proprietary drivers (I mean, that is where you found it’s 472.12, or through NVIDIA X Server Settings or nvidia-smi)? It's a shame the RUclips comment section doesn't offer a way to share screenshots, unfortunately.

Thank you for the interaction, good suggestion. I've added your request to the FreeBSD Mondays list.

You're very welcome sir! Thank you

Perfect! Nice of you to leave a comment, much appreciated.

You're very welcome!

Hi, glad you got it to work initially. Can you provide a bit more information so we can start to troubleshoot this together? When and where (at what step) did it stop working, what's the error message, what has changed (firmware update of your Tapo camera)? Just some context would help, thanks!

Glad to hear! Thank you

Hi, so you mean you would like to see a straightforward step-by-step guide to upgrade from KDE Plasma 5 to KDE Plasma 6 on FreeBSD?

@@TechMimic Either to upgrade or just to install Plasma 6 on it's own. Either way is good. Or, if you know of a guide that you could link here, that would be great as well. FreeBSD has quite the learning curve.

@@woolfy02 I'll do both, now on the list. Thank you for the suggestion!

@@TechMimic I appreciate it!

Hi, the video to upgrade from KDE PLASMA 5 to KDE PLASMA 6 on FreeBSD just dropped: How to UPGRADE from KDE Plasma 5 to KDE PLASMA 6 on FREEBSD (Step-by-Step) ruclips.net/video/MYLAV-mLJtk/видео.html

Glad it helped! Thank you

A very kind comment, thank you so much. See you at the next FreeBSD Monday!

Hi, thanks for watching. Are you sure that your device is actually on the Supported Devices List? (fprint.freedesktop.org/supported-devices.html). Can you post a bit more information/context, for example the output of lsusb? Let's start there.

The device is not there in the list.... Is there any other way?

If your device is not even listed in the output of lsusb, you now have the situation that your fingerprint device is not recognised by Linux Mint on the operating system level and you won't get it to work with fprintd. Others had similar issues (please see the comments in the related videos, for example "How to configure FINGERPRINT scanning in LINUX MINT") and others had it listed in lsusb but not supported by fprintd. Even before going down the route of getting it to work with the OS, try to find out if it is on the supported devices list on the fprintd website to avoid burning your time.

Ok thanks

It's such a great OS, more to come! Thanks for watching

You're welcome!

No need for 5 minute introductions!

Hi and thanks for watching. It appears that your user account (vishal) is not in the "sudo" group, which will prevent you from running sudo commands. When logged in as your vishal user type: groups It there's no mention of a group named sudo in the output, switch to the root account with: su - (You could also use any other account with administrative privileges) and type: usermod -aG sudo vishal You should now be able to use "sudo visudo" as the user vishal. Alternatively just use "visudo" as root.

@@TechMimic I have no other account just "vishal" as logged and I tried this ,it doesn't worked.

@@TechMimic after su - I type password which is null just spacebar, then it shows su: Authentication failure.

​@@versionfilm6629 Understood. But if you get authentication failure with su, then your password is still incorrect. I just installed a brand new Linux Mint 22 and created the normal user account during installation. "sudo visudo" works out of the box and my user is part of the sudo group by default. So something is off on your system. Does installing a package (try sudo apt install neofetch for example) work without problems? Anyway, try to use " sudo -i". That should allow you to become root with your own password and allow you to add your user back into the sudo group. Give it a go please. //Adjusted - after re-reading this, obviously sudo -i is not going to work, because sudo commands are not working for you :-)

@@TechMimic both installing not allowed nd sudo -i shows same error.

It is indeed! Now corrected, also for the Linux Mint 21 video. Thanks for watching and pointing that out.

You are so right. Oh My Zsh!

@@TechMimic yup. For lazy people like me oh-my-zsh is perfect.

Hi David, I double-checked and in Linux Mint 22 the procedure is indeed different from Linux Mint 21. Thank you for the nudge. ruclips.net/video/jjRKVPQAN04/видео.html

Hello and thanks for watching. This video tutorial is created for Ubuntu-based distros (like Ubuntu itself, Linux Mint, etc.) so all the "apt" related commands will be "dnf" in Fedora. My guess is that you've downloaded and installed the Quickgui RPM for Fedora. Because then I can reproduce your error: "quickemu was not found in your PATH". As Quickgui is a graphical overlay for Quickemu, make sure that it is actually installed. The related video on this channel ("How to RUN MacOS on LINUX") includes the installation of Quickemu, but again this is for Ubuntu. Quickemu's GitHub provides the information how to install this for Fedora. Once installed, simply add the path where Quickemu is located (Add to your PATH with "export path" or in your .bashrc file) and then when you start Quickgui it will start without issues. If it doesn't work by clicking the Quickemu icon from the menu, try just typing "quickgui" in a terminal after you've configured your PATH variable correctly. I've linked the related videos below. Hope this helped and maybe someone else can add more insights! Related videos: How to RUN MacOS on LINUX (Ubuntu, Linux Mint) ruclips.net/video/itG_rBntF8c/видео.html How to RETAIN system variables across REBOOTS in LINUX (Ubuntu/Fedora/Linux Mint) ruclips.net/video/BdxdKo2303o/видео.html

Hi, we could try to troubleshoot it together. But can you provide some more details and context around your comment, please? At what step does it fail for you or differ from the video, that would be a good start. When you say "still at the top" - do you mean it is still in the default location and the Dash to Dock plugin is not working for you, or is the extension not visible?

Hi, well spotted indeed. The "src not installed, skipped" can, I think, safely be ignored by a normal user if they don’t plan to modify or rebuild the kernel or base system. It would appear for a root user as well, because it wasn't selected in the "Distribution Select" step. But your point is certainly valid. I'm planning on another short video on the topic of wheel/su/sudo (or follow-up topics in general after the initial installation). In this video I kept it simple for now and left it at just logging in as the root user (maybe in a second tty) when needed. Indeed, at 10:03 in the video (the step "Add User Account") a user can be added to the wheel group. Once said video is ready, I'll link to it on screen so any confusion might be mitigated. Thanks again, and I hope you're enjoying your FreeBSD OS!

The related video just dropped. I will place a link to it in this video, thank you again. How to configure and use SU / WHEEL and SUDO in FREEBSD ruclips.net/video/V9yoViz4uTQ/видео.html

And you! Glad it was helpful.

Hi Francisco, you're welcome. But your mouse moves but doesn't click? Interesting indeed. I never ran into that before, but there are some posts about it on the FreeBSD Forum, so I'm sure you will find them during your research. Are you using QEMU or Virtualbox? Also, if you did find a solution meanwhile please let us know!

Thanks!

Hi Francisco; thank you for taking the effort to comment, very kind of you and thanks for watching!

Excellent! Thanks for letting me know. Enjoy Linux Mint!

Thanks for watching, you're most welcome!

Thank you! Glad it helped.

Thanks for watching and leaving this comment - it is very much appreciated!

We do share the same fascination, fantastic OS!

Hi, thanks for watching. I believe on the FitGirl Repack website torrents are provided as well (besides direct download links), or you can find them by using the search engine plugin as demonstrated in the video. I'm afraid I must don't fully understand your question, because downloading a torrent on Linux will work just like on Windows. The qBittorrent interface is the same. There are platform differences of course, after you've downloaded the files.

@@TechMimic I'm sorry I didn't phrase my question clearly.What I wanted to ask if we were to download the torrent will it be safe from malware or will it cause any problems with the system.Like for example windows has defender that helps to keep it somewhat protected.Anyways,thanks for the reply.

@@ericthawin6900 No worries, that's a comparison if Windows is safer or more susceptible to malware than Linux, which it probably is (because it needs Windows Defender in the first place). But I prefer to leave that tin of worms untouched. Just create a virtual machine and test your torrent in there would be my first thought, to isolate if from your production machine. Obviously not all torrents are created equal.

@TechMimic alright good idea thanks

Hi, the fact that it at least enrols once or sometimes more, indicates that the hardware is working. The fact that it is not consistent might be the same hardware indeed or software. So, a good start, including it being on the supported devices list. A silly thing that comes to mind; is it possible that your reader is just dirty? If that's a "swiping" fingerprint device (is it for the x200?), just clean it with rubbing alcohol or similar even if you can't see any dirt. I know, it does sound silly. You could also try a different finger? You might want to take a look here, dedicated to ThinkPad: www.thinkwiki.org/wiki/How_to_enable_the_integrated_fingerprint_reader Don't forget to check the system log on Linux Mint (sudo journalctl) or start fprintd in the foreground (instead of as a daemon) and check the messages on-screen. Hope any of this is helpful to you.

@@TechMimic Hey, thank you for the reply, i already cleaned the sensor (and my finger lol) with rubbing alcohol prior to texting you. And i just switched linux (because i was fed up with windows) so can you guide me how to open fprintd in foreground ? Thanks.

Welcome to Linux! I just looked into it, but I think a better option is to enable debugging so you can see its every move. To explain this specifically for fprintd with the level of detail I want to provide, is a bit hard in a RUclips comment, so I'm going to create a short video for it. That will take me a couple of days, so please bear with me. Meanwhile, if it is a swiping fingerprint device, can you try to play around with the swiping speed? Try to scan your finger slower I mean to give it time to process. Give it a go please.

@@TechMimic Thanks for the reply, i tried swiping my finger at all speeds, even as slow as humanly possible :D, giving it some time to process, but still i had to kill the process, because it would do nothing. I will try with fingerprint GUI.

Hi, your requested video just dropped. Hope it helps! How to troubleshoot and DEBUG FINGERPRINT scanning in LINUX MINT ruclips.net/video/3eeowPlSNx0/видео.html

Hi Pat, thanks for watching! I'm going provide my first thoughts here and hopefully somebody else can add to this. Obviously the first thought has to be that if it was working for Mint 21.3 and LMDE (Debian Edition), the first suspect for me wouldn't be Linux Mint 22 itself, but more the drivers being used. Because this is an older NVIDIA GTX 770 I would start to figure out what was the exact version of the driver on 21.3 (or LMDE) and what changed in 22. If different, try the older driver in 22. If you don't have 21 installed anymore to check this, try the live USB. I'm going to assume you let Driver Manager install the proprietary NVIDIA drivers and they are not working. Also you could try to switch to the open-source Nouveau driver in the driver manager. Maybe you are now using the Nouveau driver, in that case switch to the proprietary one to see if it works. Also if a manual detection of the display doesn't work, a trick I found to be working for me in the past is to turn the 2nd monitor off and boot up. Then turn it on while the OS is running. Or even turn it off and physically plug it in while booting (or while the OS is running), both are worth a try. But most likely none of this will work if it is the driver. Try checking the log for errors (sudo dmesg | grep -i nvidia). Hope this provides a place to start for you.

Thank you, that's very kind of you. Much appreciated!

Thank you, wishing you the same and thanks for watching! That's an excellent suggestion, thank you for that. Intel's AX200 and AX210 are indeed well known and not expensive. It's also good to know that FreeBSD does play well with them. You can simply follow the video and use the same steps and just replace and adjust wherever needed. Re your question (that you can't access local files outside of the home directory) I can think of the fact the LXQT is managing things for the user and it will start GVFS daemons when needed. Most likely that's why it worked after you installed GVFS and rebooted. So for Openbox make sure GVFS services are started. Verify with "ps aux | grep gvfs" after logging into Openbox. Can you try to add this to your Openbox autostart file: /usr/local/libexec/gvfsd & /usr/local/libexec/gvfsd-fuse /run/user/$(id -u)/gvfs & That's (I think, but I haven't tested it) why Yazi or EagleMode don't have an issue, they manage the operations differently then PcManFM. Can you give it a try, please?

​@@TechMimic Thank you for the reply, I will try what you suggested. Again thanks, it's much appreciated.

@@TechMimic Hi, Just reporting back trying your suggestion, (once logged into openbox). Unfortunately adding your suggestion to the openbox config did not work. * Note to self: By default the openbox .config file doesn't exist in the users .config home directory, this needed to be created first for openbox. I'm very new to FreeBSD, nearly 2 weeks new, just so your aware of where i'm at within this journey. It would be great to find a solution, however not to worry if not. Best Regards, I love your channel, the education is greatly appreciated.

Hi, unfortunately I don't have an immediate answer to your GVFS/Openbox challenge, but I've added this as a video topic to the list. I'm interested in Openbox myself and it is something I want to look into for sure. Thank you once again for watching (and the feedback), glad you liked it! Every Monday a FreeBSD video will drop; the so-called "FreeBSD Mondays". Another one this afternoon (CET). Thank you!

Hi, thanks for watching. That's interesting indeed, because your device is actually on the Supported Devices list (fprint.freedesktop.org/supported-devices.html). Can you post a bit more information/context? Is the Fingerprint Authentication option available in the PAM configuration screen? You might want to check if fprintd is actually running (sudo systemctl status fprintd). Also, I've noticed that sometimes restarting fprintd can resolve detection issues (sudo systemctl restart fprintd). If this all doesn't help, you might need to start looking at Linux system logs for messages.

😀Yes and make you a cuppa and do the dishes while they're at it. Glad it helped!

You're welcome! Yes, you can do that as well. Here's a video how to configure that: How to DISABLE authentication in LINUX MINT ruclips.net/video/Casn_ZFdU88/видео.html

Hi, unfortunately not. It's indeed not mentioned on the supported devices list. When I search around I do find Synaptics devices, this specific one mainly in a Lenovo Yoga. It's clear people are trying to get this to work, but it's not supported officially. It's even listed on the "Unsupported devices list" of the fprintd Github page, so that's not a good indication.

Good suggestion. The package fingerprint-gui comes to mind, but maybe not for Linux Mint. I have some ideas in mind, will create a video for it. Thanks for watching!

Hi David, I've seen your request in the comments of the "How to configure fingerprint scanning in Linux Mint". I'll produce a video around it indeed, it is on the list, but several other videos are already done and should be released first. However, I looked into it, created the video and it has now dropped. Hope it helps!

Hi, looks like you're ready to go then and start with virtualization! if it's enabled in the UEFI and cpu-checker tells you so, you should be good to go. I'm just showing multiple methods in the video. But it might be simple, it appears to me like you're missing the | character. I do have the same issue if I use your command, but when I use (vmx|svm), like in the video, the result is 8. The number doesn't matter, but if typed correctly it should read >0. If I remove the | it becomes 0 indeed. This command will just count the # of times it finds 'vmx 'or 'svm' in /proc/cpuinfo and without the | character it will search for the string 'vmx svm', which it won't find, hence the result of 0. Can you give it a whirl with | included, please?