[Dx-packages] [Bug 1581920] Re: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1581920 Title: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed Status in indicator-applet package in Ubuntu: Confirmed Bug description: Every time I look at my syslog it is a sea of assertions interspersed with actual relevant logs. I have been letting this go for a long time. I think it is time I tried to stop the log spam. I love the applet, it is great! My syslog consists of endless spam like this: May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7
On Tue, Jan 10, 2017 at 12:39:40PM -, Jean-Baptiste Lallement wrote: > I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders > the device completely unusable (cf bug 1654241) > > Marking as verification-failed. That's fair, but note that this is *not* a bug with this SRU. Something is starting a dbus-daemon and setting its address in the environment. It then is terminated and not available in the session. This SRU makes dbus not start a new bus if the environment is saying there already is one. Yes, it should be held out of -updates until that is fixed. But the fix is elsewhere. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: Fix Committed Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7
I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders the device completely unusable (cf bug 1654241) Marking as verification-failed. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: Fix Committed Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
