[Bug 1854590] Re: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)

[Jackalux]

Duly reported upstream at https://gitlab.freedesktop.org/xkeyboard-
config/xkeyboard-config/issues/193

** Bug watch added: 
gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #193
   https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/193

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854590

Title:
  No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately
  equal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1854590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854590] [NEW] No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)

[Jackalux]

Public bug reported:

I don't know much, so forgive me if I use the wrong terminology.

Problem:
There is no ComposeKey mapping for the symbols ≈ (Unicode 2248) and ≅ (Unicode 
2248) in Compose Tables.

Details:
According to  https://help.ubuntu.com/community/ComposeKey  the files such as  
/usr/share/X11/locale/en_US.UTF-8/Compose  have all ComposeKey combinations to 
type special symbols, characters and graphemes.
Two standard graphemes (≈ and ≅) seem to be missing from multiple compose files 
although their negated versions (are present mapped to compositions

Solution?!: I propose this (but wouldn't know how to commit it except by filing 
a bug - if it's straightforward to improve Linux, then please tell me how!  I'd 
love to commit something to the code!
I added these lines to a copy of the  compose  file that I made at ~/.Xcompose
I propose that they should be added to the multiple, original  Compose  files 
in:
  /usr/share/X11/locale/en_US.UTF-8/Compose
  /usr/share/X11/locale/iso8859-1/Compose
  /usr/share/X11/locale/iso8859-15/Compose
 etc etc etc

# _Added by Jackalux_
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
 : "≈"   U2248 # ALMOST EQUAL TO
# End of Jackalux's additions


Notes:
The list at 
https://www.x.org/releases/X11R7.7/doc/libX11/i18n/compose/en_US.UTF-8.html 
also misses combinations for ≈ and ≅ .   Perhaps that should be updated too if 
it is a reference list.

I also wanted to add:
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
But I've realised that they create clashes with other compositions, as the 
composition forms before the ComposeKey is released.
If this can be corrected and added at the same time, then that would be amazing 
as I don't know how to access the actual compositions listed for those 
characters.

Co-operatively,
Jackalux

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854590

Title:
  No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately
  equal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1854590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833556] Re: Default, encrypted install runs out of /boot space after 2 months

[Jackalux]

Hi again,
After an automatic update it's about to happen again (I got a low disk space 
warning for /boot) so I'll list details and see what happens.

/boot$ ls -a -h -l
total 208M
drwxr-xr-x  4 root root 1.0K Jun 29 10:52 .
drwxr-xr-x 24 root root 4.0K Jun 29 10:51 ..
-rw-r--r--  1 root root 213K May 15 13:48 config-4.15.0-51-generic
-rw-r--r--  1 root root 213K Jun  4 21:33 config-4.15.0-52-generic
-rw-r--r--  1 root root 213K Jun 24 10:39 config-4.15.0-54-generic
drwxr-xr-x  5 root root 1.0K Jun 29 10:53 grub
-rw-r--r--  1 root root  57M Jun 21 18:21 initrd.img-4.15.0-51-generic
-rw-r--r--  1 root root  57M Jun 29 10:52 initrd.img-4.15.0-52-generic
-rw-r--r--  1 root root  57M Jun 29 10:52 initrd.img-4.15.0-54-generic
drwx--  2 root root  12K May 10 11:01 lost+found
-rw-r--r--  1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw---  1 root root 3.9M May 15 13:48 System.map-4.15.0-51-generic
-rw---  1 root root 3.9M Jun  4 21:33 System.map-4.15.0-52-generic
-rw---  1 root root 3.9M Jun 24 10:39 System.map-4.15.0-54-generic
-rw---  1 root root 8.0M May 15 15:11 vmlinuz-4.15.0-51-generic
-rw---  1 root root 8.0M Jun  4 21:39 vmlinuz-4.15.0-52-generic
-rw---  1 root root 8.0M Jun 24 11:21 vmlinuz-4.15.0-54-generic

Free space is listed as 7.1MB

Results of sudo apt autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED
  linux-headers-4.15.0-51 linux-headers-4.15.0-51-generic
  linux-image-4.15.0-51-generic linux-modules-4.15.0-51-generic
  linux-modules-extra-4.15.0-51-generic
0 to upgrade, 0 to newly install, 5 to remove and 7 not to upgrade.
After this operation, 334 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 233764 files and directories currently installed.)
Removing linux-headers-4.15.0-51-generic (4.15.0-51.55) ...
Removing linux-headers-4.15.0-51 (4.15.0-51.55) ...
Removing linux-modules-extra-4.15.0-51-generic (4.15.0-51.55) ...
Removing linux-image-4.15.0-51-generic (4.15.0-51.55) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-4.15.0-51-generic
/etc/kernel/postrm.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-54-generic
Found initrd image: /boot/initrd.img-4.15.0-54-generic
Found linux image: /boot/vmlinuz-4.15.0-52-generic
Found initrd image: /boot/initrd.img-4.15.0-52-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Removing linux-modules-4.15.0-51-generic (4.15.0-51.55) ...

Not all of this 334MB has been cleared from /boot
Here is another file listing:

total 139M
drwxr-xr-x  4 root root 1.0K Jun 29 11:07 .
drwxr-xr-x 24 root root 4.0K Jun 29 10:51 ..
-rw-r--r--  1 root root 213K Jun  4 21:33 config-4.15.0-52-generic
-rw-r--r--  1 root root 213K Jun 24 10:39 config-4.15.0-54-generic
drwxr-xr-x  5 root root 1.0K Jun 29 11:07 grub
-rw-r--r--  1 root root  57M Jun 29 10:52 initrd.img-4.15.0-52-generic
-rw-r--r--  1 root root  57M Jun 29 10:52 initrd.img-4.15.0-54-generic
drwx--  2 root root  12K May 10 11:01 lost+found
-rw-r--r--  1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw---  1 root root 3.9M Jun  4 21:33 System.map-4.15.0-52-generic
-rw---  1 root root 3.9M Jun 24 10:39 System.map-4.15.0-54-generic
-rw---  1 root root 8.0M Jun  4 21:39 vmlinuz-4.15.0-52-generic
-rw---  1 root root 8.0M Jun 24 11:21 vmlinuz-4.15.0-54-generic

There is now 79.5MB in /boot  Is this enough.  I'm suggesting not since
this keeps recurring.  Autoremove may indeed be working fine, but it
seems to me that the default installer has set the /boot partition size
value inappropriately low.  Am I right?

I suspect that when I posted the OP, that autoremove merely couldn't
remove enough space for a bulky update, rather than 'didn't work' as I
wrote.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833556

Title:
  Default, encrypted install runs out of /boot space after 2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833556] Re: Default, encrypted install runs out of /boot space after 2 months

[Jackalux]

Thanks very much for the reply, Brian.

I'm really grateful for the work that's gone into this as it used to be
a bane of my previous install (12.04).  That was merely an encrypted
/home with carefully researched and chosen (guessed) partition sizes;
this however is a default, entirely encrypted option of 18.04.

>From memory, I saw only one old kernel (I never see the purple boot menu
to select a kernel) and was amazed that I could be out of space.

Screenshot of folder properties for /boot from Nautilus is attached (I'm
obvs a Noob after all these years)

Current folder listing is:
/boot$ ls -a -h -l
total 143M
drwxr-xr-x  4 root root 1.0K Jun 21 18:22 .
drwxr-xr-x 24 root root 4.0K Jun 21 18:19 ..
-rw-r--r--  1 root root 213K May  6 17:59 config-4.15.0-50-generic
-rw-r--r--  1 root root 213K May 15 13:48 config-4.15.0-51-generic
-rw-r--r--  1 root root 213K Jun  4 21:33 config-4.15.0-52-generic
drwxr-xr-x  5 root root 1.0K Jun 21 18:22 grub
-rw-r--r--  1 root root  57M Jun 21 18:21 initrd.img-4.15.0-51-generic
-rw-r--r--  1 root root  57M Jun 21 18:22 initrd.img-4.15.0-52-generic
drwx--  2 root root  12K May 10 11:01 lost+found
-rw-r--r--  1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r--  1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw---  1 root root 3.9M May  6 17:59 System.map-4.15.0-50-generic
-rw---  1 root root 3.9M May 15 13:48 System.map-4.15.0-51-generic
-rw---  1 root root 3.9M Jun  4 21:33 System.map-4.15.0-52-generic
-rw---  1 root root 8.0M May 15 15:11 vmlinuz-4.15.0-51-generic
-rw---  1 root root 8.0M Jun  4 21:39 vmlinuz-4.15.0-52-generic

Partition info from GParted:
sda  = 698.64 GiB
sda1 = 243.00 MiB  /boot  ext2
sda2 = 698.40 GiB extended
sda5 = 698.40 GiB  ubuntu-vg  [Encrypted] lvm2 pv


I may always be making a mistake or misremembering something but I'm being as 
thorough as I know how.  I hope I'm not wasting any of your time!

Cheers

** Attachment added: "Nautilus Screenshot from 2019-06-21 21-15-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+attachment/5272224/+files/Nautilus%20Screenshot%20from%202019-06-21%2021-15-22.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833556

Title:
  Default, encrypted install runs out of /boot space after 2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833556] Re: Default, encrypted install runs out of /boot space after 2 months

[Jackalux]

** Description changed:

  This bug is about the installer defaults, not this symptom of the bug.
  
- I installed a fresh install of 18.04 on a laptop with a 750GB HDD.  The
- update-manager reported that I'd ran out of space within 2 months and
- could not perform updates.
+ I installed a fresh encrypted* install of 18.04 on a laptop with a 750GB HDD. 
 The update-manager reported that I'd ran out of space within 2 months and 
could not perform updates.
+ * AFAIK, encrypted installs place /boot in a separate partition
  
  'apt autoremove' didn't remove anything and only running the advice from
  http://tuxtweaks.com/2010/10/remove-old-kernels-in-ubuntu-with-one-
  command/ worked, which seems to leave me with no backup kernel.
  
  This would turn off Noobs who want something that doesn't require almost
  immediate, then ongoing, tech intervention.
  
  Does the installer need to change the allocated size of /boot in new
  installs?  Noobs will run back to Windoze if they encounter this... it
  looks like a fresh install has a shelf life of two months unless you
  learn to fiddle around under the bonnet/hood.
  
  Blessed are the coders!
  J

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833556

Title:
  Default, encrypted install runs out of /boot space after 2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833556] [NEW] Default, encrypted install runs out of /boot space after 2 months

[Jackalux]

Public bug reported:

This bug is about the installer defaults, not this symptom of the bug.

I installed a fresh install of 18.04 on a laptop with a 750GB HDD.  The
update-manager reported that I'd ran out of space within 2 months and
could not perform updates.

'apt autoremove' didn't remove anything and only running the advice from
http://tuxtweaks.com/2010/10/remove-old-kernels-in-ubuntu-with-one-
command/ worked, which seems to leave me with no backup kernel.

This would turn off Noobs who want something that doesn't require almost
immediate, then ongoing, tech intervention.

Does the installer need to change the allocated size of /boot in new
installs?  Noobs will run back to Windoze if they encounter this... it
looks like a fresh install has a shelf life of two months unless you
learn to fiddle around under the bonnet/hood.

Blessed are the coders!
J

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833556

Title:
  Default, encrypted install runs out of /boot space after 2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1833556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[Jackalux]

Grazie mille!

Sadly, I'm a very long way from being able to handle the creation of the
GUI side... it's too many decades since I used to programme.
Respect to the coders!

On 14 November 2017 at 09:08, Daniele Napolitano 
wrote:

> This was fixed upstream with Network Manager 1.10:
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/
> tree/NEWS?h=nm-1-10
>
>
> Now we need a good GUI to configure all the WPS stuff
> (gnome-control-center).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/388553
>
> Title:
>   Wi-Fi Protected Setup (WPS) not supported
>
> Status in Ayatana Design:
>   New
> Status in NetworkManager:
>   In Progress
> Status in network-manager package in Ubuntu:
>   Triaged
>
> Bug description:
>   As the title the Wi-Fi Protected Setup (WPS) is not supported by
>   NetworkManager (but is supported by wpa_supplicant).
>
>   The WPS WI-Fi standard is implementated in various newer access points
>   and allow user to configure the access point in just a few of steps
>   and do all configuring process very simple.
>
>   Specifications: http://www.wi-fi.org/wifi-protected-setup/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/388553

Title:
  Wi-Fi Protected Setup (WPS) not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1722932] Re: libreoffice-core 5.4.2 breaks libreoffice-calc, libreoffice-draw, libreoffice-impress ...

[Jackalux]

And both Ubuntu and LibreOffice bugs are getting 'Resolved' as 'It's
their fault'!

Anyone?   Err... me!  Just worked it out!

Solution in fellow Noobspeak:

1. Run Synaptic Package Manager
If not sure how, press the Windows/Super key then type Synaptic and 
click the appropriate icon
2. Enter your password when prompted
3. Click On The 'Status' button.  Above that, select 'Broken Dependencies'
4. To the right, Select all four affected LibreOffice Packages
5. Right click them and choose 'Mark For Upgrade' option
6. Click the big Apply button, above.

Unless the tiger is hiding, waiting to bite my hubristic backside, I
think that this solves it.

If it hasn't worked, perhaps you'd deseleted the LibreOffice PPA in the
Depositary List.  Reenable it and start again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722932

Title:
  libreoffice-core 5.4.2 breaks  libreoffice-calc,  libreoffice-draw,
  libreoffice-impress ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1722932/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1722932] Re: libreoffice-core 5.4.2 breaks libreoffice-calc, libreoffice-draw, libreoffice-impress ...

[Jackalux]

Reported to LibreOffice as bug as well.

See  https://bugs.documentfoundation.org/show_bug.cgi?id=113269

** Bug watch added: Document Foundation Bugzilla #113269
   https://bugs.documentfoundation.org/show_bug.cgi?id=113269

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722932

Title:
  libreoffice-core 5.4.2 breaks  libreoffice-calc,  libreoffice-draw,
  libreoffice-impress ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1722932/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jackalux]

I don't have hardware that I imagine will run 16.xx so need this
addressed on older LTS versions.

My output for...
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
 ... was 120 lines long!  I had to teach myself scripting to delete them all 
manually.  I only discovered the error after a different Linux machine I 
created (with a separate /boot) ran into the bug.

Deleting this junk freed 10GB of total disk space.

This is too much to ask of novice users and will stop Linux being more
widely adopted.  I'm not a complete Noob but this was annoying to deal
with... it will be impossible for others.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs