Im using vdr(1.3.34) + xine-plugin (0.7.6) under debian 3.1 (sarge) After a while all my Console's (bash) begin to freeze. I have opened a Console with 6 Tabs. If I start ./runvdr -P'xine -r als other tabs will freeze after a while. Same if I dont run xine(ui).
Maybe this is a debian problem. Has anybody the same feature?
DS
--- Ursprüngliche Nachricht --- Von: Patrick Fischer patrick_fischer@gmx.de An: vdr@linuxtv.org Betreff: [vdr] vdr+xine -> freeze Console Datum: Wed, 12 Oct 2005 16:25:28 +0200
Im using vdr(1.3.34) + xine-plugin (0.7.6) under debian 3.1 (sarge) After a while all my Console's (bash) begin to freeze. I have opened a Console with 6 Tabs. If I start ./runvdr -P'xine -r als other tabs will freeze after a while. Same if I dont run xine(ui).
Maybe this is a debian problem. Has anybody the same feature?
yes, i have. i don't find a workaround. the only way for me is to use Rxvt or Xterm
bye Horst
On Wednesday 12 October 2005 16:31, Peter Weber wrote:
Im using vdr(1.3.34) + xine-plugin (0.7.6) under debian 3.1 (sarge) After a while all my Console's (bash) begin to freeze. I have opened a Console with 6 Tabs. If I start ./runvdr -P'xine -r als other tabs will freeze after a while. Same if I dont run xine(ui).
Maybe this is a debian problem. Has anybody the same feature?
yes, i have. i don't find a workaround. the only way for me is to use Rxvt or Xterm
I have it, too. This seems to be a known bug according to xine bugtracker.
The wordaround is quite simple: If your konsole locks up, deactivate Scroll Lock and it will work again. Of course working that way is quite annoying.
Greetings, Sascha
...
The wordaround is quite simple: If your konsole locks up, deactivate Scroll Lock and it will work again. Of course working that way is quite annoying.
Greetings, Sascha
Hi Lord,
that's right, i can't believe it. thx
Horst
Hi,
Peter Weber wrote:
The wordaround is quite simple: If your konsole locks up, deactivate Scroll Lock and it will work again. Of course working that way is quite annoying.
that's right, i can't believe it.
Does this only happen while xine is replaying? Could it be related to xine's way of deactivating the screensaver while replaying?
Bye.
The wordaround is quite simple: If your konsole locks up, deactivate Scroll Lock and it will work again. Of course working that way is quite annoying.
that's right, i can't believe it.
Does this only happen while xine is replaying?
yes
Could it be related to xine's way of deactivating the screensaver while replaying?
can i deactivate this? find nothing in preferences.
bye Horst
I demand that Peter Weber may or may not have written...
The wordaround is quite simple: If your konsole locks up, deactivate Scroll Lock and it will work again. Of course working that way is quite annoying.
that's right, i can't believe it.
Does this only happen while xine is replaying?
yes
Could it be related to xine's way of deactivating the screensaver while replaying?
can i deactivate this? find nothing in preferences.
Disable the XTest check in configure.ac, re-run autoconf then rebuild.
The XTest code will be disabled by default in the next gxine release (the relevant changes are already in CVS).
On Wednesday 12 October 2005 23:06, Reinhard Nissl wrote:
Does this only happen while xine is replaying?
Always and only when xine is actually replaying. Im my case xine was replaying fullscreen to display :0.1 (TV-Out) and konsole locks up (e.g. Scroll Lock gets activated) on display :0.0 :-)
However, if I switch applications (i.e. xterm running in parallel), scroll lock isn't activated there. Only in konsole. Actually even only in one konsole tab. The other tabs are still receiving input then.
Greetings, Sascha
Hi,
Sascha Volkenandt wrote:
Does this only happen while xine is replaying?
Always and only when xine is actually replaying. Im my case xine was replaying fullscreen to display :0.1 (TV-Out) and konsole locks up (e.g. Scroll Lock gets activated) on display :0.0 :-)
I must admit, I've never run such a setup.
However, if I switch applications (i.e. xterm running in parallel), scroll lock isn't activated there. Only in konsole. Actually even only in one konsole tab. The other tabs are still receiving input then.
What are you trying to do in this tab from which xine was started?
Bye.
-
Darren Salt -
Patrick Fischer -
Peter Weber -
Reinhard Nissl -
Sascha Volkenandt