[kmail2] [Bug 359260] New: Launching kmail5 give crash

2016-02-11 Thread Bruno Friedmann via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359260

Bug ID: 359260
   Summary: Launching kmail5 give crash
   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: br...@ioda-net.ch

Application: kmail (5.1.1)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160208) (x86_64)"

-- Information about the crash:
After starting my kde plasma5 session, I launch kmail using my global shortcut
(meta+J) immediately this crash dialog appear. Then the complete interface
start and work afterwards.

The crash can be reproduced sometimes.

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

Thread 16 (Thread 0x7f025d8f0700 (LWP 3900)):
#0  0x7f028146524d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f02743fe432 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f025d8efb80) at /usr/include/bits/poll2.h:46
#2  0x7f02743fe432 in _xcb_conn_wait (c=c@entry=0x1f441e0,
cond=cond@entry=0x1f44220, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7f027447 in xcb_wait_for_event (c=0x1f441e0) at xcb_in.c:693
#4  0x7f025fc49e29 in QXcbEventReader::run() (this=0x1f51400) at
qxcbconnection.cpp:1229
#5  0x7f0281d6c94f in QThreadPrivate::start(void*) (arg=0x1f51400) at
thread/qthread_unix.cpp:331
#6  0x7f02777fd4a4 in start_thread (arg=0x7f025d8f0700) at
pthread_create.c:334
#7  0x7f028146dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f02571df700 (LWP 3919)):
#0  0x7f0277805d9a in __lll_unlock_wake () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371
#1  0x7f0277801121 in __pthread_mutex_unlock_usercnt (mutex=0x7f02765965d0,
decr=) at pthread_mutex_unlock.c:57
#2  0x7f0276317ce5 in  () at /usr/X11R6/lib64/libGL.so.1
#3  0x7f027631d018 in  () at /usr/X11R6/lib64/libGL.so.1
#4  0x7f026b529001 in  () at /usr/lib64/tls/libnvidia-tls.so.352.79
#5  0x7f0277322210 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f02571deab0, __fd=) at /usr/include/bits/unistd.h:44
#6  0x7f0277322210 in g_wakeup_acknowledge (wakeup=0x7f02580015b0) at
gwakeup.c:210
#7  0x7f02772dfd94 in g_main_context_check
(context=context@entry=0x7f0259b0, max_priority=2147483647,
fds=fds@entry=0x7f02500013c0, n_fds=n_fds@entry=1) at gmain.c:3632
#8  0x7f02772e0208 in g_main_context_iterate
(context=context@entry=0x7f0259b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3837
#9  0x7f02772e036c in g_main_context_iteration (context=0x7f0259b0,
may_block=may_block@entry=1) at gmain.c:3901
#10 0x7f0281f9152b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0258e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#11 0x7f0281f3b63a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f02571dec90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#12 0x7f0281d67b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#13 0x7f0281d6c94f in QThreadPrivate::start(void*) (arg=0x20faf40) at
thread/qthread_unix.cpp:331
#14 0x7f02777fd4a4 in start_thread (arg=0x7f02571df700) at
pthread_create.c:334
#15 0x7f028146dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f025493f700 (LWP 4617)):
#0  0x7f02773234d4 in g_mutex_unlock (mutex=0x7f0238002cd0) at
gthread-posix.c:1350
#1  0x7f02772e0376 in g_main_context_iteration (context=0x7f0238002cd0,
may_block=may_block@entry=1) at gmain.c:3902
#2  0x7f0281f9152b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0238002c00, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f0281f3b63a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f025493ec90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#4  0x7f0281d67b1c in QThread::exec() (this=) at
thread/qthread.cpp:503
#5  0x7f0281d6c94f in QThreadPrivate::start(void*) (arg=0x258c7c0) at
thread/qthread_unix.cpp:331
#6  0x7f02777fd4a4 in start_thread (arg=0x7f025493f700) at
pthread_create.c:334
#7  0x7f028146dbdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f0255140700 (LWP 4619)):
#0  0x7f028146524d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f02772e0264 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f0244003070, timeout=, context=0x7f0244002ed0) at
gmain.c:4135
#2  0x7f02772e0264 in g_main_context_iterate
(context=context@entry=0x7f0244002ed0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f02772e036c in

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Grégory Oestreicher via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #11 from Grégory Oestreicher  ---
> --- Comment #10 from Stephan Olbrich  ---
> in kdebugdialog5 I see kio_http and kio_http_debug. I selected both.

Yup, seems good. Note that the HTTP Authorization may be written in the logs,
so remove it before sending the .xsession-errors file. Not doing so would leave
your password in the clear.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Grégory Oestreicher via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #9 from Grégory Oestreicher  ---
The full name on my station is "KIO HTTP slave (KIO)", but searching for "http"
should show up only this one. Also maybe on your version you have to use
"kdebugdialog" or "kdebugdialog5".

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message

2016-02-11 Thread Thomas Fischer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359063

--- Comment #2 from Thomas Fischer  ---
Created attachment 97157
  --> https://bugs.kde.org/attachment.cgi?id=97157=edit
Before rendering HTML code, showing rendering issues with
iso-8859-1/quoted-printable-encoded HTML text

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Stephan Olbrich via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #8 from Stephan Olbrich  ---
I enabled dav logs but there is no kio http

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message

2016-02-11 Thread Thomas Fischer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359063

Thomas Fischer  changed:

   What|Removed |Added

 CC||fisc...@unix-ag.uni-kl.de

--- Comment #1 from Thomas Fischer  ---
I may have the same problem. My observation is as follows:
The user receives a HTML-only mail in an European language (which makes use of
non-ASCII characters code 128-255 such as åäö), the mail is quoted-printable
encoded.
My test case mail's source code looks like this:



abc123=E5=E4=F6ABC123=C5=C4=D6


The relevant mail headers look like this:
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

This mail should look like this when correctly displayed:

abc123åäö
ABC123ÅÄÖ

I'll attach two screen shots. One will reproduce how the mail is displayed in
"non-HTML" mode, where a box is show for the use to "click here" to render the
HTML code. The second screen shot reproduces the output of just this render.
Please observe the incorrect rendering in the first screenshot.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message

2016-02-11 Thread Thomas Fischer via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359063

--- Comment #3 from Thomas Fischer  ---
Created attachment 97158
  --> https://bugs.kde.org/attachment.cgi?id=97158=edit
After confirming that HTML code should be rendered

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359138] KMail doesn't set "In-Reply-To" and "References" headers when forwarding

