Bug 576792 - [abrt] crash in gwibber-1:2.29.92.1-1.fc12: __init__.py:715:connect:error: [Errno 111] Connection refused
Summary: [abrt] crash in gwibber-1:2.29.92.1-1.fc12: __init__.py:715:connect:error: [E...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9b1ffd89
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-25 08:00 UTC by Matthias Runge
Modified: 2010-08-20 02:11 UTC (History)
12 users (show)

Fixed In Version: gwibber-2.31.4-1.fc12
Clone Of:
Environment:
Last Closed: 2010-08-20 01:56:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (2.24 KB, text/plain)
2010-03-25 08:00 UTC, Matthias Runge
no flags Details

Description Matthias Runge 2010-03-25 08:00:30 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gwibber
component: gwibber
executable: /usr/bin/gwibber
kernel: 2.6.32.10-90.fc12.i686.PAE
package: gwibber-1:2.29.92.1-1.fc12
reason: __init__.py:715:connect:error: [Errno 111] Connection refused
release: Fedora release 12 (Constantine)

comment
-----
Start gwibber via gnome menu
Failed connection may be a connection to twitter. (I do not use any other account)

How to reproduce
-----
1. start gwibber
2. crash
3.

Comment 1 Matthias Runge 2010-03-25 08:00:32 UTC
Created attachment 402498 [details]
File: backtrace

Comment 2 Matthias Runge 2010-03-25 08:05:15 UTC
Hmm, machine had a little load. Maybe a timing problem?

Comment 3 Tom "spot" Callaway 2010-03-25 11:34:51 UTC
Seems like a good guess, looks like it couldn't get to the couchdb. Is this reproducable?

Comment 4 Matthias Runge 2010-03-25 12:03:30 UTC
Sadly, I'm unable to reproduce this. I tend to close this bug report and to ignore it.

Comment 5 Matthias Runge 2010-03-29 05:54:23 UTC

How to reproduce
-----
1. start gwibber
2. let it run a long time
3. crash


Comment
-----
I don't know what really happened. Started gwibber and came back after a weekend and gwibber has crashed.

Comment 6 Tom "spot" Callaway 2010-03-29 14:32:58 UTC
Hm. Was there any output at the console?

Comment 7 Matthias Runge 2010-03-30 05:50:11 UTC
no console output, gwibber was startet via gnome-menu.

Machine was in use by boinc over the weekend. I'm not sure, if this matters. 

What else could I do, to reproduce this error?

Comment 8 Matthias Runge 2010-03-30 07:17:23 UTC
Just more additional info:
[mrunge@mrungexp ~]$ gwibber

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

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

** (gwibber:4346): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
/usr/lib/python2.6/site-packages/httplib2/__init__.py:29: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
/usr/lib/python2.6/site-packages/httplib2/__init__.py:44: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
Removing stale, deceptive pid file.
Apache CouchDB has started, time to relax.
Browse your desktop CouchDB at file:///home/mrunge/.local/share/desktop-couch/couchdb.html
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files


Looks pretty ugly to me.

Comment 9 Tom "spot" Callaway 2010-03-30 13:34:58 UTC
Believe it or not, that's normal output. It looks like the application did die as you reported (Removing stale, deceptive pid file.), but it started up again cleanly. The "ERROR" lines are unimplemented feature functionality, not real program faults.

If it crashes again, please give me the console output.

Comment 10 Justin O'Brien 2010-04-22 05:21:05 UTC
Package: gwibber-1:2.30.0.1-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. minimize app
2. enjoy abrt
3.

Comment 11 Jesse Kahtava 2010-05-19 13:57:16 UTC
Package: gwibber-1:2.29.92.1-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


Comment
-----
This bug is related to bug #542823:

https://bugzilla.redhat.com/show_bug.cgi?id=542823

Comment 12 Matthew Booth 2010-05-19 22:34:55 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


Comment
-----
Gwibber crashed on waking from hibernate

Comment 13 Justin O'Brien 2010-05-28 00:26:12 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.  
2.
3.


Comment
-----
i had two streams open (home and replies) and two accounts (twitter and identica)

Comment 14 Agung Nugroho K 2010-06-03 09:33:18 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Please help
2.
3.

Comment 15 eric 2010-06-20 14:11:13 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Start the program.
2.
3.

Comment 16 Justin O'Brien 2010-06-23 13:26:52 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. opened from menu after login
2.
3.

Comment 17 Guido 2010-06-26 02:13:37 UTC
Package: gwibber-1:2.30.0.1-6.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Restart from hibernate whit gwibber open

Comment 18 Fedora Update System 2010-07-26 19:22:45 UTC
gwibber-2.31.2-7.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12

Comment 19 Fedora Update System 2010-07-26 19:30:08 UTC
gwibber-2.31.2-7.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13

Comment 20 Fedora Update System 2010-07-27 02:26:32 UTC
gwibber-2.31.2-7.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13

Comment 21 Fedora Update System 2010-07-27 02:31:48 UTC
gwibber-2.31.2-7.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12

Comment 22 Fedora Update System 2010-08-09 20:27:29 UTC
gwibber-2.31.4-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12

Comment 23 Fedora Update System 2010-08-09 20:32:22 UTC
gwibber-2.31.4-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13

Comment 24 Fedora Update System 2010-08-10 21:29:23 UTC
gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12

Comment 25 Fedora Update System 2010-08-10 21:34:58 UTC
gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13

Comment 26 Fedora Update System 2010-08-20 01:51:58 UTC
gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 27 Fedora Update System 2010-08-20 02:06:32 UTC
gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.