Re: startx
On Sun, 20 Jun 1999, Chris Flipse wrote: Is there a way to set up startx so that it will open on a specified tty (say, tty 13) instead of the next available one? I know it can be done with the various x login apps, but I've had some bad experiences with xdm and wdm locking up my box, and I prefer not to take that chance. :) I think I may be suffering from this. Every so often (it used to be rare, but just recently it's started to happen almost every time I boot, within a few minutes of booting) my machine will freeze up completely. The screen either goes grey or gets vertical stripes (or occasionally different patterns). Ctrl-alt-F? do nothing, neither does Ctrl-alt-Bksp or Ctrl-alt-del. I have one of those danged intelligent power buttons, so that doesn't work either. Unfortunately the machine isn't networked so I can't tell you if it is really dead or just all keyboard input is disabled. I am running the latest of everything as of a few days ago from unstable, and I have xdm managing both tty7 and tty8. My kernel is the kernel-package version of 2.2.7 - I want to recompile it but I haven't had a chance yet. Please, please, can anybody suggest a particular package or set of packages that could be downgraded to fix this? Also any way to keep the machine alive long enough to do the downgrade? TIA, Stuart.
Possible bug report - confirmation anyone?
I recently ended up with a package that refused to either install or remove with dpkg or apt-get. The package was bplay; the version is 0.96-7, which is current in slink. It refused to run either the postinst or the prerm script, erroring out of each with install-mime: command not found. Today, after a lot of experimentation, I was able to get bplay to install by installing mime-support first. Can somebody confirm or deny that bplay should require or suggest mime-support (or at least check that it is present before trying to run install-mime) and if so, file a bug report? Thanks, Stuart.
Re: Apt still not working
Curiouser and curiouser - the files http.us.debian.org_debian_stable_main_binary-i386_Packages http.us.debian.org_debian_stable_non-free_binary-i386_Packages in /var/state/apt/lists are identical (and contain what non-free should contain). I can delete the files and run apt-get update, and the same wrong information comes back. I'm beginning to think the unthinkable... could http.us.debian.org be *wrong*? Stuart. On Sat, 8 May 1999 [EMAIL PROTECTED] wrote: After some poking around in /var/lib/dpkg/available, etc, I have been able to narrow down the problem to the following: apt is only registering the availability of contrib and non-free, but not main. All the entries in available have either Section: contrib/xxx or Section: non-free/xxx. The procedure I went through during install is as follows (maybe I missed some step that should have been obvious...) Boot from first CD, go through install procedure, etc. Select tasks. Go into dselect in the install procedure. Choose multi-cd as the method. Select the paths. Update list of packages. Skip the select page, and go straight to install. Answer all the packages questions. Do the configure and remove steps, just in case. Quit dselect. Use the system (it works fine at this point - all the packages are there) do apt-get update - appears to work fine do apt-get install (anything in main) no installation candidate do apt-get install (anything in contrib/non-free) [usually] unmet dependencies Going into dselect and changing the method to apt acquisition makes no difference. Changing the sources.list lines to say unstable instead of stable also makes no difference. Here are the exact lines from sources.list on one of the computers: deb http://http.us.debian.org/debian stable main contrib non-free deb http://non-us.debian.org/debian-non-US stable non-US Thank you in advance for any help, Stuart. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Apt still not working
Okay, this is getting frustrating :( Please, if anyone has any ideas, I would really appreciate them. I now have two computers installed from the same set of official slink CDs (burned from the official images). I must be doing something *really* stupid, because they are both misbehaving in exactly the same way. After some poking around in /var/lib/dpkg/available, etc, I have been able to narrow down the problem to the following: apt is only registering the availability of contrib and non-free, but not main. All the entries in available have either Section: contrib/xxx or Section: non-free/xxx. The procedure I went through during install is as follows (maybe I missed some step that should have been obvious...) Boot from first CD, go through install procedure, etc. Select tasks. Go into dselect in the install procedure. Choose multi-cd as the method. Select the paths. Update list of packages. Skip the select page, and go straight to install. Answer all the packages questions. Do the configure and remove steps, just in case. Quit dselect. Use the system (it works fine at this point - all the packages are there) do apt-get update - appears to work fine do apt-get install (anything in main) no installation candidate do apt-get install (anything in contrib/non-free) [usually] unmet dependencies Going into dselect and changing the method to apt acquisition makes no difference. Changing the sources.list lines to say unstable instead of stable also makes no difference. Here are the exact lines from sources.list on one of the computers: deb http://http.us.debian.org/debian stable main contrib non-free deb http://non-us.debian.org/debian-non-US stable non-US Thank you in advance for any help, Stuart.
