[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #1 from Øystein Steffensen-Alværvik --- Created attachment 114036 --> https://bugs.kde.org/attachment.cgi?id=114036&action=edit New crash information added by DrKonqi akregator (5.8.2) using Qt 5.11.1 Here's a backtrace with proper debug symbols installed. Also reproducible every time. -- Backtrace (Reduced): #7 0x7f9531368d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffe8df8d8a8) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added CC||yst...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #2 from Øystein Steffensen-Alværvik --- Sorry, *here's* the backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81089bd980 (LWP 13572))] Thread 2 (Thread 0x7f80d4f78700 (LWP 13574)): #0 0x7f810484627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f80fce416f0 in read (__nbytes=16, __buf=0x7f80d4f779f0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0xd1f0b0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210 #3 0x7f80fcdfde74 in g_main_context_check (context=context@entry=0x7f80d990, max_priority=2147483647, fds=fds@entry=0x7f80d0003020, n_fds=n_fds@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632 #4 0x7f80fcdfe330 in g_main_context_iterate (context=context@entry=0x7f80d990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837 #5 0x7f80fcdfe49c in g_main_context_iteration (context=0x7f80d990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #6 0x7f81051620bb in QEventDispatcherGlib::processEvents (this=0x7f80d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f81051095ba in QEventLoop::exec (this=this@entry=0x7f80d4f77c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #8 0x7f8104f3e5e4 in QThread::exec (this=this@entry=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #9 0x7f8106e2cf35 in QDBusConnectionManager::run (this=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #10 0x7f8104f49727 in QThreadPrivate::start (arg=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #11 0x7f80fed566ba in start_thread (arg=0x7f80d4f78700) at pthread_create.c:333 #12 0x7f810485641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f81089bd980 (LWP 13572)): [KCrash Handler] #6 0x7f8104e8d558 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f81084c1d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffd3e22a518) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 396694 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #1 from Øystein Steffensen-Alværvik --- Created attachment 114036 --> https://bugs.kde.org/attachment.cgi?id=114036&action=edit New crash information added by DrKonqi akregator (5.8.2) using Qt 5.11.1 Here's a backtrace with proper debug symbols installed. Also reproducible every time. -- Backtrace (Reduced): #7 0x7f9531368d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffe8df8d8a8) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added CC||yst...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #2 from Øystein Steffensen-Alværvik --- Sorry, *here's* the backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81089bd980 (LWP 13572))] Thread 2 (Thread 0x7f80d4f78700 (LWP 13574)): #0 0x7f810484627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f80fce416f0 in read (__nbytes=16, __buf=0x7f80d4f779f0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0xd1f0b0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210 #3 0x7f80fcdfde74 in g_main_context_check (context=context@entry=0x7f80d990, max_priority=2147483647, fds=fds@entry=0x7f80d0003020, n_fds=n_fds@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632 #4 0x7f80fcdfe330 in g_main_context_iterate (context=context@entry=0x7f80d990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837 #5 0x7f80fcdfe49c in g_main_context_iteration (context=0x7f80d990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #6 0x7f81051620bb in QEventDispatcherGlib::processEvents (this=0x7f80d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f81051095ba in QEventLoop::exec (this=this@entry=0x7f80d4f77c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #8 0x7f8104f3e5e4 in QThread::exec (this=this@entry=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #9 0x7f8106e2cf35 in QDBusConnectionManager::run (this=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #10 0x7f8104f49727 in QThreadPrivate::start (arg=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #11 0x7f80fed566ba in start_thread (arg=0x7f80d4f78700) at pthread_create.c:333 #12 0x7f810485641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f81089bd980 (LWP 13572)): [KCrash Handler] #6 0x7f8104e8d558 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f81084c1d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffd3e22a518) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 396694 *** -- You are receiving this mail because: You are watching all bug changes.
