Bug 234035 - Kaffeine crashes with "Read Error from:"
Summary: Kaffeine crashes with "Read Error from:"
Status: RESOLVED INTENTIONAL
Alias: None
Product: kaffeine
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.x
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-11 13:19 UTC by Walter Cadek
Modified: 2017-10-04 09:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walter Cadek 2010-04-11 13:19:46 UTC
Version:           1.0-svn3 (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

Kaffeine as TV-Player using a USB-DVB-T stick AF9005 works normal, but crashes when receiving signal is weak while searching better antenna position.
A message box appears telling me "Read Error from:"
The only option is to say OK then Kaffeine crashes.

Also the signal strength and quality bar graphs does not work.
Comment 1 Christian S 2010-09-04 20:45:11 UTC
Actually in my case (Kubuntu 10.04 KDE 4.4.5, Kaffeine 1.0-svn3, DVB-T Pci card) kaffeine does only NOT give this error message immediatelly after reboot of the system. After I wait a while before starting kaffeine, I NEVER get the TV to function without reboot. 

Kaffeine will give me the information of the channel/program after clicking a channel but will never get beyond a black screen before the error message appears.
Comment 2 Mauro Carvalho Chehab 2016-06-01 11:23:00 UTC
The Kaffeine version you're using is too old. We just released upstream a version 2.0.1, with is based on KDE5, and changed both the DVB and video play backends. Could you please test the upstream version and see if it works? The README file contains instructions about how to compile it. You can find it at our git repository:

https://quickgit.kde.org/?p=kaffeine.git

As this BZ is on an old version that we're not maintaining upstream anymore, I'm closing the bug. If you find similar issues with version 2.0.1, please re-open.