FS#28017 - [kaffeine]: wrong device search path

Attached to Project: Arch Linux
Opened by Florian Zeitz (Florob) - Friday, 20 January 2012, 19:26 GMT
Last edited by Dan McGee (toofishes) - Monday, 30 January 2012, 02:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Kaffeine appears to be looking for DVB devices in the current working directory instead of under /dev.
Starting it from anywhere but /dev the output is:
kaffeine(1468) DvbLinuxDevice::startDevice: cannot open frontend "dvb/adapter0/frontend0"


Additional info:
* package version 1.2.2-2
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 30 January 2012, 02:39 GMT
Reason for closing:  Works for me
Additional comments about closing:  Fixed with latest udev/kernel
Comment by Heiko Baums (cyberpatrol) - Saturday, 21 January 2012, 14:48 GMT
Same happens to me, too. If I start kaffeine from the Xfce menu and change to the DVB tab I get an alert window with the message "No device found.". If I start it from console with ~ as the current working directory I get the same error message as Florian. If I start it from console with /dev as current working directory dvb is working again in kaffeine.
Comment by Peter Klotz (p.klotz) - Saturday, 21 January 2012, 22:15 GMT
I reported an upstream bug regarding this issue:

https://bugs.kde.org/show_bug.cgi?id=292138
Comment by bastler (bastler) - Sunday, 22 January 2012, 11:23 GMT
same here - strange enough as it worked until last friday
Comment by bastler (bastler) - Sunday, 22 January 2012, 22:11 GMT
Administrators, please fix the subject of this bug report: nobody can find this report searching for 'wrong deivce search path'
Comment by bastler (bastler) - Friday, 27 January 2012, 16:59 GMT
can somebody confirm that kaffeine works again using kernel >= 3.2.1
Comment by Florian Zeitz (Florob) - Friday, 27 January 2012, 17:07 GMT
I'm personally "blaming" it on a udev update, but yes I can confirm that.
Comment by Heiko Baums (cyberpatrol) - Sunday, 29 January 2012, 13:53 GMT
I can confirm that it works again with kernel 3.2.2 and udev 179.

Loading...