So, I've started plugging my headphone into my monitor's headphone jack rather than the analog audio ports in my CPU and there's been a drastic reduction in the volume levels. The volume is often insufficient even when everything in my volume settings is maxed out. Here are a couple of things to try out in KDE/Kubuntu/Linux that might help alleviate the situation.
Today, I started dabbling in doing some screen recording in Linux and while I could find programs to record the screen, I couldn't get the audio working as I wanted. By default, the programs record either the system audio, or the mic audio (or if the program is shit, neither); they don't record both the system audio and the mic audio. The fix for this on my Kubuntu 16.04 (Xenial) system which uses the Pulseaudio system to manage audio is as follows:
So I've been having trouble getting a Windows program to work in Wine (Windows emulator) on my Kubuntu 16.04 system. It's a simple program but one that requires .NET 3.5. Considering its simplicity, I thought that it'd work fine using just Mono and it did fire up. However, it wasn't terribly usable throwing constant errors and being very buggy. So I had to also install .NET 3.5.
On a fresh Debian 8 (Jessie) install, I found that I couldn't update the package repository using apt because security.debian.org was always timing out. While I initially thought this was because of a mirroring issue oslt, it turns out that it's because I was trying to access it via the IPV6 that my VPS was using. Turns out that the fix is reasonably straightforward. You simply tell apt not to bother with ipv6 and simply use ipv4 … like so:
echo 'Acquire::ForceIPv4 "true";' >> /etc/apt/apt.conf.d/99force-ipv4
Edit: Skip this and scroll down for a proper fix!
Just tried installing MongoDB support for PHP on Kubuntu 15.10 via pecl and ran into the following error message which caused the installation to fail:
configure: error: Cannot find OpenSSL's libraries
While this can probably be fixed using some magickery, in my case, I did not want SSL support on a dev server. I just wanted to get the fucker up and running. To this end, I discovered that the issue was that I was using:
So I upgraded my Linux box to the latest Kubuntu 15.10 (Wily Werewolf!) and it's been an interesting few days ironing out niggles. One of them has been the missing partition manager icon which (IIRC) was present in 14.04 and where I could control which partitions were automounted at login. From the looks of it, there is no easy solution for this like installing a package or some weird Plasma widget. The only solution I was provided on IRC was the following roundabout-borderline-hack:
So here I was happy with my installation of program foo.exe under Wine in Linux (Kubuntu if you must know). All of a sudden, the program starts whining a little, wobbling a touch, and generally exhibiting wonky tendencies. While I could have uninstalled it and tried to reinstall it to see if that fixes the problem, there's a neater solution that is only available for Wine users.
A quick and easy way to join or merge multiple PDFs together on Linux (Kubuntu 14.10):
pdfunite toc.pdf chapter1.pdf chapter2.pdf book.pdf
This doesn't resample pages or any other nonsense like that either :) pdfunite is provided by the poppler-utils package which should already be installed.
If you want to do the opposite, i.e. split a unified PDF file into multiple ones, poppler-utils also provides the aptly named pdfseparate.
Hope this helps :)
If you see something like the following error message when you run a sed command:
invalid reference \1 on `s' command's RHS
then it (probably) means that your regex capture group has not been escaped properly.
So, if you are using a command like:
then it needs to be escaped like so:
In other words, round parentheses/brackets need to be escaped while the square brackets do not :|
For the last few weeks, I've noticed weird red dots/lines or similar marks on my Kubuntu screen. I'd attributed them to a graphics issue that I'd recently sorted out, particularly because I was mainly noticing these marks when resuming the system from sleep mode. Turns out I was wrong. Very wrong.