Session mouse over crash (libsession.so)
kepicorp opened this issue · comments
Prerequisites
- [ X] I have searched open and closed issues for duplicates.
Describe the bug
If I mouse over the session related button on the wing panel (all the way to the right) it freeze and eventually crash
To Reproduce
Mouse over the session button, wingpanel freeze until restart
Logs
syslog
Feb 5 10:21:13 FusionCore nm-applet[1751]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Feb 5 10:21:13 FusionCore nm-applet[1751]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Feb 5 10:21:13 FusionCore nm-applet[1751]: Can't set a parent on widget which has a parent
Feb 5 10:21:40 FusionCore zenity[5382]: GtkDialog mapped without a transient parent. This is discouraged.
Feb 5 10:21:43 FusionCore io.elementary.c[5237]: ProcessWrapper.vala:99: Process 'wingpanel' watch exit
Feb 5 10:21:43 FusionCore io.elementary.c[5237]: ProcessWrapper.vala:111: Process wingpanel is being terminated
Feb 5 10:21:43 FusionCore io.elementary.c[5237]: ProcessWrapper.vala:123: ET = 32.324749 secs#011Min allowed time = 3.500000
Feb 5 10:21:43 FusionCore io.elementary.c[5237]: ProcessWrapper.vala:46: Crash count of 'wingpanel' has been reset
Feb 5 10:21:43 FusionCore gala[1694]: invalid cast from 'CoglTexture2D' to '(null)'
kern.log
Feb 5 10:15:15 FusionCore kernel: [ 396.291371] wingpanel[4811]: segfault at 48 ip 0000563c531a5608 sp 00007ffc387a6e60 error 4 in wingpanel[563c5319a000+13000]
Feb 5 10:15:15 FusionCore kernel: [ 396.291379] Code: ba ff ff 0f 1f 80 00 00 00 00 48 8d 15 32 3e 00 00 48 8d 35 aa 40 00 00 48 8d 3d b9 2f 00 00 e9 ee ad ff ff 66 0f 1f 44 00 00 <48> 8b 78 48 e8 6f b3 ff ff 48 8b 7b 48 49 89 c4 e8 63 b3 ff ff 4c
Current workaround
I removed the button from wingpanel
cd /usr/lib/x86_64-linux-gnu/wingpanel
sudo mv libsession.so libsession.backup
pkill wingpanelPlatform Information
OS: elementary OS 5.1 Hera
Linux 5.3.0-28-generic
GTK 3.22.30
HW:
Dual-Core Intel® Core™ m7-6Y75 CPU @ 1.20GHz
Intel Corporation HD Graphics 515 (rev 07)
8GB Ram
256 SSD
ACK
Thanks a lot for the great work on elementary definitely my favorite distro <3
Adding log of wingpanel when not restarted by Cerbere
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.194: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.194: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.194: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.195: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.195: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.195: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.197: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.197: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7145): Gtk-CRITICAL **: 09:43:57.197: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
With debug
(wingpanel:7272): Gtk-DEBUG: 09:46:58.119: Connecting to session manager
** (wingpanel:7272): DEBUG: 09:46:58.126: Indicator.vala:237: Activating Sample Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.126: IndicatorManager.vala:319: session registered
** (wingpanel:7272): DEBUG: 09:46:58.155: Indicator.vala:230: Activating DateTime Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.155: IndicatorManager.vala:319: datetime registered
** (wingpanel:7272): DEBUG: 09:46:58.171: Indicator.vala:132: Activating Power Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.171: IndicatorManager.vala:319: power registered
** (wingpanel:7272): DEBUG: 09:46:58.172: Backlight.vala:28: backlight present: true
** (wingpanel:7272): DEBUG: 09:46:58.175: DeviceManager.vala:67: Connection to UPower bus established
** (wingpanel:7272): DEBUG: 09:46:58.177: Device.vala:165: Connection to UPower device established
** (wingpanel:7272): DEBUG: 09:46:58.179: Device.vala:165: Connection to UPower device established
** (wingpanel:7272): DEBUG: 09:46:58.238: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/line_power_AC" registered
** (wingpanel:7272): DEBUG: 09:46:58.240: Device.vala:165: Connection to UPower device established
** (wingpanel:7272): DEBUG: 09:46:58.242: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/battery_BAT0" registered
** (wingpanel:7272): DEBUG: 09:46:58.242: Indicator.vala:117: Icon changed to "battery-low-charging-symbolic"
** (wingpanel:7272): DEBUG: 09:46:58.242: Indicator.vala:97: Activating Monitor Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.245: IndicatorManager.vala:319: monitor registered
** (wingpanel:7272): DEBUG: 09:46:58.245: Indicator.vala:74: Activating Bluetooth Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.246: IndicatorManager.vala:319: bluetooth registered
** (wingpanel:7272): DEBUG: 09:46:58.246: Indicator.vala:111: Activating Keyboard Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.247: IndicatorManager.vala:319: keyboard registered
** (wingpanel:7272): DEBUG: 09:46:58.248: LayoutsManager.vala:99: get_name_for_xkb_layout (us, (null))
** (wingpanel:7272): DEBUG: 09:46:58.256: Indicator.vala:94: Activating Network Indicator
e** (wingpanel:7272): DEBUG: 09:46:58.304: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_WEAK
** (wingpanel:7272): DEBUG: 09:46:58.304: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:46:58.304: AbstractWifiInterface.vala:175: Active ap: PLACE
-Corporate
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:175: Active ap: PLACE
-Corporate
** (wingpanel:7272): DEBUG: 09:46:58.305: NMVisualizer.vala:106: Wifi interface added
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:175: Active ap: PLACE
-Corporate
** (wingpanel:7272): DEBUG: 09:46:58.305: NMVisualizer.vala:114: Unknown device: NM_DEVICE_TYPE_BRIDGE
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:46:58.305: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
** (wingpanel:7272): DEBUG: 09:46:58.308: VpnInterface.vala:25: Starting VPN Interface
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.311: IndicatorManager.vala:319: network registered
** (wingpanel:7272): DEBUG: 09:46:58.312: Indicator.vala:93: Activating Nightlight Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.312: IndicatorManager.vala:319: wingpanel-indicator-nightlight registered
** (wingpanel:7272): DEBUG: 09:46:58.315: Indicator.vala:218: Activating Notifications Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.316: IndicatorManager.vala:319: messages registered
** (wingpanel:7272): DEBUG: 09:46:58.321: Indicator.vala:123: Activating Slingshot
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.321: IndicatorManager.vala:319: app-launcher registered
c** (wingpanel:7272): DEBUG: 09:46:58.383: Indicator.vala:549: Activating Sound Indicator
(wingpanel:7272): wingpanel-DEBUG: 09:46:58.388: IndicatorManager.vala:319: sound registered
** (wingpanel:7272): DEBUG: 09:46:58.447: Volume-control.vala:653: Setting volume to 1.000000 for profile -1 because 0
** (wingpanel:7272): DEBUG: 09:47:00.970: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:47:00.971: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:47:00.971: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
** (wingpanel:7272): DEBUG: 09:47:00.971: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:47:00.971: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:47:00.971: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:47:00.991: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
** (wingpanel:7272): DEBUG: 09:47:08.327: AbstractWifiInterface.vala:280: New network state: NETWORK_STATE_CONNECTED_WIFI_OK
** (wingpanel:7272): DEBUG: 09:47:08.327: AbstractWifiInterface.vala:159: Update active AP
** (wingpanel:7272): DEBUG: 09:47:08.327: AbstractWifiInterface.vala:175: Active ap: PLACE-Corporate
(wingpanel:7272): Gtk-CRITICAL **: 09:48:27.030: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7272): Gtk-CRITICAL **: 09:48:27.030: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7272): Gtk-CRITICAL **: 09:48:27.030: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.052: ActUserManager: calling 'ListCachedUsers'
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.052: ActUserManager: Listing cached users, so not setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.057: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.057: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.061: ActUserManager: unrefing manager owned by finished ListCachedUsers call
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.061: ActUserManager: Loading new users, so not setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: Loading new users, so not setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: Found x11 display of session 'c2': :0
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: trying to track new user with uid 1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: finding user with id 1000 state 1
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: waiting for user manager to load before finding user with id 1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUser: adding session c2
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: added session for user with id 1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: Loading new users, so not setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: Loading new users, so not setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: user user is now loaded
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: user user was not yet known, adding it
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: tracking user 'user'
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: not yet loaded, so not emitting user-added signal
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: no pending users, trying to set loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.062: ActUserManager: Seat loaded, so now setting loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: user manager now loaded, proceeding with fetch user request for user with id 1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: finding user with id 1000 state 2
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: Looking for user with id 1000 in accounts service
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: sending user-changed signal for user user
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: sent user-changed signal for user user
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.071: ActUserManager: updating user user
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.082: ActUserManager: Found object path of user with id 1000: /org/freedesktop/Accounts/User1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.082: ActUserManager: finding user with id 1000 state 3
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.082: ActUserManager: user with id 1000 fetched
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.084: ActUserManager: finished handling request for user with id 1000
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.084: ActUserManager: unrefing manager owned by fetch user request
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.090: ActUserManager: user user is now loaded
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.090: ActUserManager: sessions changed (user user) num=1
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.094: ActUserManager: no pending users, trying to set loaded property
(wingpanel:7272): AccountsService-DEBUG: 09:48:27.094: ActUserManager: already loaded, so not setting loaded property
** (wingpanel:7272): DEBUG: 09:48:58.432: Indicator.vala:117: Icon changed to "battery-low-charging-symbolic"
Does not help much I will try to gdb the process.
@peteruithoven the app autorestart when crash (in spite of cerbere being down) so I can't run backtrace
@peteruithoven [UPDATE] wingpanel does not crash when I mouse over the session button if I run it as root.
Any feedback on this ? My session hung on shutdown as well it seems that io.elementary.c has trouble to shut down both plank and wingpanel.
I'm afraid you'll have to do more debugging yourself.
In the indicator itself I only see this press event listener:
https://github.com/elementary/wingpanel-indicator-session/blob/master/src/Indicator.vala#L64-L72
The only mouse over / hover related event in GTK I can find is:
https://valadoc.org/gtk+-3.0/Gtk.Widget.motion_notify_event.html
Which I can't track to an event handler in the code.
Worst case you'll need to remove logic from the indicator until you can hone into what might be triggering the issue.
@peteruithoven Unfortunately I am not a vala expert I cloned the code locally and can build it but do you know how I can activate stronger logging ? Should I just add logging myself ?
That's a great start.
Here's some docs on adding more logs:
https://elementary.io/docs/code/os-dev#debug-logs
But in your case I might just start by commenting out large parts of code until you notice it doesn't crash anymore.
Pinpointed to this
manager = new Session.Services.UserManager (users_separator);Anytime manager is manipulated it freeze the wingpanel
Does that help ? (my compiled version does not show the users but does not freeze anymore)
Interesting. That raises the question whether you've made your current user in a special way?
What happens when you create a new user and from that user try to hover over the indicator?
@peteruithoven Same problem with a brand new account.
I will try to comment some code in userManager.vala to pinpoint what part of the service fails
@danrabbit It still freeze and eventually crash in the log I have this now
EndSessionDialogServer.vala:35: Could not acquire name
@kepicorp could you clarify whether you tried the master or gobject-style-cleanup branch? Maybe try both?
@peteruithoven sorry if I wasn't clear, I tried the gobjet-style-cleanup branch and it still crashes.
With the master origin I experience crash with the new log "Could not acquire name"
@peteruithoven @danrabbit Finally pinpointed to the line that makes it run out of memory
seat = Bus.get_proxy_sync (BusType.SYSTEM, DM_DBUS_ID, seat_path, DBusProxyFlags.NONE);I also get this in the logs at the start of wingpanel
** (wingpanel:10827): WARNING **: 06:54:59.060: EndSessionDialogServer.vala:31: An object is already exported for the interface io.elementary.wingpanel.session.EndSessionDialog at /io/elementary/wingpanel/session/EndSessionDialog
** (wingpanel:10827): WARNING **: 06:54:59.189: EndSessionDialogServer.vala:35: Could not acquire name
Is it possible that wingpanel is already running or trying to start twice?
Is there anything in your syslogs that indicates that wingpanel is running with two different PIDs?
I can't see any other wingpanel process running.
Journalctl shows everything from the same PID.
It seems to take a long time to do any Bus operations. Any ideas of what can slow it down ?
(it does not crash anymore just take around 2-3 min to display the user box)
You could try running sudo dbus-monitor --system while starting wingpanel and reproducing the issue to see if there's anything obvious in the bus traffic.
Are you running a pretty much stock elementary system? Have you installed anything other than the session indicator from source? wingpanel itself for example? Or have you added the daily PPA?
This is a very strange issue that we're not hearing of anyone else experiencing.
This line of code takes always around 1 min to execute:
Bus.get_proxy_sync (BusType.SYSTEM, DM_DBUS_ID, seat_path, DBusProxyFlags.NONE);Where seat_path value is /org/freedesktop/DisplayManager/Seat0
dbus_monitor
The 1 min breaks occurs after this:
method call time=1582030484.227093 sender=:1.190 -> destination=:1.18 serial=117 path=/org/freedesktop/DisplayManager/Seat0; interface=org.freedesktop.DBus.Properties; member=GetAll
string "org.freedesktop.DisplayManager.Seat"
Also after it loaded the menu when I access it, no more 1 min wait but this in the log:
(wingpanel:12690): Gtk-CRITICAL **: 07:39:11.972: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:12690): Gtk-CRITICAL **: 07:39:11.972: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:12690): Gtk-CRITICAL **: 07:39:11.972: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
Could you try with the replace-stderr branch I've just pushed?
It would be interesting to see if there are any additional warnings/errors in the logs with this branch.
Additional critical error I would say (less warning logs though)
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.576: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.576: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.576: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.579: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:8551): Gtk-CRITICAL **: 09:23:45.580: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
None of these logs are the kind I'm looking for, how did you get the Could not acquire name message before? Are there any more criticals/warnings in that log?
Those do not appear anymore (the freeze for a few min still does).
I restarted my computer in the meanwhile.
If you kill cerbere and then start wingpanel with debug logging, what do you get?
You can do this with the following:
killall io.elementary.cerbere
killall wingpanel
G_MESSAGES_DEBUG=all wingpanel
(wingpanel:9678): Gtk-CRITICAL **: 09:57:48.348: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:9678): Gtk-CRITICAL **: 09:57:48.348: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:9678): Gtk-CRITICAL **: 09:57:48.349: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.434: ActUserManager: calling 'ListCachedUsers'
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.434: ActUserManager: Listing cached users, so not setting loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.436: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.436: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.441: ActUserManager: unrefing manager owned by finished ListCachedUsers call
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: user pierre is now loaded
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: user pierre was not yet known, adding it
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: tracking user 'pierre'
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: not yet loaded, so not emitting user-added signal
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: no pending users, trying to set loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.451: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.452: ActUserManager: Found x11 display of session 'c2': :0
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.452: ActUser: adding session c2
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.452: ActUserManager: added session for user pierre
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.452: ActUserManager: Seat loaded, so now setting loaded property
(wingpanel:9678): AccountsService-DEBUG: 09:57:48.463: ActUserManager: already loaded, so not setting loaded property
Are you running a pretty much stock elementary system? Have you installed anything other than the session indicator from source? wingpanel itself for example? Or have you added the daily PPA?
Stock version no daily PPA only wingpanel from source.
None of these outputs are what I'd expect to see. The log output in your last message, was that from syslog or from the terminal after you ran the G_MESSAGES_DEBUG=all wingpanel ? Are you including the full messages while reproducing the issue, or is some of the log omitted?
Lastly, you say you've installed wingpanel from source, do you mean wingpanel, wingpanel-indicator-session, or both? You've obviously built the source of wingpanel-indicator-session, but have you done wingpanel too? There have been some changes to wingpanel recently that may be causing issues if you've installed that from source.
None of these outputs are what I'd expect to see. The log output in your last message, was that from syslog or from the terminal after you ran the
G_MESSAGES_DEBUG=all wingpanel? Are you including the full messages while reproducing the issue, or is some of the log omitted?
From the terminal, message truncated until I click on the power icon (libsession.so part) - nothing logs during the freeze
Lastly, you say you've installed wingpanel from source, do you mean
wingpanel,wingpanel-indicator-session, or both? You've obviously built the source ofwingpanel-indicator-session, but have you donewingpaneltoo? There have been some changes to wingpanel recently that may be causing issues if you've installed that from source.
Only wingpanel-indicator-session not wingpanel do you want me to build it from source ?
** (wingpanel:10827): WARNING **: 06:54:59.189: EndSessionDialogServer.vala:35: Could not acquire name
I don't get this in the replace-stderr branch
I'd like to see all of the warnings/criticals that appear in the terminal logs when you start wingpanel, as this may be a problem when wingpanel starts, not just when you're reproducing the issue.
There you go (I obfuscated WIFI data)
(wingpanel:6250): Gtk-DEBUG: 10:55:38.895: Connecting to session manager
** (wingpanel:6250): DEBUG: 10:55:38.902: Indicator.vala:230: Activating Session Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:38.902: IndicatorManager.vala:319: session registered
** (wingpanel:6250): DEBUG: 10:55:38.930: Indicator.vala:230: Activating DateTime Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:38.930: IndicatorManager.vala:319: datetime registered
** (wingpanel:6250): DEBUG: 10:55:38.945: Indicator.vala:132: Activating Power Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:38.945: IndicatorManager.vala:319: power registered
** (wingpanel:6250): DEBUG: 10:55:38.946: Backlight.vala:28: backlight present: true
** (wingpanel:6250): DEBUG: 10:55:38.948: DeviceManager.vala:67: Connection to UPower bus established
** (wingpanel:6250): DEBUG: 10:55:38.951: Device.vala:165: Connection to UPower device established
** (wingpanel:6250): DEBUG: 10:55:38.953: Device.vala:165: Connection to UPower device established
** (wingpanel:6250): DEBUG: 10:55:39.018: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/line_power_AC" registered
** (wingpanel:6250): DEBUG: 10:55:39.024: Device.vala:165: Connection to UPower device established
** (wingpanel:6250): DEBUG: 10:55:39.026: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/battery_BAT0" registered
** (wingpanel:6250): DEBUG: 10:55:39.026: Indicator.vala:117: Icon changed to "battery-good-charging-symbolic"
** (wingpanel:6250): DEBUG: 10:55:39.028: Indicator.vala:97: Activating Monitor Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.033: IndicatorManager.vala:319: monitor registered
** (wingpanel:6250): DEBUG: 10:55:39.034: Indicator.vala:74: Activating Bluetooth Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.035: IndicatorManager.vala:319: bluetooth registered
** (wingpanel:6250): DEBUG: 10:55:39.037: Indicator.vala:111: Activating Keyboard Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.037: IndicatorManager.vala:319: keyboard registered
** (wingpanel:6250): DEBUG: 10:55:39.041: LayoutsManager.vala:99: get_name_for_xkb_layout (us, (null))
** (wingpanel:6250): DEBUG: 10:55:39.057: Indicator.vala:94: Activating Network Indicator
** (wingpanel:6250): DEBUG: 10:55:39.123: NMVisualizer.vala:106: Wifi interface added
** (wingpanel:6250): DEBUG: 10:55:39.123: NMVisualizer.vala:114: Unknown device: NM_DEVICE_TYPE_BRIDGE
** (wingpanel:6250): DEBUG: 10:55:39.125: VpnInterface.vala:25: Starting VPN Interface
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.126: IndicatorManager.vala:319: network registered
** (wingpanel:6250): DEBUG: 10:55:39.127: Indicator.vala:93: Activating Nightlight Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.127: IndicatorManager.vala:319: wingpanel-indicator-nightlight registered
** (wingpanel:6250): DEBUG: 10:55:39.131: Indicator.vala:218: Activating Notifications Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.131: IndicatorManager.vala:319: messages registered
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.162: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.162: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.162: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.165: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.165: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.165: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.168: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.168: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.168: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.171: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.171: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.171: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.175: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.175: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.175: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.179: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.180: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.180: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.184: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.184: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.184: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.190: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.191: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.191: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.194: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.194: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.194: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.198: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.198: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:55:39.198: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
** (wingpanel:6250): DEBUG: 10:55:39.205: Indicator.vala:123: Activating Slingshot
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.206: IndicatorManager.vala:319: app-launcher registered
** (wingpanel:6250): DEBUG: 10:55:39.266: Indicator.vala:549: Activating Sound Indicator
(wingpanel:6250): wingpanel-DEBUG: 10:55:39.270: IndicatorManager.vala:319: sound registered
** (wingpanel:6250): DEBUG: 10:55:39.272: Indicator.vala:117: Icon changed to "battery-good-charging-symbolic"
** (wingpanel:6250): DEBUG: 10:55:39.501: Volume-control.vala:653: Setting volume to 1.000000 for profile -1 because 0
(wingpanel:6250): Gtk-CRITICAL **: 10:57:04.354: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:57:04.354: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:57:04.354: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.398: ActUserManager: calling 'ListCachedUsers'
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.399: ActUserManager: Listing cached users, so not setting loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.400: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.401: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.406: ActUserManager: unrefing manager owned by finished ListCachedUsers call
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: user pierre is now loaded
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: user pierre was not yet known, adding it
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: tracking user 'pierre'
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: not yet loaded, so not emitting user-added signal
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: no pending users, trying to set loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.414: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.415: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.415: ActUserManager: Found x11 display of session 'c2': :0
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.415: ActUser: adding session c2
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.415: ActUserManager: added session for user pierre
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.415: ActUserManager: Seat loaded, so now setting loaded property
(wingpanel:6250): AccountsService-DEBUG: 10:57:04.427: ActUserManager: already loaded, so not setting loaded property
(wingpanel:6250): Gtk-CRITICAL **: 10:57:11.744: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:57:11.744: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6250): Gtk-CRITICAL **: 10:57:11.744: gtk_widget_get_allocation: assertion 'GTK_IS_WIDGET (widget)' failed
And the log in replace-stderr branch
USER@HOSTNAME:/usr/lib/x86_64-linux-gnu/wingpanel$ G_MESSAGES_DEBUG=all wingpanel
(wingpanel:6601): Gtk-DEBUG: 11:01:59.561: Connecting to session manager
** (wingpanel:6601): DEBUG: 11:01:59.568: Indicator.vala:230: Activating Session Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.568: IndicatorManager.vala:319: session registered
** (wingpanel:6601): DEBUG: 11:01:59.600: Indicator.vala:230: Activating DateTime Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.600: IndicatorManager.vala:319: datetime registered
** (wingpanel:6601): DEBUG: 11:01:59.620: Indicator.vala:132: Activating Power Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.620: IndicatorManager.vala:319: power registered
** (wingpanel:6601): DEBUG: 11:01:59.621: Backlight.vala:28: backlight present: true
** (wingpanel:6601): DEBUG: 11:01:59.625: DeviceManager.vala:67: Connection to UPower bus established
** (wingpanel:6601): DEBUG: 11:01:59.628: Device.vala:165: Connection to UPower device established
** (wingpanel:6601): DEBUG: 11:01:59.631: Device.vala:165: Connection to UPower device established
** (wingpanel:6601): DEBUG: 11:01:59.690: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/line_power_AC" registered
** (wingpanel:6601): DEBUG: 11:01:59.693: Device.vala:165: Connection to UPower device established
** (wingpanel:6601): DEBUG: 11:01:59.694: DeviceManager.vala:126: Device "/org/freedesktop/UPower/devices/battery_BAT0" registered
** (wingpanel:6601): DEBUG: 11:01:59.695: Indicator.vala:117: Icon changed to "battery-good-charging-symbolic"
** (wingpanel:6601): DEBUG: 11:01:59.695: Indicator.vala:97: Activating Monitor Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.698: IndicatorManager.vala:319: monitor registered
** (wingpanel:6601): DEBUG: 11:01:59.699: Indicator.vala:74: Activating Bluetooth Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.699: IndicatorManager.vala:319: bluetooth registered
** (wingpanel:6601): DEBUG: 11:01:59.700: Indicator.vala:111: Activating Keyboard Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.700: IndicatorManager.vala:319: keyboard registered
** (wingpanel:6601): DEBUG: 11:01:59.703: LayoutsManager.vala:99: get_name_for_xkb_layout (us, (null))
** (wingpanel:6601): DEBUG: 11:01:59.719: Indicator.vala:94: Activating Network Indicator
** (wingpanel:6601): DEBUG: 11:01:59.788: NMVisualizer.vala:106: Wifi interface added
** (wingpanel:6601): DEBUG: 11:01:59.788: NMVisualizer.vala:114: Unknown device: NM_DEVICE_TYPE_BRIDGE
** (wingpanel:6601): DEBUG: 11:01:59.790: VpnInterface.vala:25: Starting VPN Interface
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.792: IndicatorManager.vala:319: network registered
** (wingpanel:6601): DEBUG: 11:01:59.793: Indicator.vala:93: Activating Nightlight Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.793: IndicatorManager.vala:319: wingpanel-indicator-nightlight registered
** (wingpanel:6601): DEBUG: 11:01:59.796: Indicator.vala:218: Activating Notifications Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.796: IndicatorManager.vala:319: messages registered
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.825: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.825: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.825: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.830: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.830: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.830: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.833: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.833: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.833: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.837: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.837: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.837: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.840: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.840: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.840: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.843: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.843: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.843: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.846: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.846: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.846: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.849: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.849: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.849: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.852: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.852: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.852: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.855: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.855: gtk_style_context_remove_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
(wingpanel:6601): Gtk-CRITICAL **: 11:01:59.855: gtk_style_context_add_class: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
** (wingpanel:6601): DEBUG: 11:01:59.863: Indicator.vala:123: Activating Slingshot
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.863: IndicatorManager.vala:319: app-launcher registered
** (wingpanel:6601): DEBUG: 11:01:59.926: Indicator.vala:549: Activating Sound Indicator
(wingpanel:6601): wingpanel-DEBUG: 11:01:59.931: IndicatorManager.vala:319: sound registered
** (wingpanel:6601): DEBUG: 11:01:59.933: Indicator.vala:117: Icon changed to "battery-good-charging-symbolic"
** (wingpanel:6601): DEBUG: 11:02:00.024: Volume-control.vala:653: Setting volume to 1.000000 for profile -1 because 0
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.652: ActUserManager: calling 'ListCachedUsers'
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.652: ActUserManager: Listing cached users, so not setting loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.655: ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.656: ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.659: ActUserManager: unrefing manager owned by finished ListCachedUsers call
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: user pierre is now loaded
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: user pierre was not yet known, adding it
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: tracking user 'pierre'
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: not yet loaded, so not emitting user-added signal
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: no pending users, trying to set loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.674: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.675: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.684: ActUserManager: Seat still actively loading, so not setting loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.685: ActUserManager: Found x11 display of session 'c2': :0
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.685: ActUser: adding session c2
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.685: ActUserManager: added session for user pierre
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.685: ActUserManager: Seat loaded, so now setting loaded property
(wingpanel:6601): AccountsService-DEBUG: 11:03:35.700: ActUserManager: already loaded, so not setting loaded property
There's nothing in either of those logs that gives me any hints 😕
I can't think of anything else to try now. Sorry I can't be more help.
The line of code you've highlighted as being the problem runs on hundreds of thousands of computers including mine without issue, or else we'd be getting issue reports about this every second. Did this always happen since you installed elementary or did it start happening after some configuration changes or updates?
If you can set of steps to reproduce this in a VM or if you can think of any more information that might help us track down what's caused this, we can try and look into it further. But unfortunately, the logs look relatively normal now.
The backtrace from the original crash could be useful, so I suppose you could try reinstalling the original version of the indicator and reproducing the crash you had originally in gdb with the following:
sudo apt install --reinstall wingpanel-indicator-session
killall io.elementary.cerbere
killall wingpanel
gdb wingpanel
There's nothing in either of those logs that gives me any hints confused
I can't think of anything else to try now. Sorry I can't be more help.
The line of code you've highlighted as being the problem runs on hundreds of thousands of computers including mine without issue, or else we'd be getting issue reports about this every second. Did this always happen since you installed elementary or did it start happening after some configuration changes or updates?
Since I installed Elementary on this OS I experienced the freeze.
If you can set of steps to reproduce this in a VM or if you can think of any more information that might help us track down what's caused this, we can try and look into it further. But unfortunately, the logs look relatively normal now.
I just compiled my own version of the indicator that bypass those too and it works fine.
The backtrace from the original crash could be useful, so I suppose you could try reinstalling the original version of the indicator and reproducing the crash you had originally in gdb with the following:
sudo apt install --reinstall wingpanel-indicator-session killall io.elementary.cerbere killall wingpanel gdb wingpanel
Can't get it to crash anymore just freeze for 1 or 2 min (gdb not really useful then)
Thanks a lot for checking on this I will just use my workaround.