[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#252888: marked as done (Sudden crash of konsole)

Your message dated Sat, 20 May 2006 10:13:46 +0200
with message-id <20060520081346.GA7003@hades.madism.org>
and subject line Sudden crash of konsole
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: konsole
Version: 4:3.2.2-1
Severity: normal

I've used konsole for a long time. It works good for me.
However, today strange situation happened. I was logged on by ssh on
remote machine. I was running shell script with a lot of output lines.
While browsing the script output with ctrl-pgdn/ctrl-pgup konsole
disappeared.
I had two konsole sessions opened, so couldn't close both of them by
accident.
No bugreport window from KDE appeared (the one with Konqui, saying, that
application did something wrong (SIG11 or sth)).
I couldn't reproduce the problem (but will try to), but I am pretty
sure that the bug exists somewhere, because:
a) I didn't do anything special, which could cause observed behaviour
b) I have no strange problems with system - everything works as expected

So, while it is still easy to close the bug with UNREPRODUCIBLE tag, I'd
like to give it a chance and try to find and fix it.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (ignored: LC_ALL set to pl_PL)

Versions of packages konsole depends on:
ii  kdelibs4                  4:3.2.2-2      KDE core libraries
ii  libart-2.0-2              2.3.16-5       Library of functions for 2D graphi
ii  libc6                     2.3.2.ds1-13   GNU C Library: Shared libraries an
ii  libfam0c102               2.7.0-5        client library to control the FAM 
ii  libgcc1                   1:3.3.3-9      GCC support library
ii  libice6                   4.3.0.dfsg.1-4 Inter-Client Exchange library
ii  libpng12-0                1.2.5.0-6      PNG library - runtime
ii  libqt3c102-mt             3:3.2.3-2      Qt GUI Library (Threaded runtime v
ii  libsm6                    4.3.0.dfsg.1-4 X Window System Session Management
ii  libstdc++5                1:3.3.3-9      The GNU Standard C++ Library v3
ii  libx11-6                  4.3.0.dfsg.1-4 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-4 X Window System miscellaneous exte
ii  libxrender1               0.8.3-7        X Rendering Extension client libra
ii  libxtst6                  4.3.0.dfsg.1-4 X Window System event recording an
ii  xlibs                     4.3.0.dfsg.1-4 X Window System client libraries m
ii  zlib1g                    1:1.2.1.1-3    compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Jun 05, 2004 at 08:45:27PM +0200, Robert Gomułka wrote:
> Package: konsole
> Version: 4:3.2.2-1
> Severity: normal
> 
> I've used konsole for a long time. It works good for me.
> However, today strange situation happened. I was logged on by ssh on
> remote machine. I was running shell script with a lot of output lines.
> While browsing the script output with ctrl-pgdn/ctrl-pgup konsole
> disappeared.
> I had two konsole sessions opened, so couldn't close both of them by
> accident.
> No bugreport window from KDE appeared (the one with Konqui, saying, that
> application did something wrong (SIG11 or sth)).
> I couldn't reproduce the problem (but will try to), but I am pretty
> sure that the bug exists somewhere, because:
> a) I didn't do anything special, which could cause observed behaviour
> b) I have no strange problems with system - everything works as expected
> 
> So, while it is still easy to close the bug with UNREPRODUCIBLE tag, I'd
> like to give it a chance and try to find and fix it.

  there is no useful information in that bug report: no backtrace, no
steps to reproduce, hence not tagging UNREPRODUCIBLE, just *closing* it.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: