CrunchBang Linux Forums - Gwibber in 9.04.01

Re: Gwibber in 9.04.01

2009-08-01T11:18:08Z

omns, thank you for solution with downgrade. It works pretty well for me.

Re: Gwibber in 9.04.01

2009-07-15T17:13:43Z

Not that I know of, at least not without hacking the sources. :/ There has been talk of making it more configurable, but I believe this was in response to the knee-jerk reaction when it replaced the original notification system.

Re: Gwibber in 9.04.01

2009-07-15T10:43:14Z

hmm, ended up making my own script based on conkywonky. Not sure what I think of notify-osd. I like that it is transparent. Can the fonts and icon size be tweaked?

Re: Gwibber in 9.04.01

2009-07-15T10:23:19Z

corenominal wrote:

P.S. I will post in another thread with the shell script I am using which switches from the old notification system to the new one.

Looking forward to it. The current notifications aren't quite what they could be.

Re: Gwibber in 9.04.01

2009-07-15T08:41:23Z

^^ good stuff, thank you for sharing. :) For what it is worth, I have noticed that the version that comes with CrunchBang seems much more stable when using the new notifications system, notify-osd. I am not sure why this is, but I thought I would mention it. :/

P.S. I will post in another thread with the shell script I am using which switches from the old notification system to the new one.

Re: Gwibber in 9.04.01

2009-07-14T21:52:00Z

^the above solution didn't work. Pinning to level 1002 seems to have done the trick. So to summarise

In a terminal:

sudo gedit /etc/apt/preferences

then add this entry in the file that opens

Package: gwibber
Pin: release a=jaunty
Pin-Priority: 1002

Update apt or reload synaptic and the ppa should now be the preferred repo for this package. This method should work for any package.

Re: Gwibber in 9.04.01

2009-07-12T02:25:36Z

My only issue with using the gwibber trunk ppa was that the crunchbang repo is pinned to be given preference hence it always tries to downgrade to the 0.9 release. I've solved it by adding the following pin to /etc/apt/preferences. I've never used pins much before. Please advise if this is wrong or could be done better.

Package: gwibber
Pin: release a=jaunty
Pin-Priority: 500

It seems to be working as I want it to. My understanding is that a pin-priority of 500 always favours the highest release number. i.e the PPA

Re: Gwibber in 9.04.01

2009-07-12T01:24:33Z

I've noticed issues as well. For me, it was installing the PPA for Midori. It pulled more recent webkit packages that seemed to make Gwibber unusable. Gwibber would start but never display information. I removed Midori since it always seems to crash for me anyway. Problem solved.

Re: Gwibber in 9.04.01

2009-07-11T23:11:20Z

Mehall wrote:

I use the PPA, so don't notice anything.

I hadn't noticed the trunk PPA for jaunty, will add that to the list :)

Re: Gwibber in 9.04.01

2009-07-11T22:54:50Z

I use the PPA, so don't notice anything.

Re: Gwibber in 9.04.01

2009-07-11T22:46:58Z

My Gwibber does have a tendency to hang now-and-again. I should possibly take a look at the Karmic version. Thanks for the tip! :)

Re: Gwibber in 9.04.01

2009-07-11T22:33:47Z

nm, switched to the latest release available for karmic. Works well but I lost the crunchbang theme. Dark gilouche which is in this package is a nice substitute though :)

Gwibber in 9.04.01

2009-07-11T22:22:03Z

Is anyone else having problems with Gwibber in 9.04.01. I get these errors at startup

console message:  @1: ReferenceError: Can't find variable: addMessages
console message:  @42: ReferenceError: Can't find variable: setGtkConfig
console message:  @1: ReferenceError: Can't find variable: setAccountConfig
console message:  @1: ReferenceError: Can't find variable: addMessages
console message:  @42: ReferenceError: Can't find variable: setGtkConfig
console message:  @1: ReferenceError: Can't find variable: setAccountConfig
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 1094, in process
    self.manage_indicator_items(view.message_store, tab_num=self.tabs.page_num(tab))
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 1050, in manage_indicator_items
    if not self.is_gwibber_active():
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 1047, in is_gwibber_active
    return self.window.xid == screen.get_active_window().get_xid()
AttributeError: 'NoneType' object has no attribute 'get_xid'