[kmail2] [Bug 387559] New: KMail crashes when retrieving mails

2017-12-03 Thread micu 
https://bugs.kde.org/show_bug.cgi?id=387559

Bug ID: 387559
   Summary: KMail crashes when retrieving mails
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: micuin...@gmx.de
  Target Milestone: ---

Application: kmail (5.6.3)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.16-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
Its always similar. At a sudden moment, Kmail starts fetching all of the mails
(it has already retrieved) again, then filters go loco... gets slower and
slower and then it would crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0b79ba5340 (LWP 3104))]

Thread 25 (Thread 0x7f0a17263700 (LWP 9564)):
#0  0x7f0b6f41613a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b6691d462 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668f3519 in base::PosixDynamicThreadPool::WaitForTask() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668f3a7b in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f0a167f8700 (LWP 4502)):
#0  0x7f0b734eb8bb in poll () at /lib64/libc.so.6
#1  0x7f0b5e270ed9 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f0b5e270fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f0b7435635b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f0b743040ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f0b741558ba in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f0b74159b92 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#8  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f0ab4dab700 (LWP 3154)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b668eea15 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668eeef7 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668efc91 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f0ab55ac700 (LWP 3153)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b668eea15 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668eeef7 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668efc91 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f0ab6c4e700 (LWP 3152)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b548dd604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f0b548dd649 in  () at /lib64/libQt5Script.so.5
#3  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f0ae57fa700 (LWP 3138)):
#0  0x7f0b7350698c in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7f0b73508764 in __fprintf_chk () at /lib64/libc.so.6
#2  0x7f0b57e463e0 in _warn_helper () at /lib64/libevent-2.0.so.5
#3  0x7f0b57e465a4 in event_warn () at /lib64/libevent-2.0.so.5
#4  0x7f0b57e4ad40 in epoll_dispatch () at /lib64/libevent-2.0.so.5
#5  0x7f0b57e358de in event_base_loop () at /lib64/libevent-2.0.so.5
#6  0x7f0b668bf849 in
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#7

[kontact] [Bug 387553] New: Kontact crash while exiting

2017-12-03 Thread Robert Scott 
https://bugs.kde.org/show_bug.cgi?id=387553

Bug ID: 387553
   Summary: Kontact crash while exiting
   Product: kontact
   Version: 5.2.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@humanleg.org.uk
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 9.2 (stretch)

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

Closing Kontact through right clicking on the Akregator system tray entry. No
main Kontact window open.

- Unusual behavior I noticed:

Kontact main window had been failing to repaint itself properly (was using
kmail pane).

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5253f09dc0 (LWP 29594))]

Thread 10 (Thread 0x7f51dd797700 (LWP 29603)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51dd797700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7f51ddf98700 (LWP 29602)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51ddf98700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f51de799700 (LWP 29601)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51de799700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f51def9a700 (LWP 29600)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d17f1 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51def9a700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f51d700 (LWP 29599)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f522c72475b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f522c724487 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f524b632494 in start_thread (arg=0x7f51d700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f522d972700 (LWP 29598)):
#0  0x7f52520212a9 in QMutex::unlock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f525224d7f1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5249834edd in g_main_context_prepare
(context=context@entry=0x7f51e990, priority=priority@entry=0x7f522d971b40)
at ././glib/gmain.c:3501
#3  0x7f524983591b in g_main_context_iterate
(context=context@entry=0x7f51e990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#4  0x7f5249835b0c in g_main_context_iteration (context=0x7f51e990,
may_block=1) at ././glib/gmain.c:3990
#5  0x7f525224e06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f52521f79ca in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f52520250f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5252029da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f524b632494 in start_thread (arg=0x7f522d972700) at
pthread_create.c:333
#10 0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 4 (Thread 0x7f522f432700 (LWP 29597)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f6c998b in  () at

[akregator] [Bug 387550] According to panopticlick 3.0 test does not protect against trackers

2017-12-03 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=387550

--- Comment #2 from Martin Steigerwald  ---
See also bug #387549 Konqueror: According to panopticlick 3.0 test does not
protect against trackers

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

[akregator] [Bug 387550] According to panopticlick 3.0 test does not protect against trackers

2017-12-03 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=387550

--- Comment #1 from Martin Steigerwald  ---
See also #387549 Konqueror: According to panopticlick 3.0 test does not protect
against trackers

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

[akregator] [Bug 387550] New: According to panopticlick 3.0 test does not protect against trackers

2017-12-03 Thread Martin Steigerwald 
https://bugs.kde.org/show_bug.cgi?id=387550

Bug ID: 387550
   Summary: According to panopticlick 3.0 test does not protect
against trackers
   Product: akregator
   Version: 5.6.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: internal browser
  Assignee: kdepim-bugs@kde.org
  Reporter: mar...@lichtvoll.de
  Target Milestone: ---

Created attachment 109188
  --> https://bugs.kde.org/attachment.cgi?id=109188=edit
akregator with results of panopticlick 3.0 test

Choosing major as priority according to the elected privacy by default goal.

Despite proxy settings pointing to Privoxy, as well as quite some ad blocking
lists enabled in the ad blocker settings according to
https://panopticlick.eff.org/ neither Konqueror 17.08 nor Akregator 17.08 block
trackers or protect against fingerprinting:

# How to reproduce
- Tell Konqueror to use Qt Webengine (only offered renderer in my Debian
Unstable system)
- Activate Ad filter in Module settings
- Activate EasyList Germany, Schuzak´s Universal Filter, Adblocklist.org,
EasyPrivacy+EasyList, Xfiles, Cedrics Liste
- Call https://panopticlick.eff.org/
- Run the test

# Actual results
TestResult
Is your browser blocking tracking ads?  ✗ no
Is your browser blocking invisible trackers?✗ no
Does your browser unblock 3rd parties that promise to honor Do Not Track?  
✗ no
Does your browser protect from fingerprinting?  ✗ no

It suggests me to install Privacy Badger. Which I can´t and I won´t, cause it
is easily fingerprintable as it learns what to block.

# Expected results
Konqueror / Akregator blocks trackers at least if being told to.

Or even better: Konqueror / Akregator block trackers *by default*.

It appears to be better for me to switch to some RSS feed reading withing
Firefox. Together with uBlock Origin and probably some of my other tweaks it
blocks trackers nicely.

# Recommendation
I strongly suggest into looking whether uBlock Origin would be adaptable to
Konqueror / Qupzilla/Falcon / Akregator. It does its job. It does its job well.
It is properly maintained. And I see no point in reinventing it.

I also strongly suggesting *unifying* Qt Webengine privacy/adblock integration.
>From a usability point of view I don´t see why I should do the same privacy
related settings in two completely different GUIs.

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