[kmail2] [Bug 368014] Kmail tooltip icon is really pixellated
https://bugs.kde.org/show_bug.cgi?id=368014 Laurent Montelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #3 from Laurent Montel --- now we use breeze icons. So it's ok. Reopen if you see pb in new version 5.3.x Regards -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 rynolang...@gmail.com changed: What|Removed |Added CC||rynolang...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368014] Kmail tooltip icon is really pixellated
https://bugs.kde.org/show_bug.cgi?id=368014 Eike Heinchanged: What|Removed |Added Product|plasmashell |kmail2 Component|Task Manager|general Target Milestone|1.0 |--- Version|5.7.3 |unspecified Assignee|h...@kde.org|kdepim-bugs@kde.org --- Comment #2 from Eike Hein --- This is caused by KMail installing a wrong .desktop file name, which makes libtaskmanager unable to identify the window and fall back to a suboptimal codepath for loading the icon asset. The KMail devs have been informed about this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Alejandro Lorenzochanged: What|Removed |Added CC||alejandro_a...@yahoo.es --- Comment #58 from Alejandro Lorenzo --- I am also experiencing this bug with Kmail and i think i have found the problem. Some CardDav clients, when creating an .ics file in a remote resource (E.g. owncloud in its caldav resource) creates a VCALENDAR file that does not contain the tag "VERSION:2.0" which declares the file conforming to VCALENDAR files version 2.0 I have manually accessed the caldav storage and added the VERSION:2.0 line to an owncloud created file and it immediately syncs into korganizer According to the RFC that defines iCal, VERSION is mandatory and owncloud is not including it, so korganizer is actually doing the right thing (i think) which is to ignore the file The relevant bug in owncloud is: https://github.com/owncloud/core/issues/23715 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 --- Comment #1 from Ian--- *** Bug 367632 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 Ianchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Ian --- duplicate of 368016 *** This bug has been marked as a duplicate of bug 368016 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368016] New: Kmail2 (v5.3.0) Crash at will on startup
https://bugs.kde.org/show_bug.cgi?id=368016 Bug ID: 368016 Summary: Kmail2 (v5.3.0) Crash at will on startup Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160812) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: All i had done was load kmail2 and it displayed everything as normal, i didn;t have chance to click on anything The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fceca853940 (LWP 4257))] Thread 34 (Thread 0x7fcdb1cac700 (LWP 4350)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fceb3960129 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fceb3960840 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fceb3960a10 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fceb395d5cd in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcebd488474 in start_thread (arg=0x7fcdb1cac700) at pthread_create.c:333 #6 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fce33dab700 (LWP 4343)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fceae425fc4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fceae426009 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fcebd488474 in start_thread (arg=0x7fce33dab700) at pthread_create.c:333 #4 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 32 (Thread 0x7fce34e10700 (LWP 4331)): #0 0x7fcec75f1a1d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcebcc65036 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcebcc6514c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcec8134aeb in QEventDispatcherGlib::processEvents (this=0x7fce4c002b40, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fcec80dc76a in QEventLoop::exec (this=this@entry=0x7fce34e0fc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fcec7f023b3 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fcec7f072d8 in QThreadPrivate::start (arg=0x3378800) at thread/qthread_unix.cpp:341 #7 0x7fcebd488474 in start_thread (arg=0x7fce34e10700) at pthread_create.c:333 #8 0x7fcec75fa3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 31 (Thread 0x7fce3583b700 (LWP 4320)): #0 0x7fff433c4989 in ?? () #1 0x7fff433c4c61 in clock_gettime () #2 0x7fcec76070a6 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7fce3583a9e0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fcec7fb2d96 in qt_clock_gettime (ts=0x7fce3583a9e0, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fcec8132699 in QTimerInfoList::updateCurrentTime (this=this@entry=0x32da540) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fcec8132c45 in QTimerInfoList::timerWait (this=0x32da540, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fcec8133fde in timerSourcePrepareHelper (timeout=0x7fce3583aab4, src=) at kernel/qeventdispatcher_glib.cpp:126 #9 timerSourcePrepare (source=, timeout=0x7fce3583aab4) at kernel/qeventdispatcher_glib.cpp:159 #10 0x7fcebcc64589 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x7fcebcc64f5b in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7fcebcc6514c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7fcec8134aeb in QEventDispatcherGlib::processEvents (this=0x32da390, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #14 0x7fcec80dc76a in QEventLoop::exec (this=this@entry=0x7fce3583ac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7fcec7f023b3 in QThread::exec (this=) at thread/qthread.cpp:500 #16 0x7fcec7f072d8 in QThreadPrivate::start (arg=0x32d7140) at thread/qthread_unix.cpp:341 #17 0x7fcebd488474 in start_thread (arg=0x7fce3583b700) at pthread_create.c:333 #18 0x7fcec75fa3ed in clone
[kontact] [Bug 368011] New: Kontact crash every time when try to read full story on rss feed
https://bugs.kde.org/show_bug.cgi?id=368011 Bug ID: 368011 Summary: Kontact crash every time when try to read full story on rss feed Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: eierajat@gmail.com Application: kontact (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: When I open any rss news to see full story, it does crash every time. even though I just tried only 2 time - Unusual behavior I noticed: just avoide to read feed full story The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe5cc64800 (LWP 8678))] Thread 7 (Thread 0x7efdd6490700 (LWP 8734)): #0 0x7efe541cb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efdd74f9d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7efdd74fa819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7efdd6c91700 (LWP 8733)): #0 0x7efe541cb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efdd74f9d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7efdd74fa819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7efdd7492700 (LWP 8732)): #0 0x7efe541cb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efdd74f9d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7efdd74fa819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7efdf05da700 (LWP 8683)): #0 0x7efe5a13abfd in poll () at /lib64/libc.so.6 #1 0x7efe53bfae64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efe53bfaf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efe5a939fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7efe5a90bd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7efe5a90c045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7efe5a8094df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7efe5a80bbbf in () at /usr/lib64/libQtCore.so.4 #8 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7efdff764700 (LWP 8680)): #0 0x7efe541cb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe590c5b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7efe5937aa06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7efe40077700 (LWP 8679)): #0 0x7efe541cb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe59352eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7efe59352ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7efe541c70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe5a14302d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7efe5cc64800 (LWP 8678)): [KCrash Handler] #6 0x7efe58fc93a7 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () at /usr/lib64/libQtWebKit.so.4 #7 0x7efe57fa1a5c in WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle, void*, JSC::SlotVisitor&) () at /usr/lib64/libQtWebKit.so.4 #8 0x7efe590c4a9a in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () at /usr/lib64/libQtWebKit.so.4 #9 0x7efe590d233b in JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () at /usr/lib64/libQtWebKit.so.4 #10 0x7efe590c7785 in JSC::Heap::markRoots(bool) () at /usr/lib64/libQtWebKit.so.4 #11 0x7efe590c9355 in JSC::Heap::collect(JSC::Heap::SweepToggle) () at /usr/lib64/libQtWebKit.so.4 #12 0x7efe5929c872 in JSC::DefaultGCActivityCallback::doWork() () at /usr/lib64/libQtWebKit.so.4 #13 0x7efe590cc3bd in
[kmail2] [Bug 362995] KMail identity configuration loses selected spellcheck dictionary
https://bugs.kde.org/show_bug.cgi?id=362995 --- Comment #3 from d...@newtech.fi --- Reported this earlier: https://bugs.kde.org/show_bug.cgi?id=360071 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362995] KMail identity configuration loses selected spellcheck dictionary
https://bugs.kde.org/show_bug.cgi?id=362995 d...@newtech.fi changed: What|Removed |Added CC||d...@newtech.fi --- Comment #2 from d...@newtech.fi --- Happens to me too. kmail 4.14.10 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] New: quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 Bug ID: 367998 Summary: quick-search field does not receive some keys Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Version 5.3.0 (QtWebEngine) When using the quick-search filter field above the folder tree, I can no longer enter some characters, e.g. typing "cvs" would just enter "cv" and after the v the focus is gone from this field. It seems to me that all characters which are shortcuts (as "v" is for "view source") trigger this problem. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367997] New: regression: clicking on HTML Side Bar can no longer toggle html/plain text
https://bugs.kde.org/show_bug.cgi?id=367997 Bug ID: 367997 Summary: regression: clicking on HTML Side Bar can no longer toggle html/plain text Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at In kmail2/KDE4 I could click on the left HTML Side Bar in the message viewer to toggle between plain-text and HTML display of a mail which had both body parts available. kmail 5.3.0 now still shows in the tooltip that "toggle" shall be possible, but I can only switch from plain-text to HTML but not back. The mail I'm seeing has Content-Type: multipart/alternative; First part is Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable next part is Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Frits Spiekerchanged: What|Removed |Added CC||s.pa...@spiekerbros.com --- Comment #1 from Frits Spieker --- I am "glad" I am not the only one. Have exactly the same error. -- You are receiving this mail because: You are the assignee for the bug.
[kmail] [Bug 201080] The composer window does not appear when running KMail from an NX xterm session
https://bugs.kde.org/show_bug.cgi?id=201080 --- Comment #7 from Tristan Miller--- I can confirm that the problem still occurs with KMail 4.14.10. Please reopen and reassign this bug. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 367992] Blacked notes tiled over my monitors
https://bugs.kde.org/show_bug.cgi?id=367992 Rafaelchanged: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #1 from Rafael --- Created attachment 100848 --> https://bugs.kde.org/attachment.cgi?id=100848=edit My desktop filled with black notes everywhere. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 367992] New: Blacked notes tiled over my monitors
https://bugs.kde.org/show_bug.cgi?id=367992 Bug ID: 367992 Summary: Blacked notes tiled over my monitors Product: knotes Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rafael.linux.u...@gmail.com CC: myr...@kde.org Distro: openSUSE 20160822 (x86_64) VERSION = 20160822 CODENAME = Tumbleweed Kernel: 4.7.1-1-default x86_64 (64 bit) Desktop KDE Frameworks 5.24.0 Qt 5.6.1 Knotes 16.04.3-2.1 After upgrading to KDE 5.24.0, all my notes appears filling my (two) monitors, tiled. They all: - Have a black background - The text remains black, so no legible text at all. - Font title is not default (now is "!Y2KBUG" font, the very first of installed fonts. - Moving a note is not smooth, but doing "jumps" from the point of title bar I'm clicking on. If I change background and text color of one note, they are only changing after I close and launch again Knotes. Usually, I need to close and launch again Knotes to make it to load notes. In other case, is like there were no notes. Reproducible: Always Steps to Reproduce: 1.Launch Knotes Actual Results: All notes are visible, tiled, with black background and uncontrollable on dragging. Expected Results: To show notes like default config. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367779] kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 Denis Kurzchanged: What|Removed |Added CC||a...@cryptomilk.org --- Comment #3 from Denis Kurz --- *** Bug 367836 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367955] Crash at startup
https://bugs.kde.org/show_bug.cgi?id=367955 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 367779 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367836] kontact always crashes on exit
https://bugs.kde.org/show_bug.cgi?id=367836 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 367779 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367779] kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 Denis Kurzchanged: What|Removed |Added CC||crgla...@gmail.com --- Comment #2 from Denis Kurz --- *** Bug 367955 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367566] Crashed creating filter
https://bugs.kde.org/show_bug.cgi?id=367566 Denis Kurzchanged: What|Removed |Added CC||pascal.vo...@freesbee.fr --- Comment #2 from Denis Kurz --- *** Bug 367794 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 367794] mail crash when importing archived messages
https://bugs.kde.org/show_bug.cgi?id=367794 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 367566 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367964] kmail crashes on editing filter rule
https://bugs.kde.org/show_bug.cgi?id=367964 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 367566 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367566] Crashed creating filter
https://bugs.kde.org/show_bug.cgi?id=367566 Denis Kurzchanged: What|Removed |Added CC||marara...@gmx.net --- Comment #3 from Denis Kurz --- *** Bug 367964 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.