[Akonadi] [Bug 397589] Crash while first starting Kmail

2018-10-10 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=397589

--- Comment #6 from Martin Tlustos  ---
In case the reporter does not supply more info, should I try to run kmail in
gdb?

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

[Akonadi] [Bug 388196] akonadi_control crash after login

2018-10-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=388196

--- Comment #4 from Christoph Feck  ---
Comment #1 is bug 392092.

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

[Akonadi] [Bug 397589] Crash while first starting Kmail

2018-10-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=397589

--- Comment #5 from Christoph Feck  ---
>From the backtrace, could be. But the fatal() message could also be different,
and without the Qt logging output, we cannot know. Comment #2 either does not
show the complete output, or Qt logging was redirected elsewhere
(xorg-session.log, systemd log, ...)

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

[Akonadi] [Bug 398918] Akonadi server crashes after enabling Notification Monitor

2018-10-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=398918

--- Comment #1 from Christoph Feck  ---
Pasting relevant part of backtrace from comment #0:

Thread 3 (Thread 0x7fcbed5f5700 (LWP 27402)):
[KCrash Handler]
#6  std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/bits/atomic_base.h:713
#7  std::atomic::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/atomic:452
#8 
QAtomicOps::load
(_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227
#9  QBasicAtomicPointer::load
(this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:238
#10 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x0) at
tools/qsharedpointer.cpp:1445
#11 0x5626c27c9fd1 in
QWeakPointer::QWeakPointer
(ptr=0x0, this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:684
#12 QPointer::QPointer (p=0x0,
this=) at /usr/include/qt5/QtCore/qpointer.h:71
#13 Akonadi::Server::NotificationSubscriber::notify (this=this@entry=0x0,
notification=...) at
/var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationsubscriber.cpp:646
#14 0x5626c27c2ca6 in
Akonadi::Server::NotificationManager::emitPendingNotifications
(this=0x5626c2b76230) at
/var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationmanager.cpp:226
#15 0x7fcbf99890a7 in QtPrivate::QSlotObjectBase::call (a=0x7fcbed5f4500,
r=0x5626c2b76230, this=0x7fcbe0005120) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#16 QMetaObject::activate (sender=sender@entry=0x7fcbe0004f00,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fcbed5f4500) at kernel/qobject.cpp:3750
#17 0x7fcbf9989607 in QMetaObject::activate
(sender=sender@entry=0x7fcbe0004f00, m=m@entry=0x7fcbf9da8ec0
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fcbed5f4500) at kernel/qobject.cpp:3629
#18 0x7fcbf9995427 in QTimer::timeout (this=this@entry=0x7fcbe0004f00,
_t1=...) at .moc/moc_qtimer.cpp:200
#19 0x7fcbf9995738 in QTimer::timerEvent (this=0x7fcbe0004f00, e=) at kernel/qtimer.cpp:255
#20 0x7fcbf9989c8b in QObject::event (this=0x7fcbe0004f00, e=) at kernel/qobject.cpp:1269
#21 0x7fcbf996025a in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1099
#22 0x7fcbf9960347 in QCoreApplication::notifyInternal2
(receiver=0x7fcbe0004f00, event=event@entry=0x7fcbed5f4680) at
kernel/qcoreapplication.cpp:1024
#23 0x7fcbf99b0c8b in QCoreApplication::sendEvent (event=0x7fcbed5f4680,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
#24 QTimerInfoList::activateTimers (this=0x7fcbe0004cf0) at
kernel/qtimerinfo_unix.cpp:643
#25 0x7fcbf99b1581 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:182
#26 0x7fcbf5a4a5a7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#27 0x7fcbf5a4a810 in ?? () from /usr/lib64/libglib-2.0.so.0
#28 0x7fcbf5a4a8bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#29 0x7fcbf99b19bf in QEventDispatcherGlib::processEvents
(this=0x7fcbeb20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x7fcbf995f0ba in QEventLoop::exec (this=this@entry=0x7fcbed5f4910,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#31 0x5626c27c3963 in
Akonadi::Server::NotificationManager::waitForSocketData (this=0x5626c2b76230)
at
/var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationmanager.cpp:129
#32 0x7fcbf99954d4 in QtPrivate::QSlotObjectBase::call (a=0x7fcbed5f49c0,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#33 QSingleShotTimer::timerEvent (this=0x7fcbe00142e0) at kernel/qtimer.cpp:318
#34 0x7fcbf9989c8b in QObject::event (this=0x7fcbe00142e0, e=) at kernel/qobject.cpp:1269
#35 0x7fcbf996025a in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1099
#36 0x7fcbf9960347 in QCoreApplication::notifyInternal2
(receiver=0x7fcbe00142e0, event=event@entry=0x7fcbed5f4b10) at
kernel/qcoreapplication.cpp:1024
#37 0x7fcbf99b0c8b in QCoreApplication::sendEvent (event=0x7fcbed5f4b10,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
#38 QTimerInfoList::activateTimers (this=0x7fcbe0004cf0) at
kernel/qtimerinfo_unix.cpp:643
#39 0x7fcbf99b1581 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:182
#40 0x7fcbf5a4a5a7 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#41 0x7fcbf5a4a810 in ?? () from /usr/lib64/libglib-2.0.so.0
#42 0x7fcbf5a4a8bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#43 0x7fcbf99b19bf in QEventDispatcherGlib::processEvents
(this=0x7fcbeb20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#44 0x7fcbf995f0ba in QEventLoop::exec (this=this@entry=0x7fcbed5f4d60,
flags=..., 

[akregator] [Bug 382575] Akregator crash when middle-clicking a link

2018-10-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=382575

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED

--- Comment #4 from Christoph Feck  ---
See comment #2.

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

[kmail2] [Bug 399632] Can't load mail via VPN

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399632

sr-tr...@yandex.ru changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from sr-tr...@yandex.ru ---
Bad ipv6 setups on VPN

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

[kmail2] [Bug 399632] Can't load mail via VPN

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399632

sr-tr...@yandex.ru changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[korganizer] [Bug 332048] Opening an existing To-do item for editing results in both the "Start" and "Due" times (yyyy MM dd hh mm ss) changing

2018-10-10 Thread Denis Kurz
https://bugs.kde.org/show_bug.cgi?id=332048

Denis Kurz  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||kde...@posteo.de
Version|5.7.3   |5.9.1
 Ever confirmed|0   |1
  Component|todoview|incidence editors
   Keywords|triaged |

--- Comment #6 from Denis Kurz  ---
Still present in 5.9.1. Spoiler: will still be present in 5.9.2. It also
happens for events, so I move this from component todoview to incidenceeditor.

I just learned about incidence templates in KOrganizer, which kind of puzzles
me after having used KOrganizer for quite some time now... Templates do not
appear anywhere other than the incidence editor: not in any menu and neither in
the preferences. Discoverability could probably be improved. Still not sure if
I use templates correctly.

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

[kmail2] [Bug 399632] New: Can't load mail via VPN

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399632

Bug ID: 399632
   Summary: Can't load mail via VPN
   Product: kmail2
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sr-tr...@yandex.ru
  Target Milestone: ---

Kmail and Akregator don't update content (mail & rss) via VPN connection.


STEPS TO REPRODUCE
1. Connect to VPN
2. get mail or news

OBSERVED RESULT
Can't connect to server

EXPECTED RESULT
Update content

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
OS: Archlinux x64

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

[kmail2] [Bug 399631] New: kmail crash after update with segmentation fault, korganizer too

2018-10-10 Thread Paul Heeg
https://bugs.kde.org/show_bug.cgi?id=399631

Bug ID: 399631
   Summary: kmail crash after update with segmentation fault,
korganizer too
   Product: kmail2
   Version: 5.7.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: paul.h...@ibaf.de
  Target Milestone: ---

Created attachment 115549
  --> https://bugs.kde.org/attachment.cgi?id=115549=edit
"die gesmmelten Absturzinformationen sind nutzlos"

SUMMARY


STEPS TO REPRODUCE
1. update deb http://ftp.de.debian.org/debian/ testing main non-free contrib
2. start kmail from terminal
3. 

OBSERVED RESULT
KCrash: crashing ... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/bin pid = 8379
KCrash: Arguments: /usr/bin/kmail
KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0


EXPECTED RESULT


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version:  5.13.5
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

Happens after i updated debian today on my two separate computers. 
Maybe akonadi or QT problem?

on laptop:
QSocketNotifier: Invalid socket 9 and type 'Read', disabling ...
on 
QSocketNotifier: Invalid socket 11 and type 'Read', disabling ...

Thank you for any clue?

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

[korganizer] [Bug 391769] KOrganizer 5.9.0: Incident times of tasks are not updated when edited by keyboard only

2018-10-10 Thread Denis Kurz
https://bugs.kde.org/show_bug.cgi?id=391769

Denis Kurz  changed:

   What|Removed |Added

Version|5.9.0   |5.9.1
 Ever confirmed|0   |1
 CC||kde...@posteo.de
 Status|REPORTED|CONFIRMED

--- Comment #2 from Denis Kurz  ---
https://phabricator.kde.org/D16114

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

[knotes] [Bug 399551] Knotes Crash on start

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399551

--- Comment #2 from caputchinefrob...@yahoo.com.br ---
Probably a partial update on debian repo, because at this moment, there are no
further upgradable packages available.

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

[korganizer] [Bug 399622] New: Accepting invitations duplicates entries

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399622

Bug ID: 399622
   Summary: Accepting invitations duplicates entries
   Product: korganizer
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: groupware
  Assignee: kdepim-bugs@kde.org
  Reporter: johan.claudebreunin...@gmail.com
  Target Milestone: ---

SUMMARY

Accepting an invitation leads to the creation of a new entry with me as
Organizer. Leading to confusion in the team and to duplicate events in the
calendar.

STEPS TO REPRODUCE & OBSERVED RESULT
1. Accept an invitation from an Organizer
2. A window shows to select the calendar to save the invite into (the bug may
be here?)
3. Duplicate entry with you as organizer is sent to everybody invited to the
event.


EXPECTED RESULT
1. Accept an invitation from an organizer
2. The answer is sent to all the persons invited and store in the right event
and not duplicated


SOFTWARE VERSIONS

KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

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

[korganizer] [Bug 399622] Accepting invitations duplicates entries

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399622

johan.claudebreunin...@gmail.com changed:

   What|Removed |Added

 CC||johan.claudebreuninger@gmai
   ||l.com

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

[kmail2] [Bug 399614] HTML body is not displayed in message containing calendar invitation (.ics file)

2018-10-10 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=399614

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Laurent Montel  ---
5.7.3 is very old.
It works fine here.
Could you test with last version please.
Thanks

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

[kmail2] [Bug 399614] New: HTML body is not displayed in message containing calendar invitation (.ics file)

2018-10-10 Thread Yan
https://bugs.kde.org/show_bug.cgi?id=399614

Bug ID: 399614
   Summary: HTML body is not displayed in message containing
calendar invitation (.ics file)
   Product: kmail2
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: yanp.b...@gmail.com
  Target Milestone: ---

When I get a mail with calendar invitation inside (.ics file) I can't see
attached html body, only in the source code

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.44
Qt Version: 5.9.5

ADDITIONAL INFORMATION

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

[kmail2] [Bug 378011] KMail 5.4.3 Mailing list not resolved

2018-10-10 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=378011

--- Comment #27 from Axel Braun  ---
In between I believe its not the number of recipients - it's the name of the
group: If I rename test_group to testgroup, everything works

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

[korganizer] [Bug 399603] New: KDE applications (Kontacts, KOrganizer etc.) crash at start

2018-10-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399603

Bug ID: 399603
   Summary: KDE applications (Kontacts, KOrganizer etc.) crash at
start
   Product: korganizer
   Version: 5.7.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: tanacs...@gmail.com
  Target Milestone: ---

Application: korganizer (5.7.3)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.18.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed: Updated Debian from stable to
Testing. Since that these applications crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcc4366ea80 (LWP 4074))]

Thread 3 (Thread 0x7fcc416c7700 (LWP 4076)):
#0  0x7fcc50b74739 in __GI___poll (fds=0x7fcc34004db0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fcc4c3ebe46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcc4c3ebf6c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcc5109e24b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fcc5104b25b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fcc50e9a176 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fcc5082e545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fcc50ea3d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fcc4d6f2f2a in start_thread (arg=0x7fcc416c7700) at
pthread_create.c:463
#9  0x7fcc50b7eedf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fcc427f7700 (LWP 4075)):
#0  0x7fcc50b74739 in __GI___poll (fds=0x7fcc427f6a38, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fcc4c179cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fcc4c17b90a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fcc433786d9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fcc50ea3d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fcc4d6f2f2a in start_thread (arg=0x7fcc427f7700) at
pthread_create.c:463
#6  0x7fcc50b7eedf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fcc4366ea80 (LWP 4074)):
[KCrash Handler]
#6  0xfff0 in ?? ()
#7  0x7fcc52fecf9d in
KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5
#8  0x55c94fcd90f3 in main () at ./src/main.cpp:55
#9  0x7fcc50aa9b17 in __libc_start_main (main=0x55c94fcd8df0 ,
argc=1, argv=0x7ffe849fa288, init=, fini=,
rtld_fini=, stack_end=0x7ffe849fa278) at ../csu/libc-start.c:310
#10 0x55c94fcd92fa in _start () at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:125

