Kaffeine crashes ALWAYS

Bug #110470 reported by Diwaker Gupta
30
Affects Status Importance Assigned to Milestone
kaffeine (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Feisty by Henrik Nilsen Omma
Declined for Gutsy by Henrik Nilsen Omma

Bug Description

Binary package hint: kaffeine

Kaffeine crashes whenever I try to play ANY kind of media with it. I'm using the Xine engine. Everything used to work fine before. I'm using Feisty Fawn. I get a SIGSEV with the following backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1239455088 (LWP 30713)]
[New Thread -1265198192 (LWP 30716)]
[New Thread -1252357232 (LWP 30715)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb5b6f47f in KXineWidget::getXineLog () from /usr/lib/kde3/libxinepart.so
#7 0xb5b5fac1 in XinePart::slotError () from /usr/lib/kde3/libxinepart.so
#8 0xb5b6867e in XinePart::qt_invoke () from /usr/lib/kde3/libxinepart.so
#9 0xb6a8b88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb6a8bdc0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb5b6e333 in KXineWidget::signalXineError ()
   from /usr/lib/kde3/libxinepart.so
#12 0xb5b7e25f in KXineWidget::initXine () from /usr/lib/kde3/libxinepart.so
#13 0xb5b570b7 in XinePart::slotPlay () from /usr/lib/kde3/libxinepart.so
#14 0xb5b64940 in XinePart::openURL () from /usr/lib/kde3/libxinepart.so
#15 0x0807580b in ?? ()
#16 0x080758df in ?? ()
#17 0x08076991 in ?? ()
#18 0x0807a830 in ?? ()
#19 0x0807e403 in ?? ()
#20 0x08073c46 in ?? ()
#21 0xb71b679f in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#22 0xb71cd1b8 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#23 0xb6a8b88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e17ae0 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#25 0xb6aab81e in QSignal::activate () from /usr/lib/libqt-mt.so.3
#26 0xb6ab3234 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#27 0xb6a22a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#28 0xb6a2488f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#29 0xb71e6ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#30 0xb69b51e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#31 0xb6a154ab in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#32 0xb69c9d25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#33 0xb6a3d136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#34 0xb6a3cf46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#35 0xb6a24609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#36 0x08073faa in ?? ()
#37 0xb623cebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#38 0x08073b71 in ?? ()

Revision history for this message
Sebastian Goth (seezer) wrote :

What Xorg driver do you use?
I have the same problem when I use xorg-driver-fglrx. With "vesa" it works without any errors.

xorg-driver-fglrx:
  Installed: 7.1.0-8.37.6+2.6.22.2-7.2
linux-restricted-modules-2.6.22-7-generic:
  Installed: 2.6.22.2-7.2
kaffeine-xine:
  Installed: 0.8.4-0ubuntu3
libxine1:
  Installed: 1.1.7-1ubuntu1

Revision history for this message
Diwaker Gupta (diwaker) wrote :

I can confirm this bug. I'm using the nVidia proprietary drivers. I haven't tested with 'vesa' yet. What I don't understand is that how come other players using Xine as backend have no problems playing any kind of media (for instance, the xine-ui client itself)

Revision history for this message
Diwaker Gupta (diwaker) wrote :

In fact, I can induce this crash without even playing any media. With Xine selected as the Kaffeine backend, simply go to Settings -> Xine Engine Parameters to cause the crash.

Revision history for this message
Fathi Boudra (fboudra) wrote :

could you check you use which video driver xine use ?
see ~/.xine/config
it must be auto. if it is opengl, this video driver is well know buggy.

Revision history for this message
Fathi Boudra (fboudra) wrote :

pfff what a bad comment ;)

could you check which video driver xine use ?
 see ~/.xine/config
 it must be auto. if it is opengl, this video driver is well known buggy.

Revision history for this message
AleksysP (kovalenya) wrote :

file ~/.xine/config don't exist by default

Revision history for this message
numeritos (ttesone) wrote :

I have exactly the same problem. Unable to use Kaffeine at all. No problem with MPlayer though

Revision history for this message
Jeroen Maris (jealma) wrote :

I have this bug too. This bug is already present in Feisty, but I can reproduce this with Gutsy as well. My laptop has a ATI x1400 card, and with the 8.40 driver and older, this bug seems to come back.
Another problem, which is probably closely related, is that playing a video in kaffeine with the output module "Xv" corrupts the video (inconsistency's, sluggish). Using VLC or Mplayer with the Xv module gives no problems at all. OpenGL seems not to work with Kaffeine as well, this works with VLC and Mplayer.
I'd really like to see this problem solved in the final release from Gutsy.

Revision history for this message
Jeroen Maris (jealma) wrote :

I forgot to say, the other, closely related problem, is with my workstation, using a Nvidia 7300GT with the nvidia 100.14.11 and 100.14.19 driver. With both drivers, the problem persists, when switching to the opensource "nv" driver, the problem is not present, but neither is 3d then :)

