[Touch-packages] [Bug 1854590] Re: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)
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 Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1854590 Title: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal) Status in xkeyboard-config package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1854590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported
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 Touch seeded packages, which is subscribed to network-manager in Ubuntu. 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
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 Touch seeded packages, which is subscribed to unattended-upgrades in 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 Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp