Aliot's questions

I'm trying to migrate a Ubuntu 19.04 install to the last Ubuntu version. The problem is the migration tool refuses to update to the next version:

sudo do-release-upgrade 
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

Get:1 Upgrade tool signature [1,554 B]                                                                                                                                                                                                                                                  
Get:2 Upgrade tool [1,336 kB]                                                                                                                                                                                                                                                           
Fetched 1,338 kB in 0s (0 B/s)                                                                                                                                                                                                                                                          
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
extracting 'focal.tar.gz'

Reading cache

Checking package manager

Can not upgrade 

An upgrade from 'disco' to 'focal' is not supported with this tool. 

How can I migrate instead of a fresh install where I would have to reconfigure everything?

Thanks in advance for your kind help

I've an issue with ubuntu 14.10 and 15.04. I'm logged out from my user session randomly and suddenly.

Here are some log information:

kern.log

first logout:

May  3 16:34:59 rm-work kernel: [28558.808129] traps: metacity[7712] trap int3 ip:7fe10cb50d00 sp:7ffdb4f06a00 error:0
May  3 16:34:59 rm-work gnome-session[7637]: Unrecoverable failure in required component metacity.desktop
May  3 16:35:12 rm-work gnome-session[30100]: Entering running state

second logout:

May  4 00:50:24 rm-work kernel: [54634.236474] traps: metacity[30179] trap int3 ip:7f68e3eddd00 sp:7ffc5e2b9d30 error:0
May  4 00:50:24 rm-work gnome-session[30100]: Unrecoverable failure in required component metacity.desktop
May  4 00:50:42 rm-work gnome-session[27957]: Entering running state

syslog.log

first log out:

May  3 16:34:59 rm-work gnome-session[7637]: Avertissement du gestionnaire de fenêtres : Log level 6: The program 'metacity' received an X Window System error.
May  3 16:34:59 rm-work gnome-session[7637]: This probably reflects a bug in the program.
May  3 16:34:59 rm-work gnome-session[7637]: The error was 'BadRegion (invalid Region parameter)'.
May  3 16:34:59 rm-work gnome-session[7637]: (Details: serial 63596288 error_code 140 request_code 138 (XFIXES) minor_code 12)
May  3 16:34:59 rm-work gnome-session[7637]: (Note to programmers: normally, X errors are reported asynchronously;
May  3 16:34:59 rm-work gnome-session[7637]: that is, you will receive the error a while after causing it.
May  3 16:34:59 rm-work gnome-session[7637]: To debug your program, run it with the GDK_SYNCHRONIZE environment
May  3 16:34:59 rm-work gnome-session[7637]: variable to change this behavior. You can then get a meaningful
May  3 16:34:59 rm-work gnome-session[7637]: backtrace from your debugger if you break on the gdk_x_error() function.)
May  3 16:34:59 rm-work kernel: [28558.808129] traps: metacity[7712] trap int3 ip:7fe10cb50d00 sp:7ffdb4f06a00 error:0
May  3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: Child process 7712 was already dead.
May  3 16:34:59 rm-work gnome-session[7637]: WARNING: Child process 7712 was already dead.
May  3 16:34:59 rm-work gnome-session[7637]: WARNING: Application 'metacity.desktop' killed by signal 5
May  3 16:34:59 rm-work gnome-session[7637]: WARNING: App 'metacity.desktop' respawning too quickly
May  3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: Application 'metacity.desktop' killed by signal 5
May  3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: App 'metacity.desktop' respawning too quickly
May  3 16:34:59 rm-work gnome-session[7637]: Unrecoverable failure in required component metacity.desktop
May  3 16:34:59 rm-work gnome-session[7637]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: CRITICAL: We failed, but the fail whale is dead. Sorry....

second log out:

