dnschneid / crouton

Chromium OS Universal Chroot Environment
https://goo.gl/fd3zc?si=1
BSD 3-Clause "New" or "Revised" License
8.56k stars 1.24k forks source link

E: Unable to locate package kde-runtime #4779

Open gtxg16 opened 2 years ago

gtxg16 commented 2 years ago
chronos@localhost ~/Downloads $ sudo edit-chroot -all
name: bullseye
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/bullseye...
crouton: version 1-20220111101058~master:a9eafaee
release: bullseye
architecture: amd64
xmethod: xorg
targets: kde-desktop
host: version 14816.99.0 (Official Build) stable-channel hatch 
kernel: Linux localhost 4.19.241-13212-ge9b0bab46475 #1 SMP PREEMPT Fri Jul 1 18:52:20 PDT 2022 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/bullseye...

Please describe your issue:

Whenever I try and create a chroot with the latest Debian version with KDE, the setup ends with:

E: Unable to locate package kde-runtime
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/bullseye...

Then when I try and start it, I get this:

chronos@localhost ~/Downloads $ sudo startkde
Entering /mnt/stateful_partition/crouton/chroots/bullseye...
A chroot setup script still exists inside the chroot.
The chroot may not be fully set up.
Would you like to finish the setup? [Y/n/d] n
Skipping setup. You will be prompted again next time.
UID 1000 not found in bullseye
Unmounting /mnt/stateful_partition/crouton/chroots/bullseye...

Saying yes will just repeat trying to create the chroot with the same problem.

If known, describe the steps to reproduce the issue:

sudo crouton -r bullseye -t kde-desktop OR sudo crouton -r bullseye -t kde They bothh end up with the same error, and the former option is the exact same as the latter except with apps.

TomTravis commented 2 years ago

the user account in chroot has no been setup uid 1000 is missing i would start the install again and with for kde install after chroot boots kde uses x11 crouton sortof does this may cause issues

lightsrgr8 commented 3 weeks ago

Same issue here. Forked my own repo just to remove the 'kde-runtime' package...