Note to self: Einstellungen für einen erfolgreichen Senderscan der Vu+ Zero an einer unicable-Anlage (Kanal & Frequenz mit anderen Usern abklären). WICHTIG: “Unicable user defined” in der transponder-Config auswählen!

Vielen Dank auch an die freundlichen Helfenden im vu+ support-Forum unter

https://vuplus-forum.org/

In the world of cryptic and rather unhelpful error messages, “invalid json response” when trying to save & update a post or page in wordpress’ new editor runs a close second to my all time favourite “invalid shared memory realm” from Oracle’s absysmal overhyped, and overly expensive database stuff.

So what do you have to do? Simple:

o become “root”

o edit /etc/apache2/apache2.conf using the editor of your choice (nano, emacs, …)

o find the section for /var/www

o Change “AllowOverride None” to “AllowOverride All”

o make sure mod_rewrite for apache is installed and enabled (a2enmod rewrite)

o reload the apache config using systemctl reload apache2

That’s it, switching to SEO-friendly permalinks in Settings -> permalinks on your wordpress site should no longer break making changes to posts / pages and saving them.

Oh yeah, I think I left out the “what it means” part, but hey, I guess you can come up with an explanation of your own 🙂

ffmpeg -ss 565 -to 01:56:40 -i input.mpg -c:a copy -c:v libx264 -crf 18 -preset ultrafast -s 1280x720 -pix_fmt yuv420p -map 0:a? -map 0:v -ignore_unknown output.mkv

Explanation:

-ss 565: cut the first 565 seconds (time format can also be used I think)

-to 01:56:40: cut the movie at 1h56m40secs, discarding the rest

-crf 18: Higher values: smaller file, worse quality; lower values (e. g. 10): bigger file, higher quality.

-i input file

The resulting scaled file will be written to “output.mkv”.

Source:

https://superuser.com/questions/1527662/visually-lossless-1080p-to-720p-using-ffmpeg

Installation of the HDX RealTime Media Engine 2.9 for Microsoft Skype for Business on Linux Mint not working? See below to see what needs changing in the install script.

grep -n LinuxMint HDXRTME_install.sh

1289: "LinuxMint" | "Ubuntu" | "ThinPro" | "Debian")
1447:if [ "$os" != "Ubuntu" ] "$os" != "LinuxMint" ] && [ "$os" != "RedHat" ] && [ "$os" != "ThinPro" ] && [ "$os" != "Debian" ]; then
1468: "Ubuntu" | "LinuxMint" | "ThinPro" | "Debian")
1542: "Ubuntu" | "LinuxMint" | "ThinPro" | "Debian")
1594: "Ubuntu" | "LinuxMint" | "ThinPro" | "Debian")

Change the lines above in the original install script to add Linux Mint support during installation.

If you want to use an existing google authenticator account for use with keepass, the process to extract the base32 seed required by Keepass’ TOTP plugin can be quite involved.

So for posterity, I’ve documented the process here (I am using a company provided iphone and an Ubuntu Linux VM, but I think the process will be quite similar for android systems and other Linux distributions).

If you have any questions, feel free to leave a comment!

Open the google authenticator app on your phone

Select “export” from the hamburger menu

uncheck all accounts & re-check the one you want exported (make sure you don’t accidentally delete the original account on your phone :))

save the generated QR-code (jpg or png) to your photos or wherever & copy it to your Linux machine (I used telegram’s very handy “Saved Messages” feature for this)

install the “zbar-tools” package using apt or apt-get

o clone this git repository:

git clone https://github.com/scito/extract_otp_secret_keys

change to the newly created directory:

cd extract_otp_secret_keys

o extract information from the qr code image (using test.jpg as an example)

zbarimg test.jpg > test.txt

o edit test.txt, remove the leading “QR-Code:” string

o use pip to install the packages protobuf & qrcode:

pip install protobuf==3.20.1 qrcode # use this version as later versions won't work as of this writing

o extract the keys:

python3 extract_otp_secret_keys.py -p test.txt

Use the string labelled “Secret” as the “base32” TOTP-Secret in keepass2

That’s it! From now on, you should be able to generate TOTP tokens even if you just dropped your mobile into the toilet (it happens :))

As I keep forgetting how this works, here’s an example config that will require basic auth for the “/” URI while permitting basic-authless access to “/test” for IPs listed in the Allow from statement (other source IPs will still be able to access stuff in “/test” if proper basic authentication info is provided with the request):

I know I’m about 10 years late to the party, but I recently picked up “Counter Strike: global offensive (“csgo” for short) on Linux when I found out the title was now free to play on steam.

My distro of choice is Linux Mint 19.2 and getting the game to run itself on Linux was not a big issue thanks to using modern drivers for my nvidia gtx1070ti, however no matter what I tried, csgo would insist on playing its ingame sound (both effects & VOIP) on my external speakers (when everybody knows you need a proper headset to fully enjoy the 3d effects the game provides).