May  4 00:50:24 rm-work gnome-session[30100]: Avertissement du gestionnaire de fenêtres : Log level 6: The program 'metacity' received an X Window System error.
May  4 00:50:24 rm-work gnome-session[30100]: This probably reflects a bug in the program.
May  4 00:50:24 rm-work gnome-session[30100]: The error was 'BadRegion (invalid Region parameter)'.
May  4 00:50:24 rm-work gnome-session[30100]: (Details: serial 170024023 error_code 140 request_code 138 (XFIXES) minor_code 12)
May  4 00:50:24 rm-work gnome-session[30100]: (Note to programmers: normally, X errors are reported asynchronously;
May  4 00:50:24 rm-work gnome-session[30100]: that is, you will receive the error a while after causing it.
May  4 00:50:24 rm-work gnome-session[30100]: To debug your program, run it with the GDK_SYNCHRONIZE environment
May  4 00:50:24 rm-work gnome-session[30100]: variable to change this behavior. You can then get a meaningful
May  4 00:50:24 rm-work gnome-session[30100]: backtrace from your debugger if you break on the gdk_x_error() function.)
May  4 00:50:24 rm-work kernel: [54634.236474] traps: metacity[30179] trap int3 ip:7f68e3eddd00 sp:7ffc5e2b9d30 error:0
May  4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: Child process 30179 was already dead.
May  4 00:50:24 rm-work gnome-session[30100]: WARNING: Child process 30179 was already dead.
May  4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: Application 'metacity.desktop' killed by signal 5
May  4 00:50:24 rm-work gnome-session[30100]: WARNING: Application 'metacity.desktop' killed by signal 5
May  4 00:50:24 rm-work gnome-session[30100]: WARNING: App 'metacity.desktop' respawning too quickly
May  4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: App 'metacity.desktop' respawning too quickly
May  4 00:50:24 rm-work gnome-session[30100]: Unrecoverable failure in required component metacity.desktop
May  4 00:50:24 rm-work gnome-session[30100]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May  4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Any idea to fix it?

Regards

I'd like to migrate my Ubuntu 14.04 install from a smaller SSD (256GB) to a bigger one (Crucial MX100 512GB) without reinstalling. What is the best way to process? I read that Clonezilla was not appropriate to deal with the SSD alignment.

More details about my install (a full encrypted install with LVM):

df -h

Filesystem                  Size Used Available Used% Mount on
/dev/mapper/rm--work--vg-root    23G     11G   12G  47% /
none                            4,0K       0  4,0K   0% /sys/fs/cgroup
udev                            7,7G    4,0K  7,7G   1% /dev
tmps                            7,7G     74M  7,7G   1% /tmp
tmpfs                           1,6G    1,6M  1,6G   1% /run
none                            5,0M       0  5,0M   0% /run/lock
none                            7,7G    764K  7,7G   1% /run/shm
none                            100M     64K  100M   1% /run/user
tmpfs                           4,0G       0  4,0G   0% /var/cache/apt/archives
/dev/sda1                       228M     85M  132M  39% /boot
/dev/mapper/rm--work--vg-home   204G    189G  4,9G  98% /home

cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/aliot--work--vg-root /               ext4    errors=remount-ro,noatime,discard 0       1
# /boot was on /dev/sdc1 during installation
UUID=c15f5e23-e892-4f00-8744-2805ae304cf9 /boot           ext2    defaults        0       2
/dev/mapper/aliot--work--vg-home /home           ext4    defaults,noatime,discard        0       2
/dev/mapper/aliot--work--vg-swap_1 none            swap    sw              0       0

#tmp to ram
#tmpfs   /tmp       tmpfs   defaults,noatime,mode=1777   0  0
tmps /tmp tmpfs defaults,suid,nodev,exec 0 0

#/var/log/ to ram
#tmpfs /var/log tmpfs defaults,nosuid,nodev,noatime,mode=0755,size=5% 0 0

#apt cache to ram
tmpfs    /var/cache/apt/archives    tmpfs    defaults,size=4g    0    0

#cache to ram
tmpfs    /home/rm/.cache    tmpfs    defaults,size=1g    0    0

sudo lvdisplay

  --- Logical volume ---
  LV Path                /dev/aliot-work-vg/swap_1
  LV Name                swap_1
  VG Name                aliot-work-vg
  LV UUID                ym1lJD-aRxN-23NA-Wgs8-0YbP-ryIv-RWzY6v
  LV Write Access        read/write
  LV Creation host, time aliot-work, 2013-06-24 14:29:45 +0200
  LV Status              available
  # open                 2
  LV Size                7,86 GiB
  Current LE             2013
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:1

  --- Logical volume ---
  LV Path                /dev/aliot-work-vg/root
  LV Name                root
  VG Name                aliot-work-vg
  LV UUID                degnqJ-5KOJ-IW6t-FPJx-5xhy-DUTa-jaWVLY
  LV Write Access        read/write
  LV Creation host, time aliot-work, 2013-06-24 14:31:07 +0200
  LV Status              available
  # open                 1
  LV Size                23,24 GiB
  Current LE             5949
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:2

  --- Logical volume ---
  LV Path                /dev/aliot-work-vg/home
  LV Name                home
  VG Name                aliot-work-vg
  LV UUID                beExpf-NH3n-1CZL-BnLp-eAm3-jrpl-WTBu7U
  LV Write Access        read/write
  LV Creation host, time aliot-work, 2013-06-24 14:31:17 +0200
  LV Status              available
  # open                 1
  LV Size                207,13 GiB
  Current LE             53025
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:3