tools/manjaro-tools

Fork 0

manjaro-tools-iso-git-r1918.a300acd-1 stopps after de-image creation with error #189

New issue

Closed

opened 2016-02-23 20:03:04 +00:00 by philm · 20 comments

philm commented

2016-02-23 20:03:04 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Seems some is wrong within manjaro-tools-iso-git-r1918.a300acd-1. It simply stops after de-image creation with an error message. Using however manjaro-tools-iso-git-r1909.6a8a408-1 with the same profile, the ISO get created.

(253/253) installing zfs-utils                   [######################] 100%
 --> Killing chroot process: dbus-launch (28243)
 --> Killing chroot process: dbus-daemon (28244)
Generating locales...
Generation complete.
  -> Copying mate-overlay ...
==> Configuring [mate-image]
  -> Setting plymouth sonar-elegant ....
  -> Configuring Displaymanager ...
 --> Loading [/usr/share/manjaro-tools/desktop.map] ...
  -> Trying to detect desktop environment ...
  -> Detected: mate
  -> Configuring AccountsService ...
  -> Configured: gdm
 --> Configuring [systemd] ....
  -> Setting bluetooth ...
  -> Setting cronie ...
  -> Setting ModemManager ...
==> ERROR: A failure occurred in /var/lib/manjaro-tools/buildiso/mate-sonar/x86_64/mate-image().
    Aborting...

*Created by: philmmanjaro* Seems some is wrong within **manjaro-tools-iso-git-r1918.a300acd-1**. It simply stops after de-image creation with an error message. Using however **manjaro-tools-iso-git-r1909.6a8a408-1** with the same profile, the ISO get created. ``` (253/253) installing zfs-utils [######################] 100% --> Killing chroot process: dbus-launch (28243) --> Killing chroot process: dbus-daemon (28244) Generating locales... Generation complete. -> Copying mate-overlay ... ==> Configuring [mate-image] -> Setting plymouth sonar-elegant .... -> Configuring Displaymanager ... --> Loading [/usr/share/manjaro-tools/desktop.map] ... -> Trying to detect desktop environment ... -> Detected: mate -> Configuring AccountsService ... -> Configured: gdm --> Configuring [systemd] .... -> Setting bluetooth ... -> Setting cronie ... -> Setting ModemManager ... ==> ERROR: A failure occurred in /var/lib/manjaro-tools/buildiso/mate-sonar/x86_64/mate-image(). Aborting... ```

philm commented

2016-02-23 20:05:05 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Related to #45

*Created by: udeved* Related to #45

philm commented

2016-02-23 20:06:02 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Well, it happens even without logging.

*Created by: philmmanjaro* Well, it happens even without logging.

philm commented

2016-02-23 20:06:31 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

See my last comment, its the wrapper function I guess.

*Created by: udeved* See my last comment, its the wrapper function I guess.

philm commented

2016-02-23 20:14:09 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

I think it is more or less the run_safe function ...

*Created by: philmmanjaro* I think it is more or less the **run_safe** function ...

philm commented

2016-02-23 20:15:38 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Right, but we can easily debig this...

Comment out

&> /dev/null

in util-iso-image.sh

*Created by: udeved* Right, but we can easily debig this... Comment out ``` &> /dev/null ``` in util-iso-image.sh

philm commented

2016-02-23 20:19:47 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

--> Configuring systemd ....
  -> Setting bluetooth ...
Created symlink /etc/systemd/system/dbus-org.bluez.service, pointing to /usr/lib/systemd/system/bluetooth.service.
Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service, pointing to /usr/lib/systemd/system/bluetooth.service.
  -> Setting cronie ...
Created symlink /etc/systemd/system/multi-user.target.wants/cronie.service, pointing to /usr/lib/systemd/system/cronie.service.
  -> Setting ModemManager ...
Operation failed: No such file or directory
==> ERROR: A failure occurred in /build/manjaro-tools/buildiso/mate-sonar/x86_64/mate-image().
    Aborting...

*Created by: udeved* ``` --> Configuring systemd .... -> Setting bluetooth ... Created symlink /etc/systemd/system/dbus-org.bluez.service, pointing to /usr/lib/systemd/system/bluetooth.service. Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service, pointing to /usr/lib/systemd/system/bluetooth.service. -> Setting cronie ... Created symlink /etc/systemd/system/multi-user.target.wants/cronie.service, pointing to /usr/lib/systemd/system/cronie.service. -> Setting ModemManager ... Operation failed: No such file or directory ==> ERROR: A failure occurred in /build/manjaro-tools/buildiso/mate-sonar/x86_64/mate-image(). Aborting... ```

philm commented

2016-02-23 20:28:07 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Hmm, now I wonder why it slipped thru in older versions ... github.com/manjaro/manjaro-tools-iso-profiles@f30934f1c0

*Created by: philmmanjaro* Hmm, now I wonder why it slipped thru in older versions ... https://github.com/manjaro/manjaro-tools-iso-profiles/commit/f30934f1c018daf056dfe6ee242fe24983787aff

philm commented

2016-02-23 20:31:08 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

because we suppressed output, and the wrapper function has an exit trap, that seems to influence exit codes of calls.

*Created by: udeved* because we suppressed output, and the wrapper function has an exit trap, that seems to influence exit codes of calls.

philm commented

2016-02-23 20:31:51 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

So how does MM get activated properly on systemd?

*Created by: udeved* So how does MM get activated properly on systemd?

philm commented

2016-02-23 20:33:49 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Well it was not installed in sonar editions. We should check the warper function again. Catching the error code is ok, but then we should know where to look. in kde-minimal for example I get it cos cups is not installed and I try to activate it ...

*Created by: philmmanjaro* Well it was not installed in sonar editions. We should check the warper function again. Catching the error code is ok, but then we should know where to look. in **kde-minimal** for example I get it cos **cups** is not installed and I try to activate it ...

philm commented

2016-02-23 20:35:26 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

The exit trap is basically cool, we can expand it for #174.
Good opportunity to make the exits safe.

*Created by: udeved* The exit trap is basically cool, we can expand it for #174. Good opportunity to make the exits safe.

philm commented

2016-02-23 20:36:36 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

We need to check if the service file exists.

*Created by: udeved* We need to check if the service file exists.

philm commented

2016-02-23 20:38:15 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

I don't complain about the error exit. This is great and wanted. However we should print out the error at least.

*Created by: philmmanjaro* I don't complain about the error exit. This is great and wanted. However we should print out the error at least.

philm commented

2016-02-23 20:39:15 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Hang on, we need to remove all stderr to /dev/null stuff.

*Created by: udeved* Hang on, we need to remove all stderr to /dev/null stuff.

philm commented

2016-02-23 20:39:57 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

&> /dev/null

This needs to go so we get errors printed.

*Created by: udeved* ``` &> /dev/null ``` This needs to go so we get errors printed.

philm commented

2016-02-23 20:40:10 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Take your time. No pressure.

*Created by: philmmanjaro* Take your time. No pressure.

philm commented

2016-02-23 20:40:52 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Just pushed the logger to tackle this.
It was expected to produce all kind of little errors. ;)

*Created by: udeved* Just pushed the logger to tackle this. It was expected to produce all kind of little errors. ;)

philm commented

2016-02-23 20:41:27 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

And it seemed it worked just fine ...

*Created by: philmmanjaro* And it seemed it worked just fine ...

philm commented

2016-02-23 20:42:03 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

The basic logging ability works fine,yes. :)

*Created by: udeved* The basic logging ability works fine,yes. :)

philm commented

2016-02-23 21:43:10 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

With the last commits, kde-minimal builds for me with systemd.

*Created by: udeved* With the last commits, kde-minimal builds for me with systemd.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

tools/manjaro-tools#189

No description provided.

Rows
Columns