desktop folderview needs to be added on first boot on oem installs

[lordievader]

On Kubuntu Vivid Alpha2 i386, after a successful oem install, has no oem-config utility anywhere.
There is no icon on the desktop, or in the menu's, to launch the final setup program.
Thus effectively there is no way to complete the installation.

Ubuntu: Vivid Vervet (15.04)
Arch: i386
Ubiquity: 2.21.5

Bug 1444980 is about oem-config-kde not being installed.

This bug is about folderview needing to be set up to show to the user to run oem-config

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1413521

[Mathieu Trudel-Lapierre (cyphermox)]

Did the installer ask you for an OEM identifier at the beginning of the installation? I've seen some cases already where it looks like you're doing an OEM installation, but there are only few differences between both OEM and a standard install, so the resulting installed system does not include oem-config.

Ways to notice are the OEM identifier that is requested early in the installation process, and the fact that the installer will ask for a generic username and password rather than pre-filling prompts with the 'oem' username, for example.

If you could attach /var/log/installer/syslog from the resulting install (or /var/log/syslog from the installation process), this could help in identifying where things went wrong.

Thanks!

[lordievader (oliviervdtoorn)]

I just did an install of Vivid Beta1. The same problem exists. However this time there is a "Prepare for shipping" in the menu.
Clicking this results in the asking of the password and further nothing.

Opening the Konsole and running "oem-config-prepare" gives as output that it will run on the next boot. However after a reboot the oem user is logged in an no prepare for shipping wizard is shown.

[Marcin Sągol (soee)]

I can confirm this bug for amd64 images.

[Mathieu Trudel-Lapierre (cyphermox)]

I can see that the .desktop packages are there as they should, so I'd expect this is an issue with the Desktop folder not showing after install on the desktop, which may be on purpose.

Reassigning to kde-workspace; it's the best package I can think of as a target for the issue.

[Jonathan Riddell (jr)]

three issues
1) oem-config-kde is not installed after an OEM install
2) if you install it and run it it runs fine but something should set up a shortcut on the desktop to point to it
3) it runs fine but it quits at the end without a friendly "do you want to reboot now?" dialog

[Jonathan Riddell (jr)]

Let's use this bug for 2) set up a shortcut on the desktop.

Alas I forget how this was done in kde4 times.

On the live CD casper will run
chroot /root install -D -o $USERNAME -g $USERNAME /usr/share/kubuntu-default-settings/layout.js /usr/share/plasma/shells/org.kde.plasma.desktop/contents/layout.js
to copy over a first run setup which uses folderview

on netbook the layout.js would set something up if oem-config was around
netbook/share/apps/plasma/layout-templates/org.kde.plasma-netbook.defaultSal/contents/layout.js:if (applicationExists("oem-config-prepare-kde.desktop")) {

however bug 1444980 means it's not installed anyway so low priority for now

[Martin Pitt (pitti)]

Too late for vivid now, Jonathan says we'll ignore OEM mode for vivid. Probably not a big loss, most OEMs would prefer LTSes anyway?

[lordievader (oliviervdtoorn)]

In Wily beta 1 I've found that the desktop icon is there but due to the desktop settings it is not being shown. If the desktop is set to folderview the oem-icon appears.