Xconsole craps out after Potato-upgrade

Hi Debs Previously (in slink, 4 days ago), Xconsole was run when launching fvwm. Now, it doesn't start automagically, and gives an error: Couldn't open console when I start it manually. I find it quite annoying; I've gotten used to keeping an eye on the modem when dialing and my ailing /dev/hdc

Re: Xconsole craps out after Potato-upgrade

if you didn't specify the file option, try: xconsole -file /dev/xconsole On Mon, May 29, 2000 at 03:47:53PM +0200, Vitux wrote: Hi Debs Previously (in slink, 4 days ago), Xconsole was run when launching fvwm. Now, it doesn't start automagically, and gives an error: Couldn't open console

Re: Xconsole craps out after Potato-upgrade

On Mon, May 29, 2000 at 03:47:53PM +0200, Vitux wrote: Previously (in slink, 4 days ago), Xconsole was run when launching fvwm. Now, it doesn't start automagically, and gives an error: Couldn't open console when I start it manually. I find it quite annoying; I've gotten used to keeping an eye

Re: Xconsole craps out after Potato-upgrade

Brad wrote: On Mon, May 29, 2000 at 03:47:53PM +0200, Vitux wrote: Previously (in slink, 4 days ago), Xconsole was run when launching fvwm. Now, it doesn't start automagically, and gives an error: Couldn't open console when I start it manually. I find it quite annoying; I've gotten used

Re: Xconsole craps out after Potato-upgrade

On Tue, May 30, 2000 at 12:59:08AM +0200, Vitux wrote: I see. Security isn't such a big issue on this stand-alone home-use box, but anyway: how do I find out which group owns /dev/xconsole? ls -l /dev/xconsole Should be root.adm and be a fifo /dev/xconsole| -- ¶