gabble log: set_shared_status (conn-presence.c:385): shared status invisibility is available dbus-monitor signal sender=org.freedesktop.DBus -> dest=:1.252 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.252" method call sender=:1.252 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='method_call'" method call sender=:1.252 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='method_return'" method call sender=:1.252 -> dest=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='error'" signal sender=:1.244 -> dest=(null destination) serial=537 path=/org/freedesktop/Telepathy/debug; interface=org.freedesktop.Telepathy.Debug; member=NewDebugMessage double 1.3021e+09 string "wocky" uint32 5 string "_end_element_ns: Received stanza * iq xmlns='jabber:client' from='xinu.at' to='biru.ionut@gmail.com/ba64d422' id='1213695752' type='get' * query xmlns='http://jabber.org/protocol/disco#info' node='http://telepathy.freedesktop.org/caps#video-v1'" method call sender=:1.241 -> dest=org.freedesktop.Telepathy.AccountManager serial=160 path=/org/freedesktop/Telepathy/Account/gabble/jabber/biru_2eionut_40gmail_2ecom0; interface=org.freedesktop.DBus.Properties; member=Set string "org.freedesktop.Telepathy.Account" string "RequestedPresence" variant struct { uint32 6 string "busy" string "" } method call sender=:1.27 -> dest=:1.244 serial=1046 path=/org/freedesktop/Telepathy/Connection/gabble/jabber/biru_2eionut_40gmail_2ecom_2fba64d422; interface=org.freedesktop.Telepathy.Connection.Interface.SimplePresence; member=SetPresence string "dnd" string "" method return sender=:1.27 -> dest=:1.241 reply_serial=160 signal sender=:1.244 -> dest=(null destination) serial=538 path=/org/freedesktop/Telepathy/debug; interface=org.freedesktop.Telepathy.Debug; member=NewDebugMessage double 1.3021e+09 string "gabble/connection" uint32 5 string "set_shared_status (conn-presence.c:385): shared status invisibility is available" method return sender=:1.244 -> dest=:1.27 reply_serial=1046 signal sender=:1.27 -> dest=(null destination) serial=1048 path=/org/freedesktop/Telepathy/Account/gabble/jabber/biru_2eionut_40gmail_2ecom0; interface=org.freedesktop.Telepathy.Account; member=AccountPropertyChanged array [ dict entry( string "RequestedPresence" variant struct { uint32 6 string "busy" string "" } ) dict entry( string "ChangingPresence" variant boolean true ) ]
telepathy-gabble 0.11.10
telepathy-gabble 0.11.10 is really broken. The contacts never received my messages and once i downgraded to 0.11.7, everything is alright I used gmail but i didn't test with other xmpp servers to see if they have problems.
log related to message send. gabble/location-DEBUG: 04/07/2011 20:51:45.448035: get_cached_location (conn-location.c:104): - biru.ionut@gmail.com: unknown gabble/location-DEBUG: 04/07/2011 20:51:47.54644: get_cached_location (conn-location.c:104): - biru.ionut@gmail.com: unknown gabble/location-DEBUG: 04/07/2011 20:51:54.67936: get_cached_location (conn-location.c:104): - biru.ionut@gmail.com: unknown gabble/location-DEBUG: 04/07/2011 20:51:57.590471: get_cached_location (conn-location.c:104): - biru.ionut@gmail.com: unknown gabble/vcard-DEBUG: 04/07/2011 20:52:10.957484: timeout_request (vcard-manager.c:787): Request 0xa15f420 timed out, notifying callback 0x81258d0 gabble/vcard-DEBUG: 04/07/2011 20:52:10.957673: pipeline_reply_cb (vcard-manager.c:1344): called for entry 0xa15f400 gabble/vcard-DEBUG: 04/07/2011 20:52:10.957756: delete_request (vcard-manager.c:751): Discarding request 0xa15f420 gabble/pipeline-DEBUG: 04/07/2011 20:52:10.957828: gabble_request_pipeline_go (request-pipeline.c:390): called; 0 pending items, 0 items in flight first should be the notification that i'm typing, second is after i hit enter. i sent two lines
(In reply to comment #2) > telepathy-gabble 0.11.10 is really broken. > > The contacts never received my messages and once i downgraded to 0.11.7, > everything is alright Could be related to bug #36077 maybe?
(In reply to comment #4) > (In reply to comment #2) > > telepathy-gabble 0.11.10 is really broken. > > > > The contacts never received my messages and once i downgraded to 0.11.7, > > everything is alright > > Could be related to bug #36077 maybe? I tried looking at this as Will thought it could be related to the new stanza queuing we have in gabble, but I couldn't reproduce. It could indeed be related to #36077.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #2) > > > telepathy-gabble 0.11.10 is really broken. > > > > > > The contacts never received my messages and once i downgraded to 0.11.7, > > > everything is alright > > > > Could be related to bug #36077 maybe? > > I tried looking at this as Will thought it could be related to the new stanza > queuing we have in gabble, but I couldn't reproduce. > It could indeed be related to #36077. what i'm experiencing is that this happen after a while of being connected. Kill the gabble doesn't help and only after i kill mission-control and logger it will work
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #2) > > > > telepathy-gabble 0.11.10 is really broken. > > > > > > > > The contacts never received my messages and once i downgraded to 0.11.7, > > > > everything is alright > > > > > > Could be related to bug #36077 maybe? > > > > I tried looking at this as Will thought it could be related to the new stanza > > queuing we have in gabble, but I couldn't reproduce. > > It could indeed be related to #36077. > > > what i'm experiencing is that this happen after a while of being connected. > Kill the gabble doesn't help and only after i kill mission-control and logger > it will work yes is related to #36077. I just studied the logs and is related to stanza. I can replicate this issue every morning after leaving the empathy opened all night.
this bug is fixed in 0.12.0
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.