When I attempt to log back in after hibernation, sometimes I need to attempt the login screen two times.
The first time I get the usual lock screen wallpaper and I press enter (to get into login mode) and then I type in my password. After that the screen freezes for sometime and then shows me my desktop but I can’t interact with it, then soon (like under 5 seconds) I get a lock screen second time.
This time however I don’t get to see my lock screen wallpaper, its just a black screen, I press enter, type in my password and the desktop is shown again, this time everything seems to be working.
I have recently switched from NVIDIA performance mode to Intel power saving. I am not sure but maybe after that this problem has started. I have 10GB swap-area for my 8GB RAM.
Thanks @carmar for your response. You are right. It was not a driver issue. I checked the Logs app and found this error message appearing every time I logged in:
“failed to set mode blocked through rfkill (0x12)”.
I didn’t research how the problem was generated. but I followed this and was able to resolve the issue. Bluetooth-blocked-through-rfkill.
The problem is not gone. Now that I have experimented with it a little bit, I have got some patterns and more details.
Login Glitch : I need to unlock the lock screen multiple times after I either lock the screen, or hibernate the system. This doesn’t happen on the first login after a fresh reboot. This doesn’t happen always,maybe like 1/3 times.
Mega Glitch : Sometimes on an ongoing Login Glitch it even clears all apps open in the session. This part sometimes is really annoying.
So in my previous reply I think it was a mere coincidence that the glitch didn’t happen when I ran the command in the stackoverflow link.
These are my journalctl logs with priority levels between 0…3 of a Mega Glitch happening while an ongoing Login Glitch
`
[ 1 ] Jan 30 11:00:40 acer gnome-shell[9647]: Creating pipes for GWakeup: Too many open files
[ 2 ] Jan 30 11:00:40 acer gnome-session-binary[7036]: Unrecoverable failure in required component org.gnome.Shell.desktop
[ 3 ] Jan 30 11:00:40 acer gnome-session-binary[7036]: CRITICAL: We failed, but the fail whale is dead. Sorry....
[ 4 ] Jan 30 11:00:53 acer pulseaudio[10758]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
[ 5 ] Jan 30 11:00:54 acer spice-vdagent[10876]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0`
Of the above errors, error type [ 1 ] happens every time Login Glitch occurs.
Error type [ 2 ] & [ 3 ] happens everytime Mega Glitch occurs.
Error type [ 4 ] & [ 5 ] I think so aren’t important cause they happen even when session starts properly.
I even looked at syslog and found that error type [ 1 ] is some JS related problem. I would send those logs too if required.
Out of curiosity - what happens when you close all your applications (or at least the larger resource users) and hibernate? I assume this is hibernate and not suspend.
This is a short snippet from /var/log/syslog from a Login Glitch.
Jan 30 13:20:26 acer gnome-shell[1435]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
Jan 30 13:20:26 acer gnome-shell[1435]: JS ERROR: GLib.Error g-unix-error-quark: Too many open files
Jan 30 13:20:26 acer gnome-shell[1435]: Object St.BoxLayout (0x562060b1c660), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: == Stack trace for context 0x56205ba1b290 ==
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #0 7ffe91e87020 b resource:///org/gnome/shell/ui/popupMenu.js:727 (7ff844527c10 @ 22)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #1 7ffe91e870e0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #2 7ffe91e87190 b resource:///org/gnome/shell/ui/popupMenu.js:745 (7ff844527ee0 @ 23)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #3 7ffe91e87250 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #4 7ffe91e872f0 b /usr/share/gnome-shell/extensions/zorin-printers@zorinos.com/extension.js:106 (7ff8040b4280 @ 232)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #5 7ffe91e873b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #6 7ffe91e87450 b /usr/share/gnome-shell/extensions/zorin-printers@zorinos.com/extension.js:203 (7ff8040b4670 @ 28)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #7 7ffe91e87510 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #8 7ffe91e87550 I self-hosted:975 (7ff8447f0280 @ 392)
Jan 30 13:20:26 acer gnome-shell[1435]: clutter_container_get_children: assertion 'CLUTTER_IS_CONTAINER (container)' failed
Jan 30 13:20:26 acer gnome-shell[1435]: Object St.BoxLayout (0x562060b1c660), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: == Stack trace for context 0x56205ba1b290 ==
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #0 7ffe91e87040 I resource:///org/gnome/shell/ui/environment.js:41 (7ff844785430 @ 20)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #1 7ffe91e87130 b resource:///org/gnome/shell/ui/popupMenu.js:652 (7ff844527700 @ 61)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #2 7ffe91e87240 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #3 7ffe91e872f0 b /usr/share/gnome-shell/extensions/zorin-printers@zorinos.com/extension.js:109 (7ff8040b4280 @ 345)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #4 7ffe91e873b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #5 7ffe91e87450 b /usr/share/gnome-shell/extensions/zorin-printers@zorinos.com/extension.js:203 (7ff8040b4670 @ 28)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #6 7ffe91e87510 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff8447b0b80 @ 71)
Jan 30 13:20:26 acer org.gnome.Shell.desktop[1435]: #7 7ffe91e87550 I self-hosted:975 (7ff8447f0280 @ 392)
the above section is just repeated many times
and then finally at the end our type [ 1 ] error
Jan 30 13:20:26 acer gnome-shell[1435]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
Jan 30 13:20:26 acer gnome-shell[1435]: JS ERROR: GLib.Error g-unix-error-quark: Too many open files
Jan 30 13:20:26 acer dbus-daemon[707]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Jan 30 13:20:26 acer systemd[1]: Started Location Lookup Service.
Jan 30 13:20:26 acer gnome-software[2111]: no app for changed alternate-tab@gnome-shell-extensions.gcampax.github.com
Jan 30 13:20:26 acer gnome-software[2111]: no app for changed apps-menu@gnome-shell-extensions.gcampax.github.com
Jan 30 13:20:26 acer gnome-software[2111]: no app for changed auto-move-windows@gnome-shell-extensions.gcampax.github.com
Jan 30 13:20:26 acer gnome-shell[1435]: Creating pipes for GWakeup: Too many open files
Hope this helps in diagnosing my system problem. Thanks for your patience.
I tried to install a previous gdm3 version but I get this error message
The following packages have unmet dependencies:
> gdm3 : Depends: libgdm1 (= 3.28.0-0ubuntu1) but 3.28.3-0ubuntu18.04.6+zorin1 is to be installed
> Depends: gir1.2-gdm-1.0 (= 3.28.0-0ubuntu1) but 3.28.3-0ubuntu18.04.6+zorin1 is to be installed
It's that time of morning- I have to drive to the airport- back in about an hour or so.
In the link I posted above, please scroll down far enough to see
"Steps to find memory leak"
It has detailed step by step walkthrough that may help.
Once you go through the steps you can post the memory dump here in this thread.
Downgrading gdm3 didn’t help. The problem still exists.
I tried to follow the memory dump step by step but on running strings command on my memory.dump file didn’t gave anything as output. Besides I think I didn’t much understood diff command step and what do actually I have to look for in the difference.
I ran all this on a process call gdm with command /usr/bin/gnome-shell , I am not sure even if I did that correctly.
Do the output from syslog that I gave really not help in identifying the problem ?
Well, it was worth a shot to roll back GDM3. You can roll it back forward, if you like.
sudo apt full-upgrade
The only output I see in the logs above that I think relate is the one I quoted that made me immediately think that too many file descriptors are open. You also mentioned
JS ERROR: GLib.Error g-unix-error-quark: Too many open files
Normally, cleaning out some space can resolve the issue. In your case, though, it is affecting Login and On Wake. Which means cache and such should have cleared on logout.
On the steps in the link- It may be outdated.
Can you run in terminal:
gnome-shell --version
and post the output here.
Same with:
cat /proc/meminfo
You might consider using htop to display memory usage, then run htop in terminal and let it run while you work on other tasks and go about your normal computering business- IF you notice a slow down or performance drop, look at the terminal window running htop for a large wad of memory being gobbled up.
sudo apt install htop
htop
and you can relay that output here.
Here is an example of htop running on my machine:
Almost 14 gigs in your commit limit. You are not even using any swap space currently.
Are you working with heavy resource or graphics intensive projects during the times when you have the login issue and errors? Can you recall any software you were consistently using each time (Not including Gnome-shell :P)
Ok. I was hoping that you might say it was GImp or some non-integrated software that we could narrow doing a possible memory leak to.
what does (terminal) this yield: