[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions
Almost forget, Thank you very much for you help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions
Yeah, it does work as expected now. After: chmod +x /home/sneetsher/.local chmod +x /home/sneetsher/.local/share I was working in real machine. I just checked 3 fresh installed VirtualBox machines 14.04 0755 16.04 0700 16.10 0755 Anyway, this seems only for 16.04. It is better to get that package back-ported, or may be more convenient putting a note about those stable PPA's as alternative way to install the edge release. To save users from falling in same pit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions
It couldn't start but got a different error messages. Please, here is the attached log & commands output. ** Attachment added: "lxc_debug_info_after_installing_lxcfs2.0.5.zip" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+attachment/4792357/+files/lxc_debug_info_after_installing_lxcfs2.0.5.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1650499] Re: apport should use journalctl instead of dmesg
Here is the log example from my other report: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1649835 ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650499/+attachment/4792330/+files/CurrentDmesg.txt.txt -- 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/1650499 Title: apport should use journalctl instead of dmesg Status in apport package in Ubuntu: New Bug description: 1) $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) $ apt-cache policy apport apport: Installed: 2.20.1-0ubuntu2.2 Candidate: 2.20.1-0ubuntu2.2 Version table: *** 2.20.1-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) apport report should have the complete kernel boot message (like dmesg was using upstart) 4) I noticed on late bug reports using apport to collect info in Ubuntu 16.04. That apport still using dmesg command which does not show the whole log any more, it missed the boot up messages. expected solution: AFAIK, the full boot message could be collected using `journalctl` commmand from systemd package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CrashReports: 640:1000:116:7681399:2016-12-13 00:39:27.693699598 +0100:2016-12-13 00:39:28.693699598 +0100:/var/crash/_usr_bin_thunar.1000.crash 664:1000:116:0:2016-12-13 00:39:40.553566707 +0100:2016-12-13 00:39:40.553566707 +0100:/var/crash/_usr_bin_thunar.1000.upload 640:1000:116:10998770:2016-12-14 18:45:44.058813095 +0100:2016-12-14 18:45:45.058813095 +0100:/var/crash/_usr_bin_parole.1000.crash 600:109:116:0:2016-12-13 00:39:45.857507643 +0100:2016-12-13 00:39:45.857507643 +0100:/var/crash/_usr_bin_thunar.1000.uploaded 640:1000:116:425073:2016-12-10 14:14:15.244681119 +0100:2016-12-10 14:14:16.244681119 +0100:/var/crash/_opt_teamviewer_tv_bin_teamviewerd.1000.crash CurrentDesktop: XFCE Date: Fri Dec 16 10:49:41 2016 InstallationDate: Installed on 2016-07-09 (159 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650499/+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 1650499] [NEW] apport should use journalctl instead of dmesg
Public bug reported: 1) $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 2) $ apt-cache policy apport apport: Installed: 2.20.1-0ubuntu2.2 Candidate: 2.20.1-0ubuntu2.2 Version table: *** 2.20.1-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) apport report should have the complete kernel boot message (like dmesg was using upstart) 4) I noticed on late bug reports using apport to collect info in Ubuntu 16.04. That apport still using dmesg command which does not show the whole log any more, it missed the boot up messages. expected solution: AFAIK, the full boot message could be collected using `journalctl` commmand from systemd package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CrashReports: 640:1000:116:7681399:2016-12-13 00:39:27.693699598 +0100:2016-12-13 00:39:28.693699598 +0100:/var/crash/_usr_bin_thunar.1000.crash 664:1000:116:0:2016-12-13 00:39:40.553566707 +0100:2016-12-13 00:39:40.553566707 +0100:/var/crash/_usr_bin_thunar.1000.upload 640:1000:116:10998770:2016-12-14 18:45:44.058813095 +0100:2016-12-14 18:45:45.058813095 +0100:/var/crash/_usr_bin_parole.1000.crash 600:109:116:0:2016-12-13 00:39:45.857507643 +0100:2016-12-13 00:39:45.857507643 +0100:/var/crash/_usr_bin_thunar.1000.uploaded 640:1000:116:425073:2016-12-10 14:14:15.244681119 +0100:2016-12-10 14:14:16.244681119 +0100:/var/crash/_opt_teamviewer_tv_bin_teamviewerd.1000.crash CurrentDesktop: XFCE Date: Fri Dec 16 10:49:41 2016 InstallationDate: Installed on 2016-07-09 (159 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1650499 Title: apport should use journalctl instead of dmesg Status in apport package in Ubuntu: New Bug description: 1) $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) $ apt-cache policy apport apport: Installed: 2.20.1-0ubuntu2.2 Candidate: 2.20.1-0ubuntu2.2 Version table: *** 2.20.1-0ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) apport report should have the complete kernel boot message (like dmesg was using upstart) 4) I noticed on late bug reports using apport to collect info in Ubuntu 16.04. That apport still using dmesg command which does not show the whole log any more, it missed the boot up messages. expected solution: AFAIK, the full boot message could be collected using `journalctl` commmand from systemd package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CrashReports: 640:1000:116:7681399:2016-12-13 00:39:27.693699598 +0100:2016-12-13 00:39:28.693699598 +0100:/var/crash/_usr_bin_thunar.1000.crash 664:1000:116:0:2016-12-13 00:39:40.553566707 +0100:2016-12-13 00:39:40.553566707 +0100:/var/crash/_usr_bin_thunar.1000.upload 640:1000:116:10998770:2016-12-14 18:45:44.058813095 +0100:2016-12-14 18:45:45.058813095 +0100:/var/crash/_usr_bin_parole.1000.crash 600:109:116:0:2016-12-13 00:39:45.857507643 +0100:2016-12-13 00:39:45.857507643 +0100:/var/crash/_usr_bin_thunar.1000.uploaded 640:1000:116:425073:2016-12-10 14:14:15.244681119 +0100:2016-12-10 14:14:16.244681119 +0100:/var/crash/_opt_teamviewer_tv_bin_teamviewerd.1000.crash CurrentDesktop: XFCE Date: Fri Dec 16 10:49:41 2016 InstallationDate: Installed on 2016-07-09 (159 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport
[Touch-packages] [Bug 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions
Yeah, please see lxc_cgroup_debug_outputs.txt file for all outputs and lxc config. ** Attachment added: "lxc_cgroup_debug_outputs.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+attachment/4792203/+files/lxc_cgroup_debug_outputs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1649582] Re: lxc-start fails to start a unprivileged container - cgroup permissions
Yes. $ apt-cache policy libpam-cgfs libpam-cgfs: Installed: 2.0.4-0ubuntu1~ubuntu16.04.1 Candidate: 2.0.4-0ubuntu1~ubuntu16.04.1 Version table: *** 2.0.4-0ubuntu1~ubuntu16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.0-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages I also reinstall it, just in case, but still fails to start -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1649582] [NEW] lxc-start fails to start a unprivileged container - cgroup permissions
Public bug reported: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "lxc-start debug log" https://bugs.launchpad.net/bugs/1649582/+attachment/4791140/+files/ci.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1649582 Title: lxc-start fails to start a unprivileged container - cgroup permissions Status in lxc package in Ubuntu: New Bug description: I was following this simple getting start tutorial: https://linuxcontainers.org/lxc/getting-started/ Created using: lxc-create -t download -n ci -- -d ubuntu -r trusty -a amd64 But it always fails at: lxc-start -n ci -d I even tried another Ubuntu 14.04 but didn't work too for same problem. Below the debug log got from running `lxc-start` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.5-0ubuntu1~ubuntu16.04.3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 13 14:05:44 2016 InstallationDate: Installed on 2016-07-09 (156 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1649582/+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 1519310] [NEW] libqt4-core and all other binary packages should be uploaded to same repository component
Public bug reported: libqt4-core is a transitional package, uploaded to "universe" in the official Ubuntu repository. Its dependencies: libqtcore4 libqt4-xml libqt4-test libqt4-script libqt4-network libqt4-dbus are uploaded to "main". They are built from the same source package. This just creates an "unmet dependency" error, if the user don't enable both components "universe" (+"main" enabled by default) with same repositories of "updates", "security" & "backports". I think that the libqt4-core package and all other transitional packages should be moved to "main". I face this dependency problem on Ask Ubuntu, for more details: http://askubuntu.com/questions/700096/libqt4-core-has-unmet- dependencies/ ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Description changed: libqt4-core is a transitional package, uploaded to "universe" in the official Ubuntu repository. Its dependencies: libqtcore4 libqt4-xml libqt4-test libqt4-script - libqt4-network libqt4-dbus are uploaded to "main" + libqt4-network libqt4-dbus are uploaded to "main". - They are built from same source package. This just create a "unmet - dependency" error if the user don't enable both component with same - repositories of "updates", "security" & "backports". + They are built from the same source package. This just creates an "unmet + dependency" error, if the user don't enable both components "universe" + (+"main" enabled by default) with same repositories of "updates", + "security" & "backports". - I think that libqt4-core and all other transitional packages should be - moved to "main". + I think that the libqt4-core package and all other transitional packages + should be moved to "main". I face this dependency problem on Ask Ubuntu, for more details: http://askubuntu.com/questions/700096/libqt4-core-has-unmet- dependencies/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1519310 Title: libqt4-core and all other binary packages should be uploaded to same repository component Status in qt4-x11 package in Ubuntu: New Bug description: libqt4-core is a transitional package, uploaded to "universe" in the official Ubuntu repository. Its dependencies: libqtcore4 libqt4-xml libqt4-test libqt4-script libqt4-network libqt4-dbus are uploaded to "main". They are built from the same source package. This just creates an "unmet dependency" error, if the user don't enable both components "universe" (+"main" enabled by default) with same repositories of "updates", "security" & "backports". I think that the libqt4-core package and all other transitional packages should be moved to "main". I face this dependency problem on Ask Ubuntu, for more details: http://askubuntu.com/questions/700096/libqt4-core-has-unmet- dependencies/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1519310/+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 1330302] Re: Indicator is not autostared in Gnome Flashback session
Fix released for Utopic. Commit: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/utopic/indicator-power/utopic/revision/68#data /indicator-power.desktop.in ** Changed in: indicator-power (Ubuntu) Status: New = Fix Released ** Changed in: indicator-power Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330302 Title: Indicator is not autostared in Gnome Flashback session Status in The Power Indicator: Fix Released Status in indicator-power package in Ubuntu: Fix Released Bug description: Indicator autostarted in Unity Xfce session but not in Gnome Flashback which uses same indicator. Other indicator start with start up like: indicator-sound, indicator-datetime, ... Here's its .desktop file: [Desktop Entry] Type=Application Name=Indicator Power Exec=/usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service NotShowIn=Unity; NoDisplay=true StartupNotify=false Terminal=false Like other indicators setup, Removed: NoDisplay=true and added following line fixed it: OnlyShowIn=Unity;XFCE;GNOME; AutostartCondition=GNOME3 unless-session gnome To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1330302/+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
