Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Might be that it didn't install correctly? Try uninstalling GDM using slapt-get then reinstalling. The config files (even when running stock Slackware) always point to GDM first because if it's installed, Pat thinks you want to use it.
If that doesn't work, you may need to uninstall the gsb desktop and reinstall. I've had this problem before when I tried gsb, and the top command worked.
I think no reason to reinstall gsb-desktop, as I have twice reinstalled fresh Slackware + fresh gsb-desktop.
I have found within logfiles:
within /var/log/gdm/:0.log
...
(WW) VESA(0): Failed to set up write-combining range (0xd0000000, 0x770000)
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing
...
within /var/log/Xorg.0.log
...
(WW) VESA(0): Bad V_BIOS checksum
...
(WW) VESA(0): Failed to set up write-combining range (0xd0000000, 0x770000)
...
What do these log entries mean? Is it something serious? Maybe some other log files could identify errors throwing libraries / packages?
Asus X58L laptop. Video - Embedded Intel® GMA X3100 Gfx.
I have gone to Slackware 13.1 on my laptop. There was visualy similar problem, I solved that by emptying home folder for user, starting kdm logon manager and first logon into gnome.
Whith fresh Slack 13.1 there was visually similar problem, with some differences.
Slack 13.1 - gdm logon window starts normally, logging into gnome crashes and gives xterm window.
Slack 12.1 - couldnot start neither gdm logon window, neither gnome from kdm. Some message frame was infinitelly blinking in both cases.
KDM and KDE works fine on Slack 12.1 and on Slack 13.1.
On Slackware 13.1, gsb 2.30 I solved that by emptying home folder, starting kdm, first logon into gnome.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.