Intrepid: Oem Installs fail on Kubuntu

Bug #251634 reported by Dave Morley
2
Affects Status Importance Assigned to Milestone
oem-config (Ubuntu)
Fix Released
High
Unassigned
Intrepid
Fix Released
High
Unassigned

Bug Description

Binary package hint: oem-config

Testing for alpha 3 show oem-config to fail on kubuntu alternative 32 and 64 bit.

Kubuntu's failure occurs firstly in 2 places:

1/ Hitting the "prepare to ship to end user" button does nothing. This is on the whole down to the no function of kdesudo. However running "sudo oem-config-prepare" showed up a number of error but apparently worked.

2/ Upon reboot you are greeted by a black screen with a white outlined black cross (cursor) and nothing else.

Log files to follow once I re-install.

Tags: iso-testing
Revision history for this message
Colin Watson (cjwatson) wrote :

Please supply more detail, and file separate bugs for separate problems.

Exactly what were the failures you refer to? Logs (/var/log/oem-config.log) would be helpful.

Changed in oem-config:
status: New → Incomplete
Dave Morley (davmor2)
description: updated
Dave Morley (davmor2)
description: updated
Revision history for this message
Dave Morley (davmor2) wrote :

Errors from running the sudo oem-config-prepare command

oem@ubuntu:~$ sudo oem-config-prepare
 Adding system startup for /etc/init.d/oem-config ...
   /etc/rc2.d/S12oem-config -> ../init.d/oem-config
   /etc/rc3.d/S12oem-config -> ../init.d/oem-config
   /etc/rc4.d/S12oem-config -> ../init.d/oem-config
   /etc/rc5.d/S12oem-config -> ../init.d/oem-config
Error: "/var/tmp/kdecache-oem" is owned by uid 29999 instead of uid 0.
Error: "/tmp/kde-oem" is owned by uid 29999 instead of uid 0.
kdialog(14149) KToolInvocation::klauncher: klauncher not running... launching kdeinit
Error: "/tmp/kde-oem" is owned by uid 29999 instead of uid 0.
Error: "/tmp/ksocket-oem" is owned by uid 29999 instead of uid 0.
kdeinit4: Shutting down running client.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
Error: "/tmp/ksocket-oem" is owned by uid 29999 instead of uid 0.
Error: "/tmp/kde-oem" is owned by uid 29999 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kded4
Error: "/var/tmp/kdecache-oem" is owned by uid 29999 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-oem" is owned by uid 29999 instead of uid 0.
Error: "/var/tmp/kdecache-oem" is owned by uid 29999 instead of uid 0.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
Error: "/tmp/kde-oem" is owned by uid 29999 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/knotify4
Error: "/var/tmp/kdecache-oem" is owned by uid 29999 instead of uid 0.
kdialog(14149): Couldn't start knotify from knotify4.desktop: "KDEInit could not launch '/usr/bin/knotify4'."

kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update

Revision history for this message
Dave Morley (davmor2) wrote :
Revision history for this message
Dave Morley (davmor2) wrote :
Revision history for this message
Dave Morley (davmor2) wrote :

Still happening in 20080811

Revision history for this message
Dave Morley (davmor2) wrote :

Is this bug still incomplete as I have given the info required?

Colin Watson (cjwatson)
Changed in oem-config:
importance: Undecided → High
status: Incomplete → Confirmed
Revision history for this message
Jonathan Riddell (jr) wrote :

Should be fixed in oem-config 1.48

Changed in oem-config:
status: Confirmed → 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.