Bug 320244 - Web Accounts application crashed
Summary: Web Accounts application crashed
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 4.10.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-05-25 01:21 UTC by Gary Mullinix
Modified: 2018-10-27 02:44 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Mullinix 2013-05-25 01:21:33 UTC
Application: kcmshell4 (4.10.3)
KDE Platform Version: 4.10.3
Qt Version: 4.8.3
Operating System: Linux 3.5.0-31-generic x86_64
Distribution: Netrunner 12.12

-- Information about the crash:
- What I was doing when the application crashed: I was entering information for my google account in Web Accounts - has crashed numerous times. Unable to enter Facebook or Runners-ID information as well.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e89dd2780 (LWP 2469))]

Thread 2 (Thread 0x7f5e78a2c700 (LWP 2481)):
#0  0x00007f5e914ca313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f5e8bea4d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5e8bea4ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f5e900f8c46 in QEventDispatcherGlib::processEvents (this=0x7f5e740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f5e900c92ef in QEventLoop::processEvents (this=this@entry=0x7f5e78a2bdd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f5e900c9578 in QEventLoop::exec (this=0x7f5e78a2bdd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f5e8ffcab40 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f5e900a99df in QInotifyFileSystemWatcherEngine::run (this=0x12ec5e0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f5e8ffcdb1c in QThreadPrivate::start (arg=0x12ec5e0) at thread/qthread_unix.cpp:338
#9  0x00007f5e8cbc5e9a in start_thread (arg=0x7f5e78a2c700) at pthread_create.c:308
#10 0x00007f5e914d5ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f5e89dd2780 (LWP 2469)):
[KCrash Handler]
#6  0x00007f5e91418425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f5e9141bb8b in __GI_abort () at abort.c:91
#8  0x00007f5e8f003e2d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f5e8f001f26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f5e8f001f53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f5e8f0021c6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f5e900c97e4 in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f5e8f92a428 in QDialog::exec (this=0xefd630) at dialogs/qdialog.cpp:554
#14 0x00007f5e917c5c8c in kdemain (_argc=13594768, _argv=<optimized out>) at ../../kcmshell/main.cpp:297
#15 0x00007f5e9140376d in __libc_start_main (main=0x4006a0 <main(int, char**)>, argc=2, ubp_av=0x7fff4b0e2588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4b0e2578) at libc-start.c:226
#16 0x00000000004006d1 in _start ()

Possible duplicates by query: bug 320128, bug 318896, bug 318309, bug 316907, bug 316495.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-05-25 06:08:05 UTC
Please follow the guide[1] and try to provide a better backtrace, since you can reproduce it every time. 

[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 2 Jekyll Wu 2013-09-30 13:30:05 UTC
See comment #1.
Comment 3 Andrew Crouthamel 2018-09-25 03:54:37 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 4 Andrew Crouthamel 2018-10-27 02:44:33 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!