SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Desktop=Any of them.
Terminal=All of them, Even downloaed Eterm, still will not start. Xterm in Xtwm will not work either.
Kernel=2.7.6 Went back into the stock kernel and still nothing.
Can't really use any commands because Im in X.
Dropped out of X into console and removed and reinstalled Gnome-Terminal and still nothing.
I added like two extra packages. Thunderbird and K3b on here, (my desktop) and it did the same thing as on my laptop. Terminal will not start with the same error. This was after I rebooted.
I take it Im the only one with this problem and Slack 10?
That's really weird... so it only happened after a reboot? did u modify something? Can u try with XFree instead of X11? I can't help you further because i've never seen that kind of error, maybe some guru around here...
I thought that I had gone back into the stock kernel and tried, but I didn't. Sorry my bad.
Anyways I did try going back into the stock kernel just now and I had to change back the "nvidia" to "vesa" in the drivers area and logged in. (Thats how I figured out I didn't do this yet. :duh. Clicked on the terminal icon and it worked.
So I went back into the 2.6.7 kernel and changed the drivers around in there (xorg.conf). Booted and tried a terminal and still nothing. So I think I have it narrowed down to a 2.6.7 thing. Which really makes me lost. Could it be something different I have compiled in with the 2.6.7 kernel? Exactly how would I cp the exact .config file over to use in the 2.6.7 compile? Wonder if that will work.
I have reinstalled and changed the drivers around in the 2.4.26 kernel and yes the terminal still works.
I'm having this EXACT same problem, using Dropline Gnome 2.6.x, slack 10, kernel 2.6.8-rc2....
The first time I booted 2.6.8-rc2 and installed Dropline Gnome, then ran it for the first time, everything was fine.
I then exited dropline, and rebooted.
I now get the same error as above... I'm not sure whether restarting dropline or rebooting caused it.
EDIT: I'm pretty positive my kernel config is correct, I've done countless kernel configs for this hardware on various distros... in fact gnome-terminal worked before a reboot, but reboot of same kernel... i think this may be a dropline thing. if no response in a couple days I'll crosspost dropline forums with relevant info.
reverting away from >=2.6.6 not an option.
Last edited by hollywoodb; 07-28-2004 at 10:13 PM.
hollywoodb: If youy are still following this thread...I had the same problem, wasn't just gnome though...flux and kde were broken as well. Your solution did the trick. How did you come accross this? I have been using Linux for a while now and have never had that line in my fstab...
I am having this problem as well (2.6.9 kernel, Dropline 2.8), however, opening the terminal in x as root produces no error, whereas opening the terminal as an user other than root produces the error "there was an error opening the child process for this terminal"
I will try the solution posted above and report back w/ result.