Bug 413518

Can you post your kwinrc file?

Thanks for your investigation. Here is my kwinrc file content:

[$Version]
update_info=kwin.upd:replace-scalein-with-scale,kwin.upd:port-minimizeanimation-effect-to-js,kwin.upd:port-scale-effect-to-js,kwin.upd:port-dimscreen-effect-to-js,kwin.upd:auto-bordersize

[Compositing]
OpenGLIsUnsafe=false

[Desktops]
Id_1=66c07a90-597f-46ca-98e3-f7f6a9433803
Id_2=87b53c0d-295e-411a-8e1b-c3312b4acdc3
Number=2
Rows=1

[Effect-Blur]
BlurStrength=1
NoiseStrength=0

[Effect-CoverSwitch]
TabBox=false
TabBoxAlternative=false
zPosition=653

[Effect-Cube]
BorderActivate=9
BorderActivateCylinder=9
BorderActivateSphere=9
TouchBorderActivate=9
TouchBorderActivateCylinder=9
TouchBorderActivateSphere=9

[Effect-CubeSlide]
RotationDuration=190

[Effect-DesktopGrid]
BorderActivate=9
TouchBorderActivate=9

[Effect-DimInactive]
DimByGroup=false
DimFullScreen=false
DimKeepAbove=true

[Effect-FlipSwitch]
TabBox=true
TabBoxAlternative=false

[Effect-PresentWindows]
BorderActivate=9
BorderActivateAll=9
BorderActivateClass=9
TouchBorderActivate=7
TouchBorderActivateAll=9
TouchBorderActivateClass=9

[Effect-Slide]
SlideDocks=true

[Effect-ThumbnailAside]
Opacity=100

[Effect-Wobbly]
AdvancedMode=true
Drag=90
Stiffness=6
WobblynessLevel=2

[Effect-kwin4_effect_login]
FadeToBlack=true

[Effect-kwin4_effect_translucency]
MoveResize=100

[ElectricBorders]
Bottom=None
BottomLeft=None
BottomRight=None
Left=None
Right=None
Top=None
TopLeft=None
TopRight=None

[ModifierOnlyShortcuts]
Meta=

[Plugins]
blurEnabled=true
contrastEnabled=true
coverswitchEnabled=true
desktopchangeosdEnabled=false
enforcedecoEnabled=true
fallapartEnabled=true
flipswitchEnabled=true
glideEnabled=true
highlightwindowEnabled=true
kwin-script-tilingEnabled=false
kwin4_effect_dimscreenEnabled=true
kwin4_effect_fadeEnabled=false
kwin4_effect_squashEnabled=false
magiclampEnabled=true
minimizeallEnabled=false
sheetEnabled=true
slideEnabled=false
synchronizeskipswitcherEnabled=false
thumbnailasideEnabled=true
videowallEnabled=false
wobblywindowsEnabled=true

[Script-desktopchangeosd]
PopupHideDelay=1000
TextOnly=false

[TabBox]
ActivitiesMode=1
ApplicationsMode=0
BorderActivate=9
BorderAlternativeActivate=9
DesktopLayout=org.kde.breeze.desktop
DesktopListLayout=org.kde.breeze.desktop
DesktopMode=1
HighlightWindows=true
LayoutName=text
MinimizedMode=0
MultiScreenMode=0
ShowDesktopMode=0
ShowTabBox=true
SwitchingMode=0
TouchBorderActivate=9
TouchBorderAlternativeActivate=9

[TabBoxAlternative]
ActivitiesMode=1
ApplicationsMode=0
DesktopMode=1
HighlightWindows=true
LayoutName=org.kde.breeze.desktop
MinimizedMode=0
MultiScreenMode=0
ShowDesktopMode=0
ShowTabBox=true
SwitchingMode=0

[TouchEdges]
Bottom=None
Left=None
Right=None
Top=None

[Windows]
ElectricBorderCooldown=350
ElectricBorderCornerRatio=0.25
ElectricBorderDelay=150
ElectricBorderMaximize=false
ElectricBorderTiling=false
ElectricBorders=0
RollOverDesktops=true

[org.kde.kdecoration2]
BorderSize=None
BorderSizeAuto=false
ButtonsOnLeft=
ButtonsOnRight=IAX
CloseOnDoubleClickOnMenu=false
ShowToolTips=true
library=org.kde.kwin.aurorae
theme=__aurorae__svg__Sweet-Dark

The crash itself is somewhat irrelevant, what's key is we have:

#14 0x00007f9e6fc146a7 in __run_exit_handlers () at /usr/lib/libc.so.6

lower in the stack. 

So we're already quitting due to something triggered from the Qt XCB QPA.

Thong, could you get debug symbols for QtXCB and reproduce?

(In reply to David Edmundson from comment #3)
> So we're already quitting due to something triggered from the Qt XCB QPA.
> 
> Thong, could you get debug symbols for QtXCB and reproduce?
As far as I know, there's only one place where QtXCB may call exit() and it is here https://code.woboq.org/qt5/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp.html#1013

Can you post kwin's logs? You can retrieve kwin's logs on arch linux by running the following command from terminal

    journalctl /usr/bin/kwin_x11

Created attachment 124028 [details]
attachment-13894-0.html

Hi Vlad,

sorry for delay because I dont have many time to  use that pc, I will try to take required log to you ASAP (if I have chance).
Tks for your kind and sorry for my inconvenient

ThongT
________________________________
From: Vlad Zahorodnii <bugzilla_noreply@kde.org>
Sent: Wednesday, November 20, 2019 10:22:48 PM
To: thong01687300206@gmail.com <thong01687300206@gmail.com>
Subject: [kwin] [Bug 413518] Kwin crash when access phone from KDE connect

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

--- Comment #5 from Vlad Zahorodnii <vladzzag@gmail.com> ---
Can you post kwin's logs? You can retrieve kwin's logs on arch linux by running
the following command from terminal

    journalctl /usr/bin/kwin_x11

--
You are receiving this mail because:
You reported the bug.

Created attachment 124097 [details]
kwin_log

Hi Vlad and David,

I see the kwin log may have been rotated, because I no longer see the log
at the error timestamp, I don't know if this is still useful. I also attach
the Xorg log for more information.
I tried to reproduce but now there is a another issue that I cannot connect
(kde connect) my phone to my computer :| and display error "

The file or folder /run/user/1000/bd31ade8c644d656/8698-7CDA does not
exist." in dolphin, so I will try in another time to get log again.


Thanks

Created attachment 124098 [details]
Xorg.0.log

Created attachment 124099 [details]
Xorg.0.log.old

This bug report is quite old. Does the crash still occur with KDE 5.23? If so, then please install debugging packages for QtXCB following the instructions given here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
reproduce the bug and submit a new backtrace.

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!

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!