The reporter indicates this bug may be a duplicate of or related to bug 389840.

Possible duplicates by query: bug 398557, bug 398152, bug 396724, bug 396700,
bug 389840.

Reported using DrKonqi

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

[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts

2018-10-10 Thread Jacopo Torrini
https://bugs.kde.org/show_bug.cgi?id=398847

Jacopo Torrini  changed:

   What|Removed |Added

 CC||jac...@gmail.com

--- Comment #3 from Jacopo Torrini  ---
I confirm this bug for me.

KAddressBook 5.9.1
KDE 5.14.0
KDE Frameworks 5.50.0
Qt 5.11.1

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

[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"

2018-10-10 Thread imraro
https://bugs.kde.org/show_bug.cgi?id=399245

imraro  changed:

   What|Removed |Added

 CC||imr...@gmail.com

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

[korganizer] [Bug 399597] New: Korganizer crashing when creating a todo

2018-10-10 Thread Thomas Citharel
https://bugs.kde.org/show_bug.cgi?id=399597

Bug ID: 399597
   Summary: Korganizer crashing when creating a todo
   Product: korganizer
   Version: 5.9.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: t...@tcit.fr
  Target Milestone: ---

Application: korganizer (5.9.1)

Qt Version: 5.11.1
Frameworks Version: 5.50.0
Operating System: Linux 4.15.0-36-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
Creating a todo task (just title). Tasks are synched over CalDAV.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fed4c7ac880 (LWP 19106))]

