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

Bug #1413521 reported by lordievader
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Fix Committed
High
Unassigned
Vivid
Won't Fix
High
Unassigned

Bug Description

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

Jonathan Riddell (jr)
Changed in ubiquity (Ubuntu):
milestone: none → ubuntu-15.04
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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

tags: added: iso-testing
Changed in ubiquity (Ubuntu Vivid):
importance: Undecided → High
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

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!

Changed in ubiquity (Ubuntu Vivid):
status: New → Incomplete
Revision history for this message
lordievader (oliviervdtoorn) wrote :

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.

Revision history for this message
lordievader (oliviervdtoorn) wrote :
Revision history for this message
lordievader (oliviervdtoorn) wrote :
Revision history for this message
Marcin Sągol (soee) wrote :

I can confirm this bug for amd64 images.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

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.

affects: ubiquity (Ubuntu Vivid) → kde-workspace (Ubuntu Vivid)
Jonathan Riddell (jr)
summary: - oem config not shown first boot
+ oem config not shown on first boot
Revision history for this message
Jonathan Riddell (jr) wrote : Re: oem config not shown on first boot

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

Revision history for this message
Jonathan Riddell (jr) wrote :

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

summary: - oem config not shown on first boot
+ desktop folderview needs to be added on first boot on oem installs
Changed in kde-workspace (Ubuntu Vivid):
status: Incomplete → Confirmed
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

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?

Changed in kde-workspace (Ubuntu Vivid):
milestone: ubuntu-15.04 → none
status: Confirmed → Won't Fix
Changed in kde-workspace (Ubuntu):
milestone: none → ubuntu-15.05
Jonathan Riddell (jr)
Changed in kde-workspace (Ubuntu):
milestone: ubuntu-15.05 → ubuntu-15.10
Revision history for this message
lordievader (oliviervdtoorn) wrote :

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.

isa (isa-zenab)
Changed in kde-workspace (Ubuntu):
status: Confirmed → Fix Committed
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.