Bug 1133749 - [abrt] yum-cron: arch.py:6:<module>:ValueError: bad marshal data (unknown type code)
Summary: [abrt] yum-cron: arch.py:6:<module>:ValueError: bad marshal data (unknown typ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:9003f012a6d74a8666f6457d1c2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-26 04:02 UTC by Jim
Modified: 2014-10-06 12:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-06 12:44:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (6.68 KB, text/plain)
2014-08-26 04:03 UTC, Jim 		no flags Details
File: environ (213 bytes, text/plain)
2014-08-26 04:03 UTC, Jim 		no flags Details
View All

Description Jim 2014-08-26 04:02:58 UTC 
Version-Release number of selected component:
yum-cron-3.4.3-152.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        /usr/bin/python -tt /usr/sbin/yum-cron /etc/yum/yum-cron-hourly.conf
dso_list:       yum-3.4.3-152.fc20.noarch
executable:     /usr/sbin/yum-cron
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
#1 <module> in /usr/lib/python2.7/site-packages/rpmUtils/arch.py:6
#2 <module> in /usr/lib/python2.7/site-packages/yum/rpmsack.py:24
#3 <module> in /usr/lib/python2.7/site-packages/yum/__init__.py:62
#4 <module> in /usr/sbin/yum-cron:7
Comment 1 Jim 2014-08-26 04:03:06 UTC 
Created attachment 930711 [details]
File: backtrace
Comment 2 Jim 2014-08-26 04:03:07 UTC 
Created attachment 930712 [details]
File: environ
Comment 3 Valentina Mukhamedzhanova 2014-10-06 12:44:49 UTC 
The error messages occurs when trying to import a python standard library module, this has nothing to do with yum.
Note You need to log in before you can comment on or make changes to this bug.