Gwibber doesn't display updates (due to newer webkit/pywebkitgtk builds)

Bug #304033 reported by Cezar
148
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Medium
Ryan Paul
gwibber (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

After a recent Ubuntu upgrade, Gwibber quit showing updates. There is no error reported and new updates show in notification bubbles. The Replies tab is also empty. I'm running Hardy.

Revision history for this message
Joshua Blount (jblount) wrote : Re: Window doesn't display updates

Although I'm unsure if I had any upgrade prior, I'm experiencing the same problem. No significant changes to my setup, no errors reported via the command line or through View -> Errors, and no updates shown inside of the window.

Revision history for this message
Joshua Blount (jblount) wrote :

Also, I'm still getting updates in the notification bubbles, so that's working. I'm on Ubuntu 8.10 using .7 release of Gwibber from the gwibber-team PPA

Revision history for this message
Joshua Blount (jblount) wrote :

Also, it seems the new version that lp:~jorge packaged (.7.2) hasn't fixed this.

Is it possible that wherever the messages are being stored is "full" ?

Revision history for this message
Joshua Blount (jblount) wrote :

Ok, I found out what my problem was, I had the following in my sources.list:

deb http://ppa.launchpad.net/webkit-team/ubuntu hardy main
deb-src http://ppa.launchpad.net/webkit-team/ubuntu hardy main

I'm unsure when or why I added these, but when I removed them, removed and renstalled gwibber, gwibber was fully functional again (.7.2)

I'm not going to close this bug in case lp:~Cezar is still experiencing trouble, but it seems to be the webkit dependencies that were breaking gwibber for me.

Revision history for this message
Cezar (emperorcezar) wrote : Re: [Bug 304033] Re: Window doesn't display updates

I remember that the webkit ppa was used because the gwibber ppa needed a
never version of webkit than Hardy had in it's repos. IIRC.

On Tue, Dec 2, 2008 at 5:38 AM, Joshua Blount <email address hidden> wrote:

> Ok, I found out what my problem was, I had the following in my
> sources.list:
>
>
> deb http://ppa.launchpad.net/webkit-team/ubuntu hardy main
> deb-src http://ppa.launchpad.net/webkit-team/ubuntu hardy main
>
> I'm unsure when or why I added these, but when I removed them, removed
> and renstalled gwibber, gwibber was fully functional again (.7.2)
>
> I'm not going to close this bug in case lp:~Cezar is still experiencing
> trouble, but it seems to be the webkit dependencies that were breaking
> gwibber for me.
>
> --
> Window doesn't display updates
> https://bugs.launchpad.net/bugs/304033
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Andrew Conkling (andrewski) wrote : Re: Window doesn't display updates

Specifically, the PPA version is 1.0.1-4+r38850~intrepidppa1 and the intrepid-updates version (which works) is 1.0.1-2ubuntu0.1.

I'm guessing something in Webkit's trunk that was applied to the PPA package broke something.

Revision history for this message
Paul Pritchard (paulpritchard68) wrote :

I'm using 8.04 and am seeing the same issue. I've tried removing and reinstalling gwibber but with no joy. I did install the libwebkit-1.0-1 upgrade yesterday and am assuming that this is the problem.

Is there any way of reverting to the previous version?

Revision history for this message
Kimme Utsi (kimme) wrote :

I have the same trouble here with gwibber and have tried to remove it then install it again, to no success. Then I have tried to start it from the terminal, and got this error report....

error: 0 is wrong flag id

Reading here I have tried adding the webkit repo for intrepid to no success.

Revision history for this message
Eetu Huisman (eh) wrote :

I was able to locate the previous version of libwebkit (1.0.1-4+r38688~hardyppa1) in /var/cache/apt/packages and after downgrading to it, Gwibber works again. Apparently something that has happened between 38688 and 38850 is incompatible with Gwibber. Not sure whether it is Gwibber's problem or libwebkit's. (Or maybe just a packaging problem, both of them are in third party repos in Hardy...)

Revision history for this message
Kimme Utsi (kimme) wrote :

Hmmm, how do I that doesn't have that particular file in /var/cache/apt/packages downgrade to that version?

Revision history for this message
Eetu Huisman (eh) wrote :

Kimme: you're using Intrepid, right? Gwibber works just fine on my home machine which I run Intrepid on, I only had this problem at work with Hardy, where libwebkit isn't available in the official repos. I'm guessing that on Intrepid this happens only if you use libwebkit from webkit-team's PPA. Not sure about that, though.

Revision history for this message
Andrew Conkling (andrewski) wrote : Re: [Bug 304033] Re: Window doesn't display updates

On Wed, Dec 3, 2008 at 4:45 AM, Eetu Huisman <email address hidden> wrote:

> I'm guessing that on Intrepid this happens only if you use libwebkit from
> webkit-team's PPA. Not sure about that, though.

That's exactly right.

Revision history for this message
Kimme Utsi (kimme) wrote : Re: Window doesn't display updates

Uhhhhmmmm, that's not right. I have had this problem before I tested out the libwebkit from webkit-team's PPA. And I still have the same problem even if I remove the webkit-team's PPA from my sources list in intrepid and remove gwibber and re-install it. The problem is there.

Revision history for this message
Jorge Castro (jorge) wrote :

Hi guys, I am at wit's end on how to fix this, I am at UDS/FOSSCamp with segphault (the author) and we will be looking hard at this to see if we can find out how to fix it.

Revision history for this message
Andrew Conkling (andrewski) wrote : Re: [Bug 304033] Re: Window doesn't display updates

On Thu, Dec 4, 2008 at 8:21 AM, Kimme Utsi <email address hidden> wrote:

> Uhhhhmmmm, that's not right. I have had this problem before I tested out
> the libwebkit from webkit-team's PPA. And I still have the same problem
> even if I remove the webkit-team's PPA from my sources list in intrepid
> and remove gwibber and re-install it. The problem is there.

You could still theoretically have the PPA libwebkit installed; just
disabling the Webkit PPA doesn't downgrade your package to the
intrepid(-updates) version. Can you post the output of `apt-cache showpkg
libwebkit-1.0-1`?

Revision history for this message
Kimme Utsi (kimme) wrote : Re: Window doesn't display updates
Download full text (3.3 KiB)

Here's the output you requested.........

--
kimme@Cathrine-PC:~$ apt-cache showpkg libwebkit-1.0-1
Package: libwebkit-1.0-1
Versions:
1.0.1-4+r38860~intrepidppa1 (/var/lib/apt/lists/ppa.launchpad.net_stemp_ubuntu_dists_intrepid_main_binary-i386_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/ppa.launchpad.net_stemp_ubuntu_dists_intrepid_main_binary-i386_Packages
                  MD5: bca91605610edfaf76f763d0f248ab54

1.0.1-2ubuntu0.1 (/var/lib/apt/lists/no.archive.ubuntu.com_ubuntu_dists_intrepid-updates_main_binary-i386_Packages) (/var/lib/apt/lists/no.archive.ubuntu.com_ubuntu_dists_intrepid-security_main_binary-i386_Packages)
 Description Language:
                 File: /var/lib/apt/lists/no.archive.ubuntu.com_ubuntu_dists_intrepid-updates_main_binary-i386_Packages
                  MD5: bca91605610edfaf76f763d0f248ab54

1.0.1-2 (/var/lib/apt/lists/no.archive.ubuntu.com_ubuntu_dists_intrepid_main_binary-i386_Packages)
 Description Language:
                 File: /var/lib/apt/lists/no.archive.ubuntu.com_ubuntu_dists_intrepid_main_binary-i386_Packages
                  MD5: bca91605610edfaf76f763d0f248ab54

Reverse Depends:
  python-webkitgtk,libwebkit-1.0-1 1.0.1
  gwibber,libwebkit-1.0-1
  midori,libwebkit-1.0-1 1.0.1
  libwebkit-dev,libwebkit-1.0-1 1.0.1
  libwebkit-1.0-1-dbg,libwebkit-1.0-1 1.0.1-4+r38860~intrepidppa1
  libwebkit-dev,libwebkit-1.0-1 1.0.1
  libwebkit-1.0-1-dbg,libwebkit-1.0-1 1.0.1-2ubuntu0.1
  python-webkitgtk,libwebkit-1.0-1 1.0.1
  midori,libwebkit-1.0-1 0~svn31841
  kazehakase-webkit,libwebkit-1.0-1 0~svn31841
  epiphany-webkit,libwebkit-1.0-1 0~svn31841
  libwebkit1.0-cil,libwebkit-1.0-1 1.0.1
  libwebkit-dev,libwebkit-1.0-1 1.0.1
  libwebkit-1.0-1-dbg,libwebkit-1.0-1 1.0.1-2
Dependencies:
1.0.1-4+r38860~intrepidppa1 - libatk1.0-0 (2 1.20.0) libc6 (2 2.8~20080505) libcairo2 (2 1.6.0) libcurl3-gnutls (2 7.16.2-1) libfontconfig1 (2 2.4.0) libfreetype6 (2 2.3.5) libgcc1 (2 1:4.1.1) libglib2.0-0 (2 2.16.0) libgtk2.0-0 (2 2.14.1) libicu38 (2 3.8-5) libjpeg62 (0 (null)) libpango1.0-0 (2 1.21.6) libpng12-0 (2 1.2.13-4) libsqlite3-0 (2 3.5.9) libstdc++6 (2 4.1.1) libx11-6 (0 (null)) libxml2 (2 2.6.27) libxslt1.1 (2 1.1.18) libxt6 (0 (null))
1.0.1-2ubuntu0.1 - libatk1.0-0 (2 1.20.0) libc6 (2 2.8~20080505) libcairo2 (2 1.6.0) libcurl3-gnutls (2 7.16.2-1) libfontconfig1 (2 2.4.0) libfreetype6 (2 2.3.5) libgcc1 (2 1:4.1.1) libglib2.0-0 (2 2.16.0) libgtk2.0-0 (2 2.14.1) libicu38 (2 3.8-5) libjpeg62 (0 (null)) libpango1.0-0 (2 1.21.6) libpng12-0 (2 1.2.13-4) libsqlite3-0 (2 3.5.9) libstdc++6 (2 4.1.1) libx11-6 (0 (null)) libxml2 (2 2.6.27) libxslt1.1 (2 1.1.18) libxt6 (0 (null))
1.0.1-2 - libatk1.0-0 (2 1.20.0) libc6 (2 2.8~20080505) libcairo2 (2 1.6.0) libcurl3-gnutls (2 7.16.2-1) libfontconfig1 (2 2.4.0) libfreetype6 (2 2.3.5) libgcc1 (2 1:4.1.1) libglib2.0-0 (2 2.16.0) libgtk2.0-0 (2 2.13.3) libicu38 (2 3.8-5) libjpeg62 (0 (null)) libpango1.0-0 (2 1.21.3) libpng12-0 (2 1.2.13-4) libsqlite3-0 (2 3.5.9) libstdc++6 (2 4.1.1) libx11-6 (0 (null)) libxml2 (2 2.6.27) libxslt1.1 (2 1.1.18) libxt6 (0 (null))
Provides:
1.0.1-4+r38860~intrepidppa1 -
1.0.1-2ubuntu0.1 -
1.0...

Read more...

Revision history for this message
Andrew Conkling (andrewski) wrote : Re: [Bug 304033] Re: Window doesn't display updates

On Thu, Dec 4, 2008 at 5:01 PM, Kimme Utsi <email address hidden> wrote:

> Can you get something out of this, and how do I downgrade my libwebkit
> package in Ubuntu?

Yes, it does look like you still have the PPA version installed.

You can either downgrade the package via Synaptic:
Select libwebkit-1.0-1 and go to Package | Force Version.... Select the
version from either intrepid-updates or intrepid (depending on which
repositories you have enabled).

Or, if you're like me and only added the Webkit PPA because you needed it
for Gwibber :), try the following to disable/remove it:
In Synaptic, Settings | Repositories. (Or go to System | Administration |
Software Sources.) On the Third-Party Software tab, find the Webkit PPA (
http://ppa.launchpad.net/webkit-team/ubuntu) and uncheck it (to temporarily
disable it) or highlight it and press Remove to get rid of it completely.
(I'd suggest disabling it for now, and then removing it later if you find
you don't need it again.)

Let me know if that doesn't work.

Revision history for this message
Kimme Utsi (kimme) wrote : Re: Window doesn't display updates

It did work, so thank you. I'm back on gwibber with this laptop. (It did work on my CrunchBang Eee 900, and on my stationary, but not on this laptop)

Revision history for this message
Marius Bock (marius) wrote :

Am on Hardy and was affected by bug #305696 which is now fixed by the new PPA webkit release so no segfault anymore.

But now I have this bug where nothing is displayed in the main window. I do received notifications in the Panel though.

Any advice.

Revision history for this message
Rémi Prévost (remiprev) wrote :

Same here. No more segfault but no more updates either.

Revision history for this message
Joe Palladino (mindfulgeek) wrote :

I had the same problem in 8.10 using the PPA webkit. When I downgraded to the webkit that is in the ubuntu repositories everything worked fine.

Revision history for this message
Ben (ben2talk) wrote :

Uninstalled Webkit, removing a few other packages (Midori) along the way. Removed extra Midori repository, and then reinstalled Webkit and Gwibber - works fine now.

Revision history for this message
Rémi Prévost (remiprev) wrote :

Upgrade to Intrepid, updated libwebkit and this bug is solved. Probably not related to Gwibber but with libwebkit.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

What version of libwebkit?

Revision history for this message
Rémi Prévost (remiprev) wrote :

The (working) one in intrepid's repositories is 1.0.1-2.
The (non-working) one in webkit-team's ppa is 1.0.1-4.

Revision history for this message
Dominic Evans (oldmanuk) wrote :

This needs further investigation, to establish what the problem is whilst running gwibber with latest trunk builds of webkit and pywebkitgtk

Changed in gwibber:
importance: Undecided → Medium
Revision history for this message
Ryan Paul (segphault) wrote :

@Dominic:

I spent some time with Ken VanDine trying to isolate the problem. It seems like using JavaScript to add content inside of a tag is not working in several revisions of WebKit. The problem is only exhibited in some cases, however, and not others. When I tested a really basic example with a simple string, it worked consistently. I suspect that it's choking on something in the strings that Gwibber is trying to append. I'm convinced that it's an upstream problem, but I can't find a pattern or narrow it down with enough specificity to file a meaningful bug report upstream.

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

Confirmed that this bug is affecting Fedora Rawhide as well (and annoying me greatly)!

WebKit-r40351 and r40408 seem to be affected (I tried both of them without success).

Revision history for this message
Ben (ben2talk) wrote :

My problem stemmed from Midori - I added repos and got .04 version of webkit and Midori runs very nicely.

Basically, I've had to revert to the earlier webkit and earlier Midori to get Gwibber back - but it's a fair sacrifice to make. I liked the new Midori - very promising.

Revision history for this message
Ryan Lerch (ryanlerch) wrote :

i am encountering this one also, on fedora 10 (revision 199 of gwibber - package - gwibber-0.7.3-3.199bzr.fc10.src.rpm)

from what i can gather from a user level perspective is that this bug (for me at least) only presents when an RSS feed "account" is enabled.

also, as well as the updates not appearing in the main window, the updates that have previously appeared in the gnome notification bubbles keep appearing with each refresh, along with the new updates.

here is what is being returned to the console (each one of these 3 tracebacks occurred during 3 sequential refreshes. ):
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/threading.py", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 867, in process
    self.show_notification_bubbles(view.message_store)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 830, in show_notification_bubbles
    message.first_seen and gintegration.can_notify and \
AttributeError: Message instance has no attribute 'first_seen'

Exception in thread Thread-6:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/threading.py", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 867, in process
    self.show_notification_bubbles(view.message_store)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 830, in show_notification_bubbles
    message.first_seen and gintegration.can_notify and \
AttributeError: Message instance has no attribute 'first_seen'

Exception in thread Thread-7:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/threading.py", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 867, in process
    self.show_notification_bubbles(view.message_store)
  File "/usr/lib/python2.5/site-packages/gwibber/client.py", line 830, in show_notification_bubbles
    message.first_seen and gintegration.can_notify and \
AttributeError: Message instance has no attribute 'first_seen'

hope this helps,
ryanlerch

Revision history for this message
Ryan Lerch (ryanlerch) wrote :

just confirming that bug only appears for me when i have this feed set up and enabled for receiving messages:
http://search.twitter.com/search.atom?q=%22open+source%22

not sure if this is the same bug as originally reported, should i open another bug report?

cheers,
ryanlerch

Revision history for this message
Eetu Huisman (eh) wrote :

Ryan, I think it is a separate bug. I've suffered of both and they don't seem to be linked.

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

Yeah, I'm 99% sure this is a different bug. The rawhide issue spits out errors like:

console message: undefined @1: ReferenceError: Can't find variable: addMessages
console message: undefined @22: ReferenceError: Can't find variable: setGtkConfig
console message: undefined @1: ReferenceError: Can't find variable: setAccountConfig
console message: undefined @1: ReferenceError: Can't find variable: addMessages
console message: undefined @22: ReferenceError: Can't find variable: setGtkConfig
console message: undefined @1: ReferenceError: Can't find variable: setAccountConfig

Those are functions in the theme.html file, part of the jquery script. It looks like either pywebkitgtk or webkit-gtk isn't able to handle these in the latest versions.

Revision history for this message
Amr Hassan (amr-hassan) wrote :

confirmed. but i don't recall updating webkit or pywebkitgtk recently! i have only one identi.ca account set up.

Revision history for this message
André Gondim (andregondim) wrote :

I've had the same problem to see twitter.
All my version:
Configurando python-simplejson (1.9.2-1) ...
Configurando python-webkitgtk (1.0.1-0ubuntu2) ...
Configurando python-feedparser (4.1-12) ...
Configurando gwibber (0.7.3~bzr200-0ubuntu1~jaunty~ppa0) ...
Configurando libtidy-0.99-0 (20081224cvs-1) ...
Configurando python-chardet (1.0.1-1.1) ...
Configurando python-utidylib (0.2-3.2ubuntu1) ...

I'm running Jaunty Alpha 4.

Cheers.

Revision history for this message
DrSimonTucker (s-tucker) wrote :

I have the same problem on Gentoo built against pywebkitgtk-1.0.2.tar.gz

Jorge Castro (jorge)
Changed in gwibber:
status: New → Triaged
Revision history for this message
Philip Taylor (scraliontis) wrote :

i just tried gwibber in intrepid 8.10, with all recent updates, from the gwibber ppa, and it runs, i get the notification bubbles but nothing in the main message window whn i get messages either direct or not, is there a formula to solve this yet, or isnt there a formula to solve ths yet.

Revision history for this message
Philip Taylor (scraliontis) wrote :

ok, i killed the webkit ppa, version of webkit, to the standerd 8.10 version of webkit, as far as i can see this solved it in 8.10. please confirm.

Revision history for this message
Philip Taylor (scraliontis) wrote :

ie, sorry, i downgraded to the standerd interpidversion of webkit.

Revision history for this message
Jorge Castro (jorge) wrote :

Let's keep this open, I'm not convinced that downgrading has been working for everyone just yet. (Though it seems to solve the problem for a bunch of people.)

Revision history for this message
Cezar (emperorcezar) wrote : Re: [Bug 304033] Re: Gwibber doesn't display updates (due to newer webkit/pywebkitgtk builds)

Also, it's a big problem for Hardy users, not just Intrepid users. From what
I understand, a lot of people use the ppas in Hardy to get a reasonably new
version.

On Sun, Feb 22, 2009 at 12:06 PM, Jorge O. Castro <email address hidden> wrote:

> Let's keep this open, I'm not convinced that downgrading has been
> working for everyone just yet. (Though it seems to solve the problem for
> a bunch of people.)
>
> --
> Gwibber doesn't display updates (due to newer webkit/pywebkitgtk builds)
> https://bugs.launchpad.net/bugs/304033
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
uvok (uvok-deactivatedaccount) wrote :

Also using gentoo.
dev-python/pywebkitgtk 1.0.2
net-libs/webkit-gtk r40220
dev-python/gwibber 0.8

will try updating to net-libs/webkit-gtk p41279

Revision history for this message
Cezar (emperorcezar) wrote :

I'm looking for an update on the progress of this bug. As time drags on and on I'm becoming more and more frustrated. If the solution is downgrading. I please please ask that it be done for the Hardy PPAs. As a Hardy user I'm feeling left out. I understand it's a PPA, but it's the only place to get gwibber for Hardy and as such it should at least work. Especially if all it takes is a downgrade.

If there isn't the ambition or will of the managers of the PPA to do the downgrade or fix then I think the section of the wiki stating the PPAs for Hardy users should be notated to reflect the situation that they currently do not work.

Revision history for this message
Ryan Paul (segphault) wrote :

@Cezar: As I understand it, the problem is that the newer revisions of WebKit from the WebKit PPA are exhibiting this bug. We don't have control over what is in the WebKit PPA nor do we have the ability to fix this specific WebKit bug.

We are currently investigating a new approach to theming that will effectively circumvent this issue and make it so that we don't have to worry about specific revisions to WebKit. I'm going to be getting this work done and into trunk shortly after we get all of the loose ends tied up for Jaunty.

As a side note, I'd like to say that we don't consider Hardy support to be a high priority, and we will not be supporting it in ongoing development for the full duration of Canonical's Hardy support cycle.

Revision history for this message
Cezar (emperorcezar) wrote :

Thanks. Knowing that it's being worked on help relieves many of my concerns.

On Mon, Mar 2, 2009 at 12:30 PM, Ryan Paul <email address hidden>wrote:

> @Cezar: As I understand it, the problem is that the newer revisions of
> WebKit from the WebKit PPA are exhibiting this bug. We don't have
> control over what is in the WebKit PPA nor do we have the ability to fix
> this specific WebKit bug.
>
> We are currently investigating a new approach to theming that will
> effectively circumvent this issue and make it so that we don't have to
> worry about specific revisions to WebKit. I'm going to be getting this
> work done and into trunk shortly after we get all of the loose ends tied
> up for Jaunty.
>
> As a side note, I'd like to say that we don't consider Hardy support to
> be a high priority, and we will not be supporting it in ongoing
> development for the full duration of Canonical's Hardy support cycle.
>
> --
> Gwibber doesn't display updates (due to newer webkit/pywebkitgtk builds)
> https://bugs.launchpad.net/bugs/304033
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

Any status update here? Fedora 11 is going to ship with WebKit 1.1.1 (at a minimum), and this is very broken with that.

Revision history for this message
Jorge Castro (jorge) wrote :

From talking with Ryan over IM it doesn't look like we're any closer to finding out the root cause of problem. I will look around for webkit and gtk smart people to see if we can get some help.

Shipping a 1.0 that doesn't work in Fedora would not be very good at all so any help hunting down someone who might be able to help would be very much appreciated.

Revision history for this message
Jorge Castro (jorge) wrote :

Hi spot, would it be possible to get some Fedora people banging on the new theme branch? It should work better with newer webkit builds.

https://code.launchpad.net/~segphault/gwibber/template-theme-engine

Revision history for this message
Ian Weller (ianweller) wrote :

Jorge, I can take a look at this in a few hours after school.

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

I tried bzr 280 for the template-theme-engine branch, and while it no longer throws the errors that the old code used to (e.g. "Can't find variable: addMessages"), it doesn't actually... umm... work. It crashes repeatedly, when I try to add my Twitter account, when I try to refresh it... and it never draws any messages.

Revision history for this message
Mark__T (mark-trompell) wrote :

Did anyone already ask the webkit guys?
Even if they don't acknowledge that it's their bug, they might know a way to work around it.

Revision history for this message
Eivind Tagseth (eivindt) wrote :

Same problem here on gentoo. However (and I haven't seen anyone else reporting this), if I post a new status (using gwibber), the messages _do_ show up.

Does posting a new status trigger something that refreshing doesn't?

Revision history for this message
Giorgio (uastasi) wrote :

Gwibber shows updates into notification popups but they are not displayed into the application. Any action performed such as reload, post an update or search brings the application to crash.

Info:
ArchLinux
gwibber-bzr 302
webkit 1.1.6
pywebkitgtk 1.1.4

Revision history for this message
Ryan Paul (segphault) wrote :

It would be very helpful if some of you who are experiencing this bug could try out the template-theme-engine branch and let me know if that fixes the problem:

https://code.edge.launchpad.net/~segphault/gwibber/template-theme-engine

Please note that this branch requires the Mako library for Python (python-mako package on ubuntu).

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

Ryan, we've moved to this in Fedora 11, and it definitely fixes the core problem, but it introduces some other less painful issues, specifically:

* Random crashes (I'm trying to pin this down, I know it is painfully vague)
* Double bubbling (each message received gets bubbled up (as a popup bubble) twice, with about a 30 second or so delay between instances of the same message popping up)

Revision history for this message
Giorgio (uastasi) wrote :

Ryan, I've switched to that branch and I'm able to see posts into the application now. Let me know if you want me to perform some other actions.

Revision history for this message
Ryan Paul (segphault) wrote :

I really appreciate the feedback! My current goal is to get the template-theme-engine branch merged into trunk this weekend. I'd like to get some of the remaining issues nailed down first.

The double bubbling sounds very strange. I have no idea what could possibly be causing that. I have definitely not observed it on Ubuntu. Does this happen to *every* message or just some? There are some that will inevitably be duplicated, like if a @reply is shown on the main tab and on the replies tab, it will be shown twice. I'm still working on fixing that issue and it's not specific to the template-theme-engine branch.

Could you tell me more about the random crashes? When do they happen? There are some WebKit bugs that are causing problems for us and they are making Gwibber crash sometimes for some users. That's not specific to the template-theme-engine branch, however. If you are seeing consistently repeatable crashes under certain conditions or a significantly higher number of crashes than people are experiencing with other branches, then I think we need to explore the problem in more depth before I can merge template-theme-engine into trunk. Basically, I would like to establish right now if there are factors that should block merging and then we can sort out these other problems separately.

Thanks!! :-)

Revision history for this message
Tom "spot" Callaway (tcallawa) wrote :

Well, the random crashes are hard, because thankfully, they're few and far between.

The double bubbles happen on EVERY message, which is rather annoying. I threw in some very crude debugging code:

--- gwibber/gwibber/client.py.BAD 2009-05-08 10:02:48.782382179 -0400
+++ gwibber/gwibber/client.py 2009-05-08 10:04:03.449382030 -0400
@@ -995,12 +995,14 @@ class GwibberClient(gtk.Window):
     new_messages.reverse()
     gtk.gdk.threads_enter()
     if len(new_messages) > 0:
+ print('len(new_messages) > 0')
         for index, message in enumerate(new_messages):
             body = microblog.support.xml_escape(message.text)
             image = hasattr(message, "image_path") and message.image_path or ''
             expire_timeout = 5000 + (index*2000) # default to 5 second timeout and increase by 2 second for each notification
             n = gintegration.notify(message.sender, body, image, ["reply", "Reply"], expire_timeout)
             self.notification_bubbles[n] = message
+ print('popping up message: %s' % body)
     gtk.gdk.threads_leave()

Then, I ran gwibber and waited:

[spot@velociraptor F-11]$ gwibber
len(new_messages) > 0
popping up message: RT @PanoramaSW: OffiSync integrates Google Docs with Microsoft Office http://bit.ly/NZ52S
popping up message: saw a giant bug in a gas station restroom today - wanted to ask it if it needed a newspaper and a match. I'm here all weekend, try the meatloaf.
popping up message: Off to Columbus today, and no, that's not some arty metaphor. Although why that would be thought metaphoric is beyond me. I'll shut up now.
len(new_messages) > 0
popping up message: RT @PanoramaSW: OffiSync integrates Google Docs with Microsoft Office http://bit.ly/NZ52S
popping up message: saw a giant bug in a gas station restroom today - wanted to ask it if it needed a newspaper and a match. I'm here all weekend, try the meatloaf.
popping up message: Off to Columbus today, and no, that's not some arty metaphor. Although why that would be thought metaphoric is beyond me. I'll shut up now.

There is about a 30 second pause between the two bunches of bubbles. It feels almost like a dbus timeout issue.

libnotify is 0.4.5, dbus is 1.2.12 (ubuntu may have older versions?)

Revision history for this message
Ken VanDine (ken-vandine) wrote :

I have seen the exact behavior on both Jaunty and Foresight

Revision history for this message
Ryan Paul (segphault) wrote :

The new template system in trunk resolves this bug. Please remember to install the Mako template library before you test it.

Changed in gwibber:
assignee: nobody → Ryan Paul (segphault)
status: Triaged → Fix Released
Revision history for this message
Matt Zimmerman (mdz) wrote :

Opening an Ubuntu task on this bug, since it's still present there (until we get the latest bits into Karmic)

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 1.2.0~bzr346-0ubuntu1

---------------
gwibber (1.2.0~bzr346-0ubuntu1) karmic; urgency=low

  * snapshot 1.2.0~bzr346 fixes: LP: #304033

  [ Fabien Tassin ]
  * New upstream snapshot
  * Add python-mako to Depends

 -- Alexander Sack <email address hidden> Fri, 03 Jul 2009 20:32:57 +0200

Changed in gwibber (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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