XFCE4.4 on Slamd64 Problems

ljones · 2007-01-27 23:34:31

Hello smile

I've just recently downloaded and begun to install XFCE4.4 using the graphical installer on two of my systems. One is running slackware 11, and is an old laptop, a IBM T22. This runs the 32-bit version of Slackware 11, and XFCE4.4 was quite easy to install -- no problems there smile .

However on the other machine I have, which is an X86-64 (64 bit, http://www.slamd64.com/ ) system it's a lot harder. This system is running a 64-bit version of slackware called "slamd64", and most of the packages such as dbus, dbus-glib, linux-PAM, PolicyKit, hal, vte etc. aren't avaliable as packages (so I've been trying to compile them from source). However I've gotten stuck at just one thing - resolving a missing dependency "SM", I just can't seem to get out of the empasse!

I've tried downloading xproto, libICE and xtrans and managed to compile libSM but to no avail, the installer still won't let me proceed to the next stage -- I'm stuck on "system requirements".

After a lot of googling I read there was a libsm-devel or sm-devel file/package, but I could not find a slackware package, nor just plain source (only the source to libSM). All I could find is lots of RPM files x.x sad . I found that library, libSM here ( http://ftp.x.org/pub/individual/lib/ ) btw. I found a lot of the software could be found on freedesktop.org .

I also tried compiling and having the file libSM.so.6.0 in both /usr/lib and /usr/lib64 but no luck x.x sad

The slackware x11-devel-6.9.0-x86_64-8.tgz is also definately installed.

Can anyone see what I'm doing wrong (or maybe there are packages ..... http://www.linuxpackages.net/ dosen't have the ones I need for x86_64).

Thanks for any help smile

ljones

ljones · 2007-01-28 11:45:53

Possibly solved -- I did (for the libSM sources) ./configure --prefix=/usr/X11R6, and discovered a line while compiling that needed to be run manually - libtool --finish /usr/lib64

ljones

ljones · 2007-01-28 14:45:56

Still no luck though. :-(

I have managed to get XFCE4.4 to compile well .... sort of, it runs but I don't know if it is really running properly. In particular I haven't gotten HAL, DBus and other bits and pieces to work really. From what I can make out, XFCE4.4 on slamd64 needs the folllowing dependenices;

* hal, vte, libsm, libice, xproto, dbus, dbus-glib, linux-pam, policykit . ( libice & xproto are needed to make libsm).

Compiling (I'm doing this all largely from source, less XFCE's graphical installer) and setting these up is a total nightmare sad and I have not been able to work out how to do this, at least not in the proper order and get everything set up 100%. I was wondering if anyone had managed to do this, unfortunatly there aren't any 64-bit packages of the above. There are 32-bit packages, but I get a feeling XFCE is going to get tangled up as it finds one thing is 64-bit, but another 32 bit and I'm guessing that won't work at all. (NB, some 32-bit packages can be found at http://www.linuxpackages.net/ ).

I've managed to find out/try the following as I've been trying to do all of this:

1) use ./configure --prefix=/usr --libdir=/usr/lib64 for most of the configuration scripts.

2) http://cblfs.cross-lfs.org/index.php/PolicyKit says how to compile policykit, but it didn't work :-(- I had to use the option "--disable-docbook-docs" - this seemed to work in the sense that it stopped most errors, but is this the right way to do things?

3) I had to copy dbus from /usr/include/dbus-1.0/dbus to /usr/include/dbus . XFCE's installer wouldn't find it otherwise.

4) For libSM after compiling libice and xproto, I had to do a "libtool --finish /usr/lib64". If not XFCE's graphical installer just won't let you get past the "SM" dependency.

5) To add HAL group and user (haldaemon) do
groupadd haldaemon
useradd -g haldaemon haldaemon .
I did the same thing for "polekit" too.

6) On my system I have XFCE4 running - just (debatable over how well it really is running!), but stuff like HAL isn't working. I read in another thread that the command "hald --daemon=no --verbose=yes" can give some help on HAL problems, and looking through there is a problem in mine which goes something like this;

arguments to dbus_error_is_set() were incorrect, assertion "error !=NULL" failed in file dbus-errors. c .

And I found another one;

Glib-CRITICAL **:g_hash_table_lookup_extended: assertion 'hash_table !=NULL' failed .

Wish I knew if the options such as --prefix=/usr --libdir=/usr/lib64 and the order I'm doing things in was correct!.

:? Really confused !

Thanks

ljones

ljones · 2007-01-28 20:23:14

*thinks ..... :?

