Re: Can't run gnome-settings-daemon 2.24.1-1 on 10.5.6

On Dec 23, 2008, at 3:50 PM, Richard Cobbe wrote:

> On Tue, Dec 23, 2008 at 11:21:06AM -0500, Alexander Hansen wrote:
>
>> Gnucash works here (10.5.6 with Xquartz 2.3.1, and most everything  
>> was
>> built before that OS was released).
>>
>> I also don't get the same messages from gnome-settings-daemon that  
>> you
>> do.
>>
>> $ /sw/lib/gnome-settings-daemon/gnome-settings-daemon --no-daemon
>> xrdb:  "*Label.background" on line 220 overrides entry on line 150
>> xrdb:  "*Text.background" on line 226 overrides entry on line 191
>> xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
>> xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
>> xscreensaver: 10:57:36: locking is disabled (not compiled with  
>> locking
>> support).
>>
>> This is running from Terminal.app with standard Fink environment
>> settings, by the way.  I tried running gnome-settings-daemon from the
>> default xterm from running X11.app, which does _not_ use my  
>> environment,
>> and I didn't get the same failure mode:
>>
>> $ /sw/lib/gnome-settings-daemon/gnome-settings-daemon --no-daemon
>>
>> ** (gnome-settings-daemon:20313): WARNING **: Couldn't connect to
>> session bus: dbus-launch failed to autolaunch D-Bus session:  
>> Autolaunch
>> requested, but X11 support not compiled in.
>> Cannot continue.
>>
>>
>> ** (gnome-settings-daemon:20313): WARNING **: Could not get a  
>> connection
>> to the bus
>>
>> But it's worth checking whether you're running from Terminal.app or
>> X11's default terminal.
>
> In the experiment I tried earlier today, I was running from xterm.   
> I just
> tried it from Terminal.app, though, and got the same behavior that I  
> saw
> this morning.
>
> This is all somewhat irrelevant, though, because normally I start
> gnome-settings-daemon from the shell script ~/.x-startup, which I have
> configured Xquartz to run automatically upon starting X, which I start
> automatically upon login.
>
> I really hate to do this, but I'm about to give up on Gnucash  
> completely
> and just buy Quicken or something, because then I won't have to go  
> through
> this kind of grief with every gnome update.  Fink's gnome support,  
> at least
> in unstable, has consistently caused problems: first, there was the  
> xmodmap
> nonsense, which was annoying but I could work around; and now this,  
> which
> is essentially preventing me from running any gnome apps  
> whatsoever.  I no
> longer have the energy or inclination to deal with this.
>
> I just tried blowing away all my gnome settings and starting the  
> daemon
> again; no change.  Once I get back from Christmas travels, I'll try
> upgrading Xquartz (and thus XCode) to see if that works, but I don't  
> want
> to try that remotely.
>
> Richard
>
> (For this I gave up Linux?)
>

I doubt changing your X11 server will change anything here.

You're starting X11 in a configuration in which it's almost guaranteed  
that Fink's environment isn't going to be processed.  Have you tried  
_not_ starting X11 at login, and instead just running gnucash at a  
Terminal.app prompt?  This works for me whether X11 is running or not,  
whereas if I try to run from xterm, with no Fink environment, it  
complains about missing configuration stuff.  For that matter, even  
just using "source /sw/bin/init.sh ; gnucash" could possibly work  
around the issue.

Apple's X11 server has always only accepted user environment  
customizations if they're in a ~/.bashrc file or ~/.MacOSX/ 
enviroment.plist . 
   

------------------------------------------------------------------------------