[akregator] [Bug 394114] Akregator 5.7.3 crash at opening an article
https://bugs.kde.org/show_bug.cgi?id=394114 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- Correct. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394114] Akregator 5.7.3 crash at opening an article
https://bugs.kde.org/show_bug.cgi?id=394114 --- Comment #1 from Pedro --- I've tracked the problem, and it seems to be a known bug in nouveau drivers. Here are the related QT and nouveau bug reports: https://bugreports.qt.io/browse/QTBUG-41242 https://bugs.freedesktop.org/show_bug.cgi?id=91632 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394114] New: Akregator 5.7.3 crash at opening an article
https://bugs.kde.org/show_bug.cgi?id=394114 Bug ID: 394114 Summary: Akregator 5.7.3 crash at opening an article Product: akregator Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pedro.gong...@gmail.com Target Milestone: --- Akregator crashes or hangs when opening some articles. I've noticed that it only happens when the article has large images. On my machine, the bug presents always, most times it crashes or just hangs, but some times it freezes all the plasma desktop. I'm using Kubuntu 18.04. Backtrace: Starting program: /usr/bin/akregator [Depuración de hilo usando libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Nuevo Thread 0x7fffc1fd0700 (LWP 14112)] [Nuevo Thread 0x7fffb5773700 (LWP 14113)] [Nuevo Thread 0x7fffb4a87700 (LWP 14114)] [Nuevo Thread 0x7fffae894700 (LWP 14115)] [Nuevo Thread 0x7fffae093700 (LWP 14120)] [Nuevo Thread 0x7fffad892700 (LWP 14121)] [Nuevo Thread 0x7fffad091700 (LWP 14122)] [Nuevo Thread 0x7fffac890700 (LWP 14123)] [Nuevo Thread 0x7fff9bdf1700 (LWP 14124)] [Nuevo Thread 0x7fff9b5f0700 (LWP 14125)] [Nuevo Thread 0x7fff9adef700 (LWP 14126)] [Nuevo Thread 0x7fff9a5ee700 (LWP 14127)] [Nuevo Thread 0x7fff99ded700 (LWP 14128)] [Nuevo Thread 0x7fff995ec700 (LWP 14129)] [Nuevo Thread 0x7fff98deb700 (LWP 14130)] [Nuevo Thread 0x7fff77fff700 (LWP 14131)] [Nuevo Thread 0x7fff777fe700 (LWP 14132)] [Nuevo Thread 0x7fff76ffd700 (LWP 14133)] [Nuevo Thread 0x7fff767fc700 (LWP 14134)] [Nuevo Thread 0x7fff75ffb700 (LWP 14135)] [Nuevo Thread 0x7fff757fa700 (LWP 14136)] [Nuevo Thread 0x7fff74ff9700 (LWP 14137)] [Nuevo Thread 0x7fff43fff700 (LWP 14138)] [Nuevo Thread 0x7fff3ac07700 (LWP 14139)] [Nuevo Thread 0x7fff398e2700 (LWP 14140)] [Nuevo Thread 0x7fff33fff700 (LWP 14145)] [Nuevo Thread 0x7fff32697700 (LWP 14156)] [Thread 0x7fff32697700 (LWP 14156) terminado] [Nuevo Thread 0x7fff32697700 (LWP 14192)] Thread 21 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault. [Cambiando a Thread 0x7fff75ffb700 (LWP 14135)] pushbuf_kref (push=push@entry=0x55888a70, bo=0x0, flags=0) at ../../nouveau/pushbuf.c:173 173 ../../nouveau/pushbuf.c: No existe el archivo o el directorio. Thread 29 (Thread 0x7fff32697700 (LWP 14192)): #0 0x7fffee0caed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff326967e0, expected=0, futex_word=0x7fffa0004594) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fff32696880, mutex=0x7fffa0004540, cond=0x7fffa0004568) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fffa0004568, mutex=0x7fffa0004540, abstime=0x7fff32696880) at pthread_cond_wait.c:667 #3 0x7fffe46d3652 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fffe46a9799 in base::PosixDynamicThreadPool::WaitForTask() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fffe46a9cfb in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fffe46a25eb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fffee0c46db in start_thread (arg=0x7fff32697700) at pthread_create.c:463 #8 0x73da388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fff33fff700 (LWP 14145)): #0 0x7fffee0ca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fffe10d9fb8 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fffe10d9f68 , cond=0x7fffe10d9f90 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fffe10d9f90 , mutex=0x7fffe10d9f68 ) at pthread_cond_wait.c:655 #3 0x7fffe0de35f4 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fffe10cbec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7fffe0de3639 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7fffee0c46db in start_thread (arg=0x7fff33fff700) at pthread_create.c:463 #6 0x73da388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fff398e2700 (LWP 14140)): #0 0x7fffee0ca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a32acc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a32a78, cond=0x55a32aa0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a32aa0, mutex=0x55a32a78) at pthread_cond_wait.c:655 #3 0x7fffe46a4c95 in base::SequencedWorkerPool::Inner::ThreadLoop
[kmail2] [Bug 392996] links and attachments don't open with qtwebengine 5.11 beta 3
https://bugs.kde.org/show_bug.cgi?id=392996 Antonio Rojas changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Antonio Rojas --- Fixed in 18.04.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394099] Weird black box appearing alongside the split between message list and preview
https://bugs.kde.org/show_bug.cgi?id=394099 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394099] New: Weird black box appearing alongside the split between message list and preview
https://bugs.kde.org/show_bug.cgi?id=394099 Bug ID: 394099 Summary: Weird black box appearing alongside the split between message list and preview Product: kmail2 Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: cliv...@protonmail.com Target Milestone: --- Created attachment 112566 --> https://bugs.kde.org/attachment.cgi?id=112566&action=edit Weird Black box There is a weird black box appearing alongside the split between message list and preview. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394094] New: Akregator crashes without warning
https://bugs.kde.org/show_bug.cgi?id=394094 Bug ID: 394094 Summary: Akregator crashes without warning Product: akregator Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: stephe...@lineone.net Target Milestone: --- Application: akregator (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.126-48-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Setting content of feed to "read" (Ctl-R) .. but the application crashes unpredictably and this does not seem to be related to any particular action The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f742462f980 (LWP 23442))] Thread 23 (Thread 0x7f7383fff700 (LWP 23516)): #0 0x7f741ab140ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7412bcf5d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f7412bcfd9d in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f7412bd05c0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f7412bcd31e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f741ab0f724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7420525e8d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f738a1e0700 (LWP 23479)): #0 0x7f741ab140ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f740f6d393b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f740f6d3969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f741ab0f724 in start_thread () at /lib64/libpthread.so.0 #4 0x7f7420525e8d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f738b7fe700 (LWP 23470)): #0 0x7f741ab140ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7412a2b160 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f7412a18c0b in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f7412a18e85 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f7412a15777 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f74141bfa4a in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f74141bfd61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f74141bfe52 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f7412bb9062 in () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f7412ba4b05 in () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f7412bd0940 in () at /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f7412bcd31e in () at /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f741ab0f724 in start_thread () at /lib64/libpthread.so.0 #13 0x7f7420525e8d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f738bfff700 (LWP 23469)): #0 0x7f741ab140ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7412bcf5d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f7412bcfd9d in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f7412bd05c0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f7412bcd31e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f741ab0f724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7420525e8d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f73c97fa700 (LWP 23467)): #0 0x7f742051d30d in poll () at /lib64/libc.so.6 #1 0x7f741a0ae314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f741a0ae42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7420e291ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f7420dd6bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f7420c11f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f7420c16a29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f741ab0f724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f7420525e8d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f73c9ffb700 (LWP 23465)): #0 0x7f742053238b in __lll_lock_wait_private () at /lib64/libc.so.6 #1 0x7f7420533fe6 in __fprintf_chk () at /lib64/libc.so.6 #2 0x7f7407884fbf in () at /usr/lib64/libevent-2.0.so.5 #3 0x7f7407885197 in event_warn () at /usr/lib64/libevent-2.0.so.5 #4 0x7f7407889448 in () at /usr/lib64/libevent-2.0.so.5 #5 0x7f7407875457 in event_base_loop () at /usr/lib64/libevent-2.0.so.5 #6 0x7f7412b85c9e in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f7412bb9062 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f7412ba4b05 in () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f7412bd0940 in () at /usr/lib64/libQt5WebEngineC
[Akonadi] [Bug 394071] New: Kmail crash after searching message
https://bugs.kde.org/show_bug.cgi?id=394071 Bug ID: 394071 Summary: Kmail crash after searching message Product: Akonadi Version: 5.8.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: tournie...@gmail.com Target Milestone: --- Created attachment 112558 --> https://bugs.kde.org/attachment.cgi?id=112558&action=edit This is the crash report generated by akonadiserver. I selected "find a message" in the kmail tool menu. I filled the popup window, typed search. Then kmail asked me either to re-index the directory (during all the tests I have done in order to reproduce the crash, kmail always asked me to re-index, even I did it before) or to continue. Kmail crashed for the both choices. The message I received (in french): "Le service de gestion des informations personnelles n'est pas opérationnel. Il est impossible d'utiliser cette application sans ce service." Best regards, -- You are receiving this mail because: You are the assignee for the bug.
