[korganizer] [Bug 334460] Korganizer displays "Reminder: 1 minute before the start" when the reminder is actually set to a different number of minutes
https://bugs.kde.org/show_bug.cgi?id=334460 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 335893] coloring of events in month view is unclear
https://bugs.kde.org/show_bug.cgi?id=335893 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 451314] iCloud Synch can only create new events, but doesn't download them from the cloud
https://bugs.kde.org/show_bug.cgi?id=451314 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Component|general |general Product|kdepim |korganizer -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 448106] KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=448106 gjditchfi...@acm.org changed: What|Removed |Added Product|kdepim |korganizer Component|general |general CC||gjditchfi...@acm.org -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 421531] Google calendars cannot be updated through the UI
https://bugs.kde.org/show_bug.cgi?id=421531 gjditchfi...@acm.org changed: What|Removed |Added Component|general |general Product|kdepim |korganizer CC||gjditchfi...@acm.org -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 378299] icalmime.c:182: bad call to memset ?
https://bugs.kde.org/show_bug.cgi?id=378299 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- libical is not a KDE library. It is maintained at https://github.com/libical/libical. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 453292] KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||gjditchfi...@acm.org -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 453304] Getting available smart card readers failed: No data
https://bugs.kde.org/show_bug.cgi?id=453304 Arian Molina changed: What|Removed |Added Version|unspecified |3.1.21.220400 -- You are receiving this mail because: You are on the CC list for the bug.
[kleopatra] [Bug 453304] New: Getting available smart card readers failed: No data
https://bugs.kde.org/show_bug.cgi?id=453304 Bug ID: 453304 Summary: Getting available smart card readers failed: No data Product: kleopatra Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: linuxc...@teknik.io CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- Application: kleopatra (3.1.21.220400 (22.04.0)) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.0-5.1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Preferences were being reviewed, when arriving at the Smartcard menu, the application to Crasshead. The crash can be reproduced every time. -- Backtrace: Application: Kleopatra (kleopatra), signal: Segmentation fault [New LWP 353341] [New LWP 353342] [New LWP 353373] [New LWP 353965] [New LWP 354036] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fcc0914e9cf in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7fcc05392280 (LWP 353335))] Thread 6 (Thread 0x7fcbeb7fe700 (LWP 354036)): #0 0x7fcc0914e9cf in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fcbfc3ae1d6 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fcbfc39f841 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fcbfc39fec3 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fcbfc39ff70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fcbfc3ae11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fcbfc34a72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7fcc0ac3b609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fcc0915b163 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7fcbebfff700 (LWP 353965)): #0 0x7fcc0ac42376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fcc0950168b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x555a2b857989 in ?? () #3 0x7fcc094fb623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc0ac3b609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7fcc0915b163 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7fcbf0cbe700 (LWP 353373)): #0 0x7fcc0ac42376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fcbf663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7fcbf663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7fcc0ac3b609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fcc0915b163 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fcbfefa1700 (LWP 353342)): #0 0x7fcc07fefac0 in g_ptr_array_set_size () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcc0801f7ee in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc0802029b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc080204a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcc0973c65b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc096e087b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcc094fa442 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcc0a841f4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fcc094fb623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcc0ac3b609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7fcc0915b163 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fcc04824700 (LWP 353341)): #0 0x7fcc0914e9cf in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fcc089c3c1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fcc089c590a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fcc04f4f1a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fcc094fb623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc0ac3b609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7fcc0915b163 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7fcc05392280 (LWP 353335)): [KCrash Handler] #4
[Akonadi] [Bug 453299] kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 Till Schäfer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453298] kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 Till Schäfer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 Till Schäfer changed: What|Removed |Added Keywords||regression --- Comment #10 from Till Schäfer --- Bug 453299: kalendarac: Notifications miss option to edit event directly -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453300] New: kalendarac: Notifications click removes the event form notification history
https://bugs.kde.org/show_bug.cgi?id=453300 Bug ID: 453300 Summary: kalendarac: Notifications click removes the event form notification history Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- When clicking a reminder event of kalendarac, the event is highlighted in Korganizer for me. By doing so the notification popup as well as the notification history entry is removed. While the former is expected, the latter makes not sense to me. The notification history should make it possible to re-access the event after the popup disappeared. Removing it from history effectively disables the history feature. On use case of the history would be for example, that someone gets distracted by something else after clicking, but not handling the event. Then it would be useful to just have a look into the history to bring up the event again. Thus, I propose to keep the history entry when clicking an event (i.e., handled such as timeouts). Instead, the history entry should be only removed, when the close button (x) is pressed as for other notification entries. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453299] New: kalendarac: Notifications miss option to edit event directly
https://bugs.kde.org/show_bug.cgi?id=453299 Bug ID: 453299 Summary: kalendarac: Notifications miss option to edit event directly Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- The replacement of korgac does no longer support the direct editing of an event from the reminder popup. I propose to re-implement this previous feature. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 --- Comment #9 from Till Schäfer --- (In reply to Till Schäfer from comment #8) > I would like to add that the new notification also misses the remind later > function for other durations than 5 minutes. > > I used this a lot. For example when I was in a phone call and a reminder > popped up, i said remind me in a hour or so. Now, I am either bothered every > 5 minutes or I have to re-configure the event in Korganizer, which is quite > cumbersome. Bug 453298: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453298] New: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes
https://bugs.kde.org/show_bug.cgi?id=453298 Bug ID: 453298 Summary: kalendarac: Notifications miss option to remind later with other time duration than 5 minutes Product: Akonadi Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- With the removal of korgac, the calendar notifications now miss an option to remind later other than 5 minutes. I had several use cases for this remind later functionality. Here are some examples: 1. I often trigger a reminder well ahead of an event, because I need some time to prepare myself for that event (e.g. read some protocol of a previous meeting). When I am currently doing something else I often delayed the reminder to remind me again when my current doing is no longer interrupted or the other event becomes time critical. With the 5 minutes delay it is impossible to work without disturbance if my current doing is taking another hour or so. 2. Sometimes events span several days (e.g. at some week I am responsible to clean the coffee machine at work). So i configure one reminder each day. However, when I am currently not close to the kitchen, I let me remind later, when I know I am back in office. Of course it is also possible to re-configure an event. However, this i A. very cumbersome B. not very good for periodic events (e.g. the the periodic coffee machine job of example 2) Thus, I propose the re-implement this regressed feature. Operating System: Gentoo Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-gentoo-r1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453297] New: KMail + Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=453297 Bug ID: 453297 Summary: KMail + Akonadi crash Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: kmail (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.60-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.3 -- Information about the crash: KMail and Akonadi crash while retrieving mails. They crash at the same time. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x118, t=@0x7ffc4b94ad90: 0x5624e0fb8680) at ../../include/QtCore/../../src/corelib/tools/qlist.h:584 #9 0x7f7f74aff858 in QWidget::insertAction (this=0x5624e0fb8680, before=, action=0x5624e0ea02b0) at kernel/qwidget.cpp:3314 #10 0x7f7f72ce4fd2 in KXMLGUI::ActionList::plug(QWidget*, int) const () from /usr/lib64/libKF5XmlGui.so.5 #11 0x7f7f72ce8912 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) () from /usr/lib64/libKF5XmlGui.so.5 #12 0x7f7f72ce8ad6 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #13 0x7f7f72ce8b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #14 0x7f7f72ce8b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #15 0x7f7f72ce23eb in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) () from /usr/lib64/libKF5XmlGui.so.5 #16 0x7f7f6e5f6b5d in PimCommon::PluginInterface::initializePluginActions (this=, prefix=..., guiClient=0x5624e405bf10) at /usr/src/debug/pimcommon-20.04.2-bp153.2.2.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168 #17 0x7f7f75c883fe in KMMainWidget::initializePluginActions (this=this@entry=0x5624e478c770) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmmainwidget.cpp:4217 #18 0x7f7f75c8fc83 in KMMainWidget::slotShowStartupFolder (this=0x5624e478c770) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmmainwidget.cpp:4121 #19 0x7f7f73c7ee44 in QtPrivate::QSlotObjectBase::call (a=0x7ffc4b94b1c0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 QSingleShotTimer::timerEvent (this=0x5624e33faac0) at kernel/qtimer.cpp:318 #21 0x7f7f73c729db in QObject::event (this=0x5624e33faac0, e=) at kernel/qobject.cpp:1283 #22 0x7f7f74ac7f9c in QApplicationPrivate::notify_helper (this=this@entry=0x5624e0792f30, receiver=receiver@entry=0x5624e33faac0, e=e@entry=0x7ffc4b94b500) at kernel/qapplication.cpp:3701 #23 0x7f7f74acf5b0 in QApplication::notify (this=0x7ffc4b94bc70, receiver=0x5624e33faac0, e=0x7ffc4b94b500) at kernel/qapplication.cpp:3447 #24 0x7f7f73c42368 in QCoreApplication::notifyInternal2 (receiver=0x5624e33faac0, event=0x7ffc4b94b500) at kernel/qcoreapplication.cpp:1088 #25 0x7f7f73c9e859 in QTimerInfoList::activateTimers (this=0x5624e079b370) at kernel/qtimerinfo_unix.cpp:643 #26 0x7f7f73c9f021 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #27 0x7f7f666a8694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f7f666a8a30 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f7f666a8abc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f7f73c9f3ef in QEventDispatcherGlib::processEvents (this=0x5624e0876d10, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #31 0x7f7f73c405ba in QEventLoop::exec (this=this@entry=0x7ffc4b94b750, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #32 0x7f7f73c497c0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389 #33 0x5624df7cea5b in main (argc=, argv=) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/main.cpp:163 [Inferior 1 (process 8505) detached] Possible duplicates by query: bug 452717, bug 449952, bug 449891, bug 443784, bug 440840. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 340204] Korganizers reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäfer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Till Schäfer --- 22.04 removed korgac and the current implementation does not have the issue anymore -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 452264] Appointment reminder handling reduces usability and functionality between 21.12.3 and 22.03.80
https://bugs.kde.org/show_bug.cgi?id=452264 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #8 from Till Schäfer --- I would like to add that the new notification also misses the remind later function for other durations than 5 minutes. I used this a lot. For example when I was in a phone call and a reminder popped up, i said remind me in a hour or so. Now, I am either bothered every 5 minutes or I have to re-configure the event in Korganizer, which is quite cumbersome. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 453292] New: KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 Bug ID: 453292 Summary: KOrganizer shows wrong month form in headers Product: korganizer Version: 5.20.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-bugs@kde.org Reporter: gregorykku...@gmail.com Target Milestone: --- Created attachment 148513 --> https://bugs.kde.org/attachment.cgi?id=148513=edit The header in question SUMMARY Korganizer uses CLDR's "format" month form instead of "standalone" as the header of its month view (see attachment). In Slavic languages it makes the month name show in genitive case, which is correct only as a part of a full date, not as a calendar header. STEPS TO REPRODUCE 1. Open KOrganizer 2. Click "Month" in the topbar. OBSERVED RESULT The month name in the calendar's header is in genitive. EXPECTED RESULT The month name should be in nominative. -- You are receiving this mail because: You are the assignee for the bug.
