Re: [pygtk] Init trouble

2000-06-12 Thread Arkaitz
On Mon, Jun 12, 2000 at 08:25:26AM +0800, James Henstridge wrote: > On Sun, 11 Jun 2000, Deirdre Saoirse wrote: > > > On Sun, 11 Jun 2000, Niklas Saers Mailinglistaccount wrote: > > > > > > Actually, I was seriously considering making a null library (that > > > > has all the right calls but no c

Re: [pygtk] Init trouble

2000-06-12 Thread Niklas Saers Mailinglistaccount
> won't use it. If it was installed and you don't want gnome to use it, > start the control center and go to the sound properties capplet and > uncheck the "enable sound server startup" check box. That should fix the > problem. Er, it IS unchecked and has been so the entire time. Which is why I

Re: [pygtk] Init trouble

2000-06-11 Thread Deirdre Saoirse
On Mon, 12 Jun 2000, James Henstridge wrote: > > This presumes I'm using a gnome-based system, which I'm not. I've heard > > three people complaining that Glade can't open /dev/dsp. This is insane. > > Well, it would be gnome that is using esound, so I thought that was a > fairly valid asumption

Re: [pygtk] Init trouble

2000-06-11 Thread James Henstridge
On Sun, 11 Jun 2000, Deirdre Saoirse wrote: > On Mon, 12 Jun 2000, James Henstridge wrote: > > > If you don't have esound installed on your system when compiling > > gnome, it won't use it. If it was installed and you don't want gnome > > to use it, start the control center and go to the sound

Re: [pygtk] Init trouble

2000-06-11 Thread Deirdre Saoirse
On Mon, 12 Jun 2000, James Henstridge wrote: > If you don't have esound installed on your system when compiling > gnome, it won't use it. If it was installed and you don't want gnome > to use it, start the control center and go to the sound properties > capplet and uncheck the "enable sound serv

Re: [pygtk] Init trouble

2000-06-11 Thread James Henstridge
On Sun, 11 Jun 2000, Deirdre Saoirse wrote: > On Sun, 11 Jun 2000, Niklas Saers Mailinglistaccount wrote: > > > > Actually, I was seriously considering making a null library (that > > > has all the right calls but no code). Call it "equiet" and ln -s it > > > to the esound locations.:) > > > >

Re: [pygtk] Init trouble

2000-06-11 Thread Deirdre Saoirse
On Sun, 11 Jun 2000, Niklas Saers Mailinglistaccount wrote: > > Actually, I was seriously considering making a null library (that > > has all the right calls but no code). Call it "equiet" and ln -s it > > to the esound locations.:) > > Ok, so bottom line is that this is something which should b

Re: [pygtk] Init trouble

2000-06-11 Thread Niklas Saers Mailinglistaccount
> Actually, I was seriously considering making a null library (that has all > the right calls but no code). Call it "equiet" and ln -s it to the esound > locations.:) Ok, so bottom line is that this is something which should be fixed in Gnome, right? If so, who should we let know about this (to h

Re: [pygtk] Init trouble

2000-06-11 Thread Deirdre Saoirse
On Thu, 8 Jun 2000, Arkaitz wrote: > I suspect this are caused by GNOME starting esd as you suggested. Does > anyone know how to disable the sound support in GNOME? Actually, I was seriously considering making a null library (that has all the right calls but no code). Call it "equiet" and ln -s

Re: [pygtk] Init trouble

2000-06-11 Thread Deirdre Saoirse
This is a stupid gnome dependency on ethe esound libraries. Which is dumb really. I don't want my GUI builders making noise. Ever. I have now, in order to get it to work at all, recompiled my version of glade and gnome-python to be gtk+ only. I will be changing my tutorial to give info on the gtk

Re: [pygtk] Init trouble

2000-06-08 Thread Niklas Saers Mailinglistaccount
> Well, the /dev/dsp message is due to the gnome-libs initialising esd. I > don't know about the Alarm clock message. Try passing the --disable-sound > argument to your program to disable esd usage and see if that makes a > difference. Dear James, that seemed to do the trick about that. :) Than

Re: [pygtk] Init trouble

2000-06-08 Thread Arkaitz
On Thu, Jun 08, 2000 at 10:08:04AM +0800, James Henstridge wrote: > > Well, the /dev/dsp message is due to the gnome-libs initialising esd. I > don't know about the Alarm clock message. Try passing the --disable-sound > argument to your program to disable esd usage and see if that makes a > dif

Re: [pygtk] Init trouble

2000-06-07 Thread James Henstridge
On Wed, 7 Jun 2000, Niklas Saers Mailinglistaccount wrote: > Hi. When I do a > > import gnome.ui > > (or applet or capplet) or even just > python /usr/local/lib/python1.5/site-packages/gnome/ui > then I get first Permission denied to /dev/dsp0 (which is ok since I don't > have a soundcard wh

[pygtk] Init trouble

2000-06-07 Thread Niklas Saers Mailinglistaccount
Hi. When I do a import gnome.ui (or applet or capplet) or even just python /usr/local/lib/python1.5/site-packages/gnome/ui then I get first Permission denied to /dev/dsp0 (which is ok since I don't have a soundcard which is supported on my FreeBSD 4.0 box) and then I get an 'Alarm clock' and