Full help with triple boot: Win 10, Ubuntu, other Linux - separate data partition

[Dennis N]

.xsession-errors to be exact... 17.7 GB all in one little file.

Are you sure you are reading the size correctly? Mine is 4.3 K.

[dmn@Sydney ~]$ ls -alh .xsession-errors
-rw------- 1 dmn dmn 4.3K Oct 29 07:21 .xsession-errors

and the contents are:

[dmn@Sydney ~]$ cat .xsession-errors
xrdb:  "Xft.hinting" on line 19 overrides entry on line 6
xrdb:  "Xft.hintstyle" on line 22 overrides entry on line 7

(xfce4-session:732): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /home/dmn/.cache/sessions/xfce4-session-Sydney:0, Does it exist? Permissions issue?
Setting up watches.
Watches established.

** (xfce4-clipman:753): WARNING **: Unable to register GApplication: An object is already exported for the interface org.gtk.Application at /org/xfce/clipman

(xfce4-clipman:753): GLib-GIO-CRITICAL **: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:753): GLib-WARNING **: g_set_application_name() called multiple times

(xfsettingsd:752): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `XfcePanelImage::force-gtk-icon-sizes' of type `gboolean' from rc file value "((GString*) 0x1c75780)" of type `GString'

(pamac-tray:761): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(wrapper-2.0:880): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node button, owner GtkButton)

(wrapper-2.0:886): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 29
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `XfcePanelImage::force-gtk-icon-sizes' of type `gboolean' from rc file value "((GString*) 0x18546c0)" of type `GString'

(wrapper-2.0:893): Gtk-WARNING **: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner PulseaudioButton)

It's just for the current session. I would ignore all this scary stuff unless you experience a problem.
FWIW, If you should want another plan back to normalcy, plan C is to reinstall Manjaro after saving its custom menus to your data partition for reuse. My plan B is detailed in post #316.

[Mike Krall]

Are you sure you are reading the size correctly? Mine is 4.3 K.

[dmn@Sydney ~]$ ls -alh .xsession-errors
-rw------- 1 dmn dmn 4.3K Oct 29 07:21 .xsession-errors

and the contents are:

It's just for the current session. I would ignore all this scary stuff unless you experience a problem.
FWIW, If you should want another plan back to normalcy, plan C is to reinstall Manjaro after saving its custom menus to your data partition for reuse. My plan B is detailed in post #316.

Yup... real sure... Live-USB trip shows:

.xsession-errors... 17.7GB (17,692,565,504 bytes)... 4,497,352 lines

Or, it did... I dumped all of it excepting the lines looking like the lines in your 'xsession-errors' Only regret is likely never to know what or how all those bytes got into that file.

