Linux -  Kodi flooding XSession errors and filling up disk.
#16
It was not my intention to point fingers or assign blame and I hope my post was not taken that way. I just wanted to post the problem I was having in hopes that it helped someone in the future user/developer. With my VERY limited Linux experience this could absolutely have something to do with my setup and how I maintain my server.

An update for anyone interested. After doing the above I have had no more issues with that error and committing out (#) the Zesty archive in my sources list does not seem to have caused any adverse effects. I wouldn't mind hearing from someone more familiar with Linux as to whether or not what I did will last or am I setting myself for more problems.

Thanks again for any help, and thanks to all KODI developers for the work you do.
Main HTPC/Server, Ubuntu 18.04, Leia 18.0 RC.1
ASUS Chromebox, Ubuntu 18.04, Leia 18.0 RC.1, Aeon Nox 5: SiLVO Mod
Reply
#17
First: I apologize if someone was offended by my last comment.

Second: I give my great thanks to all the people spending time and effort on giving advice and suggestions to solutions to this problem. I really really appreciate their work!

Third: I am still of the opinion that this error is something that has to be or even should have been addressed by the developers or programmers. As I read the comments and explanations this is a known bug (says fritsch ,Team-Kodi Developer 2017-01-21) and has been known for some time – at least since 2016-10-25. I therefore can’t understand why developers release programs or add-ons not implementing errorhandler to catch this. I further can’t understand why Kodi 17 is released and not having the programmers immediately coming forth saying Yes, this we will fix immediately.
From what I read from this thread computers are bricked all over because of this. How can anyone not be frustrated by such? How can frisch live with this?

I am running Kodi on Linux Lite OS 3.2 based on Ubuntu 16.04 LTS. Is it too much to ask developers to test their code on a nearly one year old OS? I might do as shess757 suggests and add from Zesty. But I assume it is known that Zesty is still in Beta1? Should one possibly break the 16.04 LTS version to fix a known error?

Lastly: I would like to thank fritsch for the great suggestion! Next time my customers complains about the programs and solutions I sell and support I’ll just tell them “Go troll elsewhere!” I’m sure this will establish the very best customer relationship!
Wink
Reply
#18
What part of "it's not a kodi bug" is not clear to you?
The bug is in xorg package: https://bugs.launchpad.net/ubuntu/+sourc...ug/1636573 and I assume will be addressed (or not, then you can complain) by the package maintainer.
Reply
#19
(2017-03-09, 10:21)Bitfikler Wrote: First: I apologize if someone was offended by my last comment.

Second: I give my great thanks to all the people spending time and effort on giving advice and suggestions to solutions to this problem. I really really appreciate their work!

Third: I am still of the opinion that this error is something that has to be or even should have been addressed by the developers or programmers. As I read the comments and explanations this is a known bug (says fritsch ,Team-Kodi Developer 2017-01-21) and has been known for some time – at least since 2016-10-25. I therefore can’t understand why developers release programs or add-ons not implementing errorhandler to catch this. I further can’t understand why Kodi 17 is released and not having the programmers immediately coming forth saying Yes, this we will fix immediately.
From what I read from this thread computers are bricked all over because of this. How can anyone not be frustrated by such? How can frisch live with this?

I am running Kodi on Linux Lite OS 3.2 based on Ubuntu 16.04 LTS. Is it too much to ask developers to test their code on a nearly one year old OS? I might do as shess757 suggests and add from Zesty. But I assume it is known that Zesty is still in Beta1? Should one possibly break the 16.04 LTS version to fix a known error?

Lastly: I would like to thank fritsch for the great suggestion! Next time my customers complains about the programs and solutions I sell and support I’ll just tell them “Go troll elsewhere!” I’m sure this will establish the very best customer relationship!
Wink

Did I sell something to you? Did I charge you for something?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#20
No, fritsch, you neither sold or charged me a thing. You just make me sad because you and your colleges leave me and a few others with flooded disks and all you do is referring to that “this is not my fault” (witch by the way is well documented, effemmeffe) . I would like to see a more humble and helpful attitude from a Team-Kodi Developer. Erratum humanum est or something like that.
Till now there are just great and well documented solutions from Junior Members in the forum.

And to be clear: I really like Kodi! There must be hours and hours of work and effort put into the app and this has made a great solution for lots and lots of people!
Reply
#21
If you give me the free time to also do hand holding and detailed support (even though the solution was already named in the thread), next to writing code - then I might find time doing that. For the time being, if you'd check my "Reputation" under the forum name you might see - that you will barely find others that invest that much freetime helping users.

But: I can only explain it for you - I cannot understand it for you.

Edit: For the record: http://forum.kodi.tv/showthread.php?tid=...pid2505693
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#22
(2017-03-09, 12:22)fritsch Wrote: If you give me the free time to also do hand holding and detailed support (even though the solution was already named in the thread), next to writing code - then I might find time doing that. For the time being, if you'd check my "Reputation" under the forum name you might see - that you will barely find others that invest that much freetime helping users.

But: I can only explain it for you - I cannot understand it for you.

Edit: For the record: http://forum.kodi.tv/showthread.php?tid=...pid2505693

"then I might find time doing that." Do what? I don't ask - as far as I can see - for neither hand holding nor detailed support. I simply asked for a little bit of humbleness. I am also sorry I can't give you more free time.

But consider this: If the Kodi developers either had dropped using these Python libraries known to cause these problems or had taken into consideration this error might cause disk flooding you might have had more free time...

I see no need to take this discussion any further. Solution(s) are provided - case closed. You sure have a great reputation and surely invest much time in supporting Kodi users, me including. Thank you for your kind answers and all the best for the further work and support!
Thank you all very much!
Reply
#23
This is the kind of bugs that make me really angry on the Ubuntu developer. It should not be possible at all to fill users directories whit log spams. Something is very wrong!

By the way, who was the one helping out here? Tongue
Reply
#24
(2017-02-24, 16:58)luci84tm Wrote: How can I replicate your solution on a raspberry pi running debian jessie? Smile

python-cryptography version 1.7.1-2 and python-openssl version 16.2.0-1 should bee in Debian Sid/unstable.
Add Sid ore unstable to your source list.

Also check that you have the file /etc/apt/apt.conf and that it says: APT:Big Grinefault-Release "jessie"

That is so you do not upgrade al files to Sid.

Then run the command I mentioned to install the files.
Reply
#25
I had the exact same problem with U16.04 and K16.1 .
Thanks to folowing this thread and a few ubuntu forum posts (spotify was also loggin wild).....I had the courage update cryptography.

Ultimately did the temporary addition of the two deb packages for zesty mentioned above...apt update......then commented them out.

Works perfectly and there's still no log to tail and no change in du on that folder for several hours now.

I am still curious if someone knows for sure whether this is a serious risk/issue for my ubuntu setup ?

Thanks to everyone for sharing in this thread.
Reply
#26
(2017-02-21, 01:16)Klasw Wrote: It is actually a bug, see this:

https://bugs.launchpad.net/ubuntu/+sourc...ug/1636573

What you can do is to install python-cryptography version 1.7.1-2 and python-openssl version 16.2.0-1 from distro Zesty (Ubuntu 17.04). What I did:

Edit /etc/apt/sources.list

add:

#Zesty
deb http://se.archive.ubuntu.com/ubuntu zesty main
deb-src http://se.archive.ubuntu.com/ubuntu zesty main

(for Sweden, you can of course change to your country's repository, fist letters after http://)

sudo aptitude update
sudo aptitude install python-cryptography=1.7.1-2
(will also upgrade python-openssl to latest version)

Thank you very much. This worked for me with Linux Mint 18.1 and Kodi 17. Now I can use the Youtube plugin again.
And those who were seen dancing were thought to be insane by those who could not hear the music. - Friedrich Nietzsche
Reply
#27
(2017-03-13, 09:36)linesma Wrote: ...

Thank you very much. This worked for me with Linux Mint 18.1 and Kodi 17. Now I can use the Youtube plugin again.

Glad I could help out.

For every one how have problems that al files want to upgrade, check that you have the file /etc/apt/apt.conf and that it says the version of your OS:

APT:Big Grinefault-Release "VERSIONNAME"
Reply
#28
Here's an alternate approach to installing the Zesty packages on 16.04 without editing your apt sources:

Download the individual packages:
Code:
wget http://launchpadlibrarian.net/299484105/python-cryptography_1.7.1-2_amd64.deb
wget http://launchpadlibrarian.net/292839640/python-openssl_16.2.0-1_all.deb

Install the packages using dpkg:
Code:
sudo dpkg -i python-cryptography_1.7.1-2_amd64.deb
sudo dpkg -i python-openssl_16.2.0-1_all.deb
Reply
#29
No discussion of apt pinning here yet, so here's another way to install the newer python-cryptography package. In my case I'm using ubuntu Xenial and I'll be upgrading the package and its dependencies to the Zesty versions. Add the zesty repository to /etc/apt/sources.list as stated earlier:

Code:
# Zesty
deb http://us.archive.ubuntu.com/ubuntu/ zesty main restricted

Then to prevent your system from upgrading all packages to Zesty, pin every package from the zesty release at minus ten by adding the following to /etc/apt/preferences

Code:
Package: *
Pin: release n=zesty
Pin-Priority: -10

This will make it so no Zesty packages appear in your searches and none will be installed unless you explicitly say so. To install python-cryptography and its dependencies from the Zesty repo, run...

Code:
sudo apt-get update
sudo apt-get install python-cryptography -t zesty

You want to be sure you can reverse this if you need to, so take note of which packages are upgraded so that you can downgrade with apt-get install python-cryptography=1.2.3-1. The other packages and versions will need to be specified as well if you want them downgraded. If you missed which packages were upgraded, check /var/log/apt/history.log and copy the relevant section for your own records. The new Zesty versions you install will remain installed until you upgrade to a new release and a newer version of python-cryptography is available. So if this breaks anything and you can't fix it you're looking at a reinstall of the OS or a full upgrade to Zesty-- in which case that preferences file is going to cause problems. Anyway, tread carefully.
Reply
#30
Seems I made mistake when I used pip to update cryptography I got some nasty errors what should I do to fix this errors.

https://pastebin.com/a8m18mBb

This is on Debian server with plex server installed.

I need help.

I tried to follow the instruction in this thread http://forum.kodi.tv/showthread.php?tid=306162 because I had extreme amount of errors in kodi.log

https://pastebin.com/G0UKvqr6

And now I have this errors in pip log.
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Kodi flooding XSession errors and filling up disk.00