12.10 to 13.04 Failed, Now Get "An upgrade from raring to quantal is not supported with this tool"

Bug #1165281 reported by Dac Chartrand
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Lenovo X220, Ubuntu 12.10

The screen went black during the upgrade to 13.04.

The last thing I experienced was a black screen with a really loud fan. CTRL+ALT+F2 did nothing. The last thing I saw was "Unpacking Deja Vu TTF" then poof, blackness.

I had to reboot. I landed in what appears to be the old system.

When I try running `update-manager -d` again, I get the option to Partial Upgrade. I click it.

It says: "An upgrade from raring to quantal is not supported with this tool"

If I instead click Continue, I get a list with a thousand packages. Some of which aren't selected. I haven't dared to go beyond that.

What just happened? How do I fix things?

Regards,

Tags: bot-comment
Revision history for this message
Dac Chartrand (conner-bw) wrote :
Download full text (4.6 KiB)

In bug #999013, someone said they fixed a similar problem by running `sudo apt-get dist-upgrade` at the prompt.

I tried. It didn't work. I got this:

-=-=-

... snip ....

Unpacking libaudit1:amd64 (from .../libaudit1_1%3a2.2.2-1ubuntu4_amd64.deb) ...
Setting up libaudit1:amd64 (1:2.2.2-1ubuntu4) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
(Reading database ... 564346 files and directories currently installed.)
Preparing to replace debconf 1.5.46ubuntu1 (using .../debconf_1.5.49ubuntu1_all.deb) ...
Traceback (most recent call last):
  File "/usr/lib/python2.7/site.py", line 563, in <module>
    main()
  File "/usr/lib/python2.7/site.py", line 545, in main
    known_paths = addusersitepackages(known_paths)
  File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
    user_site = getusersitepackages()
  File "/usr/lib/python2.7/site.py", line 247, in getusersitepackages
    user_base = getuserbase() # this will also set USER_BASE
  File "/usr/lib/python2.7/site.py", line 237, in getuserbase
    USER_BASE = get_config_var('userbase')
  File "/usr/lib/python2.7/sysconfig.py", line 578, in get_config_var
    return get_config_vars().get(name)
  File "/usr/lib/python2.7/sysconfig.py", line 505, in get_config_vars
    import re
  File "/usr/lib/python2.7/re.py", line 105, in <module>
    import sre_compile
  File "/usr/lib/python2.7/sre_compile.py", line 14, in <module>
    import sre_parse
  File "/usr/lib/python2.7/sre_parse.py", line 17, in <module>
    from sre_constants import *
  File "/usr/lib/python2.7/sre_constants.py", line 18, in <module>
    from _sre import MAXREPEAT
ImportError: cannot import name MAXREPEAT
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/lib/python2.7/site.py", line 563, in <module>
    main()
  File "/usr/lib/python2.7/site.py", line 545, in main
    known_paths = addusersitepackages(known_paths)
  File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
    user_site = getusersitepackages()
  File "/usr/lib/python2.7/site.py", line 247, in getusersitepackages
    user_base = getuserbase() # this will also set USER_BASE
  File "/usr/lib/python2.7/site.py", line 237, in getuserbase
    USER_BASE = get_config_var('userbase')
  File "/usr/lib/python2.7/sysconfig.py", line 578, in get_config_var
    return get_config_vars().get(name)
  File "/usr/lib/python2.7/sysconfig.py", line 505, in get_config_vars
    import re
  File "/usr/lib/python2.7/re.py", line 105, in <module>
    import sre_compile
  File "/usr/lib/python2.7/sre_compile.py", line 14, in <module>
    import sre_parse
  File "/usr/lib/python2.7/sre_parse.py", line 17, in <module>
    from sre_constants import *
  File "/usr/lib/python2.7/sre_constants.py", line 18, in <module>
    from _sre import MAXREPEAT
ImportError: cannot import name MAXREPEAT
dpkg: error processing /var/cache/apt/archives/debconf_1.5.49ubuntu1_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
No apport report written because MaxReports is reached already
    ...

Read more...

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1165281/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → update-manager (Ubuntu)
Revision history for this message
Dac Chartrand (conner-bw) wrote :
Revision history for this message
Dac Chartrand (conner-bw) wrote :

Installation completed with a workaround that I will document below.

This bug can be summarized in two parts.

-=-=-

#1) GUI Installer crashed with black screen at start of unpacking phase. Had to reboot.

Unsolved mystery.

-=-=-

#2) Running `sudo apt-get dist-upgrade` gave an error. Workaround provided by link in comment #3.

$ sudo nano -w /usr/lib/python2.7/sre_constants.py

Look for:
  from _sre import MAXREPEAT

Replace with:
  MAXREPEAT = 65535
  #from _sre import MAXREPEAT

$ sudo nano -w /usr/lib/python2.7/sre_constants.py
$ nano -w /usr/lib/python2.7/sre_parse.py

Look for:
 from _sre import MAXREPEAT

Replace with:
 #from _sre import MAXREPEAT

-=-=-

Hope this helps someone.

Revision history for this message
Dac Chartrand (conner-bw) wrote :

Argh. Typos above. Files are:

/usr/lib/python2.7/sre_constants.py
/usr/lib/python2.7/sre_parse.py
/usr/lib/python2.7/sre_compile.py

Follor the link in comment #3 for details.

affects: update-manager (Ubuntu) → ubuntu-release-upgrader (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

This probably due to lsb_release returning raring, since that part of the upgrade completed, and the Source From in DistUpgrade.cfg being "quantal". I think the only thing to do here is to return a better error message if release == self.toDist indicating how one may resolve the situation.

From DistUpgradeController.py:

    def prepare(self):
        """ initial cache opening, sanity checking, network checking """
        # first check if that is a good upgrade
        self.release = release = subprocess.Popen(["lsb_release","-c","-s"],
                                   stdout=subprocess.PIPE,
                                   universal_newlines=True).communicate()[0].strip()
        logging.debug("lsb-release: '%s'" % release)
        if not (release == self.fromDist or release == self.toDist):
            logging.error("Bad upgrade: '%s' != '%s' " % (release, self.fromDist))
            self._view.error(_("Can not upgrade"),
                             _("An upgrade from '%s' to '%s' is not "
                               "supported with this tool." % (release, self.toDist)))
            sys.exit(1)

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Triaged
importance: Undecided → Low
sindhu (sindhu-h)
Changed in ubuntu-release-upgrader (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.