[Touch-packages] [Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
** Also affects: baltix-default-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in Default settings and artwork for Baltix OS: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Status in systemd package in Fedora: Fix Released Bug description: [Impact] The "swap kill" side of systemd-oomd has caused unexpected behavior for desktop users. A user's browser, desktop session, or some other desktop application may be killed by systemd-oomd when SwapUsedLimit is reached, but system performance otherwise appears unaffected. This leaves users confused as to why their application was killed, and has a negative impact on their desktop experience. For now, let's disable the swap kill functionality by default. [Test Plan] On Jammy desktop, check the ManagedOOMSwap property on -.slice: $ systemctl show -- "-.slice" | grep "^ManagedOOMSwap" ManagedOOMSwap=kill # After the fix, this should print ManagedOOMSwap=auto [Where problems could occur] Disabling swap kill by default means that users may experience degraded system performance due to high swap usage, because systemd- oomd will no longer act on cgroups with high swap usage. [Other Info] If a user wishes to restore the original systemd-oomd behavior, they can do so by creating the following overrides file: $ cat /etc/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf [Slice] ManagedOOMSwap=kill [Original Description] Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1972159/+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 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"
@eugenesan Is this bug fixed in your version of zram-config - https://git.launchpad.net/~eugenesan/+git/zram-config ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1978738 Title: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded" Status in systemd package in Ubuntu: Invalid Status in zram-config package in Ubuntu: Fix Released Bug description: Problem summary: I've installed the zram-config package. By default it creates a zram swap device with half the physical memory size of the system. For instance, in an 8GB RAM system: # swapon NAME TYPE SIZE USED PRIO /dev/zram0 partition 3,8G 1M5 #zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 3,8G 496K 74,9K 376K 4 [SWAP] The problem is that when systemd-oomd.service is started during boot it doesn't detect that zram swap device because zram-config.service is started later. So when systemd-oomd.service was started the zram device didn't exists yet. This is the message shown during boot: systemd-oomd[587]: Swap is currently not detected; memory pressure usage will be degraded If you restart systemd-oomd.service after boot it's correctly started because zram-config.service was previously loaded and zram device exists. So I think it's just a matter of dependencies during boot process; it's necessary to make zram-config.service be started before systemd-oomd.service (or to make systemd-oomd.service be restarted when zram-config.service is started). Aditional info: --- # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 249.11-0ubuntu3.1 Candidato: 249.11-0ubuntu3.1 Tabla de versión: *** 249.11-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # apt-cache policy zram-config zram-config: Instalados: 0.7build1 Candidato: 0.7build1 Tabla de versión: *** 0.7build1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+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 1864215] Re: Please add webp loader to gdk-pixbuf
** Also affects: gdk-pixbuf (Baltix) Importance: Undecided Status: New ** Changed in: gdk-pixbuf (Baltix) Milestone: None => baltix-18.04 ** Changed in: gdk-pixbuf (Baltix) Importance: Undecided => Low ** Changed in: gdk-pixbuf (Baltix) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues #103 https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/103 ** Also affects: gdk-pixbuf via https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/103 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Unknown Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Baltix: Triaged Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1887507] [NEW] Please remove old libgtk2-perl from Recommends and drop dependency against gnome-icon-theme
Public bug reported: Could you please remove old libgtk2-perl from Recommends and drop the dependency against gnome-icon-theme? libgtk2-perl and gnome-icon-theme is deprecated for gtk3 and replaced by adwaita-icon-theme. If I'm not wrong, gdebi only uses one icon from gnome-icon-theme, gnome-mime-application-x-deb, this icon is not available in adwaita-icon-theme. BUT, can be replaced by the package-x-generic (which is also available in other icon themes). On my machine this is the same icon as for the .deb and .udeb files. An explicit dependency against adwaita-icon-theme should probably be avoided as libgtk3 will already pull it. ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Affects: gdebi (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #831050 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831050 ** Also affects: gdebi (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831050 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1887507 Title: Please remove old libgtk2-perl from Recommends and drop dependency against gnome-icon-theme Status in gdebi package in Ubuntu: New Status in gdebi package in Debian: Unknown Bug description: Could you please remove old libgtk2-perl from Recommends and drop the dependency against gnome-icon-theme? libgtk2-perl and gnome-icon-theme is deprecated for gtk3 and replaced by adwaita-icon-theme. If I'm not wrong, gdebi only uses one icon from gnome-icon-theme, gnome-mime-application-x-deb, this icon is not available in adwaita-icon-theme. BUT, can be replaced by the package-x-generic (which is also available in other icon themes). On my machine this is the same icon as for the .deb and .udeb files. An explicit dependency against adwaita-icon-theme should probably be avoided as libgtk3 will already pull it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1887507/+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 1759014] Re: Netplan has no way to control DHCP client
** Also affects: baltix-default-settings
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
Status in Default settings and artwork for Baltix OS:
New
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Bug watch added: Debian Bug tracker #951387 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951387 ** Also affects: console-setup (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951387 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Committed Status in console-setup package in Debian: Unknown Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
This patch replaces not intuitive secondary lt(us) layout with us(altgr- intl), which uses majority of Lithuanian users as secondary layout. ** Patch added: "Patch against console-setup-1.194ubuntu2/debian/keyboard-configuration.config - fixes LT layout" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+attachment/5328000/+files/keyboard-configuration.config-LT-layout.patch ** Description changed: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" - I will attach a patch to debian/keyboard-configuration.config file which + I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue ** Tags added: patch ** Summary changed: - Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity + [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg- reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Tags added: bionic focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap
Current situation about this issue is described and fixed in bug #1863001 ** Changed in: baltix Status: New => Triaged ** Changed in: baltix Status: Triaged => In Progress -- 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/718693 Title: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap Status in xkeyboard-config package in Ubuntu: New Status in Baltix: In Progress Bug description: Binary package hint: xkeyboard-config Main lithuanian layout has no EURO symbol. Main lithuanian layout should have EURO symbol on key "e" (alt gr + e), like other layouts "Lithuanian US", "Lithuanian IBM", "Lihuanian Standard" has it on key "e". Windows OS it is also on key "e". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/718693/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Summary changed: - Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration + Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration
When user chooses Lithuanian keyboard layout then XKB variables in /etc/default/keyboard should set to: XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" I'm attaching screenshot of English US (intl with altGR) keyboard layoyut, this layout is most usefull for Lithuanians, because it contains Euro (€) and other symbols, often used in Lithuania. ** Attachment added: "Screenshot of English US (intl with altGR) keyboard layoyut" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+attachment/5327742/+files/US%28altGR%20intl%29%20keyboard%20layoyut.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863001] [NEW] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration
Public bug reported: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1644996] Re: logrotate config uses syslog group
Steve Langasek (vorlon), yes lots of Ubuntu users, including me have lots of containers (based on ubuntu-minimal - Ubuntu developers created "Minimal" LXC container image without rsyslog package by default), see ubuntu-18.04-minimal-cloudimg-amd64.manifest: https://cloud-images.ubuntu.com/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg- amd64.manifest Also see these posts and work-arounds for example: http://www.markusz.io/posts/2017/09/29/logrotate/#known-issues https://github.com/sameersbn/docker-gitlab/issues/1544#issuecomment-373366621 https://gitlab.timmertech.nl/docker/gitlab/commit/428e37a821f94af03e72201420ee2874be8834b4 ** Bug watch added: github.com/sameersbn/docker-gitlab/issues #1544 https://github.com/sameersbn/docker-gitlab/issues/1544 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Similar issue appears when zram swap is used, see bug #1781746 This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1644996] Re: logrotate config uses syslog group
@brian-murray , why you added "rls-bb-notfixing"? logrotate doesn't work at all in lots lxd containers because of this bug, lots of users are affected, why don't accept this one line patch into LTS releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
** Tags removed: amd64 ** Tags added: cosmic rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811447/+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 1644996] Re: logrotate config uses syslog group
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1644996] Re: logrotate config uses syslog group
Dimitri John Ledkov, thanks for fixing, it would be nice if fix appear in LTS releases too, at least in Ubuntu 18.04 "Bionic" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1644996] Re: logrotate config uses syslog group
This bug doesn't exist in Debian, it's only Ubuntu related workaround for Ubuntu 14.04 (Trusty), see LP bug #1258202 logrotate (3.8.6-1ubuntu2) trusty; urgency=low * debian/logrotate.conf: use group 'syslog' by default when rotating logs, otherwise logrotate will refuse to rotate logs in /var/log whose owning group is now syslog instead of root. LP: #1258202. -- Steve LangasekThu, 05 Dec 2013 10:35:47 -0800 Ubuntu developers, please change /etc/logrotate.conf line su root syslog to su root adm Or maybe we can remove this line from /etc/logrotate.conf , because in Debian logrotate package there are no such line since 2013 ... ** Tags added: bionic regression-release xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Confirmed Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
This issue is fixed in Debian since July 2018 - initramfs-tools version 0.132, please accept this simple, 3 lines patch from Debian into Ubuntu 18.04 : https://salsa.debian.org/kernel-team/initramfs- tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d Look at bug #1781746 for more info. ** Bug watch added: Debian Bug tracker #861228 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Unknown Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811447/+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 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap
What can I do to speed-up inclusion of simple, 3 lines patch from Debian into Ubuntu 18.04 LTS ? https://salsa.debian.org/kernel-team/initramfs- tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap
** Changed in: baltix-default-settings Status: New => Confirmed ** Changed in: baltix-default-settings Importance: Undecided => High ** Changed in: baltix-default-settings Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap
** Description changed: - Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed or swap is encrypted. + [Impact] + + Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. + Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) + + This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS + https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d + + [Test Case] + Install zram-config package and regenerate and initrd, for example with + sudo update-initramfs -u + When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) - I: Set the RESUME variable to override this.###.] + I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. - To disable this (as resuming from swap is not possible with an encrypted - swap, and I don't use hibernation anyway), I modified this file: /etc - /initramfs-tools/conf.d/resume. In this file, a line with RESUME=none - (instead of the UUID that was here) will disable waiting for a resume - device. + [Regression Potential] - Run sudo update-initramfs -u to apply the changes. + None, patch simply adds case for /dev/zram*: - Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10 + 60case "$resume_auto" in + 61/dev/zram*) + 62ephemeral=true + 63;; + 64esac + + + [Other Info] + Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line + RESUME=none + (instead of the UUID that was here) will disable waiting for a resume device. + and run sudo update-initramfs -u to apply the changes. ** Summary changed: - Slow startup with zram-config installed (/dev/zram0) or encrypted swap + [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: New Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Unknown Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage
[Touch-packages] [Bug 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap
This issue is fixed in Debian, initramfs-tools version 0.132, please accept this simple, 3 lines patch from Debian into Ubuntu 18.04 https://salsa.debian.org/kernel-team/initramfs- tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d ** Patch added: "Patch from Debian initramfs-tools 0.132 to fix booting when zram swap is enabled" https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1781746/+attachment/5206679/+files/312393b0cf1231125eeff3d1a2b6b778a935c21d.diff ** Tags added: bionic patch patch-accepted-debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: New Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: New Status in initramfs-tools package in Debian: Unknown Bug description: Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed or swap is encrypted. When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume. In this file, a line with RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. Run sudo update-initramfs -u to apply the changes. Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap
** Also affects: zram-config (Ubuntu) Importance: Undecided Status: New ** Also affects: baltix-default-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: New Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: New Status in initramfs-tools package in Debian: Unknown Bug description: Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed or swap is encrypted. When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume. In this file, a line with RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. Run sudo update-initramfs -u to apply the changes. Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: Slow startup with encrypted swap
** Bug watch added: Debian Bug tracker #861228 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 Importance: Unknown Status: Unknown ** Summary changed: - Slow startup with encrypted swap + Slow startup with zram-config installed (/dev/zram0) or encrypted swap ** Description changed: - The problem was due to my swap being encrypted. So the local-premount - script in initramfs was waiting for a swap device that was not - available, until it timed out. The relevant message was gave up waiting - for suspend/resume device. + Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed or swap is encrypted. + When generating initrd I get this message in terminal: + + I: The initramfs will attempt to resume from /dev/zram0 + I: (UUID=e380356c-767e-4265-98da-8be62ad28569) + I: Set the RESUME variable to override this.###.] + + So the local-premount script in initramfs was waiting for a swap device + that was not available, until it timed out. The relevant message was + gave up waiting for suspend/resume device. To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc /initramfs-tools/conf.d/resume. In this file, a line with RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. Run sudo update-initramfs -u to apply the changes. Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: New Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: New Status in initramfs-tools package in Debian: Unknown Bug description: Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed or swap is encrypted. When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume. In this file, a line with RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. Run sudo update-initramfs -u to apply the changes. Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1776074] Re: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)
indicator-datetime is the only package in Ubuntu 18.04 and older that recommends/depends on ubuntu-touch-sounds, no more packages uses ubuntu- touch-sounds, so, please make usage of ubuntu-touch-sounds in indicator- datetime optional for Desktop systems ** Changed in: baltix-default-settings Status: New => In Progress ** Changed in: baltix-default-settings Importance: Undecided => Medium ** Changed in: baltix-default-settings Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1776074 Title: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead) Status in Default settings and artwork for Baltix OS: In Progress Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome- flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+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 1776074] [NEW] indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)
Public bug reported: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome-flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. ** Affects: baltix-default-settings Importance: Undecided Status: New ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: baltix-default-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1776074 Title: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead) Status in Default settings and artwork for Baltix OS: New Status in indicator-datetime package in Ubuntu: New Bug description: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome- flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+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 1736618] Re: debconf: Switch GNOME frontend to gtk3
** Changed in: baltix-default-settings Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1736618 Title: debconf: Switch GNOME frontend to gtk3 Status in Default settings and artwork for Baltix OS: Fix Committed Status in Debconf: Fix Released Status in debconf package in Ubuntu: Fix Released Bug description: Please switch debconf's GNOME backend to gtk3. debconf's GNOME backend is one of the last 3 things to pull gtk2 in to a default Ubuntu 18.04 install (without extra input methods). The other two are Firefox and Thunderbird which have fixes in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1736618/+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 1736618] Re: debconf: Switch GNOME frontend to gtk3
** Also affects: baltix-default-settings Importance: Undecided Status: New ** Changed in: baltix-default-settings Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) ** Changed in: baltix-default-settings Importance: Undecided => High ** Changed in: baltix-default-settings Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1736618 Title: debconf: Switch GNOME frontend to gtk3 Status in Default settings and artwork for Baltix OS: In Progress Status in Debconf: Fix Released Status in debconf package in Ubuntu: Fix Released Bug description: Please switch debconf's GNOME backend to gtk3. debconf's GNOME backend is one of the last 3 things to pull gtk2 in to a default Ubuntu 18.04 install (without extra input methods). The other two are Firefox and Thunderbird which have fixes in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1736618/+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 1743873] Re: rsync version for xenial
Updating rsync to 3.1.2 would also fix Ubuntu bug #1707136 (Rsyncd doesn't start at boot in Ubuntu 16.04), to fix this problem user should run this manually: systemctl enable rsync ** Bug watch added: Debian Bug tracker #764616 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764616 ** Also affects: rsync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1743873 Title: rsync version for xenial Status in rsync package in Ubuntu: Confirmed Status in rsync package in Debian: Unknown Bug description: Any chance that rsync could be updated to 3.1.2 for xenial? The --backup-dir option in 3.1.1 doesn't work properly - it creates empty directories even when no files need to be put in them. Thanks, -Jeff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1743873/+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 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: Confirmed Status in rsync package in Debian: Fix Released Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+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 1726395] [NEW] gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE
Public bug reported: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726395 Title: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE Status in ubuntu-meta package in Ubuntu: New Bug description: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726395/+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 1711851] Re: Disable MAC address randomization on Live system
** Summary changed: - bad default setting + Disable MAC address randomization on Live system -- 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/1711851 Title: Disable MAC address randomization on Live system Status in network-manager package in Ubuntu: Confirmed Bug description: I'm using the pre-release version of artful 17.10 and network manager 1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to use the random mac address feature of network manager, which doesn't allow certain wifi cards/ routers to work together. See Debian bug 836351. I think this feature should be disabled on a live cd, because it isn't fixable during an install and it might cause a user just to give up and not install Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Sat Aug 19 14:00:17 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-19 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170818) IpRoute: default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-08-19T13:51:03.103665 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE 556F02 72b161b9-3dad-4583-ae59-1d3e0402b37e 802-11-wireless 1503165502 Sat 19 Aug 2017 01:58:22 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlxec086b17f6d1 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 1d860881-8bc6-3d0d-8455-2b15a87f1307 802-3-ethernet 1503165498 Sat 19 Aug 2017 01:58:18 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxec086b17f6d1 wifi connected /org/freedesktop/NetworkManager/Devices/3 556F02 72b161b9-3dad-4583-ae59-1d3e0402b37e /org/freedesktop/NetworkManager/ActiveConnection/1 eno1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1711851/+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 1661329] Re: Wifi password not taken into account if not entered rapidly
Maybe this bug is a duplicate of LP bug #1650835 (wifi association times out while typing password)? -- 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/1661329 Title: Wifi password not taken into account if not entered rapidly Status in network-manager package in Ubuntu: New Bug description: Hi, We install ubuntu/mint to numerous people and we got multiple reports that the wifi password was not taken into account. We managed to reproduce it by 1 - Select your wifi network 2 - Enter a fake password (Just to simulate a user error not entering well his wifi password) 3 - Obviously here we cannot connect, so we wait 4 - Password is asked a second time, and we enter it without error but we take our time to do so ( or wait some time after ). By taking our time we simulate people who are not fluent with their keyboard. 5 - Wait to connect 6 - Password is asked a third time. 7 - Here if we go into the properties of the wifi (Applet > Modify > Modify) and check the password… the first fake password is still there Nice day It might be a double of this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1219171 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1661329/+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 964705] Re: System policy prevents modification of network settings for all users
It seems Debian fix is simply to allow users from netdev (and sudo) group add/change system-wide NetworkManager connections, this fix is added in network-manager 0.9.4.0-7 and is merged in Ubuntu, look at /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla [Adding or changing system-wide NetworkManager connections] Identity=unix-group:netdev;unix-group:sudo Action=org.freedesktop.NetworkManager.settings.modify.system So, main problem is that GNOME-Shell users aren't added to netdev group by default? Walter Lapchynski (wxl) wrote on 2015-06-29:#38 > Mathieu, it doesn't seem that the upstream fix in Debian ever got merged into > Ubuntu. > Is there a reason for this? -- 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/964705 Title: System policy prevents modification of network settings for all users Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: Fix Released Status in network-manager package in openSUSE: Fix Released Bug description: This seems like a regression? The screen shot is at http://thesii.org/Screenshot.jpg The nearest link I can find is from the forum area at http://ubuntuforums.org/showthread.php?p=1146 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 19:36:45 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/964705/+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 1562002] Re: Nautilus: lag after choosing action in top right menu
I'm confirming, that gtk+3.0 version 3.18.9-1ubuntu3.3 from xenial- proposed fixes nautilus (and GNOME-Desktop) freezing issue after clicking any action in the Nautilus menu button on the right (tested with "Invert selection", "New Tab", "Select All"). Tested in GNOME- flashback and GNOME Shell sessions. adminas@K101:~$ dpkg -s libgtk-3-0 |grep Ver Version: 3.18.9-1ubuntu3.3 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1562002 Title: Nautilus: lag after choosing action in top right menu Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: Fix Committed Bug description: # Impact This is known to affect Nautilus, but can potentially affect other applications too (the upstream bug has an example test app attached). See also the duplicate bug 1644393, which is another appearance of the same bug but with other symptoms. # Proposed Fix The proposed fix is an upstream commit taken from gtk-3-20 branch: https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1 # Test Case https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case. # Regression Potential The bug is fixed in GTK+ 3.20.9, so the fix was already present in the version that shipped with Yakkety. I am not aware of any regressions. - choosing action like New Tab, New Folder, Select Items Matching, will make nautilus lag (unresponsive) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 25 20:52:21 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+685+36'" InstallationDate: Installed on 2016-03-24 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1562002/+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 1661036] [NEW] nfsmount from klibc-utils doesn't support 'fsc' option
Public bug reported: I'm PXE-booting a Ubuntu 16.04 system, where I specify the kernel parameters as follows: root=/dev/nfs nfsroot=10.0.0.1:/srv/tftp/ubuntu-baltix,fsc ip=dhcp rw After I added fsc option to kernel command line I get the following error upon boot: nfsmount: bad option 'fsc' I need to use the mount option 'fsc' in order to use FS-cache functionality (the cachefilesd package.) Why doesn't nfsmount permit this option? (It works fine when you mount manually with mount -o fsc after booting up.) I changed nfsmount to mount.nfs in the file /usr/share/initramfs-tools/scripts/nfs and added mount.nfs from /sbin to the initramfs image (copied to the /usr/lib/klibc/bin folder) Then ran update-initramfs -u to update the initramfs image and now system boots without error. This problem exists in older Ubuntu releases too, see http://askubuntu.com/questions/23767/using-the-fsc-mount-option-with- nfsroot-kernel-parameter-to-allow-fs-cache ** Affects: klibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1661036 Title: nfsmount from klibc-utils doesn't support 'fsc' option Status in klibc package in Ubuntu: New Bug description: I'm PXE-booting a Ubuntu 16.04 system, where I specify the kernel parameters as follows: root=/dev/nfs nfsroot=10.0.0.1:/srv/tftp/ubuntu-baltix,fsc ip=dhcp rw After I added fsc option to kernel command line I get the following error upon boot: nfsmount: bad option 'fsc' I need to use the mount option 'fsc' in order to use FS-cache functionality (the cachefilesd package.) Why doesn't nfsmount permit this option? (It works fine when you mount manually with mount -o fsc after booting up.) I changed nfsmount to mount.nfs in the file /usr/share/initramfs-tools/scripts/nfs and added mount.nfs from /sbin to the initramfs image (copied to the /usr/lib/klibc/bin folder) Then ran update-initramfs -u to update the initramfs image and now system boots without error. This problem exists in older Ubuntu releases too, see http://askubuntu.com/questions/23767/using-the-fsc-mount-option-with- nfsroot-kernel-parameter-to-allow-fs-cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1661036/+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 1005209] Re: app-install-data-partner package is missing desktop and icon files
** Tags added: wily xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1005209 Title: app-install-data-partner package is missing desktop and icon files Status in app-install-data-partner package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in app-install-data-partner package in Baltix: In Progress Bug description: [Impact] * app-install-data-partner doesn't install any .desktop files, so the Canonical Partners sections in the Ubuntu Software Center and the Muon Software Center are empty. [Test Case] * Install app-install-data-partner * Open Ubuntu Software Center * In the software drop-down list, select Canonical Partners [Regression Potential] * The package hasn't been updated for Precise or Trusty, so any change would be positive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/app-install-data-partner/+bug/1005209/+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 490736] Re: mawk 1.3.3-17ubuntu2 incorrectly handles "/" in "[ ]" expressions
mawk in Ubuntu and Debian is 18 years, see LP bug #1332114
Many bugs of Mawk are fixed in a new upstream versions 1.3.4-2010-2015,
but the Debian maintainer does not want to update for an obscure reason.
We need to push here: http://bugs.debian.org/554167
** Bug watch added: Debian Bug tracker #554167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
** Also affects: mawk (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/490736
Title:
mawk 1.3.3-17ubuntu2 incorrectly handles "/" in "[ ]" expressions
Status in mawk package in Ubuntu:
Confirmed
Status in mawk package in Debian:
Unknown
Bug description:
Binary package hint: mawk
Description: Ubuntu 9.04
Release: 9.04
Package version: mawk 1.3.3-13ubuntu1
Whilst attempting to run a shell script to automate the build procedure for
an embedded platform I came across a parsing error in the mawk installation on
my Ubuntu 9.04 box. I followed this up with the script author, and then the
mawk maintainer, and determined that:
(a). The behavior of mawk 1.3.3-13ubuntu1 is incorrect
(b). The incorrect behavior exhibited by mawk 1.3.3-13ubuntu1 is not
exhibited by the upstream sources mawk-1.3.3-20090920 when built on my Ubuntu
box
The error case can be demonstrated using this script fragment:
for interpretter in gawk mawk;
do
echo "Running with $interpretter..."
echo
echo "diecimila.name=Arduino Diecimila, Duemilanove, or Nano w/ATmega168" | \
$interpretter -v FS== '{boardname=$2; gsub(/[^a-zA-Z0-9_,./():-]/, "",
boardname); print boardname }'
echo
done
When run using my system's mawk installation I get the following output:
Running with gawk...
ArduinoDiecimila,Duemilanove,orNanow/ATmega168
Running with mawk...
mawk: line 1: regular expression compile failed (bad class -- [], [^] or [)
[^a-zA-Z0-9_,.
mawk: line 1: syntax error at or near )
bash: echo: write error: Broken pipe
When run using the upstream mawk I get the following output:
Running with gawk...
ArduinoDiecimila,Duemilanove,orNanow/ATmega168
Running with ./mawk...
ArduinoDiecimila,Duemilanove,orNanow/ATmega168
For reference, I built the upstream mawk package as follows:
./compile && make
That is, I used whatever defaults the autoconf script picked for my
system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/490736/+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 26603] Re: String indexes are inconsistent with other awks
mawk in Ubuntu and Debian is 18 years, see LP bug #1332114
Many bugs of Mawk are fixed in a new upstream versions 1.3.4-2010-2015,
but the Debian maintainer does not want to update for an obscure reason.
We need to push here: http://bugs.debian.org/554167
** Bug watch added: Debian Bug tracker #554167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/26603
Title:
String indexes are inconsistent with other awks
Status in mawk package in Ubuntu:
Confirmed
Bug description:
The substr() function from within mawk does not function correctly. In
particular, the
substr(s,i,n) form returns n-1 characters, instead of n as required. To
demonstrate:
% echo "1234" | mawk '{print substr($0,0,3)}'
12
It should display "123"; this can be confirmed by using gawk instead, or
trying awk on
the *BSD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/26603/+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 1159933] Re: mawk %d maxes out at 0x7FFFFFFF instead of 0xFFFFFFFF
mawk in Ubuntu and Debian is 18 years, see LP bug #1332114
I think this bug should be marked as duplicate of bug #1332114
Many bugs of Mawk are fixed in a new upstream versions 1.3.4-2010-2015,
but the Debian maintainer does not want to update for an obscure reason.
We need to push here: http://bugs.debian.org/554167
** Bug watch added: Debian Bug tracker #554167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
** Also affects: mawk (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1159933
Title:
mawk %d maxes out at 0x7FFF instead of 0x
Status in mawk package in Ubuntu:
Confirmed
Status in mawk package in Debian:
Unknown
Bug description:
I'm honestly not sure if this is a bug or just an implementation
decision, but it's different than gawk or original-awk, so I'm
reporting it. This caused problems for coreboot which is using awk to
calculate addresses up at the 0xFFFX range. We worked around it
by using %.0f to print the values.
using the test:
printf %u 0x | awk '{printf("%.0f %u %d", $1 , $1 , $1 )}'
mawk:
4294967295 2147483647 2147483647
original-awk:
4294967295 2147483648 4294967295
gawk:
4294967295 4294967295 4294967295
I'm using ubuntu 12.04.02 LTS, and mawk 1.3.3-17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1159933/+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 1074404] Re: Segfault with mawk
mawk in Ubuntu and Debian is 18 years, see LP bug #1332114
I think this bug should be marked as duplicate of bug #1332114
Many bugs of Mawk are fixed in a new upstream versions 1.3.4-2010-2015,
but the Debian maintainer does not want to update for an obscure reason.
We need to push here: http://bugs.debian.org/554167
** Bug watch added: Debian Bug tracker #554167
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
** Also affects: mawk (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554167
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
Status in mawk package in Ubuntu:
Confirmed
Status in mawk package in Debian:
Unknown
Bug description:
release: ubuntu 12.04.1 LTS
mawk version: 1.3.3-17
Got a segfault with: echo "x" | awk "/x/ { print \"(`cat test`)\"; next; } {
print; }" -
'test' file attached
removing a few chars from the test files resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1074404/+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 1074404] Re: Segfault with mawk
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.365
CurrentDesktop: Unity
Dependencies:
gcc-5-base 5.2.1-22ubuntu2
libc6 2.21-0ubuntu4
libgcc1 1:5.2.1-22ubuntu2
DistroRelease: Ubuntu 15.10
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Package: mawk 1.3.3-17ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=lt_LT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Tags: wily
Uname: Linux 4.2.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
** Tags added: apport-collected wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
Status in mawk package in Ubuntu:
Confirmed
Status in mawk package in Debian:
Unknown
Bug description:
release: ubuntu 12.04.1 LTS
mawk version: 1.3.3-17
Got a segfault with: echo "x" | awk "/x/ { print \"(`cat test`)\"; next; } {
print; }" -
'test' file attached
removing a few chars from the test files resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1074404/+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 1074404] JournalErrors.txt
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1074404/+attachment/4518675/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
Status in mawk package in Ubuntu:
Confirmed
Status in mawk package in Debian:
Unknown
Bug description:
release: ubuntu 12.04.1 LTS
mawk version: 1.3.3-17
Got a segfault with: echo "x" | awk "/x/ { print \"(`cat test`)\"; next; } {
print; }" -
'test' file attached
removing a few chars from the test files resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1074404/+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 1332114] Re: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old!
** Summary changed: - Please update mawk to latest upstream release + Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! Status in mawk package in Ubuntu: Triaged Status in mawk package in Debian: New Bug description: mawk in Ubuntu is 15 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2013. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions :( Please, update mawk package in Ubuntu 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+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 1332114] Re: Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old!
** Description changed: - mawk in Ubuntu is 15 years old and very buggy (see + mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk - 1.3.4-2013. Five years since the bug asking to upload new mawk in + 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than - saving from regressions :( + saving from regressions, see for example bug #1005077 :( - Please, update mawk package in Ubuntu 14.10. + Please, update mawk package before major Ubuntu 16.04 LTS release. ** Summary changed: - Please update mawk to latest upstream release - mawk in Ubuntu is 16 years old! + Please update mawk to latest upstream release - mawk in Ubuntu is 18 years old! ** Tags added: trusty wily xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release - mawk in Ubuntu is 18 years old! Status in mawk package in Ubuntu: Triaged Status in mawk package in Debian: New Bug description: mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions, see for example bug #1005077 :( Please, update mawk package before major Ubuntu 16.04 LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+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 1404221] Re: Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu (and Baltix) 12.04-14.04 - libgtk2-perl missing
** Description changed: - Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu (and Baltix) 12.04-14.04 - Quick solution is to add libgtk2-perl package in ubuntu-desktop and ubuntu-defaults-baltix + Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu 14.04 + Quick solution is to add libgtk2-perl package in ubuntu-desktop Recommends ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu (and Baltix) 12.04-14.04 - libgtk2-perl missing + Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu 12.04 and later - libgtk2-perl missing ** Description changed: - Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu 14.04 + Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu 14.04 and later with Ubuntu Software Center Quick solution is to add libgtk2-perl package in ubuntu-desktop Recommends -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1404221 Title: Can't install packages wich ask debconf question (like ttf- mscorefonts-installer) in Ubuntu 12.04 and later - libgtk2-perl missing Status in Default settings and artwork for Baltix OS: In Progress Status in ubuntu-meta package in Ubuntu: New Status in Baltix: New Bug description: Can't install packages wich ask debconf question (like ttf-mscorefonts-installer) in Ubuntu 14.04 and later with Ubuntu Software Center Quick solution is to add libgtk2-perl package in ubuntu-desktop Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1404221/+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 1404068] Re: No internet connection with Huawei E3272 4G modem
** Also affects: baltix-default-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1404068 Title: No internet connection with Huawei E3272 4G modem Status in Default settings and artwork for Baltix OS: New Status in ModemManager: Incomplete Status in modemmanager package in Ubuntu: Incomplete Status in usb-modeswitch-data package in Ubuntu: Invalid Status in usb-modeswitch-data package in Debian: Fix Released Bug description: There is no internet connection. My mobile broadband LTE modem is Huawei E3272. Attached a syslog. Ubuntu 14.10 modemmanager 1.2.0-1 This might contain useful information: http://askubuntu.com/questions/525965/huawei-e3272-ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1404068/+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 1285783] Re: Right panel has a transparent background
Please backport the fix for gtk3 and ubuntu-themes gtk3-widget-factory (GtkStack widgets) to Ubuntu 14.04 LTS release - users still see buggy gnome-tweak-tool, gnome-control-center, gnome-system-monitor, etc. - backgrounds of some windows elements are transparent under gnome- fallback, and turn to black under gnome-shell :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in gtk+3.0 package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1285783/+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 1285783] Re: Right panel has a transparent background
** Also affects: trusty-backports Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in trusty-backports: New Status in gtk+3.0 package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1285783/+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 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken
** Changed in: unity-control-center (Baltix)
Importance: Undecided = High
** Changed in: unity-control-center (Baltix)
Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)
** Changed in: unity-control-center (Baltix)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1365752
Title:
ubuntu-desktop depends on iBus, which is totally broken
Status in ubuntu-meta package in Ubuntu:
Confirmed
Status in unity-control-center package in Ubuntu:
Confirmed
Status in unity-control-center package in Baltix:
Confirmed
Bug description:
Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
installed in the system and activated by default. This has caused an
amount of pain because it has completely broken the input method
(symptoms: no en-uk keyboard available composite not working, backtick
to be pressed twice). The problems are reported in a number of places;
I've read somewhere I can't remember that Unity has some form of
workaround against ibus but I don't use Unity (using Awesome on some
systems, lubuntu on another one) and other windows managers are
affected.
Even disabling ibus (which has to be done via gnome-language-selector,
instead of the keyboard panel in gnome-control-center, which is an
usability problem that deserves its own bug report) the ibus processes
keep on running. Probably this has no consequence but still there is
no reason to have unwanted running processes. I have no idea where do
these processes start, but I clearly have the idea that they shouldn't
be running where not necessary.
Uninstalling ibus is not straightforward because the ubuntu-desktop
package depends on it. The dependency the core package ubuntu-desktop
on ibus is excessive for a package that is 1) unneeded by many users
and 2) broken for many users.
The best solution to date is to:
ibus exit
sudo mv /usr/lib/ibus{,.bak}
sudo mv /usr/bin/ibus{,.bak}
Please remove the dependency of ubuntu-desktop on ibus and avoid
installing it for european languages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1365752/+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 1393206] Re: SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic
It seems this is not lightdm problem
** Package changed: lightdm (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393206
Title:
SD/mmc card with exFAT fs not automatically mounted since upgrade to
utopic
Status in Ubuntu:
Confirmed
Bug description:
Inserting a memory card formatted with exFAT in my built-in memory
reader doesn't automatically mount the partition since I upgraded to
utopic (from trusty). Before this it mounted the partition without any
problems. I have installed exfat-fuse and exfat-utils as before.
udisks2 detects the partition correctly but gvfs ignores it:
17:00:48.133: Added /org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95
org.freedesktop.UDisks2.Drive:
CanPowerOff:false
Configuration: {}
ConnectionBus: sdio
Ejectable: false
Id: SU64G-0xa21a0d95
Media: flash_sd
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: flash_sd
MediaRemovable: true
Model: SU64G
Optical:false
OpticalBlank: false
OpticalNumAudioTracks: 0
OpticalNumDataTracks: 0
OpticalNumSessions: 0
OpticalNumTracks: 0
Removable: true
Revision:
RotationRate: 0
Seat: seat0
Serial: 0xa21a0d95
SiblingId:
Size: 63864569856
SortKey:01hotplug/1416153648130773
TimeDetected: 1416153648130773
TimeMediaDetected: 1416153648130773
Vendor:
WWN:
17:00:48.134: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0
DeviceNumber: 45824
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0
ReadOnly: false
Size: 63864569856
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95
org.freedesktop.UDisks2.PartitionTable:
Type: dos
17:00:48.183: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0p1
DeviceNumber: 45825
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0p1
ReadOnly: false
Size: 63863521280
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95-part1
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained:false
IsContainer:false
Name:
Number: 1
Offset: 1048576
Size: 63863521280
Table: '/org/freedesktop/UDisks2/block_devices/mmcblk0'
Type:
UUID:
Drive connected:'SU64G'
Drive(0): SU64G
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
unix-device: '/dev/mmcblk0'
themed icons: [drive-removable-media-flash-sd]
[drive-removable-media-flash] [drive-removable-media]
[Touch-packages] [Bug 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap
Vytautas, could you test if Euro symbol still doesn't exist in main Lithuanian keyboard layout on Ubuntu 12.04 and 14.04 LTS? I've just tested on 14.04.1 with Gnome Flashback and I can type € when presas AltGr + E But I found related problem Ubuntu installer (Ubiquity) or Unity DE - when I select Lithuanian keyboard during installation, then I get 3 keyboard layouts in Unity Lithuanian (LT), Lithuanian with US Layout as default (LT+US, has Euro symbol) and US layout without Euro symbol. Euro is Lithuanian currency since 2015 January, so, we don't need US Layout without Euro symbol, it's enought to have 2 layouts for Lituanians - LT and LT+US -- 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/718693 Title: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap Status in xkeyboard-config package in Ubuntu: New Status in Baltix GNU/Linux: New Bug description: Binary package hint: xkeyboard-config Main lithuanian layout has no EURO symbol. Main lithuanian layout should have EURO symbol on key e (alt gr + e), like other layouts Lithuanian US, Lithuanian IBM, Lihuanian Standard has it on key e. Windows OS it is also on key e. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/718693/+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 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap
** Changed in: baltix Assignee: (unassigned) = Mantas Kriaučiūnas (mantas) ** Changed in: baltix Importance: Undecided = Critical -- 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/718693 Title: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap Status in xkeyboard-config package in Ubuntu: New Status in Baltix GNU/Linux: New Bug description: Binary package hint: xkeyboard-config Main lithuanian layout has no EURO symbol. Main lithuanian layout should have EURO symbol on key e (alt gr + e), like other layouts Lithuanian US, Lithuanian IBM, Lihuanian Standard has it on key e. Windows OS it is also on key e. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/718693/+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 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken
** Also affects: unity-control-center (Baltix)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1365752
Title:
ubuntu-desktop depends on iBus, which is totally broken
Status in “ubuntu-meta” package in Ubuntu:
Confirmed
Status in “unity-control-center” package in Ubuntu:
Confirmed
Status in “unity-control-center” package in Baltix:
New
Bug description:
Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
installed in the system and activated by default. This has caused an
amount of pain because it has completely broken the input method
(symptoms: no en-uk keyboard available composite not working, backtick
to be pressed twice). The problems are reported in a number of places;
I've read somewhere I can't remember that Unity has some form of
workaround against ibus but I don't use Unity (using Awesome on some
systems, lubuntu on another one) and other windows managers are
affected.
Even disabling ibus (which has to be done via gnome-language-selector,
instead of the keyboard panel in gnome-control-center, which is an
usability problem that deserves its own bug report) the ibus processes
keep on running. Probably this has no consequence but still there is
no reason to have unwanted running processes. I have no idea where do
these processes start, but I clearly have the idea that they shouldn't
be running where not necessary.
Uninstalling ibus is not straightforward because the ubuntu-desktop
package depends on it. The dependency the core package ubuntu-desktop
on ibus is excessive for a package that is 1) unneeded by many users
and 2) broken for many users.
The best solution to date is to:
ibus exit
sudo mv /usr/lib/ibus{,.bak}
sudo mv /usr/bin/ibus{,.bak}
Please remove the dependency of ubuntu-desktop on ibus and avoid
installing it for european languages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1365752/+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