2016-02-11 Thread kolAflash via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359138

--- Comment #1 from kolAflash  ---
Looks like Thunderbird is also setting this reasonable additional header when
forwarding.
X-Forwarded-Message-Id: ...

So a header-template could look like this:
References: %OHEADER="References" %OHEADER="Message-ID"
In-Reply-To: %OHEADER="Message-ID"
X-Forwarded-Message-Id: %OHEADER="Message-ID"

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359266] New: kmail Search filter

2016-02-11 Thread Jarek via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359266

Bug ID: 359266
   Summary: kmail Search filter
   Product: kmail2
   Version: 4.14.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: kdepim-bugs@kde.org
  Reporter: aj.k...@linux.pl
CC: m...@vhanda.in

Do not look for work.
Search filters do not work.
Search filters is fiction.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 359266] kmail Search filter

2016-02-11 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359266

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Ok good bug report.

Please create a real bug report with testcase, usercase etc.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Stephan Olbrich via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #10 from Stephan Olbrich  ---
in kdebugdialog5 I see kio_http and kio_http_debug. I selected both.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 359286] New: KMail and Kontact crash on startup

2016-02-11 Thread Daniel Dewald via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359286

Bug ID: 359286
   Summary: KMail and Kontact crash on startup
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: thecras...@gmx.de

Application: kontact (5.1.49 pre)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.1-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

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

I started Kontact (its the same result just starting KMail standalone). It
immediately crashes.

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 0x7f308306e800 (LWP 29543))]

Thread 16 (Thread 0x7f307d3a5700 (LWP 29546)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309566d7ab in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309566d7e9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f3036d88700 (LWP 29547)):
#0  0x7f308ffc7149 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f308ffc960b in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f308ffca00b in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f308ffca1ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f3098105f1b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f30980b8b3a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f3097f166e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f3097f1ac22 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#9  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f302f7a7700 (LWP 29549)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537bf64 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f302efa6700 (LWP 29550)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f302e7a5700 (LWP 29551)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f302dfa4700 (LWP 29552)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f30257a3700 (LWP 29553)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f302d7a3700 (LWP 29554)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f302cfa2700 (LWP 29555)):
#0  0x7f3091b669cf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f309537cf93 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f309569d451 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f3091b61354 in start_thread () from /lib64/libpthread.so.0
#4  0x7f30976309cd in clone () from

[kontact] [Bug 359295] New: Kontact crashes when installing third-party header theme Material through GHNS

2016-02-11 Thread Gary 
https://bugs.kde.org/show_bug.cgi?id=359295

Bug ID: 359295
   Summary: Kontact crashes when installing third-party header
theme Material through GHNS
   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: gree...@kde.org

Application: kontact (5.1.48 pre)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Installing a new header theme through the GHNS wizard. Unsure if this is
related to the specific theme or not. The theme I was attempting to install is
called Material.

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

