I upgrade from Kubuntu 16.04 to 18.04 and after was Google Chrome really slow at starting. It took about half a minute to start and this annoyed me a bit.
As I always do when an app is in trouble I start it from Konsole and got this error:
Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I search the net but could only find information about the notifications-demon and I tried to install it with the recommendation from others (https://askubuntu.com/questions/52960/notify-send-does-nothing-yet-libnotify-is-installed#53644) but still Google Chrome was slow.
At a site I read something about the notification widget was not added to the desktop panel or desktop (sorry – lost the reference) and right after I added the notification widget to the panel Google Chrome start right away.
A friend of my helped me with the below command to open the firewall on Redhat 7:
firewall-cmd --add-port=8080/tcp --permanent
And redirect from port 80 to port 8080:
firewall-cmd --add-forward-port=port=80:proto=tcp:toport=8080 --permanent
This is often need if you a running a tomcat server…
I have an Ubuntu server 14.04 and got the message during system update:
?> sudo apt-get -y dist-upgrade
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "en_US.UTF-8",
LC_MONETARY = "en_US.UTF-8",
LC_ADDRESS = "en_US.UTF-8",
LC_TELEPHONE = "en_US.UTF-8",
LC_NAME = "en_US.UTF-8",
LC_MEASUREMENT = "en_US.UTF-8",
LC_IDENTIFICATION = "en_US.UTF-8",
LC_NUMERIC = "en_US.UTF-8",
LC_PAPER = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
To solve this you will have to compile the locale definitions:
?> sudo locale-gen en_US en_US.UTF-8
and then reconfigure the locale setup:
?> sudo dpkg-reconfigure locales
I just bought my self a ODroid C2 to be my LibreElec Media Center (http://libreelec.tv).
LibreElec don’t have an image for my new ODroid but an image can be downloaded from the ODroid forum (http://forum.odroid.com/viewtopic.php?f=138&t=20415&hilit=ir+remote).
On Linux you will have to use the dd command to wrote the image to an eMMC/SD module:
?> sudo dd if=<image filename> of=/dev/sdx bs=4M
?> sudo sync
Be careful to write to the correct device or you might loose all data on a disk drive (use the lsblk command to list all disk drives).
Then insert the eMMC/SD module in the the ODroid C2 and connect HDMI, mouse, keyboard and at last the power.
LibreElec should boot up and be ready to use except for your MCE remote.
There is a hole big process to record IR signals from your remote but thats not very easy and my results have not been good.
The easiest way is the get Lirc MCE config file from a standard installation and copy it to the /storage/.config folder on the ODroid C2.
Either install Lirc on an computer and find the file lircd.conf.mceusb or download the file :lircd.conf
To copy it to the ODroid C2 do:
?> scp lircd.conf.mceusb root@libreelec:/storeage/.config/lircd.conf
Reboot the ODroid and the MCE remote should be working now.
What’s my IP address: 18.104.22.168
Have you seen this during a apt-get update:
?> sudo apt-get update
Ign http://dk.archive.ubuntu.com trusty InRelease
Hit http://ppa.launchpad.net trusty InRelease
Hit http://security.ubuntu.com trusty-security InRelease
Hit http://dk.archive.ubuntu.com trusty-updates InRelease
Ign http://extras.ubuntu.com trusty InRelease
Reading package lists... Done
W: There is no public key available for the following key IDs:
Then you are missing a public key in the database.
To solve the problem do:
?> sudo -i bash
[sudo] password for <username>:
?> apt-get install debian-keyring debian-archive-keyring
?> gpg --keyserver keyserver.ubuntu.com --recv 1397BC53640DB551
gpg: requesting key 640DB551 from hkp server keyserver.ubuntu.com
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key D38B4796: public key "Google Inc. (Linux Packages Signing Authority) <firstname.lastname@example.org>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
?> gpg --export 1397BC53640DB551 | apt-key add -
Now will it be possible to update the package system.
I keep getting the error code: M7111-1331-5059 when trying to watch Netflix content.
It caused by the fact I use a VPN service provider to access the Internet.
I use a VPN service provider because I don’t want my ip-address being available to everybody to see.
You might think: Who cares? Well, I do.
Its like wearing a t-shirt with my address on every time I walk out the door and I would never do that.
Most of the time I just want to go out and nobody should know who I am except my friends I meet a long my way or when I order a new car or buy a house etc.
Its like the Internet have become this huge collective where I have no privacy at all.
In the real world would I never accept a shop ask and collect all my information and then let them send it to every shop on the planet.
Or if I buy a newspaper I have to report every article/item I am look at and then this information is sent all over the world completely out of my control.
I know, they need to make money and thats BS.
Its because they are simple to lacy to do there advertisement the right way, safe for there users. And as long as they wont treat me with respect and privacy I expect I wont give them any opportunity to make money of me or collect my data.
Of cause a VPN won’t do it alone, privacy browser plug ins is a necessity as well.
So Netflix as long as you have this policy I will not be your customer.
Dette er an advarsel til andre hundeejere som benytter DIBO BARF hundefoder.
2 gange har jeg fundet glasskår i foder fra DIBO.
Fundet er sket i 2 uafhængige køb af foderet og det er derfor ikke bare en tilfældighed.
Undskyldningen fra forhandleren er, at en ko har spist glas, hvilket kan tænkes, men at en ko spiser glas 2 gange og det findes i fodret i 2 uafhængige købe finder jeg er usandsynligt.
Jeg tror at der sket et uheld under produktionen og at de har været ligeglad og brugt foderet i stedet for at smide det ud.
Jeg har derfor valgt at holde op med at fodre min hund med DIBO BARF hundefoder og jeg vil opfordre dig til at holder dig langt væk fra det produkt.