Processed: Re: Bug#361566: Message Preview Pane hidden?
Processing commands for [EMAIL PROTECTED]: > forwarded 361566 http://bugs.kde.org/85175 Bug#361566: kmail: Crash when viewing message details by pressing the V key when the message is selected from the list Noted your statement that Bug has been forwarded to http://bugs.kde.org/85175. > tags 361566 + fixed-upstream Bug#361566: kmail: Crash when viewing message details by pressing the V key when the message is selected from the list Tags were: unreproducible Tags added: fixed-upstream > tags 361566 - unreproducible Bug#361566: kmail: Crash when viewing message details by pressing the V key when the message is selected from the list Tags were: fixed-upstream unreproducible Tags removed: unreproducible > 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]
Processed: Forward
Processing commands for [EMAIL PROTECTED]: > tags 353576 + upstream Bug#353576: infinite recursion in filesystem There were no tags set. Tags added: upstream > forwarded 353576 http://bugs.kde.org/118167 Bug#353576: infinite recursion in filesystem Noted your statement that Bug has been forwarded to http://bugs.kde.org/118167. > End of message, 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]
Processed: Merge
Processing commands for [EMAIL PROTECTED]: > forwarded 207456 http://bugs.kde.org/50462 Bug#207456: mail can be lost when disk is full/out of space Forwarded-to-address changed from http://bugs.kde.org/57342 to http://bugs.kde.org/50462. > merge 208317 207456 Bug#207456: mail can be lost when disk is full/out of space Bug#208317: kmail: crashes when run out of disk space Merged 207456 208317. > End of message, 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]
Processed: Merge
Processing commands for [EMAIL PROTECTED]: > severity 208317 important Bug#208317: kmail: crashes when run out of disk space Severity set to `important'. > retitle 207456 mail can be lost when disk is full/out of space Bug#207456: kmail: serious errors when it runs out of disk space Changed Bug title. > forwarded 208317 http://bugs.kde.org/50462 Bug#208317: kmail: crashes when run out of disk space Forwarded-to-address changed from http://bugs.kde.org/50462 to http://bugs.kde.org/50462. > merge 208317 207456 Bug#207456: mail can be lost when disk is full/out of space Bug#208317: kmail: crashes when run out of disk space Mismatch - only Bugs in same state can be merged: Values for `forwarded addr' don't match: #207456 has `http://bugs.kde.org/57342'; #208317 has `http://bugs.kde.org/50462' > End of message, 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#242520: marked as done (kmail: the encoding settings doesn't affect the message's subject)
Your message dated Tue, 25 Apr 2006 21:37:06 -0400 with message-id <[EMAIL PROTECTED]> and subject line Should be fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kmail Version: 4:3.2.1-1 Severity: important Tags: l10n my system is in the UTF-8 locale, kmail show the subject of some hebrew messages as rectangles (like when the encoding isn't correct), playing with the encodings from the menu affect only the message body and not the subject (i can see the message correctly).. if i run kmail with: env LANG=he_IL kmail, it's fine, but then it's on the ISO8859-8 encoding.. I guess kmail's encodings settings should affect the entire message including the subject (it detects the message encoding correctly because I can see the message just fine without changing anything from the encodings menu), or either have a config option to choose default encoding for incomming messages, since most of the hebrew mail is encoded in ISO8859-8 or cp1255. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.4-1-686 Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 Versions of packages kmail depends on: ii kdebase-kio-plugins 4:3.2.1-1KDE I/O Slaves ii kdelibs44:3.2.1-1KDE core libraries ii ktnef 4:3.2.1-1KDE TNEF viewer ii libart-2.0-22.3.16-3 Library of functions for 2D graphi ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5 client library to control the FAM ii libgcc1 1:3.3.3-6GCC support library ii libice6 4.3.0-7 Inter-Client Exchange library ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libkcal24:3.2.1-1KDE calendaring library ii libkdenetwork2 4:3.2.1-1KDE Network library ii libkdepim1 4:3.2.1-1KDE PIM library ii libksieve0 4:3.2.1-1KDE mail/news message filtering li ii libmimelib1 4:3.2.1-1KDE mime library ii libpcre34.5-1.1 Perl 5 Compatible Regular Expressi ii libpng12-0 1.2.5.0-5PNG library - runtime ii libqt3c102-mt 3:3.2.3-2Qt GUI Library (Threaded runtime v ii libsm6 4.3.0-7 X Window System Session Management ii libstdc++5 1:3.3.3-6The GNU Standard C++ Library v3 ii libx11-64.3.0-7 X Window System protocol client li ii libxext64.3.0-7 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information --- End Message --- --- Begin Message --- Version: 4:3.5.0-4 This should be fixed in KDE 3.5. I didn't test the problem, and am not sure if there could still be an issue with the subject, but if there is, it would probably be better to open a new report than reopen this one. --- End Message ---
Bug#307343: marked as done (kaudiocreator: Default is always selected in CDDB multiple match)
Your message dated Tue, 25 Apr 2006 20:37:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kaudiocreator Version: 4:3.3.2-1 Severity: normal Tags: patch KDE Bug #93875 is present in the Debian packages: [[ If KAudiocreator finds several matches for CD in freedb, it shows the dialog to select one. However it always uses the default selection even if I select another one. ]] -- http://bugs.kde.org/show_bug.cgi?id=93875 This is very annoying as it means that if the default CDDB entry is incorrect, one has to correct everything by hand, while another entry might have had the right information. Would it be possible to apply this fix: http://webcvs.kde.org/kdemultimedia/kaudiocreator/tracksimp.cpp?r1=1.43&r2=1.44 the patch being: http://webcvs.kde.org/kdemultimedia/kaudiocreator/tracksimp.cpp?r1=1.43&r2=1.44&makepatch=1&diff_format=u Cheers, Hugo -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages kaudiocreator depends on: ii kdelibs4 4:3.3.2-4.0.2 KDE core libraries ii kdemultimedia-kio-pl 4:3.3.2-1 Support for browsing audio CDs und ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libartsc01.3.2-3 aRts Sound system C support librar ii libasound2 1.0.8-3 ALSA library ii libc62.3.2.ds1-21GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6 client library to control the FAM ii libgcc1 1:3.4.3-12 GCC support library ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libidn11 0.5.13-1.0 GNU libidn library, implementation ii libkcddb14:3.3.2-1 cddb library for KDE ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libstdc++5 1:3.3.5-12 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-3 compression library - runtime -- no debconf information -- Hugo Haas - http://larve.net/people/hugo/ signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Version: 4:3.4.2-1 Hi, the upstream bug report about this issue refers to a patch which should be included in KDE 3.4. --- End Message ---
Bug#266652: marked as done (kmail: Crash with SIGILL)
Your message dated Tue, 25 Apr 2006 17:51:59 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#266652: Reproducable? 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: kmail Version: 4:3.2.92+3.3.0rc1-1 Severity: normal This crash occured while simply reading mail -- something that has been just fine at all other times. I got a SIGILL, and the kde crash handler saved this info: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1110390624 (LWP 22812)] [KCrash handler] #3 0x08082028 in ?? () #4 0x4022a517 in KMFolder::countUnread () from /usr/lib/libkmailprivate.so.0 #5 0x40261feb in KMSystemTray::updateNewMessages () from /usr/lib/libkmailprivate.so.0 #6 0x40262695 in KMSystemTray::qt_invoke () from /usr/lib/libkmailprivate.so.0 #7 0x40b7150c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x40b71334 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x40eb125b in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #10 0x40b92d22 in QTimer::event () from /usr/lib/libqt-mt.so.3 #11 0x40b14bcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #12 0x40b141ce in QApplication::notify () from /usr/lib/libqt-mt.so.3 #13 0x40741f13 in KApplication::notify () from /usr/lib/libkdecore.so.4 #14 0x40b04405 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #15 0x40abdc4b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #16 0x40b26f28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #17 0x40b26dd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #18 0x40b14e21 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #19 0x0804a0b4 in ?? () #20 0xb980 in ?? () #21 0xb890 in ?? () #22 0x in ?? () #23 0x in ?? () #24 0x40fb7600 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #25 0x081a1800 in ?? () #26 0x400076fb in _dl_unload_cache () from /lib/ld-linux.so.2 #27 0x405737f8 in __libc_start_main () from /lib/tls/libc.so.6 #28 0x40695edc in ?? () from /lib/tls/libc.so.6 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=en_US Versions of packages kmail depends on: ii kdebase-kio-plugins 4:3.3.0-1 KDE I/O Slaves ii kdelibs4 4:3.3.0-1 KDE core libraries ii libc62.3.2.ds1-16GNU C Library: Shared libraries an ii libgcc1 1:3.4.1-5 GCC support library ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library ii libkcal2 4:3.2.92+3.3.0rc1-1 KDE calendaring library ii libkdenetwork2 4:3.2.92+3.3.0rc1-1 KDE Network library ii libkdepim1 4:3.2.92+3.3.0rc1-1 KDE PIM library ii libkleopatra04:3.2.92+3.3.0rc1-1 KDE GnuPG interface libraries ii libkpimidentities1 4:3.2.92+3.3.0rc1-1 KDE PIM user identity information ii libksieve0 4:3.2.92+3.3.0rc1-1 KDE mail/news message filtering li ii libmimelib1 4:3.2.92+3.3.0rc1-1 KDE mime library ii libpng12-0 1.2.5.0-7 PNG library - runtime ii libqt3c102-mt3:3.3.3-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management ii libstdc++5 1:3.3.4-9 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte ii perl 5.8.4-2 Larry Wall's Practical Extraction ii xlibs4.3.0.dfsg.1-6 X Window System client libraries m ii zlib1g 1:1.2.1.1-5 compression library - runtime -- no debconf information --- End Message --- --- Begin Message --- John Goerzen a écrit : On Tue, Apr 25, 2006 at 12:49:23PM -0400, Filipus Klutiero wrote: OK, thanks. Then, it looks like it would be useful if you could test kmail again trying to empirically see if this is fixed. Otherwise, as nobody else mentioned experiencing this bug and it is only reported against an RC, it seems more optimal to close this than to investigate a backtrace from old code. That makes sense to me. -- John I understand that you meant that you don't intend to test kmail, and that it is more optimal to close this bug, so I'm closing as unreproducible. --- End Message ---
Bug#192168: marked as done (kmail filter settings does not accept IMAP folder as target)
Your message dated Tue, 25 Apr 2006 17:24:02 -0400 with message-id <[EMAIL PROTECTED]> and subject line Should be fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kmail Version: 3.1.1-1 In the Filter Settings, I cannot choose my IMAP folders as target. Only my local folders are listed and pickable. Other dialogs within the same KMail version accept my IMAP (sub)folders as targets, but not Filter Settings. Otherwise, KMail has improved a lot at handling IMAP since KDE 2. Cheers Mark -- produktivIT - Open-Source Solution Provider --- End Message --- --- Begin Message --- Version: 4:3.5.0-4 Hi, the upstream bug report about this is way too long, so I'm just closing assuming that this should be fixed if upstream closed the report. Feel free to reopen. --- End Message ---
Bug#103201: marked as done (Should not sign messages when saving to drafts folder)
Your message dated Tue, 25 Apr 2006 17:32:55 -0400 with message-id <[EMAIL PROTECTED]> and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kmail Version: 4:2.1.1-7 Severity: normal Well, I think the subject is clear. When I turn on automatic signing, saving a message to drafts folder will result in a signed message being saved. Later, when you continue writing the message you have to remove the sign manually and sign when you really send it. It should not sign messages saved to drafts. Thanks, -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux orion 2.4.3 #2 Thu May 24 21:48:24 EEST 2001 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages kmail depends on: ii kdebase-libs 4:2.1.1.0-10 KDE libraries amd modules for kdeb ii kdelibs3 4:2.1.2-3 KDE core libraries (runtime files) ii libc6 2.2.3-6 GNU C Library: Shared libraries an ii libjpeg62 6b-1.3The Independent JPEG Group's JPEG ii libmimelib12.2-cvs20010602-1 mime libraries needed for some KDE ii libpng21.0.11-1 PNG library - runtime ii libqt2 2:2.3.1-1 Qt GUI Library (runtime version). ii libstdc++2.10-glibc2.2 1:2.95.4-0.010604 The GNU stdc++ library ii xlibs 4.0.3-4 X Window System client libraries ii zlib1g 1:1.1.3-15compression library - runtime --- End Message --- --- Begin Message --- As upstream #28072 is closed, this should be fixed. Feel free to reopen if upstream's resolution doesn't satisfy you. --- End Message ---
Processed: bug 116826 is forwarded to http://bugs.kde.org/22723
Processing commands for [EMAIL PROTECTED]: > forwarded 116826 http://bugs.kde.org/22723 Bug#116826: flushes whole outbox when sending a single mail Forwarded-to-address changed from http://bugs.kde.org/35908 to http://bugs.kde.org/22723. > End of message, 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]
Processed: Wishlist
Processing commands for [EMAIL PROTECTED]: > severity 194624 wishlist Bug#194624: kmail: Should process the encoding prior to filtering Severity set to `wishlist'. > forwarded 194624 http://bugs.kde.org/48927 Bug#194624: kmail: Should process the encoding prior to filtering Forwarded-to-address changed from http://bugs.kde.org/67156 to http://bugs.kde.org/48927. > # changing severity according to upstream's classification > End of message, 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]
Processed: bug 208317 is forwarded to http://bugs.kde.org/50462
Processing commands for [EMAIL PROTECTED]: > forwarded 208317 http://bugs.kde.org/50462 Bug#208317: kmail: crashes when run out of disk space Forwarded-to-address changed from http://bugs.kde.org/67135 to http://bugs.kde.org/50462. > End of message, 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#364705: marked as done (libcvsservice-dev: libcvsservice.la refers to libXrender.la)
Your message dated Tue, 25 Apr 2006 13:33:26 -0700 with message-id <[EMAIL PROTECTED]> and subject line libcvsservice-dev: libcvsservice.la refers to libXrender.la 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: libcvsservice-dev Version: 4:3.5.2-1 Severity: important $ grep libXrender.la /usr/lib/libcvsservice.la dependency_libs=' -L/usr/lib -L/usr/share/qt3/lib -L/usr/X11R6/lib /usr/lib/libkdecore.la /usr/lib/libDCOP.la -lresolv -lutil /usr/lib/libart_lgpl_2.la /usr/lib/libidn.la /usr/lib/libkdefx.la /usr/lib/libqt-mt.la -laudio -lXt -ljpeg -lXi -lXrender -lXrandr -lXcursor -lXinerama -lXft -lfreetype -lfontconfig -ldl -lpng -lz -lXext -lSM -lICE -lpthread /usr/lib/libXrender.la -lX11' Please trigger a rebuild of kdesdk as it is currently impossible to use libcvsservice with libtool, which is blocking an upload of kdevelop. Cheers, Jeremy -- 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 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libcvsservice-dev depends on: ii kdelibs4-dev4:3.5.2-2+b1 development files for the KDE core ii libcvsservice0 4:3.5.2-1DCOP service for accessing CVS rep libcvsservice-dev recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- BinNMUs of kdesk have been queued on all architectures to correct this; no further maintainer action should be required for this bug. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature --- End Message ---
Bug#308971: acknowledged by developer (Unreproducible kbabel bugs)
On 4/23/06, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote: > This is an automatic notification regarding your Bug report > #308971: kbabel: [UPSTREAM]find next is not supported for the comment field, > which was filed against the kbabel package. > > It has been closed by one of the developers, namely > Olivier Trichet <[EMAIL PROTECTED]> (reply to [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 the developer, by replying to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > > > > -- Forwarded message -- > From: Olivier Trichet <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Date: Sun, 23 Apr 2006 15:14:20 +0200 > Subject: Unreproducible kbabel bugs > Package: kbabel > Version: 4:3.5.2-1 > > Bugs 308180 (kbabel seaches next instead of saving (after doing a find > next)) and 308971 (find next is not supported for the comment field) are > not reproductible with current kbabel version. Indeed, I can't reproduce these bugs, either. Probably have been fixed. -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein
Processed: Re: Bug#236133: Please explain your expectation
Processing commands for [EMAIL PROTECTED]: > severity 236133 minor Bug#236133: kmail: Handbook in wrong language Severity set to `minor'. > retitle 236133 Handbook language does not honor LC_MESSAGES Bug#236133: kmail: Handbook in wrong language 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#364775: korganizer: Ignores print options
Package: korganizer Version: 4:3.5.2-1+b1 Severity: normal In kontact, going to File: Print, and changing the sort field to Priority (or any other value) results in a summary sorted output when printing todos. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages korganizer depends on: ii kdelibs4c2a 4:3.5.2-2+b1 core libraries for all KDE applica ii libart-2.0-22.3.17-1 Library of functions for 2D graphi ii libaudio2 1.7-8The Network Audio System (NAS). (s ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libfontconfig1 2.3.2-5.1generic font configuration library ii libfreetype62.1.10-3 FreeType 2 font engine, shared lib ii libgcc1 1:4.1.0-1+b1 GCC support library ii libice6 1:1.0.0-3X11 Inter-Client Exchange library ii libidn110.5.18-2 GNU libidn library, implementation ii libjpeg62 6b-12The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.2-1+b1 KDE calendaring library ii libkdepim1a 4:3.5.2-1+b1 KDE PIM library ii libkpimexchange14:3.5.2-1+b1 KDE PIM Exchange library ii libkpimidentities1 4:3.5.2-1+b1 KDE PIM user identity information ii libpng12-0 1.2.8rel-5.1 PNG library - runtime ii libqt3-mt 3:3.3.6-1Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.0-4X11 Session Management library ii libstdc++6 4.1.0-1+b1 The GNU Standard C++ Library v3 ii libx11-62:1.0.0-6X11 client-side library ii libxcursor1 1.1.5.2-5X cursor management library ii libxext61:1.0.0-4X11 miscellaneous extension librar ii libxft2 2.1.8.2-6FreeType-based font drawing librar ii libxi6 1:1.0.0-5X11 Input extension library ii libxinerama11:1.0.1-4X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra ii libxt6 1:1.0.0-4X11 toolkit intrinsics library ii perl5.8.8-4 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3-11 compression library - runtime Versions of packages korganizer recommends: ii kghostview4:3.5.2-1 PostScript viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364774: konsolekalendar: should output data in chronological order
Package: konsolekalendar Version: 4:3.5.2-1+b1 Severity: normal Hi, konsolekalendar orders events per day, but then orders events in the order that they were added to the database, rather than in chronological order; i.e., when I have an event at 10 AM, then add one at 9 AM, konsolekalendar will show the former before the latter. This is confusing. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages konsolekalendar depends on: ii kdelibs4c2a 4:3.5.2-2+b1 core libraries for all KDE applica ii libart-2.0-22.3.17-1 Library of functions for 2D graphi ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-1GCC support library ii libkcal2b 4:3.5.2-1+b1 KDE calendaring library ii libkdepim1a 4:3.5.2-1+b1 KDE PIM library ii libqt3-mt 3:3.3.6-1Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.0-1 The GNU Standard C++ Library v3 konsolekalendar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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#319351: A possible solution
I close karm and in a console I submit: $ karm --dograb and the problem is out for my. Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364737: kpackage's "Configure KPackage..." dialog is too tall and unresizable
Package: kpackage Version: 4:3.5.2-1 Severity: normal The configure dialog is (according to my window manager) 732 pixels high. My screen is only 600 pixels high. I can't resize the dialog, so I miss the bottom of it altogether. -- 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-rrt Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages kpackage depends on: ii kdelibs4c2a 4:3.5.2-2+b1 core libraries for all KDE applica ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-1+b1 GCC support library ii libqt3-mt 3:3.3.6-1Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.0-1+b1 The GNU Standard C++ Library v3 ii zlib1g 1:1.2.3-11 compression library - runtime Versions of packages kpackage recommends: ii rpm 4.4.1-7Red Hat package manager -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#268943: korganizer crashes at start
Here you are: Double clicking on the korganizer window to open a new appointment. Removing the kitchensync and restarting KDE resolves the problem for me. libqt3-mt is 3:3.3.6-1, libkdeui.so.4 is 4:3.5.2-2. Please let me know if you need more information. Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241826912 (LWP 7556)] [KCrash handler] #6 0xb7025ef5 in QBoxLayout::setupGeom () from /usr/lib/libqt-mt.so.3 #7 0xb7026bc2 in QBoxLayout::minimumSize () from /usr/lib/libqt-mt.so.3 #8 0xb6fd5f01 in QLayout::totalMinimumSize () from /usr/lib/libqt-mt.so.3 #9 0xb702d938 in qSmartMinSize () from /usr/lib/libqt-mt.so.3 #10 0xb6fd51d9 in QWidgetItem::minimumSize () from /usr/lib/libqt-mt.so.3 #11 0xb7025a72 in QBoxLayout::setupGeom () from /usr/lib/libqt-mt.so.3 #12 0xb7026c60 in QBoxLayout::sizeHint () from /usr/lib/libqt-mt.so.3 #13 0xb6fd6044 in QLayout::totalSizeHint () from /usr/lib/libqt-mt.so.3 #14 0xb707ca9a in QWidget::sizeHint () from /usr/lib/libqt-mt.so.3 #15 0xb71085b1 in QFrame::sizeHint () from /usr/lib/libqt-mt.so.3 #16 0xb71b1115 in QWidgetStack::sizeHint () from /usr/lib/libqt-mt.so.3 #17 0xb7198622 in QTabWidget::sizeHint () from /usr/lib/libqt-mt.so.3 #18 0xb766167e in KJanusWidget::minimumSizeHint () from /usr/lib/libkdeui.so.4 #19 0xb766461f in KDialogBase::minimumSizeHint () from /usr/lib/libkdeui.so.4 #20 0xb7662b4f in KDialogBase::sizeHint () from /usr/lib/libkdeui.so.4 #21 0xb7079150 in qt_naturalWidgetSize () from /usr/lib/libqt-mt.so.3 #22 0xb707ed16 in QWidget::show () from /usr/lib/libqt-mt.so.3 #23 0xb71fd255 in QDialog::show () from /usr/lib/libqt-mt.so.3 #24 0xb7e69d28 in CalendarView::newEvent (this=0x80cf048, [EMAIL PROTECTED], [EMAIL PROTECTED], allDay=false) at calendarview.cpp:996 #25 0xb7e7750e in CalendarView::newEvent (this=0x80cf048) at calendarview.cpp:940 #26 0xb7e8c629 in CalendarView::qt_invoke (this=0x80cf048, _id=63, _o=0xbfc5705c) at calendarview.moc:970 #27 0xb704754b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #28 0xb7047fdc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #29 0xb7dd5fec in KOrg::BaseView::newEventSignal (this=0x3c) at baseview.moc:346 #30 0xb7e0ff6d in KOrg::BaseView::qt_emit (this=0x81eb168, _id=13, _o=0xbfc5719c) at baseview.moc:461 #31 0xb7e101b8 in KOEventView::qt_emit (this=0x81eb168, _id=13, _o=0xbfc5719c) at koeventview.moc:159 #32 0xb7e10324 in KOAgendaView::qt_emit (this=0x81eb168, _id=13, _o=0xbfc5719c) at koagendaview.moc:569 #33 0xb704751f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #34 0xb7047fdc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #35 0xb7dd4c49 in KOAgenda::newEventSignal (this=0x3c) at koagenda.moc:301 #36 0xb7e87953 in KOAgenda::eventFilter_mouse (this=0x81f6088, object=0x81f7650, me=0xbfc5778c) at koagenda.cpp:687 #37 0xb7dd9bdb in KOAgenda::eventFilter (this=0x81f6088, object=0x81f7650, event=0xbfc5778c) at koagenda.cpp:354 #38 0xb70446b0 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #39 0xb704472e in QObject::event () from /usr/lib/libqt-mt.so.3 #40 0xb7081b9a in QWidget::event () from /usr/lib/libqt-mt.so.3 #41 0xb6fdd87a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #42 0xb6fdddff in QApplication::notify () from /usr/lib/libqt-mt.so.3 #43 0xb6c9102e in KApplication::notify () from /usr/lib/libkdecore.so.4 #44 0xb6f6f06f in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #45 0xb6f6a7a4 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #46 0xb6f68c94 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #47 0xb6f822a2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #48 0xb6ff6255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #49 0xb6ff617a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #50 0xb6fdc38d in QApplication::exec () from /usr/lib/libqt-mt.so.3 #51 0x0805188c in main (argc=60, argv=0x3c) at main.cpp:58 #52 0xb7ae1eb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #53 0x0804fc01 in _start () at ../sysdeps/i386/elf/start.S:119 Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ## -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308977: kbabel: [UPSTREAM]A "Fuzzy" button would be a good addition
On 4/23/06, Olivier Trichet <[EMAIL PROTECTED]> wrote: > Le Vendredi 13 Mai 2005 17:24, Eddy Petrisor <[EMAIL PROTECTED]> a > écrit: > > Package: kbabel > > Version: 4:3.3.2-3 > > Severity: wishlist > > > > > > Hello, > > > > I have found that is rather hard to mark strings that I am not so sure > > on their translation with the fuzzy attribute. > > > > A 'fuzzy' button would be a good thing to add to the UI. > > Isn't the "ctrl+U" shortcut enough? I am not sure if that existed back when I reported this. -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein
Bug#285794: marked as done (kmail crashes when deleting all messages of a folder)
Your message dated Tue, 25 Apr 2006 03:07:52 -0400 with message-id <[EMAIL PROTECTED]> and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kmail Version: 4:3.3.1-3 Severity: normal Hi, thanks for maintaining this package. When I delete all messages from a folder by keeping the delete-key pressed until all messages are gone, kmail crashes, just as the last mail is deleted. I saved the following crash info: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 -1244606336 (LWP 2279)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #3 0x in ?? () #4 0xb7ebaa2b in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so.0 #5 0xb7eb1eda in KMCommand::slotPostTransfer () from /usr/lib/libkmailprivate.so.0 #6 0xb7eab892 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #7 0xb7eaf4cd in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #8 0xb7eaf901 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #9 0xb7eafb5d in KMDeleteMsgCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #10 0xb72b452c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb7eab6fa in KMCommand::messagesTransfered () from /usr/lib/libkmailprivate.so.0 #12 0xb7eb1f2a in KMCommand::transferSelectedMsgs () from /usr/lib/libkmailprivate.so.0 #13 0xb7eb1cfb in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.0 #14 0xb7eab87c in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #15 0xb7eaf4cd in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #16 0xb7eaf901 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #17 0xb7eafb5d in KMDeleteMsgCommand::qt_invoke () from /usr/lib/libkmailprivate.so.0 #18 0xb72b452c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0xb75f208a in QSignal::signal () from /usr/lib/libqt-mt.so.3 #20 0xb72ce6ed in QSignal::activate () from /usr/lib/libqt-mt.so.3 #21 0xb72d5ed3 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #22 0xb7257bcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #23 0xb72571ce in QApplication::notify () from /usr/lib/libq
Bug#292531: marked as done (kmail: Kmail silently exits after choosing "Open With" on an attachment)
Your message dated Tue, 25 Apr 2006 02:59:25 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#292531: Exit status?
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: kmail
Version: 4:3.3.1-3
Severity: normal
I have an email with multiple graphic attachements (PNG files) in my Inbox.
I choose one picture in the Description window (list of attachements) and
then click right mouse button in the displayed picture and choose"Open With"
from menu. After few seconds of busy 100% load kmail silently exits.
Here is the end of output from strace:
access("/usr/lib/qt3/plugins/codecs/.", F_OK) = -1 ENOENT (No such file or
directory)
open("/home/sojka/.DCOPserver_glab__0", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(3, "local/glab:/tmp/.ICE-unix/dcop53"..., 4096) = 51
close(3)= 0
munmap(0xb7ffe000, 4096)= 0
socket(PF_FILE, SOCK_STREAM, 0) = 3
uname({sys="Linux", node="glab", ...}) = 0
connect(3, {sa_family=AF_FILE, path="/tmp/.ICE-unix/dcop5335-1106811332"},
37) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
write(3, "\0\1\0\0\0\0\0\0", 8) = 8
read(3, "\0\1\0\0\0\0\0\0", 8) = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
read(4, "", 4096) = 0
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, "\0\2\1\1\6\0\0\0\0\0\0\0\0\0\0\0\3\0MIT\0\0\0\3\0001.0"..., 56) =
56
read(3, "\0\3\0\0\1\0\0\0", 8) = 8
read(3, "\0\0\0\0\0\0\0\0", 8) = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, "\0\4\1\1\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307"..., 32)
= 32
read(3, "\0\6\0\0\2\0\0\0", 8) = 8
read(3, "\3\0MIT\0\0\0\3\0001.0\0\0\0", 16) = 16
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
read(4, "", 4096) = 0
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, "\0\7\1\0\7\0\0\0\1\1\0\0\0\0\0\0\4\0DCOPN\257\3\0KDE?\336"..., 64)
= 64
read(3, "\0\3\0\0\1\0\0\0", 8) = 8
read(3, "\0\0MIT\0\0\0", 8) = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
close(4)= 0
munmap(0xb7ffe000, 4096)= 0
write(3, "\0\4\1\0\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307"..., 32)
= 32
read(3, "\0\10\0\2\2\0\0\0", 8) = 8
read(3, "\3\0KDE\0\0\0\3\0002.0\0\0\0", 16) = 16
getsockopt(3, SOL_SOCKET, SO_PEERCRED, "\327\24\0\0\350\3\0\0\350\3\0\0",
[12]) = 0
getuid32() = 1000
getpid()= 7877
write(3, "\1\2\1\0H\0\0\0\0\0\0\0", 12) = 12
write(3, "\0\0\0\0\0\0\0\vDCOPServer\0\0\0\0\1\0\0\0\0\25regi"..., 53) = 53
write(3, "\0\0\0\17anonymous-7877\0", 19) = 19
read(3, "\2\3\0\0027\0\0\0", 8) = 8
read(3, "\240\0\0\0", 4)= 4
read(3, "\0\0\0\vDCOPServer\0\0\0\0\0\0\0\0\tQCString\0"..., 55) = 55
write(3, "\1\2\1\0[\0\0\0\240\0\0\0", 12) = 12
write(3, "\0\0\0\17anonymous-7877\0\0\0\0\vDCOPServe"..., 81) = 81
write(3, "\0\0\0\6kmail\0", 10) = 10
read(3, "\2\3\0\0023\0\0\0", 8) =
Bug#321102: KMail with RC-Bugs moved to testing?
Hi Devs, 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. Best regards, Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KMail with RC-Bugs moved to testing?
Hi Devs, 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. Best regards, Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
