Oneiric shutdown : Tomboy not responding

[Xavier Guillot]

On Ubuntu Oneiric alpha 64, updated, and last version of Tomboy 1.7, when I want to shutdown my computer, I get an error message :

A program is still running

Tomboy Notes
Not responding

Each time I try. If I click on "Shutdown anyway", computer closes and I have not lost notes for the moment.

If I quit Tomboy before closing computer, no error message.

[Xavier Guillot (valeryan-24)]

Bug also occurs when I want to disconnect and is still present in Oneiric alpha 3 for the moment.

[Sebastien Bacher (seb128)]

Somebody should send the bug upstream, that's new since this unstable serie, 1.6 didn't have that issue

[Jeff Licquia (jeff-licquia)]

Tomboy does this on natty for me, with one difference: if you just wait, it goes away on its own after a very short wait (a few seconds). On oneiric, I've waited for several minutes for it to close on its own, with no luck.

[ngsupb (ngsupb)]

all is up. the same bug.

[Jay A. Babcock (newyorkcityjay)]

it happened in 32-bit as well

[Jamie Strandboge (jdstrand)]

FYI, looking at the upstream bug, it seems no one cares.

[Sebastien Bacher (seb128)]

Rodrigo pinged them on IRC this week but I'm not sure how active their team is...

[pablomme (pablomme)]

Tomboy remains responsive and can be shut down by hand in the indicator, which means (if I interpret this fact correctly) that the end-session signal is either not being received or not being acted upon. Having a look at the source (Tomboy/GnomeApplication.cs:{147,164}) it looks like the debug output should indicate whether the query-end-session and end-session signals are being received.

I've attached the stdout/err from 'tomboy --debug' when I reboot the machine. There should be an "[INFO]" entry saying that the query-end session signal has been received, but that does not appear in the log. It is possible that the problem lies outside of tomboy, or that tomboy needs a refresh regarding session handling (possibly due to the switch to gtk3? tomboy links against gtk2 - is the end-session signal passed correctly to gtk2 apps?).

By the way, this bug is also present with gnome-shell, so the culprit is common to unity & shell sessions.

[Evan Broder (broder)]

If you run with DBUS_VERBOSE=1, you can see that the DBus bindings are receiving the QueryEndSignal, but it's not getting passed onto tomboy's handler:

evan@caron:~$ DBUS_VERBOSE=1 tomboy
Warning: WriteBsdCred() failed; falling back to ordinary WriteCred()
Warning: WriteBsdCred() failed; falling back to ordinary WriteCred()
Warning: No signal handler for NameAcquired
Warning: No signal handler for NameAcquired
[INFO 11:52:53.993] Initializing Mono.Addins
Warning: No signal handler for NameAcquired
Warning: No signal handler for QueryEndSession
Warning: No signal handler for CancelEndSession

[Sebastien Bacher (seb128)]

Evan, could you add those comments to the upstream bug?

[Chris Halse Rogers (raof)]

This is actually a bug in dbus-sharp, not Tomboy. dbus-sharp was failing to pass the signals on to the subscribers, which was why Tomboy wasn't receiving it. This looks to be fixed in dbus-sharp trunk, in two nicely cherry-pickable commits. I'll do that now :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package dbus-sharp - 0.7.0-3ubuntu1

---------------
dbus-sharp (0.7.0-3ubuntu1) oneiric; urgency=low

  * Cherry-pick 608328b and 76f43e6c from upstream trunk. Fixes broken signal
    dispatch. (LP: #816950)
 -- Christopher James Halse Rogers <email address hidden> Tue, 04 Oct 2011 16:18:08 +1100

[snowguy (snowguy)]

I see that this was fixed on 10-4. am I reading this right? If so, the fix didn't take. I am still seeing this bug. At least I think it is the same bug. My behavior exactly matches what another user describes at http://askubuntu.com/questions/68006/how-to-fix-desktop-reloading-during-logout-shutdown-restart-after-upgrading-to-1

[Colin Law (colin-law)]

@snowguy, think that if you are not seeing the Not Responding message but are just seeing a delay on logout then you are seeing a different bug. I have started a new bug for the delay issue bug #880299, if this looks like your problem then please add yourself to the affected list.

[snowguy (snowguy)]

Thanks Colin. Agree, I do not see the "not responding" message.

[Sebastien Bacher (seb128)]

while this bug is fixed there are still some issue, see bug #880299 where users claim that tomboy block the session closing for 30s