[kmail2] [Bug 368879] New: Kmail crashes after completion

2016-09-15 Thread rakoe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368879

Bug ID: 368879
   Summary: Kmail crashes after completion
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: koellnerr...@gmail.com

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I closed the application using the Close button
- Unusual behavior I noticed:
None
- System
Tumbleweed

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 0x7f714d84c940 (LWP 10344))]

Thread 10 (Thread 0x7f70f25fb700 (LWP 10412)):
#0  0x7f714048710f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f71314187f4 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f7131418839 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f7140481454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f714a5f33ff in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f70fc3c8700 (LWP 10379)):
#0  0x7f714048710f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f71367ac850 in mojo::system::Waiter::Wait(unsigned long, unsigned
int*) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f713679910c in mojo::system::Core::WaitManyInternal(unsigned int
const*, unsigned int const*, unsigned int, unsigned long, unsigned int*,
mojo::system::HandleSignalsState*) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f71367995b7 in
mojo::system::Core::WaitMany(mojo::system::UserPointer,
mojo::system::UserPointer, unsigned int, unsigned long,
mojo::system::UserPointer,
mojo::system::UserPointer) () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f7136795e35 in MojoWaitMany () from
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f7137e99937 in
mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState
const&, bool) () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f7137e99b6e in
mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*,
base::MessagePump::Delegate*) () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f7137e99ca9 in
mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) () from
/usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f713693d0ba in base::RunLoop::Run() () from
/usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f7136928a55 in base::MessageLoop::Run() () from
/usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f7136954ae6 in base::Thread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#11 0x7f713695123d in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#12 0x7f7140481454 in start_thread () from /lib64/libpthread.so.0
#13 0x7f714a5f33ff in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f710a3d5700 (LWP 10367)):
#0  0x7f71404874b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f71369492e2 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f71369577d9 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f7136957d13 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f713695123d in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f7140481454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f714a5f33ff in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f710abd6700 (LWP 10366)):
#0  0x7f71404874b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f71369492e2 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f71369577d9 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f7136957d13 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f713695123d in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f7140481454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f714a5f33ff in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f710b3d7700 (LWP 10365)):
#0  0x7f714048710f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7136949af5 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from

[kmail2] [Bug 368874] New: Feature request: "move message to..." in Message Window

2016-09-15 Thread JM via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368874

Bug ID: 368874
   Summary: Feature request: "move message to..." in Message
Window
   Product: kmail2
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: jabezm...@yahoo.com

I would like to have a "move message to..." icon in the toolbar of the Message
Window. So, after reading a message I can file it directly without going back
to the main window.

I tried Settings -> Configure Toolbars in the Message Window, but "move message
to..." is not an available action. Is it possible to add it?


Kmail 4.14.2 using KDE Development Platform 4.14.2 under Linux Mint 17.3 Rosa. 

Reproducible: Always

Steps to Reproduce:
1. Open message for viewing
2. In message window, do Settings -> Configure Toolbars 
3. Look for "move message to..." among available actions on left side 

Actual Results:  
"move message to..." is not an available action

Expected Results:  
Provide "move message to..." as an available action so it can be added to the
toolbar

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

[kmail2] [Bug 368843] kmail2 message view with qtwebengine hidpi is broken

2016-09-15 Thread Wolfgang Bauer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368843

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #3 from Wolfgang Bauer  ---
(In reply to Laurent Montel from comment #2)
> wrong we use "QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling)"

But maybe too late? ;-)

The docs say:
This attribute must be set before Q(Gui)Application is constructed

