Bug 333801 - Kaffeine 0.8.8 crashed under opensuse 12.3 ( system was up to date )
Summary: Kaffeine 0.8.8 crashed under opensuse 12.3 ( system was up to date )
Status: RESOLVED INTENTIONAL
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Christoph Pfister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-24 02:59 UTC by qwatli
Modified: 2016-06-01 10:30 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description qwatli 2014-04-24 02:59:44 UTC 
yes it happened to me also I am using Kaffeine 0.8.8 and install all pacakge that it able it to work but when I start the program and choose one of the free channel it crashed and give me the following ERROR :<< The application unknown (nspluginviewer) crashed and caused the signal 11 (SIGSEGV)  >>

I thought it was becuase of my GAGABYTE motherborad GA-MA 770T-US3
but I disable high speed Gigabit Ethernet and IEEE1394on the Bios and kaffeine 1.1.2 that I configure to work with opensuse12.3 has already doing great with receiving   the signal and display it
and this problem did happened with me after I did finished upgrade  the system to the last signature 

Hope to  guide me to the safest site ASAP
thank you in advaced
Best Regards
 

Reproducible: Always
Comment 1 Mauro Carvalho Chehab 2016-06-01 10:30:12 UTC 
The Kaffeine version you're using is too old. It still uses libxine backend to play videos. We moved to libVLC sometime ago (version 1.3.x), and we just released upstream a version 2.0.1, with is based on KDE5. So, lots of change too. 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 anymore, I'm closing the bug. If you find similar issues with version 2.0.1, please re-open.