Bug 347005 - Crash on application startup
Summary: Crash on application startup
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kwindowsystem
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks: kdepim-15.08
  Show dependency treegraph
 
Reported: 2015-05-01 12:14 UTC by Andreas Cord-Landwehr
Modified: 2018-11-30 04:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Cord-Landwehr 2015-05-01 12:14:34 UTC
When starting KMail from the frameworks branch, using Qt 5.4.2 (self-build, updated from Git last night) and KWindowSystem (git hash 9bb99d6c06e014c7fd202597aef90afa2eaa0d38), the application segfaults with the following backtrace:

    Program received signal SIGSEGV, Segmentation fault.
    0x00007fffe2acc05c in QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
    135             return d;
    (gdb) bt
    #0  0x00007fffe2acc05c in QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
    #1  0x00007fffe2db7d89 in qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:962
    #2  0x00007fffe2db7f48 in QObject::d_func (this=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:110
    #3  0x00007fffe2daea94 in QObject::thread (this=0x0) at kernel/qobject.cpp:1412
    #4  0x00007fffe5ab3a7c in KWindowSystemStaticContainer::KWindowSystemStaticContainer (this=0x7fffe5cfc390 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>)
        at /opt/kde/src/frameworks/kwindowsystem/src/kwindowsystem.cpp:52
    #5  0x00007fffe5ab24d6 in (anonymous namespace)::Q_QGS_g_kwmInstanceContainer::Holder::Holder (this=0x7fffe5cfc390 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>)
        at /opt/kde/src/frameworks/kwindowsystem/src/kwindowsystem.cpp:58
    #6  0x00007fffe5ab2543 in (anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction () at /opt/kde/src/frameworks/kwindowsystem/src/kwindowsystem.cpp:58
    #7  0x00007fffe5ab3684 in QGlobalStatic<KWindowSystemStaticContainer, (* (anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction), (* & (anonymous namespace)::Q_QGS_g_kwmInstanceContainer::guard)>::operator()(void) (this=0x7fffe5cfc380 <g_kwmInstanceContainer>) at /opt/qt5/qtbase/src/corelib/global/qglobalstatic.h:129
    #8  0x00007fffe5ab29ba in KWindowSystem::d_func () at /opt/kde/src/frameworks/kwindowsystem/src/kwindowsystem.cpp:343
    #9  0x00007fffe5ab34ea in KWindowSystem::allowExternalProcessWindowActivation (pid=-1) at /opt/kde/src/frameworks/kwindowsystem/src/kwindowsystem.cpp:639
    #10 0x00007ffff7bd22f2 in KontactInterface::PimUniqueApplication::start (flags=...) at /opt/kde/src/kde/pim/kontactinterface/src/pimuniqueapplication.cpp:105
    #11 0x00007ffff7bd20b7 in KontactInterface::PimUniqueApplication::start () at /opt/kde/src/kde/pim/kontactinterface/src/pimuniqueapplication.cpp:76
    #12 0x00000000004038f7 in main (argc=<optimized out>, argv=<optimized out>) at /opt/kde/src/kdepim-unsplit/kmail/main.cpp:119
    (gdb)


Reproducible: Always
Comment 1 Andreas Cord-Landwehr 2015-05-01 12:41:06 UTC
The interesting information from the PIM source is probably that /opt/kde/src/kde/pim/kontactinterface/src/pimuniqueapplication.cpp:105 is:

KWindowSystem::allowExternalProcessWindowActivation();

Commenting this line out seems to be a workaround.
Comment 2 Martin Flöser 2015-05-04 06:16:00 UTC
The call is probably unrelated, it's just the first call into KWindowSystem causing the crash.
Comment 3 Martin Flöser 2015-05-04 06:17:48 UTC
oh and it's an awesome call:

void KWindowSystemPrivateX11::allowExternalProcessWindowActivation(int pid)
{
    // Normally supported by X11, but may depend on some window managers ?
    Q_UNUSED(pid)
}

as all other platforms currently don't have an implementation...
Comment 4 Andrew Crouthamel 2018-10-31 03:54:55 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-15 10:53:11 UTC
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!
Comment 6 Bug Janitor Service 2018-11-30 04:05:31 UTC
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!