On Tue, 27 Mar 2012 19:05:20 -0500 Jeff Hoogland <[email protected]> wrote:
> Thats fine - I'll just comment this error message out of the E code at > compile time then. It literally only pops up for half a second at shut > down. > > It ONLY happens with the new E notification module though. > > It DOES NOT happen when using other notification daemons such as notify-osd. > > That lead me to believe it was an E issue - if people here are of the > opinion it is not that is fine. > > On Tue, Mar 27, 2012 at 6:59 PM, thomasg <[email protected]> wrote: > > > On Wed, Mar 28, 2012 at 01:56, Joel Madero <[email protected]> wrote: > > > As Jeff said, it's been pointed out by at least 10 or so people over at > > > Bodhi forums so it's not just my system. I'm experiencing it on three > > > systems myself > > > > > > On Tue, Mar 27, 2012 at 3:01 PM, thomasg <[email protected]> wrote: > > > > > >> On Tue, Mar 27, 2012 at 23:52, Jeff Hoogland <[email protected]> > > >> wrote: > > >> > E displays a popup notification that says something along the lines > > of: > > >> > > > >> > "Error during DBus init! Please check if > > >> > dbus is correctly installed and running" > > >> > > > >> > As the system shuts down, it is harmless and the system still quickly > > >> shuts > > >> > down (which is why it is hard to say exactly what the massage says). > > But > > >> > many people have noticed it's occurrence. > > >> > > > >> > On Tue, Mar 27, 2012 at 4:19 PM, Michael Blumenkrantz < > > >> > [email protected]> wrote: > > >> > > > >> >> On Tue, 27 Mar 2012 13:38:29 -0700 > > >> >> Joel Madero <[email protected]> wrote: > > >> >> > > >> >> > This has been confirmed by quite a few people over at Bodhi Forums. > > >> >> > > > >> >> > Enabling E Notifications is causing a dbus error to come up upon > > >> shutting > > >> >> > down/rebooting. The error reads: > > >> >> > > > >> >> > "Error during DBus init! Please check if > > >> >> > dbus is correctly installed and running." > > >> >> > > > >> >> > > > >> >> > > > >> >> > The error flashes really fast, fast enough to where I haven't been > > >> able > > >> >> to > > >> >> > get the wording (another user posted the above). One of the staff > > >> over at > > >> >> > bodhi forum thinks it's got to do with the e_modapi_init function > > >> >> > > > >> >> > > > >> >> > Joel > > >> >> > > >> >> define "is causing a dbus error to come up upon shutting > > >> down/rebooting". > > >> >> > > >> >> > > >> >> > > >> > > ------------------------------------------------------------------------------ > > >> >> This SF email is sponsosred by: > > >> >> Try Windows Azure free for 90 days Click Here > > >> >> http://p.sf.net/sfu/sfd2d-msazure > > >> >> _______________________________________________ > > >> >> enlightenment-devel mailing list > > >> >> [email protected] > > >> >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >> >> > > >> > > > >> > > > >> > > > >> > -- > > >> > ~Jeff Hoogland <http://jeffhoogland.com/> > > >> > Thoughts on Technology <http://jeffhoogland.blogspot.com/>, Tech Blog > > >> > Bodhi Linux <http://bodhilinux.com/>, Enlightenment for your Desktop > > >> > > > >> > > ------------------------------------------------------------------------------ > > >> > This SF email is sponsosred by: > > >> > Try Windows Azure free for 90 days Click Here > > >> > http://p.sf.net/sfu/sfd2d-msazure > > >> > _______________________________________________ > > >> > enlightenment-devel mailing list > > >> > [email protected] > > >> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >> > > >> I'd assume your system shuts down the dbus daemon before E exits, thus > > >> E loses the socket connection and throws this error. > > >> I've never noticed it here. > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > > >> This SF email is sponsosred by: > > >> Try Windows Azure free for 90 days Click Here > > >> http://p.sf.net/sfu/sfd2d-msazure > > >> _______________________________________________ > > >> enlightenment-devel mailing list > > >> [email protected] > > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >> > > > > > ------------------------------------------------------------------------------ > > > This SF email is sponsosred by: > > > Try Windows Azure free for 90 days Click Here > > > http://p.sf.net/sfu/sfd2d-msazure > > > _______________________________________________ > > > enlightenment-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > Well, that probably leads to the conclusion that it is bodhi related :) > > > > > > ------------------------------------------------------------------------------ > > This SF email is sponsosred by: > > Try Windows Azure free for 90 days Click Here > > http://p.sf.net/sfu/sfd2d-msazure > > _______________________________________________ > > enlightenment-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > it's impossible for it to be an E issue because the notification module runs as part of the e17 process itself. this process should be shut down as soon as either 1) X closes 2) X session ends. in either case, this error message would only show up if the user's dbus session connection was closed prior to the e17 process ending (due, almost certainly, to the dbus daemon itself terminating improperly), and this is obviously no fault of ours. if, however, you had said that this popup occurred every time e17 closed while using the module, then I would consider investigating further. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
