| from requests import get | |
| from bs4 import BeautifulSoup | |
| import re | |
| import os | |
| def make_filename(fname): | |
| for c in ',! ().': | |
| fname = fname.replace(c, '_') | |
| while fname != fname.replace('__', '_'): | |
| fname = fname.replace('__', '_') |
pactl info to show which audio server is running. In occasions this tends to fail showing
Connection failure: connection refused.
I think this is saying that there is no connection to an audio server
so you'll need to enable manually the service using systemctl. please comment about it if you know more of this.
If you try installing pipewire without removing pulseaudio you'll get a conflict message complaining about it.
| ## Pre-requisite: You have to know your last commit message from your deleted branch. | |
| git reflog | |
| # Search for message in the list | |
| # a901eda HEAD@{18}: commit: <last commit message> | |
| # Now you have two options, either checkout revision or HEAD | |
| git checkout a901eda | |
| # Or | |
| git checkout HEAD@{18} |
| // I'm tired of extensions that automatically: | |
| // - show welcome pages / walkthroughs | |
| // - show release notes | |
| // - send telemetry | |
| // - recommend things | |
| // | |
| // This disables all of that stuff. | |
| // If you have more config, leave a comment so I can add it!! | |
| { |
"This is the last call for Jaunt-701," the pleasant female voice echoed through the Blue Concourse of New York's Port Authority Terminal. The PAT had not changed much in the last three hundred years or so - it was still gungy and a little frightening. The automated female voice was probably the most plesant thing about it. "This is Jaunt Service to Whitehead City, Mars," the voice continued. "All ticketed passengers should now be in the Blue Concourse sleep lounge. Make sure your validation papers are in order. Thank you."The upstairs lounge was not at all grungy. It was wall-to-wall carpeted in oyster gray. The walls were an eggshell white and hung with plesant nonrepresentational prints. A steady, soothing progression of colors met and swirled on the ceiling. There were one hundred couches in the large room, neatly spaced in rows of ten. Five Jaunt attendants circulate, speakingin low, cherry voices and offering glasses of milk. At one side of the room was the entranceway, flanked by armed guar
| Steps to Submit app to Google Play Store | |
| 1. Prepare your developer account. | |
| 1.1 Register for a Google Play Developer account using your Google Account (https://play.google.com/console/u/0/signup) | |
| 1.2 Once you have a Developer account, you can use the Play Console to publish and manage your apps | |
| 1.3 During the signup process, you'll need to review and accept the Google Play Developer Distribution Agreement | |
| 1.4 Pay registration fee. There is a $25 USD one-time registration fee that you can pay with credit or debit cards | |
| 1.5 Type your account details. Your "Developer name" is displayed to customers on Google Play. | |
| 1.6 You can add more account information after you've created your account. |
Had to do this for some advanced networking with KVM, and couldn't figure out how to do it using the Nework Manager gui. Did find an article later that showed how to do it with nmtui, but it's so much easier to record what you did when using the cli.
In the examples below "eth0" is the name of my physical interface. By default on Ubuntu and most distributions that will almost certainly be different, for example: "eno1", "ens1", or "enp2s0".
To see what everything looks like before starting:
