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

Bug#281143: marked as done (korganizer: Crash on startup)



Your message dated Sun, 15 Jan 2006 23:03:20 -0500
with message-id <43CB1B08.5050706@vif.com>
and subject line Should be fixed
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Nov 2004 01:33:22 +0000
>From bouf10pub2@myriade.ca Sat Nov 13 17:33:22 2004
Return-path: <bouf10pub2@myriade.ca>
Received: from relais.videotron.ca [24.201.245.36] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CT9Gc-0005wr-00; Sat, 13 Nov 2004 17:33:22 -0800
Received: from localhost.localdomain ([24.202.86.71])
 by VL-MO-MR010.ip.videotron.ca
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTP id <0I75002TGAQOME@VL-MO-MR010.ip.videotron.ca> for
 submit@bugs.debian.org; Sat, 13 Nov 2004 20:28:00 -0500 (EST)
Date: Sat, 13 Nov 2004 20:28:00 -0500
From: =?iso-8859-1?q?F=E9lix-Antoine_Bourbonnais?= <bouf10pub2@myriade.ca>
Subject: korganizer: Crash on startup
To: Debian Bug Tracking System <submit@bugs.debian.org>
Bcc: =?iso-8859-1?q?F=E9lix-Antoine_Bourbonnais?= <bouf10pub2@myriade.ca>
Message-id: <0I75002THAQOME@VL-MO-MR010.ip.videotron.ca>
MIME-version: 1.0
X-Mailer: reportbug 3.2
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,FROM_HAS_MIXED_NUMS,
	HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: korganizer
Version: 4:3.3.0-3
Severity: important

Korganizer crashes each time I try to start it. When I lunch the command
korganizer in a console, I see :
bouf10@claudius:~$ korganizer
ERROR: Communication problem with korganizer, it probably crashed.
bouf10@claudius:~$ KCrash: Application 'korganizer' crashing...

I'v created a new user and tried to remove all configs files and it's still
the same thing...

I'm currently using an unstable package for korganizer with
amd64/gcc-3.4.

System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.8-9-amd64-k8
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

Versions of packages korganizer depends on:
ii  kdelibs4        4:3.3.1-1                KDE core libraries
ii  ktnef           4:3.3.0-3                KDE TNEF viewer
ii  libart-2.0-2    2.3.16-6                 Library of functions for 2D graphi
ii  libc6           2.3.2.ds1-18.0.0.1.amd64 GNU C Library: Shared libraries an
ii  libgcc1         1:3.4.2-3.0.0.1.amd64    GCC support library
ii  libice6         4.3.0.dfsg.1-8           Inter-Client Exchange library
ii  libidn11        0.5.2-3                  GNU libidn library, implementation
ii  libkcal2        4:3.3.0-3                KDE calendaring library
ii  libkdepim1      4:3.3.0-3                KDE PIM library
ii  libkgantt0      4:3.3.0-3                KDE gantt charting library
ii  libkpimexchange 4:3.3.0-3                KDE PIM Exchange library
ii  libkpimidentiti 4:3.3.0-3                KDE PIM user identity information 
ii  libpng12-0      1.2.7-1                  PNG library - runtime
ii  libqt3c102-mt   3:3.3.3-5.0.0.1.amd64    Qt GUI Library (Threaded runtime v
ii  libsm6          4.3.0.dfsg.1-8           X Window System Session Management
ii  libstdc++6      3.4.2-3.0.0.1.amd64      The GNU Standard C++ Library v3
ii  libx11-6        4.3.0.dfsg.1-8           X Window System protocol client li
ii  libxext6        4.3.0.dfsg.1-8           X Window System miscellaneous exte
ii  libxrender1     0.8.3-7                  X Rendering Extension client libra
ii  perl            5.8.4-4                  Larry Wall's Practical Extraction 
ii  xlibs           4.3.0.dfsg.1-8           X Window System client libraries m
ii  zlib1g          1:1.2.2-3                compression library - runtime

-- no debconf information

---------------------------------------
Received: (at 281143-close) by bugs.debian.org; 16 Jan 2006 04:03:08 +0000
>From ido@vif.com Sun Jan 15 20:03:07 2006
Return-path: <ido@vif.com>
Received: from mail.vif.com ([216.239.64.153] helo=buddha.vif.com)
	by spohr.debian.org with esmtp (Exim 4.50)
	id 1EyLaF-0006OD-On
	for 281143-close@bugs.debian.org; Sun, 15 Jan 2006 20:03:07 -0800
Received: from [216.239.77.227] (ip216-239-77-227.vif.net [216.239.77.227])
	by buddha.vif.com (8.13.1/8.13.1) with ESMTP id k0G434ZV040511
	for <281143-close@bugs.debian.org>; Sun, 15 Jan 2006 23:03:04 -0500 (EST)
	(envelope-from ido@vif.com)
Message-ID: <43CB1B08.5050706@vif.com>
Date: Sun, 15 Jan 2006 23:03:20 -0500
From: Filipus Klutiero <ido@vif.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20051002)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: 281143-close@bugs.debian.org
Subject: Should be fixed
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-vif-MailScanner-Information: Please contact the ISP for more information
X-vif-MailScanner: Found to be clean
X-vif-MailScanner-From: ido@vif.com
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by buddha.vif.com id k0G434ZV040511
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02

Hi F=E9lix-Antoine,
please reopen if you can reproduce with a KDE version > 3.3.1 (as=20
upstream bug report indicates the fix should be in 3.3.2).



Reply to: