[Bug 1281587] Re: Ubiquity offers to encrypt the new system, but fails to set TRIM-enabling option in crypttab
note that the initramfs image does NOT support allow_discards at the moment. the script scripts/local-top/cryptroot only supports the discard option: discard) cryptdiscard=yes ;; furthermore, allow_discards is not copied into conf/conf.d/cryptroot so, to avoid changing initrd and packages/infrastructure that generates it, ubuntu should use discard in /etc/crypttab. a viable alternative is to change the default in the script/local- top/cryptroot script: # Defaults cryptcipher=aes-cbc-essiv:sha256 cryptsize=256 crypthash=ripemd160 crypttarget=cryptroot cryptsource= cryptlvm= cryptkeyscript= cryptkey= # This is only used as an argument to an eventual keyscript crypttries=3 cryptrootdev= cryptdiscard= CRYPTTAB_OPTIONS= by changing cryptdiscard to yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281587 Title: Ubiquity offers to encrypt the new system, but fails to set TRIM- enabling option in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1281587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281587] [NEW] Ubiquity offers to encrypt the new system, but fails to set TRIM-enabling option in crypttab
Public bug reported: summary: ubiquity should add, after luks, an option to enable trim support at the dm-crypt layer, if the target disk is an ssd with trim support. Alternatively, allow-discards should be ok on all systems, even not-ssd ones, since in ubuntu 14.04, is the userland script trimfs- all that choses which filesystems and disks are TRIM-capable, and issues discards weekly. Putting allow-discards on all systems shouldn't cause any problem since the choice about whatever discards are to be issued is left to the userland. copy pasting from google+: in ubuntu 14.04 there's default TRIM support. a weekly cronjob, /etc/cron.weekly/fstrim, runs the script fstrim-all, which invokes fstrim on all supported filesystems. in order to effectively issue discards, all the layers must support issuing discards, not just the filesystem. For this reason, in 14.04, lvm supports issuing discards to the lower layers of block storage by default: in /etc/lvm/lvm.conf we have issue_discards = 1 however, ubiquity supports installing a system with encryption by default. In order to effectively support issuing discards, LUKS should be configured to support them too: in /etc/crypttab we should have something like [...] luks,allow-discards, to allow higher layers to issue discards. It is also possible to have luks,discard, to automatically issue discards, but it would be more in line with ubuntu policy to trim ssd periodically from the userland to just allow them. in a default install, at the moment, no discard option is present in /etc/crypttab: sda5_crypt UUID=longuuidhere none luks as a consequence, fstrim fails: fstrim: /: FITRIM ioctl failed: Operation not supported ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281587 Title: Ubiquity offers to encrypt the new system, but fails to set TRIM- enabling option in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1281587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963587] Re: Trousers fails to set tpm permissions properly.
this bug seems to be still present on ubuntu 13.10 as of today, and it breaks apt/dpkg when trying to install 'trousers'. the initscript tries to start tcsd under the 'tss' user: execve(/sbin/start-stop-daemon, [start-stop-daemon, --start, -- quiet, --oknodo, --pidfile, /var/run/tcsd.pid, --user, tss, --chuid, tss, --exec, /usr/sbin/tcsd, --], [/* 4 vars */]) = 0 but /dev/tpm0 is only accessible by root: crw--- 1 root root 10, 224 dic 23 10:43 /dev/tpm0 and tcsd fails to start: open(/dev/tpm0, O_RDWR) = -1 EACCES (Permission denied) returning error code 137. after changing /dev/tpm0 ownership to 'tss:tss;, tcsd still fails to start because of (other) permission problems: open(/var/lib/tpm/system.data, O_RDWR|O_CREAT, 0600) = -1 EACCES (Permission denied) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963587 Title: Trousers fails to set tpm permissions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/963587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963587] Re: Trousers fails to set tpm permissions properly.
as a temporary workaround, I hacked trousers' init script:
start)
log_daemon_msg Starting $DESC $NAME
if [ ! -e /dev/tpm* ]
then
log_warning_msg device driver not loaded, skipping.
exit 0
fi
chown tss:tss /dev/tpm*
chown -R tss:tss /var/lib/tpm
start-stop-daemon --start --quiet --oknodo --pidfile
/var/run/${NAME}.pid --user ${USER} --chuid ${USER} --exec ${DAEMON} --
${DAEMON_OPTS}
RETVAL=$?
log_end_msg $RETVAL
[ $RETVAL = 0 ] pidof $DAEMON /var/run/${NAME}.pid
exit $RETVAL
;;
I simply added:
chown tss:tss /dev/tpm*
chown -R tss:tss /var/lib/tpm
and now the daemon starts. The change of ownership of /var/lib/tpm
should however be done by the package postinst script, and the change of
ownership on the tpm device via udev; a permissions check should still
be added to the init script, and maybe some 'form' of temporary
remediation too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963587
Title:
Trousers fails to set tpm permissions properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/963587/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263499] [NEW] missing dependency: python-spice-client-gtk
Public bug reported: qemu-kvm and, by extension, virt-manager, supports two graphic modes: vnc and the newer spice. virt-manager always assumes the presence of a python spice module, and lets the user select it without checking if system support is indeed present. This results in an error when trying to control guests: no module named spiceClientGtk installing the package python-spice-client-gtk does solve the problem; my suggestion is to either make it a dependency or patch virt-manager to only use and display available protocols. ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263499 Title: missing dependency: python-spice-client-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1263499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263499] Re: missing dependency: python-spice-client-gtk
Sorry, this reports seems more relevant to the package 'virt-viewer' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263499 Title: missing dependency: python-spice-client-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1263499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263534] [NEW] virt-manager (or libvirt) fails to set proper iptables routing rules for a virtual network
Public bug reported: I needed to access a service (RDP) running on a kvm guest, but I didn't want to have to modify iptables nat rules or allow the guest on my local network by bridging it on a phisical interface, so I created a virtual network, let's call it 'VirtNetLO50', with address 192.168.100.0/24 and routing torwards the interface 'lo50' I had created the lo:50 alias beforehand, as 192.168.50.1/24 I expected virt-manager/libvirt to create iptables rules allowing traffic to said interface, but I then discovered that guest connected to the VirtNet50 virtual network had routing torward all my networks and interfaces. After further controls, it appears that virt-manager/libvirt had indeed created some iptables rules: Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere 192.168.100.0/24 ACCEPT all -- 192.168.100.0/24 anywhere those rules are, in my hopinion, too broad. virt-manager gui allows me to select which interface/network route to, and I'd expect to be able to route ONLY with that network, not with 'anywhere' a more reasonable roule should have been: target prot opt source destination ACCEPT all -- 192.168.50/24 192.168.100.0/24 ACCEPT all -- 192.168.100.0/24 192.168.50/24 ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263534 Title: virt-manager (or libvirt) fails to set proper iptables routing rules for a virtual network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1263534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263534] Re: virt-manager (or libvirt) fails to set proper iptables routing rules for a virtual network
or, since that would require to be aware of the interface configuration and subsequent variation, it would have made sense making use of iptables' --in-interface and --out-interface parameters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263534 Title: virt-manager (or libvirt) fails to set proper iptables routing rules for a virtual network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1263534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038373] Re: 8086:0887 Intel Centrino 2230 card doesn't connect, and has extremely high latency when connected
This is also happpening to me on ubuntu 13.04 running kernel 3.8.0-26-generic I have the same WiFi adapter and, when I ping my router I get similar results: 64 bytes from 192.168.1.1: icmp_req=1 ttl=255 time=225 ms 64 bytes from 192.168.1.1: icmp_req=2 ttl=255 time=146 ms 64 bytes from 192.168.1.1: icmp_req=3 ttl=255 time=65.5 ms 64 bytes from 192.168.1.1: icmp_req=4 ttl=255 time=83.9 ms 64 bytes from 192.168.1.1: icmp_req=5 ttl=255 time=213 ms 64 bytes from 192.168.1.1: icmp_req=6 ttl=255 time=23.4 ms 64 bytes from 192.168.1.1: icmp_req=7 ttl=255 time=53.0 ms 64 bytes from 192.168.1.1: icmp_req=8 ttl=255 time=71.8 ms 64 bytes from 192.168.1.1: icmp_req=9 ttl=255 time=200 ms 64 bytes from 192.168.1.1: icmp_req=10 ttl=255 time=127 ms Using the workaround iwconfig wlan0 power off I get normal results again: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_req=1 ttl=255 time=2.37 ms 64 bytes from 192.168.1.1: icmp_req=2 ttl=255 time=1.91 ms 64 bytes from 192.168.1.1: icmp_req=3 ttl=255 time=4.51 ms 64 bytes from 192.168.1.1: icmp_req=4 ttl=255 time=4.52 ms 64 bytes from 192.168.1.1: icmp_req=5 ttl=255 time=1.92 ms 64 bytes from 192.168.1.1: icmp_req=6 ttl=255 time=1.83 ms ^C --- 192.168.1.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5006ms rtt min/avg/max/mdev = 1.834/2.848/4.528/1.197 ms This is definetly a regression, using debian 7 with kernel 3.2 the problem isn't present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038373 Title: 8086:0887 Intel Centrino 2230 card doesn't connect, and has extremely high latency when connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1038373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038373] Re: 8086:0887 Intel Centrino 2230 card doesn't connect, and has extremely high latency when connected
** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038373 Title: 8086:0887 Intel Centrino 2230 card doesn't connect, and has extremely high latency when connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1038373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069531] Re: Cannot login to Empathy after setting up Google online account
I have the same problem. I don't need/like to add a google account, I only need to use it for empathy. When adding it to ubuntu-online-accounts as a jabber account, in the format accountname -AT- gmail.com, empathy can't connect and asks for authentication, the following message is sent to stderr: (empathy:8345): folks-WARNING **: Failed to reach quiescence normally (0 backends and 1 persona stores still haven't reached quiescence). Forcing IndividualAggregator quiescence due to reaching the timeout. the account works if it's set up as a google account, it works in pidgin and in empathy running in other distributions which use gnome online accounts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069531 Title: Cannot login to Empathy after setting up Google online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1069531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358276] [NEW] nvidia driver
Public bug reported: Binary package hint: xorg i have a Toshiba Qosmio G20-129 with an Nvidia ge force go 6600 and it always worked with ubuntu and any other linux distro. with ubuntu 9.04 i open the restricted drivers manager and i select an invidia driver, i enable it and at the restart the system is in low grafich mode. i think this is a very serius bug. another think that always worked with 8.04 and not with the 9.04: the suspend mode. when i click suspend I get a black screen with a white blinking cursor. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- nvidia driver https://bugs.launchpad.net/bugs/358276 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358276] Re: nvidia driver
another think: NVIDIA: could not open the device file: /dev/nvidia0 (input/output error) ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- nvidia driver https://bugs.launchpad.net/bugs/358276 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357218] Re: Ubuntu wallpaper called warty-final-ubuntu.png is made with Adobe Photoshop CS3 Macintosh
** Changed in: ubuntu-wallpapers (Ubuntu) Status: New = Confirmed -- Ubuntu wallpaper called warty-final-ubuntu.png is made with Adobe Photoshop CS3 Macintosh https://bugs.launchpad.net/bugs/357218 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
