Bug 1243787 - Crash on dnf update
Summary: Crash on dnf update
Keywords:
Status: CLOSED DUPLICATE of bug 1240115
Alias: None
Product: Fedora
Classification: Fedora
Component: tracer
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Kadlčík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-16 10:05 UTC by Patrick O'Callaghan
Modified: 2015-07-20 08:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-07-20 08:47:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Patrick O'Callaghan 2015-07-16 10:05:48 UTC
Description of problem:
The tracer plugin for dnf crashed on running 'dnf update'

Version-Release number of selected component (if applicable):
tracer-0.5.8-1.fc22.noarch

How reproducible:
Seems to be 100% repeatable

Steps to Reproduce:
1. run 'dnf update' (as root)
2. dnf appears to run correctly
3. tracer reports a crash

Actual results:
Tracer:
  Program 'tracer' crashed with following error:

/usr/lib/python2.7/site-packages/bs4/__init__.py:166: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("lxml"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.

To get rid of this warning, change this:

 BeautifulSoup([your markup])

to this:

 BeautifulSoup([your markup], "lxml")

  markup_type=markup_type))


Expected results:
Normal tracer output

Additional info:
First time this has happened. I run dnf update every day, so far without problems with tracer. As of today, repeated runs give the same result.

Comment 1 Kevin Fenzi 2015-07-16 23:45:40 UTC
Might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1240115 ?

Comment 2 Jakub Kadlčík 2015-07-20 08:47:43 UTC
Hello Patrick,
thank you for the feedback.

As Kevin pointed out ^^, it is a duplicate of 1240115. I am closing this issue and asking you to watch the progress in the referenced one.

*** This bug has been marked as a duplicate of bug 1240115 ***


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