Bug 313162 - webaccounts Crashes after any try to save a login data.
Summary: webaccounts Crashes after any try to save a login data.
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords: triaged
: 313200 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-13 02:09 UTC by daekaz
Modified: 2018-10-27 02:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
a Backtrace from webaccounts (52.40 KB, text/plain)
2013-01-15 10:13 UTC, daekaz
Details
New crash information added by DrKonqi (3.74 KB, text/plain)
2013-01-30 12:27 UTC, Nitesh Pathak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description daekaz 2013-01-13 02:09:13 UTC
Application: kcmshell4 ()
KDE Platform Version: 4.9.3
Qt Version: 4.8.3
Operating System: Linux 3.5.0-21-generic x86_64
Distribution: Netrunner 12.12

-- Information about the crash:
webaccounts Crashes after any try to save a login data. The Crash will occurs on last stage of configuring web profiles (facebook, google etc.). Also, i can't provide data to my web accounts until i click on the profiles list.

The crash can be reproduced every time.

-- Backtrace:
Application: Moduł konfiguracji KDE (kcmshell4), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee0d258780 (LWP 2695))]

Thread 2 (Thread 0x7fedfbef1700 (LWP 2696)):
#0  0x00007fee1494d303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fee0f32ad84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fee0f32aea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fee1357ec16 in QEventDispatcherGlib::processEvents (this=0x7fedf40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fee1354f2bf in QEventLoop::processEvents (this=this@entry=0x7fedfbef0dd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fee1354f548 in QEventLoop::exec (this=0x7fedfbef0dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fee13450b10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fee1352f9af in QInotifyFileSystemWatcherEngine::run (this=0xa41970) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fee13453aec in QThreadPrivate::start (arg=0xa41970) at thread/qthread_unix.cpp:338
#9  0x00007fee1004be9a in start_thread (arg=0x7fedfbef1700) at pthread_create.c:308
#10 0x00007fee14958cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fee0d258780 (LWP 2695)):
[KCrash Handler]
#6  0x00007fee1489b425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fee1489eb8b in __GI_abort () at abort.c:91
#8  0x00007fee12489e2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fee12487f26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fee12487f53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fee124881c6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007fee1354f7b4 in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007fee12db0428 in QDialog::exec (this=0x913f70) at dialogs/qdialog.cpp:554
#14 0x00007fee14c48b1c in kdemain (_argc=7377120, _argv=<optimized out>) at ../../kcmshell/main.cpp:292
#15 0x00007fee1488676d in __libc_start_main (main=0x4006a0 <main(int, char**)>, argc=2, ubp_av=0x7fff6d5c2468, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6d5c2458) at libc-start.c:226
#16 0x00000000004006d1 in _start ()

Possible duplicates by query: bug 313161, bug 313047, bug 312639, bug 312490, bug 312251.

Reported using DrKonqi
Comment 1 Alex Fiestas 2013-01-13 18:21:28 UTC
Can you please install debug symbols and reproduce this bug again?
Comment 2 Jekyll Wu 2013-01-13 19:35:39 UTC
*** Bug 313200 has been marked as a duplicate of this bug. ***
Comment 3 Jekyll Wu 2013-01-13 19:39:39 UTC
The backtrace shows one exception has been thrown. 

Please follow the instruction[1] and run systemsetinngs in gdb to get a better backtrace. 

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 4 daekaz 2013-01-15 10:13:33 UTC
Created attachment 76482 [details]
a Backtrace from webaccounts
Comment 5 Jekyll Wu 2013-01-15 14:22:00 UTC
(In reply to comment #4)
> Created attachment 76482 [details]
> a Backtrace from webaccounts
> #0  0x00007fffe6bb2836 in ?? () from /usr/lib/kde4/webaccounts.so

Thanks for the better backtrace, but there is no debug symbols.
Comment 6 Nitesh Pathak 2013-01-30 12:27:48 UTC
Created attachment 76812 [details]
New crash information added by DrKonqi

kcmshell4 () on KDE Platform 4.9.4 using Qt 4.8.3

Web Accounts crashed while adding online accounts (gmail, facebook etc.)

-- Backtrace (Reduced):
#6  0x00007f3a2d647425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f3a2d64ab8b in __GI_abort () at abort.c:91
[...]
#12 0x00007f3a2c2fb7b4 in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f3a2bb5c428 in QDialog::exec (this=0xdc2410) at dialogs/qdialog.cpp:554
#14 0x00007f3a2d9f4b1c in kdemain (_argc=12341472, _argv=<optimized out>) at ../../kcmshell/main.cpp:292
Comment 7 Alex Fiestas 2013-02-24 14:19:29 UTC
Do you have kwallet disabled? we do not support that (even though we should not crash but rather inform the user).

Thanks for the feedback !
Comment 8 Andrew Crouthamel 2018-09-24 02:24:34 UTC
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!
Comment 9 Andrew Crouthamel 2018-10-27 02:41:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!