-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shell Hangs #549
Comments
Hi, can you please try to generate a support log as described here? This sounds like a bug which occurred in the version of GSConnect shipped in Ubuntu's APT repository. Can you confirm this is not installed? |
Closing due to lack of activity and information. Feel free to re-open if the issue persists and you can upload a log. |
I'm not sure if it's the same issue as @Afsalmc, but sometimes when I receive a notification gnome-shell becomes unresponsive, the default ubuntu 18.04 dash to dock extension disappears for an instant and then everything returns to normal. I have found a quite reliable method (works if you do it 2-3 times) to reproduce the issue:
|
@Zap123 's logs start here:
A quick troll 'round the interwebs makes me think those logs (ignoring the unrelated sysstat cron job that pokes up right at the start) are likely just the normal aftermath of Gnome Shell segfaulting, with the actual crash happening prior to the start of the logs. @Zap123 , any chance you could look at There's probably a point shortly before those tracebacks start getting logged, where This sounds similar enough that I'm going to reopen this report, on the assumption it's probably the same issue. |
Unfortunately, so far most of what I've found (in terms of related logs/reports) are issues filed with other shell extensions by Ubuntu users experiencing similar issues, but the extension developers never really making much progress in figuring out how (or even IF) they're actually causing them. So, this may be GSConnect's induction into a really lame club. But, hey — there's company. 👍 |
Hi @ferdnyc, thanks for your prompt response! I have tested a few things to see if something would change but it didn't:
I had already rebooted therefore I reproduced the issue from a fresh session and using journalctl I have saved the log that you can find attached. This is the error that happens exactly before the crash:
I have found an upstream bug report that has been fixed 4 months ago, It's probably not in Ubuntu yet but it seems the same problem. Anyway it seems that this bug affect gsconnect but it's not only a problem contingent on this extension (even though in my case it happens only with gsconnect). https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 I think you can close this issue again, but thanks for your assistance. |
There's a quote you always want to find while reading through a bug report:
Thanks for the update, @Zap123. I agree it sounds more and more like this isn't really a GSConnect issue, just an issue GSConnect happens to be triggering. Re-closing like one of those sandwich baggies with the plastic zipper. |
Describe the bug
Gnome Shell 3.28 Hangs for approx 20 sec while receiving first notification from connected device after boot . Issue is noted in Ubuntu 18.04.2 .
Steps To Reproduce:
Expected behavior
First notification from Paired mobile device is displayed immediately without shell Hanging after Booting up the Computer .
System Details (please complete the following information):
GSConnect environment (if applicable):
Additional Notes:
Using Linuxium spin of Ubuntu 18.04.2 for Baytrail Devices
The text was updated successfully, but these errors were encountered: