[Touch-packages] [Bug 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
I disagree with closing this as “WORKSFORME”. Just because core Firefox
plastered over the problem does not mean it's not an issue for other
cases. I have at least one Firefox add-on that continues to display
unreadable text because this bug causes the CSS InfoBackground and
InfoText values in styles to result in white-on-white text colors. It
will even affect websites that happen to style themselves in these
colors (example demo: https://artific.com/library/css-2-system-
colors.html). Who knows what other software might also be affected. I
have just tried the patch posted here and can confirm that the issues I
describe are definitely caused by this bug.
The themes are clearly broken and should be fixed. An explicit
background *and* foreground color should always be specified. There is
no guarantee the background image/effect will be used by a given
application, and relying on it is only asking for random usability
problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1478173
Title:
Ambiance & Radiance themes are missing a "background-color" for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in One Hundred Papercuts:
Confirmed
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance & Radiance GTK3 themes.
They're missing a "background-color" for the .tooltip {...} CSS rule
in their config files. They have a "tooltip_bg_color" variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the ".tooltip" CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+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 1522675] Re: Warning messages about unsandboxed downloads
The command is lowercase “chown”, without the “(1)”. The general syntax would be “chown ”. You'll normally need superuser privileges to change owners on system files and directories, activated by adding the command “sudo” before the “chown” (separated by a space). The “(1)” refers to which section in the manual pages, or “manpages”, the command is described in. A common way to get help on a command is to run “man ”; for instance, you can execute “man chown” to get the manpage on the chown command. (To exit, type the letter q; more info here: https://help.ubuntu.com/community/man) The manual pages are divided into numbered sections by categories. Occasionally, there is more than one manpage with the same name, and the section number has to be included in the “man” command to indicate which is desired (for instance, “man 1 printf” gives the page on the shell command “printf”, but “man 3 printf” gives the page on the “printf” library call for C programming). You can get a manpage on “man” itself with “man man” (or just read it online here: http://manpages.ubuntu.com/manpages/xenial/man1/man.1.html). Under “DESCRIPTION”, there's a list of the manpage sections and their numbers, if you're curious. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: Warning messages about unsandboxed downloads
^ Setting the owner of the /var/lib/update-notifier/package-data- downloads/partial directory to “_apt” on my 16.04 box is what I did to get rid of the error. I believe I've occasionally run into a few similar messages about other APT “partial” directories scattered around in /var, too; in those cases, the solution was the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
I thought it might be helpful to anyone still having this problem (where the fix hasn't been backported yet) to mention that the workaround is described in Bug #1607535 (essentially, delete the affected partial download files in /var/lib/update-notifier/package-data- downloads/partial/ and then try reinstalling again). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1657567 Title: "Content-Range: */" on non-416 responses considered invalid Status in apt package in Ubuntu: Fix Released Bug description: APT only allows Content-Range: */ to be specified on a 416 response. Sourceforge sometimes replies with that in a 302 redirect. We should probably just accept and silently ignore that content-range field for other values. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+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 1313732] Re: Impossible to report a bug about samba-tool without answering inadequate questions
I hit this today, and it absolutely infuriates me. Indeed, the questions have either no valid answers or ask things I could not possibly know. And I consider myself a reasonably experienced user. All I know is that I tried to apply security updates and it told me something happened. It withheld all the details until I gave up on the questions and cancelled, and the whole thing closed **without once giving me a single clue what the problem was**. I still have no idea what issue it was trying to report or whether Samba is now usable, etc. I really hate useless messages that say “an error occurred” with no details, but refusing to give any information at all while simultaneously demanding it from the user takes the cake. I am amazed to find something so user-hostile in a bug-reporting tool. This isn't a good way to get bug reports, and it probably isn't a very good way to encourage users *not* to simply give up and permanently disable the bug reporter *and* system updates altogether! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1313732 Title: Impossible to report a bug about samba-tool without answering inadequate questions Status in apport package in Ubuntu: Confirmed Bug description: Trying to report a bug about samba I am first asked about if: *** How would you best describe your setup? Auswahl: 1: I am running a Windows File Server. 2: I am connecting to a Windows File Server. A: Abbruch Bitte wählen Sie (1/2/A): What shall I answer? 1 - isn't right, 2 - isn't either. A? Bailing out because it isn't thought of other possibilities??! I choose 1, because if all answers are wrong it seems not to matter how wrong they are! Next question: *** Did this used to work properly with a previous release? Was möchten Sie tun? Ihre Möglichkeiten sind: Y: Yes N: No A: Abbruch Bitte wählen Sie (Y/N/A): Wow! I do not konw if it did work or not - simply because I did not use it before! Fine. Just assume Yes and answer "Y" Next question: *** Which clients are failing to connect? Auswahl: 1: Windows 2: Ubuntu 3: Both 4: Other A: Abbruch Bitte wählen Sie (1/2/3/4/A): I do not connect a client! So what?? Since I learned "A" isn't good trying "4". *** The contents of your /etc/samba/smb.conf file may help developers diagnose your bug more quickly. However, it may contain sensitive information. Do you want to include it in your bug report? Was möchten Sie tun? Ihre Möglichkeiten sind: Y: Yes N: No A: Abbruch Bitte wählen Sie (Y/N/A): Wow! The first question being concrete. I dislike to include this file without changing certain parts ... so 'N'. *** The contents of your /var/log/samba/log.smbd and /var/log/samba/log.nmbd may help developers diagnose your bug more quickly. However, it may contain sensitive information. Do you want to include it in your bug report? Was möchten Sie tun? Ihre Möglichkeiten sind: Y: Yes N: No A: Abbruch Bitte wählen Sie (Y/N/A): Same for the logs. Again 'N'. These questions are only helpful if there are connection problems, but they are not if there are other problems like not working samba-tool commands or else. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CrashReports: 640:0:106:101243:2014-04-25 09:55:06.734537444 +0200:2014-04-25 11:11:09.272081356 +0200:/var/crash/_usr_sbin_samba_dnsupdate.0.crash Date: Mon Apr 28 12:05:46 2014 InstallationDate: Installed on 2012-12-12 (501 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) PackageArchitecture: all ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2013-02-11 (440 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1313732/+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 1470235] Re: PolicyKit high memory usage
This happened to me, too. I installed Multi-Core System Monitor for just a moment and noticed the steadily growing memory usage. Worse, removing the applet did not stop the leak. The leak didn't stop until the next system reboot (presumably restarting polkitd would have also worked, but I didn't try it since I wasn't sure how safe it was). But since there's no way to know if this was the trigger for the original bug report or earlier commenters, perhaps the MCSM case should be opened as a separate, specific bug against policykit? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using > 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1522675] Re: /root/.synaptic/ not created due to locking status
I just now found a very similar message from the update-notifier cronjob: /etc/cron.daily/update-notifier-common: Get:1 http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160407.1.orig.tar.gz [27.0 MB] Fetched 27.0 MB in 1min 11s (378 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160407.1.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160407.1.orig.tar.gz Installing from local file /var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160407.1.orig.tar.gz Flash Plugin installed. So, apparently not unique to Synaptic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: /root/.synaptic/ not created due to locking status Status in apt package in Ubuntu: Invalid Status in synaptic package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: /root/.synaptic/ not created
For the Synaptic message complaining about /var/cache/apt/archives/partial, setting the owner of that directory to _apt seems to avoid it, based on my tests in a VirtualBox VM of Wily upgraded to Xenial. I haven't (yet) encountered an error complaining about /root/.synaptic/[…]. It seems really bizarre that it would insist on some system user being able to access something in root's home directory. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: /root/.synaptic/ not created Status in apt package in Ubuntu: Invalid Status in synaptic package in Ubuntu: Triaged Status in synaptic package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1539934] Re: Load thin Kernel Modules in initramfs for support on boot
I was able to use this hook to get Ubuntu 15.10 installed and running from a thin LVM volume in a VirtualBox VM. However, the lvm2-monitor service seems wonky if started from the initramfs, strange errors like: --tpool: event registration failed: 2561:11 libdevmapper-event-lvm2thin.so dlopen failed: /lib/x86_64-linux-gnu /device-mapper/libdevmapper-event-lvm2thin.so: cannot open shared object file: No such file or directory even though the library is both in the root fs and the initrd. Leaving dmeventd and its libraries out of the initramfs seems to allow it to function normally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1539934 Title: Load thin Kernel Modules in initramfs for support on boot Status in lvm2 package in Ubuntu: Confirmed Bug description: I have an issue where lvm2 thinpool volume groups are not automatically activated after reboot. Environmentals: Ubuntu Server 15.10, minimal install UEFI/Secure Boot in use Ubuntu 15.10 (GNU/Linux 4.2.0-25-generic x86_64) root@cluster-02:~# cat /etc/os-release NAME="Ubuntu" VERSION="15.10 (Wily Werewolf)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 15.10" VERSION_ID="15.10" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; Here is the volume config before adding the new volume: root@cluster-02:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvswap vgraid0 -wi-ao 29.80g lvtmp vgraid0 -wi-ao 29.80g lvvartmp vgraid0 -wi-ao 29.80g lvhome vgraid10 -wi-ao 29.80g lvroot vgraid10 -wi-ao 7.45g lvusr vgraid10 -wi-ao 7.45g lvvar vgraid10 -wi-ao 3.72g lvvarcache vgraid10 -wi-ao 119.21g lvvarlib vgraid10 -wi-ao 32.00g lvvarlog vgraid10 -wi-ao 14.90g I add a new thinpool volume using this command: lvcreate -L 1T --type thin-pool --thinpool vgraid10/lvlxc root@cluster-02:~# lvcreate -L 1T --type thin-pool --thinpool vgraid10/lvlxc Logical volume "lvlxc" created. Which results in this lvs: root@cluster-02:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvswap vgraid0 -wi-ao 29.80g lvtmp vgraid0 -wi-ao 29.80g lvvartmpvgraid0 -wi-ao 29.80g lvhome vgraid10 -wi-ao 29.80g lvlxc vgraid10 twi-a-tz-- 1.00t 0.00 0.42 [lvlxc_tdata] vgraid10 Twi-ao 1.00t [lvlxc_tmeta] vgraid10 ewi-ao 128.00m [lvol0_pmspare] vgraid10 ewi--- 128.00m lvroot vgraid10 -wi-ao 7.45g lvusr vgraid10 -wi-ao 7.45g lvvar vgraid10 -wi-ao 3.72g lvvarcache vgraid10 -wi-ao 119.21g lvvarlibvgraid10 -wi-ao 32.00g lvvarlogvgraid10 -wi-ao 14.90g I then create an unprivileged lxc container using the thinpool: root@cluster-02:~# lxc-create -B lvm --vgname=vgraid10 --thinpool=lvlxc -t download -n tmpl-centos-7-unpriv --fssize 16GB -- -d centos -r 7 -a amd64 File descriptor 3 (/var/lib/lxc/tmpl-centos-7-unpriv/partial) leaked on lvcreate invocation. Parent PID 9118: lxc-create Logical volume "tmpl-centos-7-unpriv" created. Using image from local cache Unpacking the rootfs ... The lvs output: root@cluster-02:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvswap vgraid0 -wi-ao 29.80g lvtmpvgraid0 -wi-ao 29.80g lvvartmp vgraid0 -wi-ao 29.80g lvhome vgraid10 -wi-ao 29.80g lvlxcvgraid10 twi-aotz-- 1.00t 0.09 0.46 [lvlxc_tdata]vgraid10 Twi-ao 1.00t [lvlxc_tmeta]vgraid10 ewi-ao 128.00m [lvol0_pmspare] vgraid10 ewi--- 128.00m lvroot vgraid10 -wi-ao 7.45g lvusrvgraid10 -wi-ao 7.45g lvvarvgraid10 -wi-ao 3.72g lvvarcache vgraid10 -wi-ao 119.21g lvvarlib vgraid10 -wi-ao 32.00g lvvarlog vgraid10 -wi-ao 14.90g tmpl-centos-7-unpriv vgraid10 Vwi-a-tz-- 16.00g lvlxc5.94 Everything is ok at this point. Now, I will reboot the machine. root@cluster-02:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvswap vgraid0 -wi-ao 29.80g lvtmpvgraid0 -wi-ao 29.80g lvvartmp vgraid0 -wi-ao 29.80g lvhome vgraid10 -wi-ao
