Bug 1034037

Summary: [abrt] alacarte-3.6.1-1.fc18: types.py:47:function:GError: 不支持指定位置
Product: [Fedora] Fedora Reporter: chopin xiao <hark110>
Component: alacarteAssignee: Jasper St. Pierre <jstpierr>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jpmahowald, jstpierr, mclasen, sindrepb
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bb5a5eef63c524078efb8800e881a9326b88bf45
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:33:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description chopin xiao 2013-11-25 06:37:51 UTC
Description of problem:
When edit main menu of application, click help and the error happend

Version-Release number of selected component:
alacarte-3.6.1-1.fc18

Additional info:
reporter:       libreport-2.1.7
cmdline:        /usr/bin/python2.7 -OOt /usr/bin/alacarte
dso_list:       pygobject3-base-3.4.2-6.fc18.x86_64
executable:     /usr/bin/alacarte
kernel:         3.11.4-101.fc18.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
types.py:47:function:GError: 不支持指定位置

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 439, in on_help_button_clicked
    Gtk.show_uri(Gdk.Screen.get_default(), "ghelp:user-guide#menu-editor", Gtk.get_current_event_time())
  File "/usr/lib64/python2.7/site-packages/gi/types.py", line 47, in function
    return info.invoke(*args, **kwargs)
GError: 不支持指定位置

Local variables in innermost frame:
info: <gi.FunctionInfo object (show_uri) at 0x0x23ae488>
args: (<gtk.gdk.X11Screen object at 0x1e52460 (GdkX11Screen at 0x1baa0c0)>, 'ghelp:user-guide#menu-editor', 16608219L)
kwargs: {}

Comment 1 chopin xiao 2013-11-25 06:37:57 UTC
Created attachment 828523 [details]
File: backtrace

Comment 2 chopin xiao 2013-11-25 06:38:00 UTC
Created attachment 828524 [details]
File: environ

Comment 3 Fedora End Of Life 2013-12-21 14:47:02 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 22:33:50 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.