[Touch-packages] [Bug 1291950] Re: slight delay when hitting enter to launch application from dash search
** Branch linked: lp:~3v1n0/unity/dash-prompt-app-activation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1291950 Title: slight delay when hitting enter to launch application from dash search Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Confirmed Bug description: When I hit the super key to bring up the dash and launch an application, if I partially type an application; such as ter for Terminal if I hit enter as Terminal is the first result there is a slight delay before the application is launched -- about 1 second. The delay is slightly less when I turn off searching from online sources. Sometimes, when searching, during the delay before the application launches right at the last moment I sometimes see search results pop up right before the dash closes. These are usually local searches, sometimes online search if enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291950/+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 1445265] Re: sdk header flickers when hide/show going in and out of fullscreen
also in our testing the flickering has nothing to do with an Image being displayed. The issue can be observed even with no image present, by toggling the window fullscreen and hiding/showing the header. The header clearly shows flicking and repainting issues in this scenario. Try the sample app here: lp:~artmello/+junk/fullscreen_issue_header -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1445265 Title: sdk header flickers when hide/show going in and out of fullscreen Status in Mir: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: With vivid-proposed on mako. We have a Image component with PreserveAspectRatio set as fillMode filling all the Page. When the application is going fullscreen / non- fullscreen on device the Image flickers during the process. Hiding the header too seems to make the result worse. This is the scenario for gallery-app during media viewer. On this branch [0] we have a sample app that seems to trigger the issue. Just tap the picture to go fullscreen / non-fullscreen. [0] lp:~artmello/+junk/fullscreen_issue To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445265/+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 1445265] Re: Image flickers when application going fullscreen on device
This is not related to the https://bugs.launchpad.net/tangxi/+bug/1417006 I don't believe as that bug is arale specific and this issue can be observed on mako and krillin. ** Summary changed: - Image flickers when application going fullscreen on device + sdk header flickers when hide/show going in and out of fullscreen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1445265 Title: sdk header flickers when hide/show going in and out of fullscreen Status in Mir: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: With vivid-proposed on mako. We have a Image component with PreserveAspectRatio set as fillMode filling all the Page. When the application is going fullscreen / non- fullscreen on device the Image flickers during the process. Hiding the header too seems to make the result worse. This is the scenario for gallery-app during media viewer. On this branch [0] we have a sample app that seems to trigger the issue. Just tap the picture to go fullscreen / non-fullscreen. [0] lp:~artmello/+junk/fullscreen_issue To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445265/+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 1445408] Re: USB-bluetooth-mouse not detected
** Changed in: bluez (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1445408 Title: USB-bluetooth-mouse not detected Status in bluez package in Ubuntu: Confirmed Bug description: Upgraded from Kubuntu 14.04 to 14.10 to 15.04 beta2 yesterday After finishing the final upgrade and rebooting my USB mouse is no longer working. Plugging in the USB dongle (it's a Logitech mouse with bluetooth connection, worked fine so far) I get the following in syslog: Apr 17 11:22:33 tp220 kernel: [13867.118079] usb 4-1.1: new full-speed USB device number 8 using ehci-pci Apr 17 11:22:34 tp220 kernel: [13867.213829] usb 4-1.1: New USB device found, idVendor=046d, idProduct=c52e Apr 17 11:22:34 tp220 kernel: [13867.213840] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 17 11:22:34 tp220 kernel: [13867.213845] usb 4-1.1: Product: USB Receiver Apr 17 11:22:34 tp220 kernel: [13867.213850] usb 4-1.1: Manufacturer: Logitech Apr 17 11:22:34 tp220 mtp-probe: checking bus 4, device 8: /sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1 Apr 17 11:22:34 tp220 mtp-probe: bus: 4, device: 8 was not an MTP device I remember having seen messages that the USB device list could not be accessed, but these are gone now. Please let me know if I can be of further help to track this down. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 17 11:18:08 2015 InstallationDate: Installed on 2014-09-09 (219 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4291S7Z ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic root=UUID=8c3ff90d-58e2-4696-9e3a-eddf92c84a41 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-17 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291S7Z dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 4291S7ZR9M0ZD3 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4291S7Z:pvrThinkPadX220:rvnLENOVO:rn4291S7Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291S7Z dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1445408/+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 1439436] Re: NM in vivid tries to take over my libvirt bridge, deconfigures its address
** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- 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/1439436 Title: NM in vivid tries to take over my libvirt bridge, deconfigures its address Status in network-manager package in Ubuntu: Confirmed Bug description: Over the past couple of months in vivid, from time to time I have noticed that my virbr0 interface, which is set up and managed by libvirt-bin, has been in an up state with no IP address configured. As I don't use VMs on my laptop very frequently, I don't know when the problem started and I don't know when exactly the problem is being triggered. But a search through logs shows the following: Mar 16 16:48:56 virgil systemd[1]: Stopping Network Manager... [...] Mar 16 16:48:56 virgil NetworkManager[32588]: info (virbr0): device state change: activated - deactivating (reason 'removed') [100 110 36] Mar 16 16:48:56 virgil NetworkManager[32588]: info (virbr0): device state change: deactivating - unmanaged (reason 'removed') [110 10 36] Mar 16 16:48:56 virgil NetworkManager[32588]: info (virbr0): deactivating device (reason 'removed') [36] Mar 16 16:48:56 virgil avahi-daemon[1336]: Withdrawing address record for 192.168.122.1 on virbr0. [...] Mar 16 16:48:56 virgil systemd[1]: Starting Network Manager Script Dispatcher Service... [...] Mar 16 16:48:56 virgil systemd[1]: Started Network Manager Script Dispatcher Service. [...] Mar 16 16:48:56 virgil nm-dispatcher: Dispatching action 'down' for virbr0 [...] Mar 16 16:48:56 virgil systemd[1]: Starting Network Manager... [...] Mar 16 16:48:56 virgil NetworkManager[6097]: info devices added (path: /sys/devices/virtual/net/virbr0, iface: virbr0) Mar 16 16:48:56 virgil NetworkManager[6097]: info device added (path: /sys/devices/virtual/net/virbr0, iface: virbr0): no ifupdown configuration found. [...] Mar 16 16:49:01 virgil systemd[1]: Started Network Manager. [...] Mar 16 16:49:02 virgil NetworkManager[6097]: info (virbr0): carrier is OFF Mar 16 16:49:02 virgil NetworkManager[6097]: info (virbr0): new Bridge device (driver: 'bridge' ifindex: 5) Mar 16 16:49:02 virgil NetworkManager[6097]: info (virbr0): exported as /org/freedesktop/NetworkManager/Devices/4 Mar 16 16:49:02 virgil NetworkManager[6097]: info (virbr0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Mar 16 16:49:02 virgil NetworkManager[6097]: warn (virbr0): device not up after timeout! Mar 16 16:49:02 virgil NetworkManager[6097]: info (virbr0): preparing device Mar 16 16:49:02 virgil NetworkManager[6097]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed The interface 'virbr0' also shows up in nm-applet's display, which was never the case before. This interface has always been managed by the libvirt-bin startup scripts (which causes problems of its own, since a 'service libvirt-bin restart' does not reinitialize the network and a 'service libvirt-bin stop' does not stop it). The bring-up of virbr0 appears to still be handled by libvirt-bin, not by NM; but somehow NM has a device configuration for it and is downing the interface on service stop - and not restoring it on service start. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 1 15:48:28 2015 InstallationDate: Installed on 2010-09-24 (1650 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.15.1 dev wlan2 proto static metric 1024 169.254.0.0/16 dev virbr0 scope link metric 1000 192.168.15.0/24 dev wlan2 proto kernel scope link src 192.168.15.71 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 207.224.24.209 via 192.168.15.1 dev wlan2 proto dhcp metric 10 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WWanEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-12-06 (116 days ago) 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/1439436/+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 1446269] Re: autoremove kernel management leaves one single kernel
** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: hundredpapercuts Importance: Undecided = High ** Changed in: apt (Ubuntu) Importance: Undecided = High -- 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/1446269 Title: autoremove kernel management leaves one single kernel Status in One Hundred Papercuts: Confirmed Status in apt package in Ubuntu: Confirmed Bug description: After a kernel upgrade, autoremove removes kernel -2 This is normal. BUT : If, a new update/full-upgrade is entered, apt suggests an autoremove for kernel -1 If one performs the autoremove, it leaves the system with a single kernel : :~$ dpkg -l | grep -Ei linux-headers|linux-image ii linux-headers-3.19.0-15 3.19.0-15.15 all Header files related to Linux kernel version 3.19.0 ii linux-headers-3.19.0-15-generic 3.19.0-15.15 amd64Linux kernel headers for version 3.19.0 on 64 bit x86 SMP ii linux-headers-generic 3.19.0.15.14 amd64Generic Linux kernel headers rc linux-image-3.19.0-13-generic 3.19.0-13.13 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-3.19.0-14-generic 3.19.0-14.14 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP ii linux-image-3.19.0-15-generic 3.19.0-15.15 amd64Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-extra-3.19.0-13-generic 3.19.0-13.13 amd64Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP rc linux-image-extra-3.19.0-14-generic 3.19.0-14.14 amd64Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP ii linux-image-extra-3.19.0-15-generic 3.19.0-15.15 amd64Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP ii linux-image-generic 3.19.0.15.14 amd64Generic Linux kernel image By the way, autoremove also leaves a bunch of rc files that need to be wiped with : dpkg --list |grep ^rc | cut -d -f 3 | xargs sudo dpkg --purge Having a single kernel is highly uneasy ! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 20 16:52:14 2015 InstallationDate: Installed on 2015-02-07 (71 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1446269/+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 1421009] Re: unity8 sometimes hangs on boot
** Description changed: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. + == Test Case == + + bzr branch lp:unity8 + cd unity8 + while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done + + This reboots the device in a loop, and if this bug is not fixed by + whatever proposed solution, it will hang at 30 boots. + --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes /
[Touch-packages] [Bug 1442962] Re: Dialer app reports No network even though cellular is connected
It is possible that my second ril account ($HOME rsynced from krillin) was triggering this. I've now removed it and will report back if that changed anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports No network even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) Current: offline (1) Requested: available (2) online Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 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/1442962/+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 1437459] Re: location service appears not to start occasionally
The browser does not start the location service at all. The Here apps timeout period is just too short, Google Maps default timeout value while waiting for a location update is significantly larger. With that, you are seeing a timing artifact here. ** Changed in: location-service (Ubuntu) Status: New = Invalid -- 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/1437459 Title: location service appears not to start occasionally Status in location-service package in Ubuntu: Invalid Bug description: ubuntu-touch/ubuntu-rtm/14.09-proposed #258 (krillin) Bootstrap your device, so you walk through the welcome wizard. Be sure to accept the additional check box for HERE services. Open system settings/location. Observe that the location settings do not include here. select the here option before moving on. Open Here app, and observe that it can't get your location, even when you press the 'move to location' circle bottom left. Open the browser, and go to maps.google.com. After accepting the location access prompt, observe that the browser obtains a location. Now return to the here app, and see that the location is now working. Expectation: It should not require the browser to start up the location service. Here should be able to do this itself. It is not clear to me if the inconsistency in the system-settings (with the wizard selection) is the cause of this bug, or a separate bug. Reproducibility: rare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1437459/+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 1445892] Re: There is no wifi after hybernate mode
** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- 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/1445892 Title: There is no wifi after hybernate mode Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: You close notebooke, then you open it- and there is no wifi. You have to restart network-manager for obtaining wi-fi again ! If you choose upstart-boot option there is no problem with wifi after hybernation. Bug occures unly with systemd-boot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 13:09:18 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (547 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1429438056 Вс. 19 апр. 2015 13:07:36 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/4 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/network-manager/+bug/1445892/+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 1446906] Re: lxc container with postfix, permission denied on mailq
*** This bug is a duplicate of bug 1390223 *** https://bugs.launchpad.net/bugs/1390223 ** Changed in: lxc (Ubuntu) Status: Incomplete = Confirmed ** This bug has been marked a duplicate of bug 1390223 Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel -- 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/1446906 Title: lxc container with postfix, permission denied on mailq Status in lxc package in Ubuntu: Confirmed Bug description: Hello, on three Vivid host, all of them up-to-date, I have the problem described here: https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 That bug report shows the problem was fixed, but it is not (at least on current Vivid) ii linux-image-generic 3.19.0.15.14 amd64 Generic Linux kernel image ii lxc 1.1.2-0ubuntu3 amd64 Linux Containers userspace tools ii apparmor2.9.1-0ubuntu9 amd64 User-space parser utility for AppArmor Reproducible with: $ sudo lxc-create -n test -t ubuntu $ sudo lxc-start -n test (inside container) $ sudo apt-get install postfix $ mailq postqueue: warning: close: Permission denied dmesg shows: [82140.386109] audit: type=1400 audit(1429661150.086:17067): apparmor=DENIED operation=file_perm profile=lxc-container-default name=public/showq pid=27742 comm=postqueue requested_mask=r denied_mask=r fsuid=1000 ouid=0 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoolook1913 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6 InstallationDate: Installed on 2015-02-27 (53 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: LENOVO 20150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago) UserGroups: adm docker libvirtd lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN95WW(V9.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN95WW(V9.00):bd12/19/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: 20150 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+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 1395861] Re: /sbin/upstart:io.c:1289: Not reached assertion failed in nih_io_shutdown_check
** Changed in: upstart (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1395861 Title: /sbin/upstart:io.c:1289: Not reached assertion failed in nih_io_shutdown_check Status in upstart package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding upstart. This problem was most recently seen with version 1.13.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fa67d280cf74b12a8d764417e2e216a242edb821 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1395861/+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 1441849] Re: Update force_release for Dell Latitudes
Hello Pali, or anyone else affected,
Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1441849
Title:
Update force_release for Dell Latitudes
Status in systemd package in Ubuntu:
Fix Committed
Status in udev package in Ubuntu:
Invalid
Status in udev source package in Precise:
Triaged
Status in systemd source package in Trusty:
Triaged
Status in systemd source package in Vivid:
Fix Committed
Bug description:
Wireless HW switch on Dell Latitude notebooks generate key press event
via AT Translated Set 2 keyboard, but does *not* generate release key
event. This means that operating systems and applications see key
still pressed.
Scan code of that problematic key is 136 (0x88).
Fixing this problem can be done via force_release option of atkbd
kernel driver (by adding 136 scan code to list)
Kernel developers told me that now only userspace (udev package)
maintains list of those problematic scan codes and so udev needs to be
extended/patched to add new values to atkbd kernel driver at runtime.
See: https://lkml.org/lkml/2015/4/5/157
Currenly there is file /lib/udev/keymaps/force-release/dell-touchpad
which contains some force_release scan code for all dell latitude
notebooks handled by file /lib/udev/rules.d/95-keyboard-force-
release.rules by rule:
ENV{DMI_VENDOR}==Dell Inc.,
ATTR{[dmi/id]product_name}==*Latitude*|*Precision*, RUN+=keyboard-
force-release.sh $devpath dell-touchpad
Can you extend either /lib/udev/keymaps/force-release/dell-touchpad or
/lib/udev/rules.d/95-keyboard-force-release.rules to include also scan
code 136 (0x88)? Because without is there are problems with HW
wireless switch!
This problem was tested on Ubuntu 12.04.5 LTS Precise release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441849/+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 1447243] Re: systemd crashes with Assertion 'current[*l + 1] == quotechars[0]' failed at ../src/shared/util.c:583 with invalid line break escapes
Hello Martin, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Vivid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447243 Title: systemd crashes with Assertion 'current[*l + 1] == quotechars[0]' failed at ../src/shared/util.c:583 with invalid line break escapes Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Bug description: Reproducer: - Boot current vivid amd64 VM - sudo add-apt-repository ppa:maas-maintainers/experimental - sudo apt update - sudo apt install isc-dhcp-server - sudo apt install maas-dhcp SRU TEST CASE (do this in a VM!) - Create a /lib/systemd/system/broken.service with the contents as in comment 7. Make sure that there is a trailing space after the true \ (Launchpad filtered that out in the comment!). - sudo systemctl status broken.service - This crashes pid 1 in vivid final, and should just complain a broken .service file with the fix. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 22 17:04:42 2015 ExecutablePath: /lib/systemd/systemd ExecutableTimestamp: 1429391580 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /sbin/init ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=6a708076-c5ee-4e4f-998a-4aa5ed4c3850 ro console=ttyS0 Signal: 6 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Activation of org.freedesktop.systemd1 timed out UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447243/+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 1426588] Re: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x00007fa04bf00910 ***
Hello Anders, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1426588 Title: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** Status in systemd: Won't Fix Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Bug description: root@file-control:~# systemctl disable vmware-USBArbitrator Synchronizing state for vmware-USBArbitrator.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d vmware-USBArbitrator defaults insserv: Service localfs has to be enabled to start service vmware-USBArbitrator insserv: exiting now! update-rc.d: error: insserv rejected the script header *** Error in `systemctl': double free or corruption (fasttop): 0x7f4ad5bff910 *** Aborted (core dumped) SRU TEST CASE = - Create a file /etc/init.d/broken with #!/bin/sh ### BEGIN INIT INFO # Provides: unknownservice # Required-Start: localfs # Required-Stop: localfs # Default-Start: 2 3 4 # Default-Stop: 0 6 # Short-Description: unknown service ### END INIT INFO true - Make it executable: sudo chmod 755 /etc/init.d/broken - Run sudo systemctl enable broken.service. This will show the double-free corruption. Notice that the insserv: Service localfs has to be enabled to start service unknownservice is an honest error message which must stay, as the init.d script is broken (it meant to say $local_fs presumably). ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu1 Uname: Linux 4.0.0-04rc1-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AssertionMessage: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** Date: Fri Feb 27 18:12:48 2015 ExecutablePath: /bin/systemctl InstallationDate: Installed on 2014-08-22 (189 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140730) MachineType: LENOVO 20349 ProcCmdline: systemctl disable vmware-USBArbitrator ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc1-generic root=/dev/mapper/fcntl-ubuntu ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fa049a247a0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=optimized out, str=0x7fa049a24968 double free or corruption (fasttop), action=1) at malloc.c:4996 _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 ?? () ?? () Title: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sbuild dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1426588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1447502] Re: GPS/location icon in notification top bar is out of sync with settings
** Tags added: bq ** Also affects: indicator-location (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: indicator-location (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New = Opinion ** Changed in: unity8 (Ubuntu RTM) Status: New = Opinion -- 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/1447502 Title: GPS/location icon in notification top bar is out of sync with settings Status in indicator-location package in Ubuntu: New Status in unity8 package in Ubuntu: Opinion Status in indicator-location package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Opinion Bug description: On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf 20150410-232623), I've noticed the following: - even though I've disabled GPS and Location detection, the crosshair icon is always on. - after playing around with *enabling* the GPS and waiting a bit, the icon *disappeared*. and then I found that the icon does stay away when disabling it again. perhaps GPS was on the whole time after all? Further info: - this icon had been on since I got the phone (and restarted at least two times) - I've disabled GPS almost the first thing I did Cheers, Walter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1447502/+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 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)
changelogs.ubuntu.com was fixed in the following bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1376088 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed = Fix Released ** Tags added: rls-w-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1260855 Title: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity) Status in apport package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Bug description: When installing on an IPv6 only network, the installer incorrectly reports that no Internet connectivity is available. Steps to reproduce: - Download desktop ISO. I used http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso current at Fri Dec 13 15:00 EST - Boot ISO on a computer where only IPv6 connectivity is available - Choose Install Xubuntu - Choose language Results: - At Preparing to install Xubuntu screen it states For best results, please ensure that this computer: ✓ has at least 5.5GB available drive space ✕ is connected to the Internet Expected results: - A checkmark next to is connected to the internet The install is able to complete from the ISO. Once the installed machine is booted, updates are able to be applied indicating Internet connectivity is indeed available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1260855/+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 1446846] Re: Three consistent autopilot test failures
I think I realized why the lifecycle test fails - the fake app in fixture is suspended as soon as it's launched (because screen is locked if you have a passcode/password, as we do on a phone provisioned with the CI script), and the following dbus introspection timeouts are from the app, not from unity8. -- 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/1446846 Title: Three consistent autopilot test failures Status in unity8 package in Ubuntu: Triaged Bug description: We seem to have stabilized on three tests failing repeatedly: unity8.indicators.tests.test_action_latency.TestClientRevertsToServerValue.test_slider_reverts_on_late_response(Native Device) unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_open unity8.indicators.tests.test_action_latency.TestBuffering.test_slider_buffers_activations(Native Device) Example run: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid- mako/2076/#showFailuresLink The two latency ones are relatively new tests, the lifecycle one seems to be a new consistent failure. What's even more important is that they're reliably reproducible locally using the steps below: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150409.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 21 22:18:54 2015 SourcePackage: unity8 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1446846/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
** Changed in: ntp (Ubuntu) Milestone: ubuntu-15.02 = None ** Changed in: ubuntu-meta (Ubuntu) Milestone: ubuntu-15.02 = None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+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 1447142] Re: systemd: ntpdate is started too soon (before the network)
** Changed in: ntp (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1447142 Title: systemd: ntpdate is started too soon (before the network) Status in ntp package in Ubuntu: Confirmed Bug description: Here is what I see in journalctl: ntpdate cannot do DNS resolution because NetworkManager has not finished configuring the network interface. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: info init! Apr 21 22:01:13 xeelee NetworkManager[1493]: info update_system_hostname Apr 21 22:01:13 xeelee NetworkManager[1493]: info interface-parser: parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]: info interface-parser: finished parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]: info management mode: unmanaged Apr 21 22:01:13 xeelee NetworkManager[1493]: info devices added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: info device added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: info devices added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, Apr 21 22:01:13 xeelee NetworkManager[1493]: info device added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, i Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: info devices added (path: /sys/devices/virtual/net/lo, iface: lo) Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], no ATA CHECK POWER STATUS support, ignoring -n Directive Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: info device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configur Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], is SMART capable. Adding to monitor list. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: info end _init. Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], state read from /var/lib/smartmontools/smartd.WDC_WD40EZRX_00SPE Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the Ne Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], opened Apr 21 22:01:13 xeelee ntpdate[1563]: no servers can be used, exiting Apr 21 22:01:13 xeelee NetworkManager[1493]: info Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use t Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], WDC WD40EZRX-00SPEB0, S/N:WD-WCC4E0267943, WWN:5-0014ee-25e7069b Apr 21 22:01:13 xeelee NetworkManager[1493]: info SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono Apr 21 22:01:13 xeelee NetworkManager[1493]: info SCPlugin-Ofono: init! Apr 21 22:01:13 xeelee NetworkManager[1493]: info SCPlugin-Ofono: end _init. Apr 21 22:01:13 xeelee NetworkManager[1493]: info Loaded plugin ofono: (C) 2013 Canonical Ltd. To report bugs please use the Netwo Apr 21 22:01:13 xeelee NetworkManager[1493]: info (25444896) ... get_connections. Apr 21 22:01:13 xeelee NetworkManager[1493]: info (25444896) ... get_connections (managed=false): return empty list. Apr 21 22:01:13 xeelee NetworkManager[1493]: info SCPlugin-Ofono: (25249376) ... get_connections. Apr 21 22:01:13 xeelee NetworkManager[1493]: info SCPlugin-Ofono: (25249376) connections count: 0 Apr 21 22:01:13 xeelee NetworkManager[1493]: info get unmanaged devices count: 0 Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], found in smartd database: Western Digital Caviar Green (AF, SATA Apr 21 22:01:13 xeelee NetworkManager[1493]: info monitoring kernel firmware directory '/lib/firmware'. Apr 21 22:01:13 xeelee NetworkManager[1493]: info monitoring ifupdown state file '/run/network/ifstate'. Apr 21 22:01:13 xeelee NetworkManager[1493]: info rfkill1: found WiFi radio killswitch (at /sys/devices/pci:00/:00:1c.2/000 Apr 21 22:01:13 xeelee systemd[1]: Stopped LSB: Start NTP daemon. Apr 21 22:01:13 xeelee systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks. Apr 21 22:01:13 xeelee systemd[1]: Started Accounts Service. Apr 21 22:01:13 xeelee systemd[1]: Mounted Arbitrary Executable File Formats
[Touch-packages] [Bug 1447101] Re: /usr/bin/account-console:TypeError:/usr/bin/account-console@270:__init__:__new__
** Changed in: account-plugins (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1447101 Title: /usr/bin/account-console:TypeError:/usr/bin/account- console@270:__init__:__new__ Status in Online Accounts: Account plugins: Confirmed Status in account-plugins package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding account-plugins. This problem was most recently seen with version 0.12+15.04.20150415.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/c7776aa06efdc5783feb07d963934b7cefbfbf45 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1447101/+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 1416793] Re: ifquery segfaults if /run/network/ifstate file is not found
** Changed in: ifupdown (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1416793 Title: ifquery segfaults if /run/network/ifstate file is not found Status in ifupdown package in Ubuntu: Confirmed Bug description: This makes the ifup@.service systemd unit file sad. version 0.7.48.1ubuntu6 [amd64] command: ifquery --state eth0 after a mkdir /run/network/ and a touch /run/network/ifstate the command above runs, but produces no output. Thanks for looking into this! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1416793/+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 1431582] Re: there is no wi-fi after hybernate mode
*** This bug is a duplicate of bug 1270257 *** https://bugs.launchpad.net/bugs/1270257 ** This bug has been marked a duplicate of bug 1270257 NetworkManager failed to function after suspend and resume -- 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/1431582 Title: there is no wi-fi after hybernate mode Status in network-manager package in Ubuntu: Confirmed Bug description: During last three days: after hybernate mode there is no wi-fi. I have to turn off Network-manager and turn it on again- only after that wi-fi works again !!! If you choose upstart-boot option there is no problem with wifi after hybernayion ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 00:56:10 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (510 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1426197268 Пт. 13 марта 2015 00:54:28 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- 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/1431582/+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 1349649] Re: libimobiledevice: GnuTLS error: A TLS packet with unexpected length was received
user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ sudo idevicebackup2 backup --full ~/Downloads/hacktivate/backup/ Backup directory is /home/user/Downloads/hacktivate/backup/ GnuTLS error: A TLS packet with unexpected length was received. user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ idevice_id -l 206d70c03a1e50b8eb6b663dcf3eb755fd711489 user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ ideviceinfo GnuTLS error: A TLS packet with unexpected length was received. user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ idevicepair validate SUCCESS: Validated pairing with device 206d70c03a1e50b8eb6b663dcf3eb755fd711489 user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ idevice_id -l 206d70c03a1e50b8eb6b663dcf3eb755fd711489 user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ ideviceinfo GnuTLS error: A TLS packet with unexpected length was received. user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ apt-cache policy libimobiledevice4 libimobiledevice4: Installed: 1.1.5+git20140313.bafe6a9e-0ubuntu1 Candidate: 1.1.5+git20140313.bafe6a9e-0ubuntu1 Version table: *** 1.1.5+git20140313.bafe6a9e-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status user@PLUS:~/Downloads/hacktivate/idevicerestore-master$ ** Description changed: Trying to do anything useful with libimobiledevice4-based utilities fails with GnuTLS error: A TLS packet with unexpected length was received. pairing, unpairing seem to work. verify seems to work. Nothing useful though. The device can't be used in any application. Attempted with an iPod touch, and an iPod classic. :~$ idevicepair validate SUCCESS: Validated pairing with device 7d789461608b267c53edee815895ae9e9a9c164b :~$ idevice_id -l 7d789461608b267c53edee815895ae9e9a9c164b :~$ ideviceinfo GnuTLS error: A TLS packet with unexpected length was received. - :~$ idevicedate + :~$ idevicedate GnuTLS error: A TLS packet with unexpected length was received. :~$ idevicename GnuTLS error: A TLS packet with unexpected length was received. - :~$ idevicescreenshot + :~$ idevicescreenshot GnuTLS error: A TLS packet with unexpected length was received. :~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 :~$ apt-cache policy libimobiledevice4 libimobiledevice4: - Installed: 1.1.5+git20140313.bafe6a9e-0ubuntu1 - Candidate: 1.1.5+git20140313.bafe6a9e-0ubuntu1 - Version table: - *** 1.1.5+git20140313.bafe6a9e-0ubuntu1 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.1.5+git20140313.bafe6a9e-0ubuntu1 + Candidate: 1.1.5+git20140313.bafe6a9e-0ubuntu1 + Version table: + *** 1.1.5+git20140313.bafe6a9e-0ubuntu1 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1349649 Title: libimobiledevice: GnuTLS error: A TLS packet with unexpected length was received Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Trying to do anything useful with libimobiledevice4-based utilities fails with GnuTLS error: A TLS packet with unexpected length was received. pairing, unpairing seem to work. verify seems to work. Nothing useful though. The device can't be used in any application. Attempted with an iPod touch, and an iPod classic. :~$ idevicepair validate SUCCESS: Validated pairing with device 7d789461608b267c53edee815895ae9e9a9c164b :~$ idevice_id -l 7d789461608b267c53edee815895ae9e9a9c164b :~$ ideviceinfo GnuTLS error: A TLS packet with unexpected length was received. :~$ idevicedate GnuTLS error: A TLS packet with unexpected length was received. :~$ idevicename GnuTLS error: A TLS packet with unexpected length was received. :~$ idevicescreenshot GnuTLS error: A TLS packet with unexpected length was received. :~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 :~$ apt-cache policy libimobiledevice4 libimobiledevice4: Installed: 1.1.5+git20140313.bafe6a9e-0ubuntu1 Candidate: 1.1.5+git20140313.bafe6a9e-0ubuntu1 Version table: *** 1.1.5+git20140313.bafe6a9e-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1349649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1447606] Re: incoming call ringtone is not played repeatedly
** Changed in: telephony-service (Ubuntu) Status: Confirmed = In Progress ** Changed in: canonical-devices-system-image Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in telephony-service package in Ubuntu: In Progress Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1434272] Re: Icons are too small when title bars and menus are scaled by 1.75
** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1434272 Title: Icons are too small when title bars and menus are scaled by 1.75 Status in unity package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 14.10 on a Macbook Pro Retina 13. I tried setting the menu and title bar scaling to 1.75 but the icons did not scale up appropriately; they stayed at a factor of 1 AFAICT. Certain apps, eg Nautilus and the settings app, seemed to be using the icon size to determine layout, so the text appeared cramped and some was truncated. I increased the setting to 2 and then the icons did scale up (but not the pointer, see #1359211). However, now title bars, menus and other text-based widgets are larger than ideal. I can reduce the font sizes with unity-tweak-tool but it doesn't seem to affect the title bar size etc. I presume the lack of icon scaling is because GTK only supports integer scaling settings and Unity is rounding down the setting for it. Please could it be changed to round up for fractions over 0.5. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Mar 19 20:51:27 2015 InstallationDate: Installed on 2015-03-19 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1434272/+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 1413595] Re: Cannot answer/disconnect calls with earphones button
** Changed in: telephony-service (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1413595 Title: Cannot answer/disconnect calls with earphones button Status in telephony-service package in Ubuntu: Confirmed Bug description: 0. Make sure you have wired headphones connected. 1. Create an incoming call 2. press the headphones button to answer it What happens: Nothing. The issue was found during regression testing. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: telephony-service 0.1+15.04.20150113~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Jan 22 18:31:13 2015 InstallationDate: Installed on 2015-01-22 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150122-030204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1413595/+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 1421009] Re: unity8 sometimes hangs on boot
https://code.launchpad.net/~mardy/ubuntu-system-settings-online- accounts/lp1421009/+merge/257267 got added to the PPA now. It seems to move the problem so that it never happens anymore during reboot - after reboot, the account is always still there. But it'd seem possible that a similar fix to a racy code would be needed somewhere that gets called when Install button gets pressed for the first time after a reboot. It now often removes the account when it's pressed, although sometimes you can do a full add U1 account, reboot, install app cycle without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+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 1447282] Re: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
Thanks Jason. Just to make sure my suspicion is correct, can you please give me the output of systemctl --all|grep swap and give me all files that turn up in find /run/systemd/generator* | grep swap? I figure the Apr 22 11:34:38 jason-Kudu-Professional kernel: Adding 4194300k swap on /dev/sda3. Priority:-1 extents:1 across:4194300k SSFS comes from systemd-gpt-generator that picks up the raw/bogus /dev/sda3 partition, and as it's slightly faster it's causing this: Apr 22 11:38:31 username-Kudu-Professional systemd-cryptsetup[645]: Loading of cryptographic parameters failed: Invalid argument which makes cryptsetup fail. FTR, GPT will be used (by default) if you install on an EFI system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) Status in systemd package in Ubuntu: New Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+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 1442962] Re: Dialer app reports No network even though cellular is connected
** Changed in: telepathy-ofono (Ubuntu) Importance: Undecided = Critical ** Changed in: dialer-app (Ubuntu) Importance: Undecided = Critical ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) = Tiago Salem Herrmann (tiagosh) ** Changed in: telepathy-ofono (Ubuntu) Assignee: (unassigned) = Tiago Salem Herrmann (tiagosh) ** Changed in: canonical-devices-system-image Importance: Undecided = Critical ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Bill Filler (bfiller) ** Changed in: canonical-devices-system-image Milestone: None = ww17-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports No network even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) Current: offline (1) Requested: available (2) online Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 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/1442962/+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 1445580] Re: Impossible to end a call after switching to airplane mode
The Phone app does need to handle cases that software can't, like ejecting the SIM or going out of range. But entering Flight Mode is something you do interactively, so likely mistakes should be handled interactively. And this exact case has been in the Flight Mode section of the Networking spec since April 2014. https://wiki.ubuntu.com/Networking?action=diffrev2=165rev1=164 (If the design is inappropriate, then let's change it, but that doesn't seem to be the issue here. If there's anything I can do to make it easier or more fun for engineers to ask I wonder what the spec says about this?, please let me know.) ** Description changed: As I described here https://lists.launchpad.net/ubuntu-phone/msg12177.html I accidentally switched the phone to the airplane mode while having an active incoming call. As a result it is impossible to end a call - the red button does not end the call. The bug is easy to reproduce: 1. Make a call to your Ubuntu phone and answer it. 2. Switch on 'airplane mode' 3. As a result you get unusable phone. Of course switching gsm off while having an active call is not a typical use of the phone, but still the phone should react to this situation differently. Another thing is that I somehow switched gsm off while holding my phone to my ear (which may suggest some issue with the top panel) - but I don't know how to reproduce this, hence currently I treat this as an very unfortunate accident. Workaround for ending the call: make another incoming call to your phone. BQ (r21) + + https://wiki.ubuntu.com/Networking#flight-mode: When you turn on + Flight Mode: 1. If a phone or Voip call is in progress, an alert should + appear, “Turning on Flight Mode will end your call.”, with buttons + “Cancel” and “End Call”. The alert should close automatically if the + call finishes by itself. ** Changed in: indicator-network (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1445580 Title: Impossible to end a call after switching to airplane mode Status in the base for Ubuntu mobile products: In Progress Status in Telephony Service: New Status in dialer-app package in Ubuntu: Incomplete Status in indicator-network package in Ubuntu: Triaged Status in ofono package in Ubuntu: Fix Committed Bug description: As I described here https://lists.launchpad.net/ubuntu-phone/msg12177.html I accidentally switched the phone to the airplane mode while having an active incoming call. As a result it is impossible to end a call - the red button does not end the call. The bug is easy to reproduce: 1. Make a call to your Ubuntu phone and answer it. 2. Switch on 'airplane mode' 3. As a result you get unusable phone. Of course switching gsm off while having an active call is not a typical use of the phone, but still the phone should react to this situation differently. Another thing is that I somehow switched gsm off while holding my phone to my ear (which may suggest some issue with the top panel) - but I don't know how to reproduce this, hence currently I treat this as an very unfortunate accident. Workaround for ending the call: make another incoming call to your phone. BQ (r21) https://wiki.ubuntu.com/Networking#flight-mode: When you turn on Flight Mode: 1. If a phone or Voip call is in progress, an alert should appear, “Turning on Flight Mode will end your call.”, with buttons “Cancel” and “End Call”. The alert should close automatically if the call finishes by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+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 1447515] Re: provide /sbin/resize2fs
** Changed in: initramfs-tools-ubuntu-touch (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1447515 Title: provide /sbin/resize2fs Status in initramfs-tools-ubuntu-touch package in Ubuntu: In Progress Bug description: In order to be able to resize the userdata partition on first boot, we need the resize2fs tool in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1447515/+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 1421009] Re: unity8 sometimes hangs on boot
** Branch linked: lp:~mardy/ubuntu-system-settings-online- accounts/lp1421009 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting
** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium ** Changed in: hundredpapercuts Importance: Undecided = Medium -- 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/1442044 Title: Ordering processes: networkmanager should wait for kernel'module been activated first before starting Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (lo): link connected NetworkManager[724]: info (lo): carrier is ON NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: info (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (eth0): carrier is OFF NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: info (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: info (eth0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] NetworkManager[724]: info (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: info (eth1): carrier is OFF NetworkManager[724]: info (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: info (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: info (eth1): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: info (eth1): preparing device NetworkManager[724]: info urfkill disappeared from the bus that mobo have eth0 eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. network-manager 0.9.10.0-4ubuntu13 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1447146] Re: NetworkManager assertion failure: dir != NULL
** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- 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/1447146 Title: NetworkManager assertion failure: dir != NULL Status in network-manager package in Ubuntu: Confirmed Bug description: Here is an error seen in journalctl: Apr 21 22:01:13 xeelee NetworkManager[1493]: (NetworkManager:1493): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 22 14:24:07 2015 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 802-3-ethernet 1429705273 Wed 22 Apr 2015 02:21:13 PM CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- 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/1447146/+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 1440852] Re: Need a way to tell our userspace if GPS is currently active or not
The respective functionality is available on the bus. The respective properties are: com.ubuntu.location.Service.IsOnline : bool com.ubuntu.location.Service.DoesSatelliteBasedPositioning : bool Both properties are available via the platform-api, too. ** Changed in: location-service (Ubuntu) Status: New = Invalid -- 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/1440852 Title: Need a way to tell our userspace if GPS is currently active or not Status in location-service package in Ubuntu: Invalid Bug description: As a result of bug 1434379, QA wanted to check if there could be a way (cmdline/API) to know, from the location-service itself, when the GPS hardware is active or not. Basically the only reliable way to know that is by checking /system/bin/logcat, and retrieving the GPS HAL logs. Having such call could allow us to create regression tests that could check for bug 1434379 (and similar ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1440852/+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 1434521] Re: account-polld does not recognize when messages are cleared
Ok, I just gave r433 a go and it didn't work. Therefore, we now know that the commit which broke this was r433. ** Changed in: indicator-messages (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1434521 Title: account-polld does not recognize when messages are cleared Status in account-polld package in Ubuntu: Invalid Status in indicator-messages package in Ubuntu: In Progress Status in ubuntu-push package in Ubuntu: Invalid Bug description: After each reboot, account-polld stops showing incoming emails after displaying 3 notifications. The reason for that is that account-polld does not recognize when messages are cleared from the messaging indicator and therefore does not show any further notifications. How to reproduce: 1) Reboot your phone. 2) Send yourself 3 test emails 3) Wait 5 minutes until account-polld has been run 4) You'll see three notifications stating that there are new emails 5) Tap on the clear all entry in the notifications indicator 6) Mark your last three emails as read (this is optional) 7) Send yourself another test email 8) Wait 5 minutes again until account-polld has been run 9) No notification about the new unread email is shown Why does it happen: When clicking the clear all button, the internal cache of previous messages isn't cleared. Therefore, account-polld still thinks that there are 3 notifications and does not display any further messages. Log: http://paste.ubuntu.com/10664183/ Old one: http://paste.ubuntu.com/10634045/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1434521/+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 1447715] [NEW] dhclient -6: Can't bind to dhcp address: Cannot assign requested address
Public bug reported: After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network- manager.dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-c0a3dfde- 5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager /dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network- manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6 -c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in isc-dhcp package in Ubuntu: New Bug description: After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1447715/+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 1447717] [NEW] Xorg freeze, black screen suspend / resume
Public bug reported: When closing/opening laptop lid, screen is black, does not resume. This happens using the open source video driver in Xubuntu Vivid 15.04 daily (04/23/15). This does not happen using the fglrx (proprietary) driver. Lenovo model 20B2001CUS (e545) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 12:01:50 2015 InstallationDate: Installed on 2015-04-23 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze vivid -- 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/1447717 Title: Xorg freeze, black screen suspend / resume Status in xorg package in Ubuntu: New Bug description: When closing/opening laptop lid, screen is black, does not resume. This happens using the open source video driver in Xubuntu Vivid 15.04 daily (04/23/15). This does not happen using the fglrx (proprietary) driver. Lenovo model 20B2001CUS (e545) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 12:01:50 2015 InstallationDate: Installed on 2015-04-23 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447717/+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 1351177] Re: Suggestions improvements
here is screenshot before installing the silo ** Attachment added: before.png https://bugs.launchpad.net/webbrowser-app/+bug/1351177/+attachment/4382199/+files/before.png -- 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/1351177 Title: Suggestions improvements Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: Per design specification, the suggestions that show up when the user types in the address bar need to be updated in the following ways: - take up the whole screen (as opposed to being a popover) - include additional sources: bookmarks (auto-suggest is being tracked separately by bug #1351151) - display symbolic icons to tell apart different types of entries (search, history, bookmarks) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+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 1447719] [NEW] system deadlock after hiberbate wake up
Public bug reported: above behavior is 100% reproducible since new installation of Ubuntu 14.04 (no upgrade from 12.04). After hibernate wake up the screen displayed looks like a distorted chess game with black and white areas no coloured areas visible. Trying to open a console does not work! Mouse and keyboard actions show no response. Only the power off switch is still working! In 12.04 I had no such problems with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 23 18:50:52 2015 InstallationDate: Installed on 2015-03-26 (28 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1447719 Title: system deadlock after hiberbate wake up Status in lightdm package in Ubuntu: New Bug description: above behavior is 100% reproducible since new installation of Ubuntu 14.04 (no upgrade from 12.04). After hibernate wake up the screen displayed looks like a distorted chess game with black and white areas no coloured areas visible. Trying to open a console does not work! Mouse and keyboard actions show no response. Only the power off switch is still working! In 12.04 I had no such problems with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 23 18:50:52 2015 InstallationDate: Installed on 2015-03-26 (28 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1447719/+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 1351177] Re: Suggestions improvements
after. No difference. ** Attachment added: after.png https://bugs.launchpad.net/webbrowser-app/+bug/1351177/+attachment/4382200/+files/after.png -- 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/1351177 Title: Suggestions improvements Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: Per design specification, the suggestions that show up when the user types in the address bar need to be updated in the following ways: - take up the whole screen (as opposed to being a popover) - include additional sources: bookmarks (auto-suggest is being tracked separately by bug #1351151) - display symbolic icons to tell apart different types of entries (search, history, bookmarks) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+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 1351177] Re: Suggestions improvements
The popup does not take up the whole screen width as its meant to. -- 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/1351177 Title: Suggestions improvements Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: Per design specification, the suggestions that show up when the user types in the address bar need to be updated in the following ways: - take up the whole screen (as opposed to being a popover) - include additional sources: bookmarks (auto-suggest is being tracked separately by bug #1351151) - display symbolic icons to tell apart different types of entries (search, history, bookmarks) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
@leandromartinez98 your solution works also to IntelliJ, Webstorm and Emacs after the restart, thank you. Will this bug be fixed natively to next versions of Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Won't Fix Status in ibus package in Ubuntu: In Progress Status in language-selector package in Ubuntu: Fix Released Status in libx11 package in Ubuntu: In Progress Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1437051] Re: Keyboard not detected ThinkPad Helix
Why is this bug being closed -- I've seen a few reports of it in various other forums, and it effects me. Happy to help troubleshoot. ** Changed in: xorg (Ubuntu) Status: Invalid = Confirmed -- 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/1437051 Title: Keyboard not detected ThinkPad Helix Status in xorg package in Ubuntu: Confirmed Bug description: Brand new ThinkPad Helix with docking keyboard (part number 20CGCTO1WW) Keyboard works fine in Windows and in Grub, but is not detected whatsoever in Ubuntu. (I've also tried Ubuntu MATE and Mint with the same result.) I did find /dev/input/by-path/platform-i8042-serio-0-event-kbd which looks like it might be the correct device. It is a link to /dev/input/event3. Running an hd and an evtest on that device yields no results, while it does give results for a USB keyboard. xinput -list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8595) id=10 [slave pointer (2)] ⎜ ↳ ATML1000:00 03EB:8A29 id=12 [slave pointer (2)] ⎜ ↳ WCOM0009:00 056A:0114 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Video Bus id=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Rear Camera id=9[slave keyboard (3)] ↳ Integrated Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=17 [slave keyboard (3)] xinput -list-props AT Translated Set 2 keyboard Device 'AT Translated Set 2 keyboard': Device Enabled (136): 1 Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Product ID (253):1, 1 Device Node (254): /dev/input/event3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Mar 26 17:11:11 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:222b] InstallationDate: Installed on 2015-03-24 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: LENOVO 20CGCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=aaad9f95-89f8-4a89-bc15-c5c867da639c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET70W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET70W(1.70):bd12/26/2014:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CGCTO1WW dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1351177] Re: Suggestions improvements
While testing the silo I am having hard time understanding what this bug really fixes. I have looked at the design doc as well but was not able to find what I was looking for. -- 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/1351177 Title: Suggestions improvements Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: Per design specification, the suggestions that show up when the user types in the address bar need to be updated in the following ways: - take up the whole screen (as opposed to being a popover) - include additional sources: bookmarks (auto-suggest is being tracked separately by bug #1351151) - display symbolic icons to tell apart different types of entries (search, history, bookmarks) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+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 1447748] Re: SIM unlock screen unusable when launched from indicator
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447748 Title: SIM unlock screen unusable when launched from indicator Status in indicator-network package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+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 1447756] [NEW] segfault in log.c code causes phone reboot loops
Public bug reported: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in upstart package in Ubuntu: New Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1447756/+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 1447606] Re: incoming call ringtone is not played repeatedly
** Also affects: media-hub Importance: Undecided Status: New ** Changed in: media-hub Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: New Status in telephony-service package in Ubuntu: In Progress Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work
For anyone, who cannot/doesn't want to wait month or two more, I did a quick backport of the 4.0 driver for 3.16 kernel (https://github.com/andree182/psmouse-dkms-alpsv7 , just call install.sh). Both trackpoint and touchpad appears to work fine. Hopefully this will work out of box later even with the official kernel... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1447282] Re: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
Martin, Another interesting tidbit is that this pre-lightdm passphrase prompt isn't actually doing anything... you can enter a blank passphrase or the wrong passphrase, and it will still happily proceed to lightdm. Here's the output you asked for: $ systemctl --all | grep -i swap dev-mapper-cryptswap1.device loadedinactive dead start dev-mapper-cryptswap1.device systemd-cryptsetup@cryptswap1.service loadedactivating start start Cryptography Setup for cryptswap1 dev-disk-by\x2did-ata\x2dCrucial_CT120M500SSD3_14260C6F95F9\x2dpart3.swap loadedactive active /dev/disk/by-id/ata-Crucial_CT120M500SSD3_14260C6F95F9-part3 dev-disk-by\x2did-wwn\x2d0x10806682451855888394x\x2dpart3.swap loadedactive active /dev/disk/by-id/wwn-0x10806682451855888394x-part3 dev-disk-by\x2dpartlabel-primary.swap loadedactive active /dev/disk/by-partlabel/primary dev-disk-by\x2dpartuuid-54ce1181\x2d8e2b\x2d456d\x2db679\x2d6a22d25fd361.swap loadedactive active /dev/disk/by-partuuid/54ce1181-8e2b-456d-b679-6a22d25fd361 dev-disk-by\x2duuid-92a5e233\x2dc249\x2d42df\x2d8425\x2d3d6e8ac3af41.swap loadedactive active /dev/disk/by-uuid/92a5e233-c249-42df-8425-3d6e8ac3af41 dev-mapper-cryptswap1.swap loadedinactive dead start /dev/mapper/cryptswap1 dev-sda3.swap loadedactive active Swap Partition swap.target loadedinactive deadSwap $ find /run/systemd/generator* | grep -i swap /run/systemd/generator/dev-mapper-cryptswap1.device.d /run/systemd/generator/dev-mapper-cryptswap1.device.d/90-device-timeout.conf /run/systemd/generator/dev-mapper-cryptswap1.device.requires /run/systemd/generator/dev-mapper-cryptswap1.device.requires/systemd-cryptsetup@cryptswap1.service /run/systemd/generator/cryptsetup.target.requires/systemd-cryptsetup@cryptswap1.service /run/systemd/generator/dev-disk-by\x2duuid-92a5e233\x2dc249\x2d42df\x2d8425\x2d3d6e8ac3af41.device.wants/systemd-cryptsetup@cryptswap1.service /run/systemd/generator/systemd-cryptsetup@cryptswap1.service /run/systemd/generator/swap.target.requires /run/systemd/generator/swap.target.requires/dev-mapper-cryptswap1.swap /run/systemd/generator/dev-mapper-cryptswap1.swap /run/systemd/generator.late/swap.target.wants /run/systemd/generator.late/swap.target.wants/dev-sda3.swap /run/systemd/generator.late/dev-sda3.swap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) Status in systemd package in Ubuntu: New Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional
[Touch-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
On 2015-04-23 19:13, Felipe Micaroni Lalli wrote: Will this bug be fixed natively to next versions of Ubuntu? It's not clear to me what you mean. As regards Brazilian Portuguese, there is nothing left to do, as far as I can tell. There are three ways to enable the '+c = ç behavior in Ubuntu 15.04, assuming that you keep IBus (default) as the IM framework: 1. Select Brazilian Portuguese as the display language (via Language Support). 2. Select Brazilian Portuguese as the regional formats setting (via Language Support). 3. Set the LC_CTYPE variable manually, as explained in comment #115. I will probably propose that the same is set up for Portuguese (Portugal) when the development of 15.10 opens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Won't Fix Status in ibus package in Ubuntu: In Progress Status in language-selector package in Ubuntu: Fix Released Status in libx11 package in Ubuntu: In Progress Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1243642] Re: .Xmodmap not automatically loaded on start
I'm seeing the same behaviour after an upgrade from Precise to Trusty, and it is disheartening to see that the bug was reported during an upgrade between intermediate versions with very little traction. I've added logic to my shell rc script to run xmodmap when I log in, but this does not address the case where I resume, so I still need to manually run xmodmap somewhat regularly. -- 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/1243642 Title: .Xmodmap not automatically loaded on start Status in xorg package in Ubuntu: Confirmed Bug description: I'm using a ~/.Xmodmap file to define two keycode mappings. 13.10 doesn't seem to automatically load this file any more. 13.04 did. (same file, same laptop) manual execution of xmodmap ~/.Xmodmap works on 13.10! That means I'm e.g. able to use this key in a terminal or in geany. I discovered, that by switching the keyboard layouts using gnome- control-center region layouts the mappings of the xmodmap ~/.Xmodmap will be lost again. Then another manual execution of xmodmap ~/.Xmodmap has to be executed and it works again. Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control- center () later. Sorry, I can't figure out which packet this bug has to be asigned to. By using apport-bug xorg was choosen, but it could be xorg-server or gnome-control-center, also. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Wed Oct 23 12:05:11 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:013c] Subsystem: Acer Incorporated [ALI] Device [1025:013c] InstallationDate: Installed on 2013-10-18 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Acer Extensa 5630 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 23 11:15:16 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5459 vendor CMO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+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 1447748] [NEW] SIM unlock screen unusable when launched from indicator
Public bug reported: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-silo -- 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/1447748 Title: SIM unlock screen unusable when launched from indicator Status in unity8 package in Ubuntu: New Bug description: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447748/+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 1313370] Re: Support for installing Digital Certificates
Hi, is the priority list published sowewhere? BTW full support of SSL certificates import should include both possibility to install website/CA certificates and personal certificates. -- 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/1313370 Title: Support for installing Digital Certificates Status in Oxide Webview: New Status in Web Browser App: Triaged Status in webbrowser-app package in Ubuntu: Triaged Bug description: I am trying to enter a page, and to me it is necessary to have in the digital certificate installed browser. Where is the option to install the digital certificate. Without that the browser is unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1313370/+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 1442962] Re: Dialer app reports No network even though cellular is connected
I noticed my device was in the same bad state this morning. I flashed it yesterday and I had only one account, so I assume it is probably not related to your $HOME synced from another device. I wonder if this is only happening after a long deep sleep over night. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports No network even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) Current: offline (1) Requested: available (2) online Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 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/1442962/+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 1442962] Re: Dialer app reports No network even though cellular is connected
W dniu 23.04.2015 o 17:16, Tiago Salem Herrmann pisze: I noticed my device was in the same bad state this morning. I flashed it yesterday and I had only one account, so I assume it is probably not related to your $HOME synced from another device. I wonder if this is only happening after a long deep sleep over night. That's likely, it was always happening to me in the afternoon after I've not used the phone for a few hours. I don't get it in the morning since I'm usually charging overnight. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports No network even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) Current: offline (1) Requested: available (2) online Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 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/1442962/+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 1429460] Re: package initscripts 2.88dsf-53.2ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1429460 Title: package initscripts 2.88dsf-53.2ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in sysvinit package in Ubuntu: Confirmed Bug description: bad upgrade to 15.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: initscripts 2.88dsf-53.2ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Sat Mar 7 17:15:20 2015 DuplicateSignature: package:initscripts:2.88dsf-53.2ubuntu10:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-02-20 (15 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: sysvinit Title: package initscripts 2.88dsf-53.2ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-03-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1429460/+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 1447566] Re: Need to expose API to notify about user closing the app
StateSaver discards the saved states on SIGTERM. This has been agreed long ago when we stabilised the StateSaver requirements: - states are saved every time the app goes background (inactive) - SIGINT keeps the states saved - SIGTERM, quit() clears the state data, as well as when the app comes foreground So donate assume states being saved when SIGTERM comes. This was like this since 1.0, so we cannot break that. We can however expose an interface to apps so they can save whatever they want. Any other signals we should listen on? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447566 Title: Need to expose API to notify about user closing the app Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Apps currently have no way to clean up when a user closes them (swipes an app away in the right-edge switcher). It'd be useful to expose a signal that the app can subscribe to to handle SIGTERM that's sent to it by upstart. The app should not exit until the signal handler returns. Initially we'll rely on upstart to SIGKILL the app after a timeout, but later we'll need to implement a way for the app to suppress that if e.g. it needs to ask the user what to do with unsaved data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447566/+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 1447735] Re: PopupUtils.open may not work from non-root Component.onCompleted
My suspicion is that the root item, which the popup will use as its parent, is not yet completed when open() is called. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447735 Title: PopupUtils.open may not work from non-root Component.onCompleted Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If PopupUtils.open is used from a Component.onCompleted that is not the root of the hierarchy, it may not show. See: http://askubuntu.com/questions/282629/how-to-display-popup-dialog-after-app-start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447735/+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 1447735] [NEW] PopupUtils.open may not work from non-root Component.onCompleted
Public bug reported: If PopupUtils.open is used from a Component.onCompleted that is not the root of the hierarchy, it may not show. See: http://askubuntu.com/questions/282629/how-to-display-popup-dialog-after-app-start ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Summary changed: - PopupUtils.open may not work from non-root Component.onComplete + PopupUtils.open may not work from non-root Component.onCompleted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1447735 Title: PopupUtils.open may not work from non-root Component.onCompleted Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If PopupUtils.open is used from a Component.onCompleted that is not the root of the hierarchy, it may not show. See: http://askubuntu.com/questions/282629/how-to-display-popup-dialog-after-app-start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1447735/+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 1435324] Re: qtbase5-dev not installable on Ubuntu 14.04 LTS
sgon00 is right , weird but true -- 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/1435324 Title: qtbase5-dev not installable on Ubuntu 14.04 LTS Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: I discovered the problem when I tried to compile a Qt5 QML program firstly. I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only nodejs and owncloud, not affecting this problem here) and with all the -lts-utopic upgrade packages installed. With that system, I tried to install qtbase5-dev, and apt told me: [...] The following packages have unmet dependencies: qtbase5-dev : Depends: libgles2-mesa-dev or libgles2-dev but it is not installable unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. So this package seems to be not installable. This tried in synaptic, it tries to uninstall all -lts-utopic packages (inclusive all xserver*.deb) and install the old ones instead of them. So the problem somewhere lies within the new lts packages that seem not to be compatible with qtbase5-dev (and its dependency: libgles2 -mesa-dev - but I am not able to find out further. The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is NOT possible without a fix. The make process always complains about not finding gl libraries. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtbase5-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 14:01:20 2015 InstallationDate: Installed on 2015-02-25 (26 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435324/+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 1447606] Re: incoming call ringtone is not played repeatedly
The test program below can be used to verify the problem is solved: https://code.launchpad.net/~boiko/+junk/media_playback_loop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: New Status in media-hub package in Ubuntu: New Status in telephony-service package in Ubuntu: Invalid Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1360403] Re: MMS does not work with T-Mobile US
Yes please! Preventing me from using Ubuntu Phone on my Nexus 4. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1360403 Title: MMS does not work with T-Mobile US Status in lxc-android-config package in Ubuntu: Triaged Status in nuntium package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: My /var/lib/ofono/*/gprs file contains: [Settings] Powered=1 RoamingAllowed=0 [context1] Name=T-Mobile GPRS AccessPointName=fast.t-mobile.com Username= Password= Type=internet Protocol=ipv6 MessageProxy= MessageCenter=http://mms.msg.eng.t-mobile.com/mms/wapenc I guess bug #1331813 is getting in the way of IPv6 working, so I was told to try 'Protocol=ip', but it doesn't work either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1360403/+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 1447756] Re: segfault in log.c code causes phone reboot loops
I think I see a potential problem if 'initctl notify-disk-writeable' is called multiple times. The log_clear_unflushed() function walks the log_unflushed_files list, attempting to flush each of the logs and freeing them when done with nih_free(). But as far as I know, nih_free() will not cause the element to be removed from the log_unflushed_files list, so if this function is ever called a second time it looks to me that it will re-process the list, traversing freed memory with undefined results. We can't see anything in the official Ubuntu rootfs that would account for this function being called more than once. On the other hand, we also haven't seen this reproduced on any devices other than those installed in the factory, so it could be that an error has crept in there. We can try to produce a patch to upstart to fix this bug, to see if it fixes the segfault for those who are seeing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1366418] Re: Bluetooth BCM43142A0 doesn’t work
@Pilot6 I mean that this patch has been applied to official Ubuntu kernel. Sounds great; But is there the patch for www.kernel.org's non-compiled kernels or is there a way to avoid re-compiling at all? I am asking cause I have pre-compiled kernel 3.16.7 so I really want to fing some generic solution; Any ideas? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1366418 Title: Bluetooth BCM43142A0 doesn’t work Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not displayed in the menu bar, if I open the bluetooth UI and switch on, nothing happens and the result of “hcitool dev” is empty. I have tried to install the windows driver with ndiswrapper, and the bluetooth device seems to be detected as an usb bluetooth device but still not working. I then add the device to the bluetooth usb device and was able to activate bluetooth in the UI but it does not detect any other devices (I’ve tested with a smartphone). The driver I have installed can be found in asus page = http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/ Select Windows OS, then “bluetooth” section, take the Broadcom driver (should be the first one). If you extract this archive, you will find a file named “bcbtums- win8x64-brcm.inf” which I installed using the following command: ndiswrapper -i bcbtums-win8x64-brcm.inf Then, the result of “ndiswrapper -l” is: bcbtums-win8x64-brcm : driver installed device (04CA:2006) present in usb-devices, I find a device which was not present before installation (I might have activated btusb before on this paste): T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=2006 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM43142A0 S: SerialNumber=B8EE6593D989 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) then, “echo 04ca 2006 /sys/bus/usb/drivers/btusb/new_id”, and I can switch usb on, but no device will be detected and I’ve found this in the dmesg: [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout which looks pretty much like a “bluetooth not working” message which I don’t understand in details. I leave here my full dmesg: [0.253889] NetLabel: domain hash size = 128 [0.253890] NetLabel: protocols = UNLABELED CIPSOv4 [0.253901] NetLabel: unlabeled traffic allowed by default [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [0.255995] Switched to clocksource hpet [0.260468] AppArmor: AppArmor Filesystem Enabled [0.260488] pnp: PnP ACPI init [0.260500] ACPI: bus type PNP registered [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [0.260642] pnp 00:01: [dma 4] [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active) [0.260924] system 00:04: [io 0x0680-0x069f] has been reserved [0.260927] system 00:04: [io 0x] has been reserved [0.260928] system 00:04: [io 0x] has been reserved [0.260930] system 00:04: [io 0x] has been reserved [0.260932] system 00:04: [io 0x1c00-0x1cfe] has been reserved [0.260934] system 00:04: [io 0x1d00-0x1dfe] has been reserved [0.260935] system 00:04: [io 0x1e00-0x1efe] has been reserved [0.260937] system 00:04: [io 0x1f00-0x1ffe] has been reserved [0.260939] system 00:04: [io 0x1800-0x18fe] could not be reserved [0.260941] system 00:04: [io 0x164e-0x164f] has been reserved [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active) [0.261012] system 00:06: [io 0x1854-0x1857] has been reserved [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [0.261059] system 00:07: [io 0x04d0-0x04d1] has been reserved [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [0.261089] system 00:08: [io
[Touch-packages] [Bug 1447807] [NEW] systemctl enable fails to enable a SysV service
Public bug reported: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description:Ubuntu 15.04 Release:15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: New Bug description: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1413611] Re: [dialer] Speaker button with x is confusing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1413611 Title: [dialer] Speaker button with x is confusing Status in Dialer app for Ubuntu Touch: New Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: Confirmed Bug description: on active call screen, the icon used to enable the phone speaker is a speaker icon with a x, that give me the false idea that I will make the call mute if I click on it. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1413611/+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 1447606] Re: incoming call ringtone is not played repeatedly
** Changed in: telephony-service (Ubuntu) Assignee: Tiago Salem Herrmann (tiagosh) = Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: New Status in media-hub package in Ubuntu: New Status in telephony-service package in Ubuntu: Invalid Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1447282] Re: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
can you please give me the contents of /run/systemd/generator.late/dev- sda3.swap ? One more interesting tidbit: it seems that when booting with systemd, it's never enabling encrypted swap, it's just enabling normal swap using the underlying physical swap partition. Yes, that's expected after the log above. upstart doesn't do auto- discovery of swap partitions, systemd-gpt-generator does. I figure /run/systemd/generator.late/dev-sda3.swap comes from s-gpt-generator. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) Status in systemd package in Ubuntu: New Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+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 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run
** Tags added: rls-w-incoming -- 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/1389357 Title: whoopsie reuses CRASH_DB_IDENTIFIER on next run Status in whoopsie package in Ubuntu: Confirmed Bug description: On Vivid, Ubuntu 15.04, I observed the following behavior. bdmurray@blacklightning:~/Downloads$ sudo stop whoopsie [sudo] password for bdmurray: whoopsie stop/waiting bdmurray@blacklightning:~/Downloads$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com CRASH_DB_IDENTIFIER=deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd APPORT_REPORT_DIR=/var/crash/ whoopsie -f [11:07:17] Using lock path: /var/crash/whoopsie_lock [11:07:18] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] online bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd bdmurray@blacklightning:~/Downloads$ sudo start whoopsie whoopsie start/running, process 9083 bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd Notice, how the same CRASH_DB_IDENTIFIER was used by whoopsie when starting up, rather than calculating the system identifier. This may lead to crashes being reported under the wrong system-identifier if people switch from setting the environmental variable to just running whoopsie. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1389357/+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 1291950] Re: slight delay when hitting enter to launch application from dash search
** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.2 Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1291950 Title: slight delay when hitting enter to launch application from dash search Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: When I hit the super key to bring up the dash and launch an application, if I partially type an application; such as ter for Terminal if I hit enter as Terminal is the first result there is a slight delay before the application is launched -- about 1 second. The delay is slightly less when I turn off searching from online sources. Sometimes, when searching, during the delay before the application launches right at the last moment I sometimes see search results pop up right before the dash closes. These are usually local searches, sometimes online search if enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291950/+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 1447767] [NEW] [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: I installed Ubuntu 15.04 64 bit (desktop editition) on a DELL XPS 13 notebook (model 9343) and I have no sound at all. Before installing Ubuntu I upgraded bios to A03. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 23 15:46:30 2015 InstallationDate: Installed on 2015-04-23 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1447767 Title: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I installed Ubuntu 15.04 64 bit (desktop editition) on a DELL XPS 13 notebook (model 9343) and I have no sound at all. Before installing Ubuntu I upgraded bios to A03. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 23 15:46:30 2015 InstallationDate: Installed on 2015-04-23 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cribari1733 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [XPS 13 9343, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1447767/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu) Importance: Undecided = Critical ** Changed in: upstart (Ubuntu) Status: New = Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided = Critical ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww17-2015 ** Tags added: hotfix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447282] Re: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
One more interesting tidbit: it seems that when booting with systemd, it's never enabling encrypted swap, it's just enabling normal swap using the underlying physical swap partition. After booting with systemd: $ sudo swapon --summary FilenameTypeSizeUsedPriority /dev/sda3 partition 4194300 0 -1 After booting with Upstart on the same install: $ sudo swapon --summary FilenameTypeSizeUsedPriority /dev/mapper/cryptswap1 partition 4193788 0 -1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) Status in systemd package in Ubuntu: New Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+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 1366418] Re: Bluetooth BCM43142A0 doesn’t work
@Mark, Why do you need to compile something or use some unofficial kernels? Why don't you use normal Ubuntu kernel? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1366418 Title: Bluetooth BCM43142A0 doesn’t work Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not displayed in the menu bar, if I open the bluetooth UI and switch on, nothing happens and the result of “hcitool dev” is empty. I have tried to install the windows driver with ndiswrapper, and the bluetooth device seems to be detected as an usb bluetooth device but still not working. I then add the device to the bluetooth usb device and was able to activate bluetooth in the UI but it does not detect any other devices (I’ve tested with a smartphone). The driver I have installed can be found in asus page = http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/ Select Windows OS, then “bluetooth” section, take the Broadcom driver (should be the first one). If you extract this archive, you will find a file named “bcbtums- win8x64-brcm.inf” which I installed using the following command: ndiswrapper -i bcbtums-win8x64-brcm.inf Then, the result of “ndiswrapper -l” is: bcbtums-win8x64-brcm : driver installed device (04CA:2006) present in usb-devices, I find a device which was not present before installation (I might have activated btusb before on this paste): T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=2006 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM43142A0 S: SerialNumber=B8EE6593D989 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) then, “echo 04ca 2006 /sys/bus/usb/drivers/btusb/new_id”, and I can switch usb on, but no device will be detected and I’ve found this in the dmesg: [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout which looks pretty much like a “bluetooth not working” message which I don’t understand in details. I leave here my full dmesg: [0.253889] NetLabel: domain hash size = 128 [0.253890] NetLabel: protocols = UNLABELED CIPSOv4 [0.253901] NetLabel: unlabeled traffic allowed by default [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [0.255995] Switched to clocksource hpet [0.260468] AppArmor: AppArmor Filesystem Enabled [0.260488] pnp: PnP ACPI init [0.260500] ACPI: bus type PNP registered [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [0.260642] pnp 00:01: [dma 4] [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active) [0.260924] system 00:04: [io 0x0680-0x069f] has been reserved [0.260927] system 00:04: [io 0x] has been reserved [0.260928] system 00:04: [io 0x] has been reserved [0.260930] system 00:04: [io 0x] has been reserved [0.260932] system 00:04: [io 0x1c00-0x1cfe] has been reserved [0.260934] system 00:04: [io 0x1d00-0x1dfe] has been reserved [0.260935] system 00:04: [io 0x1e00-0x1efe] has been reserved [0.260937] system 00:04: [io 0x1f00-0x1ffe] has been reserved [0.260939] system 00:04: [io 0x1800-0x18fe] could not be reserved [0.260941] system 00:04: [io 0x164e-0x164f] has been reserved [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active) [0.261012] system 00:06: [io 0x1854-0x1857] has been reserved [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [0.261059] system 00:07: [io 0x04d0-0x04d1] has been reserved [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [0.261089] system 00:08: [io 0x0240-0x0259] has been reserved [0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) [0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 SYN0002
[Touch-packages] [Bug 1447606] Re: incoming call ringtone is not played repeatedly
** Changed in: media-hub Status: New = Triaged ** Changed in: media-hub (Ubuntu) Status: New = Confirmed ** Changed in: media-hub Assignee: (unassigned) = Jim Hodapp (jhodapp) ** Changed in: media-hub (Ubuntu) Assignee: (unassigned) = Jim Hodapp (jhodapp) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Triaged Status in media-hub package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Invalid Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1421009] Re: unity8 sometimes hangs on boot
With latest silo 18 on mako #183 I still got the account deleted after reboot. And the spinner is still shown many times after clicking on Sign In in the online accounts screen, both when started from system- settings-account and from the apps scope Install button. Then it takes more than 10 minutes for the user to regain back control, after what looks like a unity8 crash. While the spinner is shown, both online-accounts-ui and unity8 seem to go on a merry dance while chewing at the cpu. (perhaps it's online- accounts-lib the one inside the unity8 process, or it's qtdbus) The top that alesage sees on arale looks similar to what I see on mako: http://pasteboard.co/2MKR1ed7.png But, starting dbus-monitor doesn't show any unusual traffic that might explain the high cpu usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+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 1447606] Re: incoming call ringtone is not played repeatedly
** Changed in: canonical-devices-system-image Assignee: Bill Filler (bfiller) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1447606 Title: incoming call ringtone is not played repeatedly Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Triaged Status in media-hub package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Invalid Bug description: Mako/arale/krillin device, r196, ubuntu-touch/vivid-proposed Steps 1. Call the ubuntu phone from another phone 2. Don't answer it Expect Incoming call ringtone should be played repeatedly Result Ringtone is only played once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447606/+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 1447748] Re: SIM unlock screen unusable when launched from indicator
Unity8 has basically no idea what that dialog is, it's driven completely by the network indicator, so that's where the bug likely lies. ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447748 Title: SIM unlock screen unusable when launched from indicator Status in indicator-network package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+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 1447748] Re: SIM unlock screen unusable when launched from indicator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-network (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447748 Title: SIM unlock screen unusable when launched from indicator Status in indicator-network package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+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 1447796] Re: Some icons are not visible
The issue in Apps is likely bug #1430828, it's going to be resolved in the first vivid-based OTA. The launcher issue, however, is new to me, can you identify what app is it? If you long-press, unpin it and pin it again, is the icon back? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- 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/1447796 Title: Some icons are not visible Status in unity8 package in Ubuntu: Incomplete Bug description: Bought a bq phone with Ubuntu. First thing it does was updating Apps and the OS to Ubuntu Utopic Unicorn (development branch) - armhf (20150410-232623). Build number 21. Icons are missing at the apps scope as well as in the launcher see: https://plus.google.com/113135226934524593062/posts/Rc7eYNHdntM I can't remember if the icons were visible prior to the OS Update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447796/+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 1442962] Re: Dialer app reports No network even though cellular is connected
Next time you reproduce the issue, can you try reconnecting with mc- tool reconnect ofono/ofono/account0 and then grab the following output? dbus-send --print-reply --type=method_call --dest=org.freedesktop.Telepathy.AccountManager /org/freedesktop/Telepathy/debug org.freedesktop.Telepathy.Debug.GetMessages mission_control.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports No network even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) Current: offline (1) Requested: available (2) online Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 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/1442962/+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 1441626] Re: Opening a Quicklist while in Spread can sometimes render the Quicklist and Launcher unusable
** Changed in: unity Status: Confirmed = In Progress ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity/7.2 Importance: Undecided = Low ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None = 7.2.6 ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1441626 Title: Opening a Quicklist while in Spread can sometimes render the Quicklist and Launcher unusable Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: When opening a Quicklist while in Spread, the Quicklist and Launcher can sometimes be unusable. The Quicklist will be open, but it doesn't accept clicks nor does the Launcher. In order to clear out this condition, I enter keynav mode for the Launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1441626/+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 1407928] Re: [phone] Does not auto-switch to available, known WiFi
I'm not sure if this is a regression but I have this identical problem on a bq Aquaris 14.10 (r21) after the update from r20. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in the base for Ubuntu mobile products: Incomplete Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Incomplete Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+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 1447810] [NEW] Entering Launcher keynav mode should cancel Spread/Expo if active
Public bug reported: If the Spread or Expo is active and Launcher keynav mode is started, then Spread or Expo should be terminated. ** Affects: unity Importance: Low Assignee: Christopher Townsend (townsend) Status: In Progress ** Affects: unity/7.2 Importance: Low Assignee: Christopher Townsend (townsend) Status: Triaged ** Affects: unity (Ubuntu) Importance: Low Assignee: Christopher Townsend (townsend) Status: In Progress ** Also affects: unity/7.2 Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = In Progress ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity Importance: Undecided = Low ** Changed in: unity/7.2 Importance: Undecided = Low ** Changed in: unity (Ubuntu) Importance: Undecided = Low ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 ** Changed in: unity/7.2 Milestone: None = 7.2.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1447810 Title: Entering Launcher keynav mode should cancel Spread/Expo if active Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: If the Spread or Expo is active and Launcher keynav mode is started, then Spread or Expo should be terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1447810/+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 1351177] Re: Suggestions improvements
The linked branch does not fix the popup style (this will be taken care of in a subsequent branch). What it does is include bookmarks in the suggestions, so if you have bookmarks that match the terms entered in the address bar, they will be displayed there 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/1351177 Title: Suggestions improvements Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: Per design specification, the suggestions that show up when the user types in the address bar need to be updated in the following ways: - take up the whole screen (as opposed to being a popover) - include additional sources: bookmarks (auto-suggest is being tracked separately by bug #1351151) - display symbolic icons to tell apart different types of entries (search, history, bookmarks) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+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 1447825] [NEW] Headset jack setting not saved after a reboot
Public bug reported: When plugging in the headset for a session the headset receive sound. After a reboot, the headset still plugged in, the headset does not receive any sound. You have to reconnect the headset to receive sound. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kl 1345 F pulseaudio /dev/snd/pcmC0D0p: kl 1345 F...m pulseaudio /dev/snd/controlC0: kl 1345 F pulseaudio Date: Thu Apr 23 23:40:22 2015 InstallationDate: Installed on 2014-10-18 (187 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO GEN3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1447825 Title: Headset jack setting not saved after a reboot Status in pulseaudio package in Ubuntu: New Bug description: When plugging in the headset for a session the headset receive sound. After a reboot, the headset still plugged in, the headset does not receive any sound. You have to reconnect the headset to receive sound. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kl 1345 F pulseaudio /dev/snd/pcmC0D0p: kl 1345 F...m pulseaudio /dev/snd/controlC0: kl 1345 F pulseaudio Date: Thu Apr 23 23:40:22 2015 InstallationDate: Installed on 2014-10-18 (187 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO GEN3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1447825/+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 1447654] Re: installing policykit-1 hangs under systemd
I can reproduce this in a minimal VM by purging policykit-1, restarting systemd, and installing a service: sudo dpkg -P policykit-1 apport sudo systemctl daemon-reexec sudo apt-get install policykit-1 apport This reminds me a lot of bug 1423811, but this might actually lead to a simpler test case and a different angle for understanding this. Workaround: Install policykit-1 first, then reboot, then install everything else. Thanks for your report! ** Changed in: systemd (Ubuntu) Importance: Undecided = High ** Changed in: systemd (Ubuntu) Status: New = In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) ** Tags added: systemd-boot ** Also affects: systemd (Ubuntu Vivid) Importance: High Assignee: Martin Pitt (pitti) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447654/+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 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.
3.19.0-15-generic x86_64 x86_64 x86_64 problem persists -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1014992 Title: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied. Status in bluez package in Ubuntu: Confirmed Bug description: After updating from 8.04 to 12.04 I cannot use rfcomm without sudo. I've already added the user to group 'dialout' . Temporary I tried to change udev.rules (KERNEL==rfcomm[0-9]*, GROUP=dialout, MODE=666) but this doesn't solve the problem so I removed it again. Here the commands I used : burki@orion:/$ hcitool scan Scanning ... 00:12:6F:08:98:FFGEO LE-71 1 burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF Can't open RFCOMM device: Permission denied burki@orion:/$ ls -l /dev/rfcomm1 ls: cannot access /dev/rfcomm1: No such file or directory burki@orion:/$ groups burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse scanner lpadmin netdev sambashare burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1 Press CTRL-C for hangup In another terminal while connection is running ... burki@orion:/$ ls -l /dev/rfcomm1 crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1 burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1) (I've stolen this command from another bug report #570692. Output is very long. Please see attachment) WORKAROUND: sudo chmod u+s /usr/bin/rfcomm ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18 Uname: Linux 3.2.0-25-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: burki 1730 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 56' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0887,10438444,00100302 HDA:80862805,80862805,0010' Controls : 49 Simple ctrls : 21 Date: Tue Jun 19 09:15:54 2012 HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-25-generic-pae N/A linux-backports-modules-3.2.0-25-generic-pae N/A linux-firmware1.79 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1014992/+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 1447807] Re: systemctl enable fails to enable a SysV service
Looking closer, the service is getting enabled - the update-rc.d commands are succeeding and the init.d links are getting created - but systemctl is still returning an error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Invalid Bug description: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1437051] Re: Keyboard not detected ThinkPad Helix
jonnieo, as this bug report is closed, please file a new report via a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. When opening up the new report, please feel free to subscribe me to it. ** Changed in: xorg (Ubuntu) Status: Confirmed = Invalid -- 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/1437051 Title: Keyboard not detected ThinkPad Helix Status in xorg package in Ubuntu: Invalid Bug description: Brand new ThinkPad Helix with docking keyboard (part number 20CGCTO1WW) Keyboard works fine in Windows and in Grub, but is not detected whatsoever in Ubuntu. (I've also tried Ubuntu MATE and Mint with the same result.) I did find /dev/input/by-path/platform-i8042-serio-0-event-kbd which looks like it might be the correct device. It is a link to /dev/input/event3. Running an hd and an evtest on that device yields no results, while it does give results for a USB keyboard. xinput -list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8595) id=10 [slave pointer (2)] ⎜ ↳ ATML1000:00 03EB:8A29 id=12 [slave pointer (2)] ⎜ ↳ WCOM0009:00 056A:0114 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Video Bus id=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Rear Camera id=9[slave keyboard (3)] ↳ Integrated Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=17 [slave keyboard (3)] xinput -list-props AT Translated Set 2 keyboard Device 'AT Translated Set 2 keyboard': Device Enabled (136): 1 Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Product ID (253):1, 1 Device Node (254): /dev/input/event3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Mar 26 17:11:11 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:222b] InstallationDate: Installed on 2015-03-24 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: LENOVO 20CGCTO1WW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=aaad9f95-89f8-4a89-bc15-c5c867da639c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N17ET70W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ET70W(1.70):bd12/26/2014:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct11:cvrNone: dmi.product.name: 20CGCTO1WW dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work
@Pilot6 I have bluetooth issue as well but I have Linux Arch OS (kernel 3.16.7); Currently I coudn't find any Arch's os adapted solution so there is only way to compile and install the standart www.kernel.org's kernel which is patched or similar :) The bluetooth issue which described here (bug 1366418) is quite specific so I am really hope to find generic solution; Adding (inserting) working bluetooth firmware module for example? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1366418 Title: Bluetooth BCM43142A0 doesn’t work Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not displayed in the menu bar, if I open the bluetooth UI and switch on, nothing happens and the result of “hcitool dev” is empty. I have tried to install the windows driver with ndiswrapper, and the bluetooth device seems to be detected as an usb bluetooth device but still not working. I then add the device to the bluetooth usb device and was able to activate bluetooth in the UI but it does not detect any other devices (I’ve tested with a smartphone). The driver I have installed can be found in asus page = http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/ Select Windows OS, then “bluetooth” section, take the Broadcom driver (should be the first one). If you extract this archive, you will find a file named “bcbtums- win8x64-brcm.inf” which I installed using the following command: ndiswrapper -i bcbtums-win8x64-brcm.inf Then, the result of “ndiswrapper -l” is: bcbtums-win8x64-brcm : driver installed device (04CA:2006) present in usb-devices, I find a device which was not present before installation (I might have activated btusb before on this paste): T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=2006 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM43142A0 S: SerialNumber=B8EE6593D989 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) then, “echo 04ca 2006 /sys/bus/usb/drivers/btusb/new_id”, and I can switch usb on, but no device will be detected and I’ve found this in the dmesg: [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout which looks pretty much like a “bluetooth not working” message which I don’t understand in details. I leave here my full dmesg: [0.253889] NetLabel: domain hash size = 128 [0.253890] NetLabel: protocols = UNLABELED CIPSOv4 [0.253901] NetLabel: unlabeled traffic allowed by default [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [0.255995] Switched to clocksource hpet [0.260468] AppArmor: AppArmor Filesystem Enabled [0.260488] pnp: PnP ACPI init [0.260500] ACPI: bus type PNP registered [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [0.260642] pnp 00:01: [dma 4] [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active) [0.260924] system 00:04: [io 0x0680-0x069f] has been reserved [0.260927] system 00:04: [io 0x] has been reserved [0.260928] system 00:04: [io 0x] has been reserved [0.260930] system 00:04: [io 0x] has been reserved [0.260932] system 00:04: [io 0x1c00-0x1cfe] has been reserved [0.260934] system 00:04: [io 0x1d00-0x1dfe] has been reserved [0.260935] system 00:04: [io 0x1e00-0x1efe] has been reserved [0.260937] system 00:04: [io 0x1f00-0x1ffe] has been reserved [0.260939] system 00:04: [io 0x1800-0x18fe] could not be reserved [0.260941] system 00:04: [io 0x164e-0x164f] has been reserved [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active) [0.261012] system 00:06: [io 0x1854-0x1857] has been reserved [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [0.261059] system 00:07: [io 0x04d0-0x04d1] has
[Touch-packages] [Bug 1446081] Re: Incorrect scaling of launcher icons
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446081 Title: Incorrect scaling of launcher icons Status in unity package in Ubuntu: Confirmed Bug description: Launcher icons shown w/o issues only on this sizes of launcher: 16, 24, 32, 48, 64. Screenshot attached. Look at Sublime, Chrome and Skype icons. There was no such issue before vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 20 00:26:44 2015 JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446081/+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 1431957] Re: ActivityIndicator much more CPU intensive
** Summary changed:
- ActivityIndicator much more CPU intensive under xvfb
+ ActivityIndicator much more CPU intensive
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1431957
Title:
ActivityIndicator much more CPU intensive
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Given:
import QtQuick 2.3
import Ubuntu.Components 1.2
Item {
width: childrenRect.width
height: childrenRect.height
Grid {
columns: 20
Repeater {
model: 400
ActivityIndicator {
id: indicator
running: true
}
}
}
Timer {
interval: 1
running: true
onTriggered: Qt.quit()
}
}
Running it under xvfb with current UITK:
$ time xvfb-run -s -screen 0 1024x1024x24 qmlscene testactivity.qml
20,60s user 0,44s system 205% cpu 10,225 total
When with the release before (1.1.1403+15.04.20150206-0ubuntu2¹):
8,42s user 0,10s system 83% cpu 10,226 total
As you can see the difference is more than double. The offending
revision is 1222.1.16² that changes the ActivityIndicatorStyle's
RotationAnimation to RotationAnimator, making sure that it runs on the
rendering thread and is not blocked by the GUI thread.
The difference in runs outside of xvfb are minimal, in favour of the new
version:
$ time qmlscene testactivity.qml
1,13s user 0,18s system 12% cpu 10,412 total
vs.
1,13s user 0,13s system 12% cpu 10,415 total
There is unfortunately some side-effect of this, the unity8 QML test
suite went from taking under an hour to over two hours during our CI
runs - see the attached trend chart. You can clearly see the spike at
around job #563. Part of the increase is the fact that we were using
the ActivityIndicator to force a render pass and cause
waitForRendering() calls to return early, but the difference caused by
that is about 10 minutes³, not an hour.
¹
https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.1.1403+15.04.20150206-0ubuntu2
²
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1122.1.16
³ https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-vivid/602/
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-ubuntu-ui-toolkit-plugin
1.2.1433+15.04.20150306-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 17:11:18 2015
SourcePackage: ubuntu-ui-toolkit
SystemImageInfo:
current build number: 0
device name:
channel: daily
last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1431957/+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 1421009] Re: unity8 sometimes hangs on boot
Note that the activity indicator itself might be the CPU hogger - see bug #1431957. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+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 1447654] Re: apt-get install lubuntu-core fails when installed from netboot
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: apt-get install lubuntu-core fails when installed from netboot Status in debian-installer package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1447654/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch
@Sebastien: thank you for that link. I have allready tried that ubuntu-location-serviced-cli commands before. And I think that was exactly the cause for losing the ability to provide geolocations to the apps. Now I remember that you have to reboot the phone after issuing those commands to give access to geodata back to the apps. Obviously I haven't rebooted the device for some days now. (that's a good sign, isn't it?) Now I get some data at least. Currently I'm indoors so it's only calculated from the cell info. So I'll keep an eye on the GPS during the next days and report back here. btw: the logfiles in /var/log/ubuntu-location-service are dated from january and february. that is long before I got my device. should I worry about that, or is it rather a good sign. indicating that currently everything is ok? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+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 1447807] Re: systemctl enable fails to enable a SysV service
This is because the sysstat package does not actually have a systemd unit. It just has a sysvinit init.d script, so you can't enable/disable this via systemd. You need to enable/disable it via update-rc.d (or manual symlinks in /etc/rc?.d/). ** Changed in: systemd (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Invalid Bug description: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1447816] [NEW] Unity desktop broken after last update
Public bug reported: Few days ago, I updated my system from Ubuntu Updater. When the process finished, Unity desktop freezed, although the mouse pointer was still responsive. I did a system reboot, but once when my session was open: 1. Unity launcher was freezed, with no icons (white squares were placed instead of them). 2. Global menu was freezed. 3. No icons in the right-upper corner of the screen (wifi indicator, keyboard language button, bluetooth icon, etc, wheren't displayed). 4. Mouse pointer was responsive, it didn't freeze. 5. When the icons of the top bar finally appeared, they reacted very slowly to the mouse clicks. I tried to solve this issue with sudo apt-get install --reinstall ubuntu-desktop, but it didn't work. Using: Ubuntu 14.04, 64 bits. NVIDIA GeForce 6200, with official NVIDIA driver (installed with 'additional drivers' tool). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20150316-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.agp.gpu: Fast Writes:Supported SBA:Supported AGP Rates: 8x 4x Registers: 0xff000e1b:0x1f000302 .proc.driver.nvidia.agp.host.bridge: Host Bridge:PCI device 1106:0204 Fast Writes:Not Supported SBA:Supported AGP Rates: 8x 4x Registers: 0x1f000a0b:0x0b02 .proc.driver.nvidia.agp.status: Status: Enabled Driver: AGPGART AGP Rate: 8x Fast Writes:Disabled SBA:Enabled .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 23 17:38:24 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation NV44A [GeForce 6200] [10de:0221] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:a403] InstallationDate: Installed on 2014-11-22 (152 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=0bbaee34-88b2-46e9-9fd2-9d7efa698bdc ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-M2 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/18/2005:svn:pn:pvr:rvn:rnK8M800-M2:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 23 17:37:57 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04f3:0103KEYBOARD, id 8 inputHID 04f3:0103KEYBOARD, id 9 inputUSB Optical MouseMOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1447816 Title: Unity desktop broken after last update Status in unity package in Ubuntu: New Bug description: Few days ago, I updated my system from Ubuntu Updater. When the process finished, Unity desktop freezed, although the mouse pointer was still responsive. I did a system reboot, but once when my session was open: 1. Unity launcher was freezed, with no icons (white squares were placed instead of them). 2. Global menu was freezed. 3. No icons in the right-upper corner of the screen (wifi indicator, keyboard language
