Bug 292138 - DvbLinuxDevice::startDevice uses wrong device path
Summary: DvbLinuxDevice::startDevice uses wrong device path
Status: RESOLVED NOT A BUG
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: 1.x
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Christoph Pfister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-21 20:52 UTC by Peter Klotz
Modified: 2017-10-04 09:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Klotz 2012-01-21 20:52:15 UTC
Version:           1.2.2 (using KDE 4.7.4) 
OS:                Linux

After upgrading Arch Linux (x86_64) to Linux 3.2.1 when starting up Kaffeine I get a "No device found." error message although my DVB-T USB stick is attached and properly recognized by the kernel.

"kaffeine --dumpdvb" display this message:

kaffeine(3483) DvbLinuxDevice::startDevice: cannot open frontend "dvb/adapter0/frontend0"

It seems that Kaffeine tries to open the device without the leading "/dev/" attached.

If I create a symbolic link "dvb" in the current directory pointing to "/dev/dvb", Kaffeine starts without the error message and my DVB-T stick works properly.

It seems that since the upgrade to Linux 3.2.1 (or maybe another update that came in the last few days) the path used by Kaffeine is no longer correct.

Reproducible: Always

Steps to Reproduce:
* Attach DVB-T USB stick
* Kernel recognizes stick and loads firmware
* Start Kaffeine

Actual Results:  
* Kaffeine displays error message "No device found."
* DVB-T does not work

Expected Results:  
* No error message
* DVB-T should work
Comment 1 Heiko Baums 2012-01-21 23:35:09 UTC
Another way workaround this is to first cd to /dev and then start kaffeine from the commandline.

Here's the downstream bug report:
https://bugs.archlinux.org/task/28017
Comment 2 Peter Klotz 2012-01-27 20:46:13 UTC
It seems, an upgrade to udev 179 fixed the problem. I am still using the same Kaffeine version.