abrt version: 1.1.13 architecture: i686 component: pidgin executable: /usr/bin/purple-url-handler kernel: 2.6.33.6-147.2.4.fc13.i686.PAE package: libpurple-2.7.3-1.fc13 reason: warnings.py:29:_show_warning:AttributeError: 'NoneType' object has no attribute 'write' release: Fedora release 13 (Goddard) time: 1282158865 uid: 500 backtrace ----- warnings.py:29:_show_warning:AttributeError: 'NoneType' object has no attribute 'write' Traceback (most recent call last): File "/usr/bin/purple-url-handler", line 395, in <module> main() File "/usr/bin/purple-url-handler", line 391, in main print "Error: %s" % (e.message) File "/usr/lib/python2.6/warnings.py", line 29, in _show_warning file.write(formatwarning(message, category, filename, lineno, line)) AttributeError: 'NoneType' object has no attribute 'write' Local variables in innermost frame: category: <type 'exceptions.DeprecationWarning'> filename: '/usr/bin/purple-url-handler' lineno: 391 file: None line: None message: DeprecationWarning('BaseException.message has been deprecated as of Python 2.6',) How to reproduce ----- 1. При открытии ссылки irc://utf.rusnet.org.ru:7770/lurkmore из браузера Google Chrome 2. 3.
Created an attachment (id=439473) File: backtrace
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open firefox 2. Go to http://fedoraproject.org/wiki/Communicate#IRC 3. Click link #fedora-es 4. Choose purplr-url-handler on the Launch Application menu and press OK
Package: libpurple-2.7.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Clicked the IRC-link (irc://irc.freenode.net/fedora-test-day) near the top of https://fedoraproject.org/wiki/Test_Day:2010-09-28_Nouveau
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.open an irc channel 2.click the link text in the channel. It is best to click a link of irc protocal to open another irc channel It won't be reproduced if you click a http protocal or something else except irc protocal 3.It would crash as you expected. Comment ----- It crashed when I was trying to open another irc channel by clicking a link in one channel's topic message.
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.open an irc channel 2.click the link text in the channel. It is best to click a link of irc protocal to open another irc channel It won't be reproduced if you click a http protocal or something else except irc protocal 3.It would crash as you expected. For example: 1.open #moblin channel of freenode.net 2.click the link text in the channel's topic:"irc://irc.freenode.net/meego" 3.It would generate this bug. Comment ----- It crashed when I was trying to open another irc channel by clicking a link in one channel's topic message.
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open http://irc.mozilla.org/ in Firefox 2. Click on Firefox project channel, irc://irc.mozilla.org/firefox 3.
Package: libpurple-2.7.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Clicked on the link irc://irc.mozilla.org/thunderbird in Firefox 2. Selected "purple-url-handler"
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Package: libpurple-2.7.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Go to some site, for example http://www.xams.org/pages/support/support.php 2. Click on #xams-devel link 3. Choose "Open with purple-url-handler"
Package: libpurple-2.7.3-1.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Tried to open firefox channel from firefox 2. 3. Comment ----- http://irc.mozilla.org/
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Visit a page with an IRC link in Firefox (e.g. <http://www.transmissionbt.com/>). 2. Click on the link. 3. Tell Firefox to open the link with purple-url-handler.
Package: libpurple-2.7.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I just log in into http://www.broffice.org/reuniao_abril_irc 2. And than I click on the follow link on my web browser Google Chromium irc://irc.freenode.net/broffice.org 3. So, I got the follow bug reporting in purple-url-handler
Package: libpurple-2.7.4-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. navigate with firefox to http://matchbox-project.org/get_involved.html 2. click on IRC link 3. chose to upen with purple-url-handler
Package: libpurple-2.7.5-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Adding a IRC to pidgin 2. 3.
Package: libpurple-2.7.9-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Access URI irc://server/room from Google Chrome 9.0.597.98 2. This invoked xdg-open (??) 3. Received this crash notification.
Package: libpurple-2.7.10-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Run pidgin on Fed 13 2. Attempt to open a URI that calls xdg-open "irc://server/#channel" or any uri that invokes purple-url-handler 3. You will get this ABRT report Comment ----- I've been told by Pidgin Dev that this seems to be an error being caused by Python reporting that their DBus call is deprecated. This is the call that is producing the dbus error: purple-remote "PurpleAccountGetProtocolID(5513)" Traceback (most recent call last): File "/usr/bin/purple-remote", line 240, in <module> output = execute(arg) File "/usr/bin/purple-remote", line 208, in execute return purple.__getattr__(name)(*fargs) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleAccountGetProtocolID" with signature "i" on interface "im.pidgin.purple.PurpleInterface" doesn't exist However, when called in python, the ABRT reported is in this bug report.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Package: libpurple-2.7.11-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. irc://example.com/thisthat (click on it) 2. see the crash 3.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.