[kholidays] [Bug 359708] Updated holiday file for Ukraine
https://bugs.kde.org/show_bug.cgi?id=359708 --- Comment #9 from 38dosb+99yi2ktucs...@guerrillamailblock.com --- Created attachment 104196 --> https://bugs.kde.org/attachment.cgi?id=104196&action=edit A holiday file with conditional expressions Sorry for my prolonged absence. I've attached a holiday file with the conditionals. It has been tested against KDE 4 only. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 332624] NFS support
https://bugs.kde.org/show_bug.cgi?id=332624 Bug 332624 depends on bug 275261, which changed state. Bug 275261 Summary: Akonadi on NFS mounted home directories is very fragile https://bugs.kde.org/show_bug.cgi?id=275261 What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 275261] Akonadi on NFS mounted home directories is very fragile
https://bugs.kde.org/show_bug.cgi?id=275261 Daniel Vrátil changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #14 from Daniel Vrátil --- Reopening, NFS support is still rather fragile :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376852] Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375104] Crash during shutdown: ASSERT: "mDev" in datastream_p_p.h:89
https://bugs.kde.org/show_bug.cgi?id=375104 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátil changed: What|Removed |Added CC||kde...@posteo.de --- Comment #28 from Daniel Vrátil --- *** Bug 375104 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátil changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #27 from Daniel Vrátil --- *** Bug 375450 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375450] akonadiserver crashes on system shudown
https://bugs.kde.org/show_bug.cgi?id=375450 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375558] Akonadiserver crashes on restart
https://bugs.kde.org/show_bug.cgi?id=375558 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 --- Comment #26 from Daniel Vrátil --- *** Bug 375558 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátil changed: What|Removed |Added CC||kosse...@kde.org --- Comment #25 from Daniel Vrátil --- *** Bug 375714 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 375714] Crash on akonadictl stop (while filteragent was hanging)
https://bugs.kde.org/show_bug.cgi?id=375714 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátil changed: What|Removed |Added CC||a...@cryptomilk.org --- Comment #24 from Daniel Vrátil --- *** Bug 376852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376852] Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátil changed: What|Removed |Added Severity|critical|normal CC||dvra...@kde.org Version Fixed In||5.4.3 Latest Commit||https://commits.kde.org/ako ||nadi/5219f770b998aad16a3d51 ||bbd4f4c7ceb8b143c9 --- Comment #23 from Daniel Vrátil --- The crash itself has been fixed by commit https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 which will be in Akonadi 5.4.3 (KDE Applications 16.12.3) in March. The patch fixes the crash itself, but does not address the underlying problem. I'll keep this opened until the underlying problem is resolved. --- Notes for future me: The root cause is the nested QEventLoop in ItemRetriever::exec(). When Connection is terminated (by server shutdown or connection loss on socket) while the nested QEventLoop in ItemRetriever is running, Connection::quit() will be invoked from the nested loop, destroying certain resources (socket, datastore). This then leads to various crashes once the nested event loop ends and execution within ItemRetriever::exec() continues. I don't think it's possible to prevent nested event loop from executing metacalls on Connection, after all the main reason for using QEventLoop in ItemRetriever was to make it more interactive and interruptable. Connection::quit() cannot directly terminate the nested QEventLoop, because it has been invoked from it. It could however use delay invocation to quit the loop and return early without actually quiting and destroying the thread. The thread would quit once the excecution would return from the Handler back to Connection::slotNewData(). Connection::quit() could probably set a flag or something. However it's not clear how Connection::quit() should detect where it's invoked from and whether it's a nested QEL or not, and how it should interact with it. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 --- Comment #3 from Christoph Feck --- On 23.02.2017 19:18, eric.v...@msg4.us wrote: > Hi Christophe, > I'm sorry that the bug report system is unable to find a bug that > appears every other day and reported with the same title from the same > person > > That's why I HAVE to create a new one each time. > > I can feel your frustration, please consider mine. > > It's also unfortunate that KDE is not suggesting Kmail/Kontact update, > even though I zypper patch AND Zypper up every other day if not every day > > I will do a manual specific update of the package, hopping it won't > smash all my simlinks, it took me ages to find them all and simlink them > one by one > > Thks again for your support ! > Eric > A long time user still novice ;) > > > On 2017-02-22 22:39, Christoph Feck wrote: >> https://bugs.kde.org/show_bug.cgi?id=376654 >> >> Christoph Feck changed: >> >>What|Removed |Added >> >> >> Resolution|--- |INVALID >> Status|UNCONFIRMED |RESOLVED >> >> --- Comment #1 from Christoph Feck --- >> Already reported, and I am not going to search it again. >> >> Please update your software, we already released KMail 5.3 and KMail 5.4. > Hi Eric, I suggest to ask in a forum of your distribution how to update to openSUSE Leap 42.2. It ships with KMail 5.3.x, not the newest, but still should fix at least some of your issues. Manually updating packages from non-standard repositories is also possible, but only recommended for more experienced users. Christoph Feck KDE Bug Triaging team -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376385] Restarting Akonadi while it fails to deliver content to frontend makes it crash
https://bugs.kde.org/show_bug.cgi?id=376385 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/ako ||nadi/5219f770b998aad16a3d51 ||bbd4f4c7ceb8b143c9 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.4.3 --- Comment #1 from Daniel Vrátil --- Git commit 5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 by Daniel Vrátil. Committed on 23/02/2017 at 18:45. Pushed by dvratil into branch 'Applications/16.12'. DataStream: throw exception if device is null During Connection destruction it can happen that the socket is deleted, but the actual handler is still running and tries to write to that socket (in which case it passes a nullptr to DataStream). This is caused by the issue described in #376822. To prevent the crash in this case (until the root cause is fixed) the DataStream throws an exception if its used without a valid device. This will effectively cause execution to leave the Handler and return. FIXED-IN: 5.4.3 M +5-2src/private/datastream_p.cpp M +10 -6src/private/datastream_p_p.h https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376791] akonadiserver crash in moveToRoot () at /lib64/libsqlite3.so.0
https://bugs.kde.org/show_bug.cgi?id=376791 --- Comment #2 from PC LX --- SQLite3 version info: # sqlite3 --version 3.14.2 2016-09-12 18:50:49 29dbef4b8585f753861a36d6dd102ca634197bd6 # rpm -qa | grep -i sqlite | sort lib64qt4-database-plugin-sqlite-4.8.7-14.mga6 lib64qt5-database-plugin-sqlite-5.6.2-6.mga6 lib64sqlite3_0-3.14.2-5.mga6 lib64vsqlite++3-0.3.12-7.mga6 libsqlite3_0-3.14.2-5.mga6 sqlite3-tools-3.14.2-5.mga6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376791] akonadiserver crash in moveToRoot () at /lib64/libsqlite3.so.0
https://bugs.kde.org/show_bug.cgi?id=376791 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Looks like a bug in SQLite. Could you please check which version of sqlite3 do you have? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue
https://bugs.kde.org/show_bug.cgi?id=376822 Daniel Vrátil changed: What|Removed |Added Ever confirmed|0 |1 CC||dvra...@kde.org Priority|NOR |HI Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Daniel Vrátil --- ItemRetriever now uses QEventLoop to wait for request to be processed. If Akonadi Server is shut down during that, the QEventLoop will cause Connection::quit() to be executed, destroying the QSqlDriver and deleting the thread. When the QEventLoop finishes and ItemRetriever::exec() returns, the QSqlQuery() tries to dereference the already-destroyed QSqlDriver. We need a mechanism to either prevent Connection::quit() from being executed while an event loop is running on the Connection, or we need a way to quickly abort ItemRetriever::exec() from Connection::quit() before destroying the SQL connection and the thread. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 --- Comment #2 from Eric --- Hi Christophe, I'm sorry that the bug report system is unable to find a bug that appears every other day and reported with the same title from the same person That's why I HAVE to create a new one each time. I can feel your frustration, please consider mine. It's also unfortunate that KDE is not suggesting Kmail/Kontact update, even though I zypper patch AND Zypper up every other day if not every day I will do a manual specific update of the package, hopping it won't smash all my simlinks, it took me ages to find them all and simlink them one by one Thks again for your support ! Eric A long time user still novice ;) On 2017-02-22 22:39, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=376654 > > Christoph Feck changed: > >What|Removed |Added > > Resolution|--- |INVALID > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Christoph Feck --- > Already reported, and I am not going to search it again. > > Please update your software, we already released KMail 5.3 and KMail > 5.4. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376852] New: Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Bug ID: 376852 Summary: Akonadi server crash Product: Akonadi Version: 5.4.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: a...@cryptomilk.org Target Milestone: --- I'm running KMail 5.4.2 on openSUSE Tumbleweed. After some time it stops working and then it crashes. akonadi-server-16.12.2 Backtrace: Thread 10 (Thread 0x7fdfb97fa700 (LWP 12253)): [KCrash Handler] #6 QScopedPointer >::data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:141 #7 qGetPtrHelper > (p=...) at ../../src/corelib/global/qglobal.h:980 #8 QIODevice::d_func (this=0x0) at ../../src/corelib/io/qiodevice.h:178 #9 QIODevice::write (this=0x0, data=data@entry=0x7fdfb97f93ec "\227", maxSize=maxSize@entry=1) at io/qiodevice.cpp:1596 #10 0x7fe044385bc0 in Akonadi::Protocol::DataStream::operator<< (this=0x7fdfb97f9470, val=) at /usr/src/debug/akonadi-16.12.2/src/private/datastream_p_p.h:91 #11 0x7fe04438932f in Akonadi::Protocol::CommandPrivate::serialize (stream=..., this=0x7fdf98011a00) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:266 #12 Akonadi::Protocol::ResponsePrivate::serialize (stream=..., this=0x7fdf98011a00) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:425 #13 Akonadi::Protocol::FetchItemsResponsePrivate::serialize (this=0x7fdf98011a00, stream=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:3344 #14 0x7fe0443709b4 in Akonadi::Protocol::operator<< (command=..., stream=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:383 #15 Akonadi::Protocol::serialize (device=, command=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:636 #16 0x0042cde3 in Akonadi::Server::Connection::sendResponse (this=0x1d6cef0, tag=1339, response=...) at /usr/src/debug/akonadi-16.12.2/src/server/connection.cpp:404 #17 0x00431272 in Akonadi::Server::Handler::sendResponse (response=..., this=0x7fdf9800d160) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:268 #18 Akonadi::Server::Handler::sendResponse (this=0x7fdf9800d160, response=...) at /usr/src/debug/akonadi-16.12.2/src/server/handler.h:152 #19 Akonadi::Server::Handler::failureResponse (this=this@entry=0x7fdf9800d160, failureMessage=...) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:261 #20 0x0043142f in Akonadi::Server::Handler::failureResponse (this=0x7fdf9800d160, failureMessage=) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:252 #21 0x0042efbd in Akonadi::Server::Connection::slotNewData (this=0x1d6cef0) at /usr/src/debug/akonadi-16.12.2/src/server/connection.cpp:252 #22 0x7fe0434a1a7e in QtPrivate::QSlotObjectBase::call (a=0x7fdfb97f98d0, r=0x1d6cef0, this=) at ../../src/corelib/kernel/qobject_impl.h:101 #23 QMetaObject::activate (sender=0x7fdf98002cd0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #24 0x7fe0434a1709 in QMetaObject::activate (sender=0x7fdf98002dc8, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #25 0x7fe0440ac265 in ?? () from /usr/lib64/libQt5Network.so.5 #26 0x7fe0440ac31c in ?? () from /usr/lib64/libQt5Network.so.5 #27 0x7fe0440b7121 in ?? () from /usr/lib64/libQt5Network.so.5 #28 0x7fe043475aeb in doNotify (event=0x7fdfb97f9ae0, receiver=0x7fdf98003060) at kernel/qcoreapplication.cpp:1063 #29 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #30 QCoreApplication::notifyInternal2 (receiver=0x7fdf98003060, event=event@entry=0x7fdfb97f9ae0) at kernel/qcoreapplication.cpp:988 #31 0x7fe0434ca61d in QCoreApplication::sendEvent (event=0x7fdfb97f9ae0, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #32 socketNotifierSourceDispatch (source=0x7fdf98002a00) at kernel/qeventdispatcher_glib.cpp:106 #33 0x7fe03f5ab697 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #34 0x7fe03f5ab900 in ?? () from /usr/lib64/libglib-2.0.so.0 #35 0x7fe03f5ab9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #36 0x7fe0434ca16f in QEventDispatcherGlib::processEvents (this=0x7fdf980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #37 0x7fe043473aea in QEventLoop::exec (this=this@entry=0x7fdfb97f9d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #38 0x7fe0432a1813 in QThread::exec (this=) at thread/qthread.cpp:507 #39 0x7fe0432a64c8 in QThreadPrivate::start (arg=0x1d69380) at thread/qthread_unix.cpp:368 #40 0x7fe0417c8454 in start_thread (arg=0x7fdfb97fa700) at pthread_create.c:333 #41 0x7fe04299c37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 358559] akonadi_imap_resource incorrectly handles RFC 5464
https://bugs.kde.org/show_bug.cgi?id=358559 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Could you please run the following in terminal: export KIMAP_LOGFILE=/tmp/kimap.log akonadictl restart Then reproduce the issue again (wait until you see the error in terminal). After that look into /tmp folder, you should see several files starting with kimap.log - find the one that contains the error line and paste it here. Please also include a few (5 or so) lines above the error. If there are any sensitive information (folder names for instance), you can sanitize them. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 376379] Calendar folder name cannot be changed for iCal resources
https://bugs.kde.org/show_bug.cgi?id=376379 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||pim-runtime/c551ad2f4dc3a82 ||9241aec05eb343de020fee67f Status|UNCONFIRMED |RESOLVED Version Fixed In||5.4.3 Resolution|--- |FIXED --- Comment #1 from Daniel Vrátil --- Git commit c551ad2f4dc3a829241aec05eb343de020fee67f by Daniel Vrátil. Committed on 23/02/2017 at 17:42. Pushed by dvratil into branch 'Applications/16.12'. Preserve icaldir resource/collection display name Match the root collection's display name to AgentBase::name() and update the agent name when user modifies the root collection's name. This way it's possible to persistently customize icaldir resource names instead of having multiple "Calendar Folder" entries in Korganizer. It also makes the resource visible under the "nice" name in resource listing, instead of using the agent identifier. FIXED-IN: 5.4.3 M +13 -1resources/icaldir/icaldirresource.cpp M +2-0resources/icaldir/icaldirresource.h https://commits.kde.org/kdepim-runtime/c551ad2f4dc3a829241aec05eb343de020fee67f -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 --- Comment #3 from Christian Saemann --- Thanks for your quick reply, this fixed it. I should have probably googled more thoroughly. BTW: You mentioned in the blog post that this bug should be fixed in 16.12.1, I experienced it on 16.12.2 (openSUSE Tumbleweed packages). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Please try the following guide to resolve the problem: http://www.dvratil.cz/2017/01/kmail-multiple-merge-candidates-error-and-how-to-fix-it/ -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 373519] baloo indexer crashed at restart akonadi
https://bugs.kde.org/show_bug.cgi?id=373519 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Daniel Vrátil --- Sorry, but KDE 4 version of KDE PIM is no longer maintained, and the indexing infrastructure has changed significantly since then. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 376584] Action menu missing in addressbook
https://bugs.kde.org/show_bug.cgi?id=376584 --- Comment #5 from Knut Hildebrandt --- One last remark. As much as I know in KDE applications the menu display can be toggled with CTRL-M. At least this works with amarok (still KDE4), dolphin, gwenview, kate, kdenlive, where I use it heavily. In Kontact no reaction. Knut -- You are receiving this mail because: You are on the CC list for the bug.
[akregator] [Bug 358796] Akregator crashes when clicking on specific url
https://bugs.kde.org/show_bug.cgi?id=358796 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 317475 *** -- You are receiving this mail because: You are the assignee for the bug.