[Touch-packages] [Bug 1371625] Re: wifi don't work after suspend
Your command is very useful. Thank you! :) I have also a problem in boot sequence. Do you have same situation? When i boot pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network is ready after more 60 seconds and before nmcli nm command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1366355] Re: getty allows to move cursor using arrow keys
Confirming here, too. Now the cursor keys "just" cause their escape sequence to be printed out, but you can't move around any more. ** Changed in: util-linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1366355 Title: getty allows to move cursor using arrow keys Status in “util-linux” package in Ubuntu: Fix Released Bug description: util-linux version: 2.20.1-1ubuntu3.1 Switch to tty. Press any arrow key. Cursor has been moved. You may type and replace labels or write own text. getty should not allow move cursor out of login field. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1366355/+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 1371625] Re: wifi don't work after suspend
I find a way to easy reproduce it. gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.HybridSleep true -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1387908] Re: FIDO u2f security keys should be supported out of the box
Also see http://lists.freedesktop.org/archives/systemd- devel/2014-October/024605.html -- 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/1387908 Title: FIDO u2f security keys should be supported out of the box Status in “systemd” package in Ubuntu: Incomplete Status in “systemd” source package in Trusty: New Status in “systemd” source package in Utopic: New Status in “systemd” source package in Vivid: Incomplete Bug description: FIDO u2f is an emerging standard for public-private cryptography based 2nd factor authentication, which improves on OTP by mitigating phishing, man-in-the-middle attacks and reply attacks. Google Chrome supports u2f devices which are now widely available from Yubico (new premium neo Yubikeys and Security keys). However, udev rules are required to setup permissions to allow the web-browsers which are running as regular users to access the devices in question. E.g.: KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev", ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120" Something like that should be enabled by default, however probably not encode on the vendor/productid as other vendors will also make u2f devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387908/+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 1387908] Re: FIDO u2f security keys should be supported out of the box
I agree that we shouldn't hardcode vendor/product IDs then; this would be ok for a minimally intrusive SRU, though (where we probably don't want to introduce new helpers). So how can these be identified in a generic way? ** Changed in: systemd (Ubuntu Vivid) Status: New => Incomplete -- 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/1387908 Title: FIDO u2f security keys should be supported out of the box Status in “systemd” package in Ubuntu: Incomplete Status in “systemd” source package in Trusty: New Status in “systemd” source package in Utopic: New Status in “systemd” source package in Vivid: Incomplete Bug description: FIDO u2f is an emerging standard for public-private cryptography based 2nd factor authentication, which improves on OTP by mitigating phishing, man-in-the-middle attacks and reply attacks. Google Chrome supports u2f devices which are now widely available from Yubico (new premium neo Yubikeys and Security keys). However, udev rules are required to setup permissions to allow the web-browsers which are running as regular users to access the devices in question. E.g.: KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev", ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120" Something like that should be enabled by default, however probably not encode on the vendor/productid as other vendors will also make u2f devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387908/+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 1387944] Re: Transition to bluez5
** Changed in: bluez (Debian) Status: Unknown => Fix Released -- 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/1387944 Title: Transition to bluez5 Status in “bluez” package in Ubuntu: New Status in “bluez” package in Debian: Fix Released Bug description: Please package bluez 5 for ubuntu vivid. It changes much of the API and is required by projects such as gnome-bluetooth, bluedevil, and blueman. Bluez 4 has been deprecated for some time, so fixes will only be received in version 5 anyway. The only components that need major work are ubuntu-only packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387944/+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 1387985] [NEW] impossible to update
Public bug reported: Bonjour est il possible de m'aidé en français, je ne métrissse pas assez l'anglais Merci d'avance JPDW jpdwhp@jpdwhp:~$ ls -l /etc/apt/sources.list.d total 76 -rw-r--r-- 1 root root 168 oct 29 17:13 andykimpe-freshplayerplugin-daily-trusty.list -rw-r--r-- 1 root root 170 oct 29 17:13 andykimpe-freshplayerplugin-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 danielrichter2007-grub-customizer-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 danielrichter2007-grub-customizer-trusty.list.save -rw-r--r-- 1 root root 337 oct 29 17:13 eid.list -rw-r--r-- 1 root root 337 oct 29 17:13 eid.list.save -rw-r--r-- 1 root root 452 jun 26 10:49 eid.list.ucf-dist -rw-r--r-- 1 root root 0 oct 23 10:01 getdeb.list -rw-r--r-- 1 root root 56 jun 25 12:05 getdeb.list.bck -rw-r--r-- 1 root root 0 oct 23 10:01 getdeb.list.save -rw-r--r-- 1 root root 0 mai 28 10:43 google.list -rw-r--r-- 1 root root 0 mai 28 10:43 google.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 gwendal-lebihan-dev-cinnamon-nightly-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 gwendal-lebihan-dev-cinnamon-nightly-trusty.list.save -rw-r--r-- 1 root root 0 jun 26 10:53 gwendal-lebihan-dev-cinnamon-stable-trusty.list -rw-r--r-- 1 root root 0 jun 26 10:53 gwendal-lebihan-dev-cinnamon-stable-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-daily-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-stable-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-stable-trusty.list.save -rw-r--r-- 1 root root 68 oct 29 17:13 jd-team-jdownloader-trusty.list -rw-r--r-- 1 root root 68 oct 29 17:13 jd-team-jdownloader-trusty.list.save -rw-r--r-- 1 root root 146 oct 29 17:13 jon-severinsson-ffmpeg-trusty.list -rw-r--r-- 1 root root 146 oct 29 17:13 jon-severinsson-ffmpeg-trusty.list.save -rw-r--r-- 1 root root 0 aoû 4 10:32 motumedia-mplayer-daily-trusty.list -rw-r--r-- 1 root root 76 aoû 4 10:32 motumedia-mplayer-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 nemh-gambas3-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 nemh-gambas3-trusty.list.save -rw-r--r-- 1 root root 0 oct 21 11:06 nilarimogard-webupd8-trusty.list -rw-r--r-- 1 root root 0 oct 21 11:06 nilarimogard-webupd8-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 noobslab-pear-apps-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 noobslab-pear-apps-trusty.list.save -rw-r--r-- 1 root root 0 jun 26 10:54 openshot_developers-ppa-trusty.list -rw-r--r-- 1 root root 76 jun 26 10:54 openshot_developers-ppa-trusty.list.save -rwxr-xr-x 1 root root 0 mai 12 09:24 opera.list -rwxr-xr-x 1 root root 0 mai 12 09:24 opera.list.save -rw-r--r-- 1 root root 148 oct 29 17:13 otto-kesselgulasch-gimp-trusty.list -rw-r--r-- 1 root root 148 oct 29 17:13 otto-kesselgulasch-gimp-trusty.list.save -rw-r--r-- 1 root root 0 jun 18 09:29 rvm-mplayer-trusty.list -rw-r--r-- 1 root root 64 jun 18 09:29 rvm-mplayer-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 spotify.list -rw-r--r-- 1 root root 0 mai 6 13:38 spotify.list.save -rw-r--r-- 1 root root 0 aoû 3 10:17 stebbins-handbrake-releases-trusty.list -rw-r--r-- 1 root root 0 aoû 3 10:17 stebbins-handbrake-releases-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 tsbarnes-indicator-keylock-daily-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 tsbarnes-indicator-keylock-daily-trusty.list.save -rw-r--r-- 1 root root 140 oct 29 17:13 ubuntu-mate-dev-ppa-trusty.list -rw-r--r-- 1 root root 140 oct 29 17:13 ubuntu-mate-dev-ppa-trusty.list.save -rw-r--r-- 1 root root 156 oct 29 17:13 ubuntu-mate-dev-trusty-mate-trusty.list -rw-r--r-- 1 root root 156 oct 29 17:13 ubuntu-mate-dev-trusty-mate-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 ubuntu-tweak-testing-ppa-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 ubuntu-tweak-testing-ppa-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 yannubuntu-boot-repair-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 yannubuntu-boot-repair-trusty.list.save jpdwhp@jpdwhp:~$ cat /etc/apt/sources.list.d/eid.list.ucf-dist # To enable the testing repository, uncomment the below line and run # "dpkg-reconfigure eid-archive" to enable the archive key. # # WARNING WARNING WARNING # The testing repository contains untested and unsupported prerelease # packages. Use at your own risk! # WARNING WARNING WARNING # deb http://files.eid.belgium.be/debian continuous/trusty main # The regular repository with released packages. deb http://files.eid.belgium.be/debian trusty main jpdwhp@jpdwhp:~$ cat /etc/apt/sources.list.d/getdeb.list.bck deb http://archive.getdeb.net/ubuntu trusty-getdeb apps J'ai aussi ce message E: /var/cache/apt/archives/mate-applets_1.8.1+dfsg1-1~trusty1_amd64.deb: tentative de remplacement de « /usr/share/man/man1/cpuf
[Touch-packages] [Bug 1330037] Re: [FFe] upower 0.99.1 transition
gnome-session moved to systemd in https://code.launchpad.net/~darkxst /gnome-session/3.14/+merge/240212, thus dropping the upower dep. ** Changed in: gnome-session (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: Fix Committed Status in “cinnamon-session” package in Ubuntu: Fix Released Status in “cinnamon-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Committed Status in “gnome-session” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: Fix Committed Status in “gnome-shell-pomodoro” package in Ubuntu: Fix Committed Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Committed Status in “mate-power-manager” package in Ubuntu: Fix Committed Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: Fix Committed Status in “powerd” package in Ubuntu: In Progress Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Fix Committed Status in “unity-settings-daemon” package in Ubuntu: Fix Committed Status in “upower” package in Ubuntu: Fix Committed Status in “wmbattery” package in Ubuntu: Fix Committed Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: Fix Committed Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1378438] Re: Printer dialog stuck on "Getting printer information..."
Did you kill the process after you `chmod -r`'d it? Or, did you restart? Don't forget to `killall scp-dbus-service.py` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1378438 Title: Printer dialog stuck on "Getting printer information..." Status in “cups” package in Ubuntu: Confirmed Bug description: In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered printer, the "Status" field changes to "Getting printer information..." and the mouse cursor goes into spinning icon, and the Print button stays disabled, so I cannot print. In Firefox, the status tells me the printer is low on toner, but allows me to print. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cups 1.7.5-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CupsErrorLog: E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address - Permission denied E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address - Permission denied CurrentDesktop: GNOME Date: Tue Oct 7 09:29:43 2014 InstallationDate: Installed on 2014-02-24 (224 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro11,3 Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B02.1310181745 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
I found this which might be the problem: QUrl AalMediaPlayerControl::unescape(const QMediaContent &media) const { if (media.isNull()) return QUrl(); return QUrl::fromPercentEncoding(media.canonicalUrl().toString().toUtf8()); } I tested this with a small commandline thing, and fromPercentEncoding() can mangle that url : QString str = "http://previews.7digital.com/clip/40202347?oauth_signature=FVgXk5tzbSyyB6/g/78GO8REavA%3D";; qDebug() << QUrl::fromPercentEncoding(str.toUtf8()); output: "http://previews.7digital.com/clip/40202347?oauth_signature=FVgXk5tzbSyyB6/g/78GO8REavA="; -- 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/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Status in “unity8” package in Ubuntu RTM: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner 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/1381930/+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 1348784] Re: dbus invoked while in recovery mode
** Summary changed: - thermald prevents unmounting /dev/sda1 in recovery mode + dbus invoked while in recovery mode ** Changed in: thermald (Ubuntu) Status: In Progress => Invalid -- 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/1348784 Title: dbus invoked while in recovery mode Status in “thermald” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: New Bug description: I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is started in the recovery mode it is not possible to unmount /dev/sda1 because thermald is running. Interestingly lsof hasn't even showed that something has a file descriptor on /dev/sda1 open but executing "stop thermald" has worked as a workaround. --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes NonfreeKernelModules: fglrx Package: upstart 1.13.2-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic root=UUID=af27feae-4c9e-4b5f-a1e1-900c0e71c5cb ro elevator=cfq ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Tags: utopic Uname: Linux 3.16.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.13.2) UserGroups: _MarkForUpload: True modified.conffile..etc.lxdm.lxdm.conf: [modified] mtime.conffile..etc.init.control.alt.delete.conf: 2012-05-05T17:10:11.434470 mtime.conffile..etc.init.tty2.conf: 2014-05-29T05:14:16.791093 mtime.conffile..etc.init.tty3.conf: 2012-05-05T17:10:49.238469 mtime.conffile..etc.init.tty4.conf: 2012-05-05T17:10:58.066468 mtime.conffile..etc.init.tty5.conf: 2012-05-05T17:11:02.938468 mtime.conffile..etc.init.tty6.conf: 2012-05-05T17:11:09.442468 mtime.conffile..etc.lxdm.lxdm.conf: 2012-12-23T19:04:26.948844 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1348784/+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 1387985] Re: impossible to update
hello jp maitriser l'anglais est indispensable (et le français aussi d'ailleurs !!! ) "est il possible de m'aidé en français, je ne métrissse pas assez l'anglais" "est-il possible de m'aider en français, je ne maitrise pas assez l'anglais" en ce qui concerne ton problème, ce n'est pas un 'bug', mais un sources.list impossible à gérer: - trop d'entrées 'exotique' et non fiable (à désactiver/purger ces ppa à l'aide de ppa-purge) - ensuite suivre les 'howto' & 'wiki' d'ubuntu (http://doc.ubuntu-fr.org/) à noter que 'ubuntu forum' est le lieu prioritaire pour obtenir de l'aide en cas de difficulté (http://forum.ubuntu-fr.org/) ** Changed in: xorg (Ubuntu) Status: New => 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/1387985 Title: impossible to update Status in “xorg” package in Ubuntu: Invalid Bug description: Bonjour est il possible de m'aidé en français, je ne métrissse pas assez l'anglais Merci d'avance JPDW jpdwhp@jpdwhp:~$ ls -l /etc/apt/sources.list.d total 76 -rw-r--r-- 1 root root 168 oct 29 17:13 andykimpe-freshplayerplugin-daily-trusty.list -rw-r--r-- 1 root root 170 oct 29 17:13 andykimpe-freshplayerplugin-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 danielrichter2007-grub-customizer-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 danielrichter2007-grub-customizer-trusty.list.save -rw-r--r-- 1 root root 337 oct 29 17:13 eid.list -rw-r--r-- 1 root root 337 oct 29 17:13 eid.list.save -rw-r--r-- 1 root root 452 jun 26 10:49 eid.list.ucf-dist -rw-r--r-- 1 root root 0 oct 23 10:01 getdeb.list -rw-r--r-- 1 root root 56 jun 25 12:05 getdeb.list.bck -rw-r--r-- 1 root root 0 oct 23 10:01 getdeb.list.save -rw-r--r-- 1 root root 0 mai 28 10:43 google.list -rw-r--r-- 1 root root 0 mai 28 10:43 google.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 gwendal-lebihan-dev-cinnamon-nightly-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 gwendal-lebihan-dev-cinnamon-nightly-trusty.list.save -rw-r--r-- 1 root root 0 jun 26 10:53 gwendal-lebihan-dev-cinnamon-stable-trusty.list -rw-r--r-- 1 root root 0 jun 26 10:53 gwendal-lebihan-dev-cinnamon-stable-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-daily-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-stable-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 i-nex-development-team-stable-trusty.list.save -rw-r--r-- 1 root root 68 oct 29 17:13 jd-team-jdownloader-trusty.list -rw-r--r-- 1 root root 68 oct 29 17:13 jd-team-jdownloader-trusty.list.save -rw-r--r-- 1 root root 146 oct 29 17:13 jon-severinsson-ffmpeg-trusty.list -rw-r--r-- 1 root root 146 oct 29 17:13 jon-severinsson-ffmpeg-trusty.list.save -rw-r--r-- 1 root root 0 aoû 4 10:32 motumedia-mplayer-daily-trusty.list -rw-r--r-- 1 root root 76 aoû 4 10:32 motumedia-mplayer-daily-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 nemh-gambas3-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 nemh-gambas3-trusty.list.save -rw-r--r-- 1 root root 0 oct 21 11:06 nilarimogard-webupd8-trusty.list -rw-r--r-- 1 root root 0 oct 21 11:06 nilarimogard-webupd8-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 noobslab-pear-apps-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 noobslab-pear-apps-trusty.list.save -rw-r--r-- 1 root root 0 jun 26 10:54 openshot_developers-ppa-trusty.list -rw-r--r-- 1 root root 76 jun 26 10:54 openshot_developers-ppa-trusty.list.save -rwxr-xr-x 1 root root 0 mai 12 09:24 opera.list -rwxr-xr-x 1 root root 0 mai 12 09:24 opera.list.save -rw-r--r-- 1 root root 148 oct 29 17:13 otto-kesselgulasch-gimp-trusty.list -rw-r--r-- 1 root root 148 oct 29 17:13 otto-kesselgulasch-gimp-trusty.list.save -rw-r--r-- 1 root root 0 jun 18 09:29 rvm-mplayer-trusty.list -rw-r--r-- 1 root root 64 jun 18 09:29 rvm-mplayer-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 spotify.list -rw-r--r-- 1 root root 0 mai 6 13:38 spotify.list.save -rw-r--r-- 1 root root 0 aoû 3 10:17 stebbins-handbrake-releases-trusty.list -rw-r--r-- 1 root root 0 aoû 3 10:17 stebbins-handbrake-releases-trusty.list.save -rw-r--r-- 1 root root 0 mai 6 13:38 tsbarnes-indicator-keylock-daily-trusty.list -rw-r--r-- 1 root root 0 mai 6 13:38 tsbarnes-indicator-keylock-daily-trusty.list.save -rw-r--r-- 1 root root 140 oct 29 17:13 ubuntu-mate-dev-ppa-trusty.list -rw-r--r-- 1 root root 140 oct 29 17:13 ubuntu-mate-dev-ppa-trusty.list.save -rw-r--r-- 1 root root 156 oct 29 17:13 ubuntu-mate-dev-trusty-mate-trusty.list -rw-r--r-- 1 root root 156 oct 29 17:13 ubuntu-mate-dev-trusty-mate-trusty.list.save -rw-r--r-- 1 root root 0 mai
[Touch-packages] [Bug 1370852] Re: Scans all user accounts when not required
It seems that this change actually broke .dmrc files on Debian. I'm currently investigating, but it seems that the files (~/.dmrc and /var/cache/lightdm/dmrc/user.dmrc) are not updated anymore with the selected session. -- 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/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] When AccountsService is not present on startup LightDM scans all the user accounts and attempts to access the dmrc file for each user. It does not use any information from the dmrc files. If you have many users and/or the dmrc files are on a slow filesystem this creates a big startup delay. [Test Case] 1. Start LightDM on a system that doesn't have AccountsService and has many users Expected result: LightDM starts quickly Observed result: LightDM takes a long time to start [Regression potential] Low. We now only access the dmrc files when information from them i s required (lazy load). Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1371625] Re: wifi don't work after suspend
paolo, I did have encountered the issue you mentioned in comment #7, however that was on ubuntu precise (12.04), and it wasn't reproduced on 12.10 and later. Could you please report a separate LP bug for it. For the NM asleep issue, we can put the workaround in a PM hook, so we don't have to manually invoke the command every time. Please create a file /etc/pm/sleep.d/90_awake-network-manager with below content: ``` #!/bin/sh case "$1" in resume|thaw) nmcli nm sleep false ;; esac ``` Please also make sure it's executable: chmod a+x /etc/pm/sleep.d/90_awake-network-manager -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1294732] Re: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term
This is not the only case where the UI assumes the device is a phone; bug 1258211 is another. I don't think using "device" is a general solution, because that makes the OS seem as if it doesn't know that it's running on a phone. "Welcome to your new ... uh ... whatever the heck this thing is." Maybe this discussion will seem quaint 30 years from now, but in the meantime, I suggest we come up with a standard method to label the type of device Ubuntu is running on. Otherwise we'll end up with some parts of the UI calling it a phone because it has a SIM, other parts calling it a tablet because its screen is more than 6.5 inches, etc. ** Description changed: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" + + See also bug 1258211. -- 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/1294732 Title: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Invalid Bug description: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" See also bug 1258211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294732/+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 1294732] Re: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed -- 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/1294732 Title: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Invalid Bug description: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" See also bug 1258211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294732/+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 1382510] Re: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch
I've installed packages: http://launchpadlibrarian.net/188726673/libsystemd-daemon0_204-5ubuntu20.8_amd64.deb http://launchpadlibrarian.net/188726662/systemd-services_204-5ubuntu20.8_amd64.deb http://launchpadlibrarian.net/188727128/libpam-systemd_204-5ubuntu20.8_i386.deb http://launchpadlibrarian.net/18872/libpam-systemd_204-5ubuntu20.8_amd64.deb and the issue is resolved for me. Thanks. -- 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/1382510 Title: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Fix Committed Bug description: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so &> /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) SRU TEST CASE = - On an amd64 system, run "sudo apt-get install libpam-systemd:i386" - Then run "sudo restart systemd-logind" - On current trusty this will result in stop/waiting, with the error in /var/log/upstart/systemd-logind.log as above. - With this fix this will result in start/running and no error. My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+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 740506]
Hi all Funding is all very well, and +1 for the initiative! But first we'll need to find developers who are willing to take up the task. Is there anyone interested in implementing this (immensely important, believe me!) feature? Can we spur his or her interest with money? Or can we say that allowing this functionality to exist in one closed- source vendor's application alone is tantamount to having your passports checked at the border by a representative of a commercial enterprise, who does not tell you by what criteria it checks the document, bit still is entitled to deny you admission? We did a fundraiser (http://wilhelmtux.ch/?MID=11&PID=96) recently for finishing the implementation of the *signing* part in LibreOffice, which is also in C++ and uses Mozilla NSS. So maybe some of the code can be reused. Most of the original code should be available here: http://cgit.freedesktop.org/libreoffice/core/commit/?id=9c8dc01d3a40ec905c9d816c733ceb5d621e0426 Search by author should also work: http://cgit.freedesktop.org/libreoffice/core/log/?qt=author&q=eraslan As this is still work in progress, please follow https://bugs.freedesktop.org/show_bug.cgi?id=83940 for updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures Status in Evince document viewer: Confirmed Status in Poppler: Confirmed Status in “poppler” package in Ubuntu: Triaged Bug description: Binary package hint: evince This is a feature request to verify digital signatures. I'm receiving more and more digitally signed PDF's and evince already acknowledges them with: Signature Not Verified Digitally signed by Date: Reason: Location: but it would be great if Evince would be integrated into the distro's ca-certificate infrastructure to verify these signatures. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+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 740506] Re: verify digital signatures
** Bug watch added: freedesktop.org Bugzilla #83940 https://bugs.freedesktop.org/show_bug.cgi?id=83940 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures Status in Evince document viewer: Confirmed Status in Poppler: Confirmed Status in “poppler” package in Ubuntu: Triaged Bug description: Binary package hint: evince This is a feature request to verify digital signatures. I'm receiving more and more digitally signed PDF's and evince already acknowledges them with: Signature Not Verified Digitally signed by Date: Reason: Location: but it would be great if Evince would be integrated into the distro's ca-certificate infrastructure to verify these signatures. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+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 1388005] [NEW] ppa-purge
Public bug reported: je bonjour je ne parviens pas à intaller ppa-purge ou de le mettre en ligne de commande terminal donc je ne sais pas mettre à jour. Merci pour votre aide Sur le forum je n'ai pas encore eu de solution Cordialement JPDW ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 31 10:22:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a8c] InstallationDate: Installed on 2014-05-10 (174 days ago) InstallationMedia: Cubuntu 14.04 - Release amd64 LightdmGreeterLog: ** (lightdm-gtk-greeter:1656): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1661): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: Compaq-Presario WC690AA-UUG CQ5310BE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2e8ed171-6550-4a46-a4b4-3db56a7eed2d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.09 dmi.board.name: ETON dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.09:bd11/27/2009:svnCompaq-Presario:pnWC690AA-UUGCQ5310BE:pvr:rvnFOXCONN:rnETON:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: WC690AA-UUG CQ5310BE dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Oct 31 08:25:00 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49177 vendor PHL xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1388005 Title: ppa-purge Status in “xorg” package in Ubuntu: New Bug description: je bonjour je ne parviens pas à intaller ppa-purge ou de le mettre en ligne de commande terminal donc je ne sais pas mettre à jour. Merci pour votre aide Sur le forum je n'ai pas encore eu de solution Cordialement JPDW ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 31 10:22:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a8c] InstallationDate: Installed on 2014-05-10 (174 days ago) InstallationMedia: Cubuntu 14.04 - Release amd64 LightdmGreeterLog: ** (lightdm-gtk-greeter:1656): WARNING **: Failed to load user bac
[Touch-packages] [Bug 244250] Re: Spurious reboot notifications caused by libssl upgrades.
@mdeslaur: Thank you for your reply! Does that mean that it is supposed to happen on an Ubuntu server system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/244250 Title: Spurious reboot notifications caused by libssl upgrades. Status in “openssl” package in Ubuntu: Fix Released Bug description: The postinst script for libssl0.9.8 currently has a bug where it sends a reboot notifcation whenever libssl is configured. So reconfiguring libssl0.9.8 or even just installing libssl0.9.8 will result in a reboot notification. Sending of the reboot notification should definitely be moved inside the upgrading guard. The correct fix is likely to move it inside a version comparison guard for particular important updates like Colin suggests below -- this is what every other standard package using notify-reboot-required does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+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 1388011] [NEW] package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Public bug reported: since updating linux image 1.13.0-24 ,updating is no longer possible without problems about configuring.I dont no wat i need to do ,i'm not a computer nerd just a computer user. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-38-generic 3.13.0-38.65 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Oct 31 10:23:20 2014 DuplicateSignature: package:linux-image-3.13.0-38-generic:3.13.0-38.65:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2014-05-21 (162 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=/dev/sda1 ro quiet splash security=selinux selinux=1 vt.handoff=7 SourcePackage: initramfs-tools Title: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2006 dmi.bios.vendor: Acer dmi.bios.version: V2.90 dmi.board.name: Grapevine dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV2.90:bd09/20/2006:svnAcer:pnTravelMate2490:pvrV2.90:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 2490 dmi.product.version: V2.90 dmi.sys.vendor: Acer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-from-proposed trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1388011 Title: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in “initramfs-tools” package in Ubuntu: New Bug description: since updating linux image 1.13.0-24 ,updating is no longer possible without problems about configuring.I dont no wat i need to do ,i'm not a computer nerd just a computer user. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-38-generic 3.13.0-38.65 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Oct 31 10:23:20 2014 DuplicateSignature: package:linux-image-3.13.0-38-generic:3.13.0-38.65:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2014-05-21 (162 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=/dev/sda1 ro quiet splash security=selinux selinux=1 vt.handoff=7 SourcePackage: initramfs-tools Title: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2006 dmi.bios.vendor: Acer dmi.bios.version: V2.90 dmi.board.name: Grapevine dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV2.90:bd09/20/2006:svnAcer:pnTravelMate2490:pvrV2.90:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 2490 dmi.product.version: V2.90 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388011/+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 1388011] Re: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1388011 Title: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in “initramfs-tools” package in Ubuntu: New Bug description: since updating linux image 1.13.0-24 ,updating is no longer possible without problems about configuring.I dont no wat i need to do ,i'm not a computer nerd just a computer user. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-38-generic 3.13.0-38.65 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Oct 31 10:23:20 2014 DuplicateSignature: package:linux-image-3.13.0-38-generic:3.13.0-38.65:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2014-05-21 (162 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=/dev/sda1 ro quiet splash security=selinux selinux=1 vt.handoff=7 SourcePackage: initramfs-tools Title: package linux-image-3.13.0-38-generic 3.13.0-38.65 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2006 dmi.bios.vendor: Acer dmi.bios.version: V2.90 dmi.board.name: Grapevine dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV2.90:bd09/20/2006:svnAcer:pnTravelMate2490:pvrV2.90:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 2490 dmi.product.version: V2.90 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388011/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Problem still happening for me in Ubuntu 14.10 Utopic Unicorn. Worse: while in Trusty I could avoid it by disabling the Google Calendar integration, it seems that it now reactivates by itself. -- 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/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Status in “account-plugins” source package in Trusty: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Status in “signon-plugin-oauth2” source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1388019] [NEW] unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
Public bug reported: On mako 117 (= krillin 139) ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash armhf local-libs utopic -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1388019] Re: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
** Tags removed: need-armhf-retrace -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1386653] [NEW] Scopes fail to launch when the network stack is not up
On Friday, October 31, 2014, Olli Ries <1386...@bugs.launchpad.net> wrote: > while I have been able to reproduce this issue reliably on images up to > #135 I am not able to reproduce anymore on #139 Same here on krillin, can't reproduce on r139. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1386653 Title: [TOPBLOCKER] Scopes fail to launch when the network stack is not up Status in “unity-scope-click” package in Ubuntu: Confirmed Status in “unity-scope-scopes” package in Ubuntu: Confirmed Status in “unity-scopes-api” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: I've seen this randomly from time to time on every other boot, but it happens reliably when flight mode is enabled Steps to reproduce: - Enable flight mode - Reboot Expected result: - Scopes launch and fail network requests Actual: - Black scope screen Notes: - Launcher items work and launch fine - Indicators work fine In the logs I see something like: unity8: Pre-populating scope "unity-scope-nearby" Pre-populating scope "com.canonical.scopes.photos_photos" file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:77:1: QM L Label: Binding loop detected for property "height" file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool invalidateScopeResults: no such scope ' "musicaggregator" ' invalidateScopeResults: no such scope ' "mediascanner-music" ' invalidateScopeResults: no such scope ' "videoaggregator" ' invalidateScopeResults: no such scope ' "mediascanner-video" ' scope-registry: ... RegistryObject::ScopeProcess::on_process_death(): Process for scope: "clickscope" exited ... current build number: 129 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-26 15:25:59 version version: 129 version ubuntu: 20141026 version device: 20141015-32e0f27 version custom: 1413941794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1386653/+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 1388019] Re: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
** Description changed: On mako 117 (= krillin 139) + + https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: - ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 - ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 - ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 - ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 - core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 + ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 + ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 + ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 + ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 + core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1330037] Re: [FFe] upower 0.99.1 transition
** Changed in: gnome-session (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: Fix Committed Status in “cinnamon-session” package in Ubuntu: Fix Released Status in “cinnamon-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Committed Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-shell” package in Ubuntu: Fix Committed Status in “gnome-shell-pomodoro” package in Ubuntu: Fix Committed Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Committed Status in “mate-power-manager” package in Ubuntu: Fix Committed Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: Fix Committed Status in “powerd” package in Ubuntu: In Progress Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Fix Committed Status in “unity-settings-daemon” package in Ubuntu: Fix Committed Status in “upower” package in Ubuntu: Fix Committed Status in “wmbattery” package in Ubuntu: Fix Committed Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: Fix Committed Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1330037] Re: [FFe] upower 0.99.1 transition
** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: Fix Committed Status in “cinnamon-session” package in Ubuntu: Fix Released Status in “cinnamon-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Committed Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-shell” package in Ubuntu: Fix Committed Status in “gnome-shell-pomodoro” package in Ubuntu: Fix Committed Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Committed Status in “mate-power-manager” package in Ubuntu: Fix Committed Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: Fix Committed Status in “powerd” package in Ubuntu: In Progress Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Fix Committed Status in “unity-settings-daemon” package in Ubuntu: Fix Committed Status in “upower” package in Ubuntu: Fix Committed Status in “wmbattery” package in Ubuntu: Fix Committed Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: Fix Committed Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1330037] Re: [FFe] upower 0.99.1 transition
gnome-settings-daemon committed/uploaded as well, which drops the "revert to 3.10 upower" patch. To complete the transition, we now need to land these two MPs: https://code.launchpad.net/~pitti/powerd/upower0.99/+merge/240141 https://code.launchpad.net/~laney/ubuntu-system-settings/upower0.99/+merge/230988 Everything else should be ready in -proposed now. ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-settings-daemon (Ubuntu) Assignee: Tim (darkxst) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: Fix Committed Status in “cinnamon-session” package in Ubuntu: Fix Released Status in “cinnamon-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Committed Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-shell” package in Ubuntu: Fix Committed Status in “gnome-shell-pomodoro” package in Ubuntu: Fix Committed Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Committed Status in “mate-power-manager” package in Ubuntu: Fix Committed Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: Fix Committed Status in “powerd” package in Ubuntu: In Progress Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Fix Committed Status in “unity-settings-daemon” package in Ubuntu: Fix Committed Status in “upower” package in Ubuntu: Fix Committed Status in “wmbattery” package in Ubuntu: Fix Committed Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: Fix Committed Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/13
[Touch-packages] [Bug 1376331] Re: Current package is not thread-safe
** Branch linked: lp:debian/fribidi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fribidi in Ubuntu. https://bugs.launchpad.net/bugs/1376331 Title: Current package is not thread-safe Status in “fribidi” package in Ubuntu: New Bug description: The current fribidi release (fribidi-0.19.6) is not thread-safe unless configured with `--enable-malloc`. This can cause crashes when using fribidi in multiple libraries concurrently. This option is removed, and thread-safe allocation enabled by default, in this commit: http://cgit.freedesktop.org/fribidi/fribidi/commit/?id=54b4496e9c2368c53f1cff57347c1f395328a142 The maintainer has not yet produced a release containing this change, so for now, package maintainers should either switch to a git version or pass the `--enable-malloc` switch at configure-time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fribidi/+bug/1376331/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
If the graphics driver is the problem, would it be possible/sensible to downgrade it to whatever version we had und 14.04? Does anyone know how to do this? -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1388019] Re: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
** Tags removed: local-libs ** Tags added: need-armhf-retrace -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1388019] Re: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
** Tags removed: need-armhf-retrace -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1386653] Re: [TOPBLOCKER] Scopes fail to launch when the network stack is not up
I've tried rebooting my krillin on image 139 with airplane mode turned on around 30 times this morning, and haven't seen this happen a single time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1386653 Title: [TOPBLOCKER] Scopes fail to launch when the network stack is not up Status in “unity-scope-click” package in Ubuntu: Confirmed Status in “unity-scope-scopes” package in Ubuntu: Confirmed Status in “unity-scopes-api” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: I've seen this randomly from time to time on every other boot, but it happens reliably when flight mode is enabled Steps to reproduce: - Enable flight mode - Reboot Expected result: - Scopes launch and fail network requests Actual: - Black scope screen Notes: - Launcher items work and launch fine - Indicators work fine In the logs I see something like: unity8: Pre-populating scope "unity-scope-nearby" Pre-populating scope "com.canonical.scopes.photos_photos" file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:77:1: QM L Label: Binding loop detected for property "height" file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool invalidateScopeResults: no such scope ' "musicaggregator" ' invalidateScopeResults: no such scope ' "mediascanner-music" ' invalidateScopeResults: no such scope ' "videoaggregator" ' invalidateScopeResults: no such scope ' "mediascanner-video" ' scope-registry: ... RegistryObject::ScopeProcess::on_process_death(): Process for scope: "clickscope" exited ... current build number: 129 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-26 15:25:59 version version: 129 version ubuntu: 20141026 version device: 20141015-32e0f27 version custom: 1413941794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1386653/+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 1385630] Re: systemd 215 hangs in fsck
Oh, so you can't even switch between other consoles? Or is the debug console not working for you for some reason? I. e. when you press Alt+F2, F3, etc., do you see any change at all? Does SysRq still work, e. g. SysRQ+s (sync), then SysRQ+u (unmount), then SysRQ+b (reboot). If not even that works, then the kernel itself crashed. Did you ever encounter this without "quiet" and "splash"? With more debug information I'm afraid I have nothing in my hands to see where the problem is. My system also boots rather fast (quad-core i5, very fast (500 MB/s) SSD), but I've never seen such a hard lock-up. ** Summary changed: - systemd 215 hangs in fsck + systemd 215 hangs during boot -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+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 1382567] Re: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADD
This is really a bug in the events scope, please see this hanloon bug: https://bugs.launchpad.net/hanloon/+bug/1388035 ** Changed in: savilerow Importance: Undecided => Critical ** Changed in: savilerow Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1382567 Title: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADDR *** Status in The Savilerow project: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-scopes-api. This problem was most recently seen with version 0.6.7+14.10.20141010.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/69d0dabacb1ee1cc5be6fba75784a0751c80617d contains more details. Steps to reproduce: 1. Swipe up from bottom of screen and select dashboard 2. Swipe up from bottom of screen and select apps expected result: no crash actual result: crash To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1382567/+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 1354519] Re: [dash] [design] When searching in a scope, loading feedback is hidden by the keyboard
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- 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/1354519 Title: [dash] [design] When searching in a scope, loading feedback is hidden by the keyboard Status in Ubuntu UX bugs: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Go to the music lens in the dash 2. Tap on the search button and start typing Expected result: Some visual feedback is displayed showing that it is loading/fetching content Current result: No visual feedback is displayed This is the result of the fix for https://bugs.launchpad.net/unity8/+bug/1351539 where a loading bar has been added at the bottom of the screen. However the keyboard is on top of it. I suggest doing what Mike Nagle (mikenagle) wrote on 2014-07-21 in https://bugs.launchpad.net/unity8/+bug/1285731: "Scope should display an activity indicator just under the divider. However, we need a thin, horizontal one that isn't the spinner." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1354519/+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 1382621] Re: [sim pin] prompt on boot but after greeter
** Summary changed: - sim pin prompt on boot but after greeter + [sim pin] prompt on boot but after greeter -- 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/1382621 Title: [sim pin] prompt on boot but after greeter Status in Ubuntu UX bugs: Triaged Status in “indicator-network” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Per this bug 1382604 it was discussed that the sim pin prompt is occuring before the greeter on boot, and doesn't seem to match the spec per this bug 1333121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382621/+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 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
I also have this problem. After this error my wi-fi disconnected and can not connect for a long time. Please, fix this bug quickly. tail -f /var/log/syslog Oct 31 16:27:26 ASUS NetworkManager[821]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted serj@ASUS:~$ uname -a Linux ASUS 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lspci | grep -i network 04:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe -- 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/1118446 Title: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted Status in “network-manager” package in Ubuntu: Triaged Bug description: I see the following messages in /var/log/syslog: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted When it goes down, I have to bounce network-manager to resolve it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 08:59:00 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-26 (12 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.11 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca 802-11-wireless 1360249035 Thu 07 Feb 2013 08:57:15 AM CSTyes no /org/freedesktop/NetworkManager/Settings/2 Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12 802-11-wireless 1359750784 Fri 01 Feb 2013 02:33:04 PM CSTyes no /org/freedesktop/NetworkManager/Settings/1 MIA-WiFi ea25a58d-9cb8-48a8-843a-2dc3231a1e17 802-11-wireless 1359754973 Fri 01 Feb 2013 03:42:53 PM CSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1118446/+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 1388045] [NEW] system running in low graphic mode
Public bug reported: the bug was previously reported by many.i have tried everything from reinstalling ubuntu desktop installing gdm nothing is working. i have ubuntu 14.04 and intel integrated graphic card. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Oct 31 13:34:36 2014 DistUpgraded: 2014-10-28 20:59:15,991 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2ab4] InstallationDate: Installed on 2014-03-18 (226 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) LightdmGreeterLog: Failed to open PAM session: Error in service module LightdmGreeterLogOld: Failed to open PAM session: Error in service module MachineType: Hewlett-Packard CQ3540IX ProcEnviron: LANGUAGE=en_IN:en TERM=linux PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=e6d34c60-c872-49e2-a1fe-33a65bdb06f1 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-10-28 (2 days ago) dmi.bios.date: 11/29/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB4 dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: INA110WD99 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd11/29/2010:svnHewlett-Packard:pnCQ3540IX:pvrxxx0204GR0:rvnMSI:rn2AB4:rvr2.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: CQ3540IX dmi.product.version: xxx0204GR0 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20141023.065256df-0ubuntu0ricotz~trusty version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141016.6b98f162-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty xserver.bootTime: Fri Oct 31 12:18:30 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputNOVATEK USB Keyboard KEYBOARD, id 8 inputNOVATEK USB Keyboard KEYBOARD, id 9 inputUSB Optical MouseMOUSE, id 10 xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does not exist, 0) Server terminated successfully (0). Closing log file. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1388045 Title: system running in low graphic mode Status in “xorg” package in Ubuntu: New Bug description: the bug was previously reported by many.i have tried everything from reinstalling ubuntu desktop installing gdm nothing is working. i have ubuntu 14.04 and intel integrated graphic card. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Oct 31 13:34:36 2014 DistUpgraded: 2014-10-28 20:59:15,991 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2ab4] InstallationDate: Installed on 2014-03-18 (226 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Sa
[Touch-packages] [Bug 1387948] Re: Enabling flight mode does not refresh scopes
There's two bits here, the "no feedback on no network" which we designed how to handle, just never managed to implement (a full overlay when no results, just a hint at the top when there could be more results). Since the scope+machinery should tell us when the reason for that is no network, we could indeed invalidate those when network comes on. ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- 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/1387948 Title: Enabling flight mode does not refresh scopes Status in “unity-scopes-shell” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: Reboot the phone while in flight mode, with some aggregators favourited (such as Music, Video, and YouTube). After reboot, swiping to any of the aggregators displays an empty screen. That's as expected, seeing that the network is not available. It would be nice though to have some indication as to *why* nothing is shown. Now enable flight mode again and swipe to any of the three blank scopes. They are still blank, and I have to do a manual refresh to get them to work again. It might be nice to check whether the network has been up and down since last time a scope was seen by the user and, if so and there are either no results, or results that are too old, do a refresh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1387948/+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 244250] Re: Spurious reboot notifications caused by libssl upgrades.
@khaled-blah: yes, on a server, it should do the usual and add a reboot required blurb to the motd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/244250 Title: Spurious reboot notifications caused by libssl upgrades. Status in “openssl” package in Ubuntu: Fix Released Bug description: The postinst script for libssl0.9.8 currently has a bug where it sends a reboot notifcation whenever libssl is configured. So reconfiguring libssl0.9.8 or even just installing libssl0.9.8 will result in a reboot notification. Sending of the reboot notification should definitely be moved inside the upgrading guard. The correct fix is likely to move it inside a version comparison guard for particular important updates like Colin suggests below -- this is what every other standard package using notify-reboot-required does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+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 1376331] Re: Current package is not thread-safe
** Branch linked: lp:ubuntu/vivid-proposed/fribidi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fribidi in Ubuntu. https://bugs.launchpad.net/bugs/1376331 Title: Current package is not thread-safe Status in “fribidi” package in Ubuntu: New Bug description: The current fribidi release (fribidi-0.19.6) is not thread-safe unless configured with `--enable-malloc`. This can cause crashes when using fribidi in multiple libraries concurrently. This option is removed, and thread-safe allocation enabled by default, in this commit: http://cgit.freedesktop.org/fribidi/fribidi/commit/?id=54b4496e9c2368c53f1cff57347c1f395328a142 The maintainer has not yet produced a release containing this change, so for now, package maintainers should either switch to a git version or pass the `--enable-malloc` switch at configure-time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fribidi/+bug/1376331/+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 1388052] [NEW] OptionSelector in dialog has inconsistent borders
Public bug reported: Ubuntu 14.10 r135 1. Go to System Settings > "Wi-Fi". 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose "Connect to hidden network". 4. Look at the "Security" menu. What you see: The menu has a border along most of its bottom, but not all, and not the other three sides. What you should see: The menu has a consistent border. To be consistent with text fields, probably its corners should be rounded as well. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot with the problem highlighted" https://bugs.launchpad.net/bugs/1388052/+attachment/4249957/+files/OptionSelector%20border.png -- 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/1388052 Title: OptionSelector in dialog has inconsistent borders Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Ubuntu 14.10 r135 1. Go to System Settings > "Wi-Fi". 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose "Connect to hidden network". 4. Look at the "Security" menu. What you see: The menu has a border along most of its bottom, but not all, and not the other three sides. What you should see: The menu has a consistent border. To be consistent with text fields, probably its corners should be rounded as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388052/+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 1386803] Re: [TOPBLOCKER] unity8 crashing a lot since image #126
** Also affects: qtubuntu-media (Ubuntu) Importance: Undecided Status: New ** Changed in: qtubuntu-media (Ubuntu) Status: New => In Progress ** Changed in: qtubuntu-media (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: dbus-cpp (Ubuntu) Status: In Progress => Fix Released -- 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/1386803 Title: [TOPBLOCKER] unity8 crashing a lot since image #126 Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Opinion Status in “media-hub” package in Ubuntu RTM: Fix Released Bug description: Since RTM image #126 was released on friday, most users have been reporting frequent unity8 crashes. Some scenarios where this commonly happen appear to be: - Unlocking SIM cards for the first time - Tapping on snap notifications when receiving an SMS A lot of crashes are also observed during automated image testing. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Oct 28 17:20:40 2014 InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141028-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1386803/+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 1387544] Re: Sync pangox-compat 0.0.2-5 (main) from Debian unstable (main)
This bug was fixed in the package pangox-compat - 0.0.2-5 Sponsored for Artur Rona (ari-tczew) --- pangox-compat (0.0.2-5) unstable; urgency=medium * Use dh-autoreconf during build to support newer architectures. Closes: #755909 -- Michael Biebl Tue, 02 Sep 2014 12:37:51 +0200 ** Changed in: pangox-compat (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pangox-compat in Ubuntu. https://bugs.launchpad.net/bugs/1387544 Title: Sync pangox-compat 0.0.2-5 (main) from Debian unstable (main) Status in “pangox-compat” package in Ubuntu: Fix Released Bug description: Please sync pangox-compat 0.0.2-5 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Build using dh-autoreconf. * Build using dh-autoreconf. * Build using dh-autoreconf. Debian has merged Ubuntu changes. Changelog entries since current vivid version 0.0.2-4ubuntu1: pangox-compat (0.0.2-5) unstable; urgency=medium * Use dh-autoreconf during build to support newer architectures. Closes: #755909 -- Michael Biebl Tue, 02 Sep 2014 12:37:51 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pangox-compat/+bug/1387544/+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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
Using RTM silo 16 this is fixed. -- 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/1386109 Title: com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1388019] Re: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()
*** This bug is a duplicate of bug 1386803 *** https://bugs.launchpad.net/bugs/1386803 ** This bug has been marked a duplicate of bug 1386803 [TOPBLOCKER] unity8 crashing a lot since image #126 -- 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/1388019 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() Status in “unity8” package in Ubuntu: New Bug description: On mako 117 (= krillin 139) https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 31 09:40:57 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 141471 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libmedia-hub-client.so.2 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 Title: unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388019/+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 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
The last patch is big and seems to fail quite largely on top of 5.3.0 + the other patches. I haven't tried to look it hard yet to see how much work the rebasing would be, but if in the end we will want that patch to fix this bug, rebasing needs to be done for it too. If interested, I've pushed a branch to https://code.launchpad.net /~kubuntu-packagers/kubuntu-packaging/qtbase-opensource- src_530_networkmanagerfixes now. The first four patches have been rebased to apply, this last one fails as can be tried locally with: apt install bzr-builddeb apt-get build-dep qtbase-opensource-src wget https://launchpad.net/ubuntu/+archive/primary/+files/qtbase-opensource-src_5.3.0%2Bdfsg.orig.tar.xz bzr branch lp:~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src_530_networkmanagerfixes cd qtbase-opensource-src_530_networkmanagerfixes bzr bd Which produces the attached failure to apply. ** Attachment added: "buildlog.txt" https://bugs.launchpad.net/savilerow/+bug/1357321/+attachment/4249958/+files/buildlog.txt -- 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/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1140716]
*** Bug 85609 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [] ? __switch_to+0x12b/0x420 [26285.658612] [] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [] process_one_work+0x12a/0x420 [26285.658629] [] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [] worker_thread+0x12e/0x2f0 [26285.658636] [] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [] kthread+0x93/0xa0 [26285.658644] [] kernel_thread_helper+0x4/0x10 [26285.658649] [] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.384285] [ cut here ] [26932.384354] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26932.384356] Hardware name: SATEL
[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Assignee: (unassigned) => Iain Lane (laney) ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
"Can't publish: Some projects (urfkill) that were in the silo configuration list were not built" I can't confirm. I'm on 14.09-proposed, I did: citrain host-upgrade 16 ubuntu-rtm and I'm getting 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I'm probably doing something wrong. -- 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/1386109 Title: com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
** Changed in: nux Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: Fix Committed Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: Fix Released Bug description: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 compiz: Geïnstalleerd: 1:0.9.12+14.10.20140812-0ubuntu1 Kandidaat: 1:0.9.12+14.10.20140812-0ubuntu1 Versietabel: *** 1:0.9.12+14.10.20140812-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 1 12:30:05 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationDate: Installed on 2014-08-29 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140826) MachineType: ASUSTeK Computer INC. 1001PX ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=nl_NL XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=UUID=e2155ee3-e907-44c0-b6e7-f0608f136055 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0xb0d08ed1 <_ZN3nux16WindowCompositor13DndEventCycleERNS_5EventE+257>: mov(%edx),%ecx PC (0xb0d08ed1) ok source "(%edx)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: nux::WindowCompositor::DndEventCycle(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::DoProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/18/2011:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 1 09:21:40 2014 xserver.configfile: default xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xse
[Touch-packages] [Bug 1387959] Re: unity8 crash in image krillin rtm 139
When you say it's 'crashy' how many crashes did you actually get - just the one? The description doesn't make that clear. -- 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/1387959 Title: unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: New Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 1387959] Re: unity8 crash in image krillin rtm 139
In 3 hours testing this morning I got one crash: http://people.canonical.com/~brendan-donegan/_usr_bin_unity8.32011.crash -- 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/1387959 Title: unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: New Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 1388060] [NEW] Sim pin unlock is crashing unity8
Public bug reported: With the right configuration of sim/sims you can reliablly crash simpin unlock. For Ogra: conngstart (payg) eplus/kpn (contract) For me: T-mobile (contract) Orange (payg) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 31 11:55:53 2014 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- 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/1388060 Title: Sim pin unlock is crashing unity8 Status in “unity8” package in Ubuntu: New Bug description: With the right configuration of sim/sims you can reliablly crash simpin unlock. For Ogra: conngstart (payg) eplus/kpn (contract) For me: T-mobile (contract) Orange (payg) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 31 11:55:53 2014 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388060/+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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
Old school me just added deb http://ppa.launchpad.net/ci-train-ppa-service/landing-016/ubuntu-rtm 14.09 main deb-src http://ppa.launchpad.net/ci-train-ppa-service/landing-016/ubuntu-rtm 14.09 main to apt sources and update+dist-upgrade -- 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/1386109 Title: com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1376331] Re: Current package is not thread-safe
This bug was fixed in the package fribidi - 0.19.6-3 --- fribidi (0.19.6-3) unstable; urgency=medium * debian/control: Bumped Standards-Version to 3.9.6 * debian/copyright: Switched to machine readable format. * Pass --enable-malloc to configure to avoid crashes when using fribidi in multiple libraries concurrently. (LP: #1376331) * Update my email address. -- أحمد المحمودي (Ahmed El-Mahmoudy) Fri, 31 Oct 2014 08:30:53 +0200 ** Changed in: fribidi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fribidi in Ubuntu. https://bugs.launchpad.net/bugs/1376331 Title: Current package is not thread-safe Status in “fribidi” package in Ubuntu: Fix Released Bug description: The current fribidi release (fribidi-0.19.6) is not thread-safe unless configured with `--enable-malloc`. This can cause crashes when using fribidi in multiple libraries concurrently. This option is removed, and thread-safe allocation enabled by default, in this commit: http://cgit.freedesktop.org/fribidi/fribidi/commit/?id=54b4496e9c2368c53f1cff57347c1f395328a142 The maintainer has not yet produced a release containing this change, so for now, package maintainers should either switch to a git version or pass the `--enable-malloc` switch at configure-time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fribidi/+bug/1376331/+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 1029289] Re: Need to authorize my google account each time I boot the computer
On 10/31/2014 11:49 AM, Brice Terzaghi wrote: > Problem still happening for me in Ubuntu 14.10 Utopic Unicorn. Worse: > while in Trusty I could avoid it by disabling the Google Calendar > integration, it seems that it now reactivates by itself. You mean that you disable the Google Calendar, and then when you reopen the Online Accounts panel you find it enabled again? If so, does it happen immediately, or when? -- 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/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Status in “account-plugins” source package in Trusty: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Status in “signon-plugin-oauth2” source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
> citrain host-upgrade 16 ubuntu-rtm This should be $ citrain device-upgrade 16 I imagine. -- 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/1386109 Title: com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1388060] Re: Sim pin unlock is crashing unity8
*** This bug is a duplicate of bug 1386803 *** https://bugs.launchpad.net/bugs/1386803 ** This bug has been marked a duplicate of bug 1386803 [TOPBLOCKER] unity8 crashing a lot since image #126 -- 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/1388060 Title: Sim pin unlock is crashing unity8 Status in “unity8” package in Ubuntu: New Bug description: With the right configuration of sim/sims you can reliablly crash simpin unlock. For Ogra: conngstart (payg) eplus/kpn (contract) For me: T-mobile (contract) Orange (payg) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 31 11:55:53 2014 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388060/+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 1387949] Re: power cycling BT device caused phone to reboot
Is this headset new? You might have hit an interop issue - if there was no crash it was probably a kernel panic or something like that. I've tried disconnecting and reconnecting a number of time with my headset and there are no issues. ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling BT device caused phone to reboot Status in “indicator-bluetooth” package in Ubuntu: Incomplete Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1387949/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot
It's worth noting no restart is required - with the latest images I can go into flight mode and back to activate swapped SIM cards without a restart. -- 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/1332306 Title: Hot-swapped SIMs should be detected and prompt user to reboot Status in Ubuntu UX bugs: Fix Committed Status in “indicator-network” package in Ubuntu: Triaged Status in “ofono” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Incomplete Bug description: Our telephony stack doesn't support hot-swapping of SIM cards. If a user hot-swaps a SIM, the telephony stack will become unusable. The telephony-service should detect when this happens and display a snap-decision informing the user that they need to restart their device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1332306/+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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
$ citrain device-upgrade 16 ubuntu-rtm Correct, thank you Saviq. It was sitting really long on phablet-writable-image, so I ended-up going Albert's route. I confirm the problem is solved in silo 16. -- 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/1386109 Title: com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1388068] [NEW] sysctl.conf is not loaded by 'sysctl --system'
Public bug reported: As described in the sysctl man page, /etc/sysctl.conf should be loaded by running 'sysctl --system': --system Load settings from all system configuration files. /run/sysctl.d/*.conf /etc/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf This patch seems to have broken that, by loading it only in the case of an *error* from stat() on /etc/sysctl.conf, rather than success. http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/procps/trusty/revision/77/.pc/ignore_eaccess.patch/sysctl.c See the new line 643 in that patch. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1388068 Title: sysctl.conf is not loaded by 'sysctl --system' Status in “procps” package in Ubuntu: New Bug description: As described in the sysctl man page, /etc/sysctl.conf should be loaded by running 'sysctl --system': --system Load settings from all system configuration files. /run/sysctl.d/*.conf /etc/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf This patch seems to have broken that, by loading it only in the case of an *error* from stat() on /etc/sysctl.conf, rather than success. http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/procps/trusty/revision/77/.pc/ignore_eaccess.patch/sysctl.c See the new line 643 in that patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1388068/+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 1387959] Re: unity8 crash in image krillin rtm 139
Yours, Brendan, is unknown as of yet, it's in errors as https://errors.ubuntu.com/oops/ac6af12e-60fa-11e4-940c-fa163e22e467 and https://errors.ubuntu.com/oops/e8b1c5f4-60e1-11e4-9f52-fa163e525ba7. -- 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/1387959 Title: unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: New Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 1388060] Re: Sim pin unlock is crashing unity8
*** This bug is a duplicate of bug 1386803 *** https://bugs.launchpad.net/bugs/1386803 ** Also affects: qtubuntu-media Importance: Undecided Status: New -- 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/1388060 Title: Sim pin unlock is crashing unity8 Status in QT Ubuntu Media: New Status in “unity8” package in Ubuntu: New Bug description: With the right configuration of sim/sims you can reliablly crash simpin unlock. For Ogra: conngstart (payg) eplus/kpn (contract) For me: T-mobile (contract) Orange (payg) ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 31 11:55:53 2014 InstallationDate: Installed on 2014-10-31 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-022521) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu-media/+bug/1388060/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot
> It's worth noting no restart is required - with the latest images I can > go into flight mode and back to activate swapped SIM cards without a > restart. This was working on krillin for a long time (like... always?). Not so on mako, though - is it working for you on mako? -- 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/1332306 Title: Hot-swapped SIMs should be detected and prompt user to reboot Status in Ubuntu UX bugs: Fix Committed Status in “indicator-network” package in Ubuntu: Triaged Status in “ofono” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Incomplete Bug description: Our telephony stack doesn't support hot-swapping of SIM cards. If a user hot-swaps a SIM, the telephony stack will become unusable. The telephony-service should detect when this happens and display a snap-decision informing the user that they need to restart their device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1332306/+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 1383702] Re: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue
The unity8 side of this got released to vivid: unity8 (8.01+15.04.20141030-0ubuntu1 [ Michael Terry ] * Provide 'passphrase' as a field of Components.Lockscreen * Fix a race between Qml loading and DBus registration that caused problems when jenkins tried to unlock the phone. * Set domain explicitly for the Dialogs component because the welcome wizard wants to import it. (LP: #1381731) * When greeter or lockscreen has focus, show active call panel. (LP: #1378872) ... ** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Released -- 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/1383702 Title: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue Status in Ubuntu Touch System Settings: New Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1383702/+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 706011] Re: gpg --key-gen doesn't have enough entropy and rng-tools install/start fails
I have this issue when generating GPG keys on a remote server. It seems like generating GPG keys on remote web servers is a relatively common use case, and might deserve another look by the GPG developers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/706011 Title: gpg --key-gen doesn't have enough entropy and rng-tools install/start fails Status in “gnupg” package in Ubuntu: Confirmed Bug description: Binary package hint: gnupg Description: Ubuntu 10.04.1 LTS Release: 10.04 If you install gpg and then type: gpg --gen-key, it 'freezes up' during the entropy gathering phase. We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! (Need 278 more bytes) (freeze here) I found some reference on the interwebs suggesting to install rng- tools so that the rngd daemon can gather more entropy for the system because by default cat /proc/sys/kernel/random/entropy_avail has a very very low number. Thus, installation of rng-tools, fails to start the rngd daemon... Setting up rng-tools (2-unofficial-mt.12-1ubuntu3) ... Trying to create /dev/hwrng device inode... Starting Hardware RNG entropy gatherer daemon: (failed). invoke-rc.d: initscript rng-tools, action "start" failed. It is then required to do this: echo "HRNGDEVICE=/dev/urandom" >> /etc/default/rng-tools and then start rngd: /etc/init.d/rng-tools start After this process is done, gpg --gen-key is immediate... We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. .+ ...+ We need to generate a lot of random bytes. It is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. + .+ And cat /proc/sys/kernel/random/entropy_avail has a much higher number. All in all, I think this process should be simplified by maybe making gpg depend on rng-tools. The whole reason why I need to generate a gpg key is because I want to sign the .deb debians that I'm creating for my repository. Thanks for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/706011/+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 1383702] Re: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue
And in rtm ** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- 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/1383702 Title: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue Status in Ubuntu Touch System Settings: New Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1383702/+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 1386803] Re: [TOPBLOCKER] unity8 crashing a lot since image #126
** Changed in: qtubuntu-media (Ubuntu) Importance: Undecided => Critical ** Branch linked: lp:~thomas-voss/qtubuntu-media/disconnect-from- playback-status-changed-signal-on-destruction -- 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/1386803 Title: [TOPBLOCKER] unity8 crashing a lot since image #126 Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Opinion Status in “media-hub” package in Ubuntu RTM: Fix Released Bug description: Since RTM image #126 was released on friday, most users have been reporting frequent unity8 crashes. Some scenarios where this commonly happen appear to be: - Unlocking SIM cards for the first time - Tapping on snap notifications when receiving an SMS A lot of crashes are also observed during automated image testing. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Oct 28 17:20:40 2014 InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141028-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1386803/+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 1387090] Re: boot breaks if /etc/machine-id is missing
** Tags added: systemd-boot -- 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/1387090 Title: boot breaks if /etc/machine-id is missing Status in “systemd” package in Ubuntu: Triaged Bug description: When no /etc/machine-id file is present the boot breaks. Once this bug is fixed we can modify live-build so that it remove /etc /machine-id from the generated live rootfs instead of truncating it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387090/+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 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser
might be related to https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1388065 -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Status in DBus C++: In Progress Status in “dbus-cpp” package in Ubuntu: In Progress Status in “indicator-network” package in Ubuntu: In Progress Status in “location-service” package in Ubuntu: In Progress Status in “dbus-cpp” package in Ubuntu RTM: In Progress Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot
I mentioned this as flight mode was broken for me for a long time :-) and I was wondering if the bug intentionally talks about reboot even though it doesn't seem to be necessary. I'll update the title then. ** Summary changed: - Hot-swapped SIMs should be detected and prompt user to reboot + Hot-swapped SIMs should be detected and reconnect -- 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/1332306 Title: Hot-swapped SIMs should be detected and reconnect Status in Ubuntu UX bugs: Fix Committed Status in “indicator-network” package in Ubuntu: Triaged Status in “ofono” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Incomplete Bug description: Our telephony stack doesn't support hot-swapping of SIM cards. If a user hot-swaps a SIM, the telephony stack will become unusable. The telephony-service should detect when this happens and display a snap-decision informing the user that they need to restart their device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1332306/+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 1387643] Re: Pruning of probably stale sessions should be less aggressive
** Tags added: ota-1 rtm14 -- 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/1387643 Title: Pruning of probably stale sessions should be less aggressive Status in “location-service” package in Ubuntu: Confirmed Bug description: Right now, after 10 non-successful attempts to deliver location updates to clients, the service considers the client to be hanging or dead and prunes the session from the service's cache. With that, if the app wakes up again, it does not receive updates for the same session anymore. A restart of the app fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1387643/+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 1388082] [NEW] package libnih1 1.0.3-4ubuntu25 failed to install/upgrade: no package named `libnih1' is installed, cannot configure
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnih1 1.0.3-4ubuntu25 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Oct 31 13:19:44 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.3 DuplicateSignature: package:libnih1:1.0.3-4ubuntu25:no package named `libnih1' is installed, cannot configure ErrorMessage: no package named `libnih1' is installed, cannot configure InstallationDate: Installed on 2013-02-18 (620 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: libnih Title: package libnih1 1.0.3-4ubuntu25 failed to install/upgrade: no package named `libnih1' is installed, cannot configure UpgradeStatus: Upgraded to trusty on 2014-10-31 (0 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1388082 Title: package libnih1 1.0.3-4ubuntu25 failed to install/upgrade: no package named `libnih1' is installed, cannot configure Status in “libnih” package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnih1 1.0.3-4ubuntu25 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Oct 31 13:19:44 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.3 DuplicateSignature: package:libnih1:1.0.3-4ubuntu25:no package named `libnih1' is installed, cannot configure ErrorMessage: no package named `libnih1' is installed, cannot configure InstallationDate: Installed on 2013-02-18 (620 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: libnih Title: package libnih1 1.0.3-4ubuntu25 failed to install/upgrade: no package named `libnih1' is installed, cannot configure UpgradeStatus: Upgraded to trusty on 2014-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1388082/+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 1378438] Re: Printer dialog stuck on "Getting printer information..."
Comment #7 is only valid if you get links created in /tmp. You have to both remove the executable bit from scp-dbus-service.py and kill the scp-dbus-service.py process in this case. If this is the case for you, does printing return to work normally after applying the workaround? The original description tells that printing works from Firefox and does not work from applications with GTK3 Print dialog. This looks like that something is wrong with the print dialog, as CUPS is able to print but the GTK3 print dialog does not give access to the printer. So please try to print from LibreOffice and/or from KDE applications (Okular, Digikam, ...). Can you print from these applications? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1378438 Title: Printer dialog stuck on "Getting printer information..." Status in “cups” package in Ubuntu: Confirmed Bug description: In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered printer, the "Status" field changes to "Getting printer information..." and the mouse cursor goes into spinning icon, and the Print button stays disabled, so I cannot print. In Firefox, the status tells me the printer is low on toner, but allows me to print. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cups 1.7.5-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CupsErrorLog: E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address - Permission denied E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address - Permission denied CurrentDesktop: GNOME Date: Tue Oct 7 09:29:43 2014 InstallationDate: Installed on 2014-02-24 (224 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro11,3 Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B02.1310181745 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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 1383702] Re: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue
** Changed in: ubuntu-system-settings (Ubuntu) Importance: Critical => High -- 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/1383702 Title: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue Status in Ubuntu Touch System Settings: New Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1383702/+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 1378218] Re: Calling back from notification center opens an emergency-mode dialer
This got synced to RTM with unity8. ** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Fix Released -- 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/1378218 Title: Calling back from notification center opens an emergency-mode dialer Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: This is extracted out of bug #1367916: Steps to reproduce: 1) make sure you have a passcode lock setup on phone 2) make sure you have indicator allows to show on lock screen (default) 3) lock the phone 4) call the phone and hang up before answering it, then wait till phone turns off after 1 minute 5) turn on screen but don't unlock 6) pull down the messaging menu, and click on the Missed Call to expand it, then tap in right corner to launch the app Expected Results: The passcode unlock screen should be shown Actual Results: The dialer gets launched in step 6 and is visible but it's in Emergency calling mode (because the phone is locked) so the call can't be made. The correct thing to do in both cases is to display the passcode unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141006-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Tue Oct 7 09:39:25 2014 InstallationDate: Installed on 2014-10-07 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141007-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378218/+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 1301125] Re: Lock screen after idle time freezes unity
Update: Previously mentioned "workaround" (comment #13) is not working. It probably worked a few times by accident. I have lately seen just as many freezes with manual locking as with timeout locking. I have started to disable and avoid screen locking as much as possible, but that is of course not a good security strategy. My graphics card is Sapphire Radeon HD 6850, open source (default) drivers. -- 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/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.
[Touch-packages] [Bug 1258753] Re: package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1258753 Title: package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 Status in “bluez” package in Ubuntu: Confirmed Bug description: Can't manage a2dp profile to work. Using xubuntu 13.10 connected to an external bluetooth speaker. I can add it with blueman but can't send audio stream. It worked with xubutu 12.04.3 . ProblemType: Package DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 7 11:58:56 2013 DuplicateSignature: package:bluez:4.101-0ubuntu8b1:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-12-06 (0 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) InterestingModules: rfcomm btusb bluetooth MachineType: ASUSTeK Computer Inc. U36SG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=1728c978-09d7-49eb-835d-8030ded608e5 ro quiet splash i915.i915_enable_rc6=1 SourcePackage: bluez Title: package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SG.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SG dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SG.202:bd10/19/2011:svnASUSTeKComputerInc.:pnU36SG:pvr1.0:rvnASUSTeKComputerInc.:rnU36SG:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36SG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 4C:80:93:75:41:4D ACL MTU: 310:10 SCO MTU: 64:8 DOWN RX bytes:484 acl:0 sco:0 events:20 errors:0 TX bytes:323 acl:0 sco:0 commands:20 errors:0 modified.conffile..etc.dbus.1.system.d.bluetooth.conf: [deleted] mtime.conffile..etc.bluetooth.audio.conf: 2013-12-07T11:53:30.463114 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1258753/+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 1388005] Re: ppa-purge
De nouveau, ce n'est pas un bug: donc rien à faire ici. Les developpers ont d'autre préoccupations que de répondre à des utilisateurs qui ne prennent pas la peine de rechercher une solution (google et/ou ubuntu forum). Lorsqu'on sait ajouter des ppa, on doit aussi assumer la responsabilité des disfonctionnements créé, sans venir pleurnicher. sudo apt-get install ppa-purge sudo ppa-purge ppa:nom_du_dépôt ( remplacer 'nom_du_ppa' par le libellé exact evidemment. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1388005 Title: ppa-purge Status in “xorg” package in Ubuntu: Incomplete Bug description: je bonjour je ne parviens pas à intaller ppa-purge ou de le mettre en ligne de commande terminal donc je ne sais pas mettre à jour. Merci pour votre aide Sur le forum je n'ai pas encore eu de solution Cordialement JPDW ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 31 10:22:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a8c] InstallationDate: Installed on 2014-05-10 (174 days ago) InstallationMedia: Cubuntu 14.04 - Release amd64 LightdmGreeterLog: ** (lightdm-gtk-greeter:1656): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1661): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: Compaq-Presario WC690AA-UUG CQ5310BE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2e8ed171-6550-4a46-a4b4-3db56a7eed2d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.09 dmi.board.name: ETON dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.09:bd11/27/2009:svnCompaq-Presario:pnWC690AA-UUGCQ5310BE:pvr:rvnFOXCONN:rnETON:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: WC690AA-UUG CQ5310BE dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Oct 31 08:25:00 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49177 vendor PHL xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388005/+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 1387282] Re: bluetooth.service not started automatically
Hmm, bluez looks fine at first sight. Reassigning this back, apparently the bluetooth.target behaviour changed. ** Package changed: bluez (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Triaged => Confirmed ** Changed in: systemd (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) -- 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/1387282 Title: bluetooth does not work due to firmware load failure Status in “systemd” package in Ubuntu: Confirmed Bug description: I cannot use bluetooth devices while using systemd as the default init system. While going to gnome-control-center to check for bluetooth devices, all the bluetooth functionality is deactivated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 17:43:44 2014 InstallationDate: Installed on 2014-10-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387282/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
After a 14.10 install from scratch (no update) with Gnome Shell on Intel 915 graphics (Lenovo S440), I still have the same issue. Most noticeable is the very slow text editing in gedit. There is no issue when I use Unity, Gnome Classic or Xfce. -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1387282] Re: bluetooth.service not started automatically
So the way this is *supposed* to work is that bluetooth.target is activated by udev rules, like those: 99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_ALIAS}+="/sys/subsystem/bluetooth/devices/%k" 99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_WANTS}+="bluetooth.target" But in my current "udevadm info --export-db" I don't have any device with SUBSYSTEM=bluetooth, and /sys/class/bluetooth/ is empty. In dmesg I see [ 6639.785913] bluetooth hci0: Direct firmware load failed with error -2 [ 6639.785918] bluetooth hci0: Falling back to user helper [ 6639.787431] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not found So this seems to be the reason why even after starting bluetooth.service manually (which was a red herring) there are still no BT devices. Can you please confirm that your problem is the same? I. e. run "dmesg | grep bluetooth", and you get something like above? Thanks! ** Summary changed: - bluetooth.service not started automatically + bluetooth does not work due to firmware load failure -- 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/1387282 Title: bluetooth does not work due to firmware load failure Status in “systemd” package in Ubuntu: Confirmed Bug description: I cannot use bluetooth devices while using systemd as the default init system. While going to gnome-control-center to check for bluetooth devices, all the bluetooth functionality is deactivated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 17:43:44 2014 InstallationDate: Installed on 2014-10-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387282/+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 1387282] Re: Bluetooth is not activated
Indeed, bluetooth.service does not get started by default any more. This used to work, but apparently got broken recently. With a manual "sudo systemctl start bluetooth.service" I get this back. ** Tags added: systemd-boot ** Package changed: systemd (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Summary changed: - Bluetooth is not activated + bluetooth.service not started automatically -- 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/1387282 Title: bluetooth does not work due to firmware load failure Status in “systemd” package in Ubuntu: Confirmed Bug description: I cannot use bluetooth devices while using systemd as the default init system. While going to gnome-control-center to check for bluetooth devices, all the bluetooth functionality is deactivated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 17:43:44 2014 InstallationDate: Installed on 2014-10-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387282/+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 1388089] [NEW] [webapp-container] apps are not handled by lifecycle management properly
Public bug reported: in image 137, if you open a gazillion of apps and have webapps among them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, the whole content window turns white (sometimes the app header stays around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Affects: qtmir (Ubuntu RTM) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu RTM) Importance: Undecided Status: New ** Description changed: in image 137, if you open a gazillion of apps and have webapps among - them, the webapp screenshot never turn blurry when the OOM score is + them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, - the whole content window turns white. + the whole content window turns white (sometimes the app header stays + around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: webbrowser-app (Ubuntu RTM) Importance: Undecided Status: New -- 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/1388089 Title: [webapp-container] apps are not handled by lifecycle management properly Status in “qtmir” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: New Status in “qtmir” package in Ubuntu RTM: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: in image 137, if you open a gazillion of apps and have webapps among them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, the whole content window turns white (sometimes the app header stays around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1388089/+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 1384810] Re: "Next" key is too big for keyboard and doesn't translate well
** Branch linked: lp:~renatofilho/address-book-app/fix-1384810 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1384810 Title: "Next" key is too big for keyboard and doesn't translate well Status in Address Book App: In Progress Status in Ubuntu Keyboard: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “address-book-app” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: In the address book, we replace the enter button with the text "Next" as it automatically navigates you to the next field. A better solution would be to use an icon that represents Next (some kind of forward arrow). To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1384810/+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 1384810] Re: "Next" key is too big for keyboard and doesn't translate well
** Changed in: address-book-app Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1384810 Title: "Next" key is too big for keyboard and doesn't translate well Status in Address Book App: In Progress Status in Ubuntu Keyboard: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “address-book-app” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: In the address book, we replace the enter button with the text "Next" as it automatically navigates you to the next field. A better solution would be to use an icon that represents Next (some kind of forward arrow). To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1384810/+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 1330037] Re: [FFe] upower 0.99.1 transition
** Branch linked: lp:ubuntu/vivid-proposed/wmbattery -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: Fix Committed Status in “cinnamon-session” package in Ubuntu: Fix Released Status in “cinnamon-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Committed Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “gnome-shell” package in Ubuntu: Fix Committed Status in “gnome-shell-pomodoro” package in Ubuntu: Fix Committed Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Committed Status in “mate-power-manager” package in Ubuntu: Fix Committed Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: Fix Committed Status in “powerd” package in Ubuntu: In Progress Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Fix Committed Status in “unity-settings-daemon” package in Ubuntu: Fix Committed Status in “upower” package in Ubuntu: Fix Committed Status in “wmbattery” package in Ubuntu: Fix Committed Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: Fix Committed Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1388094] [NEW] Slider component can have problems when binding value
Public bug reported: In ubuntu-system-settings and the indicators, we deal with values that come from system services. When binding to the value in the Slider component, this can cause unpredictable behavior because we get property notifications back that change the value while the slider is being moved. This has been worked around in ubuntu-settings-component by creating a SliderMenu which used in the indicators and system-settings for things using the MenuModel provided by the indicator services. The SliderMenu is based on the Slider for the SDK, but adds some logic for handling this value binding loop. It would be best to improve the Slider to handle this sort of problem and reduce the amount of custom components. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1388094 Title: Slider component can have problems when binding value Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: In ubuntu-system-settings and the indicators, we deal with values that come from system services. When binding to the value in the Slider component, this can cause unpredictable behavior because we get property notifications back that change the value while the slider is being moved. This has been worked around in ubuntu-settings-component by creating a SliderMenu which used in the indicators and system- settings for things using the MenuModel provided by the indicator services. The SliderMenu is based on the Slider for the SDK, but adds some logic for handling this value binding loop. It would be best to improve the Slider to handle this sort of problem and reduce the amount of custom components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388094/+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 244250] Re: Spurious reboot notifications caused by libssl upgrades.
@mdeslaur: Again, thank you for your reply! Pardon my ignorance but I've never quite understood why that is - why is an update of libssl different from an update of other libs where you can simply restart the depending applications/daemons? And why is it different on a desktop? Maybe these questions require lengthy answers so if you could point me in a direction where I read up on these questions I'd be very grateful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/244250 Title: Spurious reboot notifications caused by libssl upgrades. Status in “openssl” package in Ubuntu: Fix Released Bug description: The postinst script for libssl0.9.8 currently has a bug where it sends a reboot notifcation whenever libssl is configured. So reconfiguring libssl0.9.8 or even just installing libssl0.9.8 will result in a reboot notification. Sending of the reboot notification should definitely be moved inside the upgrading guard. The correct fix is likely to move it inside a version comparison guard for particular important updates like Colin suggests below -- this is what every other standard package using notify-reboot-required does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+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 1388097] [NEW] waiting for network configuration in boot sequence - ubuntu 13.04
Public bug reported: When i boot my pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network don't work and "nmcli nm" command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown After a minute this is output of "nmcli nm" command: RUNNING:running STATE:connected WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1388097 Title: waiting for network configuration in boot sequence - ubuntu 13.04 Status in “network-manager” package in Ubuntu: New Bug description: When i boot my pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network don't work and "nmcli nm" command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown After a minute this is output of "nmcli nm" command: RUNNING:running STATE:connected WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1388097/+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 1388099] [NEW] In dialog, field labels are bold while title is not
Public bug reported: Ubuntu 14.10 r135 1. Go to System Settings > "Wi-Fi". 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose "Connect to hidden network". 4. Look at the text in the dialog. What you see: The dialog title is not bold, but the field labels are. What you should see: either (a) both are bold, (b) neither are bold, or (c) the title is bold but the labels are not. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of the problem" https://bugs.launchpad.net/bugs/1388099/+attachment/4250031/+files/Connect%20to%20hidden%20network%20dialog.cropped.png -- 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/1388099 Title: In dialog, field labels are bold while title is not Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Ubuntu 14.10 r135 1. Go to System Settings > "Wi-Fi". 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose "Connect to hidden network". 4. Look at the text in the dialog. What you see: The dialog title is not bold, but the field labels are. What you should see: either (a) both are bold, (b) neither are bold, or (c) the title is bold but the labels are not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388099/+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 1387282] Re: bluetooth devices are missing when booting with systemd
** Summary changed: - bluetooth does not work due to firmware load failure + bluetooth devices are missing when booting with systemd -- 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/1387282 Title: bluetooth devices are missing when booting with systemd Status in “systemd” package in Ubuntu: Confirmed Bug description: I cannot use bluetooth devices while using systemd as the default init system. While going to gnome-control-center to check for bluetooth devices, all the bluetooth functionality is deactivated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 17:43:44 2014 InstallationDate: Installed on 2014-10-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387282/+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 1371206] Re: [TOPBLOCKER] [SDK] Text selection - can't drag the handle
** Branch unlinked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/insertMode -- 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/1371206 Title: [TOPBLOCKER] [SDK] Text selection - can't drag the handle Status in Ubuntu UI Toolkit: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: When in insert mode, I can't drag the handle in a new position UX Spec https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#bookmark=kix.x877v0jqsn42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1371206/+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 1289465] Re: Brightness icons are suboptimal
** Branch linked: lp:~ken-vandine/ubuntu-system- settings/brightness_slider -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1289465 Title: Brightness icons are suboptimal Status in “indicator-power” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Fix Released Bug description: Ubuntu Trusty r188, Ubuntu 14.10 r2, Ubuntu 14.10 r152 1. Go to System Settings > "Battery". 2. Look at the icons at the ends of the "Display brightness" slider. What you see: * The minimum-brightness icon is a light bulb with no rays. * The maximum-brightness icon is a light bulb with rays and a lightning bolt inside it. What you should see: * The minimum-brightness bulb should have rays, because it is not zero brightness. * The maximum-brightness icon does not have a lightning bolt, because that is strongly associated with battery charging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1289465/+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