Since emerging nvidia-kernel-1.0.4496-r3 and corresponding nvidia-glx, xawtv exits with a segmentation fault immediately after starting. Using bttv with a Hauppage tv card, but other people have the same problem with different hardware. Not all people have it though. Reproducible: Always Steps to Reproduce: 1.emerge -u nvidia 2.start xawtv 3. Actual Results: The window of xawtv is visible for a split second after which it closes and gives a segmentation fault. Expected Results: Shown the window and show tv. Hauppage WinTV with bttv driver, kernel 2.4
emerging the previous drivers (1.0.4363) fixes the problem.
I tried to debug xawtv with gdb. I used the source-code from "/usr/portage/distfiles/" and extract it in my home-directory. I used "./configure --prefix=/usr" for configuring, and it segfaults as expected. I began with the last message "xawtv -v 3" gave me. This is "x11/xawtv.c:1776" (file: x11/xawtv.c line 1776). After this message, it segfaults after "attr_init(); x11/xawtv.c:1777", so I step into this function. After "attr_notify(); common/commands.c:453" it segfaults, so I step into this function. From this points, it crached the second time. After a breakpoint, I type "continue" and after the second time by that breakpoints, it segfaults (always). After this, it segfaults after "x11/xawtv.c:566". The last opportunity to dig into the program is in line "libng/grab-ng.c:231". At this point, it segfaults definitive. The last message gdb always return: "Program received signal SIGSEGV, Segmentation fault. 0x0806e0e5 in ng_attr_getstr (attr=0x0, value=-1) at libng/grab-ng.c:231 231 for (i = 0; attr->choices[i].str != NULL; i++)" I hope somebody can do something with this.
It seems as though there is something wrong with nvidia drivers version 4496. My bug (29336) and this one indicate to me that the problem lies with the nvidia drivers and not the gentoo team. Perhaps someone who's actually on the gentoo team could bring this information to nvidia's attention?
I've been noticing complete lock-ups using tvtime and nvidia-*-4496. The keyboard and display become unresponsive, and only hard rebooting fixes the problem (no NumLock light, no ability to switch to tty1). Poking around on nVidia's forums, there is a note that "xawtv -noxv" will get past the segmentation fault. It does. However, xawtv then causes the same kinds of lock-ups. Could nVidia's build 4496 please get marked as unstable? It's causing a lot of problems. Thanks.
Got the same results as Douglas told, downgrading to 4363 helped. the newer driver installs correctly, so I would suggest to mark it unstable, too.
Yup, confirming this on my box as well. I have immediate xawtv segfaults with 1.0.4496 and the problem goes away upon downgrading to 1.0.4496.
Same problem with kernel-2.6-test7. And the older one (1.0.4363?) doesn't compile for the kernel 2.6 :-(
I just added xawtv-3.90 into portage. I used to get the segfaults with 3.88 (2.4 kernel), but 3.90 doesn't segfault. I don't see a picture yet, but that's a different story.
I was having the same symptoms with xawtv. However if I launch xawtv like so: xawtv -c /dev/v4l/video0 Everything works fine.
Got it running with xawtv-3.91. Used kernel gentoo-2.6.3-r1 and xfree 4.3.0-r5. Remark: I had to add 'Load "v4l"' in section Module of XF86Config to get overlay mode running.
Is this still a problem with the latest versions 533*?
I have hardware since this bug was first opened. My new laptop has a different nVidia card -- without any video capture capabilities anymore. So, I can't help anymore....
As far as I now the only drivers with this problem are the 4496-drivers. That are the only drivers I have masked. I have two computers with a nvidia-card and a tv-capture card. They both work fine (with the 5336-driver). I use the arguments "xawtv -noxv -dga" to fix an other problem with this combination, but that is not relavant to this bug.
Im marking this as LATER, as it seems we need to stablise the newer nvidia drivers seen as though they successfully work with xawtv in this instance. There are other problems with these drivers though hence why later. As a few reminders and also for information purposes 1) Are any of you _NOT_ using devfsd? (If not are you using udev or just nothing) 2) Do you have : Load "v4l" listed in your XF86Config (or xorg.conf depending) 3) Can you please try compiling xawtv with --enable-gl (needs ebuild modification)
reopening
Much newer drivers are now stable. Closing with the proper resolution.
