debian etch to lenny dist-upgrade broke X for current user.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
debian etch to lenny dist-upgrade broke X for current user.
Today I did an apt-get dist-upgrade from debian etch to lenny. seems to work great except that my regular user account startx then immediately closes. There are also warnings about could not init font path elements. Using root or any other account I can startx fine. There are no error messages in /var/log/Xorg.0.log. This seems like a permissions issue or something simple, but I do not know what to check. I am used to slackware where if something broke, you knew what it was...
It's something simple like you need new drivers, or you forgot to install a DM, or xorg didn't install correctly. You shouldn't be able to log into an X session as root. You must have done something wrong there, but since you're such an expert Slackware user, I'm sure you can figure it out.
Don't mean to be an *** but that reply seems a bit caustic. For the past two years or however long I have come here for help I have never been greeted like that. We try to help each other here, don't we?
Anyway, since when can root not start x? X starts correctly for other users. I have seen similar problems when using gnome (I have broken the current user's gconf or something). I am not using gnome or kde here though, just fluxbox. I am by no means a slackware expert it is just what I have used for the longest time. Maybe I gave the impression that i was using a login manager (xdm, gmd, kdm - by default root can not log in with those) but I am not, I prefer to log in to console then startx when I want to. For me this has a few advantages .. if I break X (which happens a lot because I can never leave stuff alone )I can still log in to work on stuff without a livecd, etc
I don't really think I did anything wrong. I had a fully functional system and did a dist-upgrade. I know in the world of Ubuntu that normally causes problems (for my brother at least). I thought maybe debian would be better about that. As I was saying everything works great with the new kernel and new packages. Maybe I just have something in one of my regular users hoem directory configuration files that just freaks out the new stuff?? I don't think it is xorg.conf becasue X works fine for other users. This problem seems like it would be really easy to solve, can someone point me in the right direction? I suppose I could just create a new user and use that the copy all my files over and fix permissions but I don't learn much by doing that...
Last edited by pauledwards03; 11-15-2008 at 01:01 PM.
It's something simple like you need new drivers, or you forgot to install a DM, or xorg didn't install correctly.
Strike "or you forgot to install a DM"
It's something simple like you need new drivers, or xorg didn't install correctly.
Slurring Debian with comments like ... "I am used to slackware where if something broke, you knew what it was." are an open invitation to flames. On the Debian boards, it could get you (figuratively) tarred and feathered.
Debian, by default, generally disables GUI logins by root. Since you did an upgrade rather than a fresh install, it's likely that your xorg.conf file is messed up. Normally, this would not be an issue, but with Lenny under intensive development, strange things come and go right now. When Lenny is released there will be release notes to point out potential problems, as of now there are not, so it makes sense to upgrade carefully.
I did not mean to say anything bad about debian, in fact debian potato I think was my first introduction to linux. I have always approached distribution upgrades with caution. I do prefer to do clean installs, other than this small X issue, the upgrade went very well. I will post my xorg.conf when I get back to the office on Monday.
This may be relevant: I did not do a regular install of etch, I used the netisnt disc and only installed X and fluxbox (and other stuff like gtk and such). The machine I am using is a bit antiquated by today's standards, so I like using only what I need.
Last edited by pauledwards03; 11-15-2008 at 02:40 PM.
This was not an X problem, nor a permissions issue. All it was was the new version of fluxbox used different configuration files. namely, I now have a ~/.fluxbox/startup, whereas before I did not. Previously I created a file called ~/.fluxbox/startup to house my startup commands. With the new version of fluxbox, my conflicting files just freaked it out I guess. The solution was to merge the contents of my old startup file into the new one. Knowing this, I have to applaud Debian on this upgrade (especailly to unstable!). :-D