Customized Gnome image does not reach X, failing services #101
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: ryanvade
I created an image using the Gnome profile but I added some themes and wallpapers from the AUR. I then modified the gnome-backgrounds.xml file to use those wallpapers. I also modified the dconf/user file to use a different default wallpaper. Nothing else was changed. The Normal unchanged image works fine but the modified one does not reach the desktop and it freezes. I also noticed that a systemd tempfiles service is failing. Could this be an issue with permissions?
Created by: Kirek
Is normal that tmpfiles services fails in livecd, it can be ignored.
Can you upload your modified profile somewhere?
Created by: ryanvade
Yeah, here it is:
https://github.com/ryanvade/manjaro-tools-iso-profiles/tree/master/gnome
I forgot to mention that I added the .local/share/gnome-shell/extensions directory gnome-overlay/etc/skel/
Created by: Kirek
Did you add the aur packages in a local repo?
https://wiki.manjaro.org/index.php?title=Buildiso_with_AUR_packages:_Using_buildpkg
https://wiki.manjaro.org/index.php?title=Buildiso_with_AUR_packages:_Using_yaourt
Created by: ryanvade
Yes. The image builds fine.
Created by: ryanvade
I narrowed it down a little bit more. plymouth is not starting with this message:
so gdm-plymouth.service is failing.
Created by: ryanvade
I've update to 0.9.8. Maybe that will help.
Created by: Kirek
You may need to copy the manjaro-tools.conf again
Created by: ryanvade
It seems to have gotten worse. GDM is segfaulting.
buildiso output: http://slexy.org/view/s2ioNYrfNt
dmesg: http://slexy.org/view/s21mrfC5hC
Created by: Kirek
Did you use a manjaro-tools-git or the one in the repos?
Created by: ryanvade
I was originally using the one in the repos. That last buildiso output and dmesg was from manjaro-tools-git 0.9.8 built with this package:
https://github.com/manjaro/packages-extra/blob/master/manjaro-tools-git/PKGBUILD
I am going to reinstall Manjaro on my laptop and start from the beginning again.
Created by: ryanvade
I also noticed that the new version had roughly 200 extra packages installed increasing the size of the ISO from 1.6 Gb to 2.2 Gb.
Created by: Kirek
there was a major bug for a few hours in devel that caused the creation of bad isos. Use 0.9.8 from the repos or rebuild latest git devel.
Created by: ryanvade
It appears I was using 0.9.8 before the PKGBUILD was updated to 0.9.9:
http://slexy.org/view/s20xBfInvb
Created by: ryanvade
manjaro-tools in community is 0.9.7.4
Created by: ryanvade
The issue is still happening with manjaro-build-tools-git (0.9.9 devel branch).
gdm does not start, plymouthd no such directory, etc. I only removed the gnome-background-properties.xml file and added ozunity-wallpapers package to Packages-Gnome.
Created by: ryanvade
http://owncloud.ryanvade.info/index.php/s/Q2FpQtDjH4MU5QW --system.journal
http://owncloud.ryanvade.info/index.php/s/idQmToFdjbbOVN5 --dmesg.txt
Created by: ryanvade
I think the issue is that mhwd is not fully creating the symlinks for the graphics drivers.
Created by: philmmanjaro
The issue is something is locking the pacman data-base. mhwd-live script waits 15 seconds and removes it then. However the other process locks it again, so pacman fails ...
Created by: philmmanjaro
Please check if commit fixes your issue. Related package you find in unstable branch
Created by: philmmanjaro
@ryanvade: I added another commit which will add some more info to /var/log/livecd.log. Please post it, if you still face your issue.
Created by: ryanvade
I will rebuild with manjaro-tools-git. buildiso -p gnome -b unstable
Created by: ryanvade
Not quite fixed. The script should not be dependent on an internet connection right?
GDM and Plymouth still don't start.
without internet connection:
with internet connection:
Created by: philmmanjaro
@ryanvade: No, it doesn't need internet connection. You have a local package repository. Please check if those packages are located there.
Created by: ryanvade
@philmmanjaro
Created by: philmmanjaro
Try to run mhwd-live again. It calls followed cmd on your end:
Created by: philmmanjaro
Actually pacman get called for example like this:
Created by: ryanvade
with the last commit the ISO jumped up to 3.2 Gb in size.
Created by: ryanvade
Okay so some progress has been made. GDM is now starting fine. Plymouth is not starting but one thing at a time.
Created by: philmmanjaro
@ryanvade: seems the sync enabling made it working for you. Regarding the size jump, I don't know as I didn't change anything package wise. Please check which part got larger. It is also good to delete any cache you may have. Use the -x switch to clean also xorg-cache. Plymouth is again another story.
Created by: ryanvade
I completely removed /var/lib/manjaro-tools/buildiso/gnome before rebuilding. Does the -x switch do something different?
Created by: philmmanjaro
please call
sudo buildiso -qandsudo buildiso -qxto see the difference. It will clean the xorg-cache. However, gnome image is around 1.6 GB if you have it correct set up ...Created by: ryanvade
@philmmanjaro I just updated manjaro-tools-git and now this is happening:
Created by: philmmanjaro
Ok, I reverted it now. Please check again. However I don't know what had changed on your end to make it work after all ...
Created by: ryanvade
As far as I know nothing has changed with any of my configs. I will post the build log again.
*EDIT it must have been
github.com/manjaro/manjaro-tools-livecd@9b225ecdcband the complete clearing of the caches.
Created by: philmmanjaro
Ok, so it works now for you?
Created by: ryanvade
@philmmanjaro I keep getting odd results. Some builds work fine while others fail during building. Builds sometimes have missing package issues. The number of packages to be installed changes from 812 to 1033 sometimes for no reason which is probably the issue. I am not changing the configuration files nor am I making changes to the profile during each build. For example, the last build failed with this:
The build command I am using is
Created by: Kirek
For some reason the kernel module aufs is not active.
cat /proc/filesystems | grep aufsIf there is no output, try rebooting your machine or changing the kernel.
Created by: ryanvade
@Kirek I just rebooted which seems to fix that error. I also noticed that the number of packages to install changed again to 813 from the previous run. Something is going on with the package selection. I will rebuild manjaro-tools-git again.
Created by: ryanvade
Is there something wrong with this profile?
http://owncloud.ryanvade.info/index.php/s/shQZiEWh3gHO0YP
Created by: Kirek
When it fails to properly mount the overlay (aufs) system properly things like that may happen.
It's something like this:
base system: 300 packages
desktop system: 1000 packages, but lets say 200 where already installed with the base system, so it will only install 800. But in the case that it fails to mount de base system before installing the new packages, it will install 1000 packages.
Because you where having problems with aufs, that's what happened.
Created by: ryanvade
@philmmanjaro @Kirek It seems that
is empty and the issue with missing packages is back. Can someone check that profile I uploaded?
Created by: Kirek
Builds and boots fine here with latest manjaro-tools-devel-git (only removed the custom repo).
Created by: udeved
Regarding aufs error, I can't reproduce it on two machines, one laptop with systemd, the other my main system openrc.
Both run kernel 319, iso kernel 318.
Created by: Kirek
The aufs error sometimes happen after updating a kernel and not rebooting.
Created by: philmmanjaro
Yep. If you update the kernel and did not reboot, aufs is "broken". Also the bumblebee profile is correct on my end. So @ryanvade: always reboot your system first before building anything. This issue gets more and more to a how to use manjaro-tools probably, rather than manjaro-tools has an issue ...
Created by: ryanvade
@philmmanjaro then close this. The latest commits, with the new pacakge installatiion system, seems to have fixed the issues. I think packages were not being downloaded/installed properly before.