[kontact] [Bug 372903] Kontact crash on startup (Wayland)

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
it seems to have a bug with qtwebengine + wayland
https://bugreports.qt.io/browse/QTBUG-54038

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

[kontact] [Bug 372903] New: Kontact crash on startup (Wayland)

[IRIGOYEN Unai]

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

Bug ID: 372903
   Summary: Kontact crash on startup (Wayland)
   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: u.irigo...@gmail.com
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.8-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
Just launched Kontact on Wayland KDE session. Kontact window showed up for a
couple of seconds on mail view and then crashed. I can reproduce each time I
try to launch it.

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 0x7fe2ce630940 (LWP 5911))]

Thread 33 (Thread 0x7fe196df4700 (LWP 5970)):
#0  0x7fe2d96aa1f4 in g_source_iter_next () at /lib64/libglib-2.0.so.0
#1  0x7fe2d96ac63b in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fe2d96ad07b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fe2d96ad26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fe2e7205d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fe2e71b70ba in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fe2e7014643 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fe2e7018a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fe2de12d6ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fe2e640bf6f in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7fe1975f5700 (LWP 5969)):
#0  0x7fe2e64d in poll () at /lib64/libc.so.6
#1  0x7fe2d96ad156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe2d96ad26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe2e7205d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fe2e71b70ba in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fe2e7014643 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fe2e7018a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fe2de12d6ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fe2e640bf6f in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7fe197df6700 (LWP 5968)):
#0  0x7fe2e64d in poll () at /lib64/libc.so.6
#1  0x7fe2d96ad156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe2d96ad26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe2e7205d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fe2e71b70ba in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fe2e7014643 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fe2e7018a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fe2de12d6ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fe2e640bf6f in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fe19700 (LWP 5961)):
#0  0x7fe2e64d in poll () at /lib64/libc.so.6
#1  0x7fe2d96ad156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe2d96ad26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe2e7205d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fe2e71b70ba in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fe2e7014643 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fe2e7018a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fe2de12d6ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fe2e640bf6f in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fe1ac87a700 (LWP 5959)):
#0  0x7fe2e64d in poll () at /lib64/libc.so.6
#1  0x7fe2d96ad156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe2d96ad26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe2e7205d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fe2e71b70ba in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fe2e7014643 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fe2e7018a1a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7fe2de12d6ca in start_thread () at /lib64/libpthread.so.0
#8  0x7fe2e640bf6f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fe1af37e700 (LWP 5953)):
#0  0x7fe2e64d in poll () at /lib64/libc.so.6
#1  

[kmail] [Bug 254285] Kmail cannot include/insert remote images in signatures

[Solerman Kaplon]

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

Solerman Kaplon  changed:

   What|Removed |Added

 CC||soler...@wonder.com.br

--- Comment #3 from Solerman Kaplon  ---
Works for me in kmail 5.1.3

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

[kmail2] [Bug 300142] Kmail can't render a html signature

[Solerman Kaplon]

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

Solerman Kaplon  changed:

   What|Removed |Added

 CC||soler...@wonder.com.br

--- Comment #16 from Solerman Kaplon  ---
I upgraded to KMail 5.1.3 and image signatures are now showing correctly for me

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

[kmail2] [Bug 372866] KMail crashes on "normal" usage (scrolling/clicking on messages)

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

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

--- Comment #1 from Laurent Montel  ---
it's a problem with nouveau driver.

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