Bug 1581743

Summary: [abrt] telepathy-gabble: syntax(): invalid syntax (telepathy-gabble-xmpp-console, line 316)
Product: [Fedora] Fedora Reporter: Saurabh Pradhan <pradhanphy>
Component: telepathy-gabbleAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: bdpepple, john.j5live, sander, tomeu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7faa35ee252df8476f9ba65a0e8ef8dedd283b5f
Whiteboard: abrt_hash:d48362b1cc2490dd5abd762f43f87286ddc73ccb;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 21:43:06 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: cgroup
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Saurabh Pradhan 2018-05-23 14:34:58 UTC
Description of problem:
Tried to run /usr/bin/telepathy-gabble-xmpp-console

Version-Release number of selected component:
telepathy-gabble-0.18.4-5.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        /usr/bin/python3 /usr/bin/telepathy-gabble-xmpp-console
crash_function: syntax
exception_type: SyntaxError
executable:     /usr/bin/telepathy-gabble-xmpp-console
kernel:         4.16.9-200.fc27.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
invalid syntax (telepathy-gabble-xmpp-console, line 316)

  File "/usr/bin/telepathy-gabble-xmpp-console", line 316
    except Exception, e:
                    ^
SyntaxError: invalid syntax

Potential duplicate: bug 1259808

Comment 1 Saurabh Pradhan 2018-05-23 14:35:06 UTC
Created attachment 1440641 [details]
File: backtrace

Comment 2 Saurabh Pradhan 2018-05-23 14:35:07 UTC
Created attachment 1440642 [details]
File: cgroup

Comment 3 Saurabh Pradhan 2018-05-23 14:35:09 UTC
Created attachment 1440643 [details]
File: cpuinfo

Comment 4 Saurabh Pradhan 2018-05-23 14:35:10 UTC
Created attachment 1440644 [details]
File: environ

Comment 5 Saurabh Pradhan 2018-05-23 14:35:12 UTC
Created attachment 1440645 [details]
File: mountinfo

Comment 6 Saurabh Pradhan 2018-05-23 14:35:13 UTC
Created attachment 1440646 [details]
File: namespaces

Comment 7 Saurabh Pradhan 2018-05-23 14:35:14 UTC
Created attachment 1440647 [details]
File: open_fds

Comment 8 Ben Cotton 2018-11-27 15:37:38 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 9 Ben Cotton 2018-11-30 21:43:06 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.