budgie profile loading fails at boot after remastering:
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
last week I've remastered Bionic customizing it (it's something I'm doing since 10.04 for distributing it to our students).
Remastering process is totally "hand made", I mean using only terminal, without any prebuilt software, so extracting dvd. unsquashing filesystem, chrooting, installing packages, configuring "son et lumière" (wallpaper etc) and finally rebuilding it with makeisofs.
For not wasting time, iso is minimal and users can find on their desktop a script that they can run to dselect-upgrade their minimal distro to (let's say this way) "our university standard" (obviously, if they want, they can just delete it).
Never failed or anyway never happened unresolvable problems.
Until 16.04 (we customize and distribute only LTSs) I was using Gnome Flashback as DE and, to speed customization process, I was used to copy a standard ~/.config/dconf/user (got from a brand new installed machine) into /etc/skel/.config/dconf/user and everything went OK.
Now something strange is happening with Budgie Bionic: once copied the above mentioned standard /etc/skel/.config/dconf/user file (got from a 18.04 brand new budgie ... not the old one) and remastered iso, at boot an error msg appears saying error found when loading /etc/profile. Nothing to do, then graphical environment loads and everything works at its best; more, logging out and re-logging in nothing more happens.
I've spent an afternoon looking into fs trying to understand and the only thing I've noticed is that /etc/profile's owner was user1000 (my user on my pc): bizarre, because I never touched iso's /etc/profile when working as user silvia (whose UID is 1000), mostly because I was working as root and more nothin happened when I went in chroot again, changed that file ownership and remastered iso ...
I don't understand, honestly.
Best regards,
Silvia
permissions 18.04 chroot budgie
asked May 9 at 13:16
Silvia
40328
add a comment |Â
up vote
0
down vote
favorite
last week I've remastered Bionic customizing it (it's something I'm doing since 10.04 for distributing it to our students).
Remastering process is totally "hand made", I mean using only terminal, without any prebuilt software, so extracting dvd. unsquashing filesystem, chrooting, installing packages, configuring "son et lumière" (wallpaper etc) and finally rebuilding it with makeisofs.
For not wasting time, iso is minimal and users can find on their desktop a script that they can run to dselect-upgrade their minimal distro to (let's say this way) "our university standard" (obviously, if they want, they can just delete it).
Never failed or anyway never happened unresolvable problems.
Until 16.04 (we customize and distribute only LTSs) I was using Gnome Flashback as DE and, to speed customization process, I was used to copy a standard ~/.config/dconf/user (got from a brand new installed machine) into /etc/skel/.config/dconf/user and everything went OK.
Now something strange is happening with Budgie Bionic: once copied the above mentioned standard /etc/skel/.config/dconf/user file (got from a 18.04 brand new budgie ... not the old one) and remastered iso, at boot an error msg appears saying error found when loading /etc/profile. Nothing to do, then graphical environment loads and everything works at its best; more, logging out and re-logging in nothing more happens.
I've spent an afternoon looking into fs trying to understand and the only thing I've noticed is that /etc/profile's owner was user1000 (my user on my pc): bizarre, because I never touched iso's /etc/profile when working as user silvia (whose UID is 1000), mostly because I was working as root and more nothin happened when I went in chroot again, changed that file ownership and remastered iso ...
I don't understand, honestly.
Best regards,
Silvia
permissions 18.04 chroot budgie
asked May 9 at 13:16
Silvia
40328
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
last week I've remastered Bionic customizing it (it's something I'm doing since 10.04 for distributing it to our students).
Remastering process is totally "hand made", I mean using only terminal, without any prebuilt software, so extracting dvd. unsquashing filesystem, chrooting, installing packages, configuring "son et lumière" (wallpaper etc) and finally rebuilding it with makeisofs.
For not wasting time, iso is minimal and users can find on their desktop a script that they can run to dselect-upgrade their minimal distro to (let's say this way) "our university standard" (obviously, if they want, they can just delete it).
Never failed or anyway never happened unresolvable problems.
Until 16.04 (we customize and distribute only LTSs) I was using Gnome Flashback as DE and, to speed customization process, I was used to copy a standard ~/.config/dconf/user (got from a brand new installed machine) into /etc/skel/.config/dconf/user and everything went OK.
Now something strange is happening with Budgie Bionic: once copied the above mentioned standard /etc/skel/.config/dconf/user file (got from a 18.04 brand new budgie ... not the old one) and remastered iso, at boot an error msg appears saying error found when loading /etc/profile. Nothing to do, then graphical environment loads and everything works at its best; more, logging out and re-logging in nothing more happens.
I've spent an afternoon looking into fs trying to understand and the only thing I've noticed is that /etc/profile's owner was user1000 (my user on my pc): bizarre, because I never touched iso's /etc/profile when working as user silvia (whose UID is 1000), mostly because I was working as root and more nothin happened when I went in chroot again, changed that file ownership and remastered iso ...
I don't understand, honestly.
Best regards,
Silvia
permissions 18.04 chroot budgie
asked May 9 at 13:16
Silvia
40328
last week I've remastered Bionic customizing it (it's something I'm doing since 10.04 for distributing it to our students).
Remastering process is totally "hand made", I mean using only terminal, without any prebuilt software, so extracting dvd. unsquashing filesystem, chrooting, installing packages, configuring "son et lumière" (wallpaper etc) and finally rebuilding it with makeisofs.
For not wasting time, iso is minimal and users can find on their desktop a script that they can run to dselect-upgrade their minimal distro to (let's say this way) "our university standard" (obviously, if they want, they can just delete it).
Never failed or anyway never happened unresolvable problems.
Until 16.04 (we customize and distribute only LTSs) I was using Gnome Flashback as DE and, to speed customization process, I was used to copy a standard ~/.config/dconf/user (got from a brand new installed machine) into /etc/skel/.config/dconf/user and everything went OK.
Now something strange is happening with Budgie Bionic: once copied the above mentioned standard /etc/skel/.config/dconf/user file (got from a 18.04 brand new budgie ... not the old one) and remastered iso, at boot an error msg appears saying error found when loading /etc/profile. Nothing to do, then graphical environment loads and everything works at its best; more, logging out and re-logging in nothing more happens.
I've spent an afternoon looking into fs trying to understand and the only thing I've noticed is that /etc/profile's owner was user1000 (my user on my pc): bizarre, because I never touched iso's /etc/profile when working as user silvia (whose UID is 1000), mostly because I was working as root and more nothin happened when I went in chroot again, changed that file ownership and remastered iso ...
I don't understand, honestly.
Best regards,
Silvia
permissions 18.04 chroot budgie
asked May 9 at 13:16
Silvia
40328
asked May 9 at 13:16
Silvia
40328
asked May 9 at 13:16
Silvia
40328
asked May 9 at 13:16
Silvia
40328
40328
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49
add a comment |Â
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034042%2fbudgie-profile-loading-fails-at-boot-after-remastering%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
At a guess you may have removed something that the scripts in /etc/profile.d depends upon to run. Suggest look at those scripts and see if they are trying to execute stuff that is not in your custom distro.
– fossfreedom♦
May 15 at 15:49