Re: Continuing saga of xorg restarts

2007-07-03 Thread Andrew Sackville-West
On Mon, Jul 02, 2007 at 11:07:04PM -0400, Carl Fink wrote: Per Andrew's advice, I started X in VT1 using startx. During each of the multiple xorg crashes today (!) I got this: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591] 1: [0xb7f36420] 2: /usr/bin/X11/X [0x80ddae5]

Re: Continuing saga of xorg restarts

2007-07-03 Thread Carl Fink
On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote: [much snipping] I've seen some xorg crashes lately too... mostly caused by mplayer, but not reliably. I'll grab my backtrace too. contact the xorg team (Debian X strike force?) and see what they say... I'll wait until

Re: Continuing saga of xorg restarts

2007-07-03 Thread Andrew Sackville-West
On Tue, Jul 03, 2007 at 12:39:05PM -0400, Carl Fink wrote: On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote: [much snipping] I've seen some xorg crashes lately too... mostly caused by mplayer, but not reliably. I'll grab my backtrace too. contact the xorg team

Re: Continuing saga of xorg restarts

2007-07-03 Thread Carl Fink
On Tue, Jul 03, 2007 at 03:26:29PM -0700, Andrew Sackville-West wrote: but that is induced by a very specific situation: dragging an active mplayer window from my left-hand screen to my right hand-screen (which gives me a blank mplayer frame) and then dragging it back. crashes every time. I

Re: Continuing saga of xorg restarts

2007-07-02 Thread Andrew Sackville-West
On Sun, Jul 01, 2007 at 08:33:43PM -0400, Carl Fink wrote: I tried switching to VLC. I was resetting the hotkeys, clicked Save, and xorg restarted. how are you start X? have you looked in .Xsession-errors? anything showing in the VT from which X was started (usually VT-1 if using *dm).

Re: Continuing saga of xorg restarts

2007-07-02 Thread Carl Fink
xOn Mon, Jul 02, 2007 at 11:00:19AM -0700, Andrew Sackville-West wrote: On Sun, Jul 01, 2007 at 08:33:43PM -0400, Carl Fink wrote: I tried switching to VLC. I was resetting the hotkeys, clicked Save, and xorg restarted. how are you start X? xdm have you looked in .Xsession-errors?

Re: Continuing saga of xorg restarts

2007-07-02 Thread Carl Fink
Per Andrew's advice, I started X in VT1 using startx. During each of the multiple xorg crashes today (!) I got this: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591] 1: [0xb7f36420] 2: /usr/bin/X11/X [0x80ddae5] 3: /usr/bin/X11/X(miHandleValidateExposures+0x78) [0x813b828] 4:

Re: Continuing saga of xorg restarts

2007-07-02 Thread Carl Fink
Switching from icewm to fluxbox didn't make any difference. Now I can kill X just by having VLC *open* and task-switching from iceweasel to the open vlc window using alt-tab. This is ludicrous. -- Carl Fink [EMAIL PROTECTED] Read my blog at

Continuing saga of xorg restarts

2007-07-01 Thread Carl Fink
I tried switching to VLC. I was resetting the hotkeys, clicked Save, and xorg restarted. I'm utterly unfamiliar with the internals of X. What would VLC have been doing when I clicked Save that would cause a xorg restart? -- Carl Fink [EMAIL PROTECTED] Read

RE: Java not working, the continuing saga

2004-05-19 Thread David Baron
With netbeans not working, wanted to try Eclipse. Installed all that stuff which also installed a Blackdown JRE and Kaffe. The stuff would not configure so I removed it. Also needed to get rid of a conf file for Kaffe and change a symlink to that in /usr/bin. Did all that, cleaning up with more

Hotplug: The Continuing Saga

2004-04-09 Thread David Baron
I think this module is getting crazier with every update. Last two versions on bootup, unknown interface sit0:-hotplug Last version: More repeated module loads AND repeated listings of blacklisted modules (some of which were blacklisted to clean up the repeated listings) :-) Good old (new for

Re: Hotplug: The Continuing Saga

2004-04-09 Thread Jaap Haitsma
David Baron wrote: I think this module is getting crazier with every update. Last two versions on bootup, unknown interface sit0:-hotplug Last version: More repeated module loads AND repeated listings of blacklisted modules (some of which were blacklisted to clean up the repeated listings) :-)

Re: The Continuing Saga of the Kernel that Now Boots, but doesn't Work

2002-03-02 Thread scott worley
On Fri, 2002-03-01 at 18:39, Timothy R. Butler wrote: Hi everyone, Anyone who has been following the threads Linux Progress Patch (Splash Screen) and The Kernel that Wouldn't Boot, have probably gotten really tired of hearing about my little kernel. Well, hopefully I'll finally have it

The Continuing Saga of the Kernel that Now Boots, but doesn't Work

2002-03-01 Thread Timothy R. Butler
Hi everyone, Anyone who has been following the threads Linux Progress Patch (Splash Screen) and The Kernel that Wouldn't Boot, have probably gotten really tired of hearing about my little kernel. Well, hopefully I'll finally have it fixed soon, so not to worry. :-) Anyway, my kernel now

Continuing saga...

1999-04-16 Thread Small, Bradley
Hi y'all and thanks for all the help so far.. Now I have X windows up and well it is cool so far. Just so everyone knows, when you D/L and install 3.3.3.1 of XFree86 you must also D/L the stuff in their Servers directory. Soon as I got the new SVGA server things got much better. Problem #1, I

RE: Continuing saga...

1999-04-16 Thread Ted Harding
On 16-Apr-99 Small, Bradley wrote: Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me I do when I run His OS. Try as I might I can't seem to convince Linux that it is there. I assume that I should be using wvdial and when it ran the configuration utility it said that

Re: Continuing saga...

1999-04-16 Thread Andrei Ivanov
Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me I do when I run His OS. Try as I might I can't seem to convince Linux that it is there. I assume that I should be using wvdial and when it ran the configuration utility it said that it didn't detect any modem. So I

RE: Continuing saga...

1999-04-16 Thread Small, Bradley
You may well have the modem on /dev/ttyS0 = COM1, but you probably also have your mouse there as well. In that case you are likely to hit interrupt conflicts, and Linux will only see one of the devices. I don't think so, since my mouse is a ps/2 mouse rather than a serial mouse. It could possibly

RE: Continuing saga...

1999-04-16 Thread Ted Harding
On 16-Apr-99 Small, Bradley wrote: You may well have the modem on /dev/ttyS0 = COM1, but you probably also have your mouse there as well. In that case you are likely to hit interrupt conflicts, and Linux will only see one of the devices. I don't think so, since my mouse is a ps/2 mouse rather

Re: Continuing saga...

1999-04-16 Thread Bob Nielsen
On Fri, 16 Apr 1999, Small, Bradley wrote: Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me I do when I run His OS. Try as I might I can't seem to convince Linux that it is there. I assume that I should be using wvdial and when it ran the configuration utility it

RE: Continuing saga...

1999-04-16 Thread Fabio Olive leite
Hi there, ] (the ttyS* and cua* devices are hardware-equivalent, but if I'm ] not mistaken using the /dev/cua* device is better for dialin, which ] you might want for a modem). Whoah! cua devices have been dropped from Debian (and Linux itself, so to speak) long ago and their use nowadays is

RE: Continuing saga...

1999-04-16 Thread Alec Smith
I believe cua* was dropped somewhere along the 2.1.x series... Its gone with 2.2.x On Fri, 16 Apr 1999, Fabio Olive leite wrote: Hi there, ] (the ttyS* and cua* devices are hardware-equivalent, but if I'm ] not mistaken using the /dev/cua* device is better for dialin, which ] you might

Continuing Saga: olwm and xdm

1997-08-16 Thread Reto Andreas Bachmann
Hi Obi, Hi Everyone - Obi wrote: I'm using olvwm xdm with no problem ... I never set up any enviroment variable to make it work ... I guess you are doing something wrong with your .xsession file or .Xresources or something during the session startup. xdm is looking at .xsession while