[Touch-packages] [Bug 1309915] Re: foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone)
** Summary changed: - foreground app should keep wakelock open until actual suspend happens + foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone) -- 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/1309915 Title: foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone) Status in the base for Ubuntu mobile products: Confirmed Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Status in qtmir package in Ubuntu RTM: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: while apps that you put in the background are properly SIGSTOPed (this is easy to verify with a music streaming website atm (while the browser does not use media-hub it will/should stop playback)). An app that is in the foreground will try to play on when the system is suspended (easy to verify with the same method, music plays on but becomes stuttery if the browser was in the foreground. This indicates the system tries to suspend but the running app tries to keep it alive. Unity should send s SIGSTOP/SIGCONT sequence on suspend/resume to the app in foreground when the system goes into suspend and resumes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1309915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370259] Re: apport fails to collect nvram specific information -- attach_root_command_outputs() does not work for binary data
Hello bugproxy, or anyone else affected, Accepted apport into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.14.7-0ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apport (Ubuntu Utopic) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1370259 Title: apport fails to collect nvram specific information -- attach_root_command_outputs() does not work for binary data Status in apport package in Ubuntu: Fix Released Status in apport source package in Utopic: Fix Committed Bug description: ---Problem Description--- apport fails to collect nvram specific information ---uname output--- 3.16.0-10-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 14.10 in Power non-virtualized environment. 2) Install apport package 3) Run following command to verify if apport collects power specific information. apport-cli -f -p linux-generic --save=/home/sachin/linux.apport The command fails with following error : root@lep8d:/home/sachin# apport-cli -f -p linux-generic --save=/home/sachin/linux.apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...tar: Removing leading `/' from member names ERROR: hook /usr/share/apport/general-hooks/powerpc.py crashed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook symb['add_info'](report, ui) File /usr/share/apport/general-hooks/powerpc.py, line 72, in add_info 'nvram': 'cat /dev/nvram', File /usr/lib/python3/dist-packages/apport/hookutils.py, line 469, in attach_root_command_outputs buf = f.read().strip() File /usr/lib/python3.4/codecs.py, line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 1: invalid start byte ... root@lep8d:/home/sachin# Userspace tool common name: apport Following version of apport is installed. root@lep8d:/home/sachin# dpkg --list | grep apport ii apport 2.14.7-0ubuntu1 all automatically generate crash reports for debugging ii apport-symptoms0.20 all symptom scripts for apport ii python-apport 2.14.7-0ubuntu1 all Python library for Apport crash report handling ii python3-apport 2.14.7-0ubuntu1 all Python 3 library for Apport crash report handling root@lep8d:/home/sachin# Looking at the code we are doing a cat /dev/nvram to the apport output file which doesn't sounds right to me. I would think using the function add_tar() creating a tar file and copying the content as a ascii file at end of apport output file more appropriate. One dummy question remaining, how getting the tar file from the ascii output file if we need to ? ( that's also true to validate the content of the DeviceTree tar file). Would suggest following patch: --- powerpc.py2014-09-10 10:28:18.824002770 -0400 +++ powerpc.py.old2014-09-04 06:33:16.0 -0400 @@ -69,8 +69,8 @@ 'cpu_runmode': 'ppc64_cpu --run-mode', 'cpu_freq': 'ppc64_cpu --frequency', 'cpu_dscr': 'ppc64_cpu --dscr', +'nvram': 'cat /dev/nvram', }) -add_tar(report, '/dev/nvram', 'nvram.tar') attach_file_if_exists(report, '/var/log/platform') if ispSeries and not isPowerKVM: thanks diff -urN powerpc.py.old powerpc.py --- powerpc.py.old2014-09-04 06:33:16.0
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
Hello Egon, or anyone else affected,
Accepted gdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm/3.10.0.1-0ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: gdm (Ubuntu Utopic)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in gdm package in Ubuntu:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in gdm source package in Trusty:
Fix Committed
Status in lightdm source package in Trusty:
Fix Committed
Status in gdm source package in Utopic:
Fix Committed
Status in lightdm source package in Utopic:
Fix Committed
Status in gdm package in Debian:
New
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408772] [NEW] Need (temporary) rights for applications to list directories under /media/phablet to detect the SD card
Public bug reported: The camera app does not have an API (yet) to know which folder the SD card is mounted under. For now we guess by listing the folders under /media/phablet which is an *ok* temporary solution but the app does not have the rights to do so. Can we add (temporarily) that right to apps that have picture_files and video_files in their policy groups? ** Affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1408772 Title: Need (temporary) rights for applications to list directories under /media/phablet to detect the SD card Status in apparmor-easyprof-ubuntu package in Ubuntu: New Bug description: The camera app does not have an API (yet) to know which folder the SD card is mounted under. For now we guess by listing the folders under /media/phablet which is an *ok* temporary solution but the app does not have the rights to do so. Can we add (temporarily) that right to apps that have picture_files and video_files in their policy groups? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1408772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card
Depends on https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof- ubuntu/+bug/1408772 ** Changed in: camera-app Status: Fix Released = In Progress -- 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/1392368 Title: Support storing and viewing photos on an SD card Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in Gallery App: In Progress Status in camera-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in camera-app package in Ubuntu RTM: In Progress Status in ciborium package in Ubuntu RTM: New Status in gallery-app package in Ubuntu RTM: In Progress Bug description: If an SD card is present we will use it as extended storage for the device. The camera and gallery apps need to be able to access this storage. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1392368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408766] Re: GUI way of managing guest account
** Package changed: xorg (Ubuntu) = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1408766 Title: GUI way of managing guest account Status in lightdm package in Ubuntu: Triaged Bug description: It would be really good if there was a GUI interface (probably in User Accounts settings) with the option to disable the guest account. So that instead of having to run a command in Terminal (or create a new config file) such as this one: sudo sh -c 'printf [SeatDefaults]\nallow-guest=false\n /usr/share/lightdm/lightdm.conf.d/50-no-guest.conf' And then having to delete the /usr/share/lightdm/lightdm.conf.d/50-no- guest.conf file to get the guest account back, it would be really good if there could be an option to do this somewhere in the user interface so that you don't have to do it manually. My OS information: Description: Ubuntu 14.10 Release: 14.10 Xorg package version information: xorg: Installed: 1:7.7+7ubuntu2 Candidate: 1:7.7+7ubuntu2 Version table: *** 1:7.7+7ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1408766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card
apparmor-easyprof-ubuntu needs another change due to this denial: Jan 8 17:53:58 ubuntu-phablet kernel: [99908.971037]type=1400 audit(1420746838.140:316): apparmor=DENIED operation=open profile=com.ubuntu.camera_camera_3.0.0.latest name=/media/phablet/ pid=26014 comm=camera-app requested_mask=r denied_mask=r fsuid=32011 ouid=0 The media is in /media/user/label/Pictures|Music|Video. There is supposed to be a way for an app like the camera to find out the 'label', but that doesn't exist right now so the camera has to list the directory contents of /media/user to get it. As such, apparmor-easyprof-ubuntu needs to (temporarily) add this rule: /media/*/ r, ** Also affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Status: New = Triaged ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided = High ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Assignee: (unassigned) = Jamie Strandboge (jdstrand) ** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM) Importance: Undecided = High ** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM) Status: New = Triaged ** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM) Assignee: (unassigned) = Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1392368 Title: Support storing and viewing photos on an SD card Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in Gallery App: In Progress Status in apparmor-easyprof-ubuntu package in Ubuntu: Triaged Status in camera-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu RTM: Triaged Status in camera-app package in Ubuntu RTM: In Progress Status in ciborium package in Ubuntu RTM: New Status in gallery-app package in Ubuntu RTM: In Progress Bug description: If an SD card is present we will use it as extended storage for the device. The camera and gallery apps need to be able to access this storage. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1392368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367188] Re: [OOBE] [design] First-run setup Wi-Fi screen is useless when no networks detected
** Summary changed: - [OOBE] First-run setup Wi-Fi screen is useless when no networks detected + [OOBE] [design] First-run setup Wi-Fi screen is useless when no networks detected -- 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/1367188 Title: [OOBE] [design] First-run setup Wi-Fi screen is useless when no networks detected Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: Confirmed Bug description: 1. Wipe the phone. 2. Go somewhere that no Wi-Fi networks are in range. 3. Navigate the first-run setup to the Wi-Fi screen. What you see: A screen containing nothing except a Wi-Fi header, an Available networks header, and Back and Skip buttons. What you should see: Something more useful. For example, skip this screen entirely, or at least explicitly explain that no Wi-Fi networks are in range right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
