SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Schemas were not compiled - running the following -
Code:
glib-compile-schemas /usr/share/glib-2.0/schemas
This fixes the multiple keyring dirs being created. I now have one keyring dir, can close and open chrome, nm-applet ---- whatever to my hearts content, and only have a single keyring dir. AND logging out cleans the tmp directory.
Hrm, I *thought* I had handled that in postinstall scripts. I'll double-check - thanks!
Click here to see the post LQ members have rated as the most helpful post in this thread.
Four of those listed above are also required for KDE 4.95 (4.6) and they are,
libatasmart
sg3_utils
udisks
upower
Going a little further, even alot of these deps can be made optional. Robby chose to add gnome-keyring support, but it can be removed without any issue. In GVFS, the http backend stuff is disabled via. a configure switch, so that gets rid of also that chain (libsoup, libproxy, gnome-keyring, gconf, orbit2, etc). After that, and the udisks/upower stuff that inevitably has to go in (for KDE too, of course), we're down to just a a few packages without any loss of automounting magic.
I know the keyring might be useful for some, but IMO the purpose of XFCE is to provide a lighter-weight alternative; adding very optional things from gnome just doesn't feel right.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,089
Rep:
Quote:
Originally Posted by abrouwers
Going a little further, even alot of these deps can be made optional. Robby chose to add gnome-keyring support, but it can be removed without any issue....
I've found you can leave out gnome-keyring, but not libgnome-keyring. If I tried to run Xfce 4.8 without it, it would fall back to the command line with an error message that a component of libgnome-keyring was required.
I've found you can leave out gnome-keyring, but not libgnome-keyring. If I tried to run Xfce 4.8 without it, it would fall back to the command line with an error message that a component of libgnome-keyring was required.
Ah, sorry for not being clear; the xfce stack (specifically, I think just gvfs and xfce4-session) would need rebuilding without the keyring libraries around, for the deps to disappear.
I start from 'startx' from runlevel 3 after boot. I've only started Xfce from kdm to test the given solution on the google searches, but I always start from runlevel 3 with 'startx'. It's not a customized .xinitrc, it's the one from xwmconfig, indeed.
Side question, though it's not related to the above: Do we really need avahi? I mean, I haven't started it (forgot to) and Xfce does not complain about this.
I'm running into the same problem as rfernandez. The output of 'ck-list-sessions' looks like his does, except I have a login-session-id. I'm starting xfce from run level 3, and I don't have a customized xinitrc.
RE my on-going thunar problems - It looks like me not having samba installed was what was causing the problem. I don't have any network shares to browse, but apparently not having samba make thunar keep looking for the network until it gives up.
Mon Jan 31 05:31:20 UTC 2011
Rebuilt xfce (BUILD=3_rlw)
Included latest point releases of several components
Upgraded Terminal to 0.4.6
Removed mousepad
this is broken (no print function) and unmaintained for 4.8
Rebuilt gnome-keyring
Thanks to disturbed1 on LQ for noticing that I forgot to
build the glib schemas in postinstall
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,089
Rep:
Quote:
Originally Posted by rworkman
Yep, and here's tonight's entry:
Code:
Mon Jan 31 05:31:20 UTC 2011
Rebuilt xfce (BUILD=3_rlw)
Included latest point releases of several components
Upgraded Terminal to 0.4.6
Removed mousepad
this is broken (no print function) and unmaintained for 4.8
Rebuilt gnome-keyring
Thanks to disturbed1 on LQ for noticing that I forgot to
build the glib schemas in postinstall
Well...
First, your hard work is greatly appreciated.... but.... I tried the new packages and there wasn't a way
out, that is, there was no way to log off or out of the desktop. Ctrl, Alt, BackSpace was the only alternative.
Panel plugs-in, the one I like anyway, still don't work.....
Maybe next time around the gentlemen over at Xfce will get it all straighten out.
Thanks for taking the time to compile the packages.
Last edited by cwizardone; 01-31-2011 at 12:58 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,089
Rep:
Well, I tried 4.8 again this morning using all the packages including those dated 30 January.
As previously mentioned, there was not a log out option. That is, there was no way to get out of the GUI other than using Atl, Ctrl, Backspace.
There was no Settings Manager.
The following plug-ins would not install, Weather, Wavelan, System Load Montior, Sensor, Network Monitor, and Mail Watcher.
The following plug-ins apparently installed, that is, there wasn't an error message, but they promptly disappeared and were nowhere to be seen, Xfce-Xmms, Clipman, and Verve.
As to rebuilding them, no.
Tried running Zenwalk 7-Beta in VirtualBox as it uses Xfce4.8 and in regard to the plug-ins, it was about the same as what is outlined above.
Last edited by cwizardone; 02-02-2011 at 11:48 AM.
Reason: Typo.
The followiing plugi-ins apparently installed, that is, there wasn't an error message, but they promptly disappeared and were no where to be seen, Xfce-Xmms, Clipman, and Verve.
Yesterday I released a 4.8-compatible tarball of the xmms-plugin:
Its successor playercontrol-plugin will soon be available (in the git repo, at least). There is already a beta package here but the current code contains many changes and fixes.
You can not, nor should not expect plugins compiled against an older Xfce interface to be compatible with this newer interface. It was not a simple bumb in the version. There's a whole new plugin layout, ui lib ......
Most of the plugins you stated don't work, might have updated releases or patches available. Xfce 4.8 is brand new, some plugins have been unmaintained and un-updated for for a few years. Unfortunately when the main UI and libraries get re-written things do not always just work. A little human intervention is required. Lucky for us some other people have stepped up to port the most popular plugins to the new UI.
Your log out problem was noted by myself a few posts back, Robby posted a link to the bug. This has been fixed, at least on my systems. I can startx from init 3 as a regular user, and have reboot/shutdown ... options. Not sure about your session options they appear here. I'm using Xfce 4.8 on 3 32bit laptops, 2 32bit PCs, and 4 64bit PCs, and do not have any of the issues you are having. I did do a little leg work first with the plugins, and manually updated, or pulled from git the ones I use most often. Xmms, Mixer, Screen Shooter, Notes and Remmina all work fine here. Don't use any of the other ones on your list.
If you are using SBopkg to build SlackBuilds, remember, SBo is only guaranteed to work for the released versions of Slackware.
Last edited by disturbed1; 02-02-2011 at 03:10 PM.
Edited for clarify since I was too late in the posting...
(@ llgar) Wow, I didn't realize you were a plugin maintainer.
cwizardone, maybe I haven't been too clear on this, but binary packages of the plugins aren't going to work with xfce-4.8 unless the packages are built for 4.8; perhaps you did that, but I didn't -- all of my plugin packages were built for 4.6, so they're useless with 4.8.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.