Thread 61 (Thread 0x7f090074b700 (LWP 32344)):
#0  0x7f09190eec1d in poll () at /lib64/libc.so.6
#1  0x7f0912872422 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1
#2  0x7f091287400f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f090289b3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f09199fd44f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 60 (Thread 0x7f08f3215700 (LWP 32345)):
#0  0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f09169ec733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f09169ec759 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 59 (Thread 0x7f08b2252700 (LWP 32346)):
#0  0x7f09199f5cda in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f0919c30ba5 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f0911c314ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0911c31d80 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f0911c31f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f0919c30c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f0919bd7c73 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f09199f872a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f09199fd44f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 58 (Thread 0x7f08a61cd700 (LWP 32347)):
#0  0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f08b0d91ae3 in radeon_drm_cs_emit_ioctl () at
/usr/lib64/dri/r600_dri.so
#2  0x7f08b0d91337 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so
#3  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 57 (Thread 0x7f08a4d09700 (LWP 32348)):
#0  0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f09166f875d in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f0916a1b031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 56 (Thread 0x7f08a4508700 (LWP 32349)):
#0  0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f09166f9733 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7f0916a1b031 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 55 (Thread 0x7f0892ca7700 (LWP 32350)):
#0  0x7f0919c3175b in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f0911c318f1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f0911c31df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0911c31f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0919c30c7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f0919bd7c73 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f09199f872a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f09199fd44f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f09190f704d in clone () at /lib64/libc.so.6

Thread 54 (Thread 0x7f08924a6700 (LWP 32351)):
#0  0x7ffe27159b26 in clock_gettime ()
#1  0x7f0919103c9d in clock_gettime () at /lib64/libc.so.6
#2  0x7f0919aae906 in  () at

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Stephan Olbrich via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #6 from Stephan Olbrich  ---
It is on a desktop with ethernet connection.
The caldav/carddav is from owncloud running on a server in the same network.
Is there any logging I could enable? Or logfiles to look at when it happens
again?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 359277] New: Crash when opening Website

2016-02-11 Thread Bernd Rappe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359277

Bug ID: 359277
   Summary: Crash when opening Website
   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: bernd.ra...@t-online.de

Application: kontact (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-32-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
1) New start of Kontact
2) Opening all news
3) Select an entry in the owerview list on the right side
4) The Website crashes during loading:

[Part]
Children=T1
T1_mimetype=text/html
T1_url=http://www.tagesschau.de/ausland/gravitationswellen-nachweis-105.html
T1_zoom=-1
activeChildIndex=0
crashed=true
searchCombo=0
searchLine=

The same happens on/with many other Websites, not all...?

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 0x7f4bf6287800 (LWP 2637))]

Thread 10 (Thread 0x7f4bd88bc700 (LWP 2638)):
#0  0x7f4bed89f05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4bf1045686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f4bf10456b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f4b97f99700 (LWP 2639)):
#0  0x7f4bed89f05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4bf0db7e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f4bf106d1e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f4b8461b700 (LWP 2642)):
#0  0x7f4bed2cf149 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f4bed2cfb03 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4bed2cfcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4bf3fa20de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f4bf3f73e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f4bf3f74165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f4bf3e710bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f4bf3e7379f in  () at /usr/lib64/libQtCore.so.4
#8  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f4b81f37700 (LWP 2645)):
#0  0x7f4bf381fc5d in poll () at /lib64/libc.so.6
#1  0x7f4bed2cfbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4bed2cfcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4bf3fa20de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f4bf3f73e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f4bf3f74165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f4bf3e710bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f4bf3f55783 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f4bf3e7379f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f4b5e069700 (LWP 2678)):
#0  0x7f4bf381bd2d in read () at /lib64/libc.so.6
#1  0x7f4bed310750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4bed2cf714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4bed2cfb7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4bed2cff0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#5  0x7f4b60ceb946 in  () at /usr/lib64/libgio-2.0.so.0
#6  0x7f4bed2f4b85 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f4b5d868700 (LWP 2679)):
#0  0x7f4bf381fc5d in poll () at /lib64/libc.so.6
#1  0x7f4bed2cfbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4bed2cfcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4bed2cfd29 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4bed2f4b85 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f4bed89b0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4bf382808d in clone () at /lib64/libc.so.6

Thread 4 (Thread

[Akonadi] [Bug 358329] akonadi keeps loosing caldav calendars

2016-02-11 Thread Grégory Oestreicher via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358329

--- Comment #7 from Grégory Oestreicher  ---
Yes, you can use "kdebugsettings" and enable all logs from the dav resource and
kio http. Those logs will be written in your ~/.xsession-errors.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs