[Touch-packages] [Bug 1511975] Re: /lib/systemd/system/console-setup.service has incorrect ExecStart
On my 16.04.3 (keyboard-configuration 1.108ubuntu15.3) the subject line is: ExecStart=/bin/setupcon --save So, it might have already been fixed, but further version range clarification is probably needed. -- 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/1511975 Title: /lib/systemd/system/console-setup.service has incorrect ExecStart Status in console-setup package in Ubuntu: Confirmed Bug description: /lib/systemd/system/console-setup.service as provided by this package (confirmed in vivid and wily) specifies: [Service] Type=oneshot ExecStart=/usr/bin/loadkeys /etc/console-setup/cached.kmap.gz The "ExecStart" line will set the keyboard map but not the font, therefore the font remains at the default VGA font and framebuffer console mode is not enabled. The correct line which will set up both the keyboard map and the font is: ExecStart=/bin/setupcon The complete modified file is attached. I would be willing to submit a pull request on the relevant git repository if someone could point me in the right direction. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: keyboard-configuration 1.108ubuntu5 [modified: lib/systemd/system/console-setup.service] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 31 16:30:27 2015 InstallationDate: Installed on 2015-10-31 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1511975/+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 1365020] Re: option "subject-match" not working
Hi tested today with network-manager 1.0.4-0ubuntu5 Problem still exists. Note: the new Network-manager created the lines "altsubject-matches" and "phase2-altsubject-matches" I tried them an the "subject-match" line. I can still connect with "radius.uni-konstanz.de" (the right name" and "nonsense.foo.bar" which is definitely NOT part of the string. -- 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/1365020 Title: option "subject-match" not working Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager supports checking the radius certificates used within 802.1X Infrastructures. These Options are "subject-match" and "phase2-subject-match". However is these options are set the are read by networkmanager at connection activation, but is silently ignored. Even if the String supplied by this option is known wrong the connection can be established. This is a bis isues within wide spread WPA2-Infrastructures like "eduroam" where SSID on the network is well known. This issue exist in pakage Network-manager 0.9.8.8-0ubuntu7 (amd64) In other distributions like Debian 7.6 (network-mamanger 0.9.4.0-10) the option is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+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 1321958] Re: resize2fs does not start to actually grow an ext4
according to http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42.13 this BUG is fixed in e2fsprogs 1.42.12 or higher. "Fix a 32/64-bit overflow bug that could cause resize2fs to loop forever. (Addresses-Launchpad-Bug: #1321958)" is it possible to backport the newest e2fsprogs package to trusty ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 Status in e2fsprogs package in Ubuntu: Triaged Status in e2fsprogs source package in Trusty: Confirmed Bug description: Ubuntu 14.04 LTS, all proposed updates done Kernel: 3.13.0-24-generic, Package: e2fsprogs 1.42.9-3ubuntu1, System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA I tried to increse the size of an ext4 filesystem. Old size 20TB, wanted new size 28TB. I tried offline resize with "resize2fs -fp /dev/md2" and later online resize using "resize2fs -f /dev/md2". In both cases, after giving the command a rezise2fs process is created that uses nearly 100% cpu according to top, but it does not perform any actual resize. It only prints its version and date and then it does not finish for hours. I had it running for more than a day without finishing: root@marvin:~# resize2fs -f /dev/md2 resize2fs 1.42.9 (4-Feb-2014) There is never more terminal output than that. It looks to me that resize2fs hangs in a endless calcualtion or loop or something similar. Some more info about the filesystem: root@marvin:~# tune2fs -l /dev/md2 tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: data Last mounted on: /media/data01 Filesystem UUID: e3845e15-0336-47ae-8aec-df75acb217c5 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 305225728 Block count: 4883606400 Reserved block count: 0 Free blocks: 22919919 Free inodes: 302894731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 2048 Inode blocks per group: 128 RAID stride: 128 RAID stripe width:640 Flex block group size:16 Filesystem created: Fri Sep 20 19:45:01 2013 Last mount time: Tue May 20 02:14:37 2014 Last write time: Tue May 20 02:14:37 2014 Mount count: 3 Maximum mount count: -1 Last checked: Tue May 20 01:34:05 2014 Check interval: 0 () Lifetime writes: 34 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: 569ec5fc-4d5e-4639-bef3-42cde5fbe948 Journal backup: inode blocks I did also run an filesystem check: root@marvin:~# e2fsck -vfp /dev/md2 2330890 inodes used (0.76%, out of 305225728) 14882 non-contiguous files (0.6%) 949 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 2317190/13041/651 4868171016 blocks used (99.68%, out of 4883606400) 0 bad blocks 1654 large files 2273776 regular files 57105 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 2330881 files The underlying device is an mdadm RAID6 that was grown from 7 to 9 disks. The growing finished without problems before I tried to increase the ext4 size. Solution: The solution for me was to downgrade to e2fsprogs 1.42.8. Then the resize did work and finished within a few minutes. I got the hint to do so in a forum from an user, who had the same problem and solved it with
[Touch-packages] [Bug 1365020] Re: option subject-match not working
tried again with network-manager 0.9.8.8-0ubuntu28 problem still exists. the subject-match line is read by network-manager but has no effect at all. If i created a wpa_suplicant configuration instead the string is verified and the connection will not be established with the wrong string.So i can confirm wpa_supplicant working properly but network-manager is still broken somehow. -- 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/1365020 Title: option subject-match not working Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager supports checking the radius certificates used within 802.1X Infrastructures. These Options are subject-match and phase2-subject-match. However is these options are set the are read by networkmanager at connection activation, but is silently ignored. Even if the String supplied by this option is known wrong the connection can be established. This is a bis isues within wide spread WPA2-Infrastructures like eduroam where SSID on the network is well known. This issue exist in pakage Network-manager 0.9.8.8-0ubuntu7 (amd64) In other distributions like Debian 7.6 (network-mamanger 0.9.4.0-10) the option is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+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
