By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 511

Summary:	Kaffeine-trinity crashes while tuning dvb-t device
Product:	TDE	Reporter:	David Hare <dzfixes-box1>
Component:	tdemultimedia	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	major	CC:	bugwatch, darrella, slavek.banko
Priority:	P5
Version:	3.5.12 [Trinity]
Hardware:	i386
OS:	Debian Squeeze
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description David Hare 2011-09-12 14:45:36 CDT

On first start of Kaffeine the device is identified and channel scan apparently successful. As soon as an attempt is made to select a channel the crash happens. On subsequent restarts (of Kaffeine) crash happens as soon as the "dvb" button is clicked (it will normally tune to the last used channel on opening)

If a working channels configuration is copied over from another machine instead of using the scan, exactly the same result.

Device is believed to be a Twinhan, USB with dual tuner. Snip from <~$ lsusb> :

Bus 002 Device 005: ID 13d3:3237 IMC Networks DTV-DVB UDTT 704J - dual DVB-T Driver

Firmware placed manually in /lib/firmware: dvb-usb-af9015.fw

The crash happens on two different machines in exactly the same way. This is serious for DVB users as few (if any) other applications have the functionality of Kaffeine (gui channel scan, selection, scheduled recording....)

This device works perfectly well in Debian Lenny (KDE 3.5x) and is fully functional using Kaffeine and the same firmware file. The Lenny machine is used as a PVR, obviously upgrade to Squeeze/Trinity is not feasible till this is fixed.

I don't have any other DVB devices to test kaffeine-trinity DVB function with.

Comment 1 Timothy Pearson 2011-09-12 15:18:59 CDT

Can you please post a backtrace of the crash after installing the debugging symbols for kaffeine, kdebase, kdelibs, and qt3?  This will greatly help us in tracking down the origin of the bug.

Note that Kaffeine was updated to the latest upstream sources within the past year or so, so it is very possible that upstream introduced a bug.

Thanks!

Comment 2 Timothy Pearson 2012-01-21 12:57:16 CST

A proper backtrace as described above is essential to being able to repair this bug.  Also, it would be useful to know which graphics card and drivers you are using.

Comment 3 David Hare 2012-01-23 04:11:09 CST

Trouble getting more info is, the device is at my son's house 200 miles away and I don't get to access it very often. Will try again when next opportunity. Would like to get that box moved on from Lenny.

The graphics on that machine is intel (not sure which) but the error has been reproduced here one one box with nvidia fx5200 with proprietary driver and one laptop with Intel GM965/GL960

This is what I got recently from the laptop, from kaffeine's own error box backtrace option, ran out of time to investigate further. It runs TDE 3.5.13

 kaffeine-trinity-dbg, qt-x11-free-dbg, kdelibs-trinity-dbg, libqtinterface-dbg, gdb are installed

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[Thread debugging using libthread_db enabled]
[New Thread 0xac8bfb70 (LWP 3583)]
[New Thread 0xad248b70 (LWP 3582)]
[New Thread 0xada49b70 (LWP 3581)]
[New Thread 0xaa1fcb70 (LWP 3580)]
[New Thread 0xa99fbb70 (LWP 3579)]
[New Thread 0xae9feb70 (LWP 3578)]
[New Thread 0xaf1ffb70 (LWP 3573)]
[New Thread 0xb03e7b70 (LWP 3572)]
[New Thread 0xb3afeb70 (LWP 3562)]
[New Thread 0xb44ffb70 (LWP 3561)]
[New Thread 0xb4f58b70 (LWP 3560)]
0xb7876424 in __kernel_vsyscall ()
#0  0xb7876424 in __kernel_vsyscall ()
#1  0xb6f72482 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb467fc6a in xine_play () from /usr/lib/libxine.so.1
#3  0xb4570bc0 in ?? ()

Comment 4 David Hare 2012-03-06 14:06:40 CST

Fixed!
This is the same problem as in bug 559. The fix described there (replace/opt/trinity/share/apps/kaffeine/logo) solves it. Thanks Slávek Banko