[Touch-packages] [Bug 1360417] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1360417 Title: thread_collect_info can leave out information in .crash files Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Trusty: Fix Released Bug description: I noticed there were some crash reports in the Ubuntu Error Tracker with incomplete information in them (bug 1355546) and ended up creating a test case that recreates one way the problem can occur. 1) in a terminal run 'sudo chmod 600 /etc/apt/sources.list' 2) run 'update-manager' 3) observe a crash and click Leave Closed on the crash notification dialog 4) confirm that there is in /var/crash/ a .upload and .uploaded file for the update-manager crash If you inspect the update-manager crash file you'll notice it is missing Dependencies and DistroRelease so the additional apport data collection was never done. Additionally, some information from Show Details of apport dialog does not appear in the report. UnreportableReason: E: Opening /etc/apt/sources.list... DistroRelease: Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1360417/+subscriptions -- Mailing list: https://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 1360417] Re: thread_collect_info can leave out information in .crash files
This bug was fixed in the package apport - 2.14.1-0ubuntu3.4 --- apport (2.14.1-0ubuntu3.4) trusty-proposed; urgency=medium * Write report even for crashes with UnreportableReasons, so that whoopsie will upload more information. (LP: #1360417) -- Brian Murray br...@ubuntu.com Tue, 02 Sep 2014 09:53:41 -0700 ** Changed in: apport (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1360417 Title: thread_collect_info can leave out information in .crash files Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Trusty: Fix Released Bug description: I noticed there were some crash reports in the Ubuntu Error Tracker with incomplete information in them (bug 1355546) and ended up creating a test case that recreates one way the problem can occur. 1) in a terminal run 'sudo chmod 600 /etc/apt/sources.list' 2) run 'update-manager' 3) observe a crash and click Leave Closed on the crash notification dialog 4) confirm that there is in /var/crash/ a .upload and .uploaded file for the update-manager crash If you inspect the update-manager crash file you'll notice it is missing Dependencies and DistroRelease so the additional apport data collection was never done. Additionally, some information from Show Details of apport dialog does not appear in the report. UnreportableReason: E: Opening /etc/apt/sources.list... DistroRelease: Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1360417/+subscriptions -- Mailing list: https://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 1365855] Re: 100% cpu in Xorg when xorg is started via lightdm
I installed unity8-destktop-session-x11 to test click on the desktop but
I did not change any config (to my knowledge :) except for installing
this package. I actually thought I had unity8-desktop-session-mir
installed, but it seems that during testing I moved to the other one.
And indeed, when I remove unity8-desktop-session-x11 the 100% CPU
problem goes away.
Here is the output of lightdm --show-config with the unity8-desktop-session-x11
package installed:
[SeatDefaults]
A type=unity;xlocal
A unity-compositor-command=unity-system-compositor.sleep
J user-session=ubuntu
C greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session
E guest-wrapper=/usr/lib/lightdm/lightdm-guest-session
H greeter-session=lightdm-gtk-greeter
G xserver-command=X -core
[LightDM]
J session-wrapper=/etc/lightdm/Xsession
J minimum-vt=7
J seats=seat-0
[GuestAccount]
J enabled=true
J username=guest
J setup-script=/usr/share/lightdm/guest-session/guest-session-setup.sh
J cleanup-script=/usr/share/lightdm/guest-session/guest-session-cleanup.sh
Sources:
A /usr/share/lightdm/lightdm.conf.d/10-unity-system-compositor.conf
(null) mand.conf
C /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
E /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
E /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
(null) mand.conf
G /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
H /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
[Invalid UTF-8] (null) \xe8\x87\xa9\xc8@\x7f
J /etc/lightdm/lightdm.conf
I see the 100% CPU with different environments like mate too, but lightdm is
using the same commandline for X, i.e. its running with -mir -mirSocket when
the u-d-s-x11 package is installed.
Feel free to reassign to Xmir.
--
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/1365855
Title:
100% cpu in Xorg when xorg is started via lightdm
Status in “lightdm” package in Ubuntu:
Incomplete
Bug description:
I see Xorg using 100% cpu when its running via lightdm.
This is not the case if I start X via startx or when its run from lxdm or
gdm. A strace from a VT shows constant activity (where gdm has only a select()
waiting). Most notably this repeats:
select(256, [0 1 3 5 13 24 25 26], NULL NULL {417 413000}) = 1 (in [0], left
{417, 412998})
read(0, 0x72bef74a0, 1024) = -1 (Bad file descriptor)
(transcripted from the affected machine).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365855/+subscriptions
--
Mailing list: https://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 1026465] Re: unity shell disappears when cloned monitor turned off and on
** Changed in: unity Assignee: Daniel van Vugt (vanvugt) = (unassigned) -- 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/1026465 Title: unity shell disappears when cloned monitor turned off and on Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: 1. fresh install Ubuntu12.04(64 bit) 2. connect 2 monitors to my graphics card, clone mode will be configured by default 3. turn off one monitor using xrandr --output DFPx --off 4. turn on the monitor using xrandr --output DFPx --auto issue happens that the launcher disappears, should be a problem of unity shell. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1026465/+subscriptions -- Mailing list: https://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 1061339] Re: Panel shadow is visible as a thin black line in workspace switcher previews
** Changed in: unity/6.0 Assignee: Daniel van Vugt (vanvugt) = (unassigned) -- 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/1061339 Title: Panel shadow is visible as a thin black line in workspace switcher previews Status in Unity: Fix Released Status in Unity 6.0 series: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: If you switch workspaces with Ctrl+Alt+Arrow but keep Ctrl+Alt help down and look at the preview then you will see thin back lines rendered. Those are the Unity panel shadow, which should not be visible if the Unity shell is not. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 4 09:24:27 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1061339/+subscriptions -- Mailing list: https://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 613809] Re: [FFe] gnomeradio NO SOUND, no /dev/mixer present
** Attachment removed: Precise markings https://bugs.launchpad.net/debian/+source/gnomeradio/+bug/613809/+attachment/3108319/+files/installed%20Precise%20Pangolin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/613809 Title: [FFe] gnomeradio NO SOUND, no /dev/mixer present Status in Gnomeradio: Confirmed Status in “alsa-driver” package in Ubuntu: Invalid Status in “gnomeradio” package in Ubuntu: Fix Released Status in “rhythmbox” package in Ubuntu: Invalid Status in “tvtime” package in Ubuntu: Fix Released Status in “gnomeradio” package in Debian: New Status in “gnomeradio” package in Fedora: Unknown Bug description: FFe justification: Adding support for alsamixer becomes increasingly important as Raring has turned off kernel-space OSS emulation, causing a regression from Precise - Quantal - Raring for users wanting to control sound card input volume from the gnomeradio application. original description: All applications worked in all previous versions (from 7.04 to 10.04) NO SOUND from Rhythmbox FM plug-in NO SOUND from gnomeradio I CAN'T boost the volume in aplication tvtime When any of the following applications is launched, I can record sound with the help of the application gnome-sound-recorder. Sound Preferences (Input Tab) clearly shows the existence of sound, when the selected option is Line In, but sound does not play on speakers. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35 Uname: Linux 2.6.35-14-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stevo 1536 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 21' Mixer name : 'Analog Devices AD1988B' Components : 'HDA:11d4198b,104381f6,00100300' Controls : 48 Simple ctrls : 26 Date: Thu Aug 5 12:48:29 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SelectedCard: 0 NVidia HDA-Intel - HDA NVidia SourcePackage: alsa-driver Symptom: audio Title: [Analog Devices AD1988B] Playback problem dmi.bios.date: 01/25/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-E ACPI BIOS Revision 1703 dmi.board.name: M2N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-EACPIBIOSRevision1703:bd01/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-E:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/gnomeradio/+bug/613809/+subscriptions -- Mailing list: https://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 1355776] Re: WiFi shown as enabled in indicator while disabled in status bar
Ok, I have re-read this and the only problem in the original screenshot was the lack of networks, which *is* a bug. Also, the issue with just reported in comment #7 is a bug. @Antti, could you comment on this? Should be use this bug for that issue or open a new one? -- 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/1355776 Title: WiFi shown as enabled in indicator while disabled in status bar Status in “indicator-network” package in Ubuntu: New Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. # system-image-cli -i current build number: 171 device name: mako channel: ubuntu-touch/utopic-proposed last update: 2014-08-05 07:56:23 version version: 171 version ubuntu: 20140805 version device: 20140728.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://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 1355776] Re: WiFi shown as enabled in indicator while disabled in status bar
The image for comment #7 was: # system-image-cli -i current build number: 29 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-09-11 05:41:43 version version: 29 version ubuntu: 20140910 version device: 20140908-d8c11f3 version custom: 1410379789 ** Changed in: indicator-network (Ubuntu) Status: Invalid = 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/1355776 Title: WiFi shown as enabled in indicator while disabled in status bar Status in “indicator-network” package in Ubuntu: New Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. # system-image-cli -i current build number: 171 device name: mako channel: ubuntu-touch/utopic-proposed last update: 2014-08-05 07:56:23 version version: 171 version ubuntu: 20140805 version device: 20140728.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://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 1349273] Re: NM does not retry opening mobile data on reboot
My guess here is that what I saw was an instance of the generic problem that NM seems to have some times creating connections, which is probably related to not detecting the creation of the ofono's ConnectionManager interface. As I usually have two SIMs around, this is maybe easier for me to reproduce. -- 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/1349273 Title: NM does not retry opening mobile data on reboot Status in “network-manager” package in Ubuntu: Incomplete Bug description: In case NM has failed to open any mobile data context, it will not re- try when rebooting the phone. This happened with a pre-paid SIM with no credit: opening a data context for it obviously failed. After adding credit to the SIM, I followed the instructions from the operator to reboot the phone to get data. However, after rebooting I had no mobile data. Taking a look to system settings, cellular data was set to Off and I was able to revert the situation marking the 2G/3G/4G option. Make NM retry the list of contexts in case no context was ever active on previous boot would make life easier for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349273/+subscriptions -- Mailing list: https://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: upower 0.99 transition
gnome-applets does build the battstat applet now that we are in sync with debian, but is already ready. Just needs a rebuild ** Changed in: gnome-applets (Ubuntu) Status: Invalid = In Progress -- 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: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “cinnamon-control-center” package in Ubuntu: New Status in “cinnamon-session” package in Ubuntu: New Status in “cinnamon-settings-daemon” package in Ubuntu: New Status in “gnome-applets” package in Ubuntu: In Progress Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “gnome-shell-pomodoro” package in Ubuntu: New 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 Released Status in “mate-power-manager” package in Ubuntu: Fix Released Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New 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: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress 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: In Progress 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. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and 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-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental 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 mate: all mate packages need rebuilding python-dbusmock: lp:1324791 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, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa 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 1356326] Re: policykit-desktop-privileges is missing actions for MATE
** Changed in: policykit-desktop-privileges (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1356326 Title: policykit-desktop-privileges is missing actions for MATE Status in “policykit-desktop-privileges” package in Ubuntu: Fix Committed Bug description: MATE 1.8.1 is now in the Ubuntu Utopic archive. I am working on Ubuntu MATE Remix and noticed that policykit-desktop-privileges doesn't include actions for 'org.mate.cpufreqselector' or 'org.mate.settingsdaemon.datetimemechanism.settime' I will submit a merge proposal that adds the required actions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1356326/+subscriptions -- Mailing list: https://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 1329085] Re: unexpected audio policy user experience
** Tags removed: rtm14 -- 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/1329085 Title: unexpected audio policy user experience Status in Web Browser App: Invalid Status in “media-hub” package in Ubuntu: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: discovered this in testing today, image #78 play a song from Music scope in dash navigate away to video play a video the music video audio play together I would have expected music to remain paused during video playback http://www.youtube.com/watch?v=D3cOuLiB8lg To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1329085/+subscriptions -- Mailing list: https://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 1356326] Re: policykit-desktop-privileges is missing actions for MATE
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/policykit-desktop- privileges/utopic-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1356326 Title: policykit-desktop-privileges is missing actions for MATE Status in “policykit-desktop-privileges” package in Ubuntu: Fix Committed Bug description: MATE 1.8.1 is now in the Ubuntu Utopic archive. I am working on Ubuntu MATE Remix and noticed that policykit-desktop-privileges doesn't include actions for 'org.mate.cpufreqselector' or 'org.mate.settingsdaemon.datetimemechanism.settime' I will submit a merge proposal that adds the required actions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1356326/+subscriptions -- Mailing list: https://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 1368063] [NEW] The photo captured by Camera app show darkness.
Public bug reported: Install Ubuntu 14.04 and boot into OS. Opened Camera app from dash home.Clicked the roundness button to capture photos. View the photos in /home/pictures.Found the photos show darkness. Steps to Reproduce: 1.Boot into OS. 2.Opened Camera app from dash home. 3.Clicked the roundness button to capture photos. 4.View the photos in /home/pictures. 5.Found the photos show darkness. ** Affects: camera-app Importance: Undecided Status: New ** Affects: oem-priority Importance: Undecided Status: New ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Also affects: camera-app Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368063 Title: The photo captured by Camera app show darkness. Status in Camera App: New Status in OEM Priority Project: New Status in “camera-app” package in Ubuntu: New Bug description: Install Ubuntu 14.04 and boot into OS. Opened Camera app from dash home.Clicked the roundness button to capture photos. View the photos in /home/pictures.Found the photos show darkness. Steps to Reproduce: 1.Boot into OS. 2.Opened Camera app from dash home. 3.Clicked the roundness button to capture photos. 4.View the photos in /home/pictures. 5.Found the photos show darkness. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1368063/+subscriptions -- Mailing list: https://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 1368063] Re: The photo captured by Camera app show darkness.
I think we may hit the issue of this problem: http://stackoverflow.com/questions/21709940/qt-capture-qcamera-too-dark example here have the same issue. http://qt-project.org/doc/qt-5/qml-qtmultimedia-cameracapture.html#details -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368063 Title: The photo captured by Camera app show darkness. Status in Camera App: New Status in OEM Priority Project: New Status in “camera-app” package in Ubuntu: New Bug description: Install Ubuntu 14.04 and boot into OS. Opened Camera app from dash home.Clicked the roundness button to capture photos. View the photos in /home/pictures.Found the photos show darkness. Steps to Reproduce: 1.Boot into OS. 2.Opened Camera app from dash home. 3.Clicked the roundness button to capture photos. 4.View the photos in /home/pictures. 5.Found the photos show darkness. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1368063/+subscriptions -- Mailing list: https://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 1356326] Re: policykit-desktop-privileges is missing actions for MATE
This bug was fixed in the package policykit-desktop-privileges - 0.18 --- policykit-desktop-privileges (0.18) utopic; urgency=medium * Add support for MATE desktop CPU freq selector and date/time mechanism. (LP: #1356326) -- Martin Wimpress c...@flexion.org Thu, 11 Sep 2014 09:05:21 +0200 ** Changed in: policykit-desktop-privileges (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 policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1356326 Title: policykit-desktop-privileges is missing actions for MATE Status in “policykit-desktop-privileges” package in Ubuntu: Fix Released Bug description: MATE 1.8.1 is now in the Ubuntu Utopic archive. I am working on Ubuntu MATE Remix and noticed that policykit-desktop-privileges doesn't include actions for 'org.mate.cpufreqselector' or 'org.mate.settingsdaemon.datetimemechanism.settime' I will submit a merge proposal that adds the required actions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1356326/+subscriptions -- Mailing list: https://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 1367894] Re: [in call indicator] call duration time incorrect on 30 second boundaries
** Branch linked: lp:~josharenson/unity8/fix_panel_minute_count ** Changed in: unity8 (Ubuntu) Status: Confirmed = In Progress -- 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/1367894 Title: [in call indicator] call duration time incorrect on 30 second boundaries Status in “unity8” package in Ubuntu: In Progress Bug description: verified on mako image #232 1.make a call 2.check time (in indicator bar and call interface) [Expect results] the call time and the call time in indicator bar are not consistent [Actual results] The call time ‖ The call time in indicator bar 0:00 - 0:29s ‖ 0:00-0:29s √ 0:30 - 0:59s ‖ 1:30-1:59s × 1:00 - 1:29s ‖ 1:00-1:29s √ 1:30 - 1:59s ‖ 2:30-2:59s × so on . . . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1367894/+subscriptions -- Mailing list: https://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 1311316] Re: After locking screen there is no input field to type password for unlock
Confirming this issue. I have this problem on my work pc, with 2 monitors setup. Problem shows up very often. Password field stops working on the first screen but I can login on second, but if I lock system again all two screens become affected. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://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 1349921] Re: Empty! message needs to be marked for translation
This is in silo 11 now, should land early next week. -- 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/1349921 Title: Empty! message needs to be marked for translation Status in Ubuntu Translations: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: When an indicator has no content, there is an Empty! message shown that appears always in English. It seems to come from: http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Panel/Indicators/DefaultIndicatorPage.qml#L200 So to make it translatable it should simply be enclosed in i18n.tr() and the .pot template updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1349921/+subscriptions -- Mailing list: https://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 1367822] Re: Process required to pin a shortcut to the launcher does not fit users mental model
** Also affects: ubuntu-ux 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/1367822 Title: Process required to pin a shortcut to the launcher does not fit users mental model Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: Add a pin to Launcher option to all installed App and Feed (Scope) Dash previews. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367822/+subscriptions -- Mailing list: https://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 1367821] Re: Apps that are downloaded/installed should show on launcher and dash with a being-filled animation
This will require some coordination between download manager, maybe apps scope and unity8, adding the relevant tasks. ** Summary changed: - The download progress can only be checked on the apps store. + Apps that are downloaded/installed should show on launcher and dash with a being-filled animation ** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Description changed: When a user taps to install an app, the app icon should be instantly placed into all locations it will appear when the download is complete, and the icon should display the 'downloading animation' (filling with colour) until the download is complete. + + Relevant spec: + https://sites.google.com/a/canonical.com/unity8dash/scopes/store/3-previews ** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-download-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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1367821 Title: Apps that are downloaded/installed should show on launcher and dash with a being-filled animation Status in Ubuntu UX bugs: New Status in “ubuntu-download-manager” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: When a user taps to install an app, the app icon should be instantly placed into all locations it will appear when the download is complete, and the icon should display the 'downloading animation' (filling with colour) until the download is complete. Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/scopes/store/3-previews To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367821/+subscriptions -- Mailing list: https://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 1368084] [NEW] phablet-shell: 72: [: /bin/bash:: unexpected operator, tries to read /root/.bash_profile
Public bug reported: Recent phablet-shell (r307) gives a lot of error messages: $ ~/ubuntu/phablet-tools/phablet-shell /home/martin/ubuntu/phablet-tools/phablet-shell: 72: [: /bin/bash:: unexpected operator /bin/bash: /root/.bash_profile: Permission denied /home/martin/.ssh/known_hosts updated. Original contents retained as /home/martin/.ssh/known_hosts.old 9 KB/s (395 bytes in 0.040s) /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied The syntax error comes from ADBUID=$(adb shell id -u|tr -d '\n') if [ $ADBUID -eq 0 ]; then as the shell command includes all these errors about /root/.bash_profile: $ adb shell 'id -u' /bin/bash: /root/.bash_profile: Permission denied 32011 Supposedly the recent changes to adbd forgot to set a proper $HOME or something similar? ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Affects: phablet-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Summary changed: - phablet-shell: 72: [: /bin/bash:: unexpected operator + phablet-shell: 72: [: /bin/bash:: unexpected operator, tries to read /root/.bash_profile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1368084 Title: phablet-shell: 72: [: /bin/bash:: unexpected operator, tries to read /root/.bash_profile Status in “android-tools” package in Ubuntu: New Status in “phablet-tools” package in Ubuntu: New Bug description: Recent phablet-shell (r307) gives a lot of error messages: $ ~/ubuntu/phablet-tools/phablet-shell /home/martin/ubuntu/phablet-tools/phablet-shell: 72: [: /bin/bash:: unexpected operator /bin/bash: /root/.bash_profile: Permission denied /home/martin/.ssh/known_hosts updated. Original contents retained as /home/martin/.ssh/known_hosts.old 9 KB/s (395 bytes in 0.040s) /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied The syntax error comes from ADBUID=$(adb shell id -u|tr -d '\n') if [ $ADBUID -eq 0 ]; then as the shell command includes all these errors about /root/.bash_profile: $ adb shell 'id -u' /bin/bash: /root/.bash_profile: Permission denied 32011 Supposedly the recent changes to adbd forgot to set a proper $HOME or something similar? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1368084/+subscriptions -- Mailing list: https://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 1039849] Re: Lightdm fails to start up after updates
This is no longer an issue for me personally, since it's 2014 and I'm running different software in different versions. -- 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/1039849 Title: Lightdm fails to start up after updates Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've not been using this laptop for a while, but then I did, installed updates, rebooted, and ever since I'm running into failsafe X. I made some changes in between trying to see whether they would help it to load up (such as explicitly defining the driver in xorg.conf) but those didn't change the situation. I'm stuck now, not sure what to do, and would appreciate some hints. I asked for help in #ubuntu but since I don't know what exactly the problem is we didn't get anywhere really. If there's anything I can do to provide more information please let me know. This may be an issue related to gdm actually, since the only error message I can find now is in /var/log/gdm/:0.log: Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Please consult the The X.Org Foundation support at http://wiki.x.org for help. ddxSigGiveUp: Closing log /var/log/gdm/:0.log (END) But maybe I missed something in the other relevant logs... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,mousepoll,snap,move,resize,wall,regex,vpswitch,imgpng,place,grid,session,unitymtgrabhandles,animation,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: None Date: Wed Aug 22 04:37:18 2012 DistUpgraded: 2012-04-27 20:57:28,759 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Subsystem: ASUSTeK Computer Inc. Device [1043:1862] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413.1) MachineType: ASUSTeK Computer Inc. UL30A PlymouthDebug: Error: [Errno 13] Keine Berechtigung: '/var/log/plymouth-debug.log' ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-30-generic root=/dev/mapper/vg1-slash ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevDb: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden UpgradeStatus: Upgraded to precise on 2012-04-27 (116 days ago) dmi.bios.date: 10/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30A dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd10/20/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1039849/+subscriptions -- Mailing list: https://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 1334855] Re: Can't use toolbar while notifications on screen
FWIW dismissing only snap decisions doesn't really solve anything as you could always dismiss them, using a button in the snap decision (even though dismissing is actually a different action than cancelling, for example). -- 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/1334855 Title: Can't use toolbar while notifications on screen Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Opinion Bug description: With notifications on the screen, they're overlayed on top of the top toolbar, as such I can't tap the back button. To replicate. Open system settings - accounts Sign in to twitter Wait while tweet notifications come in Navigate anywhere in system settings, such as updates. Note you can't go back while the notifications are on screen. See screenshot, back button obscured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1334855/+subscriptions -- Mailing list: https://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 1368090] [NEW] /usr/bin/ubuntu-download-manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-download-manager. This problem was most recently seen with version 0.8+14.10.20140807-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a10c010557e8bb231aeec6c7c84595daf1e57562 contains more details. ** Affects: ubuntu-download-manager Importance: Undecided Status: New ** Tags: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1368090 Title: /usr/bin/ubuntu-download- manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers::Queue::onManagedTransferStateChanged:call:QMetaObject::activate Status in Ubuntu Download Manager: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-download-manager. This problem was most recently seen with version 0.8+14.10.20140807-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a10c010557e8bb231aeec6c7c84595daf1e57562 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-download-manager/+bug/1368090/+subscriptions -- Mailing list: https://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 1368090] Re: /usr/bin/ubuntu-download-manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers::
** Package changed: ubuntu-download-manager (Ubuntu) = ubuntu-download- manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1368090 Title: /usr/bin/ubuntu-download- manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers::Queue::onManagedTransferStateChanged:call:QMetaObject::activate Status in Ubuntu Download Manager: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-download-manager. This problem was most recently seen with version 0.8+14.10.20140807-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a10c010557e8bb231aeec6c7c84595daf1e57562 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-download-manager/+bug/1368090/+subscriptions -- Mailing list: https://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 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
That's in the top 10 reports for utopic for the week, setting to High, Barry could you have a look? ** Changed in: system-image (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1365761/+subscriptions -- Mailing list: https://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 1368101] [NEW] Suspended apps don't restart when launched from another app
Public bug reported: Steps to reproduce:- 1) Open twitter webapp and sign in 2) Open browser 3) Open some other apps to ensure browser gets cleaned up by app lifecycle 4) Switch to twitter 5) Click on a link in a tweet Expected behaviour:- * Clicked link opens in browser Actual behaviour:- * Nothing Note, you can swipe back to browser to wake it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) 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/1368101 Title: Suspended apps don't restart when launched from another app Status in “qtmir” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Steps to reproduce:- 1) Open twitter webapp and sign in 2) Open browser 3) Open some other apps to ensure browser gets cleaned up by app lifecycle 4) Switch to twitter 5) Click on a link in a tweet Expected behaviour:- * Clicked link opens in browser Actual behaviour:- * Nothing Note, you can swipe back to browser to wake it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1368101/+subscriptions -- Mailing list: https://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 1368099] Re: libcurl3-gnutls application crashes with NULL-pointer deref
Seems to be similar to [1], although cause in [1] to end up at the very same position might due to another problem also in transmission. [1] https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1304004 ** Also affects: curl (Ubuntu) Importance: Undecided Status: New ** Also affects: zabbix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1368099 Title: libcurl3-gnutls application crashes with NULL-pointer deref Status in “curl” package in Ubuntu: New Status in “transmission” package in Ubuntu: New Status in “zabbix” package in Ubuntu: New Bug description: Bug occurs when interacting with some but not all SSL-webservers, so it seems to be triggered by the remote side, crashing a zabbix monitoring system when connecting to a problematic Apache 2.4 server in my case. Program received signal SIGSEGV, Segmentation fault. gnutls_x509_crt_import (cert=0xb8c9bc30, data=0x0, format=GNUTLS_X509_FMT_DER) at x509.c:176 176 x509.c: No such file or directory. (gdb) bt #0 gnutls_x509_crt_import (cert=0xb8c9bc30, data=0x0, format=GNUTLS_X509_FMT_DER) at x509.c:176 #1 0xb6ea253a in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #2 0xb6ea3209 in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #3 0xb6ea3e18 in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #4 0xb6e6511c in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #5 0xb6e74328 in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #6 0xb6e87b7a in ?? () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #7 0xb6e888a0 in curl_multi_perform () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #8 0xb6e7f6fb in curl_easy_perform () from /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 #9 0xb76be6aa in process_httptests () #10 0xb76bca56 in main_httppoller_loop () #11 0xb76979a9 in MAIN_ZABBIX_ENTRY () #12 0xb76ef49b in daemon_start () #13 0xb7690abf in main () According to [1], calling the function with data=NULL seems forbidden. It seems, that [2] is a similar report for curl. The upstream patch seems to be announced in [3] as gtls: fix NULL pointer dereference, date Fixed in 7.37.0 - May 21 2014. Also the packages in Unicorn should already include the patch but adding it on Trusty (production) seems not a good idea due to change in package dependencies. # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy libcurl3-gnutls libcurl3-gnutls: Installed: 7.35.0-1ubuntu2 Candidate: 7.35.0-1ubuntu2 Version table: *** 7.35.0-1ubuntu2 0 500 http://debarchive-ehealth.d03.arc.local/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status [1] http://manned.org/gnutls_x509_crt_import/a0fb5c1f [2] http://curl.haxx.se/mail/lib-2014-04/0145.html [3] http://curl.haxx.se/changes.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1368099/+subscriptions -- Mailing list: https://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 1368101] Re: Suspended apps don't restart when launched from another app
** Also affects: qtmir (Ubuntu) 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/1368101 Title: Suspended apps don't restart when launched from another app Status in “qtmir” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Status in “url-dispatcher” package in Ubuntu: New Bug description: Steps to reproduce:- 1) Open twitter webapp and sign in 2) Open browser 3) Open some other apps to ensure browser gets cleaned up by app lifecycle 4) Switch to twitter 5) Click on a link in a tweet Expected behaviour:- * Clicked link opens in browser Actual behaviour:- * Nothing Note, you can swipe back to browser to wake it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1368101/+subscriptions -- Mailing list: https://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 1368101] Re: Suspended apps don't restart when launched from another app
This might involve url-dispatcher, too (like focusing → resuming before sending the url over dbus). ** Also affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1368101 Title: Suspended apps don't restart when launched from another app Status in “qtmir” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Status in “url-dispatcher” package in Ubuntu: New Bug description: Steps to reproduce:- 1) Open twitter webapp and sign in 2) Open browser 3) Open some other apps to ensure browser gets cleaned up by app lifecycle 4) Switch to twitter 5) Click on a link in a tweet Expected behaviour:- * Clicked link opens in browser Actual behaviour:- * Nothing Note, you can swipe back to browser to wake it up from suspend, then back to twitter, click the link and it _will_ switch back to browser and open the link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1368101/+subscriptions -- Mailing list: https://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 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Indicator Location: New Status in Network Menu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1336715/+subscriptions -- Mailing list: https://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 1364453] Re: Brightness setting does not persist across reboots
** Package changed: ubuntu-system-settings (Ubuntu) = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1364453 Title: Brightness setting does not persist across reboots Status in “indicator-power” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: When altering the brightness setting, it is always reset to the default value after a reboot. It is expected that changing the setting should persist across reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1364453/+subscriptions -- Mailing list: https://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 1355776] Re: WiFi shown as enabled in indicator while disabled in status bar
This show that this is a duplicate of bug #1336715
phablet@ubuntu-phablet:~$ dbus-send --print-reply
--dest=com.canonical.indicator.network /com/canonical/indicator/network
org.gtk.Actions.Describe string:wifi.enable
method return sender=:1.48 - dest=:1.130 reply_serial=2
struct {
boolean true
signature
array [
variant boolean 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/1355776
Title:
WiFi shown as enabled in indicator while disabled in status bar
Status in “indicator-network” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “urfkill” package in Ubuntu:
Incomplete
Bug description:
After disabling WiFi and rebooting, WiFi appears as enabled in
indicator-network and system settings.
This contradicts what is shown in the status bar (see attached
screenshot).
WiFi interface exists, but it is down:
# ip address
22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default
qlen 100
link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff
While wifi RF is not blocked:
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Which is coherent with urfkill persistent state:
# cat /var/lib/urfkill/saved-states
[ALL]
soft=false
[WLAN]
soft=false
...
However, saved-states was before rebooting (after disabling wifi):
~# cat /var/lib/urfkill/saved-states
[ALL]
soft=false
[WLAN]
soft=true
...
Difficult to say were exactly is the error, but apparently something
is powering on WiFi.
# system-image-cli -i
current build number: 171
device name: mako
channel: ubuntu-touch/utopic-proposed
last update: 2014-08-05 07:56:23
version version: 171
version ubuntu: 20140805
version device: 20140728.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions
--
Mailing list: https://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 1367804] Re: initial account after creation transfers back to the settings app
the issue is in the online accout plugin, not settings ** Changed in: ubuntu-system-settings (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1367804 Title: initial account after creation transfers back to the settings app Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Triaged Bug description: STEPS: 1. Open Settings 2. Click on accounts 3. Select any account 4. Complete the account setup EXPECTATION: I expect to be transferred back to the main accounts page showing the newly created account. ACTUAL: Instead I am returned to the main Settings app page and the online accounts is completely closed. Opening the accounts page again I see the account I created. This only ever happens on the first account and it doesn't matter which account you choose to setup first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1367804/+subscriptions -- Mailing list: https://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 1293944] Re: [regression] Mir deb packages with versioned names cannot be installed simultaneously any more
** Branch linked: lp:~vanvugt/mir/version-drivers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1293944
Title:
[regression] Mir deb packages with versioned names cannot be installed
simultaneously any more
Status in Mir:
In Progress
Status in Mir 0.6 series:
Won't Fix
Status in “mir” package in Ubuntu:
Triaged
Bug description:
Mir has some packages with ABI-versioned names (libmirserver17,
libmirclient7) so that multiple versions can be installed
simultaneously, in theory. However this plan is not working;
Package: libmirserver17
Section: libs
Architecture: i386 amd64 armhf arm64
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends},
libmirplatform (= ${binary:Version}),
libmirplatformgraphics-mesa (= ${binary:Version}) |
libmirplatformgraphics-android (= ${binary:Version}),
When we bump an ABI number, we also increase the ${binary:Version}. So
you can see from the names that libmirplatform* can only have one
version installed at a time. And that indirectly means that
libmirserverN can never be installed simultaneously with
libmirserverN+1.
This also leads to annoying CI failures as we're seeing this week:
The following packages have unmet dependencies:
libmirserver16 : Depends: libmirplatform (= 0.1.6+14.04.20140310-0ubuntu1)
but 0.1.7+autopilot0 is to be installed
Depends: libmirplatformgraphics-mesa (=
0.1.6+14.04.20140310-0ubuntu1) but 0.1.7+autopilot0 is to be installed or
libmirplatformgraphics-android (=
0.1.6+14.04.20140310-0ubuntu1) but 0.1.7+autopilot0 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify
a solution).
There are at least two possible solutions I can think of so far:
(1) Change our Depends' to not use straight equality. So we must change:
libmirplatform (= ${binary:Version}),
to:
libmirplatform (= ${binary:Version}),
or even to
libmirplatform (= some_older_version_based_on_real_requirements),
(2) Change libplatform* to include some ABI number in their names. Not
ideal.
I like (1).
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1293944/+subscriptions
--
Mailing list: https://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 1362150] Re: [Greeter] SIM PIN unlock usability needs improving
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1362150 Title: [Greeter] SIM PIN unlock usability needs improving Status in Network Menu: New Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Confirmed Bug description: Several bugs have been reported related to using the PIN unlock Grouping here for review Add feedback on failed attempts - The dialog tells you how many attempts you have remaining before a PUK code will be required - Entering the wrong PIN will result in a clear message to user of the failure and an update of the attempts remaining count After cancelling SIM unlock, how to unlock is not obvious: 1.Insert this SIM card 2.Power on device 3. Popup SIM PIN unlock interface after power on device 4. cancel this dialog 5. Go to phone app to make a call It is not obvious that the next step should be to drag down the indicator and use the unlock button. the phone and messaging apps should have a shorthand button clearly visible to unlock the relevant SIM so that the user does not have to know to go to the indicator-network first to be able to make phonecalls or send SMS To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1362150/+subscriptions -- Mailing list: https://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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Don't know if it is strongly related, but I think so. I'm using Modelio 3.1 on Ubuntu 64 bit. Sometimes, apparently without a specific sequence pattern, Modelio closes; other times, it doesn't allow to make any type of operations (i.e. when I right click on an element, it doesn't show anything). I don't know what the problem is. If I launch it from the terminal, it always returns error message like this Modelio 3:10699): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure-ref_count 0' failed or this (Modelio 3:10699): GLib-CRITICAL **: Source ID 20104 was not found when attempting to remove it The error message returned in the log file is # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f803bba4d6c, pid=27247, tid=140190697162496 # # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x31d6c] g_type_check_instance_is_a+0x3c # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # If it could be of help, I can attach the various log files it generates. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://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 1350291] Re: cloud-archive:juno unsupported
** Branch linked: lp:ubuntu/utopic-proposed/software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1350291 Title: cloud-archive:juno unsupported Status in “software-properties” package in Ubuntu: Confirmed Status in “software-properties” source package in Trusty: Confirmed Status in “software-properties” source package in Utopic: Confirmed Bug description: For 14.04, we'll be backporting OpenStack Juno using the Ubuntu Cloud Archive; we already support the existing 12.04 cloud archives using cloud-archive prefix; please add support for Juno on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1350291/+subscriptions -- Mailing list: https://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 1368135] [NEW] touching ubuntu icon when (non-favourite) scope open does not display home screen.
Public bug reported: 1) swipe up to open Manage Dash. 2) open a scope. 3) swipe left. 4) touch orange ubuntu logo. Expected outcome: main home screen displayed (phone, messaging, contacts, etc). Actual outcome: the scope you opened in (1) is displayed. Steps to get from the scope back to the home screen: 1) Click back at top of scope. 2) Click Done. Note that if you mark the scope as a favourite, the next time you launch it touching the orange ubuntu logo *will* take you to the home screen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368135 Title: touching ubuntu icon when (non-favourite) scope open does not display home screen. Status in “unity8” package in Ubuntu: New Bug description: 1) swipe up to open Manage Dash. 2) open a scope. 3) swipe left. 4) touch orange ubuntu logo. Expected outcome: main home screen displayed (phone, messaging, contacts, etc). Actual outcome: the scope you opened in (1) is displayed. Steps to get from the scope back to the home screen: 1) Click back at top of scope. 2) Click Done. Note that if you mark the scope as a favourite, the next time you launch it touching the orange ubuntu logo *will* take you to the home screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368135/+subscriptions -- Mailing list: https://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 1368140] [NEW] add guide lines overlay option
Public bug reported: Both iOS and Android cameras have an option to overlay 2 evenly-spaced vertical and 2 evenly-spaced horizonal white guide lines. These are a very useful alignment aid when composing a shot. For details: http://en.wikipedia.org/wiki/Rule_of_thirds Bonus points if we could have a Fibonacci spiral option too :-) : http://en.wikipedia.org/wiki/Golden_spiral ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - add guide lines overlay as an option + add guide lines overlay option -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368140 Title: add guide lines overlay option Status in “camera-app” package in Ubuntu: New Bug description: Both iOS and Android cameras have an option to overlay 2 evenly-spaced vertical and 2 evenly-spaced horizonal white guide lines. These are a very useful alignment aid when composing a shot. For details: http://en.wikipedia.org/wiki/Rule_of_thirds Bonus points if we could have a Fibonacci spiral option too :-) : http://en.wikipedia.org/wiki/Golden_spiral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368140/+subscriptions -- Mailing list: https://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 1368135] Re: touching ubuntu icon when (non-favourite) scope open does not display home screen.
*** This bug is a duplicate of bug 1355359 *** https://bugs.launchpad.net/bugs/1355359 ** This bug has been marked a duplicate of bug 1355359 Overview should close on left edge and Ubuntu button in launcher -- 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/1368135 Title: touching ubuntu icon when (non-favourite) scope open does not display home screen. Status in “unity8” package in Ubuntu: New Bug description: 1) swipe up to open Manage Dash. 2) open a scope. 3) swipe left. 4) touch orange ubuntu logo. Expected outcome: main home screen displayed (phone, messaging, contacts, etc). Actual outcome: the scope you opened in (1) is displayed. Steps to get from the scope back to the home screen: 1) Click back at top of scope. 2) Click Done. Note that if you mark the scope as a favourite, the next time you launch it touching the orange ubuntu logo *will* take you to the home screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368135/+subscriptions -- Mailing list: https://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 1364453] Re: Brightness setting does not persist across reboots
Yeah, and the shell needs to proxy the setting to u-s-c. ** Also affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1364453 Title: Brightness setting does not persist across reboots Status in “indicator-power” package in Ubuntu: Confirmed Status in “unity-system-compositor” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: When altering the brightness setting, it is always reset to the default value after a reboot. It is expected that changing the setting should persist across reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1364453/+subscriptions -- Mailing list: https://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 1368147] [NEW] Lenovo Thinkpad Twist: Mobile Broadbad not working any more
Public bug reported: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click Enable Mobile Broadband in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying Connection activation failed, (32) The connection was not supportedby oFono. I am using Utopic. ** 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in “network-manager” package in Ubuntu: New Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click Enable Mobile Broadband in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying Connection activation failed, (32) The connection was not supportedby oFono. I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://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 1368146] [NEW] keyboard not set to English
Public bug reported: I upgraded to 14.04 and have the international keyboard layout instead of English. This is reported as a known bug with a workaround that says I should disable IBus. I can't even find IBus! I use Xubuntu on an AMD64 system and had no problems with the previous LTS release. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1368146 Title: keyboard not set to English Status in “ibus” package in Ubuntu: New Bug description: I upgraded to 14.04 and have the international keyboard layout instead of English. This is reported as a known bug with a workaround that says I should disable IBus. I can't even find IBus! I use Xubuntu on an AMD64 system and had no problems with the previous LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1368146/+subscriptions -- Mailing list: https://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 1368144] [NEW] ImportError: No module named datetime with lp:click-toolbelt
Public bug reported: Using lp:click-toolbelt, I get the attached error when running ./click- toolbelt with the new python2.7 2.7.8-7. Short version: --- Original exception was: Traceback (most recent call last): File ./click-toolbelt, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module import plistlib File /usr/lib/python2.7/plistlib.py, line 62, in module import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. Note: this is a earlier built click-toolbelt I'm running, since the build process from a clean checkout is quite error-prone. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Attachment added: nodatetime.txt https://bugs.launchpad.net/bugs/1368144/+attachment/4201216/+files/nodatetime.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1368144 Title: ImportError: No module named datetime with lp:click-toolbelt Status in “python2.7” package in Ubuntu: New Bug description: Using lp:click-toolbelt, I get the attached error when running ./click-toolbelt with the new python2.7 2.7.8-7. Short version: --- Original exception was: Traceback (most recent call last): File ./click-toolbelt, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module import plistlib File /usr/lib/python2.7/plistlib.py, line 62, in module import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. Note: this is a earlier built click-toolbelt I'm running, since the build process from a clean checkout is quite error-prone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1368144/+subscriptions -- Mailing list: https://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 1368144] Re: ImportError: No module named datetime with lp:click-toolbelt
** Description changed: Using lp:click-toolbelt, I get the attached error when running ./click- toolbelt. Short version: --- Original exception was: Traceback (most recent call last): - File ./click-toolbelt, line 5, in module - from pkg_resources import load_entry_point - File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module - import plistlib - File /usr/lib/python2.7/plistlib.py, line 62, in module - import datetime + File ./click-toolbelt, line 5, in module + from pkg_resources import load_entry_point + File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module + import plistlib + File /usr/lib/python2.7/plistlib.py, line 62, in module + import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. + + Note: this is a earlier built click-toolbelt I'm running, since the + build process from a clean checkout is quite error-prone. ** Description changed: Using lp:click-toolbelt, I get the attached error when running ./click- - toolbelt. + toolbelt with the new python2.7 2.7.8-7. Short version: --- Original exception was: Traceback (most recent call last): File ./click-toolbelt, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module import plistlib File /usr/lib/python2.7/plistlib.py, line 62, in module import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. Note: this is a earlier built click-toolbelt I'm running, since the build process from a clean checkout is quite error-prone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1368144 Title: ImportError: No module named datetime with lp:click-toolbelt Status in “python2.7” package in Ubuntu: New Bug description: Using lp:click-toolbelt, I get the attached error when running ./click-toolbelt with the new python2.7 2.7.8-7. Short version: --- Original exception was: Traceback (most recent call last): File ./click-toolbelt, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module import plistlib File /usr/lib/python2.7/plistlib.py, line 62, in module import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. Note: this is a earlier built click-toolbelt I'm running, since the build process from a clean checkout is quite error-prone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1368144/+subscriptions -- Mailing list: https://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 1368144] Re: ImportError: No module named datetime with lp:click-toolbelt
according to Timo, this is in a virtualenv, where the python binary is copied, but not the standard library. The datetime extension is now built as a builtin, therefore the datetime module cannot be found anymore in the virtualenv. the solution is to re-create the virtualenv. ** Changed in: python2.7 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1368144 Title: ImportError: No module named datetime with lp:click-toolbelt Status in “python2.7” package in Ubuntu: Invalid Bug description: Using lp:click-toolbelt, I get the attached error when running ./click-toolbelt with the new python2.7 2.7.8-7. Short version: --- Original exception was: Traceback (most recent call last): File ./click-toolbelt, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 33, in module import plistlib File /usr/lib/python2.7/plistlib.py, line 62, in module import datetime ImportError: No module named datetime --- Downgrading to 2.7.8-6ubuntu1 by downloading the older .deb:s from Launchpad fixes the issue, upgrading again bring the issue visible again. Note: this is a earlier built click-toolbelt I'm running, since the build process from a clean checkout is quite error-prone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1368144/+subscriptions -- Mailing list: https://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 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
sudo lsusb -vvv output ** Attachment added: lsusb-vvv.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+attachment/4201217/+files/lsusb-vvv.txt -- 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in “network-manager” package in Ubuntu: New Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click Enable Mobile Broadband in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying Connection activation failed, (32) The connection was not supportedby oFono. I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://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 1307709] Re: webbrowser-app does not start in Unity 8 preview session
** Branch linked: lp:~oxide-developers/oxide/packaging.trusty -- 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/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide Webview: Fix Released Status in Web Browser App: Confirmed Status in “mesa” package in Ubuntu: Triaged Status in “unity8-desktop-session” package in Ubuntu: Fix Released Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://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 1178841] Re: [regression] iwl3945 0000:04:00.0: Radio disabled by HW RF Kill switch - wpa_supplicant causes high cpu load -
Last good version is in Ubuntu 12.04.5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1178841 Title: [regression] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch - wpa_supplicant causes high cpu load - Status in “linux” package in Ubuntu: Confirmed Status in “wpa” package in Ubuntu: Confirmed Bug description: On this notebook wifi sometimes doesn't work (wifi led not on, no wlan0 device), this issue was already present in 12.10, but aside from the non-working wifi, nothing bad™ happened in this condition. After updating to 13.04 however, dmesg gets spammed by repeated messages May 10 23:28:09 piBook kernel: [ 21.048718] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.048842] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049636] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049763] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051079] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051378] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052369] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052499] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053323] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053452] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054252] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054374] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.055140] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch a side effect of this is that now wpa_supplicant causes high CPU load, rendering the device almost unusable. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: wpasupplicant 1.0-3ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 10 23:32:16 2013 InstallationDate: Installed on 2013-03-05 (66 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: Upgraded to raring on 2013-04-25 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178841/+subscriptions -- Mailing list: https://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 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
dmesg output ** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+attachment/4201219/+files/dmesg.txt -- 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in “network-manager” package in Ubuntu: New Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click Enable Mobile Broadband in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying Connection activation failed, (32) The connection was not supportedby oFono. I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://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 1359404] Re: Symbol page switch back should match other platforms
** Changed in: ubuntu-keyboard Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1359404 Title: Symbol page switch back should match other platforms Status in Ubuntu Keyboard: Fix Released Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Bug description: Currently the automatic switch back from certain characters on the symbol page only happens with ? and !, this makes it difficult to type a sentence like: This is so awesome We should check what other platform's keyboards do and match the keys they automatically switch back on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1359404/+subscriptions -- Mailing list: https://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 1178841] Re: [regression] iwl3945 0000:04:00.0: Radio disabled by HW RF Kill switch - wpa_supplicant causes high cpu load -
** No longer affects: wpa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1178841 Title: [regression] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch Status in “linux” package in Ubuntu: Incomplete Bug description: On this notebook wifi sometimes doesn't work (wifi led not on, no wlan0 device), this issue was already present in 12.10, but aside from the non-working wifi, nothing bad™ happened in this condition. After updating to 13.04 however, dmesg gets spammed by repeated messages May 10 23:28:09 piBook kernel: [ 21.048718] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.048842] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049636] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049763] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051079] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051378] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052369] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052499] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053323] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053452] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054252] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054374] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.055140] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch a side effect of this is that now wpa_supplicant causes high CPU load, rendering the device almost unusable. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: wpasupplicant 1.0-3ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 10 23:32:16 2013 InstallationDate: Installed on 2013-03-05 (66 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: Upgraded to raring on 2013-04-25 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178841/+subscriptions -- Mailing list: https://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 1311316] Re: After locking screen there is no input field to type password for unlock
I have the same Problem and I found a similar Bug #1044251 (https://bugs.launchpad.net/bugs/1044251) solved in 2012 For me, enabling the 'Manual Login'' and replacing unity works so far. This is just an (ugly) workaround (Loginpromt changes), but some parts of the old fix might be applied here as well? I applied the following steps: 1. Switch to tty1 ( [Ctrl]+[Alt]+[F1] ) and login 2. edit the appropriate lightdm configuration, in my case: sudo vim /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf 3. set/add th following property greeter-show-manual-login=true To be able to continue work w/o restarting lightdm (loosing all running processes / open windows), one can simply replace unity (see also accepted answer in http://superuser.com/questions/570194/how- do-i-restart-a-frozen-screen-in-ubuntu-without-losing-any-open-windows ) 4. set and export the DISPLAY variable: DISPLAY=:0 export DISPLAY 5. run (re-)unity (--replace might not be neccessary): unity --replace -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://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 1097733] Re: [sdk] Ubuntu.Application component should be platform agnostic
I don't think this is still valid. Does the Ubuntu.Application import still exist? -- 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/1097733 Title: [sdk] Ubuntu.Application component should be platform agnostic Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: The current state with Ubuntu.Application being available only on arm, causes troubles when building applications on x86 and force each application developer to wrap it in a Loader to make it fail gracefully when running the applications on x86. The component should be available on all platforms to eliminate that problem. If the Loader workaround is the proposed solution, it should be at least hidden inside the component for the platform dependent stuff to ease up app development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1097733/+subscriptions -- Mailing list: https://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 1207854] Re: [greeter] should provide launcher/camera/notes options
well, I assume it means for unity8 to have some sort of acl on what can be started from the launcher on the lockscreen ** Changed in: unity8 (Ubuntu) Status: Incomplete = 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/1207854 Title: [greeter] should provide launcher/camera/notes options Status in Ubuntu Touch System Settings: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: New Bug description: The system settings' privacy design [1] has a section When locked, allow: launcher/camera/notes We need to define an configuration layer/interface that let the settings app tell the greeter about those [1] https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1207854/+subscriptions -- Mailing list: https://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 1255530] Re: /home/phablet/.pam_environment does not get updated on OTA upgrades
closing, that's an old bug and we are not going to handle migration from those versions ** Changed in: ubuntu-system-settings (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1255530 Title: /home/phablet/.pam_environment does not get updated on OTA upgrades Status in “indicator-datetime” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: starting my phone set to german language the lock screen properly shows a 24h clock ... as aoon as the panel clock shows up, the lockscreen format (and all other places where the time is shown in the UI) is swithcing to AM/PM 12h time format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+subscriptions -- Mailing list: https://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 1237642] Re: Some sound settings need to be in AccountsService
I think that is fixed, feel free to reopen if that's not the case though ** Changed in: ubuntu-system-settings (Ubuntu) Status: Triaged = 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/1237642 Title: Some sound settings need to be in AccountsService Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Triaged Bug description: Sound settings like volume and ringtone need to be accessible to the greeter once we split it. Thus, they should be stored in AS instead of gsettings (or at least in addition to). This is not a v1-phone bug, but for the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1237642/+subscriptions -- Mailing list: https://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 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity
As of 11 September, the daily(?)-live current amd64 .iso is still at 5 September, 3.16.0-12, boots to desktop no compiz/unity. Daily-live pending amd64 was at 10 3.16.0-14, boots to compiz/unity fine. Installed fine (for a develompment image). I haven't heard that there was any change in the Intel driver. Unity/compiz are under constant development. I presume pending isn't ready for current and anything could happen -- 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/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Confirmed Bug description: Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre. Boots 3.16.0-6 amd64 fine, runs compiz 3D fine. Today's amd64 iso download, 20 August, boots to desktop cursor. No unity. Did ubuntu-bug from command line on the booted iso, saved report. Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file. Planet Ubuntu asked for results on 3.16.0-9 so this is my result. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 20 16:57:57 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140820) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359299/+subscriptions -- Mailing list: https://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 1355776] Re: WiFi shown as enabled in indicator while disabled in status bar
** Tags added: rtm14 -- 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/1355776 Title: WiFi shown as enabled in indicator while disabled in status bar Status in “indicator-network” package in Ubuntu: New Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. # system-image-cli -i current build number: 171 device name: mako channel: ubuntu-touch/utopic-proposed last update: 2014-08-05 07:56:23 version version: 171 version ubuntu: 20140805 version device: 20140728.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://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 1245951] Re: Wrong oFono property used for data technology indication
for now, network-registration has been giving reliable results, so I don't see an immediate reason to fix this ASAP. ** Changed in: indicator-network (Ubuntu) Importance: High = Medium ** Changed in: indicator-network Importance: High = Medium ** Tags removed: touch-2014-09-11 ** Tags added: touch-2014-09-25 -- 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/1245951 Title: Wrong oFono property used for data technology indication Status in Network Menu: Triaged Status in “indicator-network” package in Ubuntu: Triaged Bug description: Image: Touch #100 ( aka v1.0 ). The current indicator-network code uses the ofono's NetworkRegistration interface's Technology property to determine which mobile data connection icon to display on the status bar. The code currently compares the value of Technology to: - gsm -- this causes 2G ( or a tortoise ) to be displayed - umts -- this causes 3G to be displayed - edge -- this causes E to be displayed - hspa -- this causes H to be displayed - lte -- valid, but currently not supported in the ofono/rilmodem driver ( LTE isn't yet 100% supported ) The code instead should be examining ofono's ConnectionManager interface's Bearer property. This is not currently being set by the ofono/rilmodem code ( see bug #1245954 for more details ). The valid values of the Bearer property ( with associated icons in parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ), hsupa/hsdpa/hspa ( H ), and lte ( L ). oFono doesn't currently support reporting HSPA+, whereas RIL does, so if have the need for differentiating between HSPA and HSPA+, then we'll need to patch ofono so that the value hspap is valid for Bearer. - To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1245951/+subscriptions -- Mailing list: https://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
** Changed in: indicator-network (Ubuntu) Assignee: Antti Kaijanmäki (kaijanmaki) = Jussi Pakkanen (jpakkane) ** Changed in: indicator-network (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1332306 Title: Hot-swapped SIMs should be detected and prompt user to reboot Status in “indicator-network” package in Ubuntu: Triaged Status in “ofono” package in Ubuntu: Fix Released 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/+source/indicator-network/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://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 1368019] Re: Type QQmlBinding property State.when fails to accept assignments
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1368019 Title: Type QQmlBinding property State.when fails to accept assignments Status in “qtdeclarative-opensource-src” package in Ubuntu: Confirmed Bug description: Experienced by Unity8 team. See details in the upstream bug https://bugreports.qt-project.org/browse/QTBUG-39421 This bug is causing intermittent errors in our unity8 qmltests such as this: QWARN : qmltestrunner::SurfaceContainer::test_animateRemoval() file:///home/dandrader/unity8/fix-unstable-SurfaceContainer-test/qml/Stages/SurfaceContainer.qml:46:19: Unable to assign bool to [unknown property type] FAIL! : qmltestrunner::SurfaceContainer::test_animateRemoval() Compared values are not the same Actual (): Expected (): zombie Loc: [/home/dandrader/unity8/fix-unstable-SurfaceContainer-test/tests/qmltests/Stages/tst_SurfaceContainer.qml(135)] QWARN : qmltestrunner::SurfaceContainer::test_animateRemoval() file:///home/dandrader/unity8/fix-unstable-SurfaceContainer-test/qml/Stages/SurfaceContainer.qml:46:19: Unable to assign bool to [unknown property type] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1368019/+subscriptions -- Mailing list: https://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 1336675] Re: SIM unlock - UI hangs when user enters wrong PIN
This is not fixed yet properly. Will be fixed once the attached branch lands. ** Changed in: indicator-network (Ubuntu) Status: Incomplete = In Progress ** Changed in: unity8 (Ubuntu) Status: Incomplete = In Progress -- 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/1336675 Title: SIM unlock - UI hangs when user enters wrong PIN Status in “indicator-network” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: When the user wants to unlock his SIM card and enters a wrong PIN, the UI freezes completely on second attempt and a reboot is required. Test Case: 1. Boot a SIM locked device 2. Go to network indicator/sim unlock 3. On the keypad enter a wrong PIN 4. After the notification that unlock failed, enter the right PIN Actual Result While user is entering the PIN for the second time, the UI freezes and the phone must be rebooted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140626.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu2 Architecture: armhf Date: Wed Jul 2 10:15:29 2014 InstallationDate: Installed on 2014-07-02 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140702-020204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1336675/+subscriptions -- Mailing list: https://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 1367457] Re: [messaging-app] press and hold to remove attachment needs improvement
** Summary changed: - press and hold to remove attachment needs improvement + [messaging-app] press and hold to remove attachment needs improvement -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1367457 Title: [messaging-app] press and hold to remove attachment needs improvement Status in Messaging App: New Status in Ubuntu UX bugs: Fix Committed Status in “messaging-app” package in Ubuntu: New Bug description: add a photo to a new message try to delete it by press and hold Expected results: the Remove popup menu will appear on a long press Actual result: the Remove popup menu does not appear until you release the long press To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1367457/+subscriptions -- Mailing list: https://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 1348110] Re: Please enter a number label is too big for some translations
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1348110 Title: Please enter a number label is too big for some translations Status in Dialer app for Ubuntu Touch: Confirmed Status in Ubuntu UX bugs: New Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Here's a screenshot from German translation. I guess the font size should be reduced in such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1348110/+subscriptions -- Mailing list: https://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 1336675] Re: SIM unlock - UI hangs when user enters wrong PIN
** Tags removed: touch-2014-08-28 ** Tags added: touch-2014-09-11 -- 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/1336675 Title: SIM unlock - UI hangs when user enters wrong PIN Status in “indicator-network” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: When the user wants to unlock his SIM card and enters a wrong PIN, the UI freezes completely on second attempt and a reboot is required. Test Case: 1. Boot a SIM locked device 2. Go to network indicator/sim unlock 3. On the keypad enter a wrong PIN 4. After the notification that unlock failed, enter the right PIN Actual Result While user is entering the PIN for the second time, the UI freezes and the phone must be rebooted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140626.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu2 Architecture: armhf Date: Wed Jul 2 10:15:29 2014 InstallationDate: Installed on 2014-07-02 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140702-020204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1336675/+subscriptions -- Mailing list: https://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 1319586] Re: FTBFS on latest glib
** Changed in: indicator-network (Ubuntu) Status: New = Invalid -- 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/1319586 Title: FTBFS on latest glib Status in “indicator-network” package in Ubuntu: Invalid Bug description: /tmp/buildd/indicator-network-0.5.1+14.04.20140409.1/network/mobile-sim-manager.vala:519.39-519.50: error: `Notification' is an ambiguous reference between `GLib.Notification' and `Notify.Notification' private void notification_closed (Notification? notification) /tmp/buildd/indicator-network-0.5.1+14.04.20140409.1/network/mobile-sim-manager.vala:56.14-56.25: error: `Notification' is an ambiguous reference between `GLib.Notification' and `Notify.Notification' public Notification? notification; Compilation failed: 2 error(s), 0 warning(s) Fix is to specifically use Notify namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1319586/+subscriptions -- Mailing list: https://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 1366018] Re: Not clear in Wi-Fi settings whether you are connected
Not reproducible in the indicator either. ** Changed in: indicator-network (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1366018 Title: Not clear in Wi-Fi settings whether you are connected Status in “indicator-network” package in Ubuntu: Incomplete Status in “ubuntu-system-settings” package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 r22 1. Go somewhere that many Wi-Fi networks are nearby. 2. Navigate to System Settings Wi-Fi. 3. Try to tell whether you are connected. What happens: The network you are connected to might be so far down the list that it's off-screen. What should happen: The network you are connected to is always at the top. https://wiki.ubuntu.com/Networking#wi-fi-phone: Whenever Wi-Fi is on and a network *is* connected, 'Available networks:' should instead be 'Other available networks:', because it should be preceded by a 'Connected to:' section listing the connected network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366018/+subscriptions -- Mailing list: https://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 1207854] Re: [greeter] should provide launcher/camera/notes options
** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Low -- 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/1207854 Title: [greeter] should provide launcher/camera/notes options Status in Ubuntu Touch System Settings: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: The system settings' privacy design [1] has a section When locked, allow: launcher/camera/notes We need to define an configuration layer/interface that let the settings app tell the greeter about those [1] https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1207854/+subscriptions -- Mailing list: https://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 1320828] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:11:SimUnlockDialog::state:ModemManager::Private::ofono_disappeared:ModemManager::Private::Pr
** Changed in: indicator-network (Ubuntu) Status: New = Invalid -- 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/1320828 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:11:SimUnlockDialog::state:ModemManager::Private::ofono_disappeared:ModemManager::Private::Private:ModemManager::ModemManager:Service::Service Status in “indicator-network” package in Ubuntu: Invalid 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.20140516.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f761f1b6abedfe3a66f40e2108453a087f22523c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1320828/+subscriptions -- Mailing list: https://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 1334855] Re: [design] Can't use toolbar while notifications on screen
** Summary changed: - Can't use toolbar while notifications on screen + [design] Can't use toolbar while notifications on screen -- 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/1334855 Title: [design] Can't use toolbar while notifications on screen Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Opinion Bug description: With notifications on the screen, they're overlayed on top of the top toolbar, as such I can't tap the back button. To replicate. Open system settings - accounts Sign in to twitter Wait while tweet notifications come in Navigate anywhere in system settings, such as updates. Note you can't go back while the notifications are on screen. See screenshot, back button obscured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1334855/+subscriptions -- Mailing list: https://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 1366391] Re: re-prompted for already-known password when switching networks
If you are connected to network 1, start connecting to network 2 and then cancel, the expected behaviour is to return the network status to how it was i.e. connected to network 1. The system should not ask you to retype a password for a network that you have already joined once. If your behaviour is something different, please write step by step descriptions on what happens. ** Changed in: indicator-network (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1366391 Title: re-prompted for already-known password when switching networks Status in “indicator-network” package in Ubuntu: Incomplete Bug description: When I re-connect to a known network, I am prompted for the WPA2 password. However, clicking cancel then successfully connects to this network! This is only happening for one of my networks. Not currently sure why since the other main network I use is also WPA2 protected and I'm not prompted for that networks password. I wonder if the re-prompt only occurs if the user attempts to connect to a different network to the first-joined network on boot (can't test atm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366391/+subscriptions -- Mailing list: https://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 1349273] Re: NM does not retry opening mobile data on reboot
OK, please let me know if you're able to reproduce this with multiple SIMs. Note that bug #1350332 ( which is private ) describes a problem with mobile-data not being re-established for the 2nd slot after FlightMode is disabled. I'm pretty sure this is a generic problem on krillin which affects both slots and will open a new network-manager bug after doing a bit more testing. Please try and reproduce this with multiple SIMs, and if you cannot, please change the Status to Invalid. -- 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/1349273 Title: NM does not retry opening mobile data on reboot Status in “network-manager” package in Ubuntu: Incomplete Bug description: In case NM has failed to open any mobile data context, it will not re- try when rebooting the phone. This happened with a pre-paid SIM with no credit: opening a data context for it obviously failed. After adding credit to the SIM, I followed the instructions from the operator to reboot the phone to get data. However, after rebooting I had no mobile data. Taking a look to system settings, cellular data was set to Off and I was able to revert the situation marking the 2G/3G/4G option. Make NM retry the list of contexts in case no context was ever active on previous boot would make life easier for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349273/+subscriptions -- Mailing list: https://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 1269017] Re: Emojis not fully supported which results in blank received SMS messages
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/ttf-ancient-fonts /utopic-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1269017 Title: Emojis not fully supported which results in blank received SMS messages Status in Messaging App: Confirmed Status in “messaging-app” package in Ubuntu: In Progress Status in “ofono” package in Ubuntu: Fix Released Bug description: Android allows for adding emojis[1] to SMS messages. I'm told that iOS users are able to see these emojis. Our messaging app should also support displaying emojis. emojis appear to not requires MMS since when using Google Hangouts in the new android, when you add an emoji the hangouts app says 'Sent now via SMS'. Two things need to happen: 1. need to be able to correctly receive SMS messages with arbitrary emojis. Currently, on image 120, an SMS with a known emoji, eg, a smiley face, will display correctly when it is and is not accompanied with text. However, an SMS with an unknown emoji (eg, with a pinata) will show up as a blank SMS, even when the SMS has text. At a minimum, the text of the message should always be shown, perhaps with an 'unknown emoji' placeholder 2. need to be able to send SMS messages with emojis [1]http://en.wikipedia.org/wiki/Emoji To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1269017/+subscriptions -- Mailing list: https://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 1368243] [NEW] Scope consistently causes scope runner crash
Public bug reported: Ubuntu 14.10 r29 The Photos scope consistently causes scope runner crash. See attachment. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: scope runner crash https://bugs.launchpad.net/bugs/1368243/+attachment/4201440/+files/_usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash ** Description changed: Ubuntu 14.10 r29 - Consistenlty causes scope runner crash. See attachment. + The Photos scope consistently causes scope runner crash. See attachment. -- 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/1368243 Title: Scope consistently causes scope runner crash Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r29 The Photos scope consistently causes scope runner crash. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368243/+subscriptions -- Mailing list: https://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 1232633] Re: [system] Changing volume doesn't show feedback on the phone
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity8 (Ubuntu)
Status: New = In Progress
** Tags added: rtm14 touch-2014-09-25
--
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/1232633
Title:
[system] Changing volume doesn't show feedback on the phone
Status in Ubuntu UX bugs:
Fix Committed
Status in “unity8” package in Ubuntu:
In Progress
Bug description:
Not an indicator of volume status when it makes adjusting volume
(Nexus 4)
https://wiki.ubuntu.com/Sound#volume-keys: In addition, any of
those keys/buttons should play a subtle noise for you to gauge the
volume, and display a confirmation bubble with the icon of the primary
sound output at the current volume, a volume bar, and accessible text
“Sound muted” or “Volume {X}%” (for example, “Volume 75%”).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1232633/+subscriptions
--
Mailing list: https://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 1366391] Re: re-prompted for already-known password when switching networks
1) Connect to network A. 2) Connect to network B. 3) Re-connect to network A. 4) Attempt to re-connect to network B - this results in a password prompt (it shouldn't as I've already connected in (2)). 5) If I click cancel, I *do* connect to network B (not the original network A). -- 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/1366391 Title: re-prompted for already-known password when switching networks Status in “indicator-network” package in Ubuntu: Incomplete Bug description: When I re-connect to a known network, I am prompted for the WPA2 password. However, clicking cancel then successfully connects to this network! This is only happening for one of my networks. Not currently sure why since the other main network I use is also WPA2 protected and I'm not prompted for that networks password. I wonder if the re-prompt only occurs if the user attempts to connect to a different network to the first-joined network on boot (can't test atm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366391/+subscriptions -- Mailing list: https://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 1365497] Re: Inform user when a video format is not supported
@Renato: exactly. We must rely on GStreamer's URI decodebin to tell us what codecs the streams actually are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1365497 Title: Inform user when a video format is not supported Status in Media Hub: New Status in Media Player App: Triaged Status in “mediaplayer-app” package in Ubuntu: Confirmed Bug description: When a video format is not supported the result is at best a black or green screen, a black video with audio, or worst case a crash. Instead of this the player shouldn't try playing the video and inform the user that the format is not supported. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mediaplayer-app 0.20.5+14.10.20140820-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 4 15:07:06 2014 InstallationDate: Installed on 2014-09-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140904-030254) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1365497/+subscriptions -- Mailing list: https://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 1358399] Re: [webapp-container] short url patterns are considered invalid
** Changed in: webbrowser-app Status: In Progress = Fix Committed -- 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/1358399 Title: [webapp-container] short url patterns are considered invalid Status in Web Browser App: Fix Committed Status in “webbrowser-app” package in Ubuntu: New Bug description: URL patterns without a subdomain are considered invalid. Testcase: http?://ubuntu.com/* To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1358399/+subscriptions -- Mailing list: https://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 1342856] Re: No stopping messages shown during shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New = Confirmed -- 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/1342856 Title: No stopping messages shown during shutdown Status in “upstart” package in Ubuntu: Confirmed Bug description: ubuntu 14.04 server amd64 (running on a Mac Mini FWIW) During shutdown, no messages are displayed as daemons are being stopped. This makes it almost impossible to debug problems where a daemon is causing the shutdown to freeze. How to demonstrate: (1) Ctrl-F7 to show the virtual console where the bootup messages are. The last message seen is: * Stopping System V runlevel compatibility (2) Ctrl-F1 to get back to first virtual console. (3) Add a divider to the bootup messages: echo --- /dev/tty7 (4) sudo reboot The console switches to VC7, but in general, no further messages are displayed after the divider. Exception: when I have NFS packages installed, I do see * rpcbind terminating on signal. Restart with rpcbind -w but that's it. The only way I've been able to find out what's causing the system to hang at shutdown is to reinstall the system from scratch and keep adding packages until I find the one causing the problem. (Specifically it turned out to be avahi-daemon, but that's the subject of a separate bug report) At http://upstart.ubuntu.com/wiki/Debugging it says you can run initctl events to see what's happening, but that command-line option is not supported in the Upstart included in Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jul 16 17:11:16 2014 InstallationDate: Installed on 2014-07-16 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed root=/dev/mapper/hostname--vg-root ro SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) modified.conffile..etc.dhcp.dhcpd.conf: [modified] modified.conffile..etc.modprobe.d.blacklist.conf: [modified] modified.conffile..etc.sysctl.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2014-07-16T17:07:07.863506 mtime.conffile..etc.modprobe.d.blacklist.conf: 2014-07-16T16:26:11.252552 mtime.conffile..etc.sysctl.conf: 2014-07-16T16:22:29.256880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1342856/+subscriptions -- Mailing list: https://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 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Changed in: unity8 (Ubuntu) Assignee: Michał Sawicz (saviq) = Nick Dedekind (nick-dedekind) -- 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/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Indicator Location: New Status in Network Menu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1336715/+subscriptions -- Mailing list: https://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 1368246] [NEW] Installation of Apps not functioning
Public bug reported: Current behaviour (version r237) 1. Go to app store. 2. Select 'Flappy Bird' or 'XKCD Viewer' 3. Tap 'Install' 4. Watch progress bar fill to 100% 5. App install process ends here, progress remains at 100% 6. After some time (approx. 30 seconds) App info page refreshes and comes back blank (all content other than title area and background gone) 7. On navigating back it becomes apparent that App does not appear to have been installed and doesn't show up in Apps Scope. Expected behaviour: 1. Go to app store. 2. Select 'Flappy Bird' or 'XKCD Viewer' 3. Tap 'Install' 4. Watch progress bar fill to 100% 5. Install button switches back from progress bar to a button reading uninstall 6. App info updates to reflect that the App is now installed. 7. On returning to the Apps Scope newly installed App can be seen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368246 Title: Installation of Apps not functioning Status in “unity8” package in Ubuntu: New Bug description: Current behaviour (version r237) 1. Go to app store. 2. Select 'Flappy Bird' or 'XKCD Viewer' 3. Tap 'Install' 4. Watch progress bar fill to 100% 5. App install process ends here, progress remains at 100% 6. After some time (approx. 30 seconds) App info page refreshes and comes back blank (all content other than title area and background gone) 7. On navigating back it becomes apparent that App does not appear to have been installed and doesn't show up in Apps Scope. Expected behaviour: 1. Go to app store. 2. Select 'Flappy Bird' or 'XKCD Viewer' 3. Tap 'Install' 4. Watch progress bar fill to 100% 5. Install button switches back from progress bar to a button reading uninstall 6. App info updates to reflect that the App is now installed. 7. On returning to the Apps Scope newly installed App can be seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368246/+subscriptions -- Mailing list: https://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 1350806] Re: [switcher] Apps in spread should have icon to help distinguish between them
** Changed in: ubuntu-ux Status: Triaged = In Progress -- 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/1350806 Title: [switcher] Apps in spread should have icon to help distinguish between them Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: New Bug description: As summary, it is hard in spread browse between apps, many apps look the same at first glance, adding an app icon may help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350806/+subscriptions -- Mailing list: https://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 1368243] Re: Scope consistently causes scope runner crash
Please use apport-collect to upload the .crash file to launchpad for retracing. ** Package changed: unity8 (Ubuntu) = unity-scopes-api (Ubuntu) -- 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/1368243 Title: Scope consistently causes scope runner crash Status in “unity-scopes-api” package in Ubuntu: New Bug description: Ubuntu 14.10 r29 The Photos scope consistently causes scope runner crash. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1368243/+subscriptions -- Mailing list: https://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 1223795] Re: [Ubuntu shape] Inner highlight glow is not correctly rendered in Launcher icons
Launcher highlights are fixed now. Michael Zanetti removed the highlights from Ubuntu shapes (setting some property borderSource or smth to null) And then we applied our own graphics on top of blank ubuntu shape. So I mark this from ux point of view fixed. ** 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/1223795 Title: [Ubuntu shape] Inner highlight glow is not correctly rendered in Launcher icons Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: There are some shadows and highlights in Ubuntu shape. Currently light bottom highlight rendering is not pixel perfect in Launcher icons. The left side seems to be ok (or few pixels off as well?) but on right side there is some few pixels gap between the highlight and Ubuntu shape border. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1223795/+subscriptions -- Mailing list: https://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 1365497] Re: Inform user when a video format is not supported
@Jim Sorry I am not familiar with the new media-hub, but is the app using gstreamer directly to play videos? I am trying to understand how the app can test if the video is supported or not? In my point of view we should try to play the video and receive a reply saying that the video format is not supported. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1365497 Title: Inform user when a video format is not supported Status in Media Hub: New Status in Media Player App: Triaged Status in “mediaplayer-app” package in Ubuntu: Confirmed Bug description: When a video format is not supported the result is at best a black or green screen, a black video with audio, or worst case a crash. Instead of this the player shouldn't try playing the video and inform the user that the format is not supported. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mediaplayer-app 0.20.5+14.10.20140820-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 4 15:07:06 2014 InstallationDate: Installed on 2014-09-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140904-030254) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1365497/+subscriptions -- Mailing list: https://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
** Summary changed: - [dash, design] When searching in a scope, loading feedback is hidden by the keyboard + [dash] [design] When searching in a scope, loading feedback is hidden by the keyboard -- 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: New Status in “unity8” package in Ubuntu: Confirmed 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 1363214] Re: [System Settings] [design] allow PINs of variable length instead of just 4 digits
** Summary changed: - [System Settings, design] allow PINs of variable length instead of just 4 digits + [System Settings] [design] allow PINs of variable length instead of just 4 digits -- 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/1363214 Title: [System Settings] [design] allow PINs of variable length instead of just 4 digits Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: New Bug description: Currently when setting a PIN on the device, it must be 4 digits. This is artificially limiting. Other platforms (eg Android) allow longer PINs. It has always been my understanding that we should support Swipe, Passphrase and PIN where Passphrase and PIN can be arbitrarily long. However, once longer PINs are supported, we will have to add an Enter key. Right now, the lockscreen checks the PIN once 4 digits are added so that you don't have to press Enter. I guess this was done for usability, but would be a security issue because an attacker can easily determine the PIN length, which makes it easier to for an attacker to guess the PIN. Eg, if I have a 5 digit PIN set, then an attacker need only type '1' and know that the PIN is only five characters. Now, a PIN isn't strong to begin with and an automated attack could rather quickly brute force PINs, but we shouldn't make it easier for someone manually trying to guess the PIN. The passphrase lockscreen prompt correctly allows variable length passphrases and requires you to press Enter. I suggest moving the 'X' up t the left of '0' and an Enter symbol to the rigth of '0'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1363214/+subscriptions -- Mailing list: https://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 1338984] Re: [Launcher] Icon emblem implementation is not according to the current design
** 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/1338984 Title: [Launcher] Icon emblem implementation is not according to the current design Status in Ubuntu UX bugs: Fix Released Status in The Unity 8 shell: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: The emblem design has changed from the current semi-transparent to opaque ubuntu orange. Implementation needs updating. --- Desired solution: See the attached screenshot. For more precise implementation details and key parameters see the UX specification: https://docs.google.com/a/canonical.com/document/d/1rNCz_HZIGBNf0Lq568q_iYXWvgmZF6v1jC726gmwlfw/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1338984/+subscriptions -- Mailing list: https://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 1368243] Re: Scope consistently causes scope runner crash
opes_scoperunner.32011.crashsh# apport-cli _usr_lib_arm-linux- gnueabihf_unity-sc *** Error: Problem in scoperunner Sorry, the program scoperunner closed unexpectedly Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. -- 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/1368243 Title: Scope consistently causes scope runner crash Status in “unity-scopes-api” package in Ubuntu: New Bug description: Ubuntu 14.10 r29 The Photos scope consistently causes scope runner crash. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1368243/+subscriptions -- Mailing list: https://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 1364453] Re: Brightness setting does not persist across reboots
saviq, right now there doesn't seem to be any way to 'read' the brightness from u-s-c. So on startup, in order to know what the brightness level is, indicator-power calls u-s-c's setUserBrightness() to the default level suggested by powerd. If the brightness was stored as a readwrite property in a schema somewhere, then i-power and u-s-s could simply read it at startup. Moreover, it would allow u-s-s to decouple itself from i-power, as both could listen for schema changes to know when the brightness level changed. u-s-c doesn't emit userBrightnessChanged signals, so right now u-s-s delegates its brightness work to i-power so that they don't overwrite each other's changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1364453 Title: Brightness setting does not persist across reboots Status in “indicator-power” package in Ubuntu: Confirmed Status in “unity-system-compositor” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: When altering the brightness setting, it is always reset to the default value after a reboot. It is expected that changing the setting should persist across reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1364453/+subscriptions -- Mailing list: https://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 1355284] Re: Switching swipe directions should reverse app spread
** Changed in: ubuntu-ux Status: In Progress = Fix Committed ** Description changed: The new app spread is gorgeous, thank you! In general we try to ensure reversibility of transitions - if a user starts a gesture and changes their mind they should be able to reverse the gesture and exit the transition as long as they have not lifted their finger. In this case, a user swiping from the right who intends to toggle windows but overshoots (thereby entering the spread) should be able to change direction, move their finger back towards the right edge, returning to the toggle and then to the original app if they move their finger all the way off the right edge. + + --- + Desired solution + + User should be in control through the whole the gesture. We want to have + reversibility also after second commit point the same way we have for the first commit point in current implementation. + + This has now been captured also in the right edge documentation: + https://docs.google.com/a/canonical.com/document/d/1FC_- + 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# -- 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/1355284 Title: Switching swipe directions should reverse app spread Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: The new app spread is gorgeous, thank you! In general we try to ensure reversibility of transitions - if a user starts a gesture and changes their mind they should be able to reverse the gesture and exit the transition as long as they have not lifted their finger. In this case, a user swiping from the right who intends to toggle windows but overshoots (thereby entering the spread) should be able to change direction, move their finger back towards the right edge, returning to the toggle and then to the original app if they move their finger all the way off the right edge. --- Desired solution User should be in control through the whole the gesture. We want to have reversibility also after second commit point the same way we have for the first commit point in current implementation. This has now been captured also in the right edge documentation: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355284/+subscriptions -- Mailing list: https://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 1257082] Re: MAAS does not use NTP servers specified in DHCPD options
** Also affects: ntp (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1257082
Title:
MAAS does not use NTP servers specified in DHCPD options
Status in MAAS:
Invalid
Status in “isc-dhcp” package in Ubuntu:
Invalid
Status in “ntp” package in Ubuntu:
Confirmed
Status in “isc-dhcp” source package in Precise:
New
Status in “ntp” source package in Precise:
New
Status in “isc-dhcp” source package in Trusty:
New
Status in “ntp” source package in Trusty:
New
Status in “ntp” package in Debian:
New
Bug description:
[Impact]
MAAS-deployed systems *that do not have persistent RTCs* (unusual)
have difficulty with time and authentication, generally making these
nodes unusable.
[Workaround]
See comment #8.
[Original Description]
I have tried setting up NTP servers as DHCP options to MAAS nodes
because I am behind a proxy here at work that cannot contact
ntp.ubuntu.com. Here is the top of the dhcpd.conf file on on my MAAS
head node, maas01:
root@maas01:/etc/dhcp# less dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.0.0 netmask 255.255.0.0 {
option domain-name mgmt;
option domain-name-servers 192.168.255.254;
option routers 192.168.255.254;
pool {
range 192.168.0.1 192.168.255.253;
deny unknown-clients;
}
}
subnet 10.255.0.0 netmask 255.255.0.0 {
option domain-name maas;
option domain-name-servers 10.255.0.1;
option routers 10.255.0.1;
option ntp-servers 172.31.22.1, 172.31.23.1, 172.31.20.104;
next-server 10.255.0.1;
pool {
range 10.255.1.0 10.255.255.254;
deny unknown-clients;
}
}
I have also verified the parameter is being sent to a client’s DHCP
lease:
ubuntu@sled204n0:/var$ cat /var/lib/dhcp/dhclient.eth0.leases
lease {
interface eth0;
fixed-address 10.255.4.44;
option subnet-mask 255.255.0.0;
option routers 10.255.0.1;
option dhcp-lease-time 600;
option dhcp-message-type 5;
option domain-name-servers 10.255.0.1;
option dhcp-server-identifier 10.255.0.1;
option ntp-servers 172.31.22.1,172.31.23.1,172.31.20.104;
option domain-name maas;
renew 4 2000/01/06 19:40:51;
rebind 4 2000/01/06 19:40:51;
expire 4 2000/01/06 19:40:51;
}
Even so, the date on the target node is still incorrect.
ubuntu@sled204n0:/etc$ date
Thu Jan 6 19:52:29 UTC 2000
The ntpdate defaults are the following (unchanged from MAAS defaults):
ubuntu@sled204n0:/etc$ cat /etc/default/ntpdate
# The settings in this file are used by the program ntpdate-debian, but not
# by the upstream program ntpdate.
# Set to yes to take the server list from /etc/ntp.conf, from package ntp,
# so you only have to keep it in one place.
NTPDATE_USE_NTP_CONF=yes
# List of NTP servers to use (Separate multiple servers with spaces.)
# Not used if NTPDATE_USE_NTP_CONF is yes.
NTPSERVERS=ntp.ubuntu.com
# Additional options to pass to ntpdate
NTPOPTIONS=
And the DHCP generated NTP server file is correct:
ubuntu@sled204n0:/etc$ cat /var/lib/ntpdate/default.dhcp
# NTP server entries received from DHCP server
NTPSERVERS='172.31.22.1 172.31.23.1 172.31.20.104'
The culprit seems to be in how ntpdate-debian is programmed. the logic
ignores /var/lib/ntpdate/default.dhcp if /etc/default/ntpdate sets
NTPDATE_USE_NTP_CONF=yes (the default).
After examining the script further my recommendation would be for the
/etc/dhcp/dhclient-exit-hooks.d/ntpdate to create the file
/var/lib/ntp/ntp.conf.dhcp. By doing so ntpdate-debian will work
transparently with /etc/defaults/ntpdate and NTP servers advertised by
DHCPD.
-
(contents of /var/log/maas/* is 125MB in size, will post data from there if
requested)
# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==-==--==
ii maas 1.3+bzr1461+dfsg-0ubuntu2.2+tay.8
all Ubuntu MAAS Server
ii maas-cli 1.3+bzr1461+dfsg-0ubuntu2.2+tay.8
all Ubuntu MAAS Client Tool
[Touch-packages] [Bug 1368252] [NEW] Repetitious language during unistallation of Apps
Public bug reported: UX Testing Result: Participants did not know the purpose of the confirmation screen as they didn't read the small text question, and they thought it was uninstalling. The uninstall button showed up twice, and the way that we ask for confirmation is not standard, should be 'yes' or 'no', instead of 'Uninstall' and 'cancel', which are repetition of previous screen. Change uninstall confirmation text and buttons to read: Uninstall AppName? Yes No ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368252 Title: Repetitious language during unistallation of Apps Status in “unity8” package in Ubuntu: New Bug description: UX Testing Result: Participants did not know the purpose of the confirmation screen as they didn't read the small text question, and they thought it was uninstalling. The uninstall button showed up twice, and the way that we ask for confirmation is not standard, should be 'yes' or 'no', instead of 'Uninstall' and 'cancel', which are repetition of previous screen. Change uninstall confirmation text and buttons to read: Uninstall AppName? Yes No To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368252/+subscriptions -- Mailing list: https://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 1280032] Re: No IPE Launcher
You can add the launcher manually. Download the attached text file and save it to the folder /usr/share/applications. ** Attachment added: Launcher for IPE. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1280032/+attachment/4201454/+files/ipe.desktop -- 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/1280032 Title: No IPE Launcher Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: IPE (Drawing software) launcher cannot be found in Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1280032/+subscriptions -- Mailing list: https://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 1367289] Re: /usr/bin/mtp-server:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:operator:operator
This bug needs further verification. I am unable to reproduce it. Do you have a specific set of actions that can trigger this bug? ** Changed in: mtp (Ubuntu) Status: Confirmed = Triaged ** Changed in: mtp (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1367289 Title: /usr/bin/mtp- server:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:operator:operator Status in “mtp” package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mtp. This problem was most recently seen with version 0.0.4+14.10.20140904-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3ef58537a0d1933a36d4ee4e78008c708086dd8f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1367289/+subscriptions -- Mailing list: https://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 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Tags added: touch-2014-09-25 -- 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/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Indicator Location: New Status in Network Menu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