Anyway, I have a patch ready (as you may know meanwhile.
Just waiting for the reporter to try, then I will submit a review request.

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

[Akonadi] [Bug 359434] akonadictl stop / start : run 10 secondes and crash appear

2016-09-15 Thread NoWorries via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359434

--- Comment #2 from NoWorries  ---
Created attachment 101102
  --> https://bugs.kde.org/attachment.cgi?id=101102=edit
New crash information added by DrKonqi

akonadi_baloo_indexer (4.14) on KDE Platform 4.14.16 using Qt 4.8.7

Started Kontact and the akonadiserver crashed and the akonadiserver was using
100% of one CPU.  I then entered "akonadictl restart" and this error was
reported repeatedly

-- Backtrace (Reduced):
#6  0x7f4bc2f8b418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f4bc2f8d01a in __GI_abort () at abort.c:89
[...]
#11 0x7f4bc6c93db1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7f4bc41e1fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7f4bc41e8f16 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4

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

[Akonadi] [Bug 359434] akonadictl stop / start : run 10 secondes and crash appear

2016-09-15 Thread NoWorries via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359434

NoWorries  changed:

   What|Removed |Added

 CC||colegrove...@gmail.com

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

[knotes] [Bug 368856] New: Knotes makes notice scedules without command, libkdepim cannot be installed

2016-09-15 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368856

Bug ID: 368856
   Summary: Knotes makes notice scedules without command,
libkdepim cannot be installed
   Product: knotes
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: hans-viktor.hoffm...@online.de
CC: myr...@kde.org

After Starting Opensuse 42.1 KNotes produces sometimes additional notice
scedules, which are permanent and will appear at each starting of OpenSuse.  At
moment there are 10 scedules blocking partially the program line at the bottom
of the screen. New installation of knotes leads to the following protest of the
system:

 YaST2 conflicts list - generated 2016-09-02 20:55:38 

knotes5-15.12.3-18.5.x86_64 benötigt libkdepim = 15.12.3, kann jedoch nicht zur
Verfügung gestellt werden
Nicht installierbare Anbieter: libkdepim-15.12.3-18.5.x86_64[repo-update]
[ ] Folgende Aktionen werden ausgeführt:
Deinstallation von libkdepim4-4.14.10-3.10.x86_64
Deinstallation von korganizer-4.14.10-3.10.x86_64
Deinstallation von kontact-4.14.10-3.10.x86_64
Deinstallation von kmail-4.14.10-3.10.x86_64
Deinstallation von kdepim4-4.14.10-3.10.x86_64
Deinstallation von kaddressbook-4.14.10-3.10.x86_64
Deinstallation von akregator-4.14.10-3.10.x86_64
Deinstallation von kdepim4-runtime-4.14.10-3.4.x86_64
Deinstallation von akonadi-4.14.10-3.10.x86_64
[ ] knotes5-15.12.3-18.5.x86_64 nicht installieren

[ ] knotes5-15.12.3-18.5.x86_64 durch Ignorieren einiger Abhängigkeiten
brechen

 YaST2 conflicts list END ###

Best wishes
Manfred
Must I translate it for You?

Reproducible: Sometimes

Steps to Reproduce:
1.Starting Opensuse with kde 5.5.5 - sometimes
2. I do not know, how to reproduce it, but the scedules are permant
3.

Actual Results:  
10 permant knotice scedules

Expected Results:  
knotes ought work only after calling the program

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

[kmail2] [Bug 368843] kmail2 message view with qtwebengine hidpi is broken

2016-09-15 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368843

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #2 from Laurent Montel  ---
wrong we use "QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling)"

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

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

2016-09-15 Thread Kai Uwe Broulik via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364342

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||olivier+...@migeot.org

--- Comment #19 from Kai Uwe Broulik  ---
*** Bug 368853 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 368844] New: KMail crashes on startup

2016-09-15 Thread Tom Warnke via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368844

Bug ID: 368844
   Summary: KMail crashes on startup
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: tom.war...@kolabnow.com

Application: kmail (5.2.3)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
KMail crashes immediately when I start it. Kontact (with KMail embedded) shows
the same behaviour.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7efe8effd700 (LWP 10192)):
#0  0x7efeb6c57d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7efeb6c15d1d in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7efec33d9f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7efec33898cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7efec31d006a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7efec31d4899 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7efeb892c0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7efec28c602d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7efe8f7fe700 (LWP 10190)):
#0  0x7efec28b9ccd in read () at /lib64/libc.so.6
#1  0x7efeb6c56b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7efeb6c15df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7efeb6c15f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7efec33d9f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7efec33898cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7efec31d006a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7efec31d4899 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7efeb892c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7efec28c602d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7efe8700 (LWP 10188)):
#0  0x7efec28bdbfd in poll () at /lib64/libc.so.6
#1  0x7efeb6c15e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7efec33d9f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7efec33898cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7efec31d006a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7efec31d4899 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7efeb892c0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7efec28c602d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7efe9cb2b700 (LWP 10186)):
#0  0x7efeb6c57cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7efeb6c15d55 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7efec33d9f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7efec33898cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7efec31d006a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7efec31d4899 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7efeb892c0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7efec28c602d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7efe9d9af700 (LWP 10185)):
#0  0x7efeb6c1327c in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7efeb6c1583f in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7efeb6c15f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7efec33d9f7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7efec33898cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7efec31d006a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7efec31d4899 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7efeb892c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7efec28c602d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7efe9ebc0700 (LWP 10184)):
#0  0x7efec28bdbfd in poll () at /lib64/libc.so.6
#1  0x7efeb6c15e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efeb6c15f7c in g_main_context_iteration () at

