Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

debian xfce failure code 2 #3972

Closed
githubgnulinux opened this issue Dec 27, 2018 · 14 comments
Closed

debian xfce failure code 2 #3972

githubgnulinux opened this issue Dec 27, 2018 · 14 comments
Labels

Comments

@githubgnulinux
Copy link

Please paste the output of the following command here: sudo edit-chroot -all

/mnt/stateful_partition/crouton/chroots/stretch...
crouton: version unknown
release:unknown
targets:keyboard,cli-extra,xfce
host:version 11021810 stable channel kip
kernel:4415315155g656ec00c3ce2 15-11-18
freon:yes

Please describe your issue:

-su:36:syntax error:unterminated quoted string
warning:starting chroot system dbus daemon failed with code 2

If known, describe the steps to reproduce the issue:

@DennisLfromGA
Copy link
Collaborator

@githubgnulinux,

crouton: version unknown
release:unknown

The above seems to indicate that the chroot did not finish installing or was unsuccessful.
I'd try to do a crouton update and see if it helps, you can do that with:

  • sudo sh ~/Downloads/crouton -n stretch -u

Hope this helps,
-DennisLfromGA

@githubgnulinux
Copy link
Author

The system was working well after new upgrade.

The command terminal output above:

-su:36:syntax error:unterminated quoted string
warning:starting chroot system dbus daemon failed with code 2

Occurs after:

sudo sh ~/Downloads/crouton -u -n stretch -t keyboard,xfce

@DennisLfromGA
Copy link
Collaborator

@githubgnulinux,

The system was working well after new upgrade.

Then a crouton update attempt may have broken it.
Can you get into the chroot using: sudo enter-chroot -n stretch
If so then I'd try to run the following:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get -f install

Then exit the chroot and see if you can launch your xfce desktop.
If not then attempt another crouton update - don't specify the '-t' option with an update.

Hope this helps,
-DennisLfromGA

@githubgnulinux
Copy link
Author

How to prevent automatical update of chromeos and crouton?

shell
sudo apt-get update

command not found

@DennisLfromGA
Copy link
Collaborator

@githubgnulinux,

How to prevent automatical update of chromeos and crouton?

Chrome OS updates automatically without user intervention - or explicit permission.
There are things you can do when in Developer mode to prevent it but I'm not going to recommend it or tell you what to do. If you're intent on doing that then I'd just google it.

You have to update crouton manually with it's '-u' option. I usually only update crouton if there are major features or fixes that have rolled out or if a Chrome OS update breaks something.

shell
sudo apt-get update

command not found

Yes, that's expected in the shell. I asked that you use sudo enter-chroot -n stretch before running the update commands.

Hope this helps,
-DennisLfromGA

@githubgnulinux
Copy link
Author

Yes, sorry forgot to add that the same error response is shown:

shell
sudo enter-chroot -n stretch

Entering /mnt/stateful.../stretch...
-su:36:syntax erroc:unterminated quoted string
warning:starting chroot system dbus daemon failed with code 2
-su:36:syntax erroc:unterminated quoted string
unmounting /mnt/.../stretch...
$

@DennisLfromGA
Copy link
Collaborator

@githubgnulinux,

Okay, thanx for the clarification.

I should have picked up on this earlier but you may be running into this issue:

See this comment for a workaround:

This should get fixed once the following PR is merged:

Hope this helps,
-DennisLfromGA

@githubgnulinux
Copy link
Author

Sorry but do not understand the link: #3860 (comment)

sudo -i -u stretch
sudo: unknown user: stretch
sudo: unable to initialize policy plugin
chronos@localhost / $ sudo -i -u "$USERNAME"
sudo: unknown user:
sudo: unable to initialize policy plugin

Use sudo instead of su. #3956

This is not understood because the command 'su' has not been used.

@githubgnulinux
Copy link
Author

sudo sh -e ~/Downloads/crouton -t core -r buster -n test
sudo enter-chroot -n test startxfce4
Entering /mnt/stateful_partition/crouton/chroots/test...
-sh: 1: startxfce4: not found
Unmounting /mnt/stateful_partition/crouton/chroots/test...

@githubgnulinux
Copy link
Author

just deleted stretch chroot and tried reinstall
sudo sh -e ~/Downloads/crouton -u stretch -t keyboard,cli-extra,extension
sudo startxfce4
No chroots with target 'xfce' found in /mnt/stateful_partition/crouton/chroots

@githubgnulinux
Copy link
Author

sudo sh -e ~/Downloads/crouton -r buster -t keyboard,cli-extra,extension
sudo startxfce4
No chroots with target 'xfce' found in /mnt/stateful_partition/crouton/chroots

Time to rant: had a working system able to do the required tasks. Unrequired, unrequested upgrade, now unable to use computer as wanted. Not a rich employee with unlimited internet access...

@githubgnulinux
Copy link
Author

You already have the Chromium OS extension installed, so you're good to go!

Unmounting /mnt/stateful_partition/crouton/chroots/stretch...
Done! You can enter the chroot using enter-chroot.
chronos@localhost / $ sudo startxfce4
No chroots with target 'xfce' found in /mnt/stateful_partition/crouton/chroots
chronos@localhost / $ sudo enter-chroot startxfce4
Entering /mnt/stateful_partition/crouton/chroots/stretch...
-su: 1: startxfce4: not found
Unmounting /mnt/stateful_partition/crouton/chroots/stretch...

@githubgnulinux
Copy link
Author

Successful start via:
sudo startcli
sudo apt-get install xfce4
sudo startxfce4

Starting machine each time fails to start xfce4 unless debian stretch is started via 'sudo startcli', then 'sudo startxfce4'.

Now the next step, how to disable automatic chromeos, which caused this problem.
Then find internet access to re-install all the tools I use, configure xfce4, etc. etc..

@DennisLfromGA
Copy link
Collaborator

@githubgnulinux,

Sorry to confuse you, the workaround I linked above was intended to be applied in the enter-chroot script mainly but a couple of other scripts are affected too. For details see -

Note that this will be fixed when the PR is merged.

Hope this helps,
-DennisLfromGA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants