[SOLVED] slackware current - xfce 4.10 shows completely blank black screen
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.
slackware current - xfce 4.10 shows completely blank black screen
xfce 4.10 is running though as I can hit Alt-F4 and the exit menu appears and then click on LOGOUT.
But nothing else shows on the screen.
Here is the .xsession-errors file for a user:
Code:
/usr/bin/startxfce4: X server already running on display :0
xfce4-panel: error while loading shared libraries: libexo-1.so.0: cannot open shared object file: No such file or directory
Thunar: error while loading shared libraries: libexo-1.so.0: cannot open shared object file: No such file or directory
xfdesktop: error while loading shared libraries: libgarcon-1.so.0: cannot open shared object file: No such file or directory
xfce4-volumed: error while loading shared libraries: libkeybinder.so.0: cannot open shared object file: No such file or directory
** (process:3147): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** (process:3147): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
** (process:3147): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
^[[01mHP Linux Imaging and Printing System (ver. 3.12.6)^[[0m
^[[01mSystem Tray Status Service ver. 2.0^[[0m
Copyright (c) 2001-14 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
^[[35;01mwarning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.^[[0m
** (process:3153): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** (process:3153): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
** (process:3153): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Loading configuration plugins
blueman-applet version 1.22 starting
Stale PID, overwriting
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Off hand it looks like libexo-1.so.0 and libgarcon-1.so.0 are missing from the xfce4 packages....
Last edited by aaazen; 08-02-2012 at 11:38 PM.
Reason: Alt-F4 to exit xfce ...
following which criteria?
if you want to select what to install and what not, it's assumed that you know what you're doing...
otherwise a full install is advised.
These packages are misnamed as they actually do include shared runtme libraries:
libexo-1.so.0.0.0
libgarcon-1.so.0.0.0
And the packages should be called
libexo-0.8.0-i486-1.txz and
libgarcon-0.2.0-i486-1.txz
That isn't how packages are named. Generally Slackware just favours upstream naming conventions -- other distros sometimes split packages into lib versions but that isn't the case with Slackware. For example, atk is not named libatk and gmp is not named libgmp. Both the exo and garcon packages exist in the newly created xfce/ directory, so if you want XFCE to work...then obviously you will need to install everything in that directory (unless you want to troubleshoot). They should not be moved to l/ since they are XFCE-specific and they should not be renamed since they are named according to upstream. I don't see a problem here.
That isn't how packages are named. Generally Slackware just favours upstream naming conventions -- other distros sometimes split packages into lib versions but that isn't the case with Slackware...
Both the exo and garcon packages exist in the newly created xfce/ directory, so if you want XFCE to work...then obviously you will need to install everything in that directory (unless you want to troubleshoot)...
Thanks for your post.
I found several more packages missing from my xfce installation.
Most of the time I use fvwm2 to avoid complex window managers with lots of pieces.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.