set default gcc, cpp, clang versions in Debian 11, Debian 12 Linux

edit: updated this for Debian 12 / gcc 12, but essentially same solution(s).
see also: https://apt.llvm.org/

Problem: cpp-10 is default in Debian 11

Need: cpp-9 or gcc-9 as default

Solution:

sudo apt install build-essential cpp-12 cpp-11 cpp-10 cpp-9 gcc-12 gcc-11 gcc-10 gcc-9 

sudo update-alternatives --install /usr/bin/cpp cpp /usr/bin/cpp-9 10
sudo update-alternatives --install /usr/bin/cpp cpp /usr/bin/cpp-10 20
sudo update-alternatives --install /usr/bin/cpp cpp /usr/bin/cpp-11 30
sudo update-alternatives --install /usr/bin/cpp cpp /usr/bin/cpp-12 40

update-alternatives --query cpp
sudo update-alternatives --config cpp

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-9 10
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-10 20
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 30
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 40

update-alternatives --query gcc
sudo update-alternatives --config gcc

Resource: https://stackoverflow.com/questions/7832892/how-to-change-the-default-gcc-compiler-in-ubuntu

Potential problems:
If you get something like update-alternatives: error: cannot stat file '/usr/bin/cpp': Too many levels of symbolic links, then sudo rm /etc/alternatives/cpp. BUT be sure to reinstall cpp-* to get the /user/bin links recreated.

And you may do similarly with Clang/Clang++

sudo apt install clang-14 clang-13 clang-12 clang-11

sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-11 10
sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-12 20
sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-13 30
sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-14 40

update-alternatives --query clang
sudo update-alternatives --config clang

sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-11 10
sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-12 20
sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-13 30
sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-14 40

update-alternatives --query clang++
sudo update-alternatives --config clang++

If you prefer non-interactive config, then you may

sudo update-alternatives --set clang /usr/bin/clang-12
sudo update-alternatives --set clang++ /usr/bin/clang++-12

and do so silimarly for any other alternatives



One could compile and install newer GCC as well: https://gcc.gnu.org/install/









~~
good luck!

Written with StackEdit.

SEO:
cpp gcc 9 10 default Debian Linux Ubuntu RHEL CentOS Fedora Arch Mint

Please consider crypto tipping:
  

Installing PowerCLI 10 in Debian 9

Installing PowerCLI 10 in Debian 9
 

The PowerCLI compatibility matrix states PowerShell 6.0.1 is supported. 6.0.2 and 6.1.0-Preview is not. (reference)

Firstly, install PowerShell [almost] as per documentation: (reference) or (reference)

sudo apt remove --purge powershell
sudo apt install libc6 libgcc1 libgssapi-krb5-2 liblttng-ust0 libstdc++6 libcurl3 libunwind8 libuuid1 zlib1g libssl1.0.2 libicu57 libssl1.0.0 libssl1.0.2 libssl1.1 libicu52 libicu57 curl gnupg apt-transport-https
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch main" > /etc/apt/sources.list.d/microsoft.list'
sudo apt update
sudo apt install -y powershell=6.0.1-1.debian.9

sudo apt-mark hold powershell        #Pin this version... 'unhold' for non-recommended versions

pwsh

If you get a Segmentation fault you must sudo apt remove --purge libssl1.0.0!

Install PowerCLI inside PowerShell: (reference)

Install-Module -Name VMware.PowerCLI -Scope CurrentUser
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore   #Accept self-signed certificates

You may later update with

Update-Module VMware.PowerCLI
Update-Help

If you want a scope of AllUsers, then you will have to install with sudo pwsh and perform subsequent update with sudo pwsh as well.

~~~
Good Luck!
Please consider crypto tipping:
  

[Solved] PulseAudio stopped working in Debian 9

[Solved] PulseAudio stopped working in Debian 9 Stretch on Dell Optiplex 9020

After some recent updates, unknown when and unknown why, PulseAudio stopped working properly. Sometimes it would work and sometimes not, it was the fight of all fights.

Multitudes of resources that failed to resolve only aggravated my situation. My final solution came from multiple sources, some of which i have already forgotten, but i will link some that helped.

Specifically to my Dell Optimplex with built-in Intel HD 4000 graphics, HDMI Audio was always a problem to the extreme. It always got in the way. If found a resource that spoke about making an NVidia HDMI work, but in actually this resource helped me disable it. Please refer to: https://www.linuxquestions.org/questions/linux-hardware-18/no-hdmi-audio-in-linux-819172/