Right now I've cleared off my slamd 11 install, and tried again. Now this time I seem to have gotten a little bit further - I've been using instructions from this ( http://cblfs.cross-lfs.org/index.php/Main_Page ) site. I know that's not really the "right" site to use, but most stuff has worked so far. Though I must admit I am still not sure on weather libraries need to go into /usr/lib or /usr/lib64 or even /usr/local/lib .... :?

Right now my biggest problem is on this ( http://cblfs.cross-lfs.org/index.php/PolicyKit ) page. I can do most of this but there are 3 scripts on that page, one "bootscript", a script to link into runlevels and a privilages script. That last one - the privilage script works but the first two don't because if I remember correctly, slackware does its business in /etc/rc.d in a slightly different way to other distros. For example there is no /etc/rc.d/init.d in slackware. So I can't quite use those scripts, I'm not sure what to change them to.

ljones

ljones · 2007-01-28 21:50:45

AH smile I think I might have it now! You see, I have a laptop here - it is an old IBM T22 running normal 32-bit slackware 11. It is running xfce4 & HAL,etc ok. Well, I pinched the message bus init files from it, which I found in

/etc/dbus-1

I zipped these up, and unzipped them to the same (/etc/dbus-1) on the PC with slamd64, and it seems to have worked, even without those scripts I mentioned. I also pinched /etc/rc.d/rc.messagebus and rc.hal too.

smile

Now if this really is all working, I need to write this all up properly.

weibullguy · 2007-01-29 16:50:39

ljones wrote:

Compiling (I'm doing this all largely from source, less XFCE's graphical installer) and setting these up is a total nightmare and I have not been able to work out how to do this, at least not in the proper order and get everything set up 100%. I was wondering if anyone had managed to do this, unfortunatly there aren't any 64-bit packages of the above. There are 32-bit packages, but I get a feeling XFCE is going to get tangled up as it finds one thing is 64-bit, but another 32 bit and I'm guessing that won't work at all.

Hehe, GNOME is alot more fun! XFCE just builds; no patches, no seds to put things where they need to go. It's a testament to the XFCE developers. Yes, XFCE-4.4 will build and install on a Pure64-bit or multilib platform. You are correct, you can't mix 32-bit and 64-bit libraries.

ljones wrote:

1) use ./configure --prefix=/usr --libdir=/usr/lib64 for most of the configuration scripts.

Depending on Slamd64's layout, this may or may not be correct. If Slamd64 is a multilib distro (it sounds like it is) and Slamd64 follows the FHS in this respect, then 64-bit libraries should go in /lib64, /usr/lib64, etc. If you're using the instructions from http://cblfs.cross-lfs.org/index.php/Main_Page, be careful about things like

mv -v /usr/bin/FOO{,-64} &&
ln -sfv /usr/bin/multiarch_wrapper /usr/bin/FOO

and

USE_ARCH=64 ./configure

since you won't have the multiarch_wrapper program. You also won't have the env variables BUILD64 and PKG_CONFIG_PATH64 set.

ljones wrote:

2) http://cblfs.cross-lfs.org/index.php/PolicyKit says how to compile policykit, but it didn't work :-(- I had to use the option "--disable-docbook-docs" - this seemed to work in the sense that it stopped most errors, but is this the right way to do things?

Hmmm, I'm using an older version of PolicyKit than what would currently be checked out and the CBLFS instructions work as written. All you did was disable building the documentation because you don't have docbook-utils installed (I guess). Typically, disable would be default and you would pass --enable-docbook-docs.

ljones · 2007-01-30 23:38:37

Intresting smile thanks for that I must read up on all of that. However it appears my earlier enthusiasm was a little misplaced sad I have XFCE4.4 running, and for some strange reason it will mount a USB memory stick, but not the cdrom drives. Half the problem is that I have no idea on how to configure up stuff like dbus, hal, policykit, etc x.x . Also things seem a bit mixed up with regards to cdrom drives - sometimes the icon for the cdrom drive will be there if I leave a cd in the drive, but apon ejecting it won't go away and won't mount again.

You're right about the docbook stuff but I now have this fixed smile (in the sense it compiles ok)v it's just the HAL/DBus/Policyscript stuff I have no idea about.

ljones

Xfce Forum

Sub domains

#1 2007-01-27 23:34:31

XFCE4.4 on Slamd64 Problems

#2 2007-01-28 11:45:53

Re: XFCE4.4 on Slamd64 Problems

#3 2007-01-28 14:45:56

Re: XFCE4.4 on Slamd64 Problems

#4 2007-01-28 20:23:14

Re: XFCE4.4 on Slamd64 Problems

#5 2007-01-28 21:50:45

Re: XFCE4.4 on Slamd64 Problems

#6 2007-01-29 16:50:39

Re: XFCE4.4 on Slamd64 Problems

#7 2007-01-30 23:38:37

Re: XFCE4.4 on Slamd64 Problems

Board footer