Thread 5 (Thread 0x7fed1700 (LWP 19111)):
#0  0x7fed47f920b4 in __GI___libc_read (fd=12, buf=0x7fed1fffeb10,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fed3dba8a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed3db63f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed3db643e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fed3db6454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fed48ae9a9b in QEventDispatcherGlib::processEvents
(this=0x7fed14000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed1fffed20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#7  0x7fed488b8b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#8  0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce06ec490) at
thread/qthread_unix.cpp:367
#9  0x7fed3fc386db in start_thread (arg=0x7fed1700) at
pthread_create.c:463
#10 0x7fed47fa388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fed2483e700 (LWP 19109)):
#0  0x7fed47f96bf9 in __GI___poll (fds=0x55dce11d07f0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fed3db64439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed3db6454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed48ae9a9b in QEventDispatcherGlib::processEvents
(this=0x7fed18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed2483dd20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7fed488b8b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce06c2f40) at
thread/qthread_unix.cpp:367
#7  0x7fed3fc386db in start_thread (arg=0x7fed2483e700) at
pthread_create.c:463
#8  0x7fed47fa388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fed25a4f700 (LWP 19108)):
#0  0x7fed3db6393d in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fed3db6436b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed3db6454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed48ae9a9b in QEventDispatcherGlib::processEvents
(this=0x7fed2b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed25a4ecf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7fed488b8b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7fed47440e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fed488c3aab in QThreadPrivate::start (arg=0x7fed476b8d60) at
thread/qthread_unix.cpp:367
#8  0x7fed3fc386db in start_thread (arg=0x7fed25a4f700) at
pthread_create.c:463
#9  0x7fed47fa388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fed2c8bf700 (LWP 19107)):
#0  0x7fed47f96bf9 in __GI___poll (fds=0x7fed2c8bec28, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fed3d6f6747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fed3d6f836a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fed2f679129 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce05d8350) at
thread/qthread_unix.cpp:367
#5  0x7fed3fc386db in start_thread (arg=0x7fed2c8bf700) at
pthread_create.c:463
#6  0x7fed47fa388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fed4c7ac880 (LWP 19106)):
[KCrash Handler]
#6  0x7fed48a6118c in QSortFilterProxyModel::parent (this=0x55dce096af90,
child=...) at itemmodels/qsortfilterproxymodel.cpp:2002

[knotes] [Bug 399551] Knotes Crash on start

2018-10-10 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=399551

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Could you make sure all your packages are up-to-date? Looks like you may have
an issue with mixed versions of libraries.

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