> I've been using xdaliclock for some time, but have a slight problem where if
> I restart fvwm, causing xdaliclock to be killed and restarted, sometimes
> it won't restart, and I'll have to manually start one. It spits out this
> error:
>
> X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
> Major opcode of failed request: 63 (X_CopyPlane)
> Resource id in failed request: 0x2000007
> Serial number of failed request: 8066
> Current serial number in output stream: 8084
>
> I know that I should just figure out the FvwmButtons command that causes a
> swallowed program to be regurgitated and reswallowed during a restart, but
> it doens't happen often enough to cause me to be motivated. I'm just
> curious if anyone else has seen this.
I haven't seen the error, but then I don't pay much attention to that
logfile. However, about one time out of 20, xdaliclock won't start when I
start fvwm. It's probably the same problem you're having..
--
#!/usr/bin/perl -i\$q='$q',\$p='$p';eval\$q.\$\^I#\n"# jeh22_at_cornell.edu
$q='print"$p$^I\n',$p='#!/usr/bin/perl -i';eval$q.$^I# Joey Hess
"He. He. He." - - Herman Toothrot
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Aug 16 1996 - 13:45:52 BST