[Kwintv] Re: re: Some proposals (2)

Fri Feb 18 15:57:10 CET 2005

Hi Dirk,

Thanks again.

I'll  will download the source code and make the necessary changes. I hope that I can compile it. The last time I compilled a program I got some strange errors that I did't understand. If it doesn't work out, I'll just keep using the suse rpm.

Jeroen

Send kwintv mailing list submissions to
kwintv at kde.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/kwintv
or, via email, send a message with subject or body 'help' to
kwintv-request at kde.org

You can reach the person managing the list at
kwintv-owner at kde.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kwintv digest..."
Today's Topics:

1. Crash when clicking "Picture Settings" (Adam Richard)
2. Re: kdetv on SUSE9.2 no color on svideo (David E. West)
3. Re: Re: re: Some proposals (2) (Dirk Ziegelmeier)
4. Re: Crash when clicking "Picture Settings" (Dirk Ziegelmeier)
5. Re: Crash when clicking "Picture Settings" (Adam Richard)

> ATTACHMENT part 3.1 message/rfc822 
From: Adam Richard 
To: kwintv at kde.org
Date: Mon, 14 Feb 2005 10:23:26 -0400
Subject: [Kwintv] Crash when clicking "Picture Settings"

kdetv crashed when I clicked "Picture Settings". The backtrace should be attached.

I'm using a Belkin USB Videobus II which I haven't got working yet, so that might be
the
underlying cause (though of course it's still a bug since kdetv shouldn't assume my
hardware is configured correctly).

The device is a video capture device, it doesn't have a TV tuner for watching TV or
changing channels - it just lets you plug in anything with RCA plugs or an S-Video plug
into it which goes into a USB port. I don't know, maybe kdetv assumes the device can
change channels or that it has certain other settings.Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 12127)]
[KCrash handler]
#5 0xb7f0be90 in PictureWidgetImpl::setup() () from /usr/lib/libkdetv.so.1
#6 0xb7f2068c in ViewManager::launchDialog(QWidget*, QWidget*, QString const&)
() from /usr/lib/libkdetv.so.1
#7 0xb7f20411 in ViewManager::launchPictureSettings(QWidget*) ()
from /usr/lib/libkdetv.so.1
#8 0xb7f07ed9 in Kdetv::pictureSettings() () from /usr/lib/libkdetv.so.1
#9 0xb7f089a2 in Kdetv::qt_invoke(int, QUObject*) ()
from /usr/lib/libkdetv.so.1
#10 0xb6a4a9a4 in QObject::activate_signal(QConnectionList*, QUObject*) (
this=0x822bd68, clist=0x822c070, o=0xbfffe880) at kernel/qobject.cpp:2357
#11 0xb6a4a7fc in QObject::activate_signal(int) (this=0x822bd68, signal=2)
at kernel/qobject.cpp:2326
#12 0xb74b17cb in KAction::activated() () from /usr/kde/3.3/lib/libkdeui.so.4
#13 0xb74b119f in KAction::slotActivated() ()
from /usr/kde/3.3/lib/libkdeui.so.4
#14 0xb74b19bf in KAction::qt_invoke(int, QUObject*) ()
from /usr/kde/3.3/lib/libkdeui.so.4
#15 0xb6a4aade in QObject::activate_signal(QConnectionList*, QUObject*) (
this=0x82fbf20, clist=0x82fc4a8, o=0xbfffe9b0) at kernel/qobject.cpp:2381
#16 0xb6a4a7fc in QObject::activate_signal(int) (this=0x82fbf20, signal=4)
at kernel/qobject.cpp:2326
#17 0xb6e346ab in QButton::clicked() (this=0x82fbf20)
at .moc/debug-shared-mt/moc_qbutton.cpp:152
#18 0xb6af86d7 in QButton::mouseReleaseEvent(QMouseEvent*) (this=0x82fbf20, 
e=0xbfffee40) at widgets/qbutton.cpp:833
#19 0xb6a8da25 in QWidget::event(QEvent*) (this=0x82fbf20, e=0xbfffee40)
at kernel/qwidget.cpp:4673
#20 0xb69da4c5 in QApplication::internalNotify(QObject*, QEvent*) (
this=0xbffff510, receiver=0x82fbf20, e=0xbfffee40)
at kernel/qapplication.cpp:2635
#21 0xb69d99f8 in QApplication::notify(QObject*, QEvent*) (this=0xbffff510, 
receiver=0x82fbf20, e=0xbfffee40) at kernel/qapplication.cpp:2421
#22 0xb71e1172 in KApplication::notify(QObject*, QEvent*) ()
from /usr/kde/3.3/lib/libkdecore.so.4
#23 0xb6962972 in QApplication::sendSpontaneousEvent(QObject*, QEvent*) (
receiver=0x82fbf20, event=0xbfffee40) at qapplication.h:494
#24 0xb695a752 in QETWidget::translateMouseEvent(_XEvent const*) (
this=0x82fbf20, event=0xbffff1f0) at kernel/qapplication_x11.cpp:4288
#25 0xb695801a in QApplication::x11ProcessEvent(_XEvent*) (this=0xbffff510, 
event=0xbffff1f0) at kernel/qapplication_x11.cpp:3439
#26 0xb6975889 in QEventLoop::processEvents(unsigned) (this=0x814c710, flags=4)
at kernel/qeventloop_x11.cpp:192
#27 0xb69f197d in QEventLoop::enterLoop() (this=0x814c710)
at kernel/qeventloop.cpp:198
#28 0xb69f1896 in QEventLoop::exec() (this=0x814c710)
at kernel/qeventloop.cpp:145
#29 0xb69da667 in QApplication::exec() (this=0xbffff510)
at kernel/qapplication.cpp:2758
#30 0x08056adc in main ()

> ATTACHMENT part 3.2 message/rfc822 
From: "David E. West" 
To: KWinTV General Mailing List 
Date: Mon, 14 Feb 2005 10:11:51 -0500
Subject: Re: [Kwintv] kdetv on SUSE9.2 no color on svideo 

Steve,

I had the same problem a while back when using the "s-video out" of my graphics
card. At first all I could see was a black and white image. The problem for
me turned out to be that the s-video connector I was using didn't fit well into
the back of my computer. I ended up having to shave away part of the plastic
in order to allow it to make contact on all the pins. S-video is split into
two signals, the liminance (black and white) and sync signals travel on one 
pin, and the color (chrominance) travels on the other pin. Both pins have 
their own ground for a total of 4 pins. In my case the chrominance pin wasn't
making contact. This may be totally unrealated to your situation, but the end
result sounds similar.

Just an idea.

David E. West

> I have worked out the problems of "no device" and "no channels" by reading 
> this list, Thanks,made those easy fixes.
> My problem is a little different,TV works fine on my Diamond DTV2000 card 
> but I'm wanting to use the s-video input as my camera source.
> I can switch to s-video and get pictures but they are black and white 
> only,no color...
> Is this the normal? I'm using a full size VHS camcorder as the camera 
> feeding the s-video port on the DTV2000 card.
> Any Ideas?
> 
> Steve

> ATTACHMENT part 3.3 message/rfc822 
From: Dirk Ziegelmeier 
To: KWinTV General Mailing List 
Date: Mon, 14 Feb 2005 21:44:51 +0100
Subject: Re: [Kwintv] Re: re: Some proposals (2)

On Sunday 13 February 2005 14:59, Jeroen Verhoeckx wrote:
> "I mean the complete list of all frequencies allowed
> for TV in your area, no matter whether there is really
> a station or not. Like the *.list files in
> libkdetv/data."
>
> Where can I find libkdetv/data?
> I tried to find it with Konqueror but I couldn't.
Download kdetv sources and unpack. It's a subdir.

> "But anyway, thank you for your ideas (even if I
> don't implement them all ;-) ! "
>
> If it is easy to code, could you make an option so
> that we can see how it functions? If not, it's
> alright!
This is always a difficult point. I could, but this is one of the things I'd 
call "over-configurability". A program does not get better when you a tons of 
config options for every little thing. It just gets unusable.

> "I could, but not fixing it has the advantage that
> the size scales with the window size. It is uncommon
> to fix resizeable widgets to a fixed size."
>
> But can you give it a minimum or maximum size? I don't
> know how these widgets function. This is not just a
> problem for KDETV but a general problem with KDE.
> Dialogs sometimes look really ugly because of this
> behaviour.
_Useful_ min/max always depend on the screen resolution, it's not that easy. 
The slider widget already has built-in min/max values, I won't override 
these.

> " Difficult to say, I don't observe this. Can be a
> driver bug (does xawtv work?) or a bug in kdetv that
> just does not occur on my box."
> I haven't used xawtv for a very long time but I belief
> that it would work, why not?
Because the driver could have a bug.

> "Can you comment out or remove the line
> "srcm->setMuted(muted)" in
> libkdetv/volumecontroller.cpp, function doMute(). "
>
> Yes if I can find the file volumecontroller.cpp. Where
> can I?
libkdetv/volumecontroller.cpp

> To comment out a line means removing the # for the
> line, isn't it?
No, putting "//" in front of it (this is C++ and not a shell script).
Don't worry, I see you are not a programmer. If you can't do it, I send you a 
modified volumecontroller.cpp.

Dirk

> ATTACHMENT part 3.4 message/rfc822 
From: Dirk Ziegelmeier 
To: KWinTV General Mailing List 
Date: Mon, 14 Feb 2005 21:54:53 +0100
Subject: Re: [Kwintv] Crash when clicking "Picture Settings"

On Monday 14 February 2005 15:23, Adam Richard wrote:
> kdetv crashed when I clicked "Picture Settings". The backtrace should be
> attached.
>
> I'm using a Belkin USB Videobus II which I haven't got working yet, so that
> might be the
> underlying cause (though of course it's still a bug since kdetv shouldn't
> assume my hardware is configured correctly).
>
> The device is a video capture device, it doesn't have a TV tuner for
> watching TV or changing channels - it just lets you plug in anything with
> RCA plugs or an S-Video plug into it which goes into a USB port. I don't
> know, maybe kdetv assumes the device can change channels or that it has
> certain other settings.
What kdetv version, what video plugin are you using?

Are you able to do a debug build of kdetv and send a backtrace?

Dirk

> ATTACHMENT part 3.5 message/rfc822 
From: Adam Richard 
To: KWinTV General Mailing List 
Date: Mon, 14 Feb 2005 17:03:56 -0400
Subject: Re: [Kwintv] Crash when clicking "Picture Settings"

Quoting Dirk Ziegelmeier :

> On Monday 14 February 2005 15:23, Adam Richard wrote:
> > kdetv crashed when I clicked "Picture Settings". The backtrace should be
> > attached.
> >
> > I'm using a Belkin USB Videobus II which I haven't got working yet, so that
> > might be the
> > underlying cause (though of course it's still a bug since kdetv shouldn't
> > assume my hardware is configured correctly).
> >
> > The device is a video capture device, it doesn't have a TV tuner for
> > watching TV or changing channels - it just lets you plug in anything with
> > RCA plugs or an S-Video plug into it which goes into a USB port. I don't
> > know, maybe kdetv assumes the device can change channels or that it has
> > certain other settings.
> What kdetv version, what video plugin are you using?
> 
> Are you able to do a debug build of kdetv and send a backtrace?
> 
> Dirk

I could try, though it would require being able to reproduce the crash which I can't
guarantee. Strange, I thought the backtrace I attached looked complete, but I guess
not... It might be a few days before I do it, though.

_______________________________________________
kwintv mailing list
kwintv at kde.org
https://mail.kde.org/mailman/listinfo/kwintv

---------------------------------
Do you Yahoo!?
 Yahoo! Search presents - Jib Jab's 'Second Term'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kwintv/attachments/20050218/a0ec7c74/attachment.html