Bug 373725 - Second frontend not detected
Summary: Second frontend not detected
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-16 13:56 UTC by johan.claudebreuninger
Modified: 2017-02-16 11:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description johan.claudebreuninger 2016-12-16 13:56:07 UTC 
Hi,


I'm using Kaffeine 2.0.5 for receiving live TV through a USB DVB-T/T2/C tuner with two frontends:

[75937.620382] usb 2-1.2.4: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[75937.620476] usb 2-1.2.4: DVB: registering adapter 0 frontend 1 (Panasonic MN88473)...


Kaffeine only sees the frontend 0 with the DVB-T/T2 part but not the second one for DVB-C.
Comment 1 Mauro Carvalho Chehab 2016-12-27 15:51:02 UTC 
(In reply to johan.claudebreuninger from comment #0)
> Hi,
> 
> 
> I'm using Kaffeine 2.0.5 for receiving live TV through a USB DVB-T/T2/C
> tuner with two frontends:
> 
> [75937.620382] usb 2-1.2.4: DVB: registering adapter 0 frontend 0 (Realtek
> RTL2832 (DVB-T))...
> [75937.620476] usb 2-1.2.4: DVB: registering adapter 0 frontend 1 (Panasonic
> MN88473)...
> 
> 
> Kaffeine only sees the frontend 0 with the DVB-T/T2 part but not the second
> one for DVB-C.

There was a bug on Kaffeine for devices that have just one demux, but multiple frontends. I just added a patch fixing it:

    https://cgit.kde.org/kaffeine.git/commit/?id=6b6a936a0dbf5951b6377554d0400220a5602074


Could you please test?
Comment 2 Mauro Carvalho Chehab 2017-02-16 11:34:45 UTC 
The bug was likely fixed by this commit:
    https://cgit.kde.org/kaffeine.git/commit/?id=6b6a936a0dbf5951b6377554d0400220a5602074

as, after it, it works for me. As the reporter didn't confirm it was solved on a reasonable time, I'm closing the bug. If it still happens, feel free to reopen.