Bug 422491

Summary: Plasmashell hangs on request to other servers (google calendar, dropbox, ...)
Product: [Plasma] plasmashell Reporter: Iuri Spinassi <iurispin>
Component: generic-performanceAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate, noahadvs, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.18.5   
Target Milestone: 1.0   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Exemple of a event on dolphin that hangs plasmashell

Description Iuri Spinassi 2020-06-05 15:57:58 UTC
Created attachment 129078 [details]
Exemple of a event on dolphin that hangs plasmashell

SUMMARY
Hi, everyone!

Every time I make a request for other services (dropbox, google calendar, ...), the interface hangs until the operation is done.

This problem gets worse after adding the plasma activities.

It's not the whole system that hangs, just the plasmashell.

STEPS TO REPRODUCE
1. Use dropbox integration with dolphin OR Google Calendar integration on Event Calendar widget.
2. Get a dropbox file link OR refresh the calendar events 

OBSERVED RESULT
Plasmashell hangs

EXPECTED RESULT
Do not hang.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 4.19.122-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15,4 GiB

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2020-06-05 16:45:37 UTC
that's very unusual.

I would need to see a backtrace of plasmashell to see what's going on

Can you run
sudo gdb --pid `pidof plasmashell` when you're in the frozen state

then when it connects type "bt" and paste the result
Comment 2 Iuri Spinassi 2020-06-05 17:01:59 UTC
The plasmashell is frozen right now.


Thread 1 "plasmashell" received signal SIGINT, Interrupt.
0x00007fef7378c71d in syscall () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007fef7378c71d in syscall () at /usr/lib/libc.so.6
#1  0x00007fef73b01126 in QBasicMutex::lockInternal() () at 
/usr/lib/libQt5Core.so.5
#2  0x00007fef73d0e811 in  () at /usr/lib/libQt5Core.so.5
#3  0x00007fef73d0edd9 in QObject::disconnect(QObject const*, char 
const*, QObject const*, char const*) () at /usr/lib/libQt5Core.so.5
#4  0x00007fef75973d09 in  () at /usr/lib/libQt5Quick.so.5
#5  0x00007fef75974c02 in  () at /usr/lib/libQt5Quick.so.5
#6  0x00007fef75974db2 in  () at /usr/lib/libQt5Quick.so.5
#7  0x00007fef7589a01e in QQuickItemPrivate::derefWindow() () at 
/usr/lib/libQt5Quick.so.5
#8  0x00007fef75899fe1 in QQuickItemPrivate::derefWindow() () at 
/usr/lib/libQt5Quick.so.5
#9  0x00007fef75899fe1 in QQuickItemPrivate::derefWindow() () at 
/usr/lib/libQt5Quick.so.5
#10 0x00007fef75899fe1 in QQuickItemPrivate::derefWindow() () at 
/usr/lib/libQt5Quick.so.5
#11 0x00007fef7589a70d in QQuickItem::setParentItem(QQuickItem*) ()
     at /usr/lib/libQt5Quick.so.5
#12 0x00007fef759dafc0 in  () at /usr/lib/libQt5Quick.so.5
#13 0x00007fef759db3e9 in  () at /usr/lib/libQt5Quick.so.5
#14 0x00007fef759dd285 in  () at /usr/lib/libQt5Quick.so.5
#15 0x00007fef7543a5a9 in QQmlPropertyPrivate::write(QObject*, 
QQmlPropertyData const&, QVariant const&, QQmlContextData*, 
QFlags<QQmlPropertyData::WriteFlag>) ()
     at /usr/lib/libQt5Qml.so.5
#16 0x00007fef7543e7ad in 
QQmlPropertyPrivate::writeValueProperty(QObject*, QQmlPropertyData 
const&, QQmlPropertyData const&, QVariant const&, QQmlContextData*, 
QFlags<QQmlPropertyData::WriteFlag>) () at /usr/lib/libQt5Qml.so.5
--Type <RET> for more, q to quit, c to continue without paging--

Em 05/06/2020 13:45, David Edmundson escreveu:
> https://bugs.kde.org/show_bug.cgi?id=422491
>
> David Edmundson <kde@davidedmundson.co.uk> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from David Edmundson <kde@davidedmundson.co.uk> ---
> that's very unusual.
>
> I would need to see a backtrace of plasmashell to see what's going on
>
> Can you run
> sudo gdb --pid `pidof plasmashell` when you're in the frozen state
>
> then when it connects type "bt" and paste the result
>
Comment 3 Bug Janitor Service 2020-06-20 04:33:08 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 4 Iuri Spinassi 2020-06-20 18:25:23 UTC
I provide the requested backtrace.
Comment 5 Noah Davis 2023-08-09 16:27:14 UTC
Unfortunately, it seems that your backtrace is incomplete:

> --Type <RET> for more, q to quit, c to continue without paging--

In order to see the whole backtrace, you needed to press Return/Enter to see the next page or enter "c" to continue without going page-by-page.

In addition, it seems that you did not have debug symbols installed. If this crash is reproducible, could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 6 Bug Janitor Service 2023-08-24 03:45:27 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 7 Bug Janitor Service 2023-09-08 03:45:23 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!