Version: 1.0-pre2 (using 4.3.1 (KDE 4.3.1) "release 178", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (i686) release 2.6.27.29-0.1-default I have been using Kaffeine since it's debut in KDE.I always install all audio and video codecs using distributions specific method.(Like opensuse's one click). But Kaffeine fails to work in 3 out of 4 cases.Though I cannot exactly distinguish a pattern against audio CDs,or VCDs or DVDs,I have had crashes in all types for no apparent reason.The same CDs later were able to be played in Smplayer,kmplayer,vlc,mplayer.It just crashes and KDE crash message appears.(Not even that in KDE4).But kaffeine seems to the preferred,official media player for KDE. What is the purpose of this player,if there is to be no improvement?It is no good.It only brings bad name to Linux/KDE.
Backtrace of the crashes could be useful to determine "who" to blame. There are several crashes related with Phonon (the KDE multimedia library) or even with Xine (upstream bugs, faulty configuration, outdated libraries or missing codecs)... Thank you
Don't mistake me,I actually mean to contribute to kaffeine improvement in whatever way possible,short of 'development'.(I am not a coder).How can I get backtraces of crash reports.There does not seem to be a 'debug' package for kaffeine,in opensuse.I did not see in the list.
No problem :) Even if you don't have debug information from kaffeine, the backtrace could be useful as it could be caused by other libs. Try installing the -debuginfo package for Phonon. In any case, it seems that the "kaffeine-debuginfo" package exists in OpenSuse repos (http://software.opensuse.org/search?q=kaffeine-debuginfo) For more information in how to get a backtrace, check http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports. Thanks
Created attachment 37899 [details] strace report of kaffeine crash
Also,if there is bug in a dependent package,should not kaffeine catch the problem,inform the user and stay ON? I think that can be done.
Mh, I can't read too much from that strace, we need a "backtrace". Try to get a backtrace using GDB (it is explained in the page I mentioned..) The problem is: this "dependent" packages/libs are run/executed in threads in the *same* application. I think there is no method to catch errors on them and avoid crashing the whole app. (it would be really useful ...) Regards
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Hi, I was not able then to give a backtrace at the time, as requested by Dario. Now, I do not have the same environment. Let us close it. If and when faced with, I will create a new bug-report. Thank you for you are still caring. (In reply to Andrew Crouthamel from comment #7) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least 15 days. > Please provide the requested information as soon as possible and set the bug > status as REPORTED. Due to regular bug tracker maintenance, if the bug is > still in NEEDSINFO status with no change in 30 days, the bug will be closed > as RESOLVED > WORKSFORME due to lack of needed information. > > For more information about our bug triaging procedures please read the wiki > located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please set the bug > status as REPORTED so that the KDE team knows that the bug is ready to be > confirmed. > > Thank you for helping us make KDE software even better for everyone!