[Akonadi] [Bug 368417] adding IMAP account causing akonadi_imap_resource segmentation faults

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368417

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Daniel Vrátil  ---
Thanks for the bug report. Could you please install debug info packages for
libakonadi-kde and provide a more complete backtrace? Also if you could test
with latest release (KDE Applications 16.08), it would be great. There's
actually quite a big chance we've fixed the crash.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 309216] (lib)akonadi crash

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=309216

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@kde.org
 Resolution|--- |UNMAINTAINED

--- Comment #1 from Daniel Vrátil  ---
Closing as unmaintained. The KResources integration has been removed in the
Qt5/KF5 version, and KDE4 version is no longer maintained.

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

[kmail2] [Bug 368843] kmail2 message view with qtwebengine hidpi is broken

2016-09-15 Thread Bruno Friedmann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368843

--- Comment #1 from Bruno Friedmann  ---
Created attachment 101098
  --> https://bugs.kde.org/attachment.cgi?id=101098=edit
Layout of message body on hidpi screen

Layout of message body on hidpi screen .

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

[kmail2] [Bug 368843] New: kmail2 message view with qtwebengine hidpi is broken

2016-09-15 Thread Bruno Friedmann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368843

Bug ID: 368843
   Summary: kmail2 message view with qtwebengine hidpi is broken
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: br...@ioda-net.ch

With hidpi 144 or more (I've 168 and 288 dpi screens) the display message
viewport is completely broken.

Seems kmail2 code doesn't apply this simple fix
https://bugreports.qt.io/browse/QTBUG-54114



Mention High-DPI on WebEngine documentation, and recommend to set

QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling)

before creating Q*Application.

THis is actually recommended for all applications (see
http://doc.qt.io/qt-5/highdpi.html). For WebEngineView specifically, it makes
sure that the default scaling factor of pages is reasonable.


Reproducible: Always

Steps to Reproduce:
1. open kmail2 with qtwebengine on high dpi screen
2. cry :-)
3. loose your eyes :-))


Actual Results:  
Wrong scale (dpi and scale factor) in message list
So click on link is no more feasible, copy and paste is completely wrong etc.
can't activate click to read pure html message and so on.

Expected Results:  
Wrong on hipdi as well on normal 96dpi

Screenshot coming

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

[kontact] [Bug 368841] New: Kontact crash when selecting a specific mail folder

2016-09-15 Thread rainer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368841

Bug ID: 368841
   Summary: Kontact crash when selecting a specific mail folder
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@munin-soft.de

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.2-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I tired this several time during the last days. When I select a specific folder
with a newly arrivied likely SPAM email, kontact crashes more or less directly.
Currently I run Kontact with the LIBGL_ALWAYS_SOFTWARE=1, as it unusable
unstable otherwise.

The crash can be reproduced every time.

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

