Playback of channels with totem-plugin doesnt start

Bug #743012 reported by Timo Schneemann
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME DVB Daemon
Expired
Undecided
Unassigned

Bug Description

Installed latest verion of gnome-dvb-daemon through ppa in Ubuntu 10.10. Totem-Plugin shows all scannend channels correctly but starting a channel produces:

** Message: Error: Aus der Ressource konnte nicht gelesen werden.
gstrtspsrc.c(4408): gst_rtspsrc_send (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin1/GstRTSPSrc:source:
Got error response: 503 (Service Unavailable).

I read that this was already problem but should be solved with Gnome-DVB-Daemon 1.2.2, but I use already 1.2.3.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

Thanks for reporting this issue.

Could you please start the daemon from a terminal with "gnome-dvb-daemon --debug" and post the output here.

Revision history for this message
Timo Schneemann (timobauwan) wrote :
Download full text (3.6 KiB)

Of course. Further Information: I use tvheadend at the moment, but i disabled it for testing gnomedvb because otherwise the device is blocked. I hope it hasnt any impact on gnome-dvb-daemon nevertheless.

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 12112 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 16106 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 24103 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 23113 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 24104 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 11105 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 16101 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 16102 for this device

** (gnome-dvb-daemon:3970): WARNING **: EPGScanner.vala:184: Could not find channel 16103 for this device
** (gnome-dvb-daemon:3970): DEBUG: Schedule.vala:105: Removing expired events of channel hr2 (28420)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:563: Watching channel Bayern 1 (28400)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:580: Creating new PlayerThread: true
** (gnome-dvb-daemon:3970): DEBUG: EPGScanner.vala:72: Stopping EPG scan for group 1 (0)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:115: Creating new pipeline
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:454: Element tee3 (0x94bace0) added to pipeline
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:454: Element bin1 (0x948f640) added to pipeline
** (gnome-dvb-daemon:3970): DEBUG: MediaFactory.vala:76: Retrieving sink bin with payloader
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:261: Searching for sink pay0 (0x94ed198) of channel 28400
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:280: Found sink
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:622: Stopping channel Bayern 1 (28400)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:434: Stopping pipeline
** (gnome-dvb-daemon:3970): DEBUG: EPGScanner.vala:134: Starting EPG scan for group 1 (1)
** (gnome-dvb-daemon:3970): DEBUG: Schedule.vala:105: Removing expired events of channel Das Erste HD (11100)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:563: Watching channel Phoenix (28725)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:580: Creating new PlayerThread: true
** (gnome-dvb-daemon:3970): DEBUG: EPGScanner.vala:72: Stopping EPG scan for group 1 (0)
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:115: Creating new pipeline
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:454: Element tee6 (0x94baad0) added to pipeline
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:454: Element bin2 (0x94c4588) added to pipeline
** (gnome-dvb-daemon:3970): DEBUG: MediaFactory.vala:76: Retrieving sink bin with payloader
** (gnome-dvb-daemon:3970): DEBUG: ChannelFactory.vala:261: Searchi...

Read more...

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Sorry, too many informations in the output. The beginning was missing. I am posting again a complete output in an attachment.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

There are a couple of things you can do to further narrow down the cause:

1) Schedule a recording and check if that works as expected
2) Run the daemon with "GST_DEBUG=*:2,dvb*:3 gnome-dvb-daemon --debug --gst-debug-no-color" and attach the output
3) Try to generate a channels.conf with dvb-apps scan and create a device group manually [1]

[1]: http://live.gnome.org/DVBDaemon/UserGuide#Manual_setup

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Ok, thanks again for your help! Now one by one.

1) I scheduled a recording, it startet and created correctly folder, mpg-file and at the end info.rec. But the recording-file is empty.

I had debug-mode on while testing, output in attachment.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

2) Output in attachment. Also tried starting a channel while on. Same result as every time.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

3) I generated channels.conf like discribed in manual with ("scan /usr/share/dvb/dvb-c/de-Unitymedia > channels.conf"). Configured the device and first new thing i noticed: now the epg-data are shown, which was not the case before. But still starting a channel in totem doesnt work. Debug-output in attachment.

I am still willing and keen on trying every test and tip you an give me! ;)

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

Looks like the channels.conf generated by gnome-dvb-setup contains errors. I suspect that recording should work fine with the new channels.conf. Let's investigate that further if that later and only look at the the other issue for now.

To investigate the Totem issue please run "GST_DEBUG=*:2,dvb*:3,rtsp*:3 gnome-dvb-daemon --debug --disable-epg-scanner --gst-debug-no-color"

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Here is the output. First i tried to start 2 TV channels and 1 radio station in totem and at the end also to make a recording. Everything with the same visible outcome.

Just to try something new, i am actually making a new channels.conf with w_scan to look if there is a different outcome.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

There's critical warning that looks suspicious. To find out where it happens you have to the the daemon with:

"G_DEBUG=fatal_criticals gdb gnome-dvb-daemon"

In the debugger type "run" to start the process.

