[Touch-packages] [Bug 1447157] Re: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid
** Changed in: hundredpapercuts Status: Confirmed => Fix Released ** Changed in: console-setup (Ubuntu) Status: Confirmed => Fix Released -- 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/1447157 Title: Keyboard layout reset to en_US after an upgrade from Utopic to Vivid Status in console-setup: New Status in One Hundred Papercuts: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Released Bug description: Upgrade from stock Utopic + updates to Vivid On Utopic I had 2 keyboard layouts 'Fr' and 'En', 'Fr' set as default After upgrade to Vivid 'En' was enabled but the indicator showed 'Fr'. Reselecting 'Fr' set 'Fr' as default and was kept upon reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: console-setup 1.108ubuntu5 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: Unity Date: Wed Apr 22 14:53:03 2015 InstallationDate: Installed on 2015-04-22 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to vivid on 2015-04-22 (0 days ago) modified.conffile..etc.console.setup.compose.VISCII.inc: # Compose sequences for VISCII mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-04-22T09:47:24 mtime.conffile..etc.console.setup.remap.inc: 2015-04-22T09:47:24 To manage notifications about this bug go to: https://bugs.launchpad.net/console-setup/+bug/1447157/+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 1045579] Re: software-properties-gtk makes a change resulting in a conf file prompt on upgrade that's unnecessary
** Changed in: software-properties (Ubuntu Precise) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1045579 Title: software-properties-gtk makes a change resulting in a conf file prompt on upgrade that's unnecessary Status in software-properties package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in software-properties source package in Precise: Fix Released Status in ubuntu-release-upgrader source package in Precise: Triaged Status in software-properties source package in Quantal: Fix Released Status in ubuntu-release-upgrader source package in Quantal: Fix Released Bug description: 1. Install Ubuntu 12.04. 2. Software Sources Updates Notify me of a new Ubuntu version For any new version. 3. update-manager -d 4. Upgrade What happens: A silly prompt appears, Replace the customized configuration file '/etc/update-manager/release-upgrades'? When you uncheck the LTS box on the updates tab, the line in /etc/update-manager/release-upgrades looks like: prompt=normal on upgrade the following is expected: Prompt=normal Marking this high as an unnecessary prompt on upgrade seems RC to me. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-properties-gtk 0.82.7.2 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Mon Sep 3 19:52:56 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-01-29 (218 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1045579/+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 1189677] Re: update-manager failing to install anything in saucy
** Changed in: update-manager (Ubuntu) Status: Confirmed = Fix Released -- 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/1189677 Title: update-manager failing to install anything in saucy Status in policykit-1 package in Ubuntu: New Status in update-manager package in Ubuntu: Fix Released Bug description: In saucy, update-manager is completely failing to install any packages. It auto-launches and presents me the list of packages to install; but when I click 'Install now', the window closes and update- manager exits. Running u-m from the console shows there are no error messages and the process exits 0. If I run update-manager without the '--no-update' flag, I'm given a dialog saying: You are not allowed to perform this action You don't have the required privileges to perform this action. Settings Try AgainOK This suggests that there is probably a policykit issue here. However, that issue isn't going to resolve itself, so update-manager needs to notify the user of the problem instead of silently exiting. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: update-manager 1:0.188 ProcVersionSignature: Ubuntu 3.9.0-3.8-generic 3.9.4 Uname: Linux 3.9.0-3-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Aptdaemon: Architecture: amd64 Date: Mon Jun 10 16:44:59 2013 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1370907861' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'747' b'com.ubuntu.update-manager' b'window-width' b'850' InstallationDate: Installed on 2010-09-24 (990 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) MarkForUpload: True PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1189677/+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 418809] Re: synaptic Lock Version not heeded in partial upgrade.
** Changed in: update-manager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/418809 Title: synaptic Lock Version not heeded in partial upgrade. Status in python-apt package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Fix Released Bug description: Binary package hint: update-manager Don't think this is related to bug #13408, because I only experience this on partial upgrades. Steps: 1) Lock a PPA version of a package (Frescobaldi) in synaptic, so that it does not install the Ubuntu repository version. (FYI, the repo version has different dependencies that I don't want). 2) On normal updates, the update-manager will now ignore that package. 3) If some other package triggers a partial upgrade, update-manager will try to upgrade frescobaldi along with its dependencies, forcing me to uninstall it, do the partial upgrade, force the version I want to reinstall, and then lock it back every time there's a partial upgrade. Partial upgrades should listen to the version lock as well, in my opinion. I'm on Karmic, with update-manager version 1:0.124.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/418809/+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 1020075] Re: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent()
** Changed in: unity (Ubuntu Precise) Assignee: (unassigned) = peterstan (stasnel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1020075 Title: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent() Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Precise: Fix Released Bug description: [Test Case] No clear test case. Ensure that unity does not crash when adjusting screen settings or after login. [Regression Potential] Launchers not put correctly on multiple monitors, edge barriers broken. Original description: This happened when adjusting my second monitor to be twin view and w/o sticky edges. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: compiz-core 1:0.9.8+bzr3249-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic x86_64 ApportVersion: 2.2.5-0ubuntu1 Architecture: amd64 Date: Mon Jul 2 07:34:15 2012 Disassembly: = 0x3d77: Cannot access memory at address 0x3d77 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120629) ProcCmdline: compiz ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x3d77:Cannot access memory at address 0x3d77 PC (0x3d77) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent(unity::ui::PointerBarrierWrapper*, std::shared_ptrunity::ui::BarrierEvent) () from /usr/lib/compiz/libunityshell.so sigc::internal::slot_call2sigc::bound_mem_functor2void, unity::ui::EdgeBarrierController::Impl, unity::ui::PointerBarrierWrapper*, std::shared_ptrunity::ui::BarrierEvent , void, unity::ui::PointerBarrierWrapper*, std::shared_ptrunity::ui::BarrierEvent ::call_it(sigc::internal::slot_rep*, unity::ui::PointerBarrierWrapper* const, std::shared_ptrunity::ui::BarrierEvent const) () from /usr/lib/compiz/libunityshell.so unity::ui::PointerBarrierWrapper::EmitCurrentData() () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::ui::EdgeBarrierController::Impl::OnPointerBarrierEvent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (compiz:1883): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed gnome-session[1806]: WARNING: Application 'compiz.desktop' killed by signal 11 gnome-session[1806]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[1806]: CRITICAL: We failed, but the fail whale is dead. Sorry (compiz:2518): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1020075/+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 1330770] Re: click packages rely upon tls for integrity and authenticity
** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress = New ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Ken VanDine (ken-vandine) = peterstan (stasnel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: click packages rely upon tls for integrity and authenticity Status in the base for Ubuntu mobile products: Confirmed Status in Click Package metadata search service: Fix Released Status in Online service used by software center: Fix Released Status in click package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity-scope-click package in Ubuntu: Fix Released Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+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
