[kmail2] [Bug 387025] KMail crashes when launched

2021-01-15 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=387025

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2020-12-31 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2020-12-16 Thread Justin Zobel 
https://bugs.kde.org/show_bug.cgi?id=387025

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #6 from Justin Zobel  ---
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm
if this issue is still occurring or if this bug report can be marked as
resolved.

I have set the bug status to "needsinfo" pending your response, please change
back to "reported" or "resolved/worksforme" when you respond, thank you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-12-23 Thread Allan Sandfeld 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #5 from Allan Sandfeld  ---
I downgraded to neon user instead of dev stable, so I don't know if it still
happens there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-12-23 Thread David Faure 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #4 from David Faure  ---
To remove drkonqi from the equation, simply export KDE_DEBUG=1.

Either this is a miscompilation... or I did something wrong in terms of
KConfigGroup lifetime in https://phabricator.kde.org/D8783 ... but the calling
code is simply
KConfigGroup grp(KernelIf->config(), "CollectionTreeOrder");
d->entityOrderProxy->setOrderConfig(grp);
which should be fine...

Does this still happen?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-11-18 Thread Allan Sandfeld 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #3 from Allan Sandfeld  ---
On closer inspection this line:
#10 0x7f162fdc19ee in KMMainWidget::createWidgets
(this=this@entry=0x2659970) at /workspace/build/src/kmmainwidget.cpp:996

Corresponds with the sources in the 17.12 branch of kmail, not with 17.08
branch. Is this just neon mispackaging kdepim again?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-11-18 Thread Allan Sandfeld 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #2 from Allan Sandfeld  ---
The only recent related commit I could found was
40252aae3c793c7c4df42d90073911c73cebd7f1 but that should be 7.12, and my
packages claim to be 7.08

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-11-18 Thread Allan Sandfeld 
https://bugs.kde.org/show_bug.cgi?id=387025

Allan Sandfeld  changed:

   What|Removed |Added

 CC||fa...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387025] KMail crashes when launched

2017-11-17 Thread Allan Sandfeld 
https://bugs.kde.org/show_bug.cgi?id=387025

--- Comment #1 from Allan Sandfeld  ---
Valgrind seems to be blocked by drkonqi from seeing the details of the crash,
there are few errors before though, but they look unrelated:

==21778== Thread 6 QThread:
==21778== Invalid read of size 2
==21778==at 0x6D197F9: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x12A35DC0: g_main_context_check (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3632F: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3649B: g_main_context_iteration (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x6D1992E:
QEventDispatcherGlib::processEvents(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6CC27C9:
QEventLoop::exec(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AEBCD3: QThread::exec() (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AF0988: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333)
==21778==by 0x740C3DC: clone (clone.S:109)
==21778==  Address 0x2d94b3f6 is 6 bytes inside a block of size 16 free'd
==21778==at 0x4C2F24B: operator delete(void*) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21778==by 0x6CFD105: QSocketNotifier::setEnabled(bool) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6D197F8: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x12A35DC0: g_main_context_check (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3632F: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3649B: g_main_context_iteration (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x6D1992E:
QEventDispatcherGlib::processEvents(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6CC27C9:
QEventLoop::exec(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AEBCD3: QThread::exec() (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AF0988: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333)
==21778==by 0x740C3DC: clone (clone.S:109)
==21778==  Block was alloc'd at
==21778==at 0x4C2E0EF: operator new(unsigned long) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21778==by 0x6D1A471:
QEventDispatcherGlib::registerSocketNotifier(QSocketNotifier*) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6CFCF87: QSocketNotifier::QSocketNotifier(long long,
QSocketNotifier::Type, QObject*) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x10074878: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1)
==21778==by 0x10061E44: QAbstractSocket::setSocketDescriptor(long long,
QAbstractSocket::SocketState, QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1)
==21778==by 0x100781DE: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1)
==21778==by 0x10078639:
QLocalSocket::connectToServer(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1)
==21778==by 0xCE847E9: Akonadi::Connection::doReconnect() (in
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5.6.80)
==21778==by 0xCFAF1A4: Akonadi::Connection::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (in
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5.6.80)
==21778==by 0x6CF1C58: QObject::event(QEvent*) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x5FF03FB: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1)
==21778==by 0x5FF7E06: QApplication::notify(QObject*, QEvent*) (in
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1)
==21778== 
==21778== Invalid read of size 2
==21778==at 0x6D19784: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x12A35DC0: g_main_context_check (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3632F: ??? (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x12A3649B: g_main_context_iteration (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==21778==by 0x6D1992E:
QEventDispatcherGlib::processEvents(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6CC27C9:
QEventLoop::exec(QFlags) (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AEBCD3: QThread::exec() (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x6AF0988: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1)
==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333)
==21778==by 0x740C3DC: clone (clone.S:109)
==21778==  Address 0x2d94b3f4 is 4 bytes inside a block of size 16 free'd
==21778==at 0x4C2F24B: operator delete(void*) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==217