Ubuntu 16.04 GNOME support or GNOME Shell > 3.14 in 14.04?

[s5bug]

I would like to have colored toolbars for the paper theme :smile_cat:

[tista500]

@firestar115,

If you had any Chromebooks employs Intel architectures, you would be able to install and launch Xenial GNOME.

By the way, I have not any clue what do you really want to do? In general, the required version of Gtk+ theme is depend on Gtk+ package instead of Gnome-Shell. For example, Xenial has Gtk+ 3.18.x, Wily had 3.16.x, and Trusty has had 3.10.x. If that theme requires Gtk+ 3.14.x or higher, Wily would be acceptable for. But in many cases, Gtk+ theming is done for each Gtk+ stable releases separately (it means 3.14.x theming doesn't work properly under 3.16.x and/or 3.12.x). So isn't it better to be clear that the exact Gk+ version you really want to run?

And if you would try to GNOME 3.14.x desktop on Trusty, the only way is to rebuild core 3.14.x packages/sources for Trusty by hand. Because Gnome3-staging PPA has only 1+ up version against the release (means 3.12.x for Trusty). And then Vivid had 3.14.x packages in main repository, so you might get those packages still even though Vivid had reached EOL already... Indeed, today Trusty seems quite aged, too old for some theme designers and application developers...

Forgot to mention. Still Xenial is under Alpha 2 release now so, I don't want you to run it on production machines, should be limited testing only...

Regards.

[s5bug]

Sorry for late response, I have an Acer C7 chromebook.

I want colored toolbars in paper theme, and I don't know how to do that w/o crashing my chroot. (Which is what happened last time I tried.)

[tista500]

@firestar115,

Just googled, is the Paper theme here?: https://github.com/snwh/paper-gtk-theme Unfortunately I could NOT see "required component version" anywhere, so I will not be able to help you in your current issue. You should ask to them first about the exact Gtk+ version they required to work properly.

By the way, general release upgrading method is in Wiki: https://github.com/dnschneid/crouton/wiki/Upgrade-chroot-release You can just follow those steps shown above.

Regards.

[s5bug]

After upgrading, I get this crash:

$ sudo startgnome -n programming
Entering /mnt/stateful_partition/crouton/chroots/programming...
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] y
Preparing chroot environment...
Unknown username "geoclue" in message bus configuration file
Setting up libutempter0:amd64 (1.1.6-1ubuntu1) ...
The utempter system group isn't used anymore by this package
chown: cannot access '/usr/lib/utempter': No such file or directory
dpkg: error processing package libutempter0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xterm:
 xterm depends on libutempter0 (>= 1.1.5); however:
  Package libutempter0:amd64 is not configured yet.

dpkg: error processing package xterm (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.21-0ubuntu5) ...
Errors were encountered while processing:
 libutempter0:amd64
 xterm
Failed to complete chroot setup.
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.

_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Wed Feb 3 21:14:19 PST 2016 x86_64
Kernel command line: cros_secure  console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-1 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="2 vboot none ro 1,0 2545920 bootcache PARTUUID=cfc4b35a-3cf5-8a41-ae44-8a1f20dc8f14/PARTNROFF=1 2545920 db34ca72228133ddac3ded2e3c42fa3aa7fc1c07 512 20000 100000, vroot none ro 1,0 2506752 verity payload=254:0 hashtree=254:0 hashstart=2506752 alg=sha1 root_hexdigest=9c4166618eac6c797fc26624d96282af2d8ffd1a salt=ffc1be0331e21140495d031ec2f70d6e645f1c5e0e916ca7ac172f30b47e2213" noinitrd vt.global_cursor_default=0 kern_guid=cfc4b35a-3cf5-8a41-ae44-8a1f20dc8f14 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3  
Build Date: 12 February 2015  02:49:29PM
xorg-server 2:1.15.1-0ubuntu2.7 (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: Sun Feb  7 19:23:12 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
crouton: version unknown
release: unknown
architecture: unknown
xmethod: xorg
targets: gnome,chrome-dev
host: version 7834.22.0 (Official Build) dev-channel parrot 
kernel: Linux localhost 3.8.11 #1 SMP Wed Feb 3 21:14:19 PST 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
No Chromium OS X server is available.
*** BUG ***
In pixman_region_translate: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region_translate: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region_translate: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region_translate: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down Hangup
(EE) Server terminated successfully (0). Closing log file.

Unmounting /mnt/stateful_partition/crouton/chroots/programming...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/programming...

[tista500]

@firestar115,

It seems your upgrading incomplete yet.

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] y

