gwibber dependent on network-manager connection, cannot use wvdial (text input disabled)

[ch3mi0n]

Binary package hint: gwibber

$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

$ uname -srvmo
Linux 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

$ apt-cache policy gwibber
gwibber:
  Installed: 2.32.0.1-0ubuntu1
  Candidate: 2.32.0.1-0ubuntu1
  Version table:
 *** 2.32.0.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

When trying to post anything via any registered service, the text input area remains "disabled". It is visible, with "140" in the lower-right corner, but will not accept any input.

More information: this is a brand-new/fresh install of Ubuntu 10.10, not an upgrade. It has never worked. Accounts that have been set up are: digg, twitter, ping.fm, buzz, facebook, identi.ca. Digg was removed when the problem was first discovered, since it was the only service that doesn't support "sending" (I thought maybe digg was the culprit). No change after removing digg from my accounts. All the remaining accounts are authorized and connected properly and are receiving messages (except ping.fm, which I only have configured for sending on the ping.fm site, and buzz). I ran gwibber with the (-d) debug flag, but this is the only output it produced, even thoughout my attempts at entering text in the textbox:

$ gwibber -d

** (gwibber:3566): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:3566): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:3566): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'

[Victor Vargas (kamus)]

is this issue still affecting you with latest release of gwibber 2.32.2-0ubuntu2?

[ch3mi0n (ch3mi0n)]

Yes, it is. I thought to update the ticket after the update, but I didn't have the time. The issue remains the same even after the update.

Please let me know if there is any additional information I can provide to help resolve this.

[Omer Akram (om26er)]

which connection manager are you using to connect to the internet?

[ch3mi0n (ch3mi0n)]

You might be on to something there.

Actually, I use a T-Mobile WebConnect Rocket 2.0 which isn't fully supported
under Linux yet. I am able to get online with it, however, by using a custom
usb modeswitch and wvdial. I can give you more details on that later, if you
need (I'm not near that computer at the moment). Pretty much everything
recognizes the connection when it's up except for Firefox, which I have to
manually switch out of offline mode after connecting. So, it's entirely
possible (now that you mention it) that gwibber is thinking it doesn't have
a connection.

Let me know if there's anything you need from me, or want me to try anything
special to get more information.

Thanks.
On Jan 6, 2011 8:45 AM, "Omer Akram" <email address hidden> wrote:

[Per Ångström (autark)]

I'm having the same problem, when connected to mobile broadband via wvdial. It works when connected via network manager.

[Per Ångström (autark)]

My gwibber version is 2.32.2-0ubuntu2.

[Per Ångström (autark)]

I have made a rudimentary patch to the maverick-updates branch which comments out the connection-state queries and disregards changes in the connection state. With this patch I can now use Gwibber with a wvdial connection.

The downside is that there does not seem to be any error checking in the code, so if you try to send when you really don't have a connection you won't get any error indication and your message will be lost. I have not tried to address that shortcoming.