Public bug reported:

Observed behaviour: the Ubuntu installer slows down to a crawl at the
stage of restoring previously installed packages.

The following message is displayed in the installers terminal view:
Failed to create sharedmemoryfile /WK2SharedMemory.XXXXXXXX: Permission
denied

Steps to reproduce:

1. Have an already installed version of 14.04 or 16.04
2. Start the Ubuntu 16.04(.1) installer from desktop installation media
3. Choose to do "something else" instead of installing over or alongside and 
choose the previous root partition for the new root partition but _don't_ 
format it.
4. Continue with the installation as usual.
5. Open a terminal and run `top` to monitor the CPU load, at the stage of 
"restoring previously installed packages" a WebKitWebProcess shows up consuming 
almost 100% of CPU resources. After Killing it with `killall WebKitWebProcess` 
the installation continues.

This has been reproducible on al laptop for 14.04 and 16.04 as well as
VirtualBox VMs with 14.04 and 16.04 preinstalled. Installing a package
like lyx (pulls in tex dependencies and many megabytes of data) might
help triggering this bug but I also encountered it without lyx
preinstalled during tests.

Bugs found with related error messages:
https://bugs.webkit.org/show_bug.cgi?id=134892

Users on AskUbuntu reporting this issue:
http://askubuntu.com/q/761930/40581

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1607779/+attachment/4709435/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607779

Title:
  Failed to create sharedmemoryfile /WK2SharedMemory.XXXXXXXX:
  Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1607779/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to