When I performed the command aplay -l, I found my Intel HDMI Audio to be card 0. I created/modified my /etc/modprobe.d/sound.conf to contain options snd-hda-intel probe_mask=0xfff2 as per the post. Maybe that doesn’t even do anything. But then I chose the best thing ever. The post said to sudo rmmod snd_hda_intel then sudo modprobe snd_hda_intel, but screw that, i just sudo rmmod snd_hda_intel without reinserting it. Afterward aplay -l did not show card 0, hells yeah!

PulseAudio still caused me super rage mode, it just didn’t work as expected if it worked at all. i had to rm -rf ~/.config/pulse/ and rm ~/.asoundrc multiple times. Mostly the daemon would not start under my user account, but ran much better as root after the above “fix”.

So i decided, I need to run pulseaudio as root always (really this is called running under “system”). I found the command needed to be sudo pulseaudio --system --daemonize --disallow-exit. Warning: official documents say do not do this for security reasons, but F**K, it’s a pile of S**T and fails to work, so i’m doing it.

When I ran this, it seemed to work, but then would flake out. It seemed pulseaudio wanted to re-launch under my useraccount occasionally, so I eventually found to modify /etc/client.conf to include autospawn = no.  Of course  I had to sudo killall pulseaudio multiple times too.

Now everything seemed to work, so I proceeded to make it autostart at reboot this way. I ran sudo crontab -e and inserted @reboot pulseaudio --system --daemonize --disallow-exit. I rebooted and GLORY.

Additional Notes:
I should note that I had to verify my user/groups were in order too with sudo usermod -a -G pulse,pulse-access,audio $(whoami). I also did it for the user pulse but i really think that was overkill. Regardless attempting pulseaudio as user was still B******T. Also note, that modifying group memberships requires a reboot. (There are ways to avoid reboot, but reboot is wisest.)
http://rivendell.tryphon.org/wiki/Debian_6_Installing_Pulse_Audio
https://unix.stackexchange.com/questions/338687/pulseaudio-as-system-wide-systemd-service
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PerfectSetup/ ~~~

As always, good luck!

Coolest nerd tech ever:

DJI Mavic Air @ Amazon

[SOLVED] NFS stopped mounting in Debian 9 Stretch

NFS stopped mounting in Debian 9 Stretch

After some recent updates, unknown when and unknown why, NFS mounting to my Synology device stopped working.

Thanks to these resources, I re-configured it and it works at boot-up again.
https://wiki.manjaro.org/index.php?title=Fstab_-_Use_SystemD_automount
https://linoxide.com/file-system/example-linux-nfs-mount-entry-in-fstab-etcfstab/

My /etc/fstab now looks like this:
172.16.5.49:/volume1/data /mnt/synology nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,rsize=8192,wsize=8192,timeo=14,hard,intr,noatime 0 0

~~~

As always, good luck!

Coolest nerd tech ever:

DJI Mavic Air @ Amazon

Debian Repo Generator | Ubuntu Repo Generator

Debian Repository Generator: https://debgen.simplylinux.ch/

Ubuntu Repository Generator: https://repogen.simplylinux.ch/

~~~

a stop job is running for ifup | NetworkManager

Problem:
a stop job is running for ifup
a stop job is running for NetworkManager

Why:
Debian Jessie and jessie-backports systemd versions 2.15 and 2.30 respectively have a small bug that stalls shutdown.

Tentative Solution: (i.e. unofficial; your mileage may vary)
edit /etc/systemd/system/network-online.target.wants/networking.service, replacing

ExecStop=/sbin/ifdown -a --read-environment

with

ExecStop=/sbin/ifdown -a --read-environment --force --ignore-errors

and also

TimeoutStopSec=5min

with

TimeoutStopSec=5s

~~~

  

install docker in debian jessie without unnecessary cgroupsfs-mount, mountall, and plymouth dependencies

Install docker on your debian jessie workstation without unnecessary cgroupsfs-mount, mountall, and plymouth recommended dependencies.

Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783143

Prerequisite: jessie-backports. Configure jessie-backports or the riskier unstable “sid” repositories before proceeding.

sudo aptitude install aufs-tools libnih-dbus1 libnih1 makedev git
sudo aptitude install -t jessie-backports --without-recommends docker.io

