Application: pimsettingexporter (4.14.6) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.16.7-21-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: After the continous problems with migration of kontact, I tried to export a limited set of settings with the exporter. - Unusual behavior I noticed: The thing crashed in the moment I started the procedure. This is the first time I try to export a limited set (to see if a new setup kontact will be still smashed if I avoid all supplemental settings but adresses and mail. So I do not know if this is repeatable yet. In case I will report back. -- Backtrace: Application: Esportatore delle impostazioni di PIM (pimsettingexporter), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f724e1d7800 (LWP 4705))] Thread 3 (Thread 0x7f722981f700 (LWP 4708)): #0 0x00007f7249475c3d in poll () from /lib64/libc.so.6 #1 0x00007f7240013be4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f7240013cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f7249e0f0de in QEventDispatcherGlib::processEvents (this=0x7f72240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x00007f7249de0e6f in QEventLoop::processEvents (this=this@entry=0x7f722981eda0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f7249de1165 in QEventLoop::exec (this=this@entry=0x7f722981eda0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f7249cde0bf in QThread::exec (this=this@entry=0x1dac2d0) at thread/qthread.cpp:538 #7 0x00007f7249dc2783 in QInotifyFileSystemWatcherEngine::run (this=0x1dac2d0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007f7249ce079f in QThreadPrivate::start (arg=0x1dac2d0) at thread/qthread_unix.cpp:349 #9 0x00007f72475ac0a4 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f724947e06d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7228b16700 (LWP 4718)): #0 0x00007f7240055904 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x00007f7240013318 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f7240013b03 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f7240013cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f7249e0f0de in QEventDispatcherGlib::processEvents (this=0x7f721c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x00007f7249de0e6f in QEventLoop::processEvents (this=this@entry=0x7f7228b15da0, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007f7249de1165 in QEventLoop::exec (this=this@entry=0x7f7228b15da0, flags=...) at kernel/qeventloop.cpp:204 #7 0x00007f7249cde0bf in QThread::exec (this=this@entry=0x1e86800) at thread/qthread.cpp:538 #8 0x00007f7249dc2783 in QInotifyFileSystemWatcherEngine::run (this=0x1e86800) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x00007f7249ce079f in QThreadPrivate::start (arg=0x1e86800) at thread/qthread_unix.cpp:349 #10 0x00007f72475ac0a4 in start_thread () from /lib64/libpthread.so.0 #11 0x00007f724947e06d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f724e1d7800 (LWP 4705)): [KCrash Handler] #6 unicode (this=0x2323000) at ../../src/corelib/tools/qchar.h:251 #7 QUtf8::convertFromUnicode (uc=0x1d244b8, len=<optimized out>, state=state@entry=0x0) at codecs/qutfcodec.cpp:91 #8 0x00007f7249d25d0e in QString::toUtf8 (this=this@entry=0x1bc5f50) at tools/qstring.cpp:3793 #9 0x00007f724a1f8753 in KConfigGroup::writeEntry (this=this@entry=0x7fff9b2a9ea0, key=key@entry=0x7f724c8df8cb "name", value=..., flags=...) at /usr/src/debug/kdelibs-4.14.6/kdecore/config/kconfiggroup.cpp:820 #10 0x00007f724c844683 in MailCommon::SearchPattern::writeConfig (this=this@entry=0x1bc5f48, config=...) at /usr/src/debug/kdepim-4.14.6/mailcommon/search/searchpattern.cpp:1478 #11 0x00007f724c8bd101 in MailCommon::MailFilter::writeConfig (this=this@entry=0x1bc5f40, config=..., exportFilter=exportFilter@entry=true) at /usr/src/debug/kdepim-4.14.6/mailcommon/filter/mailfilter.cpp:496 #12 0x00007f724c89efac in MailCommon::FilterImporterExporter::writeFiltersToConfig (filters=..., config=..., exportFiler=exportFiler@entry=true) at /usr/src/debug/kdepim-4.14.6/mailcommon/filter/filterimporterexporter.cpp:116 #13 0x00007f724c89f35d in MailCommon::FilterImporterExporter::exportFilters (this=this@entry=0x7fff9b2aa720, filters=..., fileName=..., saveAll=saveAll@entry=true) at /usr/src/debug/kdepim-4.14.6/mailcommon/filter/filterimporterexporter.cpp:363 #14 0x0000000000424703 in ExportMailJob::backupConfig (this=this@entry=0x1ca7270) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/mail/exportmailjob.cpp:191 #15 0x00000000004299d4 in ExportMailJob::start (this=0x1ca7270) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/mail/exportmailjob.cpp:105 #16 0x000000000045d13c in PimSettingExporterWindow::backupNextStep (this=this@entry=0x1bb6bd0) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/pimsettingexporterwindow.cpp:312 #17 0x000000000045d54b in PimSettingExporterWindow::backupStart (this=this@entry=0x1bb6bd0) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/pimsettingexporterwindow.cpp:254 #18 0x000000000045dca0 in PimSettingExporterWindow::backupData (this=this@entry=0x1bb6bd0, filename=..., templateFile=...) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/pimsettingexporterwindow.cpp:237 #19 0x000000000045df81 in PimSettingExporterWindow::slotBackupData (this=0x1bb6bd0) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/pimsettingexporterwindow.cpp:214 #20 0x00007f7249df61fa in QMetaObject::activate (sender=sender@entry=0x1c06a80, m=m@entry=0x7f724b2944a0 <QAction::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff9b2aaab0) at kernel/qobject.cpp:3576 #21 0x00007f724a7ea622 in QAction::triggered (this=this@entry=0x1c06a80, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #22 0x00007f724a7ebfd3 in QAction::activate (this=this@entry=0x1c06a80, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #23 0x00007f724ac14b79 in QMenuPrivate::activateCausedStack (this=this@entry=0x1e981e0, causedStack=..., action=action@entry=0x1c06a80, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1037 #24 0x00007f724ac190c9 in QMenuPrivate::activateAction (this=0x1e981e0, action=0x1c06a80, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1129 #25 0x00007f724ac1caa5 in QMenu::mouseReleaseEvent (this=this@entry=0x1c70f00, e=e@entry=0x7fff9b2ab1e0) at widgets/qmenu.cpp:2371 #26 0x00007f724b5bedf5 in KMenu::mouseReleaseEvent (this=0x1c70f00, e=0x7fff9b2ab1e0) at /usr/src/debug/kdelibs-4.14.6/kdeui/widgets/kmenu.cpp:464 #27 0x00007f724a83fc0a in QWidget::event (this=this@entry=0x1c70f00, event=event@entry=0x7fff9b2ab1e0) at kernel/qwidget.cpp:8389 #28 0x00007f724ac1cf2b in QMenu::event (this=0x1c70f00, e=0x7fff9b2ab1e0) at widgets/qmenu.cpp:2480 #29 0x00007f724a7f076c in QApplicationPrivate::notify_helper (this=this@entry=0x1a30fb0, receiver=receiver@entry=0x1c70f00, e=e@entry=0x7fff9b2ab1e0) at kernel/qapplication.cpp:4565 #30 0x00007f724a7f6dea in QApplication::notify (this=this@entry=0x7fff9b2abae0, receiver=receiver@entry=0x1c70f00, e=e@entry=0x7fff9b2ab1e0) at kernel/qapplication.cpp:4108 #31 0x00007f724b508cea in KApplication::notify (this=0x7fff9b2abae0, receiver=0x1c70f00, event=0x7fff9b2ab1e0) at /usr/src/debug/kdelibs-4.14.6/kdeui/kernel/kapplication.cpp:311 #32 0x00007f7249de22ad in QCoreApplication::notifyInternal (this=0x7fff9b2abae0, receiver=receiver@entry=0x1c70f00, event=event@entry=0x7fff9b2ab1e0) at kernel/qcoreapplication.cpp:953 #33 0x00007f724a7f65e3 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231 #34 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1c70f00, event=event@entry=0x7fff9b2ab1e0, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0x1c70f00, buttonDown=buttonDown@entry=0x7f724b2d0278 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173 #35 0x00007f724a867fcc in QETWidget::translateMouseEvent (this=this@entry=0x1c70f00, event=event@entry=0x7fff9b2ab520) at kernel/qapplication_x11.cpp:4464 #36 0x00007f724a86670c in QApplication::x11ProcessEvent (this=0x7fff9b2abae0, event=event@entry=0x7fff9b2ab520) at kernel/qapplication_x11.cpp:3653 #37 0x00007f724a88d5c2 in x11EventSourceDispatch (s=0x1a314d0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #38 0x00007f7240013a04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #39 0x00007f7240013c48 in ?? () from /usr/lib64/libglib-2.0.so.0 #40 0x00007f7240013cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #41 0x00007f7249e0f0be in QEventDispatcherGlib::processEvents (this=0x19d2100, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #42 0x00007f724a88d676 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #43 0x00007f7249de0e6f in QEventLoop::processEvents (this=this@entry=0x7fff9b2ab8f0, flags=...) at kernel/qeventloop.cpp:149 #44 0x00007f7249de1165 in QEventLoop::exec (this=this@entry=0x7fff9b2ab8f0, flags=...) at kernel/qeventloop.cpp:204 #45 0x00007f7249de65b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #46 0x00007f724a7eef3c in QApplication::exec () at kernel/qapplication.cpp:3823 #47 0x0000000000412b4c in main (argc=1, argv=<optimized out>) at /usr/src/debug/kdepim-4.14.6/pimsettingexporter/main.cpp:55 Reported using DrKonqi
Could you test in last version ? 5.4.3 ?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be 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 If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Andrew Crouthamel from comment #2) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least 15 days. > Please provide the requested information as soon as possible and set the bug > status as REPORTED. Due to regular bug tracker maintenance, if the bug is > still in NEEDSINFO status with no change in 30 days, the bug will be 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 > > If you have already provided the requested information, please set the bug > status as REPORTED so that the KDE team knows that the bug is ready to be > confirmed. > > Thank you for helping us make KDE software even better for everyone! Thank you for your warning. Curiously I did not receive a mail on "waitingforinfo" status from KDE bugzilla. So I will now look for what is to be done.
(In reply to Laurent Montel from comment #1) > Could you test in last version ? > 5.4.3 ? I tried this with 5.7.3 and it is still no working. The main part of export and migration tools do not work. What you can import: you can import mails if you have them in an archive from before. You fail to import: settings, accounts, filters (causes a memory leak and after migration filters do not work. It does not crash so in the latest version. It just messes up completely the data. So I do not know if this is to reported as bug now, or as several distinct bugs. What I can confirm: 5.7.3 migration and importing from a different computer via the KDE migration tool does not work and gives erratic results. This is true for Leap BTW particularly with mariadb. There is also a precise pattern on how settings are taken wrong (e.g. the program associates wrongly were the mail should be saved (in accounts, modify). Address books can be imported if exported to cvs but the ones exported to an archive do not work. The bigger problems are gone with migration to postgres96 however I did not try to do a migration from default status with the migration tool and postgres.
Are you sure that you exported your data with pimsettingexporter ? What type of data did you exported ? When you import do you see some errors ?
(In reply to Laurent Montel from comment #5) > Are you sure that you exported your data with pimsettingexporter ? > Yes. > What type of data did you exported ? I exported: Settings of POP3 accounts (identity and account, calendar, addresses, emails, in short whatever was offered. The program was in localized Italian and there is called Esportatore delle impostazioni di PIM Versione 5.7.3. If this is another program then I am sorry for the fuzz. > > When you import do you see some errors ? Good question (so much time after). But, I am really positive to have this fixed, so if it is of use to you, I can create a virtualized Leap 15 (within TW e.g) an try to import a full export of "impostazioni id PIM" to a virgin user of Leap 15, in case I could collect the errors. If you help me into setting the right debug settings this would be probably for you a more rewarding experience. BTW. a user very recently complained in a post about the non usability of KDE PIM export in Leap, on the mailing list. I recall it was on opensuse(at-nospam)opensuse.org. I may try to see if the list message is still to be found in my system and put it here as attachment for documentation (as it was like I would revive my experience reading it), of course only if you deem it useful.
Hi, Could you launch kdebugsettings and activate all pimsettingexporter debug ? After that you can launch pimsettingexporter in console and you will see error/warning. Otherwise you can save as html log when you import data and send me it in private email it's better. Thanks
Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
First of all my apologies that I did not respond on the request of Laurent (which never arrived at may desk, sometimes I do not receive he mail from kde bugzilla (which brought me to change several times provider)! I did run the exporter today with the standard kde 15.1, which I warn you in advance is quite outdated - but as it is shipped by default it is how the world sees you (at least using opensuse). As 15.2 Kmail/Pim is disfunctional and does break my system, I cannot provide feedback on that version. Currently this refers to: Opensuse 15.1 (with EOL on 31.01.2020 Plasma 5.12.8 Framework 5.55.0 QT 5.9.7 Under these conditions the KDE PIM software in general is functional (although subject to reported crashes and an apparent memory leak if used on a system for long time idling). That said, closing all applications of KDE PIM (by using exit) does not close all the application but leaves http instances belonging to Kontact in the memory. You have terminate them with sysgard. I did not try if that would have caused the exporter to crash and terminated instead. Once done the pimsettingsimporter seems to export without crash. It also does import without crashing in a vergin user but: creates entries without clear name or origin like 152040 and similar. Does not recreate all folders. Does represent alike the archiving tool a "local folder" pathology where you end up after two migrations using the default with: local folder/local folder/local folder/ importeduserfoldergoes here. You can change that by hand but for a lot "cryptic imports", that is without human readable name or without a destination folder were I found it quite difficult to understand what the program expected me to do. I was also asked to overwrite KDE PIMrc not one but several times, which may indicate a silent crash during import, but you may know, maybe it is normal. Once finished the import, starting the program KDE PIM, it crashes and is unusable because complaining of not being able to create the "resource 06 of the trash folder". akonadictl fsck and vaccum followed by a restart of the server did not help. I repaired finally, by eliminating the existing "trash" resource, on "good luck and boldly going were not user has gone before attitude" in akonadiconsole manually. Then the program KDE PIM started and seemed to have imported the rest of the resources conveniently. Personally I do not think that the exporter is currently functional in the good sense, but it does not crash while using it immediately! So we can say the bug is fixed. Or "that" bug is fixed. So feel free to close it as fixed, if you think it is applicable. I am currently considering changing distribution to find out if the sad status of the KDE PIM program is depending on a packaging / distribution problem or is inherent to the quality of the software. I am aware that the version used for this is old. I am uninformed if there have been major changes to the program since. It is also very difficult for me to "just to post the debugging" as I would have to edit all my sensitive data in the output by hand, since I do not wish to share these "details" on the internet. I can however, if you are interested, try to use the data of the exporter and import it in a instance of opensuse TW to see if the same issues present. I can confirm that the "local folder issue" has appeared at least by another user in the opensuse DE mailinglist for 15.2 (apparently that user was able to use it) and he faced the /local/local annoyance too. He also reported that not all folders were correctly restored, some were "invisible" after migration or "vanished". I think this corresponds to my import experience where some sources had cryptic names and some had (for unknown reason) no destination folder.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be 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 If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
see comment
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
So, I tried this but not with Leap but Tumbleweed (a more modern and reliable distribution) and for the last TW edition: Operating System: openSUSE Tumbleweed 20221203 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD FX(tm)-4300 Quad-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon Pro W5500 Manufacturer: Gigabyte Technology Co., Ltd. this works for me. Congratulations. I cannot say if Leap users still encounter it, but as the story goes, I now use the most recent edition of KDE where it IS fixed. Good for you, good for me.