In message <[EMAIL PROTECTED]>
Todd Suess <[EMAIL PROTECTED]> wrote:
> At 01:00 PM 1/11/00 -0500, Ben Collins wrote:
>
> >Well, if you are still having a problem with ^C (note, you must restart
> >your su shell), then it isn't caused by the login package. I tested it
> >thoroughly, and i
Yup, I rebooted the machine, etc, and even if I am on the
console and SU'd to root in a kvt window under KDE, if I do
tail -f /var/log/syslog or any kind of command, ctrl-c will not
exit the task. Have to ctrl-z and then kill %1 to actually kill
the job.
Todd
At 01:00 PM 1/11/00 -0500, Ben C
On Tue, Jan 11, 2000 at 12:55:19PM -0500, Todd Suess wrote:
> tsuess:~# dpkg --list login
> Desired=Unknown/Install/Remove/Purge
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Nam
tsuess:~# dpkg --list login
Desired=Unknown/Install/Remove/Purge
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ NameVersion Description
+++-===
On Tue, Jan 11, 2000 at 12:40:55PM -0500, Todd Suess wrote:
>
> > > > It is su, and it will be fixed in tomorrow's dinstall run.
> > >
>
> I updated login last night during apt-get dist-upgrade but ctrl-c is
> still broken.
What version of the login package?
--
---===-=-==-===
> > It is su, and it will be fixed in tomorrow's dinstall run.
>
I updated login last night during apt-get dist-upgrade but ctrl-c is
still broken.
Regards,
Todd
On Sun, Jan 09, 2000 at 06:23:39PM +0100, Peter Schuller wrote:
> > > Cant seem to kill a running process with ^C anymore. Noticed the problem
> > > last night but do not know when the problem crept in.
> > >
> > > I can suspend the process with ^Z and then kill it manually with kill but
> > > ^C
On Sun, 9 Jan 2000, Peter Schuller wrote:
> Which package is su part of? That is, which package should one apt-get
> install to get rid of this problem once the fix is in?
[EMAIL PROTECTED]:~ $ dpkg -S /bin/su
login: /bin/su
ciao,
der.hans
> Thanks!
--
# +++==
On Sun, Jan 09, 2000 at 06:23:39PM +0100, Peter Schuller wrote:
> > > Cant seem to kill a running process with ^C anymore. Noticed the problem
> > > last night but do not know when the problem crept in.
> > >
> > > I can suspend the process with ^Z and then kill it manually with kill but
> > > ^C
> > Cant seem to kill a running process with ^C anymore. Noticed the problem
> > last night but do not know when the problem crept in.
> >
> > I can suspend the process with ^Z and then kill it manually with kill but
> > ^C does not seem to work anymore.
>
> It is su, and it will be fixed in tom
On Sat, Jan 08, 2000 at 05:34:52PM -0800, Alex Romosan wrote:
> ... when i am logged in as root using bash
> as my shell things start to break. also, bash doesn't seem to export
> environment variables. this breaks a lot of scripts. we better get
> this fixed soon.
I suppose you did a `set -a',
Today's potato upgrade has debconf 0.2.67 which fixes the problem.
On Sun, Jan 09, 2000 at 02:02:40AM -, Pollywog wrote:
> I also read (on Dalnet #debian) this morning that debconf is broken so it
> should not be upgraded.
>
> --
> Andrew
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL
I also read (on Dalnet #debian) this morning that debconf is broken so it
should not be upgraded.
--
Andrew
George Bonser <[EMAIL PROTECTED]> writes:
> ^C only seems to be broken for SOME programs.
>
> If I, for example, go to /var/lib/dpkg/info and do an ls ... a ^C will not
> stop it.
>
> If I issue ^C at the bash prompt, I get a new prompt. ^C also seems to
> kill top.
>
> ^C will not kill a ps
Yep, ctrl-c wasn't killing dselect for me this afternoon, I upgraded last night.
I was su'ed in, btw.
-Aaron Solochek
[EMAIL PROTECTED]
George Bonser wrote:
> Cant seem to kill a running process with ^C anymore. Noticed the problem
> last night but do not know when the problem crept in.
>
> I
On Sat, Jan 08, 2000 at 01:55:21PM -0800, George Bonser wrote:
>
> Cant seem to kill a running process with ^C anymore. Noticed the problem
> last night but do not know when the problem crept in.
>
> I can suspend the process with ^Z and then kill it manually with kill but
> ^C does not seem to w
I noticed this as well, I think it crept in in an update a few days
ago. I first noticed it while tailing a log with -f, had to ctrl-z to get
out of it.
Todd
On Sat, 08 Jan 2000, George Bonser wrote:
> Cant seem to kill a running process with ^C anymore. Noticed the problem
> last night but do
In message <[EMAIL PROTECTED]>
George Bonser <[EMAIL PROTECTED]> wrote:
> Cant seem to kill a running process with ^C anymore. Noticed the problem
> last night but do not know when the problem crept in.
>
> I can suspend the process with ^Z and then kill it manually with kill but
> ^C d
18 matches
Mail list logo
