headers
David C. Rankin | 16 Feb 2010 10:48

Possible kde44 conflict breaking gnome - need help finding out


Listmates,

  I need your help figuring out what is killing my gnome 2.2 install on openSuSE
11.0 (x86_64). There appears to be some part of kde4 that was installed that is
breaking gnome's ability to run the gnome setting daemon, and many common
widgets (like gvolume-control, tomboy, etc.) crash immediately upon startup. For
example, the volume control in gnome is completely broken, the error for the
volume crash offers to "Reload" the volume for you, but when you click "Reload"
the volume control immediately crashes again. (sound works, you just can't
change the volume)

  I have gone back and collected all the symptoms I can in hope somebody can
help me connect-the-dots and figure out how to fix gnome. (I have saved the
xsession-error file is somebody can make heads or tails out of them) Gnome was
working perfectly immediately before kde44 install. After the install, it looks
like it has lost the ability to set any of its appearance setting (it can't even
change the background wallpaper). What is very strange is that the fonts are
huge even though they are set at the same 8pt as in kde. They look like they are
12-14pt without the gnome settings daemon running.

  Opposite to what is broken in gnome, all the gtk setting work fine in kde44.
You gnome appearance setting like theme, colors, font size, font, etc. all are
properly displayed with gimp, firefox, etc. run in kde, but all are completely
broken in Gnome??? Go figure.

  I don't know how this could be happening. Gnome settings are supposed to work
in gnome -- you could expect problems in kde -- but not the opposite.

  The symptoms and broken apps in gnome are:
(Continue reading)

Permalink | Reply | 3 comments |
headers
Neil Bird | 17 Feb 2010 12:35
Face
Favicon

Re: Possible kde44 conflict breaking gnome - need help finding out


Around about 16/02/10 09:48, David C. Rankin typed ...
>    I need your help figuring out what is killing my gnome 2.2 install on openSuSE
> 11.0 (x86_64).

   This is just a random thought or two, I'm not professing to have any 
detailed clue about any of these low-level GNOME/KDE processes!

> ------------------------------------------------------------------------------
>    Unable to start the settings manager 'gnome-settings-daemon'.
>    Without the GNOME settings manager running, some preferences may not take
>    effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE)
>    settings manager may already be active and conflicting with the GNOME
>    settings manager.
> ------------------------------------------------------------------------------

   If this is not the root cause of all your woes, it's definitely the first 
thing to figure out.  I personally wouldn't be worrying about /any/ of the 
other symptoms until this is running OK.

   *Is* there another (KDE) settings thing running, somehow added to your 
