to do so. Debian is unlikely to do anything about it unless
upstream does, however.
Thanks for everyone's help in tracking down the issues involved with dimap
and kmail.
Josh Metzler
(for the Debian Qt/KDE Team)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
this upgrade
my kmail does not start. Just after starting it shows KDE's crash
window with the text (not exact, translated from russian):
Application kmail has broken with signal 11 (SIGSEGV). Stack trace will
be included later.
[...]
I just reproduced this bug.
But i agree with Josh
Looking at the initscript Patrick included in his message, and the one
shipped with the package, it looks he added this line:
PARAMS=-m /var/spool/postfix/var/run/saslauthd
However, according to man start-stop-daemon, -m does not take an argument.
So, my guess is that start-stop-daemon is
There has been a new g++ transition and a few new upstream versions of k3b
in sid since this bug was last tested. Also, I am unsure of exactly what
it affects.
Are these correct:
The amd64 sid version of k3b works fine on a k3b system.
The stable version of i386 k3b crashes in a 32-bit chroot
On Thursday 03 November 2005 01:24 pm, Hervé Leroux wrote:
Subject: kitchensync crashes during the first run
Package: kitchensync
Version: 4:3.4.2-2
Severity: grave
Justification: renders package unusable
When I run kitchensync for the first time (or after
deleting
On Friday 18 November 2005 04:33 pm, Alexandre Touret wrote:
Unpacking libmimelib1c2 (from .../libmimelib1c2_4%3a3.4.2-2_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/libmimelib1c2_4%3a3.4.2-2_i386.deb (--unpack):
trying to overwrite `/usr/lib/libmimelib.so.1.0.1', which is also
On Saturday 05 November 2005 02:50 pm, Ronny Standtke wrote:
Package: ksayit
Version: 4:3.4.2-2
Severity: grave
Justification: renders package unusable
KSayit crashes on startup. Here is the backtrace:
...
#3 0xb799bb6e in __gnu_cxx::__pooltrue::_M_reclaim_block ()
from
On Friday 04 November 2005 06:26 am, Xavier FACQ wrote:
Package: kdelibs4-dev
Version: 4:3.4.2-4
Severity: serious
Justification: no longer builds from source
When i try to build kopete from svn or using sources from apt-get
source, it always failed with this error :
On Friday 04 November 2005 09:10 pm, Josh Metzler wrote:
It looks to me like the problem might be that kis_filter.h and
kis_filter_registry.h include each other. As far as I can tell,
kis_filter_registry.h doesn't have any reason to include kis_filter.h, so
I would try removing that include
On Friday 04 November 2005 09:36 am, Daniel Schepler wrote:
Package: koffice
Version: 1:1.4.2-2
Severity: serious
From my pbuilder build log:
...
if /bin/sh ../../libtool --silent --mode=compile --tag=CXX g++
-DHAVE_CONFIG_H -I. -I../../../krita/ui -I../..
On Sunday 16 October 2005 10:23 am, [EMAIL PROTECTED] wrote:
Package: koffice
Version: 1:1.3.5-5
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of koffice_1:1.3.5-5 on ska by sbuild/m68k 69
Build started at 20051014-1604
[...]
** Using
This is just a quick note to let you know that I rebuilt knutclient locally
in a clean sid pbuilder chroot, and it built fine. I have not yet upgraded
my desktop computer to kde 3.4.2, so I haven't yet tested the new package.
If knutclient hasn't been uploaded for the transition yet when I do
This is a followup to bug #327231, but maybe should be a separate bug
report. I tried rebuilding filelight against the latest kdelibs using
gcc-4.0, and it fails with this error:
scanmanager.h:56: error: 'void ScanManager::startPrivate(const QString)' is
private
scanmanager.h:81: error:
Package: kdebase-data
Version: 4:3.4.2-1
Severity: serious
A user reported in #debian-kde that his kcontrol was empty of modules. I lead
him through downgrading kdebase-data to 4:3.3.2-1 and that fixed it. I then
reproduced by upgrading kdebase-data to 4:3.4.2-1 on a stock sid system (all
of
reassign 325092 kdelibs4
merge 320581 325092
thanks
On Thursday 25 August 2005 11:06 pm, David Hill wrote:
Package: kmail
Version: 4:3.3.2-3
Severity: grave
Justification: renders package unusable
GDB=
Received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1244882720 (LWP
On Wednesday 24 August 2005 06:10 am, Klaus Huber wrote:
# apt-get install juk
...
The following packages have unmet dependencies:
juk: Depends: libtunepimp-bin but it is not going to be installed
E: Broken packages
This is expected. It is due to the gcc 4.0 transition currently taking
On Wednesday 24 August 2005 01:50 pm, Francesco Paolo Lovergine wrote:
Package: kdebase-dev
Version: 4:3.3.2-1
Severity: grave
Dunno if you are waiting for c++ transition completion, anyway current
sid version is not installable. Any reason to not move the experimental
one in the sid pool?
reassign 324147 kdelibs-data
severity 324147 serious
merge 323747 324147
thanks
On Saturday 20 August 2005 10:38 am, Xabier Villar wrote:
Package: kde
Severity: important
After an upgrade, KDE menus dissapear, and are not regenerated even if I
rename .kde. Menu items in kcontrol and
As far as I understand, #318979 caused xorg-x11 to FTBFS on sparc because it
included asm-sparc/fbio.h which used __user but failed to include
linux/compiler.h where __user was defined. This was apparently fixed in
linux-kernel-headers_2.6.13+0rc3-1. So, #318979 is no longer a problem.
What
On Monday 11 April 2005 07:08 am, Riku Voipio wrote:
On Mon, Apr 11, 2005 at 09:48:26AM +0100, Neil Williams wrote:
Loading kiconedit from the menu causes a SIGSEGV as soon
as the window tries to display. The window then closes
and the KDE crash handler appears.
unreproducible on sarge.
On Wednesday 23 March 2005 05:33 pm, Bartosz Fenski aka fEnIo wrote:
On Wed, Mar 23, 2005 at 11:09:17PM +0100, Joerg Jaspert wrote:
Usually NEW-queue was handled by the date of first upload of some
package. After tracking of debian-bugs and/or debian-wnpp mailing
lists last days I can
On Wednesday 26 January 2005 05:56 pm, Bill Allombert wrote:
Package: kdm
Version: 4:3.3.1-4
Severity: serious
Justification: Policy 10.7.3
Hello KDE maintainers,
kcontrol overwrite the conffile /etc/kde3/kdm/kdmrc without
respecting comment and formating. For example if you start with
22 matches
Mail list logo
