Closed svitax closed 2 years ago
@svitax,
Sorry to hear you're having so much trouble of late.
Do you get into your chroot using: sudo enter-chroot
?
Have you tried to launch your desktop from the crosh shell using: sudo startunity
?
If it still fails, you might want to add the 'xiwi' xmethiod and see if it works.
You can add it using: sudo sh ~/Downloads/crouton -n zesty -t xiwi -u
Then be sure to also install the 'crouton integration' extension.
Hope this helps, -DennisL
@DennisLfromGA
Thanks for the reply!
So this is what I normally do to get into my chroot
crosh> shell
chronos@localhost / $ sudo enter-chroot
Entering /mnt/stateful_partition/crouton/chroots/zesty...
Unknown username "whoopsie" in message bus configuration file
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
I once again tried making a new chroot, but this time on the zesty release with the gnome and chrome targets. For a brief moment, I was able to start gnome. But after I signed out, I could no longer get it to work again. And this is what I've been getting ever since.
(zesty)svitax@localhost:~$ startgnome
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-70-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashtree=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=70374bf056c1999c317d492b0fb3783428595dc0 salt=9ca2bd66ca6bf4b5eb091834658c3f46dd241cff5fb6b4babf6f2edb6f2df739" noinitrd vt.global_cursor_default=0 kern_guid=0cc0e04b-02d4-b840-863d-84eff3263533 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 28 March 2017 06:16:52AM
xorg-server 2:1.19.3-1ubuntu1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Sat Jun 3 12:57:06 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
method return time=1496519827.789496 sender=:1.11 -> destination=:1.92 serial=1693 reply_serial=2
boolean true
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
pkexec version 0.105
Error executing command as another user: Not authorized
This incident has been reported.
crouton: version 1-20170315143304~master:95589555
release: zesty
architecture: amd64
xmethod: xorg
targets: gnome,chrome
host: version 9202.64.0 (Official Build) stable-channel glimmer
kernel: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
xrandr: Output eDP1 is not disconnected but has no modes
xrandr: Output DP1 is not disconnected but has no modes
xrandr: Output HDMI1 is not disconnected but has no modes
xrandr: Output HDMI2 is not disconnected but has no modes
Kicking xrandr again
xrandr: Output eDP1 is not disconnected but has no modes
xrandr: Output DP1 is not disconnected but has no modes
xrandr: Output HDMI1 is not disconnected but has no modes
xrandr: Output HDMI2 is not disconnected but has no modes
Kicking xrandr again
Running exit commands...
/usr/bin/xinit: connection to X server lost
Hangup
waiting for X server to shut down .method return time=1496519837.290051 sender=:1.11 -> destination=:1.93 serial=1694 reply_serial=2
boolean true
(II) Server terminated successfully (0). Closing log file.
It will go into a black screen, a cursor pops up, and then it throws me back to chromeos.
So then I exited the chroot, and exited the shell. I then reentered the shell and did sudo enter-chroot
once more, followed by startgnome
No dice, same error as before.
However, I went through the exact same procedure once more... and it worked. I got into gnome. Not ideal, but at least it worked. I'm just afraid one day this won't work and I'll be locked out of the chroot for good.
So then on to your suggestions.
I tried launching the desktop using sudo startgnome
since I replaced unity with gnome, and I got the following.
chronos@localhost / $ sudo startgnome
Password:
Entering /mnt/stateful_partition/crouton/chroots/zesty...
Unknown username "whoopsie" in message bus configuration file
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-70-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashtree=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=70374bf056c1999c317d492b0fb3783428595dc0 salt=9ca2bd66ca6bf4b5eb091834658c3f46dd241cff5fb6b4babf6f2edb6f2df739" noinitrd vt.global_cursor_default=0 kern_guid=0cc0e04b-02d4-b840-863d-84eff3263533 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 28 March 2017 06:16:52AM
xorg-server 2:1.19.3-1ubuntu1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Sat Jun 3 13:14:16 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
method return time=1496520857.402921 sender=:1.11 -> destination=:1.107 serial=1949 reply_serial=2
boolean true
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
pkexec version 0.105
Error executing command as another user: Not authorized
This incident has been reported.
crouton: version 1-20170315143304~master:95589555
release: zesty
architecture: amd64
xmethod: xorg
targets: gnome,chrome
host: version 9202.64.0 (Official Build) stable-channel glimmer
kernel: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
xrandr: Output eDP1 is not disconnected but has no modes
xrandr: Output DP1 is not disconnected but has no modes
xrandr: Output HDMI1 is not disconnected but has no modes
xrandr: Output HDMI2 is not disconnected but has no modes
Kicking xrandr again
xrandr: Output eDP1 is not disconnected but has no modes
xrandr: Output DP1 is not disconnected but has no modes
xrandr: Output HDMI1 is not disconnected but has no modes
xrandr: Output HDMI2 is not disconnected but has no modes
Kicking xrandr again
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
.method return time=1496520867.077057 sender=:1.11 -> destination=:1.108 serial=1951 reply_serial=2
boolean true
(II) Server terminated successfully (0). Closing log file.
Unmounting /mnt/stateful_partition/crouton/chroots/zesty...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/zesty...
Still wouldn't enter.
So then I tried the xiwi method, and got the following.
chronos@localhost / $ sudo enter-chroot
Entering /mnt/stateful_partition/crouton/chroots/zesty...
Unknown username "whoopsie" in message bus configuration file
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
(zesty)svitax@localhost:~$ startgnome
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-70-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashtree=PARTUUID=0cc0e04b-02d4-b840-863d-84eff3263533/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=70374bf056c1999c317d492b0fb3783428595dc0 salt=9ca2bd66ca6bf4b5eb091834658c3f46dd241cff5fb6b4babf6f2edb6f2df739" noinitrd vt.global_cursor_default=0 kern_guid=0cc0e04b-02d4-b840-863d-84eff3263533 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 28 March 2017 06:16:52AM
xorg-server 2:1.19.3-1ubuntu1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Sat Jun 3 13:24:30 2017
(++) Using config file: "/etc/X11/xorg-dummy.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
crouton: version 1-20170315143304~master:95589555
release: zesty
architecture: amd64
xmethod: xiwi
targets: xiwi,gnome,chrome
host: version 9202.64.0 (Official Build) stable-channel glimmer
kernel: Linux localhost 3.10.18 #1 SMP Wed Apr 5 13:03:31 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Connected to extension, launched crouton in a window.
Error: target STRING not available
Running exit commands...
/usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
Hangup
(II) Server terminated successfully (0). Closing log file.
Even that won't work.
So I went back to xorg and my method of just exiting the chroot and shell, and then reentering and trying to launch the desktop until it somehow magically manages to enter. I guess I'll just have to stick with this until I can find a better solution.
I have the same issue, on a Pixel LS with zesty and gnome.
I'm still having this issue with Zesty. Can't fix.
I'm getting this too and cannot startxfce4. I've updated to the latest crouton and it hasn't helped.
$ sudo startxfce4
Enter encryption passphrase for xenial:
Entering /mnt/stateful_partition/crouton/chroots/xenial...
/usr/bin/startxfce4: Starting X server
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-83-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.18.0-16037-gf59ef0b48a68 #1 SMP PREEMPT Mon Nov 13 16:34:36 PST 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=1c4b0e24-5098-8e49-ab1e-853c9c72d8b0/PARTNROFF=1 hashtree=PARTUUID=1c4b0e24-5098-8e49-ab1e-853c9c72d8b0/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=a6a501cdb3158ff186d009b8a63e8fba56a47344 salt=6d5e898897dd649af64eea278004bfd4bda5022c225754c5bb69e71d177b3747" noinitrd vt.global_cursor_default=0 kern_guid=1c4b0e24-5098-8e49-ab1e-853c9c72d8b0 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 17 July 2017 05:05:12PM
xorg-server 2:1.18.4-0ubuntu0.3 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Tue Dec 26 10:58:41 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.UnknownMethod: Method "ReleaseDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
Error org.freedesktop.DBus.Error.UnknownMethod: Method "TakeDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
$
I have the same problem on Pixel LS with Xenial and Gnome.
So long, and thanks for all the fish!
Please describe your issue:
Every time I try startunity, I get the following.
Screen turns black. Sometimes I can right click and I get some unity options like create new folder, etc. But nothing else. I can also switch back to chromeos.
I have tried updating my chroot. Still nothing. I have tried creating a different chroot with a multitude of other targets and releases. I have tried xenial and zesty, unity-desktop, kde-desktop, gnome-desktop, unity, kde, and gnome without the "desktop", etc. Still nothing. At this point I'm ready to just give up on crouton altogether. I had a working chroot before on zesty with kde-desktop, but just a few days ago this started happening.
Any recommendations on what I should try next to fix this issue?