It seems I can go a number of ways from here... your mentioned "Plan B" (Post #316) and/or "Plan C" (besides the Manjaro 17.0.4 Live-usb, I've got an iso_image for Manjaro 17.0.6).

Might also follow Manjaro "Restore Grub Bootloader" https://wiki.manjaro.org/index.php?t...se_mhwd-chroot

I'll have to do some figuring = planning.

Mike

[Dennis N]

Yup... real sure... Live-USB trip shows:
.xsession-errors... 17.7GB (17,692,565,504 bytes)... 4,497,352 lines

There is an explanation and two solutions here (dates from April):
https://forum.manjaro.org/t/xsession...-growing/22068
I would use the second one.
AFAIK, I'm not affected.

Also Google ".xsession-errors is huge "
for more reports to read (mostly Ubuntu, and from years ago).

[Mike Krall]

'oldfred'... Post #305:

t also looks like Fedora has the entire grub.cfg in the ESP, not in /boot folder, but I used a partition install, not its default LVM install.

My CentOS-7 is the same... same partition install, too.

I label & name all partitions. Particularly those I only mount occasionally or temporarily. I do that with my other installs, so I can rember which partition I have installed them into, although I have written it down (somewhere?).

Would you example me your 'name' and 'label' system, 'oldfred'?

Mike

[Mike Krall]

There is an explanation and two solutions here (dates from April):
https://forum.manjaro.org/t/xsession...-growing/22068
I would use the second one.
AFAIK, I'm not affected.

Also Google ".xsession-errors is huge "
for more reports to read (mostly Ubuntu, and from years ago).

Thank you for that...

I ran this search (there are more than first hit I haven't looked at): https://www.google.com/search?q=Arch...hrome&ie=UTF-8
and found this: https://bbs.archlinux.org/viewtopic.php?id=227774

I'm dithering... trying to talk to CentOS folks about tweaking /etc/default/grub to maybe cause CentOS more comfort in a multi-boot world. They really are server-folks and I'm pretty-odd-duck-ish there. I'm going to follow the above Arch Linux link a little. Make a run at "grub-install" on Manjaro... reinstall with 17.0.6 if problems with that (started with 17.0.4... added updates).

Just found Manjaro '.xsession-errors.old' with a lot of generated lines in it (nothing like 17.7 GB, but big-ish)... last night was empty. Dumped the repetition out. At least I can deal with it though GPartEd... not have to "sudo mount... etc." my way around... or at least I think I'm dealing with it this way... ??? We'll see.

Mike

[oldfred]

When I reformat a partition, I often forget to rename it, so I now see several partitions with out labels, one is Artful.
I normally edit both labels with Disks if not when I created it with gparted.

Label is the labels that both gpt & MBR would show from formatting a partition. PARTLABEL is from gpt(GUID) partition label.

sudo blkid -c /dev/null -o list
[sudo] lsblk -o NAME,LABEL,PARTLABEL,SIZE,MOUNTPOINT,UUID
NAME   LABEL   PARTLABEL    SIZE MOUNTPOINT UUID
sda                       232.9G            
├─sda1 ESP     ESP         49.8G /boot/efi  D966-440A
├─sda2         System      30.3G /          5c1e1a3f-261f-4da5-a0c2-8f479b3039de
├─sda3 ISO     ISO         20.5G /media/fre ab916e15-8a74-4d6e-a0b1-32718a505dc7
└─sda4 root2   root2       25.4G            85a3d0a5-d4f8-473e-b89c-24c2cba6631a
sdb                       931.5G            
├─sdb1 ESP_B   EFI System Partition
│                          48.9G            F496-1330
├─sdb2 zesty   zesty       30.3G            a9bd9a65-bc8c-41b1-95b1-2dceb66b2652
├─sdb3 ISO_b   ISO_b       49.8G            c395f36d-5e02-4913-a904-e336054b2eff
├─sdb4 backup_b
│              backup_b    49.8G /media/fre dd4e4a2e-4785-4441-91b0-28234b98e625
├─sdb5         server      30.3G            b76dc590-99a3-4e34-af35-e0dd43507232
├─sdb6 data    data       205.1G /mnt/data  f9537995-8b44-4abb-b5fb-ec27023f57b2
├─sdb7                      2.1G [SWAP]     3ef43e7c-8a35-4f8b-bc73-c91d6098d4cd
├─sdb8         yakkety     25.4G            6c042846-fc6c-4f5b-80fc-7aa678cf09b7
└─sdb9 Fedora  Fedora      25.4G            5326d262-26af-4b38-a523-b0f4d261f1a4

[Mike Krall]

'Dennis N'...

Since running Manjaro, every time using 'Thunar Root', a very short time later my laptop fan kicks up... then up again. I'm guessing this is the endless writing going on. Whether I can "fix" that or not, I don't know. The number of times I need to go into "Thunar Root" is fairly high, compared to the Ubuntu's. I'm wondering a thing... pages back you showed me to editing /etc/fstab to ease getting around... replaced "umask=0077" with "defaults".

My Ubuntu /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>
# / was on /dev/sda2 during installation
UUID=0f47f885-3e8b-475b-9082-2ea2c05ff732 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=B70F-1399  /boot/efi       vfat    defaults      0       1
# swap was on /dev/sda3 during installation
UUID=a64147fb-9025-46ee-b704-c6b7877d28c7 none            swap    sw              0       0
# /mnt/data was on /dev/sda4 during installation
UUID=a3c5362b-1fb9-44b9-8afb-050980ea65c2 /mnt/data ext4 auto,users,rw,relatime 0 2

This is my Manjaro /etc/fstab (edited to get things labeled... uncommented lines identical to /fstab.backup - the original):

# /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>
# /boot/efi was on /dev/sda1 during installation 
UUID=B70F-1399                            /boot/efi      vfat    defaults,noatime 0 2
# / was on /dev/sda8 during installation
UUID=988844a7-a4ec-40ac-b12f-05724ca4c899 /              ext4    defaults,noatime,discard 0 1
# swap was on /dev/sda3 during installation
UUID=a64147fb-9025-46ee-b704-c6b7877d28c7 swap           swap    defaults,noatime,discard 0 0
# /mnt/data was on /dev/sda4 during installation
UUID=a3c5362b-1fb9-44b9-8afb-050980ea65c2 /mnt/data ext4 auto,users,rw,relatime 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

When I first saw the 'defaults' in the '/boot/efi' line, I thought it would act like switching the Ubuntu's 'umask=0077' to 'defaults' but it doesn't seem to. Is there something else needing done?

Mike

Edit: Forgot to post again... from last night. Looks like I'm about half-trained to it... =[

[Mike Krall]

Thank you, 'oldfred'...

Mike

[Dennis N]

I'm wondering a thing... pages back you showed me to editing /etc/fstab to ease getting around... replaced "umask=0077" with "defaults"...When I first saw the 'defaults' in the '/boot/efi' line, I thought it would act like switching the Ubuntu's 'umask=0077' to 'defaults' but it doesn't seem to. Is there something else needing done?

For me, 'defaults' in the /boot/efi line gives the same permissions for folders and files in the EFI system partition in both OSes: rwxr-xr-x

[Mike Krall]

For me, 'defaults' in the /boot/efi line gives the same permissions for folders and files in the EFI system partition in both OSes: rwxr-xr-x

Thank you, 'Dennis N'...