[Touch-packages] [Bug 1590582] Re: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1590582 Title: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir Status in Light Display Manager: Fix Released Status in Light Display Manager 1.18 series: Fix Committed Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Fix Committed Bug description: When .conf [Seat:*] type=xlocal and .desktop X-LightDM-Session-Type=mir The log in /var/log/lightdm is called null. It should be called something like x-greeter.log To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1590582/+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 1583624] Re: Mir cannot open a tty when started by lightdm
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1594229] Re: Not able to use multiple USC instances
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1594229 Title: Not able to use multiple USC instances Status in Light Display Manager: Fix Released Status in Light Display Manager 1.18 series: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: LightDM currently uses one Unity System Compositor instance per Mir session for the xlocal seat. This is not allowed with modern versions of USC. We should share one USC in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1594229/+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 1360247] Re: JSON format for Variant encoding uses system locale for doubles
** Branch unlinked: lp:unity-scopes-api/staging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1360247 Title: JSON format for Variant encoding uses system locale for doubles Status in unity-scopes-api package in Ubuntu: Fix Committed Bug description: e.g. Variant(1.23).serialize_json() is going to give you different results depending on your system locale setting. This seems highly risky to use in any situation where the result could either be saved to disk (and then the system locale is changed) or if two different machines with different locales were communicating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1360247/+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 1446216] Re: [Dash] CategoryHeaderBackground is not implemented
** Branch unlinked: lp:unity-scopes-api/staging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1446216 Title: [Dash] CategoryHeaderBackground is not implemented Status in unity-scopes-api package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: Invalid Bug description: CategoryHeaderBackground is supposed to be change appearance but has no effect. Quickly checking code revealed that it hasn't been implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1446216/+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 1583624] Re: Mir cannot open a tty when started by lightdm
** Changed in: lightdm
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583624
Title:
Mir cannot open a tty when started by lightdm
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.18 series:
In Progress
Status in lightdm package in Ubuntu:
Triaged
Status in lightdm source package in Xenial:
Triaged
Bug description:
From mir-greeter.log (and with minor instrumentation from RAOF)
ERROR: QMirServer - Mir failed to start
qtmir.screens: ScreenController::ScreenController
qtmir.mir: MirServer created
qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8",
"--mode=greeter")
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: Exception while creating graphics platform
ERROR:
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
Throw in function int
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address
This occurs when trying to start the unity8 greeter under unity system
compositor
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1583624/+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 1571597] Re: No lock screen
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1571597 Title: No lock screen Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Expired Bug description: Since OTA9 (I think), I can't lock my phone anymore. I have setup a code, a passphrase, reset my phone, but nothing works... Unity never ask me for a code... Another thing that my be related is that pushing "physical" button on MX4 wake up the phone... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1571597/+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 1581417] Re: Cannot get a gps fix on krillin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1581417 Title: Cannot get a gps fix on krillin Status in Canonical System Image: Incomplete Status in location-service package in Ubuntu: Confirmed Bug description: current build number: 334 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-05-13 01:22:19 version version: 334 version ubuntu: 20160513 version device: 20160329-a9bacdb version custom: 20160505-975-38-9 Steps: 1.Setup wifi and disabled cellular data 2.Open google map app(installed from ubuntu store), allow the trust prompt and tap on "center my location" 3.Open browser with maps.google.com, allow the trust prompt and tap on "center my location" 4.Enable cellular data and disable wifi 5.Open google map app and tap on "center my location" 6.Open browser with maps.google.com and tap on "center my location" Actual result: All failed to get a gps fix Expected result: Should be able to find my location To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581417/+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 1444379] Re: Plain GPS works, GPS with wifi/3g data never uses GPS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1444379 Title: Plain GPS works, GPS with wifi/3g data never uses GPS Status in location-service package in Ubuntu: Confirmed Status in phablet-tools package in Ubuntu: Confirmed Bug description: On the BQ Aquaris E4.5 I can use the GPS, but whenever I set the GPS to use wifi/mobile data it only fixes when Wifi is near. Also when I change the setting back to GPS only, I need to reboot before the setting is applied. I am using stock BQ Aquaris E4.5 with Ubuntu 14.10 (all updated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1444379/+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 1323009] Re: Light DM does not show the current automatic wallpaper changer background on Login Screen
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1323009 Title: Light DM does not show the current automatic wallpaper changer background on Login Screen Status in unity-greeter package in Ubuntu: New Bug description: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr and notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out of the user's account to show the Light DM Login screen. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. (This is the issue; the same background that was shown on the user's home screen and the user's Lock screen should appear here). 7. Now, login to the same user's account. 8. Notice there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. (This may be a side-effect of the issue in step 6). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1323009/+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 1590582] Re: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir
** Branch linked: lp:lightdm/1.18 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1590582 Title: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Fix Committed Bug description: When .conf [Seat:*] type=xlocal and .desktop X-LightDM-Session-Type=mir The log in /var/log/lightdm is called null. It should be called something like x-greeter.log To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1590582/+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 1594135] Re: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1594135 Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd Status in eglibc package in Ubuntu: New Bug description: x ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6:amd64 2.19-0ubuntu6.6 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sun Jun 19 18:31:05 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc6:amd64:2.19-0ubuntu6.6:pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd ErrorMessage: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd InstallationDate: Installed on 2015-07-22 (333 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: eglibc Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1594135/+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 1594229] [NEW] Not able to use multiple USC instances
Public bug reported: LightDM currently uses one Unity System Compositor instance per Mir session for the xlocal seat. This is not allowed with modern versions of USC. We should share one USC in this case. ** Affects: lightdm Importance: High Status: Fix Committed ** Affects: lightdm/1.18 Importance: High Status: Triaged ** Affects: lightdm (Ubuntu) Importance: High Status: Triaged ** Affects: lightdm (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: lightdm (Ubuntu Yakkety) Importance: High Status: Triaged ** Also affects: lightdm (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lightdm Importance: Undecided Status: New ** Also affects: lightdm/1.18 Importance: Undecided Status: New ** Changed in: lightdm Status: New => Fix Committed ** Changed in: lightdm Milestone: None => 1.19.1 ** Changed in: lightdm/1.18 Status: New => Triaged ** Changed in: lightdm/1.18 Importance: Undecided => High ** Changed in: lightdm Importance: Undecided => High ** Changed in: lightdm (Ubuntu Xenial) Status: New => Triaged ** Changed in: lightdm (Ubuntu Yakkety) Status: New => Triaged ** Changed in: lightdm (Ubuntu Xenial) Importance: Undecided => High ** Changed in: lightdm (Ubuntu Yakkety) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1594229 Title: Not able to use multiple USC instances Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.18 series: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: LightDM currently uses one Unity System Compositor instance per Mir session for the xlocal seat. This is not allowed with modern versions of USC. We should share one USC in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1594229/+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 1263533] Re: Cannot start without unity-system-compositor
Closing, assuming was a configuration issue. ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1263533 Title: Cannot start without unity-system-compositor Status in lightdm package in Ubuntu: Invalid Bug description: I can only start lightdm when usc is installed. I already tried purging lightdm but still no difference. Even manually executing "sudo start lightdm" doesn't work. However, I can still call "startx" and get an xsession running. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-0.9-generic 3.13.0-rc4 Uname: Linux 3.13.0-0-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 22 20:56:30 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-05-12 (954 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-11 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1263533/+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 1590582] Re: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir
** Changed in: lightdm Status: Triaged => Fix Committed ** Changed in: lightdm Milestone: None => 1.19.1 ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Yakkety) Status: New => Fix Released ** Changed in: lightdm (Ubuntu Yakkety) Status: Fix Released => Fix Committed ** Changed in: lightdm (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: lightdm (Ubuntu Xenial) Importance: Undecided => High ** Changed in: lightdm (Ubuntu Xenial) Status: New => Triaged ** Also affects: lightdm/1.18 Importance: Undecided Status: New ** Changed in: lightdm/1.18 Status: New => Fix Committed ** Changed in: lightdm/1.18 Milestone: None => 1.18.2 ** Changed in: lightdm/1.18 Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1590582 Title: greeter log is called "(null)-greeter" when seat type is xlocal and session type is mir Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Fix Committed Bug description: When .conf [Seat:*] type=xlocal and .desktop X-LightDM-Session-Type=mir The log in /var/log/lightdm is called null. It should be called something like x-greeter.log To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1590582/+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 1594217] [NEW] package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
Public bug reported: running the software updates using Unbuntu 16. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 19 21:55:53 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationDate: Installed on 2016-06-20 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1594217 Title: package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in util-linux package in Ubuntu: New Bug description: running the software updates using Unbuntu 16. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 19 21:55:53 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationDate: Installed on 2016-06-20 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1594217/+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 1575604] Re: Fast repeated scrolling with a finger changes direction of the scrolling
Nexus 4 mako proposed has this problem too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1575604 Title: Fast repeated scrolling with a finger changes direction of the scrolling Status in Oxide: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When scrolling on a page with repeated gestures with the finger on the screen, it often changes the direction of the scrolling and scrolls super fast. So if I am far down on a page and scrolls a few times with the finger, it suddenly start to scroll upwards super fast to the top. It seems like it happens if it lags while scrolling and it misses part of the gesture. Experienced on an M10 with OTA-10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1575604/+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 1588123] Re: binutils - Bugzilla ID 20159
Bug was fixed in 2.26 and trunk of project (see Bugzilla report linked). Hoping this gets into Ubuntu 16.04 soon so I can stop ignoring the error and continue developing tests that rely on a fixed version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1588123 Title: binutils - Bugzilla ID 20159 Status in binutils package in Ubuntu: New Bug description: Moved to Ubuntu 16.04 from Ubuntu 14.04 and was doing some Test Driven Development where we began to override the "time" system call from glibc. Failed on Ubuntu 16.04 and I filed a report with the binutils Bugzilla. https://sourceware.org/bugzilla/show_bug.cgi?id=20159 (Turns out it was not dynamic linking that was the problem but GNU ld itself at link-time.) They have since developed a patch and I want to get this into the binutils 1.26 line that is maintained for 16.04 so we can continue to properly develop software on this distribution. Thanks! - Paul Braman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1588123/+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 1328747] Re: x264 10bit wrapper script
/usr/bin/x264-10bit is available for some time now. ** Changed in: x264 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to x264 in Ubuntu. https://bugs.launchpad.net/bugs/1328747 Title: x264 10bit wrapper script Status in x264 package in Ubuntu: Fix Released Bug description: libx264-142 has an additional 10bit library version available, but by default x264 loads the 8 bit version. Can you add a wrapper script or something like that so that we can use 10bit without manually using LD_PRELOAD? Just a simple script like this: #!/bin/sh LD_PRELOAD="/usr/lib/x86_64-linux-gnu/x264-10bit/libx264.so.142" x264 "$@" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1328747/+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 1594198] [NEW] Terminal app crashes with "Failed to load libGLESv2"
Public bug reported: Most likely due to [1] (checking), terminal app crashes on startup, printing: > Failed to load libGLESv2 An example OOPS can be seen under [2]. [1] https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248 [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1 Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Jun 20 01:05:39 2016 InstallationDate: Installed on 2016-06-18 (1 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304) SourcePackage: qtubuntu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: canonical-devices-system-image Importance: Critical Assignee: Michał Sawicz (saviq) Status: Triaged ** Affects: qtubuntu (Ubuntu) Importance: Critical Assignee: Gerry Boland (gerboland) Status: Triaged ** Tags: apport-bug armhf third-party-packages vivid ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Milestone: backlog => 12 ** Description changed: Most likely due to [1] (checking), terminal app crashes on startup, printing: > Failed to load libGLESv2 - [1] https://code.launchpad.net/~gerboland/qtubuntu/adopt-more- - eglconvenience2/+merge/295248 + An example OOPS can be seen under [2]. + + [1] https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248 + [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1 Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Jun 20 01:05:39 2016 InstallationDate: Installed on 2016-06-18 (1 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304) SourcePackage: qtubuntu UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1594198 Title: Terminal app crashes with "Failed to load libGLESv2" Status in Canonical System Image: Triaged Status in qtubuntu package in Ubuntu: Triaged Bug description: Most likely due to [1] (checking), terminal app crashes on startup, printing: > Failed to load libGLESv2 An example OOPS can be seen under [2]. [1] https://code.launchpad.net/~gerboland/qtubuntu/adopt-more-eglconvenience2/+merge/295248 [2] https://errors.ubuntu.com/oops/020da136-3673-11e6-9055-fa163eec78fa ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtubuntu-android 0.62+15.04.20160527.1-0ubuntu1 Uname: Linux 3.10.100-user-01767-gf5aa556-dirty aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Jun 20 01:05:39 2016 InstallationDate: Installed on 2016-06-18 (1 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160618-020304) SourcePackage: qtubuntu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594198/+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 1317131] Re: avs [error]: failed to load avisynth
*** This bug is a duplicate of bug 1328744 *** https://bugs.launchpad.net/bugs/1328744 ** This bug has been marked a duplicate of bug 1328744 Trusty: x264 not built with lavf or ffms support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to x264 in Ubuntu. https://bugs.launchpad.net/bugs/1317131 Title: avs [error]: failed to load avisynth Status in x264 package in Ubuntu: Confirmed Bug description: On U14.04: x264 cannot open anything, tried with a RAW AVI file and an X264 MP4 file, the error message always: Command: x264 --qp 0 --bitrate 3000 1.mp4 -o tmp_h264.mp4 avs [error]: failed to load avisynth raw [error]: raw input requires a resolution. x264 [error]: could not open input file `1.mp4' via any method! Same with an RAW AVI file: Command: x264 --qp 0 --bitrate 3000 /tmp/tmp2j4v4j.avi -o tmp_h264.mp4 avs [error]: failed to load avisynth raw [error]: raw input requires a resolution. x264 [error]: could not open input file `/tmp/tmp2j4v4j.avi' via any method! It worked on U13.10. Differences: x264 -h @13.10: x264 core:123 r2189 35cf912 Syntax: x264 [options] -o outfile infile Infile can be raw (in which case resolution is required), or YUV4MPEG (*.y4m), or Avisynth if compiled with support (no). or libav* formats if compiled with lavf support (yes) or ffms support (yes). Outfile type is selected by filename: .264 -> Raw bytestream .mkv -> Matroska .flv -> Flash Video .mp4 -> MP4 if compiled with GPAC support (yes) Output bit depth: 8 (configured at compile time) x264 -h @14.04: x264 core:142 r2389 956c8d8 Syntax: x264 [options] -o outfile infile Infile can be raw (in which case resolution is required), or YUV4MPEG (*.y4m), or Avisynth if compiled with support (yes). or libav* formats if compiled with lavf support (no) or ffms support (no). Outfile type is selected by filename: .264 -> Raw bytestream .mkv -> Matroska .flv -> Flash Video .mp4 -> MP4 if compiled with GPAC or L-SMASH support (gpac) Output bit depth: 8 (configured at compile time) It try to use Avisynth, which is unavailable at U14.04. It used lavf/ffms @13.10, and worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1317131/+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 1536158] Re: Upgrade to 1.1.0 that was released in November 2015
** Changed in: alsa-driver (Ubuntu) Status: Triaged => Confirmed ** Changed in: alsa-driver-2.6.28-12 (Ubuntu) Status: New => Confirmed ** Summary changed: - Upgrade to 1.1.0 that was released in November 2015 + Upgrade to 1.1.1 that was released in March 2016 ** Description changed: - Please, upgrade to 1.1.0 that was released in November 2015 + Please, upgrade to 1.1.1 that was released in March 2016, see http://www + .alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1536158 Title: Upgrade to 1.1.1 that was released in March 2016 Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver-2.6.28-12 package in Ubuntu: Confirmed Bug description: Please, upgrade to 1.1.1 that was released in March 2016, see http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1536158/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
I confirm the very same bug also occurs in 12.04 LTS (just downloaded 12.04.5-desktop-amd64 and tested). Thanks, MZ ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: New Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1570749] Re: Upgrade to 11.7 from May 2016
See also https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.7 ** Summary changed: - Upgrade to 11.6 from February 2016 + Upgrade to 11.7 from May 2016 ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1570749 Title: Upgrade to 11.7 from May 2016 Status in libav package in Ubuntu: Confirmed Bug description: Please, upgrade to 11.6 from February 2016, see https://libav.org/ and https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1570749/+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 1435923] Re: [greeter/desktop] the password entry is not focussed by default
** Changed in: unity8 (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1435923 Title: [greeter/desktop] the password entry is not focussed by default Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Using current vivid in desktop mode (desktop-next live session or installed), the greeter screen for password has an entry, but this one is not getting the keyboard focus by default, which is annoying since you can't directly type your password then To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435923/+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 1582419] Re: mounting usb drives asks for password
Could be related to #1577227 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582419 Title: mounting usb drives asks for password Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Every time I insert usb drive into my laptop xubuntu 16.04 asks for password (from udisks2). This is as dumb as windows and such stupidity have not happened in 15.10. I've check user's privileges and all is marked as allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582419/+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 1091647] Re: Smart completion does not work for localc and CSV and TSV files
Can this be solved by Ubuntu or does it need to get reported at Bash in https://savannah.gnu.org/support/?group=bash=browse ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1091647 Title: Smart completion does not work for localc and CSV and TSV files Status in bash package in Ubuntu: Confirmed Bug description: (Not really sure if this is related to bash) Smart completion does not work for localc and CSV (.csv comma separated values) and TSV (.tsv tab separated values) files on the command line in bash. Please support this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1091647/+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 1091646] Re: Smart completion does not work for firefox and XML files
Can this be solved by Ubuntu or does it need to get reported at Bash in https://savannah.gnu.org/support/?group=bash=browse ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1091646 Title: Smart completion does not work for firefox and XML files Status in bash package in Ubuntu: Confirmed Bug description: (Not really sure if this is related to bash) Smart completion does not work for firefox and XML (.xml) files on the command line in bash. Please support this. TTX (.ttx) files which are generated by fonttools and are in XML format and XSD (.xsd) XML Schema Files which are also in XML format should be supported too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1091646/+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 1594167] [NEW] MX4 & BQ M10 camera app slow to open after OTA-11 update
Public bug reported: Hi I am using the MX4 with OTA-11 software update. After I completed the latest update (OTA-11) there is a longer delay of up to 8s before the camera image appears after tapping the icon. The application itself opens quickly and shows the camera icon, but the actual lens image takes another 6~8s tp appear. The delay with earlier versions was not so long, can you please investigate this problem. Note, the camera delay timing is also slow (8s) on my BQ M10 tablet with OTA-11, so this looks like a common problem across multiple devices. Thanks for your support and hard work. Regards Dave H ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1594167 Title: MX4 & BQ M10 camera app slow to open after OTA-11 update Status in camera-app package in Ubuntu: New Bug description: Hi I am using the MX4 with OTA-11 software update. After I completed the latest update (OTA-11) there is a longer delay of up to 8s before the camera image appears after tapping the icon. The application itself opens quickly and shows the camera icon, but the actual lens image takes another 6~8s tp appear. The delay with earlier versions was not so long, can you please investigate this problem. Note, the camera delay timing is also slow (8s) on my BQ M10 tablet with OTA-11, so this looks like a common problem across multiple devices. Thanks for your support and hard work. Regards Dave H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1594167/+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 1580601] Re: __nih_abort_msg symbol cannot be read any more
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnih in Ubuntu.
https://bugs.launchpad.net/bugs/1580601
Title:
__nih_abort_msg symbol cannot be read any more
Status in gcc-5 package in Ubuntu:
New
Status in libnih package in Ubuntu:
New
Bug description:
libnih has a global symbol __nih_abort_msg that contains the message
of the last failed nih_assert() (similar to glibc's own __abort_msg
and glib's __glib_assert_msg). Apport uses these to produce a more
meaningful crash report than just "/bin/foo crashed with SIGABRT", as
in these case the thing you actually want to see is the assertion
message.
This stopped working in yakkety/amd64. apport's
report.test_add_gdb_info_abort_libnih() now fails:
ERROR: test_add_gdb_info_abort_libnih (__main__.T)
add_gdb_info() with libnih assertion
--
Traceback (most recent call last):
File "./test_report.py", line 886, in test_add_gdb_info_abort_libnih
self.assertIn('Assertion failed in main: 1 < 0', pr['AssertionMessage'])
File "/usr/lib/python3.5/collections/__init__.py", line 985, in __getitem__
raise KeyError(key)
KeyError: 'AssertionMessage'
This can be reproduced with the attached script which compiles a
trivial nih_assert() C program, runs it, and runs gdb on the produced
core dump. Up until xenial it looks like:
$ ./nih-assert.sh
(null)::2: Assertion failed in main: 1 < 0
Aborted (core dumped)
[New LWP 9838]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./nih-assert'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7f28c070d418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
$1 = 0x25400f0 ":2: Assertion failed in main: 1 < 0"
But in yakkety/amd64 it now looks like
$ ./nih-assert.sh
(null)::2: Assertion failed in main: 1 < 0
Aborted (core dumped)
[New LWP 10489]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./nih-assert'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7fd303865418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
$1 = 0x869400f0
This can be reproduced easily in a schroot, you need to install "libnih-dev
pkg-config gdb".
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libnih-dev 1.0.3-4.3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: i3
Date: Wed May 11 15:13:46 2016
Dependencies:
gcc-6-base 6.0.1-0ubuntu1
libc6 2.23-0ubuntu3
libgcc1 1:6.0.1-0ubuntu1
libnih1 1.0.3-4.3ubuntu1
EcryptfsInUse: Yes
SourcePackage: libnih
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1580601/+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 1576726] Re: [SRU] network-manager 1.2.0
Works for me, marking as verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1576726 Title: [SRU] network-manager 1.2.0 Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Fix Released Status in network-manager-vpnc package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Status in network-manager-applet source package in Xenial: Fix Released Status in network-manager-openconnect source package in Xenial: Invalid Status in network-manager-openvpn source package in Xenial: Confirmed Status in network-manager-ssh source package in Xenial: Fix Committed Status in network-manager-vpnc source package in Xenial: Confirmed Status in network-manager-openconnect package in Debian: Fix Released Bug description: [Impact] Xenial was released with upstream beta2 version of network-manager to keep in time for the release schedule, and upstream stable release has been made so it's time to update to it. [Testcase] After upgrading the package, user should still be able to connect to networks like Ethernet, Wi-Fi and VPNs. [Regression Potential] Potential of causing regression is relatively small because there is not big changes made during beta2 -> stable process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1592649] Re: whoopsie fails to build from source in xenial
the package successfully built on all archs ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1592649 Title: whoopsie fails to build from source in xenial Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Bug description: whoopsie fails to build from source in xenial on all architectures, seen in a test rebuild. This already seems to be fixed in yakkety. http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test- rebuild-20160614-xenial.html fix at http://launchpadlibrarian.net/259116965/whoopsie_0.2.52_0.2.53.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1592649/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
We all Are having the exact same issue -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1593964] Re: OSK stays on screen when not needed
*** This bug is a duplicate of bug 1590820 *** https://bugs.launchpad.net/bugs/1590820 ** This bug has been marked a duplicate of bug 1590820 Inconsistent behavior when using search in the dash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1593964 Title: OSK stays on screen when not needed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: M10 rc-proposed Steps to reproduce: 1. Go to the app scope 2. Tap the 'search' icon. The keyboard appears. 3. Tap 'Cancel' Expected result: The keyboard hides What happens instead: The keyboard stays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1593964/+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 1588162] Re: Time in header is UTC instead oft UTC+2
I think I was a little bit too enthusiastic, after another reboot I am back to the setting Africa/Accra and UTC +2. But since the time in the top bar now matches the local time I think I can manage. But clearly I can not change the timezone in the system setting. I wonder what happens when I leave my timezone. Maybe you could help me what to check else. ** Attachment added: "screenshot20160619_193829423.png" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1588162/+attachment/4686745/+files/screenshot20160619_193829423.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588162 Title: Time in header is UTC instead oft UTC+2 Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I think it happened After OTA 11. All other time displays are correct also the alarm matches the real time, checked the kalendar too the red time indicator is also correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1588162] Re: Time in header is UTC instead oft UTC+2
ok, I got it now by overwriting the file localtime with Europe/Berlin. Now it works. But even after that I still had Africa/Accra in the system settings but with the UTC +2 (clearly after rebooting the system). But it let me change it to Berlin, which was not possible before.. So I guess somehow the file localtime was in the beginning damaged, otherwise the setting ETC/UTC with UTC +2 could not have been set in the beginning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588162 Title: Time in header is UTC instead oft UTC+2 Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I think it happened After OTA 11. All other time displays are correct also the alarm matches the real time, checked the kalendar too the red time indicator is also correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1593964] Re: OSK stays on screen when not needed
** Package changed: unity-scope-click (Ubuntu) => ubuntu-keyboard (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1593964 Title: OSK stays on screen when not needed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: M10 rc-proposed Steps to reproduce: 1. Go to the app scope 2. Tap the 'search' icon. The keyboard appears. 3. Tap 'Cancel' Expected result: The keyboard hides What happens instead: The keyboard stays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1593964/+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 1593964] [NEW] OSK stays on screen when not needed
You have been subscribed to a public bug: M10 rc-proposed Steps to reproduce: 1. Go to the app scope 2. Tap the 'search' icon. The keyboard appears. 3. Tap 'Cancel' Expected result: The keyboard hides What happens instead: The keyboard stays ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: Confirmed -- OSK stays on screen when not needed https://bugs.launchpad.net/bugs/1593964 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. -- 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 1574020] Re: Can't use networkmanager from lightdm
I'm also affected by it. Enbaling WiFi after logging in works fine, but not before. Fresh installation and nothing changed. -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1569582] Re: Add Bluetooth apparmor policy
** Tags added: bluetooth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1569582 Title: Add Bluetooth apparmor policy Status in Canonical System Image: Fix Committed Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Bug description: I have created a content hub plugin that allows sending files via Bluetooth. At this point this only works when unconfined so here is a request to extend the apparmor policies to allow some things over Bluetooth. This plugin does a device discovery and then uses Bluez' obex client to transmit the file. When turning on apparmor on it, it first bails out with the messages below. However, once those are resolved, it'll probably want some more. I have attached the confined package to this bug so it can be easily tested. Please disregard the app in there completey and only evaluate the shareplugin in the package. After installing the click, open the gallery, share an image and select Bluetooth to start the process: [65927.602181] type=1107 audit(1460496066.496:2509): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.602199] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65927.607588] type=1107 audit(1460496066.506:2510): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.607606] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65928.611714] type=1107 audit(1460496067.506:2511): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65928.611733] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65929.615630] type=1107 audit(1460496068.516:2512): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65929.615649] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65930.619178] type=1107 audit(1460496069.516:2513): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65930.619197] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65931.622804] type=1107 audit(1460496070.516:2514): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65931.622822] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65932.626550] type=1107 audit(1460496071.526:2515): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65932.626569] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65933.630102] type=1107 audit(1460496072.526:2516): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65933.630121] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65934.633739] type=1107 audit(1460496073.536:2517): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined"
[Touch-packages] [Bug 1594135] [NEW] package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd
Public bug reported: x ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6:amd64 2.19-0ubuntu6.6 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sun Jun 19 18:31:05 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc6:amd64:2.19-0ubuntu6.6:pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd ErrorMessage: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd InstallationDate: Installed on 2015-07-22 (333 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: eglibc Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1594135 Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd Status in eglibc package in Ubuntu: New Bug description: x ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6:amd64 2.19-0ubuntu6.6 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sun Jun 19 18:31:05 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc6:amd64:2.19-0ubuntu6.6:pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd ErrorMessage: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd InstallationDate: Installed on 2015-07-22 (333 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: eglibc Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: pakket libc6:amd64 is reeds geïnstalleerd en geconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1594135/+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 1424791] Re: Ubuntu Phone: cellular data did not recover after losing coverage
Hi, my phone is affected by exactly the same problem as described by H(deflector). Probably since the last update. Aqaris EQ4.5 20160524.1. Greetings, Benediktus -- 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/1424791 Title: Ubuntu Phone: cellular data did not recover after losing coverage Status in NetworkManager: New Status in network-manager package in Ubuntu: Incomplete Bug description: Hi! Today I travelled in train and I lost my mobile signal. BUG: After have signal, the cellular data (3G) is not recovering. I have to enter in plane mode and exit from that mode for having 3G again. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1424791/+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 1594127] Re: No update
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. Are you reporting a bug against xorg, the update/upgrade process or something else? At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1594127 Title: No update Status in xorg package in Ubuntu: Incomplete Bug description: Since some months there will stop the update of ubuntu. There are paketswith no confidence to load. What is to do? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 19 17:24:55 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] InstallationDate: Installed on 2014-12-06 (561 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: LENOVO 1703WMG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=bb5b4686-52d4-4137-8fc2-efdfbecac3cd ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7BETD6WW (2.17 ) dmi.board.name: 1703WMG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7BETD6WW(2.17):bd06/19/2008:svnLENOVO:pn1703WMG:pvrThinkPadX60s:rvnLENOVO:rn1703WMG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1703WMG dmi.product.version: ThinkPad X60s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jun 19 14:55:00 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16384 vendor LEN xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1594127/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
I also see the same problem coming out of suspend. Manually restarting network-manager with 'sudo systemctl restart network-manager.service' is a workaround but not a solution. I go in and out of suspend a lot with my laptop so this one is very annoying. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded
It seems that MongoDB is also broken due to this https://jira.mongodb.org/browse/SERVER-23397 Workarounds? -- 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/1558331 Title: message "The repository is insufficiently signed by key (weak digest)" is poorly worded Status in apt package in Ubuntu: Fix Released Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1594127] [NEW] No update
Public bug reported: Since some months there will stop the update of ubuntu. There are paketswith no confidence to load. What is to do? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 19 17:24:55 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] InstallationDate: Installed on 2014-12-06 (561 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: LENOVO 1703WMG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=bb5b4686-52d4-4137-8fc2-efdfbecac3cd ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7BETD6WW (2.17 ) dmi.board.name: 1703WMG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7BETD6WW(2.17):bd06/19/2008:svnLENOVO:pn1703WMG:pvrThinkPadX60s:rvnLENOVO:rn1703WMG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1703WMG dmi.product.version: ThinkPad X60s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jun 19 14:55:00 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16384 vendor LEN xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1594127 Title: No update Status in xorg package in Ubuntu: New Bug description: Since some months there will stop the update of ubuntu. There are paketswith no confidence to load. What is to do? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 19 17:24:55 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] InstallationDate: Installed on 2014-12-06 (561 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: LENOVO 1703WMG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=bb5b4686-52d4-4137-8fc2-efdfbecac3cd ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7BETD6WW (2.17 ) dmi.board.name: 1703WMG
[Touch-packages] [Bug 1594124] [NEW] [MS-7592, VIA VT1708S, Green Headphone Out, Front] No sound at all
Public bug reported: when i reboot my pc and login then sound is fine from the rear port but front headset port it doesn't work well do i need some packages ? i tried googling it but really hard to find out what happened it used to work well on ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: becas 11813 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 19 20:35:49 2016 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: becas 11813 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7592, VIA VT1708S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7592 dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.3:bd11/01/2010:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnMS-7592:rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1594124 Title: [MS-7592, VIA VT1708S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: when i reboot my pc and login then sound is fine from the rear port but front headset port it doesn't work well do i need some packages ? i tried googling it but really hard to find out what happened it used to work well on ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: becas 11813 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 19 20:35:49 2016 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: becas 11813 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7592, VIA VT1708S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7592 dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.3:bd11/01/2010:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnMS-7592:rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1594124/+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 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols
I am running Ubuntu Mate Xenial and gdb always reports the following bt, symbols or not: ``` Program received signal SIGSEGV, Segmentation fault. 0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3 (gdb) bt #0 0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3 #1 0x76fd983a in ?? () from /lib/ld-linux-armhf.so.3 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Is this related? ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1325503 Title: gdb reports 'corrupt stack' on armhf without symbols Status in Linaro GDB: New Status in gdb package in Ubuntu: Triaged Bug description: [Test Case] sleep 120 & kill -SEGV %1 Observe a corrupt stack in the generated crash file. Original Report --- On armhf crash files fail to retrace and gdb reports 'corrupt stack' errors For example bug 1323241 Thread 1 (Thread 0xb0b3b450 (LWP 2243)): #0 0x0030 in ?? () No symbol table info available. #1 0xa9990cbe in ?? () from /usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Launcher/libUnityLauncher-qml.so No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) I also tried directly on the device to run an unstripped and stripped build of cat and gdb fails to unwind the stack when the binary is stripped. The result of this test is: == unstripped == Reading symbols from ./cat...done. (gdb) run Starting program: /home/phablet/tmp/coreutils-8.21/src/cat ^C Program received signal SIGINT, Interrupt. 0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6 (gdb) bt #0 0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6 #1 0xb648 in read (__nbytes=65536, __buf=0x19000, __fd=0) at /usr/include/arm-linux-gnueabihf/bits/unistd.h:44 #2 safe_read (fd=0, buf=buf@entry=0x19000, count=count@entry=65536) at lib/safe-read.c:66 #3 0x9ace in simple_cat (bufsize=65536, buf=0x19000 "") at src/cat.c:168 #4 main (argc=1, argv=) at src/cat.c:730 (gdb) quit == stripped == Reading symbols from ./cat...(no debugging symbols found)...done. (gdb) run Starting program: /home/phablet/tmp/coreutils-8.21/src/cat ^C Program received signal SIGINT, Interrupt. 0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6 (gdb) bt #0 0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6 #1 0xb648 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) I'd expect the same number of frames and addresses when the binary is stripped or not with '??' instead of names when it is stripped. ProblemType: BugDistroRelease: Ubuntu 14.10 Package: gdb (not installed) Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Mon Jun 2 11:07:07 2014 InstallationDate: Installed on 2014-06-02 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140602)SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdb-linaro/+bug/1325503/+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
Re: [Touch-packages] [Bug 1570878] Re: GPS issue: Updates the speed field only
Thanks a lot! It's working again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1570878 Title: GPS issue: Updates the speed field only Status in Canonical System Image: Fix Committed Status in location-service package in Ubuntu: Fix Released Bug description: Only the speed data is updated in each new GPS position. Any other data, will be updated each 11 seconds. Testing: Nexus 4. OS: Ubuntu 15.04 (r418). WIFI Disabled. 3G Enabled. Open Sensor Status and drive (for see how the speed changes). Bug: There are new GPS positions each ~800ms, but they will update only the Speed field. Any other field (like altitude, latitude...) will be updated each 11 seconds. I tested same behavior with OpenStreetMap and uNav apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1570878/+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 1593936] Re: eON games crash at startup with nvidia-prime
** Description changed: I tried to run Dirt Showdown from Steam but each time I try, it crashes. Reporting the problem to Virtual Programming they said that the problem is within the driver itself. Here are the logs of the crash: nvidia-358 https://gist.github.com/vpltd-peterm/5d299e3f37007785182cc9a49bb79724 + nvidia-361 https://gist.github.com/vpltd-peterm/f56dd927cf945787bdd39b38e869f0d8 nvidia-364 https://gist.github.com/vpltd-peterm/a886bd9c62a04325be28097e572d383a Here are two bugs from Virtual Programming concerning this issue: https://github.com/virtual-programming/dirtshowdown-linux/issues/31 https://github.com/virtual-programming/witcher2-linux/issues/164 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 - GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 + GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jun 18 09:42:35 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] -Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] + Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] + Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2015-03-21 (454 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash intel_pstate=enable i8042.noloop=1 acpi_osi= vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 18 10:28:16 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: -
[Touch-packages] [Bug 1594115] [NEW] package libxml2 2.9.1+dfsg1-3ubuntu4.8 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file s
Public bug reported: This is not a bug - / was mounted read-only, so the installation failed. Would be good if there was a button to cancel / discard the bug report in the bug tracker. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxml2 2.9.1+dfsg1-3ubuntu4.8 ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39 Uname: Linux 3.13.0-88-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Jun 14 16:51:55 2016 DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4.8:unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.14 SourcePackage: libxml2 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.8 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system UpgradeStatus: Upgraded to trusty on 2015-07-16 (339 days ago) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-package need-duplicate-check trusty ** Changed in: libxml2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1594115 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.8 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1 .dpkg-new': Read-only file system Status in libxml2 package in Ubuntu: Invalid Bug description: This is not a bug - / was mounted read-only, so the installation failed. Would be good if there was a button to cancel / discard the bug report in the bug tracker. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxml2 2.9.1+dfsg1-3ubuntu4.8 ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39 Uname: Linux 3.13.0-88-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Jun 14 16:51:55 2016 DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4.8:unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.14 SourcePackage: libxml2 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.8 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': Read-only file system UpgradeStatus: Upgraded to trusty on 2015-07-16 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1594115/+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 1594114] [NEW] Camera-app crashes when processing HDR photo
Public bug reported: BQ E5 OTA-11, but it has been like this since i got it. (~january 2016) 7/10 when I take a photo with HDR enabled, the app crashes while processing the photo. I get the spinning wheel and then it dies and the photo is not saved. Please let me know what logs i can give you to help you fix this. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1594114 Title: Camera-app crashes when processing HDR photo Status in camera-app package in Ubuntu: New Bug description: BQ E5 OTA-11, but it has been like this since i got it. (~january 2016) 7/10 when I take a photo with HDR enabled, the app crashes while processing the photo. I get the spinning wheel and then it dies and the photo is not saved. Please let me know what logs i can give you to help you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1594114/+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 1593561] Re: help of germany
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also change the bug title to be more descriptive of you problem. Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1593561 Title: help of germany Status in xorg package in Ubuntu: Incomplete Bug description: system is low ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 17 06:45:01 2016 DistUpgraded: 2016-06-14 23:59:56,639 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation NV44A [GeForce 6200] [10de:0221] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. NV44A [GeForce 6200] [1682:2152] InstallationDate: Installed on 2016-06-13 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) MachineType: FUJITSU SIEMENS D1520 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-14 (2 days ago) dmi.bios.date: 10/01/2003 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 4.06 Rev. 1.03.1520 dmi.board.name: D1520 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D1520 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.03.1520:bd10/01/2003:svnFUJITSUSIEMENS:pnD1520:pvr:rvnFUJITSUSIEMENS:rnD1520:rvrS26361-D1520:cvnFUJITSUSIEMENS:ct6:cvr: dmi.product.name: D1520 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jun 17 06:22:47 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593561/+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 1323009] Re: Light DM does not show the current automatic wallpaper changer background on Login Screen
** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1323009 Title: Light DM does not show the current automatic wallpaper changer background on Login Screen Status in lightdm package in Ubuntu: New Bug description: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr and notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out of the user's account to show the Light DM Login screen. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. (This is the issue; the same background that was shown on the user's home screen and the user's Lock screen should appear here). 7. Now, login to the same user's account. 8. Notice there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. (This may be a side-effect of the issue in step 6). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1323009/+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 1323009] [NEW] Light DM does not show the current automatic wallpaper changer background on Login Screen
You have been subscribed to a public bug: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr and notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out of the user's account to show the Light DM Login screen. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. (This is the issue; the same background that was shown on the user's home screen and the user's Lock screen should appear here). 7. Now, login to the same user's account. 8. Notice there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. (This may be a side-effect of the issue in step 6). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Light DM does not show the current automatic wallpaper changer background on Login Screen https://bugs.launchpad.net/bugs/1323009 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- 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 1594105] [NEW] package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
Public bug reported: I was installing the Skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 19 08:56:22 2016 DuplicateSignature: package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu3) ... dpkg: error processing package libqt4-sql:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-06-18 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: qt4-x11 Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check xenial -- 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/1594105 Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in qt4-x11 package in Ubuntu: New Bug description: I was installing the Skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 19 08:56:22 2016 DuplicateSignature: package:libqt4-sql:i386:4:4.8.7+dfsg-5ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu3) ... dpkg: error processing package libqt4-sql:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-06-18 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: qt4-x11 Title: package libqt4-sql:i386 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1594105/+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 1545454] Re: Wrong keyboard layout while crypting new installation drive
** Package changed: ubuntu => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1545454 Title: Wrong keyboard layout while crypting new installation drive Status in xkeyboard-config package in Ubuntu: New Bug description: Hello, Have been experiencing an issue when I type the password for drive encryption of a new Ubuntu OS install. I am able to type the password as expected, but I am using an AZERTY keyboard layout and the install picks up my password with the QUERTY layout. I go through the full install process and after the 1st reboot the OS asks for the drive encryption password which is stored with the wrong keyboard layout (QUERTY in my case). Without a hack to figure out what are the keys equivalent, I am not able to use the fresh OS install and I have to go through the install again; when I use QUERTY/AZERTY keys that are not similar for the drive encryption password. That bug being said, a few times I did not use that security function or I purposely use a weak password to be sure to able to log into the fresh Ubuntu install. I have done the test on the 14.04 release and I have experienced the same bug on the latest Xunbuntu release as well. Thank you, Bob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1545454/+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 1559670] Re: auto login doesn't work
According to https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, LightDM is the right package for this bug report ** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1559670 Title: auto login doesn't work Status in lightdm package in Ubuntu: New Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 I want to autologin. When I check the autologin "on" and I restart, I have to put my password at restart. When i see the parameter again, it always comes to "off" after restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1559670/+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 1545454] [NEW] Wrong keyboard layout while crypting new installation drive
You have been subscribed to a public bug: Hello, Have been experiencing an issue when I type the password for drive encryption of a new Ubuntu OS install. I am able to type the password as expected, but I am using an AZERTY keyboard layout and the install picks up my password with the QUERTY layout. I go through the full install process and after the 1st reboot the OS asks for the drive encryption password which is stored with the wrong keyboard layout (QUERTY in my case). Without a hack to figure out what are the keys equivalent, I am not able to use the fresh OS install and I have to go through the install again; when I use QUERTY/AZERTY keys that are not similar for the drive encryption password. That bug being said, a few times I did not use that security function or I purposely use a weak password to be sure to able to log into the fresh Ubuntu install. I have done the test on the 14.04 release and I have experienced the same bug on the latest Xunbuntu release as well. Thank you, Bob ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- Wrong keyboard layout while crypting new installation drive https://bugs.launchpad.net/bugs/1545454 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. -- 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 1559670] [NEW] auto login doesn't work
You have been subscribed to a public bug: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 I want to autologin. When I check the autologin "on" and I restart, I have to put my password at restart. When i see the parameter again, it always comes to "off" after restart. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: autologin login -- auto login doesn't work https://bugs.launchpad.net/bugs/1559670 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- 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 1318268] Re: df says / out of space but isn't
'df' is part of the coreutils package ** Package changed: ubuntu => coreutils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1318268 Title: df says / out of space but isn't Status in coreutils package in Ubuntu: New Bug description: when I do a df, I get:/$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 20G 19G 4.6M 100% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 1.8G 12K 1.8G 1% /dev tmpfs 356M 904K 355M 1% /run none 5.0M 0 5.0M 0% /run/lock none 1.8G 80K 1.8G 1% /run/shm none 100M 12K 100M 1% /run/user /dev/sda1 80G 12G 65G 16% /home but according to /$ sudo du -hc --max-depth=1 12G ./home 15M ./etc 8.0K ./media 1.4G ./var 9.1M ./bin 153M ./boot 12K ./dev 666M ./lib 4.0K ./lib64 0 ./mnt 0 ./opt du: cannot access ‘./proc/23086/task/23086/fd/4’: No such file or directory du: cannot access ‘./proc/23086/task/23086/fdinfo/4’: No such file or directory du: cannot access ‘./proc/23086/fd/4’: No such file or directory du: cannot access ‘./proc/23086/fdinfo/4’: No such file or directory 0 ./proc 352K ./root 1000K ./run 13M ./sbin 0 ./selinux 0 ./srv 0 ./sys 4.0K ./tmp 4.0G ./usr 0 ./cdrom 4.0K ./.config 18G . 18G total says that nothing in / could be taking that much space, so a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1318268/+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 1318268] [NEW] df says / out of space but isn't
You have been subscribed to a public bug: when I do a df, I get:/$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 20G 19G 4.6M 100% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 1.8G 12K 1.8G 1% /dev tmpfs 356M 904K 355M 1% /run none 5.0M 0 5.0M 0% /run/lock none 1.8G 80K 1.8G 1% /run/shm none 100M 12K 100M 1% /run/user /dev/sda1 80G 12G 65G 16% /home but according to /$ sudo du -hc --max-depth=1 12G ./home 15M ./etc 8.0K ./media 1.4G ./var 9.1M ./bin 153M ./boot 12K ./dev 666M ./lib 4.0K ./lib64 0 ./mnt 0 ./opt du: cannot access ‘./proc/23086/task/23086/fd/4’: No such file or directory du: cannot access ‘./proc/23086/task/23086/fdinfo/4’: No such file or directory du: cannot access ‘./proc/23086/fd/4’: No such file or directory du: cannot access ‘./proc/23086/fdinfo/4’: No such file or directory 0 ./proc 352K ./root 1000K ./run 13M ./sbin 0 ./selinux 0 ./srv 0 ./sys 4.0K ./tmp 4.0G ./usr 0 ./cdrom 4.0K ./.config 18G . 18G total says that nothing in / could be taking that much space, so a bug ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- df says / out of space but isn't https://bugs.launchpad.net/bugs/1318268 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. -- 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
Re: [Touch-packages] [Bug 1569876] Re: Mouse trails disappear only on window refresh
367.27, 364.19, 358.16, 361.45.11 On Sat, Jun 18, 2016 at 8:33 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Avishay, to clarify, which 4 different version of the nvidia drivers > specifically? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1569876 > > Title: > Mouse trails disappear only on window refresh > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > While using nouveau, when I move the mouse it leaves trails that > disappear when I move the mouse over them or when I refresh the > screen. The mouse cursor is distorted when moving it slowly which > makes it harder to click on small buttons (e.g., resizing a window) as > it's hard to tell where exactly the mouse is located. > > WORKAROUND: Use nivida 367.18. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 > Uname: Linux 4.4.0-18-generic x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.20.1-0ubuntu1 > Architecture: amd64 > BootLog: /dev/sda6: clean, 789425/48300032 files, 33613548/193179136 > blocks > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: KDE > Date: Wed Apr 13 15:29:36 2016 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: kubuntu > DkmsStatus: >bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed >bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed > ExtraDebuggingInterest: No > GraphicsCard: >Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) > (prog-if 00 [VGA controller]) > Subsystem: Lenovo Skylake Integrated Graphics [17aa:222e] >NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] > InstallationDate: Installed on 2016-04-01 (12 days ago) > InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 > (20160331) > MachineType: LENOVO 20EN0013US > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic > root=UUID=8e0207fc-0fb8-42e7-9dfc-a301c74d2146 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/08/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: N1EET47W (1.21 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20EN0013US > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40705 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrN1EET47W(1.21):bd03/08/2016:svnLENOVO:pn20EN0013US:pvrThinkPadP50:rvnLENOVO:rn20EN0013US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: > dmi.product.name: 20EN0013US > dmi.product.version: ThinkPad P50 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.67-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-1build2 > xserver.bootTime: Wed Apr 13 07:51:19 2016 > xserver.configfile: default > xserver.errors: >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nvidia" (module does not exist, 0) >Unknown chipset: NV117 > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.3-1ubuntu2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1569876/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1569876 Title: Mouse trails disappear only on window refresh Status in xorg package in Ubuntu: Incomplete Bug description: While using nouveau, when I move the mouse it leaves trails that disappear when I move the mouse over them or when I refresh the screen. The mouse cursor is distorted when moving it slowly which makes it harder to click on small buttons (e.g., resizing a window) as it's hard to tell where exactly the mouse is located. WORKAROUND: Use nivida 367.18. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package:
[Touch-packages] [Bug 1581642] Re: Colors of the main camera are always distorted
I reset device but main camera doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1581642 Title: Colors of the main camera are always distorted Status in camera-app package in Ubuntu: New Bug description: BQ Acquaris E5 HD Ubuntu Edition, OTA-10.1, Ubuntu 15.04-armhf (20160408-211605), VEGETA01A-S23A_BQ_L100EN_2012_160408 Camera app version 3.0.0.649 Main camera distorts colors, white color becomes pink, other colors become greener The second camera (5 MegaPixels) works well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1581642/+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 1594087] [NEW] Wouldn't find any wifi network after suspend/resume, restart fixed the issue
Public bug reported: I suspended (note: suspended, not hibernated) and resumed. I do this all the time and usually the computer immediately reconnects to my wifi router. This time it didn't. So I clicked on the network icon and there were no wifi networks in the list. I turned wifi off and on via Fn+F3, which usually forces a re-scan of available wifi networks. However, it would still list no network. I repeated several times with no luck. I checked my phone which was connected to the same wifi network and working. So I restarted the computer and this time it immediately connected, and also now the other available networks are listed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.3 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 19 11:13:43 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (981 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (152 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1594087 Title: Wouldn't find any wifi network after suspend/resume, restart fixed the issue Status in network-manager package in Ubuntu: New Bug description: I suspended (note: suspended, not hibernated) and resumed. I do this all the time and usually the computer immediately reconnects to my wifi router. This time it didn't. So I clicked on the network icon and there were no wifi networks in the list. I turned wifi off and on via Fn+F3, which usually forces a re-scan of available wifi networks. However, it would still list no network. I repeated several times with no luck. I checked my phone which was connected to the same wifi network and working. So I restarted the computer and this time it immediately connected, and also now the other available networks are listed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.3 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 19 11:13:43 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (981 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (152 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594087/+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 1590547] Re: LXC package for trusty no longer has configuration files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- 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/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: Confirmed Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1591246] Re: Wrong icon in notification of missed alarms and events
Regarding #3: I'm aware of bug #1362962. Here I'm talking about the small icon on the right side of the notification. This is using an old image. The latest release OTA-11 introduced an anonymous icon without a number (see screenshot on the right). This should be used by calendar- notifications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1591246 Title: Wrong icon in notification of missed alarms and events Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: The new implemented notifications (Released in OTA-11; see Bug #1440111) for missed alarms and events is using wrong icons. 1) If an alarm has been missed, the notification should use the icon of the clock app instead of the calendar app's. 2) A missed alarm should use the clock-icon on the right instead of an icon showing a number. 3) A missed event should use the new event-icon without a number. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591246/+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 1591246] Re: Wrong icon in notification of missed alarms and events
Regarding #4: Notifications of missed alarms (from clock app) seems to has been introduced since OTA-11. You can see it in the screenshot in the middle. It is comming from "Wecker" which is the German wording for "Alarm". It was created after 10 min (the default timeout time) of not responding to an alarm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1591246 Title: Wrong icon in notification of missed alarms and events Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: The new implemented notifications (Released in OTA-11; see Bug #1440111) for missed alarms and events is using wrong icons. 1) If an alarm has been missed, the notification should use the icon of the clock app instead of the calendar app's. 2) A missed alarm should use the clock-icon on the right instead of an icon showing a number. 3) A missed event should use the new event-icon without a number. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591246/+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 1574020] Re: Can't use networkmanager from lightdm
It affects me as well -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1594073] [NEW] 16.04 - initrd fails to decrypt and mount /usr directory when it's on it's own cryptsetup partition
Public bug reported: Running Ubuntu 16.04 LTS, upgraded from a 15.10 that did not show the issue. Initramd fails at setting up the encrypted /usr partition. At the (initramfs) prompt the following command is accepted and succeeds at decrypting the partition: cryptsetup --key-file /root/etc/keys/sda5_usr open --type luks /dev/sda5 sda5_usr After entering the above command and pressing + to exit the initramfs shell, system boot resumes and completes successfully. /etc (in the initramd) does not have the crypttab file, which is present in the decrypted and mounted root filesystem in /root/etc. The problem manifests itself regardless that in /etc/initramfs- tools/initramfs.conf MODULES=most or MODULES=dep is set before generating the initrd. Terminal output of the failed boot up to the initramfs prompt: Begin: Running /scripts/init-premount ... done Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Please unlock disk sda3_ubuntu_root: [ 120.025413] NET: Registered protocol family 38 cryptsetup: sda3_ubuntu_root set up successfully done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mapper/sda3_ubuntu_root] fsck.ext4 -a -C0 /dev/mapper/sda3_ubuntu_root Ubuntu_rootfs: clean, 44092/625056 files, 801590/2499604 blocks done. [ 126.996543] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) done. Begin: mounting /usr file system ... Begin: Waiting for /usr file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for /usr device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=6b18125b-32be-458c-a623-612a14e74eb3 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) _ ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cryptsetup initramfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1594073 Title: 16.04 - initrd fails to decrypt and mount /usr directory when it's on it's own cryptsetup partition Status in initramfs-tools package in Ubuntu: New Bug description: Running Ubuntu 16.04 LTS, upgraded from a 15.10 that did not show the issue. Initramd fails at setting up the encrypted /usr partition. At the (initramfs) prompt the following command is accepted and succeeds at decrypting the partition: cryptsetup --key-file /root/etc/keys/sda5_usr open --type luks /dev/sda5 sda5_usr After entering the above command and pressing + to exit the initramfs shell, system boot resumes and completes successfully. /etc (in the initramd) does not have the crypttab file, which is present in the decrypted and mounted root filesystem in /root/etc. The problem manifests itself regardless that in /etc/initramfs- tools/initramfs.conf MODULES=most or MODULES=dep is set before generating the initrd. Terminal output of the failed boot up to the initramfs prompt: Begin: Running /scripts/init-premount ... done Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Please unlock disk sda3_ubuntu_root: [ 120.025413] NET: Registered protocol family 38 cryptsetup: sda3_ubuntu_root set up successfully done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.27.1
[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)
Similar results for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1585084 Title: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1380702] Re: No keyboards shortcuts in QT apps
Dear Erico_pt, How is it possible that Lubuntu 16.04 is not affected but Ubuntu 16.04 is? Thankfully, ~Robert -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: In some apps built using QT4 & 5, menu shortcuts are greyed out and inoperant. Only alt and FKeys-based shortcuts work. Others, notably ctrl+c for copying, do not. This is quite serious ; mail me for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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