login?  I don't know what the KDE equivalent of g-s-d would be, but really 
from login (into a GNOME session) I would hope not to see any KDE processes 
(unless you're also starting KDE apps. at login).

   Try killing any KDE-like processes.

   Also try starting gnome-sessions-daemon on the command line (it's in 
/usr/libexec on my Fedora box) to see if you get anything more (although all 
output should be in .xsession-errors).  Maybe there's a debug flag in the
(Continue reading)

Permalink | Reply | 2 comments |
headers
David C. Rankin | 19 Feb 2010 04:53

Re: Possible kde44 conflict breaking gnome - need help finding out


On 02/17/2010 05:35 AM, Neil Bird wrote:
>> ------------------------------------------------------------------------------
>>
>>    Unable to start the settings manager 'gnome-settings-daemon'.
>>    Without the GNOME settings manager running, some preferences may
>> not take
>>    effect. This could indicate a problem with Bonobo, or a non-GNOME
>> (e.g. KDE)
>>    settings manager may already be active and conflicting with the GNOME
>>    settings manager.
>> ------------------------------------------------------------------------------
> 
>   If this is not the root cause of all your woes, it's definitely the
> first thing to figure out.  I personally wouldn't be worrying about
> /any/ of the other symptoms until this is running OK.
> 

Neil,

	Thank you for your reply! I have checked and there isn't any kde 'anything'
running. That is the strange part. Here are two screenshots that clearly show
what I'm talking about. The first is what my black-gold gtk theme looks like,
but it is with thunderbird running in KDE!

http://www.3111skyline.com/download/bugs/gnome/gtk2-in-kde.jpg

	When I state gnome (where the gtk theme used to work perfectly), I get nothing
but the unthemed look:
(Continue reading)

Permalink | Reply | 1 comment |
headers
David C. Rankin | 19 Feb 2010 15:05

jhbuild check needed for ffi


Devs,

	After the frustration with something killing gnome settings daemon on my
openSuSE 11.0 install, I decided to build gnome with jhbuild to crosscheck with
something I would have debug information for.

	I configured jhbuild per the website, ran jhbuild sanitycheck and bootstrap and
got a clean bill of health -- no errors, no requirements not met.

	Building gnome 2.30, jhbuild failed on step 17/238 due to the missing
dependency of ffi.h (Foreign Function Interface library). Installing the library
and the continuing the build worked fine.

	It might be a good idea for a ffi.h check to be added during the jhbuild sanity
check. That way, the 2.30 build will keep running after you kick it off and then
go the sleep :p

--

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
Permalink | Reply | 0 comments |
headers
David C. Rankin | 19 Feb 2010 15:09

Re: Possible kde44 conflict breaking gnome - need help finding out


On 02/18/2010 09:53 PM, David C. Rankin wrote:
> On 02/17/2010 05:35 AM, Neil Bird wrote:
>>> >> ------------------------------------------------------------------------------
>>> >>
>>> >>    Unable to start the settings manager 'gnome-settings-daemon'.
>>> >>    Without the GNOME settings manager running, some preferences may
>>> >> not take
>>> >>    effect. This could indicate a problem with Bonobo, or a non-GNOME
>>> >> (e.g. KDE)
>>> >>    settings manager may already be active and conflicting with the GNOME
>>> >>    settings manager.
>>> >> ------------------------------------------------------------------------------
>> > 
>> >   If this is not the root cause of all your woes, it's definitely the
>> > first thing to figure out.  I personally wouldn't be worrying about
>> > /any/ of the other symptoms until this is running OK.
>> > 

As a check for the settings daemon crash problem, I'm trying jubuild with 2.30,
(see post about ffi.h check), if it works, I'll be more than happy to be brought
into the 20th century with my gnome packages. I don't know why openSuSE doesn't
keep it's packages current for its supported releases. To offer nothing but
gnome 2.2 for openSuSE 11.0 is a joke. Oh well....

--

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(Continue reading)

Permalink | Reply | 0 comments |
headers
David C. Rankin | 19 Feb 2010 15:35

jhbuild Errors - gtk+


Devs,

	I've run into a few more issues that look rather critical with jhbuild of 2.30.
The latest with the gtk build:

/gtkprintoperation-unix.c ./gtkprintunixdialog.c ./gtkprintbackend.c
./gtksearchenginebeagle.c ./gtksearchenginetracker.c ./gtkprint-win32.c
./gtkprintoperation-win32.c ./gtkplug-x11.c ./gtksocket-x11.c ./gtkxembed.c
./gtktrayicon-x11.c ./gtkmountoperation-x11.c ./gtkplug-win32.c
./gtksocket-win32.c ./gtkwin32embed.c ./gtkwin32embedwidget.c
./gtkmountoperation-stub.c ./gtksearchenginequartz.c ./gtkplug-stub.c
./gtksocket-stub.c ./gtkmountoperation-stub.c ./gtkplug-stub.c
./gtksocket-stub.c ./gtkmountoperation-stub.c ./gtktypebuiltins.h
./gtktypebuiltins.c --output Gtk-2.0.gir
/home/david/apps/bld/gnome2/gtk+/gtk/gtkalias.h:64: unexpected character `''
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:10: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:22: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:40: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:61: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:103: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:190: unexpected
character ` <at> '
/home/david/apps/bld/gnome2/gtk+/gtk/gtksearchenginequartz.h:227: unexpected
character ` <at> '
(Continue reading)

Permalink | Reply | 1 comment |
headers
David C. Rankin | 20 Feb 2010 03:16

Re: jhbuild Errors - gtk+ libproxy error (jsapi.h)


On 02/19/2010 08:35 AM, David C. Rankin wrote:
> 
> Devs,
> 
> 	I've run into a few more issues that look rather critical with jhbuild of 2.30.
> The latest with the gtk build:
> 
<snip>

Guys, I have made good progress getting all the way to the libproxy build
(71/238) and the build is apparently failing complaining about jsapi.h (see
below). I have installed every version of mozilla mozilla-xulrunner192-devel I
could (contains jsapi.h), but no help. Any suggestions?

 gcc -DPACKAGE_NAME=\"libproxy\" -DPACKAGE_TARNAME=\"libproxy\"
-DPACKAGE_VERSION=\"0.2.3\" "-DPACKAGE_STRING=\"libproxy 0.2.3\""
-DPACKAGE_BUGREPORT=\"nathaniel <at> natemccallum.com\" -DPACKAGE=\"libproxy\"
-DVERSION=\"0.2.3\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DSTDC_HEADERS=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STDLIB_H=1
-DHAVE_MALLOC=1 -I. -I../../src/lib -DXP_UNIX -DJS_THREADSAFE
-I/opt/gnome2/include/xulrunner-1.9.0.13/stable -I/opt/gnome2/include/nspr -g
-std=c99 -g -O2 -DPLUGINDIR=\"/opt/gnome2/lib64/libproxy/0.2.3/plugins\"
-DSYSCONFDIR=\"/opt/gnome2/etc\" -D_POSIX_C_SOURCE=1 -MT mozjs_la-mozjs.lo -MD
-MP -MF .deps/mozjs_la-mozjs.Tpo -c mozjs.c  -fPIC -DPIC -o
.libs/mozjs_la-mozjs.o
mozjs.c:32:19: error: jsapi.h: No such file or directory
(Continue reading)

Permalink | Reply | 0 comments |
headers
David C. Rankin | 21 Feb 2010 09:39

gnome settings daemon crash cli errors: GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed


Dev's

	Still chasing the gnome settings daemon failure. When run from fluxbox/openbox,
the setting will stay on for 3-4 seconds, then they crash back to the defaults.
The command line error when this occurs is:

(gnome-control-center:1920): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

	Any thoughts on how to cure this? I have had to give up on jhbuild for the
moment. Still stuck at 77/238 with the gudev dependencies. Let me know if you
have any wisdom to pass on. Thanks.

--

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
Permalink | Reply | 0 comments |

Gmane