Bug 399383

Summary: Does not display TV picture after OS resume from suspend mode
Product: [Applications] kaffeine Reporter: Roger England <r.england>
Component: generalAssignee: Mauro Carvalho Chehab <mchehab>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: 2.0.14   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Kaffeine Diagnostics

Description Roger England 2018-10-04 15:49:06 UTC
Created attachment 115414 [details]
Kaffeine Diagnostics

SUMMARY I am running Kaffeine on Xubuntu 18.04 to view TV channels using Haupauge WinTV. Kaffeine fails to display TV pictures after suspend of OS.


STEPS TO REPRODUCE
1. Boot PC and load Kaffeine. TV works OK.
2. Stop TV and minimize Kaffeine. Susspend OS
3. Restart OS and start Kaffeine. 

OBSERVED RESULT
At this point Kaffeine will not display any TV pictures but is does display the programme name.

The error log is attached.






EXPECTED RESULT


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Mauro Carvalho Chehab 2018-11-05 10:44:23 UTC
(In reply to Roger England from comment #0)
> Created attachment 115414 [details]
> Kaffeine Diagnostics
> 
> SUMMARY I am running Kaffeine on Xubuntu 18.04 to view TV channels using
> Haupauge WinTV. Kaffeine fails to display TV pictures after suspend of OS.
> 
> 
> STEPS TO REPRODUCE
> 1. Boot PC and load Kaffeine. TV works OK.
> 2. Stop TV and minimize Kaffeine. Susspend OS
> 3. Restart OS and start Kaffeine. 
> 
> OBSERVED RESULT
> At this point Kaffeine will not display any TV pictures but is does display
> the programme name.
> 
> The error log is attached.

Returning from suspend can be tricky. Could you please send a more detailed log with debug enabled? Also, please attach the dmesg log too, as this could be a driver issue.
Comment 2 Mauro Carvalho Chehab 2019-05-03 19:49:06 UTC
That's likely a driver's bug. So, I'm closing the issue.

If you want, feel free to add here the dmesg, and I'll try to address it very likely via a Kernel patch.