Application: akregator (4.7.2) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.0-13-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I was viewing a new item (a review on tweakers.net) and akregator segfaulted on me, twice! The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0x7f7c298407a0 (LWP 2884))] Thread 4 (Thread 0x7f7bfbd49700 (LWP 2899)): #0 0x00007f7c215d0e39 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f7c215d1dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f7c215d2792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f7bff1559cb in ?? () from /usr/lib/gio/modules/libdconfsettings.so #4 0x00007f7c215f72b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f7c21aa3efc in start_thread (arg=0x7f7bfbd49700) at pthread_create.c:304 #6 0x00007f7c263f589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 3 (Thread 0x7f7bfed37700 (LWP 2901)): #0 __pthread_mutex_unlock_usercnt (mutex=<optimized out>, decr=<optimized out>) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x44a7248) at pthread_mutex_unlock.c:290 #2 0x00007f7c215d1d79 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f7c215d2792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f7bffc9b516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x00007f7c215f72b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f7c21aa3efc in start_thread (arg=0x7f7bfed37700) at pthread_create.c:304 #7 0x00007f7c263f589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #8 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f7bfd480700 (LWP 2928)): #0 0xffffffffff60017b in ?? () #1 0x00007f7bfd47fad0 in ?? () #2 0x00007fff351ff7e7 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f7c298407a0 (LWP 2884)): [KCrash Handler] #6 0x00007f7c23b7e392 in khtml::RenderMedia::eventFilter (this=0x3f9eb48, o=0x7f7bf4107d00, e=0x7fff35114e80) at ../../khtml/rendering/render_media.cpp:81 #7 0x00007f7c26fb5c88 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x7f7bf4107d00, event=0x7fff35114e80) at kernel/qcoreapplication.cpp:902 #8 0x00007f7c279b63ef in notify_helper (e=0x7fff35114e80, receiver=0x7f7bf4107d00, this=0x1101f40) at kernel/qapplication.cpp:4482 #9 QApplicationPrivate::notify_helper (this=0x1101f40, receiver=0x7f7bf4107d00, e=0x7fff35114e80) at kernel/qapplication.cpp:4458 #10 0x00007f7c279bb291 in QApplication::notify (this=0x7fff35115840, receiver=0x7f7bf4107d00, e=0x7fff35114e80) at kernel/qapplication.cpp:4365 #11 0x00007f7c286ca126 in KApplication::notify (this=0x7fff35115840, receiver=0x7f7bf4107d00, event=0x7fff35114e80) at ../../kdeui/kernel/kapplication.cpp:311 #12 0x00007f7c26fb5afc in QCoreApplication::notifyInternal (this=0x7fff35115840, receiver=0x7f7bf4107d00, event=0x7fff35114e80) at kernel/qcoreapplication.cpp:787 #13 0x00007f7c279b6cab in sendEvent (event=0x7fff35114e80, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #14 QApplicationPrivate::dispatchEnterLeave (enter=0x7f7bf4107d00, leave=<optimized out>) at kernel/qapplication.cpp:2810 #15 0x00007f7c27a3587b in QApplication::x11ProcessEvent (this=0x7fff35115840, event=0x7fff35115420) at kernel/qapplication_x11.cpp:3686 #16 0x00007f7c27a5e412 in x11EventSourceDispatch (s=0x110aa10, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #17 0x00007f7c215d1a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x00007f7c215d2258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f7c215d2429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f7c26fe0ed6 in QEventDispatcherGlib::processEvents (this=0x10d0170, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #21 0x00007f7c27a5e07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x00007f7c26fb4cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #23 0x00007f7c26fb4ef7 in QEventLoop::exec (this=0x7fff351157f0, flags=...) at kernel/qeventloop.cpp:201 #24 0x00007f7c26fb9789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #25 0x0000000000407dac in ?? () #26 0x00007f7c2633530d in __libc_start_main (main=0x4078c0, argc=1, ubp_av=0x7fff35115b18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff35115b08) at libc-start.c:226 #27 0x0000000000408089 in _start () Possible duplicates by query: bug 262149. Reported using DrKonqi
BTW, the full URL was http://tweakers.net/nieuws/78267/nvidia-toont-android-ice-cream-sandwich-op-transformer-prime.html
*** This bug has been marked as a duplicate of bug 262149 ***