Android Oreo (8.0) USB debug hassles on Fedora Linux

After my phone received the Android Oreo update I was having trouble getting it to connect to adb. I was seeing errors like this:

$ adb devices
List of devices attached
025d15a338973018        no permissions (verify udev rules); see [http://developer.android.com/tools/device.html]

This recipe worked for me.

https://github.com/M0Rf30/android-udev-rules


Android Oreo, adb, Fedora, Linux

Tip : Don't install p4v in /usr/bin on Fedora 22 and above.

I normally install p4v into /usr/bin and /usr/lib. This is a bad idea on a system such as Fedora 22 or 23 that use Qt5. 

The reason is that the p4v tarball contains a file qt.conf. If this file is placed in /usr/bin it overrides all of the default paths that Qt uses to find the various plugins. This causes some (or most) of the Qt based applications to crash.

On reboot it also prevents the KDE Plasma Workspace from starting preventing anyone from logging in via the graphical desktop. The startup of the graphical desktop fails with a message like below.

This application failed to start because it could not find or load the Qt platform plugin "xcb" in "".   

Warwick 

PS. p4v is the graphical client to the Perforce Helix source code management system.

New NVIDIA graphics card (GeForce GTX 750 Ti) causes me lots of woes

My old NVIDIA graphics card died, so I replaced it with a new one, a GeForce GTX 750 Ti.  Sadly this caused me lots of problems. I couldn't find the right video driver for Fedora 22 until I found this post.

http://forums.fedoraforum.org/showpost.php?p=1692880&postcount=10

I want to say a very big thanks to the forum user leigh123linux

KDE fails to start with "Could not start D-Bus. Can you call qdbus?"

I had been running Fedora 19 for quite a while with KDE as my desktop happily. Then one day after a yum update I could no longer start KDE. An error message appeared each time I tried to start KDE from login.

Could not start D-Bus. Can you call qdbus?

After some debugging it turns out that kde4-config --qt-binaries returns /usr/bin/bin as the location of the Qt binaries, which is a bogus directory. 

# kde4-config --qt-binaries

/usr/bin/bin

I have temporarily worked around the problem by creating a soft link from /usr/bin/bin to /usr/bin while I search for a proper solution.

Installing skype on 64 bit linux

Skype needs a number of i686 RPMS to run on a 64 bit Fedora Linux machine. 

yum install glibc.i686 alsa-lib.i686 libXv.i686 libXScrnSaver.i686 qt.i686 qt-x11.i686

VMWare Player 4.0.2 doesn't like the latest kernel that is available for Fedora 16. A bit of patching is required.

http://weltall.heliohost.org/wordpress/2012/01/26/vmware-workstation-8-0-2-player-4-0-2-fix-for-linux-kernel-3-2-and-3-3/

A big thanks to those that posted the solution.

Making OpenVPN run as a service on Fedora 16

Make sure the config file is named something like myvpn.conf in

/etc/openvpn

# ln -s /lib/systemd/system/openvpn@.service /etc/systemd/system/multi-user.target.wants/openvpn@myvpn.service

Then start and stop the service manually this way:

# systemctl start openvpn@myvpn.service
# systemctl stop openvpn@myvpn.service

Or enable it to start at boot time:

# systemctl enable openvpn@myvpn.service

Thanks to those that took the time to post the solution here: http://forums.fedoraforum.org/showthread.php?t=272612