From owner-freebsd-multimedia Fri Jun 12 16:22:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12223 for freebsd-multimedia-outgoing; Fri, 12 Jun 1998 16:22:46 -0700 (PDT) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12212 for ; Fri, 12 Jun 1998 16:22:42 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Fri, 12 Jun 1998 19:22:12 -0400 (EDT) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA24998; Fri, 12 Jun 98 19:22:12 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA29966; Fri, 12 Jun 1998 19:22:03 -0400 Message-Id: <19980612192203.A29936@ct.picker.com> Date: Fri, 12 Jun 1998 19:22:03 -0400 From: Randall Hopper To: freebsd-multimedia@FreeBSD.ORG Subject: Re: fxtv 0.47 core dumps on exit Mail-Followup-To: freebsd-multimedia@freebsd.org References: <19980611171351.A7747@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980611171351.A7747@top.worldcontrol.com>; from brian@worldcontrol.com on Thu, Jun 11, 1998 at 05:13:51PM -0700 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmmm. PPMs work fine here, but I'm not running a current -current though so could be due to recent changes in the tree. The X error gives me some concern. I notice your $DISPLAY is set to "192.168.0.2:0.0". Is this localhost? If so, you can likely get direct video (and much better performance) by setting it to ":0" or "unix:0" instead. And the X error may just indicate bugs in your X server. However, if 192.168.0.2 is remote, this may be some indication of VidMode extension breakage specifically related to use over the network. Please let me know on this (remote or local). (However, vidmode stuff works fine for me on localhost using sockets instead of IPC -- i.e. with DISPLAY=127.0.0.1:0). And the "Failed to find current video mode in server mode list" shouldn't ever happen. This says that the current video mode's specs returned by XF86VidModeGetModeLine aren't in the master list returned by XF86VidModeGetAllModeLines. One of these APIs might be failing (not checking return status), but no failure modes for these APIs are documented in the man page. How about posting your fxtv -debug startup. Randall brian@worldcontrol.com: |bls2# fxtv (0.47 on a -current system) |Direct Video not supported by visual...using XImages |X Error of failed request: XF86VidModeExtensionDisabled | Major opcode of failed request: 142 (XFree86-VidModeExtension) | Minor opcode of failed request: 12 (XF86VidModeSetViewPort) | Serial number of failed request: 1396 | Current serial number in output stream: 1397 |XIO: fatal IO error 0 (Undefined error: 0) on X server "192.168.0.2:0.0" | after 1398 requests (1397 known processed) with 12 events remaining. |Failed to find current video mode in server mode list |Failed to find current video mode in server mode list |zsh: segmentation fault (core dumped) fxtv | |If I just start fxtv and then exit, all goes well. Generally I start |it, capture a few PPM images, and then exit with the above result. | |-- |Brian Litzinger | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-multimedia" in the body of the message Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message