This should work, but be aware aptitude show docker.io shows these are required also:

Depends: adduser, iptables, init-system-helpers (>= 1.18~), perl, libapparmor1 (>= 2.6~devel),
 libc6 (>= 2.14), libdevmapper1.02.1 (>= 2:1.02.90), libsqlite3-0 (>= 3.5.9)

Now add your user account to the docker group; otherwise you will receive the error “permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?”

sudo gpasswd -a $USER docker ( same as sudo usermod -a -G docker $USER)

Logout and re-login. Potentially, you could also exec su -l $USER

Now start docker and set it enabled by default.

sudo systemctl enable docker
sudo systemctl start docker

Now install your preferred containers

docker pull vmware/powerclicore

~ ~ ~
  

Docker : "permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?"

Docker : “permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?”, when docker pull

solution: add username to group docker, logout and relogin ; make certain the service is running

sudo groupadd docker
sudo gpasswd -a $USER docker (same as sudo usermod -a -G docker $USER)

Logout and re-login. Potentially, you could also exec su -l $USER

sudo cystemctl start docker
sudo cystemctl enable docker #if you want it enabled by default

~ ~ ~
  

Quick and Dirty Install SyncThing in Debian with a Systemd Service

I really like BTSync (aka “bittorrent sync” aka “Resillio”). It was a god-send considering a wanted to sync files between multiple computers and NAS, but did not want to store them in the cloud (read as: These are not he DropBoxes you are looking for.) I first tried AeroFS for a short stint, but the vendor soon shifted focus from individual to team/business oriented support. BTSync was released during this time.

I’ve been using BTSync for 2 years now. I stayed at v1.x all this time. BTSync is exactly what i want and has been working great.

When I recently had my work notebook replaced, I decided to “upgrade” BTSync to v2. I seem to likeed it more – the interface worked a little better, so i decided to upgrade BTSync on my Synology Diskstation to v2 also, but it failed to run at all . I seem to be stuck with v1.4.11. Let me be clear, v1 is not bad; It does work. But sometimes, i just can’t live with older, obsolete, and unsupported software. Also, I don’t believe the bittorrent team are freedom-hating, but it is certainly closed-source.

I’ve researched the file-syncing subject many, many, times. On several occasions, I was super close to trying open-source (freedom-loving) Syncthing, but at various times it was not quite ready. Well this time, after looking at it again, it was ready. And so was I.

So here is the quick and dirty install for debian/ubuntu with a systemd service:
(Note: If you are not using systemd, or are using an alternate OS, then there are other service options. )

# install syncthing as per http://apt.syncthing.net/ instructions
curl -s https://syncthing.net/release-key.txt | sudo apt-key add -
echo "deb http://apt.syncthing.net/ syncthing stable" | sudo tee /etc/apt/sources.list.d/syncthing.list
sudo apt-get update
sudo apt-get install syncthing

# create new service file via syncthing's systemd "system" file:
sudo curl -o /etc/systemd/system/syncthing@.service https://raw.githubusercontent.com/syncthing/syncthing/main/etc/linux-systemd/system/syncthing%40.service
sudo curl -o /etc/systemd/system/syncthing-resume.service https://raw.githubusercontent.com/syncthing/syncthing/main/etc/linux-systemd/system/syncthing-resume.service

# enable and start the syncthing per-user service
user=$(whoami)
sudo systemctl daemon-reload
sudo systemctl enable syncthing@${user}
sudo systemctl start syncthing@${user}
systemctl status syncthing@${user}

#launch web-UI
xdg-open http:127.0.0.1:8384

To install on Synology DiskStations, use the SynoCommunity package repository.

I won’t go into the setup, but some key things are the following:

First, be sure to set a “GUI Authentication User” and “GUI Authentication Password” via the Actions>Setting menu, then restart the service.

Next, it is important to understand that a Syncthing relationship is different than BTSync. Rather than a single key that enables syncing as with BTSync, in Syncthing you will add “devices” to each system and specific share folders. You are required to add these “both-ways“. For example for two systems to sync, you will add device A to your device B, and vice-versa. If you wish to sync between three devices, device A will need both device B and C added; device B will need both device A and C added; and finally device C will need both device A and B added. During this, you may need to create the folders before-hand, and pay special attention to the folder ID (key) provided by Syncthing, as it must be the same on each end-point.

