[akregator] [Bug 390246] New: Crash after OPML import

[Daniel]

https://bugs.kde.org/show_bug.cgi?id=390246

Bug ID: 390246
   Summary: Crash after OPML import
   Product: akregator
   Version: 5.7.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: c...@daniel.priv.no
  Target Milestone: ---

Application: akregator (5.7.2)

Qt Version: 5.9.3
Frameworks Version: 5.43.0
Operating System: Linux 4.13.0-32-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
I imported some 200 feeds. I noticed a folder at the bottom of the folder list
that didn’t have a title. I right-clicked on this folder and then Akregator
crashed.

-- 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 0x7fc50304f980 (LWP 11592))]

Thread 28 (Thread 0x7fc461536700 (LWP 11633)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc4d58dd60b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fc4d58dd517 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7fc4f95216ba in start_thread (arg=0x7fc461536700) at
pthread_create.c:333
#4  0x7fc4fef5641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fc460d35700 (LWP 11632)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc4d58dd60b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fc4d58dd517 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7fc4f95216ba in start_thread (arg=0x7fc460d35700) at
pthread_create.c:333
#4  0x7fc4fef5641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fc462df6700 (LWP 11630)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc4ebe73d04 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fc4ebe73d49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fc4f95216ba in start_thread (arg=0x7fc462df6700) at
pthread_create.c:333
#4  0x7fc4fef5641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fc463ffd700 (LWP 11627)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc4ef9af35f in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7fc4ef9afaf7 in base::SequencedWorkerPool::Worker::Run() () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7fc4ef9b08c0 in base::SimpleThread::ThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc4ef9acf2d in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc4f95216ba in start_thread (arg=0x7fc463ffd700) at
pthread_create.c:333
#6  0x7fc4fef5641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fc48cff9700 (LWP 11624)):
#0  0x7fc4fef4627d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc4f77f16f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc4f77ade74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc4f77ae330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc4f77ae49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc4ff8716cb in QEventDispatcherGlib::processEvents
(this=0x7fc478c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fc4ff819e2a in QEventLoop::exec (this=this@entry=0x7fc48cff8c40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fc4ff6428f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#8  0x7fc4ff647709 in QThreadPrivate::start (arg=0x27be920) at
thread/qthread_unix.cpp:368
#9  0x7fc4f95216ba in start_thread (arg=0x7fc48cff9700) at
pthread_create.c:333
#10 0x7fc4fef5641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fc48d7fa700 (LWP 11623)):
#0  0x7fc4fef4627d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc4df3cef61 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7fc4e6136a2e in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fc4e61374a0 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fc4e6137560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fc4e61457a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381929

nia1048...@gmail.com changed:

   What|Removed |Added

 CC|nia1048...@gmail.com|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

[Daniel]

https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #26 from Daniel  ---
The problem here may be that QDateTime can return -1 for invalid dates. Cast to
a 32-bit unsigned int, -1 is 4294967295, and interpreted as a timestamp that's
exactly 2106-02-07 07:28. The code doesn’t handle this case, as far as I can
tell.

Notably, I’ve had this happen with completely valid feeds with correct time
zone and ISO time strings. I’m not sure what the root cause is. The same feeds
will work if I delete all Akregator settings and import it anew.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Frederik Schwarzer]

https://bugs.kde.org/show_bug.cgi?id=381929

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #23 from Frederik Schwarzer  ---
Thanks for the proposed patch. I was hit by that problem today and am still
panicking a bit while restoring my feeds. :D

I am not that familiar with the Qt pointers but might a QScopedPointer be
enough here?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

[ml]

https://bugs.kde.org/show_bug.cgi?id=383710

ml  changed:

   What|Removed |Added

 CC||iivan...@gmail.com

--- Comment #15 from ml  ---
(In reply to K G from comment #14)
> This fix do not prevent from corrupting feeds. In my case it was happening
> sometimes after akregator crash.
> 
> It only make akregator usable with global menu. it avoids akregator crashing
> 100% times. After applying this patch, I didn't have any crash.

I can confirm this patch fixes akregator crash with global menu enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Mark Gannon]

https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #22 from Mark Gannon  ---
Created attachment 110511
  --> https://bugs.kde.org/attachment.cgi?id=110511=edit
Exit slotSaveFeedList() if feed is empty without writing anyfiles

The last time slotSaveFeedList() was being called with an empty feed list.  The
attached patch checks to see if the feed is null, and if so, returns without
writing any files.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=383710

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.

[akregator] [Bug 383710] akregator always crashed on next login "with start with the system"

[K G]

https://bugs.kde.org/show_bug.cgi?id=383710

--- Comment #14 from K G  ---
This fix do not prevent from corrupting feeds. In my case it was happening
sometimes after akregator crash.

It only make akregator usable with global menu. it avoids akregator crashing
100% times. After applying this patch, I didn't have any crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 390206] Kontact crash on Kmail message search

[Pierre Maraval]

https://bugs.kde.org/show_bug.cgi?id=390206

--- Comment #2 from Pierre Maraval  ---
The "Filter by status" function and the Tag selector both work flawlessly. Only
the search typing field causes the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 390206] Kontact crash on Kmail message search

[Pierre Maraval]

https://bugs.kde.org/show_bug.cgi?id=390206

--- Comment #1 from Pierre Maraval  ---
The "Filter by status" function and the Tag selector both work flawlessly. Only
the search typing field causes the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 390206] New: Kontact crash on Kmail message search

[Pierre Maraval]

https://bugs.kde.org/show_bug.cgi?id=390206

Bug ID: 390206
   Summary: Kontact crash on Kmail message search
   Product: kontact
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: marava...@yahoo.fr
  Target Milestone: ---

Application: kontact (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.104-39-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:

Reading mails on Kmail on OpenSUSE Leap 42.3

- Unusual behavior I noticed:

Typing into the search field in the message list (of IMAP accounts) and
pressing Enter or waiting a little makes Kontact crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5882988780 (LWP 26806))]

Thread 24 (Thread 0x7f571b7fe700 (LWP 2148)):
#0  0x7f587b389478 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5872b889b2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f5872b963f6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f5872b965e6 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f5872b9031e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f587b384724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f587f3e3c1d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f574d628700 (LWP 26875)):
#0  0x7f587a76bf25 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#1  0x7f587a74637c in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f587a7471d5 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f587a74742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f587fefd1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f587feaabfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f587fceaa29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f587b384724 in start_thread () at /lib64/libpthread.so.0
#9  0x7f587f3e3c1d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f574f769700 (LWP 26870)):
#0  0x7f587b3890cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5872b925d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f5872b92d9d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f5872b935c0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f5872b9031e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f587b384724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f587f3e3c1d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f5766cdb700 (LWP 26838)):
#0  0x7f587f3db37d in poll () at /lib64/libc.so.6
#1  0x7f587a747314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f587a74742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f587fefd1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f587feaabfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f587fceaa29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f587b384724 in start_thread () at /lib64/libpthread.so.0
#8  0x7f587f3e3c1d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f57674dc700 (LWP 26837)):
#0  0x7f587f3db37d in poll () at /lib64/libc.so.6
#1  0x7f587a747314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f587a74742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f587fefd1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f587feaabfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f587fceaa29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f587b384724 in start_thread () at /lib64/libpthread.so.0
#8  0x7f587f3e3c1d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f576835f700 (LWP 26836)):
#0  0x7f587f3d73fd in read () at /lib64/libc.so.6
#1  0x7f587a787750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f587a746e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f587a7472a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f587a74742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f587fefd1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f587feaabfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  

[kmail2] [Bug 387177] KMail crashes on exit - accessing KMMainWindow status bar during destruction?

[Dennis Schridde]

https://bugs.kde.org/show_bug.cgi?id=387177

--- Comment #1 from Dennis Schridde  ---
Created attachment 110504
  --> https://bugs.kde.org/attachment.cgi?id=110504=edit
New crash information added by DrKonqi

kmail (5.7.1) using Qt 5.9.4

- What I was doing when the application crashed:

I closed KMail after retrieving emails and it crashed a while after being
closed.

-- Backtrace (Reduced):
#7  0x7fa2815c5e5e in QMainWindowLayout::statusBar (this=)
at widgets/qmainwindowlayout.cpp:2332
#8  0x7fa2815c1b78 in QMainWindow::statusBar (this=0x55de9b4f9380) at
widgets/qmainwindow.cpp:623
#9  0x7fa2825ae0d9 in KMMainWin::displayStatusMessage (this=0x55de9b4f9380,
aText=...) at
/var/tmp/portage/kde-apps/kmail-17.12.1-r1/work/kmail-17.12.1/src/kmmainwin.cpp:106
#10 0x7fa280847da6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd576b7180,
r=0x55de9b4f9380, this=0x55de9bb87de0) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
[...]
#12 0x7fa277019b62 in KPIM::BroadcastStatus::statusMsg(QString const&) ()
from /usr/lib64/libKF5Libkdepim.so.5

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387177] KMail crashes on exit - accessing KMMainWindow status bar during destruction?

[Dennis Schridde]

https://bugs.kde.org/show_bug.cgi?id=387177

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

-- 
You are receiving this mail because:
You are the assignee for the bug.