Kaffeine DVB channel list not displayed

[MirjamWaeckerlin]

Binary package hint: kaffeine

On Feisty Herd 5, Kaffeine doesn't display the channel list for dvb. This reduces the usability of the DVB feature on kaffeine to almost zero. (On Edgy it works fine).

Launching from konsole:

$ kaffeine
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
11
/dev/dvb/adapter0/frontend0 : opened ( TerraTec/qanu USB2.0 Highspeed DVB-T Receiver )
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : : No such file or directory
QLayout "unnamed" added to QWidget "unnamed", which already has a layout

[ingo (rum-topf)]

Would like to confirm this bug on feisty "proper" kernel 2.6.20-15 (got the same DVB-T receiver as Mirjam).

ingo@dicker:~$ kaffeine --version
Qt: 3.3.7
KDE: 3.5.6
Kaffeine Player: 0.8.3

Apparently the scanning feature is broken. Will happily provide more info...

[ingo (rum-topf)]

forgot to say that after successful kaffeine start-up a window with "Can't bind info socket" comes up...

[ingo (rum-topf)]

This is getting more complicated, as kaffeine 0.8.3 and the TerraTec/qanu USB2.0 Highspeed DVB-T Receiver appear to be working perfectly on my Thinkpad T41 with an Intel processor.

I tried both kaffeine 0.8.2 and 0.8.4 to no avail. The same "Can't bind info socket" came up and scanning was not successfull. I attach a listing of my hardware to this mail. Below is the console output of an unsuccessfull kaffeine session (in the hope that someone can make some sense of it):

ingo@dicker:~$ kaffeine
0
/dev/dvb/adapter0/frontend0 : opened ( TerraTec/qanu USB2.0 Highspeed DVB-T Receiver )
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : : No such file or directory
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
ingo@dicker:~$ DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such file or directory
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 212500000 Hz
inv:2 bw:1 fecH:3 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 1/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 578000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 2/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 586000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 3/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 690000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 4/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 754000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 5/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Using DVB device 0:0 "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver"
tuning DVB-T to 834000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
..... LOCKED.
Transponders: 6/6

Invalid section length or timeout: pid=17

Invalid section length or timeout: pid=0

Invalid section length or timeout: pid=16

Frontend closed
Transponders: 6
dvbsi: The end :)
Channels found: 0

[Mark Rijckenberg (markrijckenberg)]

Hi,

I recommend the following workaround procedure that I successfully tested on Kubuntu Hardy Heron (v8.04 final release).

1) Download http://mtrons.googlepages.com/w_scan-20080105.tar.bz2

http://edafe.org/vdr/wscan.html
http://mtrons.googlepages.com/w_scan-20080105.tar.bz2
http://mtrons.googlepages.com/kaffeine

2) unpack the contents of http://mtrons.googlepages.com/w_scan-20080105.tar.bz2 to /tmp

3) edit the file called scan.c (part of source package) and make sure you set the correct symbol rate values for parameter "param.u.qam.symbol_rate". The symbol rate value varies from cable company to cable company. You need to do a little searching (trial and error). Unfortunately, the author of the w_scan program decided to remove the -s (symbol rate argument) option in 2006. That is why you need to edit the source code and recompile, if you live in a different country and have a different cable company than the author of w_scan. ;-)

4) recompile http://mtrons.googlepages.com/w_scan-20080105.tar.bz2 :

go into directory where you unpacked the source package:

enter following commands

a) make
b) make install

5) launch w_scan using CORRECT arguments for your specific goal -> use http://edafe.org/vdr/wscan.html as a reference guide on starting w_scan

For example: if you want to automatically generate a valid channels.dvb file for kaffeine, you need to run the command
w_scan -fc -k > channels.dvb
and then copy the channels.dvb file to ~/.kde/share/apps/kaffeine so that kaffeine can see the newly generated list

So if scan.c is configured correctly, you only need to launch w_scan ONCE so that kaffeine receives a valid channels list file...

6) launch kaffeine

I have personally tried out a lot of DVB programs for Ubuntu and kaffeine was the only program that worked good enough for my purposes.

Hope this will help someone out there with similar issues....

Regards,

Mark Rijckenberg

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!