Revision history for this message
numeritos (ttesone) wrote :

Now it works just fine and I did nothing to try to fix it... It just magically fixed itself. I'm starting to believe it can be related to compiz-fusion. Do you people use it when you are trying to open Kaffeine?

Revision history for this message
Jeroen Maris (jealma) wrote :

Unless CompizFusion is enabled in the default install of Kubuntu Gutsy, no, I don't use it. If it is enabled, how can I permanently disable it? There's nothing nice about 3d desktop effects for now.

Revision history for this message
Markus Sutter (markussutter) wrote :

Same here in Gutsy.
If I run fglrx, Kaffeine crashs with segfault. Also vlc runs not smooth, the video lacks.
Now I'm using vesa, and all works fine.

Revision history for this message
Andrei Matei (andreimatei) wrote :

I want to confirm this bug, in gutsy. I'm using fglrx for an Mobility Radeon x1300. How can I try different outputs with Kaffeine?

Revision history for this message
ugaciaka (ugaciaka) wrote :

I have upgrade the Kubuntu 7.04 to Kubuntu 7.10 and this problem show in my pc. I installed fglrx with radeon 1600 ATI.

Revision history for this message
kengou (kracine) wrote :

I'm getting this problem too on Kubuntu 7.10 with the fglrx driver, not using any compositing window manager. The weird thing is that it worked soon after I installed Gutsy, but just today apparently it decided to stop working. Gutsy also keeps switching my driver from fglrx to vesa for some reason. I have to say this seems like the buggiest ubuntu release ever.

Revision history for this message
Tony Lewis (tonylewis) wrote :

Me too, Kubuntu Gutsy with VGA compatible controller: ATI Technologies Inc M52 [Mobility Radeon X1300] and fglrx.

Seems to corrupt some screen redraws too. Will try switching to vesa to fix.

Revision history for this message
AleksysP (kovalenya) wrote :

after installation new ati fglrx (8.42) drivers a problem has been solved

Revision history for this message
Tony Lewis (tonylewis) wrote :

Offtopic, but I tried both the 8.42 from here: https://bugs.launchpad.net/ubuntu/+source/fglrx-driver/+bug/156325/comments/11 and via the ATi package.

Both times fglrxinfo reported that OpenGL was being provided by Mesa (as in, software). Any clues as to how best to trial the 8.42.x version?

Revision history for this message
AleksysP (kovalenya) wrote :
Revision history for this message
Tony Lewis (tonylewis) wrote :

AleksysP, thanks. I can confirm, for me (X1300) following the instructions above is a workaround. Seems OK so far

Revision history for this message
dukat (dukat) wrote :

Same problems here on Gutsy with fglrx from distribution on T60p (Mobility FireGL 5200) and Double head. Of course no video at all and also going to xine-settings gives immediate crash.

Revision history for this message
Anthony Mercatante (tonio) wrote :

The difference on that point between kaffeine and vlc for example is that kaffeine uses xcb and xine, and broken support of XV with fglrx causes it to crash.
This seems to be better with latest 8.42 drivers.
Shouldn't be marked as kaffeine bug, as the fact it works with vlc and xv is just in the way xv is used...
This is definately fglrx bug.

Revision history for this message
YAFU (yafu) wrote :

[Diwaker Gupta = Say] "In fact, I can induce this crash without even playing any media. With Xine selected as the Kaffeine backend, simply go to Settings -> Xine Engine Parameters to cause the crash"

I had the same problem in Xine-ui and Kaffeine. In both, the problem has been originated when in the Xine parameters I set Audio and Video Buffer = 0 (In "engine" tab). I have solved it removing the configuration files like this:

https://answers.launchpad.net/ubuntu/+source/kaffeine/+question/11061

Bye.

Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ .

If this still occurs please describe your system in much detail as possible (i.e. your graphics card, driver, etc.), and attach your /var/log/Xorg.0.log after the crash.

Changed in kaffeine:
status: New → Incomplete
Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

I'm sorry, my last post is not exact enough.

I don't know if you could test this in the live environment. However it has to be tested in Hardy Heron.

Thanks!

Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

I assume that a lot more people would have been affected by this bug in hardy heron, so I set this to fix released. If you still suffer on this issue please feel free to reopen the bug -> Set the status to new.

Thanks
emu

Changed in kaffeine:
status: Incomplete → Fix Released
Revision history for this message
Robert Shaw (rshaw3) wrote :

I just encountered this problem after an upgrade to 8.10 when trying to boot into my Windows XP install. The grub entry had been changed to hd4 and should have been hd0. Luckily, I know how to edit the Grub menu. This is still very much a problem.

Revision history for this message
Robert Shaw (rshaw3) wrote :

Opps, Sorry, wrong bug report (long night); meant to respond in another tab to a Grub bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.