Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I don't use Gnome so I can't recommend any solutions to the original issue however routinely running as root is a highly risky move, because all it takes to damage your system beyond repair is to make one typo. In fact the only time you should ever run as root is in a small number of specific circumstances (such as when you are installing new packages).
Instead, you should ordinarily always run as a regular user. Regular accounts cannot modify system-level files or directories, and therefore the worst mistake you can make as a regular user is to lose your own personal data. In contrast, the worst mistake you can make as root could cause complete and total system corruption, with your only option being to totally reinstall Linux from scratch. That can ruin your day really fast, believe me.
In short, I would strongly recommend against running as root unless you have a specific task that requires root privileges. -- J.W.
yea i understand your point j.w....and that was just my point, everything looks fine when i log in as root, however thats not a good thing, because its still pretty much broken, as i would never run a normal session as root...
ok i still havent found a solution for this but i believe it has something to do with the gconf configurations. i noticed if i open the gconf editor under a normal user, there is 3 folders to the left but none of them contain any keys. however if i am logged in as root and run gconf editor, there is quite a few folders to the left, one of them being "font_rendering" which has a key for the d.p.i. set to 96, and all other folders have keys defined....now that i think i have narrowed it down to this, i have no idea now to correct it
I gave up with garnome, I just wasn't happy with the way things worked together. Since I had been installing loads
of different window managers on the system I decided it was time for a clean out. So reinstalled the whole system - hmmm what fun.
From the installation menu I selected gnome (2.4) rather than KDE-system, and everything works a treat - whether logged in as
root/or normal user.
Now what is it about SuSE's customisation of KDE/Gnome that makes them incompatible? No matter how many times I
deleted all gnome related directories from the normal users $HOME, SuSE never generated a gconf/gconfd/gnome/gnome2
structure that gave icons/menus/working keyboard that I have now. Weird.
It might be worth someone trying an uninstall of KDE, followed by an install of gnome to see if that's the conflict here. Otherwise,
I'd definitely recommend waiting for SuSE 9.2 - should be here in a month.
I've had the same problems. Lots of times. The missing icons text is not missing. It is just so small that you cannot see it easily . How to fix it? I found that I had to change the DPI for the fonts to "96". So how do you do this when you can't see anything? Login using KDE as your window manager, go to "Gnome Control Center" and then to "fonts", then click on what should be the "details" button at the bottom of the page, and then on the next window (at the top, there will be a very small but barely visible form space) type in the number (I use a 17" Flat Panel and have 96 DPI, which is a common DPI for regular monitors too I believe). Then close the window and it ought to be OK. It is kinda hard to do when the fonts are minuscule, but I have done it. Why this happens, I haven't figured out entirely (I have several hypothesis).
Nah - I gave up and stuck with Gnome 2.4 installed from the start. I have seen lots of post on suse-linux mailbase about people having some success with gnome 2.8 as distributed on http://www.usr-local-bin.org/linux.php
But then I read that SuSE 9.2 will only have gnome 2.6 - this seems a bit silly, since I heard that a whole lot of things got fixed/improved in 2.8 - oh well
Totally agree with you there - why not join the suse-linux mailbase, and search on gnome. There are a few pertinent emails there which discuss how to get hold of the latest version of Gnome - basically until there's a consensus on the best way to install and configure Gnome such that you don't lose out on all the niceties that SuSE put in Linux I will stick with SuSE's gnome 2.4
I mean it can't be that difficult to arrange for Yast to be on the System menu, and for the icons to appear correctly. What we need is either a comprehensive install guide, or a script that downloads and configures everything for you.
Is there no section where you can select window manager?
Failing that, I guess gnome isn't distributed with the personal ed.
If you have high speed internet access, you can easily install the
Pro version using the SuSE ftp servers. There are loads of threads
telling you how to do this, and I know for a fact that you can select
gnome as part of the Pro install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.