LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6

Bug #783181 reported by Charlie Schluting ☃
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gwibber
New
Undecided
Unassigned

Bug Description

When trying to post to ping.fm, it never works.
It's working when I post to only one service (statusnet).

Running gwibber in the foreground, yields:

(gwibber:2812): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed

ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Searches:/com/gwibber/Searches: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Searches was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Messages:/com/gwibber/Messages: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Messages was not provided by any .service files

(gwibber:2888): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
(gwibber:2888): LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6

I'm posting a new message:
(gwibber:2888): LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6
I'm posting a new message:
(gwibber:2888): LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6
I'm posting a new message:
(gwibber:2888): LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6

Running the following on Natty, freshly updated today:
gwibber 3.1.0~bzr990-0ubuntu1~daily1
(it has been broken for a while - at least ~3 weeks I believe)

Revision history for this message
Matt Zimmerman (mdz) wrote :

Possibly a duplicate of bug 730976?

Revision history for this message
Charlie Schluting ☃ (cschluti) wrote :

Hmm, yes, very likely it is.
I'll mark as duplicate and watch the other bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.