Bug#373263: marked as done (KDE won't allow me to select "classic" X cursors)
Your message dated Wed, 14 Jun 2006 08:40:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#373263: KDE won't allow me to select "classic" X cursors has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kde Version: 5:47 Severity: normal Using my old distrobution, I selected "no theme" in KDE to get the orginal cursors from Xorg. Now, when using Debian Etch, there are 10 themes, but only three of them are actually different. When I select "no theme", I just get the default theme. I've uploaded a screenshot, http://tnet.no/kdebug.jpg, as you see, the previewed theme does not look anything like the orginal Xorg cursors. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-486 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages kde depends on: ii kde-amusements5:47 the K Desktop Environment games an ii kde-core 5:47 the K Desktop Environment core mod ii kdeaccessibility 4:3.5.2-1 accessibility packages from the of ii kdeaddons 4:3.5.2-1 add-on plugins and applets provide ii kdeadmin 4:3.5.2-1 system adminstration tools from th ii kdeartwork4:3.5.2-1 themes, styles and more from the o ii kdegraphics 4:3.5.2-1 graphics apps from the official KD ii kdemultimedia 4:3.5.2-2 multimedia apps from the official ii kdenetwork4:3.5.2-1 network-related apps from the offi ii kdepim4:3.5.2-1 KDE Personal Information Managemen ii kdeutils 4:3.5.2-1 general purpose utilities from the ii kdewebdev 4:3.4.3-2 web development apps from the offi kde recommends no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Le Mer 14 Juin 2006 00:59, Thomas Martinsen a écrit : > Package: kde > Version: 5:47 > Severity: normal > > Using my old distrobution, I selected "no theme" in KDE to get the > orginal cursors from Xorg. > Now, when using Debian Etch, there are 10 themes, but only three of > them are actually different. > When I select "no theme", I just get the default theme. > I've uploaded a screenshot, http://tnet.no/kdebug.jpg, > as you see, the previewed theme does not look anything like the > orginal Xorg cursors. this is dealt with alternatives. see /usr/share/icons/default/index.theme. use alternatives to chose the default theme that suits you the most -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpWC3ApSMLTT.pgp Description: PGP signature --- End Message ---
Bug#373448: (no subject)
Package: kdebindings Version: 4:3.5.1-1 Severity: important Hi, your package has been detected as generating a python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page [2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4. Please note that this bug (even not being RC) falls under the 0-day NMU policy. [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVE-2006-2197: integer overflow in wv2
Hi,
The wv2 packages are now maintained by the Debian Qt/KDE team. To the
Debian Qt/KDE people (who are CCed): please see Joey's message below.
Ben.
On Wed, Jun 14, 2006 at 10:32:04AM +0200, Martin Schulze wrote:
> A boundary checking error has been discovered in wv2, a library for
> accessing Microsoft Word documents, which can lead to an integer
> overflow induced by processing word files.
>
> Please
> . update the package in sid
> . mention the CVE id from the subject in the changelog
> . tell me the version number of the fixed package
> . use urgency=high
>
> Regards,
>
> Joey
>
> --
> The good thing about standards is that there are so many to choose from.
> -- Andrew S. Tanenbaum
> diff -u wv2-0.2.2/debian/changelog wv2-0.2.2/debian/changelog
> --- wv2-0.2.2/debian/changelog
> +++ wv2-0.2.2/debian/changelog
> @@ -1,3 +1,11 @@
> +wv2 (0.2.2-1sarge1) stable-security; urgency=high
> +
> + * Non-maintainer upload by the Security Team
> + * Applied upstream patch to fix boundary check error [src/word_helper.h,
> +CVE-2006-2197]
> +
> + -- Martin Schulze <[EMAIL PROTECTED]> Mon, 12 Jun 2006 15:19:58 +0200
> +
> wv2 (0.2.2-1) unstable; urgency=low
>
>* New upstream bugfix release.
> only in patch2:
> unchanged:
> --- wv2-0.2.2.orig/src/word_helper.h
> +++ wv2-0.2.2/src/word_helper.h
> @@ -552,8 +552,12 @@
> const U8 tmp = m_fkp.m_rgb[ m_index ].offset;
> // Now we have to calculate the real offset and then locate it
> // within our cached array...
> -if ( tmp != 0 )
> -return &m_fkp.m_fkp[ tmp * 2 - m_fkp.m_internalOffset ];
> +if ( tmp != 0 ) {
> +const int pos = tmp * 2 - m_fkp.m_internalOffset;
> +if (pos < 0 || pos >= 511 - m_fkp.m_internalOffset)
> + return 0;
> +return &m_fkp.m_fkp[ pos ];
> + }
> }
> return 0;
> }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373220: kdvi crashes on logout
Le Mer 14 Juin 2006 11:23, Felix Homann a écrit : > On Tuesday 13 June 2006 23:43, Pierre Habouzit wrote: > > if you can send a useful backtrace + the dvi that causes the crash > > yourself, you would spare us a lot of time :D > > OK, I've installed the respective -dbg packages. The new backtrace is > attached. I hope it is a "good" one. > > To reproduce please open kdvi-crash.dvi with kdvi and logout. The > LaTeX source is also attached. > > Please, let me know if you need additional information or if the > backtrace is not good enough. > > Kind regards, > > Felix this bug report is just perfect now -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgps2APxm80wm.pgp Description: PGP signature
Bug#373220: kdvi crashes on logout
On Tuesday 13 June 2006 23:43, Pierre Habouzit wrote:
> if you can send a useful backtrace + the dvi that causes the crash
> yourself, you would spare us a lot of time :D
OK, I've installed the respective -dbg packages. The new backtrace is
attached. I hope it is a "good" one.
To reproduce please open kdvi-crash.dvi with kdvi and logout. The LaTeX source
is also attached.
Please, let me know if you need additional information or if the backtrace is
not good enough.
Kind regards,
Felix
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231898336 (LWP 10212)]
[KCrash handler]
#5 KViewPart::writeSettings (this=0x81333f0)
at /build/buildd/kdegraphics-3.5.3/./kviewshell/kviewpart.cpp:1363
#6 0xb68102be in ~KViewPart (this=0x81333f0)
at /build/buildd/kdegraphics-3.5.3/./kviewshell/kviewpart.cpp:351
#7 0xb7998dfe in QPtrList::deleteItem (this=0x8132098, d=0x0)
at /usr/share/qt3/include/qptrlist.h:150
#8 0xb72c4614 in QGList::clear (this=0x8132098) at tools/qglist.cpp:701
#9 0xb75e4597 in ~KLibrary (this=0x8132060)
at /usr/share/qt3/include/qptrlist.h:93
#10 0xb75e4c23 in KLibLoader::close_pending (this=0x8131c30, wrap=0x0)
at /build/buildd/kdelibs-3.5.3/./kdecore/klibloader.cpp:516
#11 0xb75e508e in ~KLibLoader (this=0x8131c30)
at /build/buildd/kdelibs-3.5.3/./kdecore/klibloader.cpp:328
#12 0xb75884ab in KLibLoader::cleanUp ()
at /build/buildd/kdelibs-3.5.3/./kdecore/klibloader.cpp:298
#13 0xb76313e3 in ~KApplication (this=0xbfbfbef4)
at /build/buildd/kdelibs-3.5.3/./kdecore/kapplication.cpp:1609
#14 0x0805043f in main (argc=135477264, argv=0x8133810)
at /build/buildd/kdegraphics-3.5.3/./kdvi/main.cpp:153
#15 0xb7d4ceb0 in __libc_start_main () from /lib/tls/libc.so.6
#16 0x08050161 in _start () at ../sysdeps/i386/elf/start.S:119
\listfiles
\documentclass[11pt,liststotoc,a4paper,pagesize,headsepline]{scrreprt}
\pagestyle{headings}
\usepackage[latin1]{inputenc}
\usepackage{hyperref}
\begin{document}
\section{kdvi crashes on logout}
\label{sec:kdvi-crashes-logout}
kdvi reliably crashes on logout from a KDE session if this file is opened.
\end{document}
%%% Local Variables:
%%% mode: latex
%%% TeX-master: "kdvi-crash"
%%% End:
kdvi-crash.dvi
Description: TeX dvi file
Processed: sorry for the forgotten subject
Processing commands for [EMAIL PROTECTED]: > # sorry I forgot the Subject line for the mass bug filling > retitle 373401 Python policy transition Bug#373401: (no subject) Changed Bug title. > retitle 373402 Python policy transition Bug#373402: (no subject) Changed Bug title. > retitle 373403 Python policy transition Bug#373403: (no subject) Changed Bug title. > retitle 373404 Python policy transition Bug#373404: (no subject) Changed Bug title. > retitle 373405 Python policy transition Bug#373405: (no subject) Changed Bug title. > retitle 373406 Python policy transition Bug#373406: (no subject) Changed Bug title. > retitle 373407 Python policy transition Bug#373407: (no subject) Changed Bug title. > retitle 373408 Python policy transition Bug#373408: (no subject) Changed Bug title. > retitle 373409 Python policy transition Bug#373409: (no subject) Changed Bug title. > retitle 373410 Python policy transition Bug#373410: (no subject) Changed Bug title. > retitle 373411 Python policy transition Bug#373411: (no subject) Changed Bug title. > retitle 373412 Python policy transition Bug#373412: (no subject) Changed Bug title. > retitle 373413 Python policy transition Bug#373413: (no subject) Changed Bug title. > retitle 373414 Python policy transition Bug#373414: (no subject) Changed Bug title. > retitle 373415 Python policy transition Bug#373415: (no subject) Changed Bug title. > retitle 373418 Python policy transition Bug#373418: (no subject) Changed Bug title. > retitle 373419 Python policy transition Bug#373419: (no subject) Changed Bug title. > retitle 373420 Python policy transition Bug#373420: (no subject) Changed Bug title. > retitle 373421 Python policy transition Bug#373421: (no subject) Changed Bug title. > retitle 373422 Python policy transition Bug#373422: (no subject) Changed Bug title. > retitle 373423 Python policy transition Bug#373423: (no subject) Changed Bug title. > retitle 373424 Python policy transition Bug#373424: (no subject) Changed Bug title. > retitle 373425 Python policy transition Bug#373425: (no subject) Changed Bug title. > retitle 373426 Python policy transition Bug#373426: (no subject) Changed Bug title. > retitle 373427 Python policy transition Bug#373427: (no subject) Changed Bug title. > retitle 373428 Python policy transition Bug#373428: (no subject) Changed Bug title. > retitle 373429 Python policy transition Bug#373429: (no subject) Changed Bug title. > retitle 373430 Python policy transition Bug#373430: (no subject) Changed Bug title. > retitle 373431 Python policy transition Bug#373431: (no subject) Changed Bug title. > retitle 373432 Python policy transition Bug#373432: (no subject) Changed Bug title. > retitle 373433 Python policy transition Bug#373433: (no subject) Changed Bug title. > retitle 373434 Python policy transition Bug#373434: (no subject) Changed Bug title. > retitle 373435 Python policy transition Bug#373435: (no subject) Changed Bug title. > retitle 373436 Python policy transition Bug#373436: (no subject) Changed Bug title. > retitle 373437 Python policy transition Bug#373437: (no subject) Changed Bug title. > retitle 373438 Python policy transition Bug#373438: (no subject) Changed Bug title. > retitle 373439 Python policy transition Bug#373439: (no subject) Changed Bug title. > retitle 373440 Python policy transition Bug#373440: (no subject) Changed Bug title. > retitle 373441 Python policy transition Bug#373441: (no subject) Changed Bug title. > retitle 373442 Python policy transition Bug#373442: (no subject) Changed Bug title. > retitle 373443 Python policy transition Bug#373443: (no subject) Changed Bug title. > retitle 373444 Python policy transition Bug#373444: (no subject) Changed Bug title. > retitle 373445 Python policy transition Bug#373445: (no subject) Changed Bug title. > retitle 373446 Python policy transition Bug#373446: (no subject) Changed Bug title. > retitle 373447 Python policy transition Bug#373447: (no subject) Changed Bug title. > retitle 373448 Python policy transition Bug#373448: (no subject) Changed Bug title. > retitle 373449 Python policy transition Bug#373449: (no subject) Changed Bug title. > retitle 373450 Python policy transition Bug#373450: (no subject) Changed Bug title. > retitle 373451 Python policy transition Bug#373451: (no subject) Changed Bug title. > retitle 373452 Python policy transition Bug#373452: (no subject) Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. 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#373584: with imap: random crash at startup
Package: kmail Severity: important Hi, I use 2 different courier-mta. I got this crash but when i restarted kmail everything was ok again. I use kmail 4:3.5.2-1+b2. Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1249044256 (LWP 6069)] [New Thread -1278301264 (LWP 6087)] [New Thread -1269908560 (LWP 6086)] [New Thread -1261515856 (LWP 6085)] [New Thread -1253123152 (LWP 6084)] [KCrash handler] #6 0xb7cad709 in KMFolder::noContent (this=0x228) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/kmfolder.cpp:288 #7 0xb7d45dc4 in KMAcctImap::processNewMail (this=0x822af48, interactive=true) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/kmacctimap.cpp:316 #8 0xb7ce39df in KMail::AccountManager::processNextCheck (this=0x820ea10, _newMail=false) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/accountmanager.cpp:196 #9 0xb7ce3bbe in KMail::AccountManager::singleCheckMail (this=0x820ea10, account=0x822af48, interactive=true) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/accountmanager.cpp:125 #10 0xb7ce3d6f in KMail::AccountManager::checkMail (this=0x820ea10, _interactive=true) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/accountmanager.cpp:312 #11 0xb7e06ab7 in KMMainWidget::slotCheckMail (this=0x8298dd0) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/kmmainwidget.cpp:796 #12 0xb7e1ce31 in KMMainWidget::qt_invoke (this=0x8298dd0, _id=50, _o=0xbfcb4ee8) at kmmainwidget.moc:472 #13 0xb736154b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0xb76f31a9 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #15 0xb737ec4c in QSignal::activate () from /usr/lib/libqt-mt.so.3 #16 0xb7386710 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #17 0xb72f787a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #18 0xb72f7a76 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #19 0xb6fab24e in KApplication::notify (this=0xbfcb54f8, receiver=0x8375278, event=0xbfcb5258) at kapplication.cpp:550 #20 0xb7289001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #21 0xb72e9305 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #22 0xb729cd2a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #23 0xb7310255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #24 0xb731017a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #25 0xb72f638d in QApplication::exec () from /usr/lib/libqt-mt.so.3 #26 0x0804a098 in main (argc=33554472, argv=0x228) at /build/buildd/kdepim-3.5.2/build-tree/kdepim-3.5.2/kmail/main.cpp:110 #27 0xb7855eb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #28 0x08049e11 in _start () at ../sysdeps/i386/elf/start.S:119 Regards, Gonéri
Bug#373622: kcalc: incorrect sine calculation
Package: kcalc Version: 4:3.5.3-1 Severity: important Calculating sin(18108.8) produces 0.946649 while the actual answer is 0.61307. Check the compilation options for things like -ffast-math as trig calculations for large inputs are expensive and are usually not done correctly if the compiler is instructed to generate fastest code possible. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages kcalc depends on: ii kdelibs4c2a 4:3.5.3-1 core libraries and binaries for al ii libc6 2.3.6-9GNU C Library: Shared libraries ii libgcc1 1:4.1.0-4 GCC support library ii libgmp3c2 4.2.dfsg-1 Multiprecision arithmetic library ii libstdc++64.1.0-4The GNU Standard C++ Library v3 kcalc recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: cdbs blocks those packages to be upgraded to the new python policy.
Processing commands for [EMAIL PROTECTED]: > # > # you python package build-depends upon cdbs, and cdbs is not yet ready > # for the transition. blocking the bug with the cdbs one. > # > block 373301 by 373628 Bug#373301: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373302 by 373628 Bug#373302: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373314 by 373628 Bug#373314: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373309 by 373628 Bug#373309: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373312 by 373628 Bug#373312: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373315 by 373628 Bug#373315: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373418 by 373628 Bug#373418: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373419 by 373628 Bug#373419: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373420 by 373628 Bug#373420: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373423 by 373628 Bug#373423: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373430 by 373628 Bug#373430: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373431 by 373628 Bug#373431: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373435 by 373628 Bug#373435: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373438 by 373628 Bug#373438: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373440 by 373628 Bug#373440: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373444 by 373628 Bug#373444: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373445 by 373628 Bug#373445: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373447 by 373628 Bug#373447: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373448 by 373628 Bug#373448: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373449 by 373628 Bug#373449: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373560 by 373628 Bug#373560: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373455 by 373628 Bug#373455: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373465 by 373628 Bug#373465: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373467 by 373628 Bug#373467: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373473 by 373628 Bug#373473: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373474 by 373628 Bug#373474: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373473 by 373628 Bug#373473: Python policy transition Was blocked by: 373628 Blocking bugs added: 373628 > block 373475 by 373628 Bug#373475: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373480 by 373628 Bug#373480: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373479 by 373628 Bug#373479: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373483 by 373628 Bug#373483: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373484 by 373628 Bug#373484: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373487 by 373628 Bug#373487: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373491 by 373628 Bug#373491: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373493 by 373628 Bug#373493: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373499 by 373628 Bug#373499: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373501 by 373628 Bug#373501: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373503 by 373628 Bug#373503: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373504 by 373628 Bug#373504: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373518 by 373628 Bug#373518: Python policy transition Was not blocked by any bugs. Blocking bugs added: 373628 > block 373517 by
Bug#373622: marked as done (kcalc: incorrect sine calculation)
Your message dated Wed, 14 Jun 2006 14:21:54 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#373622: kcalc: incorrect sine calculation has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kcalc Version: 4:3.5.3-1 Severity: important Calculating sin(18108.8) produces 0.946649 while the actual answer is 0.61307. Check the compilation options for things like -ffast-math as trig calculations for large inputs are expensive and are usually not done correctly if the compiler is instructed to generate fastest code possible. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages kcalc depends on: ii kdelibs4c2a 4:3.5.3-1 core libraries and binaries for al ii libc6 2.3.6-9GNU C Library: Shared libraries ii libgcc1 1:4.1.0-4 GCC support library ii libgmp3c2 4.2.dfsg-1 Multiprecision arithmetic library ii libstdc++64.1.0-4The GNU Standard C++ Library v3 kcalc recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- On Wednesday 14 June 2006 12:16, Filip Spacek wrote: > Package: kcalc > Version: 4:3.5.3-1 > Severity: important > > Calculating sin(18108.8) produces 0.946649 while the actual answer is > 0.61307. Check the compilation options for things like -ffast-math as > trig calculations for large inputs are expensive and are usually not > done correctly if the compiler is instructed to generate fastest code > possible. 0.946649 is the correct answer when the angle is in degrees, which is the default for kcalc. You need to select Radians from the Angle combo box if you want to use angles in radians. Doing so gives the correct answer, so I am closing the bug. Josh --- End Message ---
Bug#372258: I can confirm this behavior
Hello, I can confirm this behavior here. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342321: marked as done (kgpg: cannot import key from keyserver)
Your message dated Wed, 14 Jun 2006 22:00:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line kgpg: cannot import key from keyserver has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kgpg Version: 4:3.4.3-2 Severity: normal When using the keyserver dialog to search for a key by name or email and a result shows up, the keyID is somehow missing. Consequently when trying to import that key an errormessage pops up that a key should be selected. Thus it is impossible to import a key from a keyserver. Searching and importing the same key from console with gpg --search-keys works. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (100, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Versions of packages kgpg depends on: ii gnupg 1.4.2-2GNU privacy guard - a free PGP rep ii kdelibs4c2a 4:3.4.3-2 core libraries for all KDE applica ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an ii libgcc1 1:4.0.2-5 GCC support library ii libqt3-mt 3:3.3.5-3 Qt GUI Library (Threaded runtime v ii libstdc++64.0.2-5The GNU Standard C++ Library v3 kgpg recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 4:3.5.2-1 Le Mercredi 7 Décembre 2005 04:11, vous avez écrit : > Package: kgpg > Version: 4:3.4.3-2 > Severity: normal > > When using the keyserver dialog to search for a key by name or email and > a result shows up, the keyID is somehow missing. Consequently when > trying to import that key an errormessage pops up that a key should be > selected. Thus it is impossible to import a key from a keyserver. > > Searching and importing the same key from console with gpg --search-keys > works. > kgpg also works now, at last. --- End Message ---
kdegraphics 4:3.5.3-1 MIGRATED to testing
FYI: The status of the kdegraphics source package in Debian's testing distribution has changed. Previous version: 4:3.5.2-1 Current version: 4:3.5.3-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kdenetwork 4:3.5.3-1 MIGRATED to testing
FYI: The status of the kdenetwork source package in Debian's testing distribution has changed. Previous version: 4:3.5.2-1 Current version: 4:3.5.3-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#321102: Further plans for possible data-loss bug in kmail
On Tue, Jun 13, 2006 at 12:09:17AM +0200, Marc 'HE' Brockschmidt wrote: > Heya, > > 321102 has been open for a long time now, but etch is relatively near > now (especially for a big and therefore slow-moving package like > kdepim). In the last few mails in the buglog disabling the dimap support > leading to this problem was proposed, but there hasn't been any reaction > to this in the last month. Could you please give a short overview and > tell us what you're planning to do about this? http://bugs.kde.org/show_bug.cgi?id=104956#c52 explains all the horror of the situation. Ping daniel ? etch is close, and we *really* need to do something here. I've looked at the source, disabling dimap seems quite ... difficult to do, and upstream is clearly unwilling to fix it before KDE 4 wich will be too late. so fixing it (with a patch presumably) won't be easy and will need testing. we should work on it. I lack the essential qualities to write that patch sadly, and I've not found any on the web. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
[bts-link] source package kdegraphics
# # bts-link upstream status pull for source package kdegraphics # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #373220 # * http://bugs.kde.org/show_bug.cgi?id=129099 # * remote status changed: (?) -> UNCONFIRMED usertags 373220 + status-UNCONFIRMED thanks
