Processed: tagging sarge
Processing commands for [EMAIL PROTECTED]: > tags 282418 + sarge Bug#282418: kaudiocreator: fails on extracting tracks There were no tags set. Tags added: sarge > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#283349: kicker: randomly chrashes (often while updating debian via aptitude)
Package: kicker Version: 4:3.3.1-2 Severity: important While updating my debian-system via aptitude, kicker often krashes. This seems to happen since a few months. Maybe it has somethin todo with KSIM which is also running permanently. Here is the output of the crashmanager: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1095731232 (LWP 2142)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #3 0x41b4e952 in CpuView::updateView () from /usr/lib/kde3/ksim_cpu.so #4 0x41b4d628 in CpuView::qt_invoke () from /usr/lib/kde3/ksim_cpu.so #5 0x40bd952c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #6 0x40bd9354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0x40f1927b in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #8 0x40bfad42 in QTimer::event () from /usr/lib/libqt-mt.so.3 #9 0x40b7cbcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #10 0x40b7c1ce in QApplication::notify () from /usr/lib/libqt-mt.so.3 #11 0x40721da3 in KApplication::notify () from /usr/lib/libkdecore.so.4 #12 0x40b6c405 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #13 0x40b25c4b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #14 0x40b8ef28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #15 0x40b8edd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #16 0x40b7ce21 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #17 0x415733f7 in kdemain () from /usr/lib/libkdeinit_kicker.so #18 0x4001b8a6 in kdeinitmain () from /usr/lib/kde3/kicker.so #19 0x0804cbb6 in ?? () #20 0x0001 in ?? () #21 0x08083cf8 in ?? () #22 0x0001 in ?? () #23 0x08084137 in ?? () #24 0x in ?? () #25 0x in ?? () #26 0x1f80 in ?? () #27 0x in ?? () #28 0x in ?? () #29 0x in ?? () #30 0x in ?? () #31 0x in ?? () #32 0x in ?? () #33 0x in ?? () #34 0x in ?? () #35 0x in ?? () #36 0x in ?? () #37 0x in ?? () #38 0x in ?? () #39 0x in ?? () #40 0x in ?? () #41 0x in ?? () #42 0x in ?? () #43 0x in ?? () #44 0x08083660 in ?? () #45 0x in ?? () #46 0x in ?? () #47 0x in ?? () #48 0x in ?? () #49 0x in ?? () #50 0x in ?? () #51 0x in ?? () #52 0x4101f620 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #53 0x in ?? () #54 0x in ?? () #55 0x in ?? () #56 0x in ?? () #57 0x8000 in ?? () #58 0x412f6da4 in mallopt () from /lib/tls/libc.so.6 #59 0x in ?? () #60 0x in ?? () #61 0x in ?? () #62 0x in ?? () #63 0x in ?? () #64 0x in ?? () #65 0x0805a3d0 in ?? () #66 0x0010 in ?? () #67 0x413ba940 in __after_morecore_hook () from /lib/tls/libc.so.6 #68 0x413b9fcc in ?? () from /lib/tls/libc.so.6 #69 0x413ba940 in __after_morecore_hook () from /lib/tls/libc.so.6 #70 0x0001 i
Processed: Update and some tests on the kdelibs upgrade problem
Processing commands for [EMAIL PROTECTED]: > reassign 183702 kdelibs4 Bug#183702: ftp.debian.org: dist-upgrade triggers massive kde uninstall Bug reassigned from package `kdelibs4-dev' to `kdelibs4'. > # the severity may be debatable, but I prefer to inflate it for > # practical reasons (i.e. ensure that it is tracked closely) > severity 183702 serious Bug#183702: ftp.debian.org: dist-upgrade triggers massive kde uninstall Severity set to `serious'. > tags 183702 patch Bug#183702: ftp.debian.org: dist-upgrade triggers massive kde uninstall Tags were: help sid Tags added: patch > tags 183702 - sid Bug#183702: ftp.debian.org: dist-upgrade triggers massive kde uninstall Tags were: patch help sid Tags removed: sid > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#183702: Update and some tests on the kdelibs upgrade problem
reassign 183702 kdelibs4
# the severity may be debatable, but I prefer to inflate it for
# practical reasons (i.e. ensure that it is tracked closely)
severity 183702 serious
tags 183702 patch
tags 183702 - sid
thanks
Hi.
We have done some tests here on the BSP regarding the KDE upgrade
problems. There are still some, allthough they are much smaller
than mentioned at the beginning of the bug report. It is definetly
a good idea to update apt(itude) to sarge before attempting a
dist-upgrade but this doesn't solve all the problems.
Especially apt-get still gets confused by the kdelibs4 <-> kdelibs <->
kdelibs3 relations (kdelibs{,3,4}-bin is similar). I would suggest
going for the meta-package solution proposed earlier in the bug report.
We have created a kdelibs3 and a kdelibs3-bin package with equivs that
just depend on kdelibs4(-bin) (>= 4:3.2). That seemed to resolve all the
problems with apt-get, however we haven't tested all the possible
combinations of woody/sarge apt-get/aptitude (yet).
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
Where is kalyxo ? :(
Kalyxo source seems to be dead :( When i go to kalyxo.org, i've got freedesktop web site, what's happening? Cedric.
Bug#183702: Update and some tests on the kdelibs upgrade problem
On Sun, Nov 28, 2004 at 04:28:00PM +0100, Frank Lichtenheld wrote:
> Especially apt-get still gets confused by the kdelibs4 <-> kdelibs <->
> kdelibs3 relations (kdelibs{,3,4}-bin is similar). I would suggest
> going for the meta-package solution proposed earlier in the bug report.
The problem with creating kdelibs3 metapackage, is that it leaves kde2
packages depending on kdelibs3 still on the system. And unsuprinsgly
they will no longer work, since the actual libs are gone...
> We have created a kdelibs3 and a kdelibs3-bin package with equivs that
> just depend on kdelibs4(-bin) (>= 4:3.2). That seemed to resolve all the
> problems with apt-get, however we haven't tested all the possible
> combinations of woody/sarge apt-get/aptitude (yet).
Did you check if packages depending on kdelibs3 where still installed
on the system after upgrade?
Re: Where is kalyxo ? :(
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 28 November 2004 17:15, Bellegarde Cédric wrote: > Kalyxo source seems to be dead :( > When i go to kalyxo.org, i've got freedesktop web site, what's happening? Kalyxo website is hosted on one of the Freedesktop machine. And AFAIK, Freedesktop has been down since the beginning of week due to a hacking/compromising of their server. ATM, I see this message on Kalyxohomepage : " Back soon... Due to some server issues the website and our archive are not available. Thank you for your understanding. The Kalyxo team. " - -- Damien Raude-Morvan / DrazziB GPG : 0x85C79389 (new!) WWW : www.drazzib.com ICQ : 68119943 TEL : (+33) 06 08 80 36 98 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBqfvtyIFXyIXHk4kRAolOAJ9Q4q2ANb3V1Xljt7JWIeeYd9r7gwCfUMus fGSF/LJxGzp/iMiZ5D9cb0M= =Y6xH -END PGP SIGNATURE-
Bug#283404: kopete: doesn't ask for passphrase -> can't decode encrypted messages
Package: kopete
Version: 4:3.3.1-2
Severity: normal
While I can send encrypted messages to my partner (who uses kopete
0.9.0) and he can decrypt them, I cannot decrypt his messages.
All I get is
"This message is encrypted."
and kopete never ever asks for my passphrase.
I assigned my key to myself and my correspondend's key to his contact,
yet I'm never asked for any passphrase.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-ac12
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=locale: Cannot set
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Versions of packages kopete depends on:
ii kdelibs4 4:3.3.1-1 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libfam0c102 2.7.0-6client library to control the FAM
ii libgadu3 1:1.5-4Gadu-Gadu protocol library - runti
ii libgcc1 1:3.4.3-1 GCC support library
ii libglib1.21.2.10-9 The GLib library of C routines
ii libgtk1.2 1.2.10-17 The GIMP Toolkit set of widgets fo
ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library
ii libidn11 0.5.2-3GNU libidn library, implementation
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpcre3 4.5-1.1Perl 5 Compatible Regular Expressi
ii libpng12-01.2.8beta5-2 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v
ii libsm64.3.0.dfsg.1-8 X Window System Session Management
ii libstdc++51:3.3.5-2 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 libxi64.3.0.dfsg.1-8 X Window System Input extension li
ii libxml2 2.6.11-5 GNOME XML library
ii libxrender1 0.8.3-7X Rendering Extension client libra
ii libxslt1.11.1.8-5XSLT processing library - runtime
ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
ii xmms 1.2.10-1.3 Versatile X audio player that look
ii zlib1g1:1.2.2-3 compression library - runtime
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "[EMAIL PROTECTED]"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Re: Where is kalyxo ? :(
* Damien Raude-Morvan [Sun, 28 Nov 2004 17:25:12 +0100]: > Back soon... archive.kalyxo.org has been set up by Peter Rockai, and maintainers have been asked to upload their packages there. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The easy way is the wrong way, and the hard way is the stupid way. Pick one.
Re: Where is kalyxo ? :(
> > Kalyxo source seems to be dead :( > > When i go to kalyxo.org, i've got freedesktop web site, what's happening? > > Kalyxo website is hosted on one of the Freedesktop machine. And AFAIK, > Freedesktop has been down since the beginning of week due to a > hacking/compromising of their server. /.../ freedesktop.org administration hasn't taken the necessary actions to bring up our stuff again. We're currently in the progress of moving to elsewhere. The new lines for /etc/apt/sources.list are: deb http://archive.kalyxo.org/kalyxo/ staging main deb http://archive.kalyxo.org/kalyxo/ experimental main Please note that the archive has to be repopulated, so not all packages are there yet. Thanks for your patience and understanding, :) */ Christoffer Sawicki <[EMAIL PROTECTED]>
Bug#283404: kopete: doesn't ask for passphrase -> can't decode encrypted messages
* Ralf Hildebrandt [Sun, 28 Nov 2004 20:54:31 +0100]: > Package: kopete > Version: 4:3.3.1-2 > Severity: normal > While I can send encrypted messages to my partner (who uses kopete > 0.9.0) and he can decrypt them, I cannot decrypt his messages. > All I get is > "This message is encrypted." > and kopete never ever asks for my passphrase. > I assigned my key to myself and my correspondend's key to his contact, > yet I'm never asked for any passphrase. can't reproduce here. do you have the appropriate settings in: kopete -> settings menu -> configure plugins -> cryptography -> "Do not ask for the passphrase?" (otherwise, a running gnupg-agent should take care of asking it). -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: Oasis - Oasis - 12 - Champagne Supernova If you think nobody cares if you're alive, try missing a couple of car payments. -- Earl Wilson
