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

Bug#264689: marked as done (lincvs: segmentation fault after upgrading Qt to 3.3)

Your message dated Fri, 12 May 2006 10:18:03 -0400
with message-id <200605121018.04269.chrsmrtn@debian.org>
and subject line lincvs Qt crashes
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: lincvs
Version: 1.3.2-1
Severity: normal

Yesterday I made a dist-upgrade. Today I tried to start lincvs, which
resulted in a segmentation fault.

Best regards, Joachim Lechner

PS: btw. Lincvs 1.3.3 is available.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.6c
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=de_DE@euro

Versions of packages lincvs depends on:
ii  cvs                       1:1.12.9-3     Concurrent Versions System
ii  libc6                     2.3.2.ds1-15   GNU C Library: Shared libraries an
ii  libfam0c102               2.7.0-5        client library to control the FAM 
ii  libgcc1                   1:3.4.1-5      GCC support library
ii  libqt3c102-mt             3:3.3.2-5      Qt GUI Library (Threaded runtime v
ii  libstdc++5                1:3.3.4-7      The GNU Standard C++ Library v3
ii  libx11-6                  4.3.0.dfsg.1-6 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii  xlibs                     4.3.0.dfsg.1-6 X Window System client libraries m

-- no debconf information

--- End Message ---
--- Begin Message --- 
This was fixed long ago.

--- End Message ---
Reply to: