Yes, Gnome uses xserver. You could say Xserver is what KDE and Gnome runs on top of, the fundament for linux GUIs.
Gedit will not work if you have to log in to recovery from the boot menu, nano can be nice to know for emergencies, or even better if you know some vi basics since nano isnt available by default in many distros. Changes in xorg.conf could cause xserver to fail and then theres no hope of starting gedit. Sure the cp of the backupfile will work anyway but nano/vi can save you some time as you dont have to restore the backup with cp and then boot up to Gnome to edit again.
Yes, Gnome uses xserver. You could say Xserver is what KDE and Gnome runs on top of, the fundament for linux GUIs.
Gedit will not work if you have to log in to recovery from the boot menu, nano can be nice to know for emergencies, or even better if you know some vi basics since nano isnt available by default in many distros. Changes in xorg.conf could cause xserver to fail and then theres no hope of starting gedit. Sure the cp of the backupfile will work anyway but nano/vi can save you some time as you dont have to restore the backup with cp and then boot up to Gnome to edit again.
True. I was assuming an operational system rather than recovery mode, but in this case that might be necessary...I make backups anyway!
The day's over for me, so I'm heading for home now to give it a shot...
Thanks, that worked (mostly). I can only see half the scroll bar on the right side of the screen, but it's usable. :-)
Quote:
Quote:
Yes, Gnome uses xserver. You could say Xserver is what KDE and Gnome runs on top of, the fundament for linux GUIs.
Gedit will not work if you have to log in to recovery from the boot menu, nano can be nice to know for emergencies, or even better if you know some vi basics since nano isnt available by default in many distros. Changes in xorg.conf could cause xserver to fail and then theres no hope of starting gedit. Sure the cp of the backupfile will work anyway but nano/vi can save you some time as you dont have to restore the backup with cp and then boot up to Gnome to edit again.
True. I was assuming an operational system rather than recovery mode, but in this case that might be necessary...I make backups anyway!
The day's over for me, so I'm heading for home now to give it a shot...
Kathryn: 7.04 did have widescreen problems if you used the standard graphics drivers, but they are completely fixed in 7.10, at least it seems that way on my laptop (a 15.4" widescreen) and those of some other people I know.
Woot!
Thanks for the info. I'm a bit bummed that I have to work the next 3 Saturdays. I don't want to attempt an upgrade on a Sunday and then be all stressed if something goes wrong.
Any idea if an upgrade to 7.10 will destroy my ability to boot into Fedora (or Vista for that matter)? My initial install of Fedora broke my ability to boot into Ubuntu. I can post my grub.conf file if necessary. I know, at minimum, to preserve my sanity, I'll have to edit it to change 7.04 to read 7.10 on the bootloader screen. Something small like that will drive me nuts.
Never underestimate my ability to break things :)
I upgraded to 7.10. And in my brilliant tinkering, I managed to completely bork my screen resolution. It's now at something horrible like 800x600. Or at least that's what it looks like. And I don't know how to get back to my slightly less horrible, fuzzy 1024x768. If I can figure out the hardware, can someone point me in the right direction on how to get things back to "normal". I rarely use Ubuntu, but I do do some stuff in it. And any tips on figuring out the graphics stuff would be incredible. I have the dxdiag output from Windows, but I'm curious to know if there's something similar in Linux.
*sigh*
Sadly, I seem to get in less trouble using the command line and manually editing config files.
And yes, I can always reinstall. I burned the 7.10 Kubuntu CD. I'd just rather not reinstall due to something so stupid and that should be easily solved (in theory).
I recommend distro openSuSE 10.3 which is stable (although newly released), easy to maintain and contains plenty of good programs in it's repositories. openSuSE contains YaST, which is a very powerful configuration manager - easy to use - so transition from Windows won't be painful.
I use 64bit version without any problems.
There is a suse forum where you can find plenty of useful information. Community on this forum is very kind, people are always willing to help.
LiveCD is already available too, you can download it from here
OpenSuse is quite nice. It was the first one I tried. But I gave up because I was in the attic and the router was in the basement. I never did get it to play nice with the wireless and I was too clueless to get it to work.
I use Fedora 7 day to day now. I've been very impressed. It got my monitor's resolution and wireless right out of the box. I bounce back and forth between using Yum and the GUI package manager. If I know what I need, I use Yum. If I'm looking for something I use the package manager. The Fedora forums were very helpful too.
The rare occasions I boot back to Vista, I just want to pull my hair out.
No idea how you managed ;-) I mainly know this problem from using Wine and playing one of those games that notoriously kill your resolution settings even in Windows (Diablo 2, for example, has always been great at that). But when it happens, I normally use "dpkg-reconfigure xserver xorg" to set it right once. Afterwards I can choose the resolution normally over the KDE applet again. Of course, you must be a bit careful not to use any settings that won't work at all, or maybe the xserver won't start, but so far I've never managed to get that far ;-) always worked okay after reconfigure apart from one time I messed up my keyboard layout (which was of course easily fixed). So if you don't suffer from "command line phobia" you might want to give it a try. Working in the GUI is great as long as everything works as it should, but when there's no way KDE will use a decent resolution there's nothing like fixing it the old school way.
No idea how you managed ;-) I mainly know this problem from using Wine and playing one of those games that notoriously kill your resolution settings even in Windows (Diablo 2, for example, has always been great at that). But when it happens, I normally use "dpkg-reconfigure xserver xorg" to set it right once. Afterwards I can choose the resolution normally over the KDE applet again. Of course, you must be a bit careful not to use any settings that won't work at all, or maybe the xserver won't start, but so far I've never managed to get that far ;-) always worked okay after reconfigure apart from one time I messed up my keyboard layout (which was of course easily fixed). So if you don't suffer from "command line phobia" you might want to give it a try. Working in the GUI is great as long as everything works as it should, but when there's no way KDE will use a decent resolution there's nothing like fixing it the old school way.
Luckily, (with a lot of help) I've gotten over my CLI phobias. I'll try it out this weekend. I've come to the conclusion that even if I break it, reinstalling the OS is a cakewalk. I have my grub config file backed up so I can fix that if something goes wrong in a reinstall. And I know how to edit in grub during the boot process. So even if I do have to reinstall, I should be good to go. And it'll give me an excuse to change over to KDE. I'm not all that crazy about Gnome.
I am using SuSE Linux 10.1. Recently I had a problem compiling the flight simulator ACM-5.0 and the manual suggested changing the default depth of the screen to 24 bits, going in the /etc/X11/xorg.conf file. But the file has a warning "DO NOT EDIT THIS FILE" so I called YAST and did the change. Sometimes it is easier to follow the rules of the game than doing changes the old way, by CLI. Maybe I am getting old.
Tullio
I upgraded to 7.10. And in my brilliant tinkering, I managed to completely bork my screen resolution. It's now at something horrible like 800x600. Or at least that's what it looks like. And I don't know how to get back to my slightly less horrible, fuzzy 1024x768. If I can figure out the hardware, can someone point me in the right direction on how to get things back to "normal". I rarely use Ubuntu, but I do do some stuff in it. And any tips on figuring out the graphics stuff would be incredible. I have the dxdiag output from Windows, but I'm curious to know if there's something similar in Linux.
I had resolution problems when I upgraded to 7.10, but using info from this post, I was able to work around it.
It may not be an exact fit, but it should point in the right direction.
Yes, Gnome uses xserver. You
)
Yes, Gnome uses xserver. You could say Xserver is what KDE and Gnome runs on top of, the fundament for linux GUIs.
Gedit will not work if you have to log in to recovery from the boot menu, nano can be nice to know for emergencies, or even better if you know some vi basics since nano isnt available by default in many distros. Changes in xorg.conf could cause xserver to fail and then theres no hope of starting gedit. Sure the cp of the backupfile will work anyway but nano/vi can save you some time as you dont have to restore the backup with cp and then boot up to Gnome to edit again.
Team Philippines
RE: Yes, Gnome uses
)
True. I was assuming an operational system rather than recovery mode, but in this case that might be necessary...I make backups anyway!
The day's over for me, so I'm heading for home now to give it a shot...
Seti Classic Final Total: 11446 WU.
@th3, Thanks, that worked
)
@th3,
Thanks, that worked (mostly). I can only see half the scroll bar on the right side of the screen, but it's usable. :-)
Seti Classic Final Total: 11446 WU.
RE: RE: Kathryn: 7.04 did
)
Never underestimate my ability to break things :)
I upgraded to 7.10. And in my brilliant tinkering, I managed to completely bork my screen resolution. It's now at something horrible like 800x600. Or at least that's what it looks like. And I don't know how to get back to my slightly less horrible, fuzzy 1024x768. If I can figure out the hardware, can someone point me in the right direction on how to get things back to "normal". I rarely use Ubuntu, but I do do some stuff in it. And any tips on figuring out the graphics stuff would be incredible. I have the dxdiag output from Windows, but I'm curious to know if there's something similar in Linux.
*sigh*
Sadly, I seem to get in less trouble using the command line and manually editing config files.
And yes, I can always reinstall. I burned the 7.10 Kubuntu CD. I'd just rather not reinstall due to something so stupid and that should be easily solved (in theory).
Kathryn :o)
Einstein@Home Moderator
I recommend distro openSuSE
)
I recommend distro openSuSE 10.3 which is stable (although newly released), easy to maintain and contains plenty of good programs in it's repositories. openSuSE contains YaST, which is a very powerful configuration manager - easy to use - so transition from Windows won't be painful.
I use 64bit version without any problems.
There is a suse forum where you can find plenty of useful information. Community on this forum is very kind, people are always willing to help.
LiveCD is already available too, you can download it from here
RE: I recommend distro
)
OpenSuse is quite nice. It was the first one I tried. But I gave up because I was in the attic and the router was in the basement. I never did get it to play nice with the wireless and I was too clueless to get it to work.
I use Fedora 7 day to day now. I've been very impressed. It got my monitor's resolution and wireless right out of the box. I bounce back and forth between using Yum and the GUI package manager. If I know what I need, I use Yum. If I'm looking for something I use the package manager. The Fedora forums were very helpful too.
The rare occasions I boot back to Vista, I just want to pull my hair out.
Kathryn :o)
Einstein@Home Moderator
No idea how you managed ;-) I
)
No idea how you managed ;-) I mainly know this problem from using Wine and playing one of those games that notoriously kill your resolution settings even in Windows (Diablo 2, for example, has always been great at that). But when it happens, I normally use "dpkg-reconfigure xserver xorg" to set it right once. Afterwards I can choose the resolution normally over the KDE applet again. Of course, you must be a bit careful not to use any settings that won't work at all, or maybe the xserver won't start, but so far I've never managed to get that far ;-) always worked okay after reconfigure apart from one time I messed up my keyboard layout (which was of course easily fixed). So if you don't suffer from "command line phobia" you might want to give it a try. Working in the GUI is great as long as everything works as it should, but when there's no way KDE will use a decent resolution there's nothing like fixing it the old school way.
RE: No idea how you managed
)
Luckily, (with a lot of help) I've gotten over my CLI phobias. I'll try it out this weekend. I've come to the conclusion that even if I break it, reinstalling the OS is a cakewalk. I have my grub config file backed up so I can fix that if something goes wrong in a reinstall. And I know how to edit in grub during the boot process. So even if I do have to reinstall, I should be good to go. And it'll give me an excuse to change over to KDE. I'm not all that crazy about Gnome.
Kathryn :o)
Einstein@Home Moderator
I am using SuSE Linux 10.1.
)
I am using SuSE Linux 10.1. Recently I had a problem compiling the flight simulator ACM-5.0 and the manual suggested changing the default depth of the screen to 24 bits, going in the /etc/X11/xorg.conf file. But the file has a warning "DO NOT EDIT THIS FILE" so I called YAST and did the change. Sometimes it is easier to follow the rules of the game than doing changes the old way, by CLI. Maybe I am getting old.
Tullio
RE: Never underestimate my
)
I had resolution problems when I upgraded to 7.10, but using info from this post, I was able to work around it.
It may not be an exact fit, but it should point in the right direction.
Seti Classic Final Total: 11446 WU.