vidarlo's questions

I have a box with kodi installed from default repositories. This works great. However, when kodi starts, it is covers only a fraction of the screen.

(Movie posters are pixelized by me, and not an artifact).

If I go to Systems settings in Kodi and change Monitor it scales properly to full screen. The Monitor settings available is Default and HDMI-1.

I do not use a window manager when running kodi, instead selecting it as the desktop on login.

This is, to put it mildly, somewhat irritating. How do I make kodi start in full screen every time?

The video card is a GeForce 210, using the nouveau open source driver.

The monitor is a LG TV, at 1920x1080. The resolution is correct on the login screen and after Kodi starts. Screenshots dimensions are actual dimensions of picture. Monitor is connected via HDMI cable.

The content of /usr/share/xsessions/kodi.desktop is the default:

[Desktop Entry]
Name=Kodi
Comment=This session will start Kodi media center
Exec=kodi-standalone
TryExec=kodi-standalone
Type=Application

I could probably modify this script, but that would be overwritten on upgrade, and this is certainly not intended behaviour for kodi.

Kodi was starting correctly up until recently. I previously had the same problem with 16.04.

I have Machine A, which is a pfsense installation, that sends logs via syslog to a Ubuntu box. The Ubuntu Box will have to rewrite the logs, to replace for instance host names and change format a bit.

The format is generally as follows

Mar  7 00:05:32 hostname service: field1 field2 field3 field4 field5 field6 field7

I would like the possibility of rewriting hostname, service and change order of fields, and filter out messages with a certain value in a certain field, as they are not interesting.

After filtering and handling, the messages should be written to disk in a log file, and sent to another machine via syslog.

Now, the logging part is trivial - simply set up rsyslogd to accept incoming messages, and forward those. However, I'm a bit stuck on the rewriting part. I'm not married to rsyslogd; any syslog-esque daemon will do.

After a upgrade to 18.04, from 16.04, all file names with spaces shows as 'file name'. Previously it was simply file name. File names without space shows up normally:

$ ls
 bar  'foo bar'

While it doesn't affect functionality in any way, I find this visually cluttering.

I use bash as shell.

How can I remove '' showing around file names with spaces?

I regularly log in to boxen via SSH, and run update and so forth as root, using sudo.

I appreciate that sudo asks for password after a certain time, in case I walk away from terminals or such. But as I already have entered either login password, or SSH key phrase, I would prefer sudo not to ask for a password for the first n minutes after a login, but behave as if sudo had been executed successfully immediately after login.

Is this possible to configure so that no password is required for first invocation after login?

To make an example of the desired behaviour

ssh [email protected]
[~]$ sudo somecommand
[~]$ #no password asked.
[~]$ sudo somecommand #n minutes later
[sudo] password for foo: 

I have a file system mounted on /srv, that is unencrypted. This is perfectly fine; the local systems are trusted.

However, I want to perform backups with Jottacloud, which does not support encryption. Is there any reverse encryption file systems, that I can use to get a on-the-fly encrypted version of my normal filesystem mounted somewhere else on the system, that can be backed up?

For performance reasons, I would prefer not to encrypt the base file system, as this contains 8TiB of data, although this is a solution if I find no other.

I would prefer the file names to be encrypted as well, but this is not a requirement.

This is currently on 16.04, but answers does not have to be for this particular version.

How can I install Apache2, php, mysql and set it up with virtual hosts and preferably Let's Encrypt SSL certificate, and then proceed to install Wordpress on it?

I have a 16.04 box running Kodi (15.2+dfsg1-3ubuntu1), and would like to have a cast to Kodi-option.

I'm aware that Kodi supports AirPlay, but support for this on Android phones, Windows and OpenSuSE clients is limited. The browser used on clients is Chrome / Chromium, and thus a Chromecast-like solution would be preferred.

I don't need exactly what Chromecast provides; installing additional plugins/software (on both clients and Kodi) is acceptable.

A solution that can stream movies stored on the remote device, and content like YouTube is preferred over a solution that only works with limited media types.

So is there any good way to cast content from Chrome / Chromium on Windows, Android and Linux, to Kodi?

I have a Technotrend CT2 4650. It worked perfectly on a Ubuntu 16.04.02, which was a upgrade from the previous LTS line as far as I remember. The USB module was dvb_usb_dvbsky.

Then my SSD crashed, and I reinstalled 16.04.02 the other day. It's not discovered anymore. It's shown in lsusb of course, but the module does not seem to initialize it:

Bus 001 Device 003: ID 0b48:3015 TechnoTrend AG 

When I modprobe dvb_usb_dvbsky, this appears in dmesg:

[  175.468458] usbcore: registered new interface driver dvb_usb_dvbsky

I have tested the module on a PC running OpenSuSE, and the following turned up in dmesg:

[220841.422482] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[220841.563158] usb 1-2: New USB device found, idVendor=0b48, idProduct=3015
[220841.563161] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[220841.563162] usb 1-2: Product: TechnoTrend USB2.0
[220841.563163] usb 1-2: Manufacturer: CityCom GmbH
[220841.563164] usb 1-2: SerialNumber: 20151107
[220843.006483] usb 1-2: dvb_usb_v2: found a 'TechnoTrend TT-connect CT2-4650 CI v1.1' in warm state
[220843.006543] usb 1-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[220843.006557] DVB: registering new adapter (TechnoTrend TT-connect CT2-4650 CI v1.1)
[220843.007850] usb 1-2: dvb_usb_v2: MAC address: bc:ea:2b:65:04:ab
[220843.020459] i2c i2c-8: Added multiplexed i2c bus 9
[220843.020462] si2168 8-0064: Silicon Labs Si2168-B40 successfully identified
[220843.020463] si2168 8-0064: firmware version: B 4.0.2
[220843.023511] si2157 9-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[220843.030075] sp2 8-0040: CIMaX SP2 successfully attached
[220843.030085] usb 1-2: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[220843.058431] Registered IR keymap rc-tt-1500
[220843.058529] input: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/rc/rc0/input25
[220843.058616] rc rc0: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/rc/rc0
[220843.058619] usb 1-2: dvb_usb_v2: schedule remote query interval to 300 msecs
[220843.058621] usb 1-2: dvb_usb_v2: 'TechnoTrend TT-connect CT2-4650 CI v1.1' successfully initialized and connected
[220843.058647] usbcore: registered new interface driver dvb_usb_dvbsky
[220849.365260] dvb_ca adapter 0: DVB CAM detected and initialised successfully

As far as I can remember, this is more or less what turned up on the previous Ubuntu install as well - I particularly remember seeing the initialization of the CAM...

I have tried insmodding the required modules manually, with no result.

This is what appears in dmesg when I plug the USB cable to the device, with relevant modules loaded:

[ 3285.678512] usb 1-1.1: new high-speed USB device number 6 using ehci-pci
[ 3285.776059] usb 1-1.1: New USB device found, idVendor=0b48, idProduct=3015
[ 3285.776065] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3285.776070] usb 1-1.1: Product: TechnoTrend USB2.0
[ 3285.776073] usb 1-1.1: Manufacturer: CityCom GmbH
[ 3285.776076] usb 1-1.1: SerialNumber: 20151107

Compared to OpenSuSE (and previous Ubuntu install) it's not much.

Any pointers are welcome.