Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Frans Pop]

I'm seeing this issue 100% reproducible as well, and for me removing 
libc6-i686 _does_ fix input handling.

I'm only seeing it on my i386 laptop, not on my amd64 desktop.

$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 2
model name  : Mobile Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping: 9
cpu MHz : 1599.960
cache size  : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up cid 
xtpr
bogomips: 3194.45

Hope this helps.


pgpKC8gAzTAyv.pgp
Description: PGP signature

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Vincent Lefevre]

On 2007-07-08 11:22:12 +0200, Frans Pop wrote:
> I'm seeing this issue 100% reproducible as well, and for me removing 
> libc6-i686 _does_ fix input handling.

Ditto here.

> I'm only seeing it on my i386 laptop, not on my amd64 desktop.
> 
> $ cat /proc/cpuinfo
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 15
> model   : 2
> model name  : Mobile Intel(R) Pentium(R) 4 CPU 2.80GHz
> stepping: 9
> cpu MHz : 1599.960
> cache size  : 512 KB
> fdiv_bug: no
> hlt_bug : no
> f00f_bug: no
> coma_bug: no
> fpu : yes
> fpu_exception   : yes
> cpuid level : 2
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up cid 
> xtpr
> bogomips: 3194.45

vin:~> cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 6
model name  : Intel(R) Pentium(R) D CPU 3.00GHz
stepping: 4
cpu MHz : 2992.882
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 6
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
pni monitor ds_cpl vmx est cid cx16 xtpr lahf_lm
bogomips: 5990.42

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 15
model   : 6
model name  : Intel(R) Pentium(R) D CPU 3.00GHz
stepping: 4
cpu MHz : 2992.882
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 6
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
pni monitor ds_cpl vmx est cid cx16 xtpr lahf_lm
bogomips: 5985.35

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Javier Serrano Polo]

Upgrading the kernel to 2.6.21 seems to have fixed this.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Frans Pop]

> Upgrading the kernel to 2.6.21 seems to have fixed this.

Hmm. That's an interesting data point, but it does not really help for all 
the cases where aptitude is run in for example a sid chroot on an Etch 
system (which is my situation).


pgpUG5FTWKbxQ.pgp
Description: PGP signature

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Jens Kubieziel]

* Javier Serrano Polo schrieb am 2007-07-11 um 14:22 Uhr:
> Upgrading the kernel to 2.6.21 seems to have fixed this.

I upgraded today to 2.6.22-rc5 and can agree. The described bug
disappeared.

Besten Gruß

-- 
Jens Kubieziel   http://www.kubieziel.de
Solange man bewundern und lieben kann, ist man immer jung. Pablo Casals

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Jens Kubieziel]

Package: aptitude
Version: 0.4.5.3-1
Severity: grave

Hi,

steps to reproduce:
1. open aptitude
2. select a package to install/upgrade/remove
3. type 'g'
4. after finished the action I can push any button, but aptitude doesn't react
to the keypress.

aptitude is listed in ps with 'Sl+' (interruptible sleep, foreground process).
When sending a SIGINT (Ctrl+C), aptitude interrupts and all characters typed
beforehand are printed to the shell prompt.

I did a strace. You can find the output at
http://www.kubieziel.de/tmp/aptitude.strace.bz2> (660 kB).

Actually I'm not sure where the problem sits. If I can provide further
information, please tell me what.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-k7 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.5 0.7.2Advanced front-end for dpkg
ii  libc6   2.5-11   GNU C Library: Shared libraries
ii  libgcc1 1:4.2-20070609-1 GCC support library
ii  libncursesw55.6-3Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a  2.0.17-2 type-safe Signal Framework for C++
ii  libstdc++6  4.2-20070609-1   The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do  (no description available)
pn  libparse-debianchangelog-perl  (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Daniel Burrows]

On Fri, Jun 29, 2007 at 11:29:20AM +0200, Jens Kubieziel <[EMAIL PROTECTED]> 
was heard to say:
> steps to reproduce:
> 1. open aptitude
> 2. select a package to install/upgrade/remove
> 3. type 'g'
> 4. after finished the action I can push any button, but aptitude doesn't react
> to the keypress.
> 
> aptitude is listed in ps with 'Sl+' (interruptible sleep, foreground process).
> When sending a SIGINT (Ctrl+C), aptitude interrupts and all characters typed
> beforehand are printed to the shell prompt.

  Is this 100% reproducible for you?

  If you can compile it with debugging symbols, could you get a threaded
dump? (i.e., run "info threads" in gdb, then "thread " and
"backtrace" for each thread number)

  Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Jens Kubieziel]

* Daniel Burrows schrieb am 2007-07-02 um 02:13 Uhr:
> On Fri, Jun 29, 2007 at 11:29:20AM +0200, Jens Kubieziel <[EMAIL PROTECTED]> 
> was heard to say:
> > 4. after finished the action I can push any button, but aptitude doesn't 
> > react
> > to the keypress.
> 
>   Is this 100% reproducible for you?

Yes, I have two different machines where I use this aptitude version and
it happens every at bith machines.

>   If you can compile it with debugging symbols, could you get a threaded
> dump? (i.e., run "info threads" in gdb, then "thread " and
> "backtrace" for each thread number)

hope this helps:

(gdb) info threads
  10 Thread -1253835888 (LWP 25615)  0xb7f4e410 in ?? ()
  8 Thread -1223259248 (LWP 25613)  0xb7f4e410 in ?? ()
  7 Thread -1231651952 (LWP 25612)  0xb7f4e410 in ?? ()
* 1 Thread -1212483888 (LWP 25552)  0xb7f4e410 in ?? ()
(gdb) thread 1
[Switching to thread 1 (Thread -1212483888 (LWP 25552))]#0  0xb7f4e410 in ?? ()
(gdb) bt
#0  0xb7f4e410 in ?? ()
#1  0xbf997338 in ?? ()
#2  0x010f in ?? ()
#3  0x in ?? ()
(gdb) thread 7
[Switching to thread 7 (Thread -1231651952 (LWP 25612))]#0  0xb7f4e410 in ?? ()
(gdb) bt
#0  0xb7f4e410 in ?? ()
#1  0xb6967278 in ?? ()
#2  0x0002 in ?? ()
#3  0xb7e20dbe in __lll_mutex_lock_wait () from /lib/i686/cmov/libpthread.so.0
#4  0xb7e1cabc in _L_mutex_lock_88 () from /lib/i686/cmov/libpthread.so.0
#5  0xb7e1c4ad in pthread_mutex_lock () from /lib/i686/cmov/libpthread.so.0
(gdb) thread 8
[Switching to thread 8 (Thread -1223259248 (LWP 25613))]#0  0xb7f4e410 in ?? ()
(gdb) bt
#0  0xb7f4e410 in ?? ()
#1  0xb71682d4 in ?? ()
#2  0x in ?? ()
(gdb) thread 10
[Switching to thread 10 (Thread -1253835888 (LWP 25615))]#0  0xb7f4e410 in ??
()
(gdb) bt
#0  0xb7f4e410 in ?? ()
#1  0xb543f318 in ?? ()
#2  0x0001 in ?? ()
#3  0xb7e1e5d6 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#4  0x08090c3f in threads::condition::wait (this=Cannot 
access memory at address 0x8
)
at ../../../src/generic/util/threads.h:454
Backtrace stopped: previous frame inner to this frame (corrupt stack?)



Besten Gruß

-- 
Jens Kubieziel   http://www.kubieziel.de
Man sollte die Menschen lehren, nicht von Gerechtigkeit zu sprechen,
sondern von Nächstenliebe. Eugène Ionesco

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Daniel Burrows]

  Let's eliminate a variable.

  If you change your language to C, do you still get this crash?
Run "LANG=C LC_ALL=C aptitude" to check.

  Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Jens Kubieziel]

* Daniel Burrows schrieb am 2007-07-02 um 16:44 Uhr:
>   If you change your language to C, do you still get this crash?
> Run "LANG=C LC_ALL=C aptitude" to check.

Yes, same behaviour as I described.

-- 
Jens Kubieziel   http://www.kubieziel.de
Computers are like air conditioning systems,
with opened Windows operate them most ineffecticely!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#431054: aptitude doesn't respond to keyboard after installing/upgrading a package

[Jakob]

On Mon, Jul 02, 2007 at 05:02:41PM +0200, Jens Kubieziel wrote:
> * Daniel Burrows schrieb am 2007-07-02 um 16:44 Uhr:
> >   If you change your language to C, do you still get this crash?
> > Run "LANG=C LC_ALL=C aptitude" to check.
> 
> Yes, same behaviour as I described.

I've experienced this myself for a while, but thought it might be
something with my eccentric setup that might be causing it.  It's great
to hear that someone else shares my woes.

For me, it's not 100% reproducible, but it does happen more often than
not.  Also, you can resize the terminal window, and it responds by
resizing and adjusting the windows' contents, so the process isn't
completely hosed, but it does not respond to any keys, making it
pretty useless.

Jakob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]