[Bug 1063399] Re: ubiquity fails when useing kde

Dmitrijs Ledkovs launchpad at surgut.co.uk
Mon Oct 21 10:23:39 UTC 2013


remastersys is not support software in ubuntu.

For remastering desktop images please use either official build-infrastructure projects which are opensource:
lp:ubuntu-cdimage & lp:livecd-rootfs.

Or you can try using ubuntu-defaults-builder for a simplier way to remaster images
https://launchpad.net/ubuntu/+source/ubuntu-defaults-builder

If there is problem remastering kubuntu images with remastersys, please
report that bug to remastersys and/or discuss it with kubuntu developers
on #kubuntu-devel on freenode.


** Tags added: kubuntu

** Changed in: ubiquity (Ubuntu)
       Status: New => Incomplete

** Summary changed:

- ubiquity fails when useing kde
+ remastersys kubuntu fails

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

Title:
  remastersys kubuntu fails

Status in “ubiquity” package in Ubuntu:
  Incomplete

Bug description:
  After making an ubuntu 12.04.1 LTS  KDE based system with remastersys
  3.03-1 after installing all updates as of 10/7/12  I can run the image
  as a live system but when trying to install I get the following error
  when running sudo ubiquity -d:

  "/home/user_name/.kde/socket-user_name/kdeinit4_0"
  Then a window saying "installer closed unexpectedly  Application installer(bin), signal aborted".

  If I pin the dbus,dbus-x11, and libdbus-1-2 packages at version
  1.4.18-1ubuntu1 and then remaster the image, it will install. Using
  later versions of those packages up to and including version
  1.4.18-1ubuntu1.3 I get the above error.

  If I remaster a standard ubuntu system (unity not KDE) remastersys has
  no problem installing with the newer packages.

  I suspect the ubiquity-frontend-kde that is used by remastersys when
  building a kde based image.

  
  There was no var/log/partman file since installation failed.

  Here is the relevant part of the var/log/syslog -I think

  Oct  7 12:22:52 lions dbus[1097]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
  Oct  7 12:22:52 lions org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
  Oct  7 12:22:52 lions dbus[1097]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
  Oct  7 12:23:39 lions ubiquity[3792]: Ubiquity 2.10.20
  Oct  7 12:24:06 lions ubiquity[3860]: Ubiquity 2.10.20
  Oct  7 12:26:56 lions kernel: [  476.536020] usb 1-2: new high-speed USB device number 5 using ehci_hcd
  Oct  7 12:26:56 lions kernel: [  476.672669] scsi3 : usb-storage 1-2:1.0
  Oct  7 12:26:57 lions mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2"

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



More information about the foundations-bugs mailing list