Bug 571352 - [abrt] crash in mumbles-0.4-12.fc12: MumblesNotify.py:280:expose:TypeError: Required argument 'cr' (pos 1) not found
Summary: [abrt] crash in mumbles-0.4-12.fc12: MumblesNotify.py:280:expose:TypeError: R...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mumbles
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: John Anderson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:270136c5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-08 09:13 UTC by Tim Waugh
Modified: 2012-08-16 18:32 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:32:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.03 KB, text/plain)
2010-03-08 09:13 UTC, Tim Waugh
no flags Details
mumbles patch (1.01 KB, text/plain)
2010-10-19 20:06 UTC, Chris
no flags Details

Description Tim Waugh 2010-03-08 09:13:38 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/bin/mumbles
component: mumbles
executable: /usr/bin/mumbles
kernel: 2.6.33-1.fc13.x86_64
package: mumbles-0.4-12.fc12
reason: MumblesNotify.py:280:expose:TypeError: Required argument 'cr' (pos 1) not found
release: Fedora release 13 (Rawhide)

backtrace
-----
MumblesNotify.py:280:expose:TypeError: Required argument 'cr' (pos 1) not found

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/mumbles/MumblesNotify.py", line 280, in expose
    cr.reset_clip()
TypeError: Required argument 'cr' (pos 1) not found

Local variables in innermost frame:
default_background_image: '/usr/share/mumbles/themes/default/bground.png'
background_image: '/usr/share/mumbles/themes/human/bground.png'
title: u'NickServ'
image: '/usr/share/mumbles/plugins/icons/pidgin.png'
pixbuf: <gtk.gdk.Pixbuf object at 0x1d21e60 (GdkPixbuf at 0x1ea4a80)>
widget: <gtk.Window object at 0x1d21eb0 (GtkWindow at 0x1b147c0)>
self: <MumblesNotify.MumblesNotify object at 0x1d971d0>
plugin_image: <gtk.gdk.Pixbuf object at 0x1dcb2d0 (GdkPixbuf at 0x1ea4ad0)>
cr: <gtk.gdk.CairoContext object at 0x7f4a6d477390>
message: u'(notice) This nickname is registered. Please choose a different nickname, or identify via  /msg NickServ identify <password> .'
event: <gtk.gdk.Event at 0x7f4a6d4f3da0: GDK_EXPOSE area=[0, 0, 250, 80]>

Comment 1 Tim Waugh 2010-03-08 09:13:41 UTC
Created attachment 398489 [details]
File: backtrace

Comment 2 Bug Zapper 2010-07-30 11:00:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Chris 2010-10-19 20:06:09 UTC
Created attachment 454430 [details]
mumbles patch

I was running into the same issue with mumbles-0.4-12.fc12.noarch giving this error when I use mumbles-send :

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/mumbles/MumblesNotify.py", line 281, in expose
    cr.reset_clip()
TypeError: Required argument 'cr' (pos 1) not found


I don't know anything about python or cairo but from looking at another posting on the web I made the changes in the patch and now mumbles appears to be working properly.

Comment 4 Jerry Lumpkins 2011-01-21 18:48:04 UTC
Package: mumbles-0.4-13.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Sorry, I didn't even notice it had crashed.
2.
3.

Comment 5 David R. Fischer 2011-02-18 02:31:42 UTC
Package: mumbles-0.4-13.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Running rhythmbox

Comment 6 David R. Fischer 2011-04-28 01:00:00 UTC
Package: mumbles-0.4-13.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
playing a song in Rhythmbox 0.13.3

Comment 7 Amrit 2012-07-30 07:40:48 UTC
How to solve this issue please help me , i couldn't find any solution

Comment 8 Fedora End Of Life 2012-08-16 18:32:31 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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


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