John's Blog

Settings Apps & Notifications See All Apps Pixel Launcher Advanced Additional Settings in the App Display Google app (To the left of the main Home Screen)

Very much like a previous blog post . In that case the bootchart package borked the F21 to F22 upgrade. Here to make a long story short in going from F25 to F26 this time it was infinality. How did I figure it out? Most of the init sequence would execute but couldn't get to gdm so startup only got so far. Booted into single user mode and then did     init 4 Did a dnf distro-sync but that didn't help. But when I looked in /var/log/messages I saw the error message regarding libharfbuzz mentioned here . /usr/lib/libharfbuzz.so.0: undefined reference to 'FT_Get_Var_Blend_Coordinates' That link mentioned infinality.  dnf remove infinality-repo dnf remove freetype-infinality  did the trick. Then I could do     init 5 So infinality seemed to break F25 to F26 upgrade.

This was puzzling me for awhile. Found the answer on the arch linux wiki which is to do a reboot. Apparently if there is skew between the latest kernel and the running kernel, things won't work. After a reboot it moutned find using MTD stuff.

In Gnome Shell 3 (3.18 actually) if I chose DarkGlass as my Shell theme and I clicked on the date at the top the calendar that "pops down" would be cut off at the right side. Actually it was there but the background color was missing. The fix is to find either the file /usr/share/themes/Dark-Glass/gnome-shell/gnome-shell.css or ~/.themes/Dark-Glass/gnome-shell/gnome-shell.css and change width: to min-width like so: /* Calendar popup */                                                                                                                                                           ...

Synergy  is a very useful piece of software that allows two (or I suppose more) computers to share a keyboard and a mouse. One computer is configured as a server, one as a client, and the client computer can be then controlled with the server computer's input devices. In my typical setup at work I have two Ubuntu computers (although I'm a Fedora user at home) - a desktop and a laptop with a dock. The desktop is configured as the server and the client is the laptop. Everything basically would work until such time as I undocked and redocked the laptop . Without thinking too much about what I was doing or why - when it came time to go to a meeting I would simply undock the laptop and go. Usually undocking wasn't too much of an issue but when I returned to my desk on redocking the laptop it would sometimes (but not always) behave incorrectly. The laptop would act as if some modifier key were permanently pressed. And up-arrow press might show "3A" on the termi...

Determine if you're vulnerable to the Logjam Attack - go to  https://weakdh.org/  with your chrome browser and see if you get a blue bar (good) or a red one (bad). When I tried this Firefox was OK, Google Chrome was not. I fixed this by editing /usr/bin/google-chrome and adding the --cipher-suite-blacklist parameter. # Make sure that the profile directory specified in the environment, if any, # overrides the default. if [[ -n "$CHROME_USER_DATA_DIR" ]]; then   # Note: exec -a below is a bashism.   exec -a "$0" "$HERE/chrome"  --user-data-dir="$CHROME_USER_DATA_DIR"  --cipher-suite-blacklist=0xcc15,0x009e,0x0039,0x0033 "$@" else   exec -a "$0" "$HERE/chrome" --cipher-suite-blacklist=0xcc15,0x009e,0x0039,0x0033 "$@" fi as shown above. https://cc.dcsec.uni-hannover.de/  will tell you which ciphers your browser currently supports.

My OBI-100 drops outbound calls usually right at 16 minutes. First thing I noticed there was some stale config on the OBI device. When I thought Google Voice (free) was going away I paid for another VOIP provider. Today I noticed there was some stale config related to the old VOIP provider related to keepalive server config. I restored all of that to default. So hopefully that will fix the problem. But then I wanted to setup syslog for my obi device and also to direct those logs to their own file. On Linux host which is on same LAN open up /etc/rsyslog.conf and uncomment the below lines: # Provides UDP syslog reception # $ModLoad imudp # $UDPServerRun 514 # Provides TCP syslog reception # $ModLoad imtcp # $InputTCPServerRun 514 (i.e. remove the hashes in red ).   2. In /etc/ryslog.conf add the following lines just before the indicated lines (assuming that OBI is at 192.168.1.2). Notice that the & ~ line will discard the message so it won't also end...