[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #14 from Jesse DuBord --- (In reply to Laurent Montel from comment #13) > (In reply to Jesse DuBord from comment #11) > > (In reply to Laurent Montel from comment #10) > > > (In reply to Jesse DuBord from comment #9) > > > > > Indeed but akonadi doesn't allow it. > > > > > We can't duplicate it directly we must to recreate it. > > > > > I fixed a lot of bug for reducing to ask this info but it's not > > > > > possible to > > > > > reduce all. > > > > > > > > So what is the expected behavior from the developer's end. When > > > > importing a > > > > compressed file, and when it says "please choose a folder" for specified > > > > email folder, but no folder exists, what are you expecting us to do? > > > > > > By default you have a folder, if you don't have default inbox/outbox etc > > > it's a bug :) > > > > 1. So you're expecting users to assign their Gmail (IMAP) folders to the > > local folder, when the default behavior when Kontact adds a new account is > > to create a new IMAP folder scheme? > > Why it's an imap account => when we will sync resource it will create > folders... > > > > > 2. What if I have multiple email addresses I manage with Kmail, not just > > one? I have my personal one, and my business one. How am I expected to > > import both? > > What is the problem ? When you export them you export all emails/accounts. > > > > > > 3. If Akonadi has the ability to create folders upon a new account creation, > > why can't the same processes be used when importing accounts? > > I don't understand your problem here ? > > > > > > I feel there are solutions to this that aren't implemented > > Really ?:) good :) > > , so I'm > > re-opening this bug. I greatly appreciate Kontact/Kmail as a product and all > > of the hard work you're doing. There is a solution that can easily satisfy > > the end-user experience, I feel we just need to find the right one to get > > there. As of right now the implementation simply doesn't work with the pim > > setting exporter, specifically during import of the data. Needing to specify > > folders instead of a more straight-forward import approach (e.g. "Oh, this > > is how it was set up on your source version of Kontact? Okay, we'll set it > > up just like it was using the export file you provided". Simple by default, > > powerful when needed, right? IMO, simplicity should be the goal of the > > importing process. > > > > It's less time for me to simply add the accounts manually than to use a tool > > that seems to offer a quicker and simpler set-up experience. So I want to help be a part of the solution. What will help resolve this matter, effectively? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #13 from Laurent Montel --- (In reply to Jesse DuBord from comment #11) > (In reply to Laurent Montel from comment #10) > > (In reply to Jesse DuBord from comment #9) > > > > Indeed but akonadi doesn't allow it. > > > > We can't duplicate it directly we must to recreate it. > > > > I fixed a lot of bug for reducing to ask this info but it's not > > > > possible to > > > > reduce all. > > > > > > So what is the expected behavior from the developer's end. When importing > > > a > > > compressed file, and when it says "please choose a folder" for specified > > > email folder, but no folder exists, what are you expecting us to do? > > > > By default you have a folder, if you don't have default inbox/outbox etc > > it's a bug :) > > 1. So you're expecting users to assign their Gmail (IMAP) folders to the > local folder, when the default behavior when Kontact adds a new account is > to create a new IMAP folder scheme? Why it's an imap account => when we will sync resource it will create folders... > > 2. What if I have multiple email addresses I manage with Kmail, not just > one? I have my personal one, and my business one. How am I expected to > import both? What is the problem ? When you export them you export all emails/accounts. > > 3. If Akonadi has the ability to create folders upon a new account creation, > why can't the same processes be used when importing accounts? I don't understand your problem here ? > > I feel there are solutions to this that aren't implemented Really ?:) good :) , so I'm > re-opening this bug. I greatly appreciate Kontact/Kmail as a product and all > of the hard work you're doing. There is a solution that can easily satisfy > the end-user experience, I feel we just need to find the right one to get > there. As of right now the implementation simply doesn't work with the pim > setting exporter, specifically during import of the data. Needing to specify > folders instead of a more straight-forward import approach (e.g. "Oh, this > is how it was set up on your source version of Kontact? Okay, we'll set it > up just like it was using the export file you provided". Simple by default, > powerful when needed, right? IMO, simplicity should be the goal of the > importing process. > > It's less time for me to simply add the accounts manually than to use a tool > that seems to offer a quicker and simpler set-up experience. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #12 from Jesse DuBord --- If I need to create a separate bug for Akonadi to help this process along and reference it, here, I can do that. Keep in mind I'm not a developer, I'm just an open-source user who loves what you all do, so I'm trying to contribute with the best, most constructive feedback that I can. :) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 Jesse DuBord changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #11 from Jesse DuBord --- (In reply to Laurent Montel from comment #10) > (In reply to Jesse DuBord from comment #9) > > > Indeed but akonadi doesn't allow it. > > > We can't duplicate it directly we must to recreate it. > > > I fixed a lot of bug for reducing to ask this info but it's not possible > > > to > > > reduce all. > > > > So what is the expected behavior from the developer's end. When importing a > > compressed file, and when it says "please choose a folder" for specified > > email folder, but no folder exists, what are you expecting us to do? > > By default you have a folder, if you don't have default inbox/outbox etc > it's a bug :) 1. So you're expecting users to assign their Gmail (IMAP) folders to the local folder, when the default behavior when Kontact adds a new account is to create a new IMAP folder scheme? 2. What if I have multiple email addresses I manage with Kmail, not just one? I have my personal one, and my business one. How am I expected to import both? 3. If Akonadi has the ability to create folders upon a new account creation, why can't the same processes be used when importing accounts? I feel there are solutions to this that aren't implemented, so I'm re-opening this bug. I greatly appreciate Kontact/Kmail as a product and all of the hard work you're doing. There is a solution that can easily satisfy the end-user experience, I feel we just need to find the right one to get there. As of right now the implementation simply doesn't work with the pim setting exporter, specifically during import of the data. Needing to specify folders instead of a more straight-forward import approach (e.g. "Oh, this is how it was set up on your source version of Kontact? Okay, we'll set it up just like it was using the export file you provided". Simple by default, powerful when needed, right? IMO, simplicity should be the goal of the importing process. It's less time for me to simply add the accounts manually than to use a tool that seems to offer a quicker and simpler set-up experience. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 408675] Kontact random crashes
https://bugs.kde.org/show_bug.cgi?id=408675 --- Comment #1 from Christoph Feck --- Unfortunately, the backtrace does not reveal much information. It seems related to timers firing while a menu was up (local event loop). Relevant part of backtrace: Thread 1 (Thread 0x7f21c2668340 (LWP 17420)): [KCrash Handler] #5 0x7f21d127e208 in QBasicTimer::stop() () at /usr/lib/libQt5Core.so.5 #6 0x7f21d202f6f1 in () at /usr/lib/libQt5Widgets.so.5 #7 0x7f21d202f7a8 in QMenu::enterEvent(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #8 0x7f21d1ed19b0 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x7f21d2033a9b in QMenu::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f21d1e84592 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f21d1e8b378 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f21d1280708 in QCoreApplication::sendEvent(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f21d1e89ce8 in () at /usr/lib/libQt5Widgets.so.5 #14 0x7f21d1ef0f62 in () at /usr/lib/libQt5Widgets.so.5 #15 0x7f21d1ef349f in () at /usr/lib/libQt5Widgets.so.5 #16 0x7f21d1e84592 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f21d1e8b378 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f21d12808c8 in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f21d184df40 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #20 0x7f21d184f93b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #21 0x7f21d182082b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #22 0x7f21b555d9ba in () at /usr/lib/libQt5XcbQpa.so.5 #23 0x7f21c620a8dd in g_main_dispatch (context=0x7f21b0004fd0) at ../glib/gmain.c:3189 #24 0x7f21c620a8dd in g_main_context_dispatch (context=context@entry=0x7f21b0004fd0) at ../glib/gmain.c:3854 #25 0x7f21c620ab68 in g_main_context_iterate (context=context@entry=0x7f21b0004fd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:3927 #26 0x7f21c620abec in g_main_context_iteration (context=0x7f21b0004fd0, may_block=1) at ../glib/gmain.c:3988 #27 0x7f21d12df0e0 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7f21d127ee16 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #29 0x7f21d202ccdd in QMenu::exec(QPoint const&, QAction*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409456] New: KMail can not deal with PGP messages sent by Exchange
https://bugs.kde.org/show_bug.cgi?id=409456 Bug ID: 409456 Summary: KMail can not deal with PGP messages sent by Exchange Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fab...@ritter-vogt.de Target Milestone: --- Exchange (in this case Office 356) mangles PGP encrypted messages when sending. Content-Type: multipart/encrypted; boundary="nextPart6734939.BlDrd8uHN9"; protocol="application/pgp-encrypted" ends up as Content-Type: multipart/mixed; boundary="_003_2390612FqyDRV8H2nlinuxe202susede_" And so KMail is unable to show the mail correctly. By editing the content-type to say multipart/encrypted, it's displayed correctly. See also https://gitlab.com/enigmail/enigmail/blob/master/package/fixExchangeMsg.jsm#L224 how enigmail deals with this. -- You are receiving this mail because: You are the assignee for the bug.
[kmail] [Bug 33044] pgp not adding headers
https://bugs.kde.org/show_bug.cgi?id=33044 Harald Sitter changed: What|Removed |Added CC||olivier.dela...@wanadoo.fr --- Comment #4 from Harald Sitter --- *** Bug 352139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 373988] KOrganiser time zone locked to UTC and not possible to change.
https://bugs.kde.org/show_bug.cgi?id=373988 Roman Fietze changed: What|Removed |Added CC||k...@fietze-home.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409110 Severity|normal |crash --- Comment #1 from Christoph Feck --- Pasting relevant part of backtrace inline: hread 7 (Thread 0x7fd73affd700 (LWP 3378)): [KCrash Handler] #6 qHash (key=..., seed=222126091) at ../../include/QtCore/../../src/corelib/tools/qstring.h:239 #7 0x55bc0c6685db in QHash::findNode (this=this@entry=0x55bc0d32dae8, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:928 #8 0x55bc0c66864a in QHash::remove (this=this@entry=0x55bc0d32dae8, akey=...) at /usr/include/qt5/QtCore/qrefcount.h:102 #9 0x55bc0c666d72 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55bc0d32dab0, request=0x7fd6cc082e70, errorMsg=...) at /usr/src/debug/akonadi-server-19.04.2-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:227 #10 0x7fd745f3cb78 in QtPrivate::QSlotObjectBase::call (a=0x7fd73affc700, r=0x55bc0d32dab0, this=0x7fd720006730) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=0x7fd73c01e530, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3776 #12 0x55bc0c6b1b94 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7fd73c01e530, _t1=, _t2=...) at /usr/src/debug/akonadi-server-19.04.2-1.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:135 #13 0x55bc0c668f23 in Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7fd73c01e530, watcher=) at /usr/include/qt5/QtCore/qchar.h:88 #14 0x7fd745f3cb78 in QtPrivate::QSlotObjectBase::call (a=0x7fd73affc8c0, r=0x7fd73c01e530, this=0x7fd720006bd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #15 QMetaObject::activate (sender=0x7fd720006b10, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3776 #16 0x7fd74628bd7f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:157 #17 0x7fd74628be80 in QDBusPendingCallWatcherPrivate::_q_finished (this=) at qdbuspendingcall.cpp:494 #18 QDBusPendingCallWatcher::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/moc_qdbuspendingcall.cpp:85 #19 0x7fd745f3d43a in QObject::event (this=0x7fd720006b10, e=) at kernel/qobject.cpp:1260 #20 0x7fd745f11e6f in doNotify (event=0x7fd73c01ef80, receiver=0x7fd720006b10) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:142 #21 QCoreApplication::notify (event=0x7fd73c01ef80, receiver=0x7fd720006b10, this=) at kernel/qcoreapplication.cpp:1136 #22 QCoreApplication::notifyInternal2 (receiver=0x7fd720006b10, event=0x7fd73c01ef80) at kernel/qcoreapplication.cpp:1060 #23 0x7fd745f14a88 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55bc0d3917c0) at kernel/qcoreapplication.cpp:1799 #24 0x7fd745f687c3 in postEventSourceDispatch (s=0x7fd720004fb0) at kernel/qeventdispatcher_glib.cpp:276 #25 0x7fd7444b3b33 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7fd7444b3dc0 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7fd7444b3e4f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7fd745f67e01 in QEventDispatcherGlib::processEvents (this=0x7fd72b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #29 0x7fd745f10bdb in QEventLoop::exec (this=this@entry=0x7fd73affcca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #30 0x7fd745d52751 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #31 0x7fd745d538d2 in QThreadPrivate::start (arg=0x55bc0d3916f0) at thread/qthread_unix.cpp:361 #32 0x7fd74512afaa in start_thread () from /lib64/libpthread.so.0 #33 0x7fd7459c871f in clone () from /lib64/libc.so.6 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409110] Akonadi Server crash after some time of having Kontact running
https://bugs.kde.org/show_bug.cgi?id=409110 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408897 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 408869] Akregator krash at starup on remote X session
https://bugs.kde.org/show_bug.cgi?id=408869 --- Comment #1 from Christoph Feck --- Do other OpenGL applications work in remote X sessions? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 408732] Support for SMTP BURL extension (RFC 4468)
https://bugs.kde.org/show_bug.cgi?id=408732 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).
https://bugs.kde.org/show_bug.cgi?id=409293 --- Comment #10 from Laurent Montel --- (In reply to Jesse DuBord from comment #9) > > Indeed but akonadi doesn't allow it. > > We can't duplicate it directly we must to recreate it. > > I fixed a lot of bug for reducing to ask this info but it's not possible to > > reduce all. > > So what is the expected behavior from the developer's end. When importing a > compressed file, and when it says "please choose a folder" for specified > email folder, but no folder exists, what are you expecting us to do? By default you have a folder, if you don't have default inbox/outbox etc it's a bug :) -- You are receiving this mail because: You are the assignee for the bug.
