Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...
On April 13, 2009 11:14:12 Lennart Sorensen wrote: That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. This is what I've done for a long time (changing the kernel in question each time, obviously). Why not use module-assitant? I sure didn't test that old way of doing it when I rewrote the build scripts. I used module-assistant and a hacked up version of linux-modules-nonfree-2.6 and both worked. I did not test make-kpkg or doing it manually (which I stopped doing years ago when I discovered module-assistant). I guess I'll switch to module-assistant - not a problem. But as was pointed out elsewhere, it might be best to make the requirement explicit. Cheers, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: Another build failure...
My build (180.44-1) also failed here: dh_installdocs dh_installmodules dh_installchangelogs dh_installmodules dh_strip dh_compress dh_fixperms dh_installdeb dh_gencontrol -- -v dpkg-gencontrol: unknown option `-v' Usage: dpkg-gencontrol [option ...] Options: -ppackage print control file for package. -ccontrolfile get control info from this file. -lchangelogfileget per-version info from this file. -Fchangelogformat force change log format. -vforceversion set version of binary package. -ffileslistfilewrite files here instead of debian/files. -Ppackagebuilddir temporary build dir instead of debian/tmp. -nfilename assume the package filename will be filename. -O write to stdout, not .../DEBIAN/control. -is, -ip, -isp, -ips deprecated, ignored for compatibility. -Dfield=valueoverride or add a field and value. -Ufieldremove a field. -Vname=value set a substitution variable. -Tvarlistfile read variables here, not debian/substvars. -h, --help show this help message. --versionshow the version. dh_gencontrol: dpkg-gencontrol returned exit code 2 make: *** [binary-modules] Error 1 --- I simply edited debian/rules to change dh_gencontrol -- -v$(VERSION) into dh_gencontrol -- $(VERSION). Seems to work... Hopefully these little glitches can be fixed up soon. Thanks, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: Another build failure...
On April 12, 2009 13:36:36 Sven Joachim wrote: Only because $(VERSION) is empty for you, and that is the problem. How did you try to build the module? I tried: cd /usr/src/modules/nvidia-kernel (after unpacking /usr/src/nvidia-kernel.tar.bz2) KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules This is what I've done for a long time (changing the kernel in question each time, obviously). Hope that helps, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: Another build failure...
On April 12, 2009 14:10:13 Sven Joachim wrote: I see. The VERSION variable is supposed to be set by including /usr/share/modass/include/generic.make, and you apparently do not have module-assistant installed, do you? Probably nvidia-kernel-source should stop recommending kernel-package and just depend on module-assistant like every other $module-source package does. Correct, I don't have module-assistant installed. signature.asc Description: This is a digitally signed message part.
Bug#501990: gwenview: Gwenview crashes when trying Copy to from a tar.gz file
severity 501990 normal
tags 501990 experimental
stop
Unless I'm misreading, there is no data loss since the tar.gz is not
deleted nor its contents affected. The problem is that files can't be
extracted from tar.gz using Gwenview.
Correct me if I'm wrong...
Thanks,
Christopher Martin
On October 12, 2008 10:03:54 Saulo Soares de Toledo wrote:
Package: gwenview
Version: 4:4.1.2-1
Severity: grave
Justification: causes non-serious data loss
1) Open a tar.gz file in Dolphin
2) Open with a image file inside this tar.gz with Gwenview, here it's
possible navigate at image files
3) Select Copy to option, the window to copy files will open
4) When try change the folder to Home or other directory, Gwenview
crashes. I don't know exactily this last pass, but will crash.
The backtrace:
Aplicativo: Gwenview (gwenview), sinal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb5e8a6c0 (LWP 4272)]
[KCrash handler]
#6 0xb7f97424 in __kernel_vsyscall ()
#7 0xb68e4640 in raise () from /lib/i686/cmov/libc.so.6
#8 0xb68e6018 in abort () from /lib/i686/cmov/libc.so.6
#9 0xb6b506cd in qt_message_output (msgType=QtFatalMsg,
buf=0xbf9ad570 ASSERT: \!isEmpty()\ in file
#/usr/include/qt4/QtCore/qlist.h, line 252) at
global/qglobal.cpp:2102 #10 0xb6b50796 in qFatal (msg=0xb6c98438
ASSERT: \%s\ in file %s, line #%d)
at global/qglobal.cpp:2303
#11 0xb6b50825 in qt_assert (assertion=0xb769cdd7 !isEmpty(),
file=0xb769c7d4 /usr/include/qt4/QtCore/qlist.h, line=252)
at global/qglobal.cpp:1872
#12 0xb7657018 in KDirOperator::Private::_k_slotSelectionChanged (
this=0x9019440) at /usr/include/qt4/QtCore/qlist.h:252
#13 0xb765eb9f in KDirOperator::qt_metacall (this=0x900afe8,
_c=QMetaObject::InvokeMetaMethod, _id=56, _a=0xbf9af6d8)
at
/tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/kdiroperator.moc:
226 #14 0xb6c5cbd0 in QMetaObject::activate (sender=0x915b120,
from_signal_index=4, to_signal_index=4, argv=0xbf9af6d8)
at kernel/qobject.cpp:3031
#15 0xb6c5d952 in QMetaObject::activate (sender=0x915b120,
m=0xb761bff0, local_signal_index=0, argv=0xbf9af6d8) at
kernel/qobject.cpp:3101 #16 0xb737dbe9 in
QItemSelectionModel::selectionChanged (this=0x915b120,
[EMAIL PROTECTED], [EMAIL PROTECTED])
at .moc/release-shared/moc_qitemselectionmodel.cpp:144
#17 0xb7385770 in QItemSelectionModel::emitSelectionChanged
(this=0x915b120, [EMAIL PROTECTED], [EMAIL PROTECTED])
at itemviews/qitemselectionmodel.cpp:1454
#18 0xb7385a76 in QItemSelectionModel::select (this=0x915b120,
[EMAIL PROTECTED], command={i = -1080363004})
at itemviews/qitemselectionmodel.cpp:1013
#19 0xb7380820 in QItemSelectionModel::select (this=0x915b120,
[EMAIL PROTECTED], command={i = -1080362952})
at itemviews/qitemselectionmodel.cpp:901
#20 0xb7664007 in KDirOperatorDetailView::currentChanged
(this=0x90a6d10, [EMAIL PROTECTED], [EMAIL PROTECTED])
at
/tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:136 #21
0xb73319fc in QAbstractItemView::qt_metacall (this=0x90a6d10,
_c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf9af9b8) at
.moc/release-shared/moc_qabstractitemview.cpp:227
#22 0xb7374e2a in QTreeView::qt_metacall (this=0x90a6d10,
_c=QMetaObject::InvokeMetaMethod, _id=51, _a=0xbf9af9b8)
at .moc/release-shared/moc_qtreeview.cpp:121
#23 0xb765418a in KDirOperatorDetailView::qt_metacall
(this=0x90a6d10, _c=QMetaObject::InvokeMetaMethod, _id=51,
_a=0xbf9af9b8) at
/tmp/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kfile/moc_kdiroperatord
etailview_p.cpp:62 #24 0xb6c5cbd0 in QMetaObject::activate
(sender=0x915b120,
from_signal_index=5, to_signal_index=5, argv=0xbf9af9b8)
at kernel/qobject.cpp:3031
#25 0xb6c5d952 in QMetaObject::activate (sender=0x915b120,
m=0xb761bff0, local_signal_index=1, argv=0xbf9af9b8) at
kernel/qobject.cpp:3101 #26 0xb737db99 in
QItemSelectionModel::currentChanged (this=0x915b120, [EMAIL PROTECTED],
[EMAIL PROTECTED])
at .moc/release-shared/moc_qitemselectionmodel.cpp:151
#27 0xb737dd3d in QItemSelectionModel::setCurrentIndex
(this=0x915b120, [EMAIL PROTECTED], command={i = -1080362272})
at itemviews/qitemselectionmodel.cpp:1082
#28 0xb732fb8a in QAbstractItemView::mousePressEvent (this=0x90a6d10,
event=0xbf9b04ac) at itemviews/qabstractitemview.cpp:1470
#29 0xb7373527 in QTreeView::mousePressEvent (this=0x90a6d10,
event=0xbf9b04ac) at itemviews/qtreeview.cpp:1761
#30 0xb766404f in KDirOperatorDetailView::mousePressEvent
(this=0x90a6d10, event=0xbf9b04ac)
at
/tmp/buildd/kde4libs-4.1.2/kfile/kdiroperatordetailview.cpp:122 #31
0xb6ec17a9 in QWidget::event (this=0x90a6d10, event=0xbf9b04ac) at
kernel/qwidget.cpp:7159
#32 0xb71f4ca3 in QFrame::event (this=0x90a6d10, e=0xbf9b04ac)
at widgets/qframe.cpp:651
#33 0xb728b3cf in QAbstractScrollArea::viewportEvent (this=0x90a6d10,
e=0x6
Bug#488637: NMU for xine-plugin
Hello, I've prepared a NMU for xine-plugin, which updates it to the long-ago released 1.0.1 version, and fixes the crashes with Iceweasel 3 and Epiphany, as far as I can tell. Please test this and let me know if it makes a difference for you. http://people.debian.org/~chrsmrtn The file 'debian.diff' contains the changes within the debian directory only; look at the .diff.gz for the source changes against upstream release 1.0.1. I've done a little more housecleaning than is normally encouraged for a NMU, so Darren, let me know what you think! I'd like to get a bit of feedback before uploading. Thanks, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#429466: gwenview crashed on menu entering
Hello, Thanks for the report. Could you explain exactly what you mean by the Modules menu? Do you mean the list of KIPI plugins for activation/deactivation, or something else? Also, please update your libkipi0 and kipi-plugins to the versions available in unstable, and tell me if the problem is affected. Thanks, Christopher Martin On June 18, 2007 05:39:48 Paul Romanchenko wrote: Package: gwenview Version: 1.4.1-1+b2 Severity: grave Justification: renders package unusable When clicking Modules menu, gwenview crashed. Console error text follows: terminate called after throwing an instance of 'Exiv2::Error' what(): MakerTagInfo registry full KCrash: Application 'gwenview' crashing... Stack trace follows (from kde crash dialog): (no debugging symbols found) Using host libthread_db library /lib/i686/cmov/libthread_db.so.1. (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) [Thread debugging using libthread_db enabled] [New Thread -1237096752 (LWP 5380)] (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) 0xe410 in ?? () #0 0xe410 in ?? () #1 0xbf9129a8 in ?? () #2 0xb7df0ff4 in ?? () from /lib/i686/cmov/libc.so.6 #3 0xbf912994 in ?? () #4 0xb7d42760 in nanosleep () from /lib/i686/cmov/libc.so.6 #5 0xb7d425af in sleep () from /lib/i686/cmov/libc.so.6 #6 0xb71e9117 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4 #7 0xb71ff127 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #8 0xe420 in ?? () #9 0x0006 in ?? () #10 0x0033 in ?? () #11 0xc02a in ?? () #12 0x007b in ?? () #13 0xbf91007b in ?? () #14 0xb7df0ff4 in ?? () from /lib/i686/cmov/libc.so.6 #15 0xbf914fec in ?? () #16 0xbf914f4c in ?? () #17 0xbf914f34 in ?? () #18 0x1504 in ?? () #19 0x0006 in ?? () #20 0x1504 in ?? () #21 0x in ?? () -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-rc3-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages gwenview depends on: ii kdelibs4c2a 4:3.5.7.dfsg.1-1 core libraries and binaries for al ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libaudio2 1.9-2 The Network Audio System (NAS). (s ii libc6 2.5-7GNU C Library: Shared libraries ii libexiv2-0 0.14-1 EXIF/IPTC metadata manipulation li ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libgcc1 1:4.2-20070516-1 GCC support library ii libice6 1:1.0.3-1X11 Inter-Client Exchange library ii libidn110.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-10The Independent JPEG Group's JPEG ii libkipi0 0.1.5-1 library for apps that want to use ii libmng1 1.0.8-1 Multiple-image Network Graphics li ii libpng12-0
Bug#392959: ssmtp uninstallable on i386
Package: ssmtp Severity: serious Version: 2.61-9 The latest ssmtp was built against an obsolete libgnutls on i386 (presumably the arch on which it was uploaded). ssmtp/i386 unsatisfiable Depends: libgnutls11 (= 1.0.16) ... and consequently can't be installed on a Sid system that doesn't have this old library left over. Please have ssmtp rebuilt against libgnutls13. Thanks, Christopher Martin pgp7gWPLdGWg1.pgp Description: PGP signature
Bug#392245: save doesnt work
tags 392245 unreproducible severity 392245 important notfound 392245 4:3.5.5a-1 stop I can't reproduce this using an up-to-date system. Unless it can be confirmed to happen on something recent, I don't think it should be an RC release blocker. Let us know what you find. Thanks, Christopher Martin On Tuesday 10 October 2006 17:32, Rafal Maj wrote: Package: kmenuedit Version: 3.5.3-2 Severity: grave Save function do not work, making the kmenueditor totally useless. The Updating system configuration shows up as usuall, it takes it time, it reaches 100% and then closes (no error report) but then chnages are not visible in KDE Menu. Although one thing do work - editing shorcut keys. ii kmenuedit 3.5.3-2 -- Rafał Maj www.Raf256.org C++ pgp92nzmLFUbG.pgp Description: PGP signature
Bug#384106: Kopete crashes whole system
Hello, It looks like KDE 3.5.5 will have Kopete 0.12.x, a big update over the version shipped in KDE 3.5.4. Could you please test whether that version of Kopete still suffers from the bug? It's currently available unofficially from http://manfred.cp69.de/debian. I'd really appreciate it if those affected could give it a try and let us know if the problem still happens. Thanks, Christopher Martin Bastian Venthur wrote: Package: kopete Version: 4:3.5.4-2 Severity: critical The latest version of kopete regulary hangs the whole system. I don't know how to reproduce this bug, but it appears randomly every few days. If it happens, kde hangs completely, leaving the user unable to switch to a different terminal or even to restart X. The mouse is not reacting anymore and the system does not respond on any keystrokes. pgpUXRSz3Fgy4.pgp Description: PGP signature
Bug#388092: kdesdk: FTBFS: Build-Depends dependency for kdesdk cannot be satisfied because no available versions of package libsvn0-dev can satisfy version requirements
reopen 388092 stop I'm wrong. It looks like we'll have to switch over to libdb4.4-dev, and kdepim will need a rebuild against the new libpisock9. Thanks for the tip. Note to self: get more sleep. On Tuesday 19 September 2006 17:33, Christopher Martin wrote: kdesdk: FTBFS: Build-Depends dependency for kdesdk cannot be satisfied because no available versions of package libsvn0-dev can satisfy version requirements Works fine on i386. This must be arch-specific uninstallability. On many architectures a lot of KDE packages are currently unbuildable, not because of a problem in the module, but due to something down the chain needing a rebuild to fix installability. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#284699: Upgrade
On Sunday 17 September 2006 03:59, Filipus Klutiero wrote: severity 284699 serious found 284699 4:3.5.4-2 thanks From what I understood, upstream KDE completely ignores licensing questions regarding non-source files beyond distributability. Other icons from crystalsvg seem non-free, such as icons for Thunderbird, Adobe Reader, Realplayer. A full inspection should be done. Yikes. Well, short of a full review, at least the icons which originate from Mozilla and non-free projects should be examined. Would you be willing to help do this, find replacement icons, etc.? The rest of the team is pretty much swamped right now, so help would be much appreciated, especially with the Etch freeze coming. I have kde-svn access, so I can ensure that good fixes make 3.5.5. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385194: closed by Christopher Martin [EMAIL PROTECTED] (reply to Christopher Martin [EMAIL PROTECTED]) (Re: Bug#385194: kdebase source is missing debian/debian-kde_default.png)
Hi, The file is uuencoded in 21_default_background_image.diff.uu, so when the build process applies the patches, the file is created. So it is present to be copied into the .debs when they're built. Cheers, Christopher Martin On Wednesday 30 August 2006 20:29, Sean Meiners wrote: What version did 'apt-get source kdebase' get you? For me it gets: Get:1 ftp://ftp.us.debian.org unstable/main kdebase 4:3.5.4-2 (dsc) [1810B] Get:2 ftp://ftp.us.debian.org unstable/main kdebase 4:3.5.4-2 (tar) [28.2MB] Get:3 ftp://ftp.us.debian.org unstable/main kdebase 4:3.5.4-2 (diff) [1789kB] And when unpacked ' grep -r debian-kde_default debian/*' finds several references to the file, but 'ls debian/debian-kde_default.png' finds nothing. On Wednesday 30 August 2006 17:04, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #385194: kdebase source is missing debian/debian-kde_default.png, which was filed against the kdebase package. It has been closed by Christopher Martin [EMAIL PROTECTED] (reply to Christopher Martin [EMAIL PROTECTED]). Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Christopher Martin [EMAIL PROTECTED] (reply to Christopher Martin [EMAIL PROTECTED]) by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384106: crashes whole system
On Monday 21 August 2006 17:40, Bastian Venthur wrote: Package: kopete Version: 4:3.5.4-2 Severity: critical The latest version of kopete regulary hangs the whole system. I don't know how to reproduce this bug, but it appears randomly every few days. If it happens, kde hangs completely, leaving the user unable to switch to a different terminal or even to restart X. The mouse is not reacting anymore and the system does not respond on any keystrokes. Sometimes it is possible to ssh into the box from another box and kill kopete which instantly resurrects the system. But if you wait too long, the box does not even answer to ping requests and you have to restart the hard way. After running Kopete for a while, does it consume a more than reasonable amount of memory? When it finally goes berserk, does it eat CPU cycles, suddenly eat memory, etc.? Also, are you always using a certain protocol when the problem happens, any fancy plugins, etc.? Thanks, Christopher Martin pgp5yOLXNtgdh.pgp Description: PGP signature
Bug#384325: libqt3-mt: Floating point exception in QPaintDevice::~QPaintDevice
On Wednesday 23 August 2006 10:11, Jean Parpaillon wrote: Package: libqt3-mt Version: 3:3.3.6-3 Severity: grave Justification: renders package unusable All apps using libqt3-mt end on a flaoting point exception. After compiling with debug an tracing amarok, it seems to fail in QPaintDevice::~QPaintDevice: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread -1476536640 (LWP 8061)] 0x4129318d in QPaintDevice::~QPaintDevice () from /usr/lib/libqt-mt.so.3 Strange that such a problem would only be reported by one person. You mention amarok, but also that all apps are afflicted. When you say all Qt apps end on a SIGFPE, do you mean that instead of quitting properly they blow up? Or that they just don't run? I don't suppose that you could attach a full backtrace? Does downgrading to libqt3-mt 3.3.6-2 from testing/etch make any difference? I'd appreciate more information; otherwise, there isn't much I can do. Cheers, Christopher Martin pgpUyYiDUQDCK.pgp Description: PGP signature
Bug#342545: qt-x11-free FTBFS
reassign 342545 libgcc2 stop On Thursday 10 August 2006 00:25, Steve Langasek wrote: It hasn't been, because I can't see any way that libglu1-mesa could have anything to do with the failure in question. libglu1-mesa should not be a dependency of the tool that's failing with SIGBUS in the build log. I would suggest that someone should investigate this further and get a clear answer on the nature of the bug, because I really don't buy that libgcc skew is to blame. Fair enough, but before I take off for the weekend, I'm sending this report back to libgcc2, since it seems to have been established long ago that this isn't a Qt bug, and it really should be assigned to something in the toolchain. I note that, for a time, the problem was thought to be in glibc, so perhaps the glibc team would again be worth consulting. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380370: FTBFS: arts on arm due to segmentation fault (program as)
FYI, this also appears to have broken a kdepim build: http://buildd.debian.org/fetch.php?pkg=kdepimver=4%3A3.5.3-3arch=armstamp=1153287934file=logas=raw Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342545: qt-x11-free FTBFS
On Sunday 30 July 2006 17:50, Marc 'HE' Brockschmidt wrote: Discussion in IRC showed that doko suspects libgcc2 deps in one of the build-deps to be the problem. A quick check revealed that libglu1-mesa still does that, so I requested a bin-NMU. Hopefully, after that was done, a reschedule will work out. qt-x11-free was retried on hppa, but failed again. However, I see no evidence that a bin-NMU of libglu1-mesa was ever done, so this isn't shocking. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381578: kdelibs4c2a: katepart crashes when pressing Return insider doxygen comments
severity 381578 important stop I don't think that it's a data-loss issue more than any other crash in an editor, browser, etc., so I don't think it's truly RC. BTW, I really appreciate your efforts to forward bugs upstream. Cheers, Christopher Martin On Saturday 05 August 2006 11:30, Andreas Pakulat wrote: Package: kdelibs4c2a Version: 4:3.5.4-3 Severity: critical Justification: causes serious data loss Hi, just found this out. Creating a doxygen comment block (beginning with /**) inside kate and then pressing Return crashes Kate with the following backtrace: #0 0xb465b9ce in KateTextLine::stringAtPos (this=0x9fe72e0, pos=4294967295, [EMAIL PROTECTED]) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/katetextline.cpp:196 #1 0xb46e2b16 in KateCSAndSIndent::handleDoxygen (this=0x90823b0, [EMAIL PROTECTED]) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateautoindent.cpp:1 497 #2 0xb46e2e9c in KateCSAndSIndent::processNewline (this=0x90823b0, [EMAIL PROTECTED]) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateautoindent.cpp:1 522 #3 0xb46fb6fb in KateDocument::newLine (this=0x917cc90, [EMAIL PROTECTED], v=0x91c8b20) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/katedocument.cpp:300 1 #4 0xb47101d4 in KateViewInternal::doReturn (this=0x91c8b20) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateviewinternal.cpp :893 #5 0xb4739d93 in KateView::keyReturn (this=0x91e2e28) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateview.h:329 #6 0xb4724daa in KateViewInternal::keyPressEvent (this=0x91c8b20, e=0xbfce4b10) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateviewinternal.cpp :2507 #7 0xb470c5e8 in KateViewInternal::eventFilter (this=0x91c8b20, obj=0x91c8b20, e=0xbfce4b10) at /home/sid-user/kdelibs/kdelibs-3.5.4/./kate/part/kateviewinternal.cpp :2439 #8 0xb680d17a in QObject::activate_filters (this=0x91c8b20, e=0xbfce4b10) at kernel/qobject.cpp:903 #9 0xb680d1f8 in QObject::event (this=0x91c8b20, e=0xbfce4b10) at kernel/qobject.cpp:735 #10 0xb684448a in QWidget::event (this=0x91c8b20, e=0xbfce4b10) at kernel/qwidget.cpp:4678 #11 0xb67a5b2a in QApplication::internalNotify (this=0xbfce4ff4, receiver=0x91c8b20, e=0xbfce4b10) at kernel/qapplication.cpp:2635 This can cause data loss when one just wanted to add a comment to a file and didn't save before writing it. If you feel this is not that important please downgrade severity. I currently am unable to report this upstream, because I think it is an upstream issue, but I will do as soon as bugs.kde.org works again. Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342545: qt-x11-free FTBFS on hppa (again)
On Sunday 30 July 2006 09:18, Matthias Klose wrote: Please see http://lists.debian.org/debian-hppa/2006/05/msg0.html the binaries in qt-x11-free still depend on libgcc2, so these should be rebuilt first (and all depending ones), then we should revisit this report. If the problem persists, please reassign the report again. Sorry to be a pain; perhaps I'm just dense, but what exactly should I do? I uploaded qt-x11-free, and the hppa buildd tried to build it with g++-4.1. This failed. How does the old version of qt-x11-free depending on libgcc2 relates to the failure of the current build? Is there something else I should have done? Are there other packages that need to be rebuilt before qt-x11-free will build? If yes, then this bug should be reassigned to them. If no, then what should I do? Thanks for your help, Christopher Martin Christopher Martin writes: I'm not quite sure I understand. The build did try to use g++-4.1, and it failed. This was long ago determined to be a glibc or gcc problem, not a qt-x11-free problem, so why was it reassigned to qt-x11-free? On Saturday 29 July 2006 18:48, Matthias Klose wrote: reassign 342545 qt-x11-free thanks please make sure, that qt-x11-free is built using g++-4.1 on hppa. The binary packages still depend on libgcc2 in some way. Note, that (before the release) we need to rebuild all binaries depending on libgcc2 on hppa, so that the dependency is replaced by libgcc4. Christopher Martin writes: reopen 342545 2.3.6-15 severity 342545 grave stop Unfortunately, the qt-x11-free FTBFS on hppa has re-occurred: http://buildd.debian.org/fetch.php?pkg=qt-x11-freever=3%3A3.3 .6-3 arch=hppastamp=1153689954file=logas=raw The error is exactly the same as before: /build/buildd/qt-x11-free-3.3.6/bin/uic -L /build/buildd/qt-x11-free-3.3.6/plugins pixmapfunction.ui -o pixmapfunction.h make[4]: *** [pixmapfunction.h] Bus error -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380499: cdbs 0.4.45 simple-patchsys.mk doesn't properly distinguish patches
Package: cdbs Version: 0.4.45 Severity: critical apt-get source kdelibs, and in the top-level source directory, try: fakeroot debian/rules apply-patches Notice how debian/patches/04_am_maintainer_mode.diff is skipped because it's already applied even though it clearly isn't? There is a similarly named but different patch, debian/patches/common/04_am_maintainer_mode.diff, which is perhaps confusing CDBS. Then of course if you try: fakeroot debian/rules clean ...we get an error, since it can't unapply a patch that wasn't actually applied. This could mess up a number of KDE builds, so a quick fix would be great. CDBS 0.4.44 worked fine. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380370: FTBFS: arts on arm due to segmentation fault (program as)
Package: binutils Version: 2.17-1 Severity: serious The package 'arts' failed to build on arm, using binutils 2.17-1. Log is available at: http://buildd.debian.org/fetch.php?pkg=artsver=1.5.4-1arch=armstamp=1153922700file=logas=raw The interesting bit: /usr/lib/gcc/arm-linux-gnu/4.0.4/../../../../include/c++/4.0.4/bits/basic_string.h:278: warning: cast from 'char*' to 'std::basic_stringchar, std::char_traitschar, std::allocatorchar ::_Rep*' increases required alignment of target type g++: Internal error: Segmentation fault (program as) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. For Debian GNU/Linux specific bug reporting instructions, see URL:file:///usr/share/doc/gcc-4.0/README.Bugs. Perhaps binutils related? I'll send the report to you for now. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342545: qt-x11-free FTBFS on hppa (again)
reopen 342545 2.3.6-15 severity 342545 grave stop Unfortunately, the qt-x11-free FTBFS on hppa has re-occurred: http://buildd.debian.org/fetch.php?pkg=qt-x11-freever=3%3A3.3.6-3arch=hppastamp=1153689954file=logas=raw The error is exactly the same as before: /build/buildd/qt-x11-free-3.3.6/bin/uic -L /build/buildd/qt-x11-free-3.3.6/plugins pixmapfunction.ui -o pixmapfunction.h make[4]: *** [pixmapfunction.h] Bus error Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342545: qt-x11-free FTBFS on hppa (again)
Hi, I'm not quite sure I understand. The build did try to use g++-4.1, and it failed. This was long ago determined to be a glibc or gcc problem, not a qt-x11-free problem, so why was it reassigned to qt-x11-free? Thanks, Christopher Martin On Saturday 29 July 2006 18:48, Matthias Klose wrote: reassign 342545 qt-x11-free thanks please make sure, that qt-x11-free is built using g++-4.1 on hppa. The binary packages still depend on libgcc2 in some way. Note, that (before the release) we need to rebuild all binaries depending on libgcc2 on hppa, so that the dependency is replaced by libgcc4. Matthias Christopher Martin writes: reopen 342545 2.3.6-15 severity 342545 grave stop Unfortunately, the qt-x11-free FTBFS on hppa has re-occurred: http://buildd.debian.org/fetch.php?pkg=qt-x11-freever=3%3A3.3.6-3 arch=hppastamp=1153689954file=logas=raw The error is exactly the same as before: /build/buildd/qt-x11-free-3.3.6/bin/uic -L /build/buildd/qt-x11-free-3.3.6/plugins pixmapfunction.ui -o pixmapfunction.h make[4]: *** [pixmapfunction.h] Bus error Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342215: kmail crashes very oftenly on SPARC (other KDE apps crash too, but not so often)
Hi, Can you confirm that the crashes you reported still afflict the latest KDE 3.5.3? It's been seven months since the report, and we've had no other reports of KMail crashes on sparc since. Thanks, Christopher Martin Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on various KDE applications but the most serious, because of the frecuency in which it happens is kmail. The worst part is that, as kmail is compiled without debuging symbols, I can't debug much on what's happening, and all I have are the signals with which it dies (4 Illegal Instruction, and 11 Invalid memory reference). *** KMail got signal 11 (Crashing) KCrash: Application 'kmail' crashing... And this doesn't happen when doing something especifically. For example, if I type to fast when composing, it sometimes crashes. Also I got crashes when configuring kmail or filters. Just a moment ago konsole died with no reason, and I wasn't even doing anything with it. KCrash: Application 'konsole' crashing... This is very annoying. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342215: kmail crashes very oftenly on SPARC (other KDE apps crash too, but not so often)
severity 342215 important stop OK, until we get some reasonable confirmation that the bug is still present, I'm lowering to 'important'. Cheers, Christopher Martin On Sunday 23 July 2006 18:23, you wrote: Sorry, but can't test at this moment. To upgrade to that version, I would have to update to xorg, which is broken for SPARC. :-( On Sun, 23 Jul 2006 11:36:15 -0400, Christopher Martin [EMAIL PROTECTED] wrote: Hi, Can you confirm that the crashes you reported still afflict the latest KDE 3.5.3? It's been seven months since the report, and we've had no other reports of KMail crashes on sparc since. Thanks, Christopher Martin Since I upgraded KDE to 3.4.x, I'm getting unpleasant crashes on various KDE applications but the most serious, because of the frecuency in which it happens is kmail. The worst part is that, as kmail is compiled without debuging symbols, I can't debug much on what's happening, and all I have are the signals with which it dies (4 Illegal Instruction, and 11 Invalid memory reference). *** KMail got signal 11 (Crashing) KCrash: Application 'kmail' crashing... And this doesn't happen when doing something especifically. For example, if I type to fast when composing, it sometimes crashes. Also I got crashes when configuring kmail or filters. Just a moment ago konsole died with no reason, and I wasn't even doing anything with it. KCrash: Application 'konsole' crashing... This is very annoying. -- - Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática| '@' || 'unl.edu.ar'; Universidad Nacional| DBA, Programador, del Litoral | Administrador -
Bug#321102: data-loss still possible with kmail 3.5.2
found 321102 4:3.5.2-1 found 332473 4:3.5.2-1 found 350851 4:3.5.2-1 stop On Tuesday 16 May 2006 10:05, Bastian Venthur wrote: So here it is, someone confirmed this bug with 3.5.2 on Debian: http://bugs.kde.org/show_bug.cgi?id=104956 Quote: Bam! I had this bug right now. Using KDE 3.5.2 on Debian. Lost a whole folder of mails (thank god it was only a ML). Nevertheless this is totally uncool... Darn, I thought that perhaps it had gone away. Whoever marked this bug as found in $VERSION should upgrade this to the newest version too or remove it completely (we know this bug is open for years and there is IMHO reason to track every version-number the bug appeared). I have added the founds for this version for the sake of clarity, but it isn't necessary to mark founds for every last upload; the bug is assumed to be present by the BTS unless marked fixed. And please consider to remove KMail from testing again. There is nothing stable about losing a whole Mail-Folder. Especially when we *know* the software leads to data loss but pretend it to be stable. Perhaps a better solution would be disable dimap support in the 3.5.3 upload, and make sure that the fixed package makes Etch (which is looming). Daniel, what do you feel about this? Given that upstream appears to be unable to replicate and fix the problem, I think this might be the safest, and least bothersome (to all other KMail users) way of dealing with this issue. Cheers, Christopher Martin pgpRLsYzVQriQ.pgp Description: PGP signature
Bug#321102: KMail with RC-Bugs moved to testing?
On Tuesday 25 April 2006 02:48, Bastian Venthur wrote: I noticed KMail moving to testing, although it has grave bugs open. Was this a mistake? I always thought packages with RC Bugs don't enter testing until they're fixed? Looking at #321102, I noticed that found in version is set to various old versions but not to the current one (which is not that old BTW). If this affected the migration to testing, it would look like cheating to me in order to get the current PIM into testing at all costs. I might be biased since I'm the reporter of some of the RC-bugs, but the according upstream-bugs are still open (and still has 780 votes), so I don't see a reason to assume this bug was somehow fixed. I suggest to keep the bug open for every current version until the according upstream-bug is closed. Since this is currently the only grave bug in upstreams BTS I think the chances that upstream will forget about the bug are pretty low. Packages are allowed in to testing if the RC bug count on the version in testing is higher or equal to the RC bug count on the version in unstable. Since upstream bug reports indicated that the problems in Kmail go back to KDE 3.4 at least (hence all the found in additions), there was no point in holding kdepim 3.5 out of testing, since there was no regression. It doesn't matter if the very latest package is not marked found in for counting purposes; if the bug is open, then this is assumed to be the case. Indeed, some people strongly suspect that kdepim 3.5.2 fixed the problems, though since this isn't certain, we should keep the bugs open for now. Still, this makes letting kdepim into testing worthwhile. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358489: VPL almost useless
severity 358489 important forwarded 358489 http://bugs.kde.org/120205 tags 358489 confirmed upstream stop On Wednesday 22 March 2006 16:58, Tore Ericsson wrote: Package: quanta Version: 4:3.5.1-1 Severity: grave Justification: renders package unusable The attachment is quanta_test.html that I have used to verify some fatal behaviours of the VPL facility of Quanta 3.5.1, here described in some numbered examples. All are fully reproducible. Confirmed, and linked to the upstream bug. But VPL crashes alone don't ruin Quanta, and aren't RC. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358415: kompare: Kompare cannot parse diff output
severity 358415 important tags 358415 unreproducible stop Hello, I can't reproduce the problem. Kompare works fine here. Can anyone else test this and report? Thanks, Christopher Martin Ferenczi Viktor [EMAIL PROTECTED] wrote: Kompare displays Could not parse diff output error dialog and displays empty difference. The bug seems to be independent of the startup method used. Starting Kompare with two files from a sheel or using it from Krusader directory synchronization gives the same result. Note: I use Hungarian locale, the above error message is translated back to English. The bug seems to be unrelated to i18n issues, so I think it's not a problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348459: Downgrading KWeather bug
severity 348459 important stop Since there are workarounds and only a subset of users seem stopped, I'm downgrading to important. Christopher Martin pgp8gwIMZwFt5.pgp Description: PGP signature
Bug#353922: Bug #353922: kdepim FTBFS on alpha
Thanks for the patch. Daniel, any plans for another kdepim upload in the near future? Cheers, Christopher Martin On Wednesday 22 February 2006 17:43, Falk Hueffner wrote: this should fix it (haven't tested though). --- kdepim-3.5.1/kresources/groupwise/soap/stdsoap2.h~ 2005-09-10 10:23:46.0 +0200 +++ kdepim-3.5.1/kresources/groupwise/soap/stdsoap2.h 2006-02-22 23:41:23.0 +0100 @@ -170,7 +170,7 @@ # endif #endif -#ifdef __alpha +#ifdef __osf__ # ifndef TRU64 # define TRU64 # endif pgpgpOj023mHX.pgp Description: PGP signature
Bug#353922: kdepim FTBFS on alpha
Package: kdepim Version: 4:3.5.1-1 Severity: serious kdepim 3.5.0-4, 3.5.0-5, and 3.5.1-1 (i.e. all kdepim uploads to Sid since 3.5 was released) have all failed to build on alpha for the same reason: hundreds of warnings /build/buildd/kdepim-3.5.0/build-tree/kdepim-3.5.0/kresources/groupwise/soap/stdsoap2.cpp: In function 'int tcp_gethost(soap*, const char*, in_addr*)': /build/buildd/kdepim-3.5.0/build-tree/kdepim-3.5.0/kresources/groupwise/soap/stdsoap2.cpp:3000: error: aggregate 'hostent_data ht_data' has incomplete type and cannot be defined /build/buildd/kdepim-3.5.0/build-tree/kdepim-3.5.0/kresources/groupwise/soap/stdsoap2.cpp:3000: warning: unused variable 'ht_data' snip more warnings make[5]: *** [libgwsoap_la.all_cpp.lo] Error 1 make[5]: Leaving directory `/build/buildd/kdepim-3.5.0/build-tree/obj-alpha-linux-gnu/kresources/groupwise/soap' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/build/buildd/kdepim-3.5.0/build-tree/obj-alpha-linux-gnu/kresources/groupwise' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd/kdepim-3.5.0/build-tree/obj-alpha-linux-gnu/kresources' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/kdepim-3.5.0/build-tree/obj-alpha-linux-gnu' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/kdepim-3.5.0/build-tree/obj-alpha-linux-gnu' make: *** [debian/stamp-makefile-build] Error 2 This is holding a number of other modules out of Etch, since they build-depend on kdepim = 3.5.x. Thanks, Christopher Martin pgpX2rgUnmJIu.pgp Description: PGP signature
Bug#332473: Found in other versions too?
On Tuesday 14 February 2006 01:33, Adam Porter wrote: On Monday 13 February 2006 11:33, Debian Bug Tracking System wrote: found 350851 4:3.4.2-2 http://bugs.kde.org/show_bug.cgi?id=104956 At the bottom it says that it's also in KMail-1.9.1/KDE-3.5.0. Should it be marked found there as well? FYI, I haven't had any problems like this with KMail-1.8.3 from KDE 3.4.3, even while using it with KDE 3.5.0/1. That's OK - it's already marked as found in both KDE 3.5 and 3.4. There do seem to be more reports of the problem since KDE 3.5, interestingly, but the bug reports (KDE #104956, KDE #114163, not to mention Debian #332473) also describe the same basic problem in KDE 3.4, sadly. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349316: kaddressbook problems known upstream
forwarded 349316 http://bugs.kde.org/87163 found 349316 4:3.4.2-2 stop This would be appear to be a longstanding upstream issue. Noting the upstream version, and the bug's existence in current Etch (KDE 3.4). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352619: FTBFS: undefined reference to `XF86VidModeQueryVersion'
On Sunday 12 February 2006 19:24, Paul Brook wrote: Package: kpovmodeler Version: 4:3.5.1-2 Severity: serious Tags: patch Justification: no longer builds from source Build fails on i386 with g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o .libs/kpovmodeler main.o -L/usr/lib -L/usr/share/qt3/lib -L/usr/X11R6/lib ./.libs/libkpovmodeler.so -lm ./.libs/libkpovmodeler.so: undefined reference to `XF86VidModeQueryVersion' ./.libs/libkpovmodeler.so: undefined reference to `XF86VidModeGetModeLine' collect2: ld returned 1 exit status The missing symbols are defined in libXxf86vm.a kdegraphics certainly builds here, and the most recent upload built fine on the buildds. We depend on libxxf86vm-dev, so everything should be available. I'm not sure why you would get a different result on your machine. Are you running X.Org from experimental? Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352619: Lowering severity - kdegraphics builds fine for me...
tags 352619 unreproducible severity 352619 important stop Well, given the unreproducibility of the problem, I'm lowering this to important, until someone other than the reporter finds that kdegraphics doesn't build. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352406: qt-x11-free: Build-depens on firebird2-dev, but not on libfirebird2-classic
On Saturday 11 February 2006 12:54, Szo wrote: Package: qt-x11-free Severity: serious Justification: no longer builds from source qt-x11-free refuses to build if libfbclient1 installed, it doesn't have libgds Current firebird2-dev packages depend on libfbembed1 and libfbclient1. libfirebird2-classic has been removed from Sid and Etch. Qt does build against the latest firebird packages, since it build-depends on firebird2-dev provides libgds.so symlinks that point to libfbclient.so.1.5.2. Perhaps you've only partially upgraded firebird. This might reflect a lack of versioning in some dependency somewhere. Let us know the full names and versions of all firebird packages installed on your system, and maybe I can figure out what the matter is and why Qt doesn't build for you. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340375: Subject: kuser destroys all passwords if /etc/shadow isn't present
severity 340375 important stop Since this bug is largely fixed in Sid, but not so totally resolved that I'd want to attach a fixed tag, I think the best course of action is to lower the bug to important, but keep it open. In any case, the bug isn't a regression with respect to what's in Etch at the moment. Cheers, Christopher Martin On Saturday 17 December 2005 14:57, Christopher Martin wrote: On Tuesday 22 November 2005 20:23, Charles G Montgomery wrote: Subject: kuser destroys all passwords if /etc/shadow isn't present Package: kuser Version: 4:3.4.2-1 Severity: grave Justification: renders package unusable Hello, I forwarded the issue upstream, and a check was added for the /etc/shadow file in the KDE 3.5 branch. The kdeadmin upload that should clear NEW and be in experimental shortly contains this fix. However, as you noted yourself, this doesn't completely resolve the issue, since /etc/shadow could be present but shadow passwords still not in use. Upstream seems to be under the astonishing impression that the ability to disable the use of shadow passwords by clearing /etc/shadow from the shadow file text field in Configure KUser is intuitive and clear to users. Even the check for /etc/shadow was added reluctantly, and upstream has stated that he has no intention of adding further checks. So what to do? Having /etc/shadow but not using shadow passwords is probably a pretty rare configuration. We could add a README.Debian to warn users of this quirk, but there is no guarantee that people would read it. Any ideas, comments, suggestions from the team? Should the bug remain RC once 3.5 enters unstable? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348459: can not select any station - unknown station?
found 348459 4:3.5.0-3 tags 348459 confirmed upstream forwarded 348459 http://bugs.kde.org/103887 stop http://bugs.kde.org/116375 and http://bugs.kde.org/118458 are also probably related. On Monday 16 January 2006 22:07, Rafal Maj wrote: Package: KWeather Version: 2.1.0 Severity: grave (using KDE 3.5.0) Hi, I added KWeather applet, I go to configure, selected available station from Whether Service (like Europe-Poland-Warsaw) clicked it to be in the right-side list Select stations: it's icon updated (it worked)... but still I can not choose any station, in Display Weather Station Options Location: there is only one option in drop-down list: Unknown Station. It renders program totally useless. Same here. KWeather has always been a buggy piece of junk, but it would now appear to be completely broken. This has been reported upstream already numerous times, so it would appear that KWeather is more or less unmaintained. Honestly, I'm not motivated to work on patching it myself (though patches are welcome), so we'll just have to watch and see if it gets fixed as Etch draws near. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348025: kdelibs seem to broke MIME types for entire KDE!
tags 348025 unreproducible severity 348025 important stop I suspect someone would have noticed by now if the latest kdelibs were simply hosing their entire desktop; there must be something else going on here. First of all, I'd do a dist-upgrade to the latest unstable. The latest libdjvulibre package no longer conflicts with kdelibs-data. A nice clean purge/reinstall of kdelibs might help, again. Be sure to apt-get clean, then re-download the packages, to make sure you're not using something corrupted. Also, you might want to move your ~/.kde directory aside (say, to ~/.kde-old) and then try again; that way you can eliminate the possibility that a problem with your user settings is at the root of the problem. Cheers, Christopher Martin On Saturday 14 January 2006 02:16, Rafal Maj wrote: Package: kdelibs-data Version: 4:3.5.0-3 Severity: grave After getting rid of the libdjvulibre15 (Bug#348020) by removing it from sytem (dpkg -r --force-all) now most KDE application dont start up because not seeing MIME types. It looks a bit like: http://lists.debian.org/debian-kde/2003/12/msg00040.html but my user didnt had such file: [EMAIL PROTECTED]:~$ stat ~/.kde/share/mimelnk/application/octet-stream.desktop stat: cannot stat `/home/raf256/.kde/share/mimelnk/application/octet-stream.desktop': No such file or directory so that solution didnt worked. but I found the file: [EMAIL PROTECTED]:/usr/share/mimelnk$ file /usr/share/mimelnk/application/octet-stream.desktop /usr/share/mimelnk/application/octet-stream.desktop: UTF-8 Unicode text [EMAIL PROTECTED]:/usr/share/mimelnk$ stat /usr/share/mimelnk/application/octet-stream.desktop File: `/usr/share/mimelnk/application/octet-stream.desktop' Size: 2011Blocks: 8 IO Block: 131072 regular file Device: 30ch/780d Inode: 1603820 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2006-01-14 08:07:58.0 +0100 Modify: 2006-01-06 15:28:47.0 +0100 Change: 2006-01-14 08:08:17.0 +0100 [EMAIL PROTECTED]:/usr/share/mimelnk$ md5sum /usr/share/mimelnk/application/octet-stream.desktop dbc402c8f458f0fd99472e65795f7da0 /usr/share/mimelnk/application/octet-stream.desktop althoug removing it didnt changed anything. I tried to install --reinstall kdelibs and kdelibs-data sinc they where referencing that file, but it didnt helped either -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342163: kdeartwork-emoticons: files under kdeartwork-3.4.3/emoticons/YazooSmileys22 fail DFSG #1
tags 342163 confirmed pending found 342163 found 342163 4:3.4.3-2 found 342163 4:3.4.2-1 stop On Monday 05 December 2005 17:47, Timo Juhani Lindfors wrote: Package: kdeartwork-emoticons Version: 3.4.3 Severity: serious Justification: Policy 2.1 Hi, it looks like the files under ../kdeartwork-3.4.3/emoticons/YazooSmileys22 fail DFSG #1 because ../kdeartwork-3.4.3/emoticons/YazooSmileys22/readme.txt says snip Thanks for reporting this. Upstream was notified, and has now removed the offending artwork from their archive (the author refused to relicense it). KDE 3.5.1 will therefore be fixed. Also, when we upload 3.5.0 to experimental (and then unstable), it will not contain this artwork. The unfree artwork did not ship with Sarge, so once 3.5 percolates through the archive, the problem will disappear. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340375: Subject: kuser destroys all passwords if /etc/shadow isn't present
On Tuesday 22 November 2005 20:23, Charles G Montgomery wrote: Subject: kuser destroys all passwords if /etc/shadow isn't present Package: kuser Version: 4:3.4.2-1 Severity: grave Justification: renders package unusable Hello, I forwarded the issue upstream, and a check was added for the /etc/shadow file in the KDE 3.5 branch. The kdeadmin upload that should clear NEW and be in experimental shortly contains this fix. However, as you noted yourself, this doesn't completely resolve the issue, since /etc/shadow could be present but shadow passwords still not in use. Upstream seems to be under the astonishing impression that the ability to disable the use of shadow passwords by clearing /etc/shadow from the shadow file text field in Configure KUser is intuitive and clear to users. Even the check for /etc/shadow was added reluctantly, and upstream has stated that he has no intention of adding further checks. So what to do? Having /etc/shadow but not using shadow passwords is probably a pretty rare configuration. We could add a README.Debian to warn users of this quirk, but there is no guarantee that people would read it. Any ideas, comments, suggestions from the team? Should the bug remain RC once 3.5 enters unstable? Cheers, Christopher Martin pgpGBVlb6fHuM.pgp Description: PGP signature
Bug#336047: epos upload soon to fix packaging bugs
In a few days I intend to do a QA upload to fix the following bugs in epos: #336047: Tries to use non-essential package on purge The check for deluser is broken; bug contains the trivial fix: test -n `which deluser` gives always true... test -n `which deluser` works. #341426: epos: missing dependency on perl-modules The deluser functions used in the maintainer scripts require the presence of perl-modules. The obvious fix is to make epos depend on perl-modules. epos may not be the world's most popular package, but it is used by the kdeaccessibility module, so I'd like to make it properly installable/purgeable. Let me know if you have any objections or additions. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342545: qt-x11-free build fails
Package: libc6 Version: 2.3.5-8.1 Severity: grave Since my message to debian-glibc didn't garner a response, I'm filing this issue as a bug. -- Forwarded Message -- Subject: Fwd: Re: qt-x11-free/arts build issues Date: Friday 02 December 2005 09:03 From: Christopher Martin [EMAIL PROTECTED] To: debian-glibc@lists.debian.org Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Hello, qt-x11-free's recent failure to build on hppa is apparently due to a glibc problem that was allegedly, but not actually, fixed in 2.3.5-8, or has since returned (presumably #326581 or something else that was thought fixed by building with gcc-3.4 on hppa). The message below has a link to an example of the build failure. Cheers, Christopher Martin Please CC me on all follow-ups. -- Forwarded Message -- Subject: Re: qt-x11-free/arts build issues Date: December 1, 2005 17:32 From: LaMont Jones [EMAIL PROTECTED] To: Christopher Martin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] On Thu, Dec 01, 2005 at 05:00:45PM -0500, Christopher Martin wrote: qt-x11-free and arts both failed on hppa recently. Qt's failure would appear to be due to this: http://lists.debian.org/debian-hppa/2005/10/msg00072.html It is precisely that, a libm error that was supposedly fixed in 2.3.5-8 (but doesn't seem to have been). Hopefully we won't have to ask for this setting to be changed with every upload - is there some way of fixing this permanently? Yes. Fix glibc. lamont --- --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342474: konqueror: URL crashes Konqueror, KDE and computer
severity 342474 normal stop On Wednesday 07 December 2005 15:18, Yann Forget wrote: Package: konqueror Version: 4:3.4.2-4 Severity: critical Justification: breaks the whole system Hi, This URL crashes Konqueror, KDE and the computer. http://www.radiofrance.fr/listen.php?file=/chaines/france-culture/chroniq ues/rpmed/rpmed_20051207.ra Kaffeine didn't react too well to it here, either, but my system somehow managed to keep going... I'm afraid you'll need to provide more information about the circumstances of your problem. And if the system truly did lockup, then perhaps you should turn off any soundservers, and try again. But I suspect underneath a perhaps frozen GUI the system kept functioning. You might also want to investigate RealPlayer for Linux. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341600: kde-i18n 3.4.3-2 still depends on kdelib4c2 (not c2a)
Hello, kde-i18n 3.4.3-2 may have been rebuilt against a transitioned kdelibs, but the individual kde-i18n-foo packages still depend on kdelibs4c2, thus making them uninstallable in Sid. Thus unfortunately another upload is needed. Thanks, Christopher Martin pgpjNQ8BJvslj.pgp Description: PGP signature
Bug#341675: [EMAIL PROTECTED]: cppunit: FTBFS on hppa]
Hello, This is probably related to qt-x11-free's FTBFS on hppa. Our build fails like this: /build/buildd/qt-x11-free-3.3.5/bin/uic -L /build/buildd/qt-x11-free-3.3.5/plugins pixmapfunction.ui -o pixmapfunction.h make[4]: *** [pixmapfunction.h] Illegal instruction ...which looks like what you're experiencing. According to lamont, this is a glibc issue (which was thought fixed by building glibc with gcc-3.4 instead of gcc-4.0, but apparently wasn't). See http://lists.debian.org/debian-glibc/2005/12/msg2.html. No reaction from the glibc team thus far. Cheers, Christopher Martin On December 3, 2005 12:45, Steve M. Robbins wrote: Could someone help me out with BTS 341675? Suddenly the uic program from Qt fails to run on the hppa build daemon. There is no relevant source change in cppunit between revision -4 (which built on September 7) and revision -5. The build log shows that it runs into an illegal instruction. I ran the command by hand on paer and indeed uic quits with SIGILL. I ran it in the debugger and it looks like a problem in libgcc_s.so. Could someone confirm whether this is the case? Or perhaps it is actually a problem in qt3's uic? That comes from package qt3-dev-tools. The successful september build used -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339212: libmusicbrainz2.1 NMU imminent (allocator transition)
Hello, I will be NMUing this package very shortly, applying the patch from Matthias Klose, for the allocator transition. If you would prefer I did not do this, let me know ASAP. Thanks, Christopher Martin pgpDbjTP53f7c.pgp Description: PGP signature
Bug#341114: kate: complete directory is deleted when saving file matching #* (e. g. #file.txt)
On November 28, 2005 09:25, Daniel Musketa wrote: Package: kate Version: 4:3.3.2-1sarge1 Severity: critical Justification: causes serious data loss *** Please type your report below this line *** When saving a file beginning with # from kate or KWrite the whole folder is deleted. I can't reproduce this with KDE 3.4 or 3.5. I don't suppose you have access to any such system where you could verify that the problem is solved in newer releases? This has already been reported upstream at http://bugs.kde.org/114374. They seem to think it's fixed now as well. Hmmm... Cheers, Christopher Martin pgpA2CS3pvPuS.pgp Description: PGP signature
Bug#339212: libmusicbrainz2.1 NMU imminent (allocator transition)
On November 28, 2005 16:24, you wrote: On Mon, 28 Nov 2005 08:52:55 -0500, Christopher Martin wrote: I will be NMUing this package very shortly, applying the patch from Matthias Klose, for the allocator transition. Well, I'm not Andreas, but only the person who just recently started considering to take over maintenance of libmusicbrainz. Still, I'd ask you to please go ahead, as I was going to NMU myself on Wednesday, the 30th, using Matthias' patch. As we don't want to delay the transition, the bug is RC for 11 days and a simple fix is available without maintainer reaction so far, I'd guess a 0-day NMU will be acceptable... Thanks, done. It's in NEW at the moment. Cheers, Christopher Martin pgpDCgu38yzV5.pgp Description: PGP signature
Bug#339223: library package needs to be renamed (libstdc++ allocator change
Hello, libtunepimp will need to have its libraries renamed as soon as libmusicbrainz-2.1 is through the NEW queue. Several KDE packages are currently waiting for libmusicbrainz-2.1/libtunepimp to be transitioned, so once libmusicbrainz-2.1 passes NEW, I plan to NMU libtunepimp. Unless, of course, you ask me not to, since you plan to do it yourself. Let me know! Thanks, Christopher Martin pgpF9VkMOgMlh.pgp Description: PGP signature
Bug#341174: boost FTBFS on hppa
Package: boost Version: 1.33.0-5 Severity: serious As revealed here: http://buildd.debian.org/fetch.php?pkg=boostver=1.33.0-5arch=hppastamp=1132750731file=logas=raw boost fails to build on hppa. Since it is important that a post-allocator transition boost be built on all architectures, please try to have this resolved shortly. You might also want to prod the m68k porters to get boost installed on that architecture (where it reportedly built successfully). Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339212: libmusicbrainz-2.1 rebuild - soon?
Hello, libmusicbrainz-2.1 will need to be uploaded very shortly if it is to avoid holding up the KDE rebuild (libmusicbrainz-2.1 - libtunepimp - kdemultimedia). If you plan to upload soon, please proceed. If not, let us know, and we can NMU. Thanks, Christopher Martin pgpaZkeQQRphc.pgp Description: PGP signature
Bug#338142: kdegraphics: FTBFS: missing declarations
-build] Error 2 = Applying the following patch in ksvg/impl helps: Thanks. This will be fixed in the next upload. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337996: FTBFS: xine-lib debian/rules contains a bashism
Package: xine-lib
Version: 1.0.1-1.3
Severity: serious
xine-lib's debian/rules contains the following:
mv debian/tmp/usr/share/doc/xine/{faq,README*} \
debian/libxine1/usr/share/doc/libxine1
This fails with dash as sh, since it doesn't understand {faq,README*}. The
easiest fix would be to move the faq and README* separately, as follows:
mv debian/tmp/usr/share/doc/xine/faq \
debian/libxine1/usr/share/doc/libxine1
mv debian/tmp/usr/share/doc/xine/README* \
debian/libxine1/usr/share/doc/libxine1
Cheers,
Christopher Martin
pgpM747zMxZJ7.pgp
Description: PGP signature
Bug#338011: kdeartwork: FTBFS: screensaver ant missing (from xscreensaver)
tags 338011 pending stop On November 7, 2005 14:47, Roland Stigge wrote: Package: kdeartwork Version: 4:3.4.2-1 Severity: serious This is caused by the new upstream version of xscreensaver (triggered by NEXES in hacks/Makefile.in). He writes about the new version 0.23: Don't install ant by default, since there is some Java tool of that name, which was causing confusion. And also it's boring. So either ignore ant.desktop by removing it from debian/kscreensaver-xsavers.install or reassign this bug to xscreensaver for reintroducing the theme. This will be fixed in the next upload (we'll just drop ant.desktop). Thanks for the report. Cheers, Christopher Martin pgpiWp0xWQUD8.pgp Description: PGP signature
Bug#337213: kdesktop: SEGV due to previous unstable - testing transition, missing audio related dependency
severity 337213 important stop On November 3, 2005 04:51, Andreas Mohr wrote: Package: kdesktop Version: 4:3.4.2-4 Severity: grave Hello all, I found the new kde 3.4.2-4 testing packages in the archive yesterday, thus I upgraded my 3.4.2-3 unstable packages (installed maybe 4 weeks ago before I made the switch from unstable - testing on this system). On next KDE startup, the result was a nice kdesktop crash (KDE error handler) with a backtrace that indicated audio related issues (sorry, didn't keep a copy of that backtrace), and of course kdesktop was gone. We know. This is a result of a toolchain bug, #336114, and there isn't much we can or should do about these crashes until we get some direction on how that bug is going to be solved (though in unstable, as you can see there, we rebuilt arts specifically to avoid the worst of the problem). Until then, users will have to avoid partial upgrades, or they can work around the crashes by disabling Sound Previews. I'm lowering this bug to important for the time being, since it doesn't break the package for everybody. Nevertheless, rest assured that we'll get this sorted out as soon as possible. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318658: quanta truncates targets of symlinks to empty files (0 bytes)
severity 318658 important stop I'm lowering the severity of thi bug, for several reasons. 1) It blocks kdewebdev from testing, even though the old testing package (reportedly) was the version with the problem. 2) It isn't clear that the problem is really in quanta at all, as the sftp kioslave is known to have issues with symlinks, though many were fixed for KDE 3.4.x. 3) No one has bothered to confirm this problem in the latest version. Some (admittedly extremely cursory) testing didn't find any problems. So important seems a better choice for the time being. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336114: gcc-4.0_4.0.1-9 backwards incompatible changes
Package: libstdc++6 Version: 4.0.2-3 Severity: grave A kdebase built with gcc/libstdc++6 4.0.1-8 is not compatible with a kdebase built with 4.0.1-9 or later. The result are crashes like #335658, unless (in that case) arts is rebuilt with 4.0.1-9+, in which case the problem disappears. Another example is #336009, a crash that can be resolved by rebuilding kdelibs and arts (but if one is still built with 4.0.1-8, crash...). Comparing old and new builds of konq_sound.so (part of libkonq4, a kdebase package), we get attachment [1]. Comparing libmcop.so.1.0.0 (part of libarts1c2, an arts package), we get attachment [2]. So either upstream will have to revert some changes, or we'll have to just rebuild all packages that seem affected and move on. The following 4 commits look like they might be the culprit: http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00667.html http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00668.html http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00701.html http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00710.html Cheers, Christopher Martin [1] base.diff [2] arts.diff --- old 2005-10-27 18:37:34.0 -0400 +++ new 2005-10-27 18:38:11.0 -0400 @@ -4,7 +4,7 @@ T _fini T _init T init_konq_sound -V guard variable for __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_get_pool()::_S_pool +V guard variable for __gnu_cxx::__common_pool__gnu_cxx::__pool, true::_S_get_pool()::_S_pool W QValueListQString::detachInternal() W KonqSoundPlayer::~KonqSoundPlayer() W KonqSoundPlayer::~KonqSoundPlayer() @@ -26,7 +26,7 @@ T KonqSoundPlayerImpl::~KonqSoundPlayerImpl() W __gnu_cxx::__mt_allocArts::TraderOffer, __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true ::deallocate(Arts::TraderOffer*, unsigned int) W __gnu_cxx::__mt_allocstd::string, __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true ::deallocate(std::string*, unsigned int) -W __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_get_pool() +W __gnu_cxx::__common_pool__gnu_cxx::__pool, true::_S_get_pool() W KLibFactory::metaObject() const W QGList::count() const W QObject::metaObject() const @@ -42,4 +42,4 @@ V vtable for KonqSoundFactory V vtable for KonqSoundPlayerImpl V vtable for QGList -V __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_get_pool()::_S_pool +V __gnu_cxx::__common_pool__gnu_cxx::__pool, true::_S_get_pool()::_S_pool --- old +++ new @@ -42,7 +42,7 @@ T lt_dlsetsearchpath T lt_dlsym T arts_strdup_printf(char const*, ...) -V guard variable for __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_get_pool()::_S_pool +V guard variable for __gnu_cxx::__common_pool__gnu_cxx::__pool, true::_S_get_pool()::_S_pool T Arts::AuthAccept::readType(Arts::Buffer) T Arts::AuthAccept::operator=(Arts::AuthAccept const) T Arts::AuthAccept::AuthAccept(Arts::AuthAccept const) @@ -1215,10 +1215,9 @@ W __gnu_cxx::__mt_allocstd::_Rb_tree_nodestd::pairstd::string const, std::string , __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true ::allocate(unsigned int, void const*) W __gnu_cxx::__mt_allocstd::_Rb_tree_nodestd::pairstd::string const, std::vectorstd::string, std::allocatorstd::string , __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true ::deallocate(std::_Rb_tree_nodestd::pairstd::string const, std::vectorstd::string, std::allocatorstd::string *, unsigned int) W __gnu_cxx::__mt_allocstd::_Rb_tree_nodestd::pairstd::string const, std::vectorstd::string, std::allocatorstd::string , __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true ::allocate(unsigned int, void const*) -W __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_get_pool() -W __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_initialize() -W __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_initialize_once() -W __gnu_cxx::__common_pool_policy__gnu_cxx::__pool, true::_S_destroy_thread_key(void*) +W __gnu_cxx::__common_pool__gnu_cxx::__pool, true::_S_get_pool() +W __gnu_cxx::__common_pool_base__gnu_cxx::__pool, true::_S_initialize() +W __gnu_cxx::__common_pool_base__gnu_cxx::__pool, true::_S_initialize_once() T Arts::AnyRefBase::type() const T Arts::AnyRefBase::_read(Arts::Buffer*) const T Arts::AnyRefBase::_write(Arts::Buffer*) const @@ -1317,7 +1316,6 @@ W std::_Deque_baseArts::IOWatchFD*, std::allocatorArts::IOWatchFD* ::_M_destroy_nodes(Arts::IOWatchFD***, Arts::IOWatchFD***) W std::_Deque_baseArts::IOWatchFD*, std::allocatorArts::IOWatchFD* ::_M_initialize_map(unsigned int) W std::_Deque_baseArts::IOWatchFD*, std::allocatorArts::IOWatchFD* ::~_Deque_base() -W std::_Deque_iteratorArts::Notification, Arts::Notification const, Arts::Notification const*::operator+=(int) W std::_Deque_iteratorArts::Notification, Arts::Notification, Arts::Notification*::operator+=(int) W std::mapstd::string, Arts::TypeIdentification, std::lessstd::string, std::allocatorstd::pairstd::string const, Arts::TypeIdentification ::operator[](std::string const) W std::listArts::NamedStoreArts::Object::Element, std
Bug#334835: kdewebdev: ftbfs [sparc] error: expected class-name before '{' token
On October 20, 2005 00:50, Blars Blarson wrote: Package: kdewebdev Version: 4:3.4.2-1.1 Severity: serious Justification: no longer builds from source kdewebdev failed to build on a sparc buildd, but did build on my sparc pbuilder. Perhaps a build dependancy is insufficiently versioned. Considering that 3.4.2-1 built on sparc, and that the 1.1 NMU that failed only changed the compiler on hppa/arm/m68k, then I suspect that this is just transient breakage. Could kdewebdev please be retried on sparc? If it builds, then we can check off another package for the gcc-4.0 ABI transition. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319232: boost FTBFS on hppa and m68k - upload to fix soon?
Hello, Will an upload to fix boost's FTBFS on hppa and m68k be made soon? As kdeedu build-depends on boost, this issue is tied into the gcc-4.0 ABI transition. Thanks, Christopher Martin pgpp4SrnAPemF.pgp Description: PGP signature
Bug#318658: quanta truncates targets of symlinks to empty files (0 bytes)
Scott Edwards wrote: The justification for grave bug is more accurately described as causes data loss, and is only recoverable from backup medium. reportbug didn't offer an accurate classification. Hello, Can you (or anyone else) test this issue with the quanta package in unstable? It would be nice to know that it has been fixed, or not. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330376: kdenetwork: ftbfs [sparc] Segmentation fault /usr/share/qt3/bin/uic
On September 27, 2005 15:52, Blars Blarson wrote: Package: kdenetwork Version: 4:3.4.2-3 Severity: serious Justification: no longer builds from source kdenetwork failed to build on my sparc pbuilder. The sparc buildd log has not yet made it to buildd.debian.org, so I don't know if if failed there or not. Note the resemblence of this error: /bin/sh: line 1: 26339 Segmentation fault /usr/share/qt3/bin/uic -L /usr/lib/kde3/plugins/designer -nounload -tr tr2i18n -i usertab.h ...to that reported in #326470: /usr/share/qt3/bin/uic -L /usr/lib/kde3/plugins/designer -nounload -impl actest.h actest.ui actest.cpp Segmentation fault ...which was reported against Qt3 3:3.3.4-7, on powerpc, but made mention of the problem being somehow related to the lack of altivec on the reporter's build system. So perhaps Qt3 is being built against certain hardware, and doesn't work properly against hardware which doesn't have all the features of the buildd hardware. For this reason, I would be very curious to see if kdenetwork succeeds on vore, since it has always built there before, as has Qt3, kdelibs, etc. Thanks, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330376: kdenetwork: ftbfs [sparc] Segmentation fault /usr/share/qt3/bin/uic
severity 330376 important reassign 330376 qt3-dev-tools merge 330376 326470 stop On September 28, 2005 10:52, Christopher Martin wrote: So perhaps Qt3 is being built against certain hardware, and doesn't work properly against hardware which doesn't have all the features of the buildd hardware. For this reason, I would be very curious to see if kdenetwork succeeds on vore, since it has always built there before, as has Qt3, kdelibs, etc. kdenetwork just built successfully on auric, so this FTBFS must be the result of a more subtle bug, likely in qt-x11-free. I'm merging it with the aforementioned powerpc report. Qt3's build system is dodgy, to say the least. For instance, on the i386 architecture, it must be built on an i686 piece of hardware, or higher, or else the buildkey will change. Perhaps something similar is occuring here - the buildds are building Qt with certain optimizations, which cause segfaults on older hardware. Yet there seems to be no easy way to control this aspect of Qt's build. Anyone able to help? Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329108: gcc-4.0 FTBFS on, uh, i386
Package: gcc-4.0
Version: 4.0.1-8
Severity: serious
Hello,
On the latest i386 Sid, gcc-4.0 does not build from source, on my machine,
and on a buildd (see the logs). With dash as sh, I get:
Will not build the Pascal compiler: disabled for 4.0
Will build the Ada compiler.
Will build the shared Ada libraries.
Will build the Treelang compiler.
Will build the FFI library.
Will run the testsuite.
/bin/bash: -c: line 0: syntax error near unexpected token `)'
make[1]: *** [stamps/04-configure-stamp] Error 2
Making bash sh solves this. Next up I get the following:
In file included from /usr/include/bits/mathinline.h:5,
from /usr/include/math.h:382,
from ../../../../src/libiberty/floatformat.c:27:
/usr/include/x86_64-linux/bits/mathinline.h:45: error: syntax error before
‘{’ token
/usr/include/x86_64-linux/bits/mathinline.h:46: error: syntax error before
‘}’ token
/usr/include/x86_64-linux/bits/mathinline.h:46: error: field name not in
record or union initializer
/usr/include/x86_64-linux/bits/mathinline.h:46: error: (near initialization
for ‘__u’)
/usr/include/x86_64-linux/bits/mathinline.h:46: error: ‘__x’ undeclared here
(not in a function)
/usr/include/x86_64-linux/bits/mathinline.h:47: error: syntax error before
‘return’
/usr/include/x86_64-linux/bits/mathinline.h:51: error: syntax error before
‘{’ token
/usr/include/x86_64-linux/bits/mathinline.h:52: error: conflicting types for
‘__i’
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous declaration
of ‘__i’ was here
/usr/include/x86_64-linux/bits/mathinline.h:52: error: syntax error before
‘}’ token
/usr/include/x86_64-linux/bits/mathinline.h:52: error: redefinition of ‘__u’
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous definition
of ‘__u’ was here
/usr/include/x86_64-linux/bits/mathinline.h:52: error: field name not in
record or union initializer
/usr/include/x86_64-linux/bits/mathinline.h:52: error: (near initialization
for ‘__u’)
/usr/include/x86_64-linux/bits/mathinline.h:53: error: syntax error before
‘return’
/usr/include/x86_64-linux/bits/mathinline.h:57: error: syntax error before
‘{’ token
/usr/include/x86_64-linux/bits/mathinline.h:58: error: conflicting types for
‘__i’
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous declaration
of ‘__i’ was here
/usr/include/x86_64-linux/bits/mathinline.h:58: error: syntax error before
‘}’ token
/usr/include/x86_64-linux/bits/mathinline.h:58: error: redefinition of ‘__u’
/usr/include/x86_64-linux/bits/mathinline.h:46: error: previous definition
of ‘__u’ was here
/usr/include/x86_64-linux/bits/mathinline.h:58: error: field name not in
record or union initializer
/usr/include/x86_64-linux/bits/mathinline.h:58: error: (near initialization
for ‘__u’)
/usr/include/x86_64-linux/bits/mathinline.h:59: error: syntax error before
‘return’
make[6]: *** [floatformat.o] Error 1
make[6]: Leaving directory
`/home/chris/gcc-temp/gcc-4.0-4.0.1/build/i486-linux-gnu/64/libiberty'
make[5]: *** [multi-do] Error 1
This may have something to do with the build-depends, and gcc-4.0's failure
on the i386 buildd. One of gcc-4.0's build-depends is: libc6-dev-amd64
[i386] | amd64-libs-dev (= 1.2) [i386]. It is my understanding that on
the buildds, the first element in any such list of packages which satisfies
a build dependency must be available, otherwise the build fails.
libc6-dev-amd64 is not installable on i386. On my machine, I fell back to
amd64-libs-dev, but clearly something still wasn't right, and the build
still failed, as above.
Cheers,
Christopher Martin
pgp1qpEdHGA0S.pgp
Description: PGP signature
Bug#328727: xmms freezes on the desktop
severity 328727 important tags 328727 unreproducible stop On September 16, 2005 19:00, fb wrote: Package: xmms Version: 1.2.10+cvs20050209-2 Severity: grave Justification: renders package unusable xmms when opened as an application, immediately crashes and ceases to function. Clicking the play applet in xmms, causes xmms to freeze to the desktop after which xkill must be invoked to delete xmms from the desktop. I can't reproduce the problem here. Could you provide more information? The incoming maintainer will likely need more data to investigate properly. Did XMMS just cease functioning one day, or did you just install it? If you launch XMMS from a console, what errors appears on the console when it crashes? If you upgrade to the package in Sid, does the problem change? Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327360: python2.3-qt3: undefined symbol: _ZTI11QMotifStyle
For your information, the split-out of the Qt styles which is the cause of this problem will be reverted in the next upload of Qt, which will likely take place in a few days. Cheers, Christopher Martin pgpWBkV12Ld2P.pgp Description: PGP signature
Bug#326935: libxine1 has an unstated dependency on libgnomevfs2-0
Package: libxine1 Version: 1.0.1-1.2 Severity: serious Without libgnomevfs2-0 installed, no xine-based players work, but simply spit out no plugin found type errors for all files. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326457: qt-x11-free: FTBFS: Cannot find postgresql server headers
tags 326457 pending stop On September 3, 2005 08:10, Daniel Schepler wrote: Package: qt-x11-free Severity: serious Version: 3:3.3.4-7 From my build log, with postgresql packages from current unstable: snip You can probably fix this by adding postgresql-server-dev-8.0 to the Build-Depends and adding -I`pg_config --includedir-server` to the include flags. Yes, the postgresql package moved some headers around recently. I fixed this in an as-of-yet-not-uploaded revision by adding -I`pg_config --includedir`/8.0, but no new build-depends. Cheers, Christopher Martin pgpBSLmIYKmxv.pgp Description: PGP signature
Bug#315433: kdelibs-bin: laptop can't wake up when kded was running when i slept it
severity 315433 important stop Hello, If kded can accomplish this, then it is uncovering a bug in the kernel, which given the context of power-saving, isn't surprising. Stull, kded probably could be better behaved in many ways, so rather then closing or re-assigning, I'll lower this to important, since it doesn't affect everybody. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317314: Any plans to fix firebird for gcc4?
Hello, Just wondering if/when firebird will likely be rebuilt for the gcc4 transition. This is required before we reenable support in Qt. Thanks for any info, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318093: xmms: XMMS does not start with Xorg and enabled CompositeExtension
severity 318093 important forwarded 318093 http://bugs.xmms.org/show_bug.cgi?id=1907 stop On July 13, 2005 12:00, Jan Christoph Uhde wrote: Package: xmms Version: 1.2.10+cvs20050209-2 Severity: grave Justification: renders package unusable [EMAIL PROTECTED]:~$ xmms Message: device: default Gdk-ERROR **: BadMatch (invalid parameter attributes) serial 468 error_code 8 request_code 2 minor_code 0 Please see http://bugs.xmms.org/show_bug.cgi?id=1907 for an explanation of the problem. In short, there are certain compatibility issues with GTK+ 1.2.x applications and the Composite extension, as you have discovered. There is a work-around, however: 'export XLIB_SKIP_ARGB_VISUALS=1 xmms' Furthermore, since this doesn't affect all users (Composite is disabled by default, and obviously for good reason), I'm lowering this bug's severity to important. Cheers, Christopher Martin pgpbA491JnhuF.pgp Description: PGP signature
Bug#312358: kdm crashes on startup
On July 3, 2005 09:27, Adeodato Simó wrote:
The real question is why the kde packages don't conflict with earlier
kdm versions if they don't work with them... (not that kde had too few
conflicts, how about a little backwards compatibility anyway?)
This situation is mostly fixed in our SVN since Jun 9, but there has
not been another upload to experimental since then. .oO(Must implement
that svn post-commit hook that tags pending and attachs changelog
entry when closing a bug in SVN, like subversion (the pacakge) does.)
We tightened the kdm dependency on kdebase-bin, which was the one
causing problems. As now kdm Depends: kdebase-bin (= ${Source-Version),
kdm will necessarily get upgraded whenever kdebase is.
This, er, solves the problem after people upgrade to kdm 3.4.1. The
possibility of remaining with an un-upgraded 3.3.2 remains, but I
haven't decided what to do with that yet. Perhaps a one-time versioned
conflicts (kdebase-bin Conflicts: kdm ( 4:3.4.1-2), what do you
think, Christopher?).
Seems fine to me!
Cheers,
Christopher Martin
pgpmUbBdEStNe.pgp
Description: PGP signature
Bug#313375: khelpcenter: missing Depends: htdig
severity 313375 important stop On June 13, 2005 12:21, Andreas Pakulat wrote: So I tried the deb and yes it seems that creating the index is comletely broken. At least: khelpcenter tries to resolve all the help://XXX URL's via normal DNS, which is wrong, IMHO. I'll add another comment to the upstream bugreport... Since this is really much more of an upstream bug than a missing depend, I'm lowering the severity to important, since the bug itself is not RC. When upstream gets its act together, then we'll add the necessary depend(s). Until then, it/they would be superfluous. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313375: khelpcenter: missing Depends: htdig
On June 13, 2005 10:28, Christopher Martin wrote: Unless there is some trick I'm missing Indeed. FINDCMD: find /usr/share/doc/HTML/en/ -name index.docbook Creating index for 'kde_application_manuals' find: /usr/share/doc/HTML/en/: No such file or directory Perhaps the only problem is simply that it isn't using Debian's correct path of /usr/share/doc/kde/HTML/en/. Let's try patching that and see what happens... pgpnKu560aiSg.pgp Description: PGP signature
Bug#313375: khelpcenter: missing Depends: htdig
On June 13, 2005 06:50, Andreas Pakulat wrote: I just wanted to create a search index for the helpcenter but couldn't as it's missing htdig. If indexing is not possible without htdig, khelpcenter should depend on it. I wasn't sure if this is a severe policy violation, thus only used severity: important instead of serious... If you install htdig, does it work? Even with htdig installed, I can't get KHelpCenter to actually index the handbooks, though it tells me that it succeeded. A quick google revealed a large number of people with similar problems. See KDE bug #102912 and Gentoo bug #89515 for a sample. Unless there is some trick I'm missing, I suspect that this feature is simply broken, or at least unsupported by Debian's htdig. Cheers, Christopher Martin pgpvAmC9VksyI.pgp Description: PGP signature
Bug#313375: khelpcenter: missing Depends: htdig
On June 13, 2005 10:36, Christopher Martin wrote: Perhaps the only problem is simply that it isn't using Debian's correct path of /usr/share/doc/kde/HTML/en/. Let's try patching that and see what happens... Still doesn't work: FINDCMD: find /usr/share/doc/kde/HTML/en/ -name index.docbook Creating index for 'kde_application_manuals' Warning: unknown locale! New server: home, 80 Unknown host: home 0:0:0:file://home/chris/.kde/share/apps/khelpcenter/ \ index/kde_application_manuals.tmp/index.html: \ size = 12663 htdig: Run complete htdig: 1 server seen: htdig: home:80 1 document Finished successfully. I noticed that htdig's debconf prompts mentioned the existence of an htdig3.2 package, yet I couldn't find it in the archive. It is available from http://users.linuxbourg.ch/ribnitz/debian, however, and while I now get a much longer and more promising set of errors, no index. pgpSt6v4kCqna.pgp Description: PGP signature
Bug#311958: kdebase: FTBFS: error making docs.
On June 5, 2005 15:30, Kurt Roeckx wrote: This a minimal sid chroot (only essential + build essential installed) with the following additional installed: apt-get install cdbs debhelper autotools-dev gawk gettext kdelibs4-dev/experimental dbus-qt-1-dev libldap2-dev libhal-dev libhal-storage-dev libncurses5-dev libpam0g-dev libpopt-dev libraw1394-dev libsensors-dev libsmbclient-dev libusb-dev libxtst-dev xutils xlibs-static-pic sharutils texinfo doxygen qt3-doc graphviz gsfonts-x11 kdelibs4=4:3.4.1-1 kdelibs-bin=4:3.4.1-1 libarts1-dev/experimental libarts1=1.4.1-1 libartsc0-dev=1.4.1-1 libartsc0=1.4.1-1 dbus-1-dev=0.23.4-1bindings0 dbus-1=0.23.4-1bindings0 What version is kdelibs-data? Was it upgraded to 3.4.1 as well? I ran the above and it stayed at 3.3.2. Upgrading solved the problem. The fix for this issue, namely forcing kdelibs4 to depend on the same version of kdelibs-data, rather than the current = 3.3.0 (which is very odd anyway), seems safe and straightforward, so I'll commit soon unless anyone objects. Cheers, Christopher Martin pgp8caj57jBJv.pgp Description: PGP signature
Bug#311958: kdebase: FTBFS: error making docs.
On June 4, 2005 07:17, Kurt Roeckx wrote: Package: kdebase Verison: 4:3.4.1-1 Severity: serious Tags: experimental Maybe this is a missing build dependency or something? Possibly, but I tried to reproduce this in a very minimal Sid chroot (arts and kdelibs came from experimental, and dbus from our alioth repo, but otherwise all Sid). It built without this problem, so I'm baffled. Are you using any non-standard packages, aside from the obvious kde bits from experimental, and dbus? Cheers, Christopher Martin pgpUz6frMup9q.pgp Description: PGP signature
Bug#310637: kde does not start
severity 310637 important stop Since this problem doesn't break the system for the vast majority of people, the severity level of important seems best here. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307066: xmms: skips all songs but the last one in a playlist
severity 307066 important stop On April 30, 2005 08:49, Joern wrote: Subject: xmms: skips all songs but the last one in a playlist Package: xmms Version: 1.2.10+cvs20050209-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** XMMS skips all tracks in a playlist and just plays the last song. If you put more songs in the playlist, it will instantly stop playing and start skipping to the last song again. The same happens if you just move a song from the playlist below the last one. The bug occurs with any kind of playable file and with any kind of output plugin I have installed (esound, alsa, oss, disk writer) XMMS isn`t rendered completely unusuable technically, as I can still play one song at a time, but it`s totally pointless using XMMS with this bug :) This bug has been reported before, but the reporter then found that it vanished... it is also unreproducible by most people, and therefore not release critical by the definitions of bug severity levels. Some information would be helpful. Are you running any XMMS-dependent utilities like wmxmms? If you're not absolutely certain, reboot. If you are, try shutting them down, and restarting them. Also, are you trying to play files from an NFS mount? Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305601: CAN-2005-0404: serious content spoofing vulnerability
severity 305601 important stop On April 20, 2005 20:34, Geoff Crompton wrote: In summary: A remote email message content spoofing vulnerability affects KDE KMail. This issue is due to a failure of the application to properly sanitize HTML email messages. An attacker may leverage this issue to spoof email content and various header fields of email messages. This may aid an attacker in conducting phishing and social engineering attacks by spoofing PGP keys as well as other critical information. securityfocus list 3.3.2 as vulnerable, which is currently in Sarge and Sid. No idea if it would affect 2.2.2 which is in Woody. See KDE bug 96020. Talking to upstream, it seems that the bug isn't quite as serious as the summary might suggest. Here's Dirk Mueller: --- It does affect kmail 3.4 the same way it affected all older versions. however, this proof of concept is pretty lame. it doesn't match the colors, the fonts or even the font sizes. of course you could theoretically tune for that. it doesn't have the usual link to the status popup though, and its clearly mentioned in several places that HTML rendering has phishing problems, and HTML rendering is *disabled* by *default* in kmail, and you get a pretty huge warning if you still enable it. anyway, the html bar also indicates that this is a spoofed message. maybe not in an obvious way. the only way we could mitigate this attack for real though is to load the actual content in a separate frame, so that it cannot paint over kmail specific HTML. This is a long term todo, and there are a few bits missing in KHTML in order to achieve that. so I'd either close it as wontfix or as duplicate, whatever you prefer. --- So it would appear that while KMail's behaviour makes phishing easier than it perhaps should be, in the real world far from a magical pass into the the user's confidence. Moreover, the only fix for the foreseeable future would be to disable HTML mail completely (it's already off by default and comes with a security warning). I don't believe that to be a reasonable course of action, as it would severely reduce KMail's usefulness for many users with only a minimal increase in theoretical security. Thus while this is an important problem, I don't feel it be in any sense release-critical. Cheers, Christopher Martin pgp8xJ1eADs0F.pgp Description: PGP signature
Bug#305833: kommander: untrusted code execution
The kdewebdev package in Sarge and Sid is vulnerable. Just for the record, though, the experimental 3.4.0 package on Alioth has already been patched. Cheers, Christopher Martin pgpEA7so0wpgj.pgp Description: PGP signature
Bug#303998: xmms: Segmentation fault
On April 10, 2005 05:20, Cristian Ionescu-Idbohrn wrote: Package: xmms Version: 1.2.10+cvs20050209-2 Severity: grave Justification: renders package unusable Hello, I can't reproduce this. Are you running any experimental packages? Are you using any special XMMS plug-ins? The Nvidia closed-source drivers? Try disabling all special plug-ins, visualizations, etc. Thanks, Christopher Martin pgp2u422VJqcq.pgp Description: PGP signature
Bug#303998: xmms: Segmentation fault
severity 303998 important stop On April 10, 2005 18:07, Mike Beattie wrote: Yep, I saw this too... finally discovered that it was because I still had wmxmms running. This sort of method *should* reproduce the problem: 1) install 1.2.10-2 2) install wmxmms 3) run xmms, and wmxmms. 4) quit xmms (leave wmxmms running) 5) upgrade to 1.2.10+cvs20050209-2 6) run xmms - should segfault 7) quit wmxmms 8) run xmms - should run fine 9) run wmxmms. Any further quits/runs of xmms will be fine. I haven't investigated this any further than getting it going again, but to me it looks like wmxmms has the control socket open when xmms starts - something about the previous version having been running with the current wmxmms causes it to bomb. Thanks very much for this information. I'm CCing this to restarting wmxmms resolves the issue. Meanwhile, I'll take the tentative liberty of downgrading the bug to important, since if the problem is a one-timer then it really isn't release critical. Cheers, Christopher Martin pgpGUYVBpb8eU.pgp Description: PGP signature
Bug#303244: kleopatra: configure crash
On April 5, 2005 11:27, Thomas Labourdette wrote: Package: kleopatra Version: 4:3.3.2-2 Severity: grave Justification: renders package unusable When I select Configurer Kleopatra ... in configuration menu, the application crash with this message : KCrash: Application 'kleopatra' crashing... Does updating to 3.3.2-3 from Sid make a difference? Thanks, Christopher Martin pgplkRBnFYVyM.pgp Description: PGP signature
Bug#300614: kmail: deletes emails when manually applying a filter for all messages in inbox manually
severity 300614 important retitle 300614 kmail crashes when filter applied manually on multiple mails stop Hello, This bug is known by upstream, and they think it likely that it is fixed in KDE 3.4. However, they don't know exactly when or where the fix was committed, making backporting extremely difficult. However, it is important to note that this is the first and only report of this problem that mentions data loss, and it seems likely that the data loss was related to the power-cycling of the box. The bug itself is merely a kmail lockup, and does not, insofar as the many other reporters of this problem have mentioned, cause data loss. Hence we are lowering the severity to important. Of course, we (the Debian KDE team) will continue to watch this issue and if a solution becomes available, will ensure that it reaches Sarge. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with sigsev or so when trying to play an mpeg
severity 301127 important stop amd64 is not an official architecture at this point, so this is hardly release critical. It would also be helpful if you updated to the latest packages (unless amd64 is really out of date, kdelibs and kdemultimedia all have updates over the versions listed in your report). Cheers, Christopher Martin On March 23, 2005 16:39, Dirk Salva wrote: Package: kaboodle Version: 4:3.3.1-2 Severity: grave Justification: renders package unusable When I start trying to view an mpeg or something else (like from leech.dk), kaboodle only starts, but does not play. When I push play-button, it breaks with a sigsev (KDE-crash-notifier) or so. Under 32bit sarge the same video-file works fine. Asus A8V Deluxe, NVidia 6600GT, 1GB RAM. pgpUDRd4pMLXa.pgp Description: PGP signature
Bug#295265: Kopete icq5 fix - please test this package and report back
Hello, We've built a kopete package that contains a fix for the icq5 crash, by disabling rich-text support. Please test the package, and let us know soon if it does indeed resolve the issue. Cheers, Christopher Martin Package: http://the-swirl.org/~adeodato/tmp/2005/03/20/kopete-and-icq5/kopete_3.3.2-2~test1_i386.deb pgp9ol0KXlNsX.pgp Description: PGP signature
Bug#292401: kdm_config override /etc/kde3/kdm/kdmrc which is a conffile
severity 292401 important stop Hello, The conclusion of discussion with the Release Managers on #debian-release was that this bug is really annoying but not RC. They conceded the (unintentional and in fact hitherto unnoticed) lack of clarity in sarge_rc_policy, but don't feel that this merits enforcing the strictest interpretation given the obvious practical difficulties, and recommend the bug be lowered to important. Cheers, Christopher Martin [12:46] Thucydides Could one of the RMs evaluate bug #292401, and advise on the different interpretations of Sarge RC-ness contained therein? [12:47] aba Thucydides: if the title is true, it is RC. [12:48] neuro no it isn't [12:48] Kamion doesn't seem RC to me; very annoying but not RC [12:48] aba eh, moment [12:48] neuro the rc policy is that the package _maintainer scripts_ don't do that to conffiles [12:48] * aba misunderstood the title [12:48] aba neuro: agreed. [12:48] Kamion aba: I think you read it as kdm.config, rather than kdm_config? [12:48] * aba goes back to the sick list [12:48] aba Kamion: yes. [12:49] aba I read it as $package overwrites conffile, not $program overwrites conffile - which is obviously quite a different thing. [12:49] Kamion although Bill is right that sarge_rc_policy goes a bit further than that [12:49] Kamion which is interesting since I don't think I've noticed that text before [12:50] aba well, the question is: What is an editor? I think I might qualify kdm_config as an specialiced editor, but - well, it's really quite annoying. [12:50] Kamion hmm. I think the current letter of our release policy is in fact that it's RC, but I would be inclined to leave this one alone for sarge now unless it's easy to fix [12:51] Kamion depending, as aba says, on exactly what you call an editor [12:51] Thucydides it's not an easy fix, I'm afraid [12:51] neuro it's not easy to fix. [12:51] Kamion seems unlikely that it would be [12:51] Kamion I think we should modify the release policy to replace an editor with a program designed to edit the file or some such [12:52] neuro it might be easy to fix if kde used certain gnome libraries to read the conf file...but I'm sure that fix wouldn't be acceptable to most. [12:52] aba I would tend to downgrade it to annyoing^Wimportant. [12:52] jvw Kamion: well, the program might be designed to edit the conffile, but it doesn't clearly advertise itself as such -- from an unsuspecting user POV, it modifies some 'registry', rather than a real conffile [12:53] Kamion yeah, but that's different from some automated process running it without any user request at all [12:53] jvw but yeah, pragmatic thinking yields to make this bug not RC [12:53] aba (we might even consider it as quite annoying, which also important) [12:53] neuro jvw: if the user is that unsuspecting, they're not going to be using a text editor on the file, either. [12:54] neuro or be answering anything other than enter to dpkg prompts [12:58] Thucydides Thanks for clarifying. I'll set the bug back to important. [12:59] Kamion feel free to quote this conversation pgpDQh3nj1yo8.pgp Description: PGP signature
Bug#292569: kdelibs-data: conflicts with openoffic.org
tags 292569 confirmed pending stop On January 27, 2005 17:25, Robert Waldner wrote: Whilst installing amarok, I encountered the following error: Unpacking kdelibs-data (from .../kdelibs-data_4%3a3.3.2-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/kdelibs-data_4%3a3.3.2-1_all.deb (--unpack): trying to overwrite `/usr/share/mimelnk/application/vnd.sun.xml.calc.desktop', which is also in package openoffice.org Installed is openoffice.org 1.0.3-2, on a mixed stable/testing/unstable system. The next upload of kdelibs will add Conflicts/Replaces against old versions of openoffice.org, in order to avoid problems such as you are encountering. Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292401: kdm_config override /etc/kde3/kdm/kdmrc which is a conffile
severity 292401 important stop On January 26, 2005 17:56, Bill Allombert wrote: Package: kdm Version: 4:3.3.1-4 Severity: serious Justification: Policy 10.7.3 ...which states: Configuration file handling must conform to the following behavior: * local changes must be preserved during a package upgrade, and * configuration files must be preserved when the package is removed, and only deleted when the package is purged. Nothing kcontrol does violates policy 10.7.3, which describes package upgrades and removals. It does not forbid some GUI tool from completely re-writing the file, since running that tool is up to the user and has nothing to do with packaging policy. That kcontrol does what it does is very annoying and a very nasty shortcoming, but not a policy violation. kcontrol overwrite the conffile /etc/kde3/kdm/kdmrc without respecting comment and formating. For example if you start with the file provided in the current kdm package, launch kcontrol, choose Login manager-Administrator Mode,make a change, cancel it and it apply, you get a complelty different file /etc/kde3/kdm/kdmrc, see patch below. This means dpkg conffiles handling is useless here since you cannot merge the changes. To fix this, we'd need either to ship a kdmrc that conforms to the kcontrol configurator's basic pattern, and so wouldn't be modified by kcontrol more than is really necessary (could we make it keep the comments, at least?), or else re-write the kdm module of kcontrol to behave less stupidly, which would be quite an undertaking. Comments? Cheers, Christopher Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