Thread 51 (Thread 0x7f83ad7f8700 (LWP 13784)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83ad7f8700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 50 (Thread 0x7f83adff9700 (LWP 13783)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83adff9700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 49 (Thread 0x7f83ae7fa700 (LWP 13782)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83ae7fa700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 48 (Thread 0x7f83aeffb700 (LWP 13781)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83aeffb700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 47 (Thread 0x7f83af7fc700 (LWP 13780)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83af7fc700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 46 (Thread 0x7f83afffd700 (LWP 13779)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437248363 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83afffd700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 45 (Thread 0x7f83f49fa700 (LWP 13778)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8437247211 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843757e981 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83f49fa700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 44 (Thread 0x7f83f570e700 (LWP 13777)):
#0  0x7f8556b7510f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f843754dc5b in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f843754dc99 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f8556b6f454 in start_thread (arg=0x7f83f570e700) at
pthread_create.c:333
#4  0x7f855acc83ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 43 (Thread 0x7f83f705e700 (LWP 13654)):
#0  0x7f8555f62fa9 in

[Akonadi] [Bug 357527] Please update the bug tracker to current versions of Akonadi

2016-09-15 Thread Till Schäfer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=357527

Till Schäfer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds

2016-09-15 Thread Till Schäfer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

Till Schäfer  changed:

   What|Removed |Added

Version|16.04   |16.08

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

[Akonadi] [Bug 362420] DAV Resource 16.08.0: Segfaults randomly

2016-09-15 Thread Till Schäfer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362420

Till Schäfer  changed:

   What|Removed |Added

Version|unspecified |16.08

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

[Akonadi] [Bug 356747] Akonadiconsole crashes on a specific folder

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356747

Daniel Vrátil  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/akon
   |im/00db9bd7154d7b4785a6f4ac |adiconsole/218e0cb71265851e
   |3da8ee6a81830754|42838c646f79f64b0838f70f

--- Comment #2 from Daniel Vrátil  ---
Git commit 218e0cb71265851e42838c646f79f64b0838f70f by Daniel Vrátil.
Committed on 15/09/2016 at 09:37.
Pushed by dvratil into branch 'master'.

Fix Browser model crash when email is missing a header
FIXED-IN: 16.08.1

M  +15   -3src/akonadibrowsermodel.cpp

http://commits.kde.org/akonadiconsole/218e0cb71265851e42838c646f79f64b0838f70f

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

[Akonadi] [Bug 356747] Akonadiconsole crashes on a specific folder

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356747

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdep
   ||im/00db9bd7154d7b4785a6f4ac
   ||3da8ee6a81830754
   Version Fixed In||16.08.1
 Resolution|--- |FIXED

--- Comment #1 from Daniel Vrátil  ---
Git commit 00db9bd7154d7b4785a6f4ac3da8ee6a81830754 by Daniel Vrátil.
Committed on 15/09/2016 at 09:39.
Pushed by dvratil into branch 'Applications/16.08'.

Fix Browser model crash when email is missing a header
FIXED-IN: 16.08.1

M  +15   -3akonadiconsole/src/akonadibrowsermodel.cpp

http://commits.kde.org/kdepim/00db9bd7154d7b4785a6f4ac3da8ee6a81830754

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

[kontact] [Bug 368837] New: kmail crash when expiring messages in a folder

2016-09-15 Thread José Matos via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368837

Bug ID: 368837
   Summary: kmail crash when expiring messages in a folder
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jama...@fep.up.pt

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-0.rc5.git1.1.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I have a gmail account where I receive several mailing lists.

Since those mailing lists are archived elsewhere there is no need to have them
archived and at the same time kmail gets slow when reading huge folders.

So I have decided to expire messages. In some cases like this mail has crashed
while expiring the folders initially.

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

Thread 48 (Thread 0x7fa3f67fc700 (LWP 19701)):
#0  0x7fa422c37809 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fa42717e222 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7fa42718d558 in base::PosixDynamicThreadPool::WaitForTask() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7fa42718da8d in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5
#4  0x7fa427186c5c in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7fa422c316ca in start_thread () from /lib64/libpthread.so.0
#6  0x7fa42aed5f6f in clone () from /lib64/libc.so.6

Thread 47 (Thread 0x7fa24c9ff700 (LWP 19626)):
#0  0x7fa41e1d47e9 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fa41e18e9c1 in g_main_context_query () from /lib64/libglib-2.0.so.0
#2  0x7fa41e18f1a8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fa41e18f34c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fa42bccfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fa42bc810ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fa42bade643 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fa42bae2a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fa422c316ca in start_thread () from /lib64/libpthread.so.0
#9  0x7fa42aed5f6f in clone () from /lib64/libc.so.6

Thread 46 (Thread 0x7fa24d531700 (LWP 18416)):
#0  0x7fa42aeca00d in poll () from /lib64/libc.so.6
#1  0x7fa41e18f236 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fa41e18f34c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fa42bccfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fa42bc810ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fa42bade643 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fa42bae2a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fa422c316ca in start_thread () from /lib64/libpthread.so.0
#8  0x7fa42aed5f6f in clone () from /lib64/libc.so.6

Thread 45 (Thread 0x7fa24dd32700 (LWP 18414)):
#0  0x7fa41e1d47e9 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fa41e18e786 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7fa41e18f15b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fa41e18f34c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fa42bccfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fa42bc810ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fa42bade643 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fa42bae2a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fa422c316ca in start_thread () from /lib64/libpthread.so.0
#9  0x7fa42aed5f6f in clone () from /lib64/libc.so.6

Thread 44 (Thread 0x7fa24e533700 (LWP 18412)):
#0  0x7fa42aec5bdd in read () from /lib64/libc.so.6
#1  0x7fa41e1d3440 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fa41e18ed40 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fa41e18f1d4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fa41e18f34c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fa42bccfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7fa42bc810ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7

[Akonadi] [Bug 349439] Kmail crashes

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=349439

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Daniel Vrátil  ---


*** This bug has been marked as a duplicate of bug 291474 ***

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

[Akonadi] [Bug 291474] kmail crashed

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=291474

Daniel Vrátil  changed:

   What|Removed |Added

 CC||tony.alp...@yahoo.ca

--- Comment #5 from Daniel Vrátil  ---
*** Bug 349439 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 291474] kmail crashed

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=291474

Daniel Vrátil  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kmai
   |im/1e38a73a143552c4438543ce |l-account-wizard/d0941393fc
   |6d11b22d50a8927f|1502463fca6d02abe4c6a83da70
   ||0de

--- Comment #4 from Daniel Vrátil  ---
Git commit d0941393fc1502463fca6d02abe4c6a83da700de by Daniel Vrátil.
Committed on 15/09/2016 at 09:21.
Pushed by dvratil into branch 'master'.

Fix potential crash if ProviderPage::fillModel() is called twice

QStandardItemModel::removeRows() actually deletes the child item,
so we should not keep a dangling pointer to it around.
FIXED-IN: 16.08.1

M  +4-1src/providerpage.cpp

http://commits.kde.org/kmail-account-wizard/d0941393fc1502463fca6d02abe4c6a83da700de

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

[Akonadi] [Bug 291474] kmail crashed

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=291474

Daniel Vrátil  changed:

   What|Removed |Added

   Version Fixed In||16.08.1
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdep
   ||im/1e38a73a143552c4438543ce
   ||6d11b22d50a8927f
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Daniel Vrátil  ---
Git commit 1e38a73a143552c4438543ce6d11b22d50a8927f by Daniel Vrátil.
Committed on 15/09/2016 at 09:20.
Pushed by dvratil into branch 'Applications/16.08'.

Fix potential crash if ProviderPage::fillModel() is called twice

QStandardItemModel::removeRows() actually deletes the child item,
so we should not keep a dangling pointer to it around.
FIXED-IN: 16.08.1

M  +4-1accountwizard/src/providerpage.cpp

http://commits.kde.org/kdepim/1e38a73a143552c4438543ce6d11b22d50a8927f

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

[Akonadi] [Bug 288393] Segfault when creating account in Kmail

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=288393

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #6 from Daniel Vrátil  ---
Closing this issue, as current version does no longer use KJSEmbed, which seems
to be what crashed here.

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

[kdepim] [Bug 364994] Kmail crash when deleting message in thread view

2016-09-15 Thread Daniel Vrátil via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364994

Daniel Vrátil  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/mess
   ||agelib/c335c60684fb6de58fae
   ||567234c72277a3b1bf58
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||16.08.1

--- Comment #14 from Daniel Vrátil  ---
Git commit c335c60684fb6de58fae567234c72277a3b1bf58 by Daniel Vrátil.
Committed on 15/09/2016 at 08:42.
Pushed by dvratil into branch 'Applications/16.08'.

Expire dying parent from threading cache before processing children

Fixes a crash in the Model when a thread leader is removed and
ViewJob for its children is started to re-attach the subtree
to a new parent node. The second pass would then get a pointer
to the now-deleted parent from the threading cache leading to
a crash eventually.

This patch makes sure the parent is expired from the cache
before the ViewJobs are started. The cache miss triggers actual
threading calculation in Pass2 and Pass3 and updates our cache.
FIXED-IN: 16.08.1

M  +5-1messagelist/src/core/model.cpp
M  +1-0messagelist/src/core/threadingcache.h

http://commits.kde.org/messagelib/c335c60684fb6de58fae567234c72277a3b1bf58

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

[kmail2] [Bug 362575] Cannot unsubscribe IMAP folder

2016-09-15 Thread Olivier Churlaud via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362575

Olivier Churlaud  changed:

   What|Removed |Added

 CC||matt.drza...@gmail.com

--- Comment #2 from Olivier Churlaud  ---
*** Bug 362804 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 362804] Can't unsubscribe folder

2016-09-15 Thread Olivier Churlaud via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362804

Olivier Churlaud  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||oliv...@churlaud.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Olivier Churlaud  ---


*** This bug has been marked as a duplicate of bug 362575 ***

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