And apt said these errors:

Setting up libutempter0:amd64 (1.1.6-1ubuntu1) ...
The utempter system group isn't used anymore by this package
chown: cannot access '/usr/lib/utempter': No such file or directory
dpkg: error processing package libutempter0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xterm:
 xterm depends on libutempter0 (>= 1.1.5); however:
 Package libutempter0:amd64 is not configured yet.

So you need to fix that at first. If you're in Crosh window, run this:

sudo enter-chroot -n programming
sudo apt-get install -f

Then apt will show you the way to resolve the errors within upgrading, and let me see the output.

Regards.

[s5bug]

$ sudo enter-chroot -n programming
Entering /mnt/stateful_partition/crouton/chroots/programming...
Unknown username "geoclue" in message bus configuration file
(programming)firestar115@localhost:~$ sudo apt-get install -f
[sudo] password for firestar115: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gcc-4.9-base:i386 gir1.2-gmenu-3.0 gstreamer1.0-clutter libbluetooth3 libcamel-1.2-45 libclutter-gst-2.0-0 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libedata-book-1.2-20 libedataserver-1.2-18
  libgdata13 libgnome-bluetooth11 libgphoto2-port10 libgtop2-7 libicu52 libimobiledevice4 libjasper1 libntdb1 libopenobex1 libopenvg1-mesa libplist1 libsystemd-daemon0 libsystemd-journal0 libupower-glib1
  libusbmuxd2 obex-data-server
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 62 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up libutempter0:amd64 (1.1.6-1ubuntu1) ...
The utempter system group isn't used anymore by this package
chown: cannot access '/usr/lib/utempter': No such file or directory
dpkg: error processing package libutempter0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xterm:
 xterm depends on libutempter0 (>= 1.1.5); however:
  Package libutempter0:amd64 is not configured yet.

dpkg: error processing package xterm (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.21-0ubuntu5) ...
Errors were encountered while processing:
 libutempter0:amd64
 xterm
E: Sub-process /usr/bin/dpkg returned an error code (1)

[s5bug]

And my screen is still blank (the new GTK+ won't work)

[tista500]

@firestar115,

Hey, why don't you read the errors at all? Hmm, anyway at this time, remove unconfigured packages manually and then do dist-upgrade:

sudo enter-chroot -n programming
sudo dpkg -r libutempter0  xterm
sudo apt-get update
sudo apt-get dist-upgrade -y
exit
sudo sh ~/Downloads/crouton -u -n programming -r xenial

Regards.

[DennisLfromGA]

@firestar115,

Definitely try @tista500's suggestions first to see if you can straighten out your chroot.

---

Looking at your third post, it looks like the installation failed pretty early on, when that happens, it's usually best login in as 'root' and let it finish the setup script or even force it with a second 'x', like:

sudo enter-chroot -n programming -u root -xx

It may be too late for that now but it might be worth a shot if you're still having problems.

[tista500]

@DennisLfromGA,

Thanks!! :) It looks nice!

Regards.

[s5bug]

@DennisLfromGA

$ sudo enter-chroot -n programming -u root -xx
Unknown username "geoclue" in message bus configuration file
chroot: failed to run command '/prepare.sh': No such file or directory
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/programming...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/programming...

OR MAYBE...

What would I do if I started a trusty chroot from scratch?

[s5bug]

@tista500 I tried your suggestion and it just :hankey:ed.

[s5bug]

@DennisLfromGA How would I upgrade to xenial from a clean trusty chroot?

(I don't know if bump is an appropriate word for this post.)

[DennisLfromGA]

@firestar115 - See Upgrade chroot release