>
> 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.
>
> --
So, how to fix it? I have exactly the same
Bodhi
On Tue, 27 Mar 2012 22:51:18 -0500 Jeff Hoogland said:
well i mostly put bafflement towards the issue and scratched my head going
"wtf? how can this be?". the hup thing came to mind as a possible way e could
go thru an init process again...
> I'll try rebuilding E with that line commented out an
I'll try rebuilding E with that line commented out and see what happens -
thanks for putting some thought towards the issues.
Love you E folks :)
On Tue, Mar 27, 2012 at 9:21 PM, Gustavo Sverzut Barbieri <
barbi...@profusion.mobi> wrote:
> On Tue, Mar 27, 2012 at 10:46 PM, Lucas De Marchi
> wro
On Tue, Mar 27, 2012 at 10:46 PM, Lucas De Marchi
wrote:
> On Tue, Mar 27, 2012 at 10:08 PM, Michael Blumenkrantz
> wrote:
>> On Wed, 28 Mar 2012 09:45:59 +0900
>> Carsten Haitzler (The Rasterman) wrote:
>>
>>> On Tue, 27 Mar 2012 20:38:39 -0400 Michael Blumenkrantz
>>> said:
>>>
>>> > > > thin
On Tue, Mar 27, 2012 at 10:08 PM, Michael Blumenkrantz
wrote:
> On Wed, 28 Mar 2012 09:45:59 +0900
> Carsten Haitzler (The Rasterman) wrote:
>
>> On Tue, 27 Mar 2012 20:38:39 -0400 Michael Blumenkrantz
>> said:
>>
>> > > > things you should investigate:
>> > > > 1) why the initial bug report was
On Wed, 28 Mar 2012 09:45:59 +0900
Carsten Haitzler (The Rasterman) wrote:
> On Tue, 27 Mar 2012 20:38:39 -0400 Michael Blumenkrantz
> said:
>
> > > > things you should investigate:
> > > > 1) why the initial bug report was entirely faulty and incomplete
> > > > 2) the results of sending a back
On Tue, 27 Mar 2012 20:38:39 -0400 Michael Blumenkrantz
said:
> > > things you should investigate:
> > > 1) why the initial bug report was entirely faulty and incomplete
> > > 2) the results of sending a backtrace produced by running e17 compiled
> > > with this really bad patch I've attached
> >
On Wed, 28 Mar 2012 09:36:41 +0900
Carsten Haitzler (The Rasterman) wrote:
> On Tue, 27 Mar 2012 20:30:19 -0400 Michael Blumenkrantz
> said:
>
> > On Tue, 27 Mar 2012 19:15:51 -0500
> > Jeff Hoogland wrote:
> >
> > > This is exactly the case - what should I investigate?
> > >
> > > On Tue, M
On Tue, 27 Mar 2012 20:30:19 -0400 Michael Blumenkrantz
said:
> On Tue, 27 Mar 2012 19:15:51 -0500
> Jeff Hoogland wrote:
>
> > This is exactly the case - what should I investigate?
> >
> > On Tue, Mar 27, 2012 at 7:14 PM, Michael Blumenkrantz <
> > michael.blumenkra...@gmail.com> wrote:
> >
On Tue, 27 Mar 2012 19:05:20 -0500 Jeff Hoogland said:
wait... i just had an idea... is something SENDING e a HUP signal during
shutdown? one of the shutdown scripts? sending e a HUP signal (killall -HUP
enlightenment) tells e to RESTART. (HUP is a common signal used for this -
telling daemons to
For #1 I take blame for incomplete bug report, I'm trying to get more
involved and I try to include what I think is helpful. It's a learning
process and I hope you bare with me. Jeff has been slowly helping me be
more complete and accurate with my reporting.
for #3.well, stop emailing and star
On Tue, 27 Mar 2012 19:15:51 -0500
Jeff Hoogland wrote:
> This is exactly the case - what should I investigate?
>
> On Tue, Mar 27, 2012 at 7:14 PM, Michael Blumenkrantz <
> michael.blumenkra...@gmail.com> wrote:
>
> > On Tue, 27 Mar 2012 19:05:20 -0500
> > Jeff Hoogland wrote:
> >
> > > Thats
On Tue, 27 Mar 2012 13:38:29 -0700 Joel Madero said:
> 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 corr
On Tue, 27 Mar 2012 19:05:20 -0500 Jeff Hoogland said:
> 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
On Tue, 27 Mar 2012 19:05:20 -0500
Jeff Hoogland 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
On Tue, 27 Mar 2012 19:02:42 -0500
Jeff Hoogland wrote:
> I guess that is just how Ubuntu shutdown order goes.
>
> Is it decided then that this is an issue with the shutdown order and not an
> E-related thing?
>
> On Tue, Mar 27, 2012 at 6:59 PM, Michael Blumenkrantz <
> michael.blumenkra...@gm
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
Now that it's been pointed out I remember vaguely reading a critical piece
against Ubuntu for decreasing shutdown times by using some method that
shuts down services incorrectly.
On Tue, Mar 27, 2012 at 5:02 PM, Jeff Hoogland wrote:
> I guess that is just how Ubuntu shutdown order goes.
>
> I
I guess that is just how Ubuntu shutdown order goes.
Is it decided then that this is an issue with the shutdown order and not an
E-related thing?
On Tue, Mar 27, 2012 at 6:59 PM, Michael Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> On Tue, 27 Mar 2012 16:56:05 -0700
> Joel Madero wro
On Wed, Mar 28, 2012 at 01:56, Joel Madero 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 wrote:
>
>> On Tue, Mar 27, 2012 at 23:
On Tue, 27 Mar 2012 16:56:05 -0700
Joel Madero 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 wrote:
>
> > On Tue, Mar 27, 201
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 wrote:
> On Tue, Mar 27, 2012 at 23:52, Jeff Hoogland
> wrote:
> > E displays a popup notificatio
On Tue, Mar 27, 2012 at 23:52, Jeff Hoogland 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
> do
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)
On Tue, 27 Mar 2012 13:38:29 -0700
Joel Madero 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 cor
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
26 matches
Mail list logo