Also, I was certainly having some sync/connection issues, and after much troubleshooting, it seemed IPv6 was stopping IPv4 from being the preferred connection method. There is no documentation stating a defacto way to disable IPv6, but after reading https://docs.syncthing.net/users/config.html, i tried setting my “Sync Protocol Listen Addresses” to simply tcp://0.0.0.0, which seems to be the equivalent of saying “use IPv4 on all interfaces.” I am still uncertain if this is necessary or even proper, so use with caution. In fact, I'd recommend do not do this yourself.

With both BTSync and Syncthing, the software repeatedly scans files for hashes, and if changed, will sync updates.  These computations are a heavy burden on an ARM based NAS such as the Synology. Syncthing's default scan interval is 60 seconds.  Every 60 seconds it will scan a sync-folder for changes -- this caused my Synology to continuously thrash the disks.  In an effort to reduce this heavy activity, i went to the advanced settings, chose my folder(s) and set rescanIntervalS to 900 seconds (15 minutes). Since my Synology is more of a backup device and I do not edit these files directly, this is a much better sync-interval.

You should certainly visit the Syncthing Documentation for your needs. Also, You may or may not need to open or port-forward TCP 22000 and UDP 21027 depending on your network environment.

As always, Good Luck!

- - -

Please consider crypto tipping:
  

OpenShot 2.1 crashing on export in Debian 8 Jessie | ShotCut 16.10 for the Win

edit: OpenShot 2.4.x works now, but i'm still a ShotCut fan using v18.x

EPIC FAIL | Story time…
 
OpenShot v2.1 is an opensource video editor that everyone is raving about. It was super easy to get a project going and i really liked the ease of use. But I’ll be damned if i could export any video without a crash.

All my research suggested i needed newer version of ffmpeg and mlt. However, every time i tried installing newer packages from jessie-backports, it just did not work with any useful explanation.

$ sudo aptitude -t jessie-backports install ffmpeg libmlt6
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

It turns out there are commands that could help. Essentially you need to find package dependencies. Enter aptitude why <package-name> or alternatively apt-cache --installed rdepends <package-name> .

aptitude why ffmpeg ; aptitude why libmlt6 reported their dependencies. After a few runs and a few un-installs (sudo aptitude remove flowblade openshot kdelive) I was able to install newer ffmpeg and libmlt6 from jessie-backports. Afterward I was able to re-install the above-mentioned removed packages.

It was s good learning session, but as it turned out OpenShot still crashed for exports – each and every time. I’ve also installed every possible codec to no avail.

So I was back to re-testing alternatives:
- Lightworks was too confusing; I really wanted this to work, but i don’t have that kind of time for the learning-curve right now, although I hope to graduate to it.
- Blender was far beyond overkill. This is primarily for animation, but also does simpler video edits. I want something normal people can use. (Not that I’m claiming to be normal)
- I didn’t get very far with Kdenlive either. I think I didnt give it a real good go, but none-the-less I moved on.
- Avidemux was way too simple for this project, but is super good for quick chops.
- FlowBlade v1.8 almost did it, so close, but i never had enough frames for successful crossfades (disolves).
- ShotCut v16.10 won! It just worked, every time! – Crossfade and export worked for my first project without complaints nor crashes. Thank you ShotCut Team!

Please consider crypto tipping:
  

Google Earth 7 Search function crashes in Debian

It pissed me off countless times, and searching for a solution was a needle in a endless mega-haystack until I found the damned sliver of pointy doom.

Everytime I searched in Google Earth 7.x in Debian, it crashed with something similar to the following:

[1003/095907:WARNING:backend_impl.cc(1875)] Destroying invalid entry.
*** Error in `./googleearth-bin': free(): invalid next size (fast): 0x0000000009398d30 ***
*** Error in `./googleearth-bin': realloc(): invalid next size: 0x0000000009398e70 ***

http://www.webupd8.org/2016/09/google-earth-for-linux-update-brings.html has the solution.

No more Google Earth Search crashes! Thank you webupd8 team!!!

Please consider crypto tipping:
  

Conky 1.10 syntax change and multi-monitor support in Debian 8 via Jessie-Backports

If you do not know, Conky is an on-screen system-monitor for Linux. Search for conky images to to see some glorious screenshots:

Conky 1.10 was released for it’s 10th birthday in June 2015. Conky 1.10.x was rewritten in C++ and now uses a Lua based config.

Debian 8 Stable (Jessie) still uses contains 1.9; However, Jessie-Backports contains the newer 1.10.x branch.

Be prepared to spend some time on fixing your conkyrc files if you decide to upgrade. I believe I spent a good hour fixing mine.

I typically use Debian-Backports to install newer versions of various software. It’s more stable to use the backports rather than the “testing” or “unstable” branches. However, sometimes you can still break your packages. With that warning, here is a link to the Backports instuctions: https://backports.debian.org/Instructions/

I installed conky from jessie-backports with the following command sudo aptitude -t jessie-backports install conky.

Afterward, the display of my various “conkyrc” files was a mess. And I also found during the execution of conky, it mentioned “converting to old syntax”. I found the following page that was a great help: https://github.com/brndnmtthws/conky/wiki/Convert-to-new-1.10-syntax

Using the information from the link, I first made a backup of my conkyrc files. I installed lua with the command sudo aptitude install lua5.3 then copied the converter script and edited the #! to use the proper lua binary which was /usr/bin/lua5.3.

I ran the script on each of my conkyrc files, but some failed. I edited my originals to clean up various problems including purging all the comments. I also paid attention to the line numbers mentioned by the script when it error-ed out.

During all this conversion and testing, I re-ran my conky-launcher script repeatedly. To give you an idea, my script looks as such:

#!/bin/sh
killall conky
sleep 5
nice conky -c ~/.conkyrc-main -d
nice conky -c ~/.conkyrc-main_2 -d
nice conky -c ~/.conkyrc-disk -d
nice conky -c ~/.conkyrc-vlans -d
nice conky -c ~/.conkyrc-todo -d
nice conky -c ~/.conkyrc-messages -d
nice conky -c ~/.conkyrc-proc -d
nice conky -c ~/.conkyrc-usb -d

After successfully converting the files, some would not display, so I edited the new transcribed files and found a few odd lines that i simply deleted. For example, I had some with a line object.0, which caused the conky execution to die.

Almost fully functional, I still found a major issue of some conkyrc files not showing onscreen or they were way-off from where I expected them.

It turned out that version 1.10.x now has proper multi-monitor support. From the information on the page https://github.com/brndnmtthws/conky/issues/249, I added the ximerama_head = line to each of my conkyrc files.

You should note that your monitor ID’s start with 0 (zero). Therefore my first screen’s config was ximerama_head = 0, and my second screens config was ximerama_head = 1,.

After editing almost all my gap_x = lines, my conky looks exactly like it did before.

Was it worth it? I have no idea.

Your turn, have fun!

- - -

Please consider crypto tipping:
  

Prevent downloaded Flowblade 1.x from being downgraded to 0.x upon Debian upgrade

I recently learned about FlowBlade, but my Debian Stable (Jessie 8.0) contained version 0.12, whereas a version 1.8 is available from https://github.com/jliljebl/flowblade/blob/master/flowblade-trunk/docs/INSTALLING.md .

I installed the .deb file using the usual sudo dpkg -i flowblade-1.8.0-1_all.deb method, but when i went to do an sudo aptitude update && sudo aptitude full-upgrade, Debian insisted on “upgrading” flowblade to version 0.12.

I searched the terms “pin” and “pinning” for apt, but that solution seemed specific to repositories. Luckily along the way, I found the correct term “hold”.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Better solution found !!! Jump to the bottom.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The solution was to put the package on hold with sudo aptitude hold flowblade, thusly full-upgrade will now not downgrade. You can conversely unhold with the similar command sudo aptitude unhold flowblade.

One unlikeable caveat however, is that it will still show up as an available update: aptitude search "~U". Since I use Updates: ${execi 360 aptitude search "~U" | wc -l | tail} in my conky setup, it looks like there is always an update to install, which is wrong.

Do you have a better solution? Please share!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Better solution found !!! Do NOT “hold” as described above, instead “Pin” the package as described below:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Edit your /etc/apt/preferences and add the following block:

Package: flowblade
Pin: version 1.*
Pin-Priority: 1001

This will prioritize version 1.x over version 0.x. When 2.x is released, don’t forget about editing your preferences again!

As always, good luck!

- - -

Please consider crypto tipping:
  

Debian replaces Iceweasel with Firefox on March 10, 2016

Today I ran my regular debian full-update only to find this crazy message:

W: Failed to fetch http://mozilla.debian.net/dists/jessie-backports/Release: Unable to find expected entry 'iceweasel-release/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

And surprisingly, the news reported that Debian has replaced Iceweasel (unbranded-Firefox) with officially branded Firefox.

Reference: http://news.softpedia.com/news/debian-is-switching-to-mozilla-firefox-after-a-decade-of-using-iceweasel-501647.shtml

Reference: https://glandium.org/blog/?p=3622

What did this mean? It means that what we’ve come to be accustomed to was suddenly different, but not all that much. I re-located the “Debian Mozilla team” web-page (http://mozilla.debian.net/) and proceded to make changes.

I chose the “release” version of Firefox. I considered the “Extended Support Release” (ESR), which I’d normally opt for, but figured what the heck – I try to live with Mozilla’s continuous “improvements”. For this, I sudo edited my /etc/apt/sources.list (or /etc/apt/sources.d/*.list) and and was sure to remove any references to the old iceweasel packages. I added deb http://mozilla.debian.net/ jessie-backports firefox-release as instructed by the “Debian Mozilla team” page.

I then ran sudo aptitude update && sudo aptitude -t jessie-backports install firefox to install.

After fixing my xfce4-panel launcher, replacing Iceweasel with Firefox, and verifying browser configs were in-tact, I chose to uninstall iceweasel with sudo aptitude remove iceweasel because it will no longer be updated as such. You will find it also wants to uninstall any xul-ext-* packages you may have installed. I tend to install add-ons manually anyway, so this was okay for me.

You might test the the apt-get/aptitude -t option for testing, unstable, or jessie-backports repositories for updated versions of the add-ons, but i’ll leave that to you. For more information on backports, please reference the instructions link from http://backports.debian.org/. (For testing and unstable, you also need to add such repositories, but you know that already, right.)

When all is done, you will of course find Firefox all the exact same as your Iceweasel except now it is branded with Firefox Icons and such. Big woop.

As always, good luck.

Please consider crypto tipping:
  

Install Pinta 1.6 in Debian Jessie 8.0

Paint.NET is a very nice PaintShop Pro alternative for Windows. And luckily, Pinta is fantastic Linux alternative of Paint.NET.

I had Pinta installed in my Debian 8.0 (Jessie) and it was stuck at version 1.5.

I actually use Pinta’s Ubuntu repo to install it and as it turns out I needed to change the repo to reference the “Trusty” version to upgrade to Pinta 1.6.

When I changed as such, the upgrade reported depedency problems with mono, specifically it seems mono v4 must have recently came out.

To resolve my issue i had to first purge pinta and mono-runtime, then reinstall them.

sudo aptitude purge pinta mono-runtime

edit your /etc/apt/sources.list to include:

#Pinta
deb http://ppa.launchpad.net/pinta-maintainers/pinta-stable/ubuntu trusty main 
deb-src http://ppa.launchpad.net/pinta-maintainers/pinta-stable/ubuntu trusty main 

Then update and install:

sudo aptitude update
sudo aptitude install mono-runtime pinta

Pinta should now be v1.6.

You may also want to look at Krita, which is in the Debian repositories – good luck!

---

Please consider crypto tipping:
  

PepperFlash in Firefox (Debian)

UPDATE MAY 2017 : Apparently Adobe is updating NPAPI flash player for firefox again.  Erase all this specialized stuff and sudo aptitude install flashplayer-mozilla instead.

https://steronius.blogspot.com/2017/05/latest-adobe-flash-player-in-firefox.html

~~~~~~~~~~~

Linux aficionados know that Adobe suspended further development of Flash for Linux. Only updates to version 11 will be provided through 2017.

Google Chrome does however continue to update and support a special embedded version of Flash called PepperFlash which is currently at version 16.

I just discovered that PepperFlash can be used with FireFox, albeit in a circumventual way.

"Fresh Player Plugin" is the PepperFlash wrapper for Firefox by i-rinat on github. I originally found this information on Web Upd8.

It was easy to install without issue. I found that my Debian distro had a pepperflash installer in it's repo; however, installing Google Chrome will work just as well.

sudo aptitude install pepperflashplugin-nonfree
sudo update-pepperflashplugin-nonfree --install

Then I was able to install Fresh Player Plugin as per documentation:

sudo apt-get install cmake gcc g++ pkg-config ragel libasound2-dev libssl-dev libglib2.0-dev libpango1.0-dev libgl1-mesa-dev libevent-dev libgtk2.0-dev libxrandr-dev libxrender-dev libxcursor-dev libv4l-dev libgles2-mesa-dev libavcodec-dev libva-dev libvdpau-dev libdrm-dev libicu-dev

#optional:
sudo apt-get install libpulse-dev libjack-jackd2-dev libsoxr-dev

cd ~/Downloads #(or your preferred folder)
git clone https://github.com/i-rinat/freshplayerplugin.git
cd freshplayerplugin
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
make

cp libfreshwrapper-flashplayer.so ~/.mozilla/plugins/

Restart your firefox and take it for a test-run.

My FireFox reported the following using the Adobe About version check.  

To make it easier to update, I've scripted the make/install process which can be run manually on occasion, or as cronjob. If the build ever fails, i've found it best to delete the folder freshplayerplugin and re-clone it.

#!/bin/bash
cd ~/Downloads/freshplayerplugin/
git pull
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..

make && cp libfreshwrapper-flashplayer.so ~/.mozilla/plugins/ && firefox "https://www.adobe.com/software/flash/about/"&

As always, Good luck!

---

Please consider crypto tipping:
  

Compile Remmina 1.1.x in Debian Jessie

Update: Okay this sucks; i'm still having copy/paste issues. But here's the post anyway:

UPDATE 2015 March: Okay this sucks even more, seems i had compilation issues and had to add more cmake flags; HOWEVER, upon install i had segmentation faults when running remmina.

SO, i've found an alternate and preferred method of installing: Add the unstable branch (debian experimental "sid") to your /etc/apt/sources.list and use sudo apt-get -t experimental install remmina freerdp to install the latest available.

i.e. I DO NOT RECOMMEND THE FOLLOWING
--

Remmina 1.0.0 is still the latest version in Debian Jessie (Testing) as of Nov 2014. However Remmina itself is up to version 1.1.x now.

Recently I have had issues with copy/paste (clipboard redirection) not working, so I decided to try to update it. Although not difficult, it was not exactly super quick to find the dependencies either.

note: I always use aptitude but you could just as easily use apt-get.

We will use the github version of Remmina:

sudo aptitude install git
cd ~/Downloads
git clone https://github.com/FreeRDP/Remmina.git

Of course, you probably already have the build tools; otherwise, install them:

sudo aptitude install build-essential

You may have issues with installing the following dependency due to a recent change in debian itself, but you should be able to work it out:

sudo aptitude install libgnutls28-dev

Now, we will install the rest of the dependencies:

sudo aptitude install libavahi-common-dev libavahi-client-dev libavahi-ui-gtk3-dev libvte-2.90-dev libappindicator3-dev libvncserver-dev libxkbfile-dev libfreerdp-dev libtelepathy-glib-dev

Now we can compile and install Remmina:

cd Remmina
cmake -DWITH_LIBSSH=OFF -DWITH_GNOMEKEYRING=OFF
make clean 
make
sudo make install

You need to make install otherwise it will not find the plugins.

I chose "keyring off" because I run XFCE and also when I compiled with it on, I still had copy/paste issues. However, that needs to be thoroughly tested and I was not interested in it.

Now you can run the new Remmina 1.1.x

killall remmina
remmina

good luck!

--

Please consider crypto tipping:
  

SSH - no matching cipher found

Edit: Please do your research, this may re-introduce vulnerable ciphers -- i don't have time to be safe. lmao.  
Please reference https://stribika.github.io/2015/01/04/secure-secure-shell.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After a recent update of either Debian testing (Jessie) or OSX (Mavericks), I could no longer SSH from OSX into my Debian testing boxes.

I really don't know which OS update was at fault, but when I tried to SSH into my Debian testing boxes, i received the following message:

no matching cipher found: client blowfish-cbc,aes128-cbc,3des-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc server aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com

I can't have that -- my daughter needed to play on the minecraft server and she NEEDED TO PLAY NOW!

What this told me is that that my client (OSX) expected blowfish-cbc,aes128-cbc,3des-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc but my server (Debian) supported aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com

That sucks; stupid computer! (Wow, had not said that once since leaving Windows®)

Via web searches, I found that I could force a cipher like so: ssh -c aes128-ctr username@hostname so i did successfully. (I could just as well used ssh -c none username@hostname, but that's risky)

Once logged into my Debian box(es), I edited the ssh daemon config:

sudo nano /etc/ssh/sshd_config

and added the following to the bottom:

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,blowfish-cbc,aes128-cbc,3des-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc

As you can see, since I didn't know if there is an order of preference or not, I erred on the safe side and added the previously supported server ciphers before the client's expected ciphers.

Afterward I had to restart and verify the SSH Daemon:

sudo service sshd restart ; sudo service sshd status

On my OSX client, I tried to SSH and it complained WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! .. Oh my lord the world will end.

An easy fix was ssh-keygen -R hostname, where hostname was my Debian's hostname or IP obviosuly.

Now it worked as expected (and should have never failed in the first place).

-end-

But Daddy, you forgot the minecraft server... START THE MINECRAFT SERVER NOW!

~~~
As always, good luck!

Please consider crypto tipping:
  

Install Teamviewer 9 in 64bit Debain Wheezy/Jessie

Updated 2015 Feb 5.

Debian Wheezy and Debian Jessie 64-bit cannot install ia32-libs due to a change in how multi-architecture works.

Teamviewer installation notes state that we cannot install teamviewer_linux_x64.deb, and must use the 32-bit teamviewer_i386.deb.

But, teamviewer_i386.deb depends on 32-bit libraries.  So we must add multi-architecture:

sudo dpkg --add-architecture i386 ; sudo apt-get update ;

Then if we attempt to install teamviewer_i386.deb, it reports we do not have dependencies met.  We can see the full dependency names by trying to install to package by name (since dpkg -i has added the info locally):

sudo apt-get install teamviewer

Using the output, we can install the dependencies manually:

sudo apt-get install libc6:i386 libgcc1:i386 libasound2:i386 libfreetype6:i386 zlib1g:i386 libsm6:i386 libxdamage1:i386 libxext6:i386 libxfixes3:i386 libxrandr2:i386 libxrender1:i386 libxtst6:i386 libjpeg62:i386 libxinerama1:i386

Then we may install teamviewer properly:

sudo dpkg -i ~/Downloads/teamviewer_i386.deb
# I assume sudo apt-get install teamviewer would also work.

Note: Refer to http://steronius.blogspot.com/2014/02/replacing-logmein-with-teamviewer-on.html for killing/restarting teamviewer over ssh.

good luck.
...

Please consider crypto tipping:
  

PBISOpen Error: ERROR_FILE_NOT_FOUND (2)

TL;DR :

• Error: ERROR_FILE_NOT_FOUND (2)
• $ sudo apt-get install samba-client
• sudo nano /etc/nsswitch.com #edit to contain "hosts: files dns [...]"

--------------------

PBISOpen (Power Broker Identity Services Opensource edition) is a Active Directory authentication system for *nix.  Read as: "Join Domain" for *nix.

I repeatedly failed to install this on a new Debian Jessie (Testing) machine with the " Error: ERROR_FILE_NOT_FOUND (2)" as the result.

It turned out I had to install "samba-client" and it was important to follow the details in this link especially regarding /etc/nsswitch.conf to contain "hosts: files dns [whatever-else-exists]" where dns is second and before any other entries.

so instead of:

Importing registry...

Error: /opt/pbis/bin/lwsm shutdown returned 1 (aborting this script)
Error: ERROR_FILE_NOT_FOUND (2)

dpkg: error processing package pbis-open (--install):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pbis-open
Error installing /home/user/Dropbox/NSU/PBISOpen/pbis-open-8.0.1.2029.linux.x86_64.deb/./packages/pbis-open_8.0.1.2029_amd64.deb
user@skynet:~/Dropbox/NSU/PBISOpen/pbis-open-8.0.1.2029.linux.x86_64.deb $ sudo /opt/pbis/bin/lwsm shutdown
Error: ERROR_FILE_NOT_FOUND (2)


i saw:

Importing registry...

Selecting previously unselected package pbis-open-gui.
(Reading database ... 162521 files and directories currently installed.)
Preparing to unpack .../pbis-open-gui_8.0.1.2029_amd64.deb ...
Unpacking pbis-open-gui (8.0.1.2029) ...
Setting up pbis-open-gui (8.0.1.2029) ...
Installing Packages was successful

New libraries and configurations have been installed for PAM and NSS.
Please reboot so that all processes pick up the new versions.

As root, run domainjoin-gui or domainjoin-cli to join a domain so you can log on
with Active Directory credentials. Example:
domainjoin-cli join MYDOMAIN.COM MyJoinAccount


good luck.

Please consider crypto tipping: