[akregator] [Bug 401905] New: Akregator crashes when HTTP request times out
https://bugs.kde.org/show_bug.cgi?id=401905 Bug ID: 401905 Summary: Akregator crashes when HTTP request times out Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: o...@iki.fi Target Milestone: --- Application: akregator (5.9.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-42-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: just reading feeds, while one feed is from a server where requests time out every now and then. It seems that crashes are reduced when I'm not touching the feed from the faulty server for some time. There is no clear way to reproduce the crash, possibly because the crashes are related to feed updates happening in the background. The crash can be reproduced sometimes. -- 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 0x7fc5f73ccbc0 (LWP 6451))] Thread 29 (Thread 0x7fc497d7a700 (LWP 6488)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7fc5f3204474 in ___fprintf_chk (fp=0x7fc5f34bf8b0 <_IO_stdfile_2_lock>, flag=1, format=0x7fc5d857f6a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7fc5d85679ad in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7fc5d8567b44 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7fc5d856946c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7fc5d855f114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7fc5e404bfc4 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc5e406c20b in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc5e408e60f in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc5e4089ff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fc5ed6de6db in start_thread (arg=0x7fc497d7a700) at pthread_create.c:463 #11 0x7fc5f31f388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fc554d6c700 (LWP 6487)): #0 0x7fc5ed6e4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc554d6b740, expected=0, futex_word=0x7fc554d6b928) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fc554d6b7e0, mutex=0x7fc554d6b8d8, cond=0x7fc554d6b900) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fc554d6b900, mutex=0x7fc554d6b8d8, abstime=0x7fc554d6b7e0) at pthread_cond_wait.c:667 #3 0x7fc5e4078917 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc5e407abf7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc5e407ace2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc5e407fd61 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc5e40812e9 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc5e4089ff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc5ed6de6db in start_thread (arg=0x7fc554d6c700) at pthread_create.c:463 #10 0x7fc5f31f388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fc555ffb700 (LWP 6486)): #0 0x7fc5ed6e49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fc5df93dfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc5df93df68, cond=0x7fc5df93df90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fc5df93df90, mutex=0x7fc5df93df68) at pthread_cond_wait.c:655 #3 0x7fc5df648954 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fc5df648999 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fc5ed6de6db in start_thread (arg=0x7fc555ffb700) at pthread_create.c:463 #6 0x7fc5f31f388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fc5567fc700 (LWP 6485)): #0 0x7fc5f31e6bf9 in __GI___poll (fds=0x7fc518004a10, nfds=1, timeout=9578) at
[Akonadi] [Bug 401902] New: crash of akonadi_imap_resource
https://bugs.kde.org/show_bug.cgi?id=401902 Bug ID: 401902 Summary: crash of akonadi_imap_resource Product: Akonadi Version: 5.9.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- Created attachment 116791 --> https://bugs.kde.org/attachment.cgi?id=116791=edit back trace made by Dr. Konqi SUMMARY Dr. Konqi reported the crashh but was unable to start reporting. STEPS TO REPRODUCE 1. Not sure it reproducible 2. 3. I selected all 12 messages in the inbox. These 12 messages should go to the Waste bin on that same IMAP server. The IMAP server is dovecot. I pressed the key Del, saw a window telling 12 are being transferred. Crash. Found the red bug in the System Tray. Clicked on it and started to make a trace back. Saved trace back to file. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: 5.52.0 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 401883] Cannot Create address book folders
https://bugs.kde.org/show_bug.cgi?id=401883 --- Comment #1 from Mr. Dashiell M Barlow --- Possibly related: this happens when I attempt the steps with gdb: org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 QIODevice::read (QLocalSocket): device not open QIODevice::read (QLocalSocket): device not open -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 401901] New: Lockup Crash
https://bugs.kde.org/show_bug.cgi?id=401901 Bug ID: 401901 Summary: Lockup Crash Product: akregator Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: captain_ve...@posteo.net Target Milestone: --- SUMMARY Akregator crashes while opening/closing tabs. In attempting to make bug reports better, and reproduce backtrace for other bugs, began to use gdb to run Kontact components, found lockup crash with segfault. STEPS TO REPRODUCE 1. Use gdb to run Akregator. 2. Begin to work through feeds. 3. Complete akregator lockup crash. OBSERVED RESULT Crashes into a locked up state and stays there indefinitely (waited 15+ minutes) EXPECTED RESULT Multiple tabs as working through feeds, no lockup. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION : The page at 'https://www.oneangrygamer.net/2018/12/sargon-of-akkad-milo-yiannopoulos-james-allsup-banned-from-patreon/73136/' was loaded over HTTPS, but requested an insecure resource 'http://dtm.advertising.com/ids/411f1e96-3bde-4d85-b17e-63749e5f0695'. This request has been blocked; the content must be served over HTTPS." WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235126=261127: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access." WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235126=261127: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access." WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235126=313065: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access." WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235126=313065: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access." WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" [New Thread 0x7ffe65519700 (LWP 10181)] WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 1 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 119 message: "%c" WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235127=261127: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access." WebEnginePage::javaScriptConsoleMessage lineNumber: 0 message: "Failed to load https://nonitation.com/sas/player/vast2vast/linear2/linear.php?tagCode=UVYEaawWysox=600=300=http%3A%2F%2Fwww.oneangrygamer.net=1544305235127=261127: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://disqusads.com' is therefore not allowed access."
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 shevegen changed: What|Removed |Added CC||sheve...@gmail.com --- Comment #8 from shevegen --- (In reply to Christophe Giboudeaux from comment #6) > I can close as duplicate of the other bug report where most comments can be > reduced to "+1" if you prefer. While you could reason that way, the problem is that the other thread has lots more comments than the one here, so this is not ideal for discussions. I think it may have been better to mark the original one as a feature request and keep it open. Nobody would force xyz or you to work on it - it would just be one feature request of many more (or, in the event that it removed existing functionality, a regression, in which case the question is whether developers should have a higher right to modify code that affects the users, and I think the users should have a higher right if it comes to any functionality that has been working at some point. Losing functionality is always bad.). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Eridani RodrÃguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 401876] Text is way too small
https://bugs.kde.org/show_bug.cgi?id=401876 --- Comment #2 from Ben Daines --- (In reply to Laurent Montel from comment #1) > Heu... > configure->apparence -> font... Oh wow I'm an idiot. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 401876] Text is way too small
https://bugs.kde.org/show_bug.cgi?id=401876 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- Heu... configure->apparence -> font... -- You are receiving this mail because: You are the assignee for the bug.