More information on how to obtain the backtrace is available at http://live.gnome.org/DVBDaemon/Debugging

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Thanks again for your effort! I had a first success without knowing why. As i said i made a new channels.conf with w-scan (w_scan -fc -c DE -X > dvb-channels.conf). In first testing I had the same issues like always.

Now i tried your debugging. I hope i made everything right, nevertheless there was the good explanation on your site. The output is in attachment. After starting i tried to start 3 channels, first "3Sat", failure, then "Arte", and if worked! First time ever i got a picture in totem. And after that i tried "3Sat" again and it failed again. Also there where several seconds, when the display got grey and the program was busy and not responding. After 2nd 3Sat-try i got the failure and the gdb-prompt again in the terminal and made the backtrace.

I got a picture, so it must work somehow! ;) I can also add, that a friend of mine has the same tv-card with (at first sight) exactly the same issues under Ubuntu 10.10 with gnome-dvb-daemon.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

Thanks for your efforts to investigate this problem!

I should have mentioned that you have to install debugging symbols in order to retrieve a meaningful backtrace, sorry for that.
Please install the following packages and try again to obtain a backtrace:
libgstreamer-0.10-0-dbg, gstreamer0.10-plugins-base-dbg, gstreamer0.10-plugins-bad-dbg

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Ok, this one looks better (although still i dont understand a word). I tried again 3Sat, Arte, 3Sat, but this time nothing happend and there was neither picture nor crash. So I went on trying several channels and got only the failure. Suddenly (12th or 15th try) 3Sat worked this time and when i tried to change channel now it crashed and I could get the backtrace.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Just to complete the problem (and maybe make it easier for others to find this report) I write the two failure messages i get in totem (sorry, only in german). Normaly i only get there "Es ist ein Fehler aufgetreten. Aus der Ressource konnte nicht gelesen werden". And together with the crash I get "Der Ort wurde nicht gefunden."

This was the first I tried to find via google. ;)

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

That is weird, I was expecting to get a backtrace for the following warning, but that doesn't look any like that.

GLib-GObject-CRITICAL **: g_value_get_int: assertion `G_VALUE_HOLDS_INT (value)' failed

Could check if you see that error if you try to record something and then try to get a backtrace. Don't use Totem for now, because this makes things just more complicate, currently.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

Ok, i did so. There was an failure at the beginning of the recording that i could back trace, but it looks like another one than you wrote.

Like before folder for channel and a recording-file is created, but it remains emty. And no info-file.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

The debug output from the daemon is missing, please run the following command to debug.

"G_DEBUG=fatal_criticals gdb --args gnome-dvb-daemon --debug --disable-epg-scanner"

Thanks a lot!

Changed in gnome-dvb-daemon:
status: New → Incomplete
Revision history for this message
Timo Schneemann (timobauwan) wrote :

Sorry, i have been busy. So here are two new tries. I started with the line you posted, wrote "set logging on" and "run", scheduled a recording, waited to the program to abort and typed "thread apply all bt full" then.

Made this two time with different channels.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

And the second one.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

I am not sure how long i will be able to provide further information to this problem for Ubuntu 10.10 as i am planing to upgrade my desktop to natty in near future. But for sure i will keep on trying gnome-dvb.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

I'm sorry, but gdb didn't log the output as I expected, therefore the output of the daemon is still missing. The following command should work:

$ G_DEBUG=fatal_criticals gdb --args gnome-dvb-daemon --debug --disable-epg-scanner
(gdb) set logging on
(gdb) run > output.txt 2>&1

This redirects the output of the daemon to the file "output.txt" and the output of gdb to "gdb.txt". Hopefully, this will help to narrows it down.

Feel free to try it on Ubuntu 10.10, the version there is the same as for 10.04, I would be surprised if the issue disappears there. Make sure to install debugging symbols as mentioned in comment 12, though.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

So here I am again. Sorry for the delay. I am now under 11.04 (upgraded from 10.10, not a clean install) and the behavior seems the same.
I made two tries. First, i ran it like you said but, when I tried to change the time for the programmed recording with the drop-down menue the whole gui froze. These are the first two files.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

And the gdb.txt.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

In the second try everything went like before and it crashed when the recording started. There is an empty mpg-file in the recordings-folder.

Revision history for this message
Timo Schneemann (timobauwan) wrote :

And the gdb.txt.

Revision history for this message
Sebastian Pölsterl (sebp) wrote :

Let's try something different and check if a basic gstreamer pipeline works.

Open your channels.conf and choose a line, e.g.:
ProSieben:330000000:INVERSION_AUTO:6900000:FEC_NONE:QAM_64:255:256:898

From this line you get a line that looks like this:
gst-launch dvbsrc frequency=330000000 inversion=AUTO symbol-rate=6900 code-rate-hp=NONE modulation="QAM 64" program-numbers=898 .program_898 ! filesink location=recording.mpg

Run this command in a terminal, if everything works correctly you should end up with a file recording.mpg that contains a recording of the channel. You can get more details about the above command if you run "gst-inspect dvbsrc".

Changed in gnome-dvb-daemon:
status: Incomplete → In Progress
Changed in gnome-dvb-daemon:
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for GNOME DVB Daemon because there has been no activity for 60 days.]

Changed in gnome-dvb-daemon:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.