Bug 1108782

Summary: [abrt] pitivi: render.py:291:_closeButtonClickedCb:GError: GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.NotificationDaemonErrorQuark.Code100: 0 is not a valid notification ID
Product: [Fedora] Fedora Reporter: dir2006 <dir2006>
Component: pitiviAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: elad, gwync, hicham.haouari, otte
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/46ca9e8fdbcd666875c4c29727c0e49c0d132a15
Whiteboard: abrt_hash:87ad8b4cb536eefb27a7a46431b08d71f3ae7f79
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:05:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description dir2006 2014-06-12 14:43:50 UTC
Version-Release number of selected component:
pitivi-0.93-4.fc20

Additional info:
reporter:       libreport-2.2.2
cmdline:        python2 /usr/bin/pitivi
executable:     /usr/bin/pitivi
kernel:         3.14.5-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
render.py:291:_closeButtonClickedCb:GError: GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.NotificationDaemonErrorQuark.Code100: 0 is not a valid notification ID

Traceback (most recent call last):
  File "/usr/share/pitivi/python/pitivi/render.py", line 291, in _closeButtonClickedCb
    self.main_render_dialog.notification.close()
GError: GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.NotificationDaemonErrorQuark.Code100: 0 is not a valid notification ID

Local variables in innermost frame:
unused_button: <Button object at 0x5380aa0 (GtkButton at 0x7f9628009630)>
self: <pitivi.render.RenderingProgressDialog object at 0x50f1250>

Comment 1 dir2006 2014-06-12 14:43:56 UTC
Created attachment 908179 [details]
File: backtrace

Comment 2 dir2006 2014-06-12 14:43:59 UTC
Created attachment 908181 [details]
File: environ

Comment 3 Fedora End Of Life 2015-05-29 12:05:51 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-06-29 21:05:27 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.