Bug 460130 - Crash on account creation wizard
Summary: Crash on account creation wizard
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Account Wizard (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-10-08 18:15 UTC by Harry T
Modified: 2022-10-10 15:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.30 KB, text/plain)
2022-10-10 15:04 UTC, coding-matter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harry T 2022-10-08 18:15:25 UTC
Application: accountwizard (0.2)

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.19.13-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 36 (Workstation Edition)
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
After entering the basic information into the account creation wizard (name, email address, etc.) and clicking the 'Next' button, the wizard just crashes. This happens no matter the state of the automatically find settings checkbox.

The crash can be reproduced every time.

-- Backtrace:
Application: Account Assistant (accountwizard), signal: Segmentation fault

[KCrash Handler]
#4  0x0000555faf61ce4f in CryptoPage::enterPageNext() ()
#5  0x0000555faf61ffc0 in Dialog::slotNextOk() ()
#6  0x00007fb80896c9a6 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#7  0x0000555faf61c520 in Dialog::next() ()
#8  0x00007fb80896c9a6 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#9  0x00007fb8094ea1c6 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5
#10 0x00007fb8094ea43e in QAbstractButtonPrivate::emitClicked() () at /lib64/libQt5Widgets.so.5
#11 0x00007fb8094ec3f9 in QAbstractButton::click() () at /lib64/libQt5Widgets.so.5
#12 0x00007fb80960619c in QDialog::keyPressEvent(QKeyEvent*) () at /lib64/libQt5Widgets.so.5
#13 0x00007fb809439610 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5
#14 0x00007fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#15 0x00007fb8093fdcf7 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#16 0x00007fb8089391c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#17 0x00007fb809454f72 in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5
#18 0x00007fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#19 0x00007fb8089391c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#20 0x00007fb808d734fd in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib64/libQt5Gui.so.5
#21 0x00007fb808d5602c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5
#22 0x00007fb7f4c2e8be in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5
#23 0x00007fb8055cbfaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#24 0x00007fb8056212c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#25 0x00007fb8055c9940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#26 0x00007fb80898a02a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#27 0x00007fb808937c1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#28 0x00007fb80893fce2 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#29 0x0000555faf60f447 in main ()
[Inferior 1 (process 41111) detached]

The reporter indicates this bug may be a duplicate of or related to bug 459308, bug 459236.

Reported using DrKonqi
Comment 1 coding-matter 2022-10-10 15:04:14 UTC
Created attachment 152688 [details]
New crash information added by DrKonqi

accountwizard (0.2) using Qt 5.15.6

Trying to create an account, after inputing name/email address and click next it crushes. Tried clikcing and not clicking the automatically find setting checkbox.

-- Backtrace (Reduced):
#4  0x00005647e6ff7e4f in CryptoPage::enterPageNext() ()
#5  0x00005647e6ffafc0 in Dialog::slotNextOk() ()
#6  0x00007fda26caa9a6 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#7  0x00005647e6ff7520 in Dialog::next() ()
#8  0x00007fda26caa9a6 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
Comment 2 coding-matter 2022-10-10 15:05:41 UTC
(In reply to Harry T from comment #0)
> Application: accountwizard (0.2)
> 
> Qt Version: 5.15.6
> Frameworks Version: 5.98.0
> Operating System: Linux 5.19.13-200.fc36.x86_64 x86_64
> Windowing System: X11
> Distribution: Fedora Linux 36 (Workstation Edition)
> DrKonqi: 5.25.5 [KCrashBackend]
> 
> -- Information about the crash:
> After entering the basic information into the account creation wizard (name,
> email address, etc.) and clicking the 'Next' button, the wizard just
> crashes. This happens no matter the state of the automatically find settings
> checkbox.
> 
> The crash can be reproduced every time.
> 
> -- Backtrace:
> Application: Account Assistant (accountwizard), signal: Segmentation fault
> 
> [KCrash Handler]
> #4  0x0000555faf61ce4f in CryptoPage::enterPageNext() ()
> #5  0x0000555faf61ffc0 in Dialog::slotNextOk() ()
> #6  0x00007fb80896c9a6 in void doActivate<false>(QObject*, int, void**) ()
> at /lib64/libQt5Core.so.5
> #7  0x0000555faf61c520 in Dialog::next() ()
> #8  0x00007fb80896c9a6 in void doActivate<false>(QObject*, int, void**) ()
> at /lib64/libQt5Core.so.5
> #9  0x00007fb8094ea1c6 in QAbstractButton::clicked(bool) () at
> /lib64/libQt5Widgets.so.5
> #10 0x00007fb8094ea43e in QAbstractButtonPrivate::emitClicked() () at
> /lib64/libQt5Widgets.so.5
> #11 0x00007fb8094ec3f9 in QAbstractButton::click() () at
> /lib64/libQt5Widgets.so.5
> #12 0x00007fb80960619c in QDialog::keyPressEvent(QKeyEvent*) () at
> /lib64/libQt5Widgets.so.5
> #13 0x00007fb809439610 in QWidget::event(QEvent*) () at
> /lib64/libQt5Widgets.so.5
> #14 0x00007fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () at /lib64/libQt5Widgets.so.5
> #15 0x00007fb8093fdcf7 in QApplication::notify(QObject*, QEvent*) () at
> /lib64/libQt5Widgets.so.5
> #16 0x00007fb8089391c8 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*) () at /lib64/libQt5Core.so.5
> #17 0x00007fb809454f72 in QWidgetWindow::event(QEvent*) () at
> /lib64/libQt5Widgets.so.5
> #18 0x00007fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () at /lib64/libQt5Widgets.so.5
> #19 0x00007fb8089391c8 in QCoreApplication::notifyInternal2(QObject*,
> QEvent*) () at /lib64/libQt5Core.so.5
> #20 0x00007fb808d734fd in
> QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::
> KeyEvent*) () at /lib64/libQt5Gui.so.5
> #21 0x00007fb808d5602c in
> QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::
> ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5
> #22 0x00007fb7f4c2e8be in xcbSourceDispatch(_GSource*, int (*)(void*),
> void*) () at /lib64/libQt5XcbQpa.so.5
> #23 0x00007fb8055cbfaf in g_main_context_dispatch () at
> /lib64/libglib-2.0.so.0
> #24 0x00007fb8056212c8 in g_main_context_iterate.constprop () at
> /lib64/libglib-2.0.so.0
> #25 0x00007fb8055c9940 in g_main_context_iteration () at
> /lib64/libglib-2.0.so.0
> #26 0x00007fb80898a02a in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () at /lib64/libQt5Core.so.5
> #27 0x00007fb808937c1a in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
> /lib64/libQt5Core.so.5
> #28 0x00007fb80893fce2 in QCoreApplication::exec() () at
> /lib64/libQt5Core.so.5
> #29 0x0000555faf60f447 in main ()
> [Inferior 1 (process 41111) detached]
> 
> The reporter indicates this bug may be a duplicate of or related to bug
> 459308, bug 459236.
> 
> Reported using DrKonqi

I believe we are meeting the same bug, but are you sure this is a akonadi problem instead of Kmail's?