Following this tutorial, I'd like to map the page-forward button of the mouse (i.e. b:9) to Shift_L. However, using the tools xte and xbinkeys the button-down works, but the button-release does not. Using xte on its own, button-press and -release work. So it has to do something with my ~/.xbindkeys.
Content of ~/.xbindkeys:
# Page forward press
"xte 'keydown Shift_L'"
b:9
# Page forward release
"xte 'keyup Shift_L'"
b:9 + Release
I try to understand the structure of the ubuntu kernel-ppa since I need to upgrade my vanilla kernel. Given the MainlineBuild manual, there exist three packages for installation (e.g. in 4.15.18):
linux-headers-*-generic-*-alllinux-headers-*-generic-*-<arch>linux-image-*-generic-*-<arch>But that is not true for all builds (e.g. 4.14.39 has four packages):
linux-headers-*-generic-*-alllinux-headers-*-generic-*-<arch>linux-image-unsigned-*-generic-*-<arch>linux-modules-*-generic-*-<arch>What's the deal behind this structure, since it is not explained in the MainlineBuild manual?
Are all modules in unsigned kernels build out-of-tree?
What is the benefit and how to install these unsigned kernels properly?
After I've install properitary nvidia drivers in my Ubuntu 14.04.5 (Kernel 4.4.0), I am not longer able to start the display manager or remote session via thinlinc. /var/log/syslog reports
gnome-session[4058]: WARNING: software acceleration check failed: Der Childprocess exited with status 1
gnome-session[4058]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Concerning this post [1], it is possible to bypass the acceleration check, but I don't know where to put the flag --disable-acceleration-check.
Can someone help?
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281
I'd like to simply show a testsource using gstreamer-1.0.
When I use (I guess) non-accelerated output gst-launch-1.0 videotestsrc ! xvimagesink everything works find, but when I try to play it like gst-launch-1.0 videotestsrc ! autovideosink I get the following error:
Setting pipeline to PAUSED ...
libva info: VA-API version 0.35.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 153 (DRI2)
Minor opcode of failed request: 1 (DRI2Connect)
Serial number of failed request: 15
Current serial number in output stream: 15
I've installed NVIDIA-Linux-x86_64-367.44.run on Ubuntu 14.04.5 as follows:
sudo apt-get remove --purge nvidia*service lightdm stop && service x11-common stop./NVIDIA-Linux-x86_64-367.44.run --no-x-checksudo apt-get install libvdpau1 vdpauinfo vdpau-va-driver vainfoHere are some helpful outputs, which still deliver errors:
$ lspci -nnk | grep -i VGA -A2
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e]
Kernel driver in use: nvidia
$ vainfo
libva info: VA-API version 0.35.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 153 (DRI2)
Minor opcode of failed request: 1 (DRI2Connect)
Serial number of failed request: 11
Current serial number in output stream: 11
$ glxinfo
name of display: localhost:10.0
X Error of failed request: GLXBadContext
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 20
Current serial number in output stream: 20
$ uname -a
Linux alpia 4.4.0-38-generic #57~14.04.1-Ubuntu SMP Tue Sep 6 17:20:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ cat /var/log/Xorg.0.log | grep driver
[ 127.579] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 127.579] X.Org XInput driver : 22.1
[ 127.786] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 128.733] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 128.815] ABI class: X.Org XInput driver, version 22.1
[ 128.815] (II) Using input driver 'evdev' for 'Power Button'
[ 128.830] (II) Using input driver 'evdev' for 'Power Button'
[ 128.831] (II) No input driver specified, ignoring this device.
[ 128.831] (II) No input driver specified, ignoring this device.
[ 128.831] (II) No input driver specified, ignoring this device.
[ 128.831] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.832] (II) No input driver specified, ignoring this device.
[ 128.833] (II) No input driver specified, ignoring this device.
[ 128.833] (II) No input driver specified, ignoring this device.
[ 128.833] (II) Using input driver 'evdev' for 'DELL Dell USB Entry Keyboard'
[ 128.833] (II) Using input driver 'evdev' for 'USB Optical Mouse'
[ 128.834] (II) No input driver specified, ignoring this device.
Does anybody have a hint? I know that it worked once with this PC following the instructions, but now something seems to be broken.
It is commonly known that the heartbleed bug exists in the OpenSSL versions 1.0.1 through 1.0.1f (inclusive).
So why are ssh and sshd compiled with OpenSSL 1.0.1, where the bug exists (12.04 -> OpenSSL 1.0.1, 14.04 -> OpenSSL 1.0.1f)?
The libssl.so is of course up-to-date, but if I run
ldd `which ssh`
# or
ldd `which sshd`
nothing links against the non corrupted versions of OpenSSL. But if I run
sshd -V
# Under Ubuntu 12.04 it says:
OpenSSH_5.9p1 Debian-5ubuntu1.4, OpenSSL 1.0.1 14 Mar 2012
# Under Ubuntu 14.04 it says:
OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
They explicitly saying, that they are compiled with a corrupted versions. On https://launchpad.net/ubuntu/+source/openssh nothing is said about any update during the heartbeat bug release.
So how can I be sure, that sshd is not using an affected version of OpenSSL.
If if it does not use it, why do they explicitly saying, that they use an affected version?
When I use the build in OpenVPN functionality of the KDE Network Manager in compairsion to the native openvpn program, I wont get any connection to the internet.
I have a Ubuntu OpenVPN server running. I just created a conf.ovpn configuration file and everything runs perfectly, if I set up the connection by sudo openvpn conf.ovpn. Which means, the tap device, ip routes and connections are established and working.
Now I want to setup the connection with my Kubuntu 14.04 KDE Network Manager. I setup everything like in my configuration file and my manager says, that the connection is established. Also the tap device is configured, but actually no connection goes through.
I mentioned that the ip routes a set differently, so maybe this is the point for hands on?
No OpenVPN:
/sbin/ip -d route
default via 192.168.0.1 dev wlan0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.15 metric 9
With sudo openvpn conf.ovpn (I obfuscated the global addresses by <someIP>):
/sbin/ip -d route
default via 192.168.0.1 dev wlan0 proto static
<someIP>/24 via 192.168.233.2 dev tap0
<someIP>/26 via 192.168.233.2 dev tap0
<someIP> via 192.168.233.2 dev tap0
<someIP>/24 via 192.168.233.2 dev tap0
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.15 metric 9
192.168.116.0/24 via 192.168.233.2 dev tap0
192.168.233.0/24 dev tap0 proto kernel scope link src 192.168.233.49
With Kubuntu Network Manager:
/sbin/ip -d route
default via 192.168.233.2 dev tap0 proto static
<someIP>/24 via 192.168.233.2 dev tap0 proto static
<someIP>/26 via 192.168.233.2 dev tap0 proto static
<someIP> via 192.168.233.2 dev tap0 proto static
<someIP> via 192.168.0.1 dev wlan0 proto static
<someIP>/24 via 192.168.233.2 dev tap0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.15 metric 9
192.168.116.0/24 via 192.168.233.2 dev tap0 proto static
192.168.233.0/24 dev tap0 proto kernel scope link src 192.168.233.49
Does the difference make the problem. And if so, how to set the routes correctly?
Kind regards!
I found my new favorite shortcut (under kubuntu 14.04) Ctrl+Shift+f which brings applications like okular or kate to full screen. Unfortunately it does not work with konsole, chrome, etc. which brings me to the question: Why, and how to do it anyway?
In my Ubuntu 12.04 Terminal one can press Alt + # which leads to the repeation of the following character #-times.
Simple question: For what is it good for? Is it some fancy feature one can use for some purpose?
Greetz, Tik0