Bug 15570 - Printer config raises exception: ImportError: cannot import name 'ResponseError'
Summary: Printer config raises exception: ImportError: cannot import name 'ResponseError'
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-25 22:19 CET by Marc Krämer
Modified: 2015-03-28 16:39 CET (History)
2 users (show)

See Also:
Source RPM: system-config-printer, python3-requests
CVE:
Status comment:


Attachments

Description Marc Krämer 2015-03-25 22:19:08 CET
starting drakconf from command line & calling Printer Installation gives this traceback:

"/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 831.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 831.
"/usr/sbin/msecgui" is not executable [Security Level] at /usr/libexec/drakconf line 831.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 831.
openjdk version "1.8.0_40"
OpenJDK Runtime Environment (build 1.8.0_40-b25)
OpenJDK 64-Bit Server VM (build 25.40-b25, mixed mode)
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 27, in <module>
    import sys, os, time, re, mga_printer_custom
  File "/usr/share/system-config-printer/mga_printer_custom.py", line 6, in <module>
    import cups, cupshelpers
  File "/usr/lib/python3.4/site-packages/cupshelpers/__init__.py", line 60, in <module>
    from . import openprinting
  File "/usr/lib/python3.4/site-packages/cupshelpers/openprinting.py", line 22, in <module>
    import requests, urllib.request, urllib.parse, urllib.error, platform, threading, tempfile, traceback
  File "/usr/lib/python3.4/site-packages/requests/__init__.py", line 60, in <module>
    from .api import request, get, head, post, patch, put, delete, options
  File "/usr/lib/python3.4/site-packages/requests/api.py", line 14, in <module>
    from . import sessions
  File "/usr/lib/python3.4/site-packages/requests/sessions.py", line 27, in <module>
    from .adapters import HTTPAdapter
  File "/usr/lib/python3.4/site-packages/requests/adapters.py", line 29, in <module>
    from .packages.urllib3.exceptions import ResponseError
ImportError: cannot import name 'ResponseError'


Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2015-03-26 09:24:21 CET
Wrong package

CC: (none) => geiger.david68210, luigiwalser, thierry.vignaud
Summary: Config of printer raises exeception => Printer config raises exception: ImportError: cannot import name 'ResponseError'
Source RPM: drakconf-12.57-1.mga5.src.rpm => system-config-printer, python3-requests

Comment 2 David Walser 2015-03-26 12:54:47 CET
Please check the version of python3-requests that you have installed.  If it is 2.6.0, run "urpmi --downgrade python3-requests" to fix it (it should be 2.3.0) and then close this bug.

CC: luigiwalser => (none)

Comment 3 Thierry Vignaud 2015-03-26 13:05:05 CET
We could add a conflict to system-config-printer against python3-requests > 2.4.0
Comment 4 David Walser 2015-03-26 17:51:48 CET
That would be inappropriate.  s-c-p will work fine with the updated requests, it's just that urllib3 at the least also needs to be updated.
Comment 5 Marc Krämer 2015-03-26 22:43:08 CET
downgrade worked, version 2.6 was installed on regular updates.
Comment 6 Thierry Vignaud 2015-03-27 06:05:56 CET
to be added to RC errata, not to final release errata?

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 7 David Walser 2015-03-28 16:39:21 CET
It certainly shouldn't be in final release errata, as it was a very time-limited Cauldron-only issue.  The 2.6.0 was only available for maybe a day in Cauldron, and I think it was also on a non-public QA-only ISO.  It can be in the RC errata if you think it's appropriate, but it shouldn't affect many people.

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