← Back to team overview

gwibber-bugs team mailing list archive

[Bug 668150] Re: gwibber dependent on network-manager connection, cannot use wvdial (text input disabled)

 

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.

** Attachment added: "patch to comment out connection-state awareness"
   https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/668150/+attachment/1864392/+files/bug-668150-patch.txt

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/668150

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

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  Confirmed

Bug description:
  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'