Bug 288393 - Segfault when creating account in Kmail
Summary: Segfault when creating account in Kmail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Account Wizard (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 11:03 UTC by Alois Steindl
Modified: 2016-09-15 09:08 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alois Steindl 2011-12-07 11:03:50 UTC
Application: accountwizard (0.1)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.8.0
Operating System: Linux 3.1.4-1.fc16.i686.PAE i686
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:
I called kmail for a Test User to find out, whether the regular crashes of nepomukservicestub occur also for a new user.
Right at the start I got the message, that a severe error occured and the program is stopped. But the program did let me continue with generating the account. When trying to input the pop server, the crash occured.

I would be very glad, if the regular crashes at the start of kmail could be resolved.
(I installed Fedora Core 16 on 2 machines; both show the same symptoms.)

The crash can be reproduced every time.

-- Backtrace:
Application: Konten-Assistent (accountwizard), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#7  0x43634065 in KJSEmbed::SlotProxy::callMethod (this=0x924a358, methodName=..., _a=0xbfa974f8) at /usr/src/debug/kdelibs-4.7.3/kjsembed/kjsembed/slotproxy.cpp:101
#8  0x43634d04 in KJSEmbed::SlotProxy::qt_metacall (this=0x924a358, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa974f8) at /usr/src/debug/kdelibs-4.7.3/kjsembed/kjsembed/slotproxy.cpp:310
#9  0x4918c57e in metacall (argv=0xbfa974f8, idx=4, cl=QMetaObject::InvokeMetaMethod, object=0x924a358) at kernel/qmetaobject.cpp:245
#10 QMetaObject::metacall (object=0x924a358, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbfa974f8) at kernel/qmetaobject.cpp:240
#11 0x4919b06d in QMetaObject::activate (sender=0x9237758, m=0x4255a13c, local_signal_index=0, argv=0xbfa974f8) at kernel/qobject.cpp:3565
#12 0x4206dac6 in QLineEdit::textChanged (this=0x9237758, _t1=...) at .moc/release-shared/moc_qlineedit.cpp:264
#13 0x4206de87 in QLineEdit::qt_static_metacall (_o=0x9237758, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa97618) at .moc/release-shared/moc_qlineedit.cpp:140
#14 0x4919ad61 in QMetaObject::activate (sender=0x9237968, m=0x42568918, local_signal_index=3, argv=0xbfa97618) at kernel/qobject.cpp:3546
#15 0x42320fb6 in QLineControl::textChanged (this=0x9237968, _t1=...) at .moc/release-shared/moc_qlinecontrol_p.cpp:148
#16 0x4207314a in QLineControl::finishChange (this=0x9237968, validateFromState=0, update=false, edited=true) at widgets/qlinecontrol.cpp:656
#17 0x42074fb6 in QLineControl::insert (this=0x9237968, newText=...) at widgets/qlinecontrol.cpp:248
#18 0x420757af in QLineControl::processKeyEvent (this=0x9237968, event=0xbfa97ee4) at widgets/qlinecontrol.cpp:1873
#19 0x4206911c in QLineEdit::keyPressEvent (this=0x9237758, event=0xbfa97ee4) at widgets/qlineedit.cpp:1707
#20 0x4285eb05 in KLineEdit::keyPressEvent (this=0x9237758, e=0xbfa97ee4) at /usr/src/debug/kdelibs-4.7.3/kdeui/widgets/klineedit.cpp:970
#21 0x41c408fd in QWidget::event (this=0x9237758, event=0xbfa97ee4) at kernel/qwidget.cpp:8385
#22 0x4206bb9b in QLineEdit::event (this=0x9237758, e=0xbfa97ee4) at widgets/qlineedit.cpp:1524
#23 0x4285cdcf in KLineEdit::event (this=0x9237758, ev=0xbfa97ee4) at /usr/src/debug/kdelibs-4.7.3/kdeui/widgets/klineedit.cpp:1403
#24 0x41be5a34 in notify_helper (e=0xbfa97ee4, receiver=0x9237758, this=0x8b9b850) at kernel/qapplication.cpp:4518
#25 QApplicationPrivate::notify_helper (this=0x8b9b850, receiver=0x9237758, e=0xbfa97ee4) at kernel/qapplication.cpp:4490
#26 0x41beba15 in QApplication::notify (this=0xbfa97d84, receiver=0x9237758, e=0xbfa97ee4) at kernel/qapplication.cpp:3959
#27 0x42784fa2 in KApplication::notify (this=0xbfa988dc, receiver=0x9237758, event=0xbfa97ee4) at /usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kapplication.cpp:311
#28 0x491854be in QCoreApplication::notifyInternal (this=0xbfa988dc, receiver=0x9237758, event=0xbfa97ee4) at kernel/qcoreapplication.cpp:876
#29 0x41be3aae in sendSpontaneousEvent (event=0xbfa97ee4, receiver=0x9237758) at ../../src/corelib/kernel/qcoreapplication.h:234
#30 qt_sendSpontaneousEvent (receiver=0x9237758, event=0xbfa97ee4) at kernel/qapplication.cpp:5512
#31 0x41c95e12 in QKeyMapper::sendKeyEvent (keyWidget=0x9237758, grab=false, type=QEvent::KeyPress, code=77, modifiers=) at kernel/qkeymapper_x11.cpp:1866
#32 0x41c962cb in QKeyMapperPrivate::translateKeyEvent (this=0x8bc6ef8, keyWidget=0x9237758, event=0xbfa9850c, grab=false) at kernel/qkeymapper_x11.cpp:1836
#33 0x41c6ef1d in QApplication::x11ProcessEvent (this=0xbfa988dc, event=0xbfa9850c) at kernel/qapplication_x11.cpp:3534
#34 0x41c9a6f5 in x11EventSourceDispatch (s=0x8b9f140, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#35 0x4841d5bf in g_main_dispatch (context=0x8b9e270) at gmain.c:2425
#36 g_main_context_dispatch (context=0x8b9e270) at gmain.c:2995
#37 0x4841dd00 in g_main_context_iterate (context=0x8b9e270, block=1212336032, dispatch=1, self=0x8b9e608) at gmain.c:3073
#38 0x4841dfaf in g_main_context_iteration (context=0x8b9e270, may_block=1) at gmain.c:3136
#39 0x491b8168 in QEventDispatcherGlib::processEvents (this=0x8b7e850, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#40 0x41c9a38b in QGuiEventDispatcherGlib::processEvents (this=0x8b7e850, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#41 0x491843ae in QEventLoop::processEvents (this=0xbfa98814, flags=...) at kernel/qeventloop.cpp:149
#42 0x49184659 in QEventLoop::exec (this=0xbfa98814, flags=...) at kernel/qeventloop.cpp:204
#43 0x491897fb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#44 0x41be3835 in QApplication::exec () at kernel/qapplication.cpp:3779
#45 0x08074d2f in ?? ()
#46 0x4818f6b3 in __libc_start_main (main=0x8074590, argc=3, ubp_av=0xbfa98a74, init=0x80fefe0 <__libc_csu_init>, fini=0x80ff050 <__libc_csu_fini>, rtld_fini=0x481612c0 <_dl_fini>, stack_end=0xbfa98a6c) at libc-start.c:226
#47 0x080751d9 in _start ()

Reported using DrKonqi
Comment 1 Blagovest Zlatev 2011-12-08 12:38:01 UTC
The bug is not reproducible or a duplicate.
Comment 2 Alois Steindl 2011-12-09 08:23:00 UTC
I think that I should add, that the error occured when I made an
su - testuser
from my ordinary session.
So maybe my akonadi-kmail-nepomuk-whatever-environment encountered some conflict with the programs started from the testuser-shell.
Later I created a new testuser, logged into that account and could use everything without any problems.

The main problem here is that every time I login with my usual account I get a segfault from nepomukservicestub. I already installed the debug-libraries and wanted to report that problem. But there is already a long list of reports for that problem, mostly indicating that the error should already be resolved in the recent program versions. Most error reports are for Ubuntu and Suse distributions, I couldn't find Fedora reports. (I don't think that this is an important information.)
 
From my experience with the new account I would guess, that Nepomuk/Akonadi/... has some problem with my configuration files; so maybe resetting everything would resolve the problem. Of course I wouldn't like to lose too much data. 
Best regards
Alois
Comment 3 Christophe Marin 2011-12-10 01:05:09 UTC
the 'su - testuser' could be the cause. Some distributions added some patches to start a user dbus session when using su.

Does 'ps x |grep dbus-launch' return something when you log as testuser ?
Comment 4 Alois Steindl 2011-12-12 11:18:23 UTC
Hello,
thanks for your response.

When logged in by su - testuser, the command
ps x |grep dbus-launch

shows no process dbus-launch.

Best regards
Alois
Comment 5 Christophe Marin 2011-12-13 09:37:10 UTC
ok, After using su, try:

eval "`which dbus-launch` --auto-syntax"

(ie: start dbus for this user)

then akonadictl start
Comment 6 Daniel Vrátil 2016-09-15 09:08:11 UTC
Closing this issue, as current version does no longer use KJSEmbed, which seems to be what crashed here.