[pkg depends issue?] Unable to add accounts using Gwibber in fresh Kubuntu Jaunty installation

[wolfger]

Binary package hint: gwibber

Description: Ubuntu jaunty (development branch)
Release: 9.04
(beta 1)

gwibber:
  Installed: 0.8-0ubuntu3
  Candidate: 0.8-0ubuntu3
  Version table:
 *** 0.8-0ubuntu3 0
        500 http://us.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Upon starting Gwibber, I attempted to add a Twitter account. I am able to fill out all fields in the account creation box, but there is no "OK" button, just a "Close" button and a "Delete" button. Pressing the Close button does nothing. Pressing the "Delete" button does nothing either. I can only get out by clicking the X in the titlebar. When I go to Manage Accounts, I see a number of accounts there, but they have no username associated with them, and are not set to send or receive (despite me having checked those boxes during creation).

[wolfger (wolfger)]

I should probably add that this is *Kubuntu*, not Ubuntu as stated above (from the lsb_release -rd command). It's also 64-bit. Output from the command line complains of not being able to talk to gnome-keyring, so that could be the key. I'm attaching that output.

[Nicolas NOEL (chessplayer352000)]

I have the same problem, here is what I get when I launch it from the terminal :

console message: @1: ReferenceError: Can't find variable: addMessages
console message: @42: ReferenceError: Can't find variable: setGtkConfig
console message: @12: 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: @12: ReferenceError: Can't find variable: setAccountConfig
console message: file:///usr/share/gwibber/ui/themes/default/jquery.js @12: SyntaxError: Parse error

[Dominic Evans (oldmanuk)]

I believe the problem here for KDE is that either a) KDE is simply not adding a new startup entry for the gnome keyring daemon or b) Gwibber's pkg dependencies did/do not include the gnome-keyring-daemon package

so check if the pkg is installed via `dpkg -l gnome-keyring-daemon` (and install it if it isn't already)

then add a startup application to your session to invoke `gnome-keyring-daemon --start`

logout and login and see if Gwibber starts

please report success/failure of this workaround

[Jelle De Loecker (skerit)]

It's not only Kubuntu, the same problem occurs in Gnome, on a regular, fresh, Ubuntu install.

[Alexander Sack (asac)]

we added python-glade2 and python-moko to the dependency list recently. Is that enough or do we need more? also, dominic, do we really need a depends on gnome-keyring-daemon?

[Alexander Sack (asac)]

not a gwibber upstream problem as it seems.

[Alexander Sack (asac)]

pkg dependency problems are high importance

[Rich Johnson (nixternal)]

Just tested out on Kubuntu Karmic and adding information per Jorge. I cannot reproduce this bug at this time due to the fact gwibber will not even start up. Pasting the output below:

-------
WARNING:root:desktopcouch is not available. . falling back to gconf

** (gwibber:12444): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (gwibber:12444): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum'

** (gwibber:12444): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 57, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 106, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 186, in __init__
    self.setup_ui()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 236, in setup_ui
    self.account_store.populate_tree()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 162, in populate_tree
    icon = pbfile(resources.icon("gtk-find", use_theme=False))
TypeError: pixbuf_new_from_file() argument 1 must be string, not None

[Ms_Angel_D (mrsangeld)]

I'm on Kubuntu Karmic and I get this error

angel@angel-desktop:~$ gwibber
WARNING:root:desktopcouch is not available. . falling back to gconf

** (gwibber:6450): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (gwibber:6450): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum'

** (gwibber:6450): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 57, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 105, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 188, in __init__
    self.setup_ui()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 238, in setup_ui
    self.account_store.populate_tree()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 157, in populate_tree
    icon = pbfile(icf)
TypeError: pixbuf_new_from_file() argument 1 must be string, not None

[Omer Akram (om26er)]

Its been a while since this bug was reported and also the last activity was a while ago. Does any one still face this issue? If so can they please try to install the daily build of gwibber. (Although its a dependency problem but still). https://launchpad.net/~gwibber-daily/+archive/ppa

[Omer Akram (om26er)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!