After a lot of googling I finally found a workaround which involves some pulseaudio (PA) hacking, but seems to work ok in a reliable and repeatable manner.

The basic principle is that you redirect csgo’s sound output (a “sink” in PA lingo), after it’s been created,to the sound device of your choice.

You’ll need to alt-tab out of the game once it’s started but I’ve found the function is rather stable if you run csgo in “fullscreen windowed” mode.

Once csgo is running, alt-tab to a 2nd virtual desktop and open a shell.

In this new shell, we’ll need to determine the current index / id of the headset like so:

$ pactl list short sinks
0 wave_output modules/module-waveout.c s16le 2ch 44100Hz RUNNING

(the above is just an example as I’m typing this on a Linux VM). The number we need is the “0” in this case, choose this according to the index number where your headset is displayed in pactl’s output.

Next, we create a simple shell script (need to to this only once of course) with the following content, calling it “movesinks.sh” or similar:

#!/bin/bash 
echo "Setting default sink to: $1";
pacmd set-default-sink $1
pacmd list-sink-inputs | grep index | while read line
do
echo "Moving input: ";
echo $line | cut -f2 -d' ';
echo "to sink: $1";
pacmd move-sink-input `echo $line | cut -f2 -d' '` $1

done

(Source: https://askubuntu.com/questions/71863/how-to-change-pulseaudio-sink-with-pacmd-set-default-sink-during-playback)

I’ve chosen $HOME/bin/movesinks.sh as my location for this script, but you can put that wherever you want as long as the directory is in your PATH.

Once you have that script at the ready and executable (chmod 755 ~/bin/movesinks.sh in my case), simply type

movesinks.sh <indexnumber>

where the <indexnumber> is the number that is displayed for your headset in the pactl output listed above.

Now you can cycle back to the virtual desktop that csgo is running on, hit alt-tab there and hey presto!, csgo should now be outputting its sounds to your headset.

Thanks to “Zanna” over at askubuntu.com for the original script!

 

Note to self: Always make a copy of your boot sectors using dd first. 
Note to world: These commands will only work if you have a separate boot partition. 



# take note of your Linux partitions (/dev/sde3 == /, /dev/sde1 = /boot in my case)

fdisk -l 

# Mount Linux partitions using your live installer cd / usb key: 

mount /dev/sde3 /mnt
mount /dev/sde1 /mnt/boot

# re-install grub to /dev/sda

grub-install --boot-directory=/mnt/boot /dev/sda 

Source(s):
https://help.ubuntu.com/community/Grub2/Installing

 

While lineage claims that the update process is mostly automatic on the Galaxy S III (gt-9300i), I found that after downloading an update and rebooting I ended up in my TWRP boot screen, with nothing much automatic going on at all.

It took me a while to determine the storage location of the downloaded updates (that much worked I’m happy to report), and it seems that for me (LineageOS 14.1) they end up on the internal SD card in a directory called

/data/lineageos_updates

 

The trick was to use the “up one level” function in TWRP’s image selection to actually see the root level of the internal SD card.

 

Then, all I needed to do was to select the most recent update (it’s in zip format so you may need to switch the image / zip display in TWRP’s “install” screen, flash it (apparently you don’t have to wipe the cache for it to work), reboot the system and wait about 15 minutes, and hey presto!, here’s my most recent Lineage OS update running fine on my S III.

Caveat: During the initial migration from CM13 to Lineage 14.1, I found the system would not boot properly if I chose to select the “SuperSU” package as offered by the Lineage OS installer. Not choosing to install that package would allow the system to boot properly.

I hope this helps you updating and keeping current your beloved GT-9300i phone!

(c) stackhpc

Our openstack pike installation crashed after a couple of days with tons of error messages in /var/log/mariadb/maria.log in the form of

Error in accept: Bad file descriptor

Some googling  hinted at mariadb running out of open files, but I had some problems getting to grips how to set the number of open files for mariadb 10.1.20 (used by the rdo openstack-pike) on a CentOS 7 system, so here’s for posterity:

1)increase the ulimit in /etc/security/limits.conf as usual:

* hard nofile 1024000
* soft nofile 1024000

2) create the file (if it doesn’t exist, otherwise edit the existing file) /etc/systemd/system/mariadb.service.d/limits.conf 

and add the following lines

[Service]
LimitNOFILE=1024000

2a) reload systemd

# systemctl daemon-reload

3) restart mariadb

# systemctl restart mariadb.service

4) check the results

# mysql -pXXXXXXXX mysql

MariaDB [mysql]> show global variables like 'open%';
+------------------+---------+
| Variable_name | Value |
+------------------+---------+
| open_files_limit | 1024000 |
+------------------+---------+
1 row in set (0.00 sec)

5) Enjoy a hopefully crash-free OpenStack Pike setup 😉