[Touch-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo
@Víctor, @Tony:
Regarding roaming, there are already mechanisms that check the content
of SIM files and the registered network that should prevent the
registration state to be roaming, even in these cases when we bounce
between different networks.
Víctor, could you please check if you see a roaming indicator on the
screen at any time? If that is the case, then that is an ofono bug.
Otherwise, my best bet here is NetworkManager not trying to attach to
the data network after a network change, as Tony has suggested above.
--
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/1371032
Title:
Cannot send MMS from Yoigo
Status in “messaging-app” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “nuntium” package in Ubuntu:
In Progress
Status in “ofono” package in Ubuntu:
Invalid
Bug description:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
AccessPointName = internet
Name = Yoigo Internet
Password =
Protocol = ip
IPv6.Settings = { }
Type = internet
Active = 1
Username =
Settings = { DomainNameServers=217.168.13.34,46.6.113.2,
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31
Interface=ccmni0 }
[ /ril_0/context2 ]
AccessPointName = mms
MessageCenter = http://mmss/
Name = Yoigo MMS
Password =
Protocol = ip
MessageProxy = 193.209.134.141:80
IPv6.Settings = { }
Type = mms
Active = 0
Username =
Settings = { }
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not
attached
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
/ril_0 1
Additional info:
- I didn't see any error in the messaging app.
- Couldn't send nor receive MMS.
- 3G connection is activated, but usually after a reboot. After a while, it
looses it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
I can confirm that QStandardPaths::writableLocation() is the main cause this and bug #1359831 is happening. The method checks whether the path specified is writable, and returns an empty string if cannot chmod +w on the path. The log we captured yesterday was not visible so far, therefore we diid not suspected that. Previous tests with the branch were working on device with any arbitrary sample app. Adding some logs to StateSaver resulted in the following: QStandardPaths: wrong permissions on runtime directory /run/user/32011 [StateSaver] PATH /com.ubuntu.camera/statesaver.appstate Which means that the state file was about to be created in the root folder due to QStandardPaths::writableLocation() returned empty string. -- 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/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Bug description: build 212 The StateSaver is not working anymore on devices, so apps saved state is no longer restored when they are relaunched after being killed by oom killer (or manually via kill -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376461] Re: unity8 AP test failures with Mir 0.8.0 silo
It's usually helpful, when a bug is weaving through a complex software stack of multiple projects, to start with the assistance of the developers at the top of the stack (Unity8). Because it's not immediately obvious what (if anything) in Mir is at play yet. -- 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/1376461 Title: unity8 AP test failures with Mir 0.8.0 silo Status in Mir: New Status in “unity8” package in Ubuntu: New Bug description: The following unity8 AP tests are failing with the Mir 0.8.0 silo PPA : unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_app_icon_on_dash_must_focus_it unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_focus unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_dash_icon_must_unfocus_application It's easily reproducible. This was seen on the stable device with ubuntu-touch/ubuntu-rtm/14.09-proposed plus the 0.8.0 rtm-20 silo. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376571] [NEW] After login, gcr-prompter pops up several times in a row, never accepting my passwords
Public bug reported: The dialog doesn't accept any of my passwords, so I have to cancel it 4 times in a row. I haven't noticed anything not working, and nothing asks for the password ever again. Also, the dialog isn't very clear on *which* password it's asking for. It just lists my email address -- which I don't have configured as an online account in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gcr 3.12.2-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 2 08:31:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (322 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gcr UpgradeStatus: Upgraded to utopic on 2014-09-16 (15 days ago) ** Affects: gcr (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1376571 Title: After login, gcr-prompter pops up several times in a row, never accepting my passwords Status in “gcr” package in Ubuntu: Confirmed Bug description: The dialog doesn't accept any of my passwords, so I have to cancel it 4 times in a row. I haven't noticed anything not working, and nothing asks for the password ever again. Also, the dialog isn't very clear on *which* password it's asking for. It just lists my email address -- which I don't have configured as an online account in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gcr 3.12.2-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 2 08:31:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (322 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gcr UpgradeStatus: Upgraded to utopic on 2014-09-16 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1376571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359831] Re: Apps incorrectly perform a chmod on XDG_RUNTIME_DIR
This looks like the problem of using QStandardPaths::writableLocation().
The relevant code snipped from
QStandardPaths::writableLocation(RuntimeLocation):
// and he MUST be the only one having read and write access to it. Its
Unix access mode MUST be 0700.
QFile file(xdgRuntimeDir);
const QFile::Permissions wantedPerms = QFile::ReadUser |
QFile::WriteUser | QFile::ExeUser;
if (file.permissions() != wantedPerms
!file.setPermissions(wantedPerms)) {
qWarning(QStandardPaths: wrong permissions on runtime directory
%s, qPrintable(xdgRuntimeDir));
return QString();
}
where QFile::permissions() drills down to ask for permissions using
QFileSystemMetaData::doStat(). This seems to cause the chmod issue we
have.
Not sure whether the failure described in this bug is caused by the
Toolkit's StateSaver services, but in case bug #1363112 fix solves this
issue, it can be marked as resolved. In StateSaver we have similar
issues as here, so at least I suspect the root cause is the same as we
have in the other bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1359831
Title:
Apps incorrectly perform a chmod on XDG_RUNTIME_DIR
Status in Camera App:
Confirmed
Status in Ubuntu Reminders app:
Invalid
Status in Sudoku game for Ubuntu Touch:
Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
Confirmed
Bug description:
From bug #1351041:
[Thu Jul 31 21:04:20 2014] type=1400 audit(1406837062.464:97):
apparmor=DENIED operation=chmod
profile=com.ubuntu.reminders_reminders_0.5.203 name=/run/user/32011/
pid=12954 comm=reminders requested_mask=w denied_mask=w fsuid=32011
ouid=32011
From irc:
Aug 21 15:47:20 ubuntu-phablet kernel: [ 251.843308] type=1400
audit(1408636040.346:137): apparmor=DENIED operation=chmod
profile=com.ubuntu.camera_camera_3.0.0.355 name=/run/user/32011/ pid=4172
comm=camera-app requested_mask=w denied_mask=w fsuid=32011 ouid=32011
AppArmor policy is correct on this denial-- apps should not be able to
change the permissions on the /run/user/32011/ (XDG_RUNTIME_DIR)
directory. I filed this against camera-app and reminders, but my guess
is this is an underlying library that is causing this. I don't know if
the denial is causing errors with the app, but it is causing confusion
for users and developers who see the denial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1359831/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376571] Re: After login, gcr-prompter pops up several times in a row, never accepting my passwords
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcr (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1376571 Title: After login, gcr-prompter pops up several times in a row, never accepting my passwords Status in “gcr” package in Ubuntu: Confirmed Bug description: The dialog doesn't accept any of my passwords, so I have to cancel it 4 times in a row. I haven't noticed anything not working, and nothing asks for the password ever again. Also, the dialog isn't very clear on *which* password it's asking for. It just lists my email address -- which I don't have configured as an online account in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gcr 3.12.2-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 2 08:31:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (322 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gcr UpgradeStatus: Upgraded to utopic on 2014-09-16 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1376571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376571] Re: After login, gcr-prompter pops up several times in a row, never accepting my passwords
I only see one prompt, not many. I don't reboot regularly so don't often see it, but have seen it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1376571 Title: After login, gcr-prompter pops up several times in a row, never accepting my passwords Status in “gcr” package in Ubuntu: Confirmed Bug description: The dialog doesn't accept any of my passwords, so I have to cancel it 4 times in a row. I haven't noticed anything not working, and nothing asks for the password ever again. Also, the dialog isn't very clear on *which* password it's asking for. It just lists my email address -- which I don't have configured as an online account in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gcr 3.12.2-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 2 08:31:13 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (322 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gcr UpgradeStatus: Upgraded to utopic on 2014-09-16 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1376571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376315] Re: Unable to add image in Yelp webapp, but can on m.yelp.com in the browser
I’m seeing the following related denial in the syslog: apparmor=DENIED operation=dbus_method_call bus=session path=/ interface=com.ubuntu.content.dbus.Service member=KnownSourcesForType mask=send name=com.ubuntu.content.dbus.Service pid=3489 profile=com.ubuntu.yelp_webapp-yelp_1.0.26 peer_pid=3751 peer_profile=unconfined -- 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/1376315 Title: Unable to add image in Yelp webapp, but can on m.yelp.com in the browser Status in “webbrowser-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the 'Yelp' application 2. From the home screen click on a review (under Hot New Businesses Nearby) 3. Click on the 'Add Photo' button on the businesses page Expected result: Content hub opens and offers e.g. Camera and Gallery as sources Actual result: Content hub opens with message 'Sorry there aren't currently any apps installed that can provide this type of content' Repeating the same test case by replacing step 1 with 'Open the browser and navigate to m.yelp.com' gives the Expected result ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140926-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Oct 1 15:17:45 2014 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141001-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1376315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376461] Re: unity8 AP test failures with Mir 0.8.0 silo
Just a sanity check to see if anything focus-related has changed in Mir 0.8; the answer is yes. But it's not clear if that change is related: http://bazaar.launchpad.net/~mir-team/mir/development- branch/revision/1887 -- 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/1376461 Title: unity8 AP test failures with Mir 0.8.0 silo Status in Mir: New Status in “unity8” package in Ubuntu: New Bug description: The following unity8 AP tests are failing with the Mir 0.8.0 silo PPA : unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_app_icon_on_dash_must_focus_it unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_focus unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_dash_icon_must_unfocus_application It's easily reproducible. This was seen on the stable device with ubuntu-touch/ubuntu-rtm/14.09-proposed plus the 0.8.0 rtm-20 silo. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo
I have just noticed that the output of monitor-ofono is part of the
logs, and I see that network status actually gets into roaming state.
But, it is in very short time windows:
2014-09-26 20:11:18,643 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 20:11:19,323 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 20:16:31,743 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 20:16:31,803 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:03:43,743 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:03:43,779 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:10:58,077 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:10:58,104 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:18:20,377 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:18:20,411 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:26:05,503 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:26:05,535 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:34:39,565 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:34:39,598 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 22:53:31,359 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 22:53:31,398 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 23:00:20,671 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 23:00:20,732 {NetworkRegistration} [/ril_0] Status = registered
...
2014-09-26 23:07:00,161 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 23:07:00,185 {NetworkRegistration} [/ril_0] Status = registered
This does not really affect the reasoning above, imho the main problem here is
NetworkManager not attaching after coming back to registered state. However,
these Status flash changes can be annoying and the user could potentially see
a flickering roaming indicator in the GUI. I would like to get more traces for
this, Víctor, could it be possible to do this:
$ phablet-shell
$ sudo su
# stop ofono
# export OFONO_RIL_DEVICE=mtk OFONO_RIL_NUM_SIM_SLOTS=2
# export OFONO_RIL_HEX_TRACE= export OFONO_RIL_TRACE=
# ofonod -n -d -P stktest,provision,sap,udev,dun,smart,hfp
/tmp/ofono_log.txt
# python3 -u /usr/share/ofono/scripts/monitor-ofono /tmp/monitor-ofono.txt
walk around so the phone switches networks, and then attach the logs
here?
--
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/1371032
Title:
Cannot send MMS from Yoigo
Status in “messaging-app” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “nuntium” package in Ubuntu:
In Progress
Status in “ofono” package in Ubuntu:
Invalid
Bug description:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
AccessPointName = internet
Name = Yoigo Internet
Password =
Protocol = ip
IPv6.Settings = { }
Type = internet
Active = 1
Username =
Settings = { DomainNameServers=217.168.13.34,46.6.113.2,
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31
Interface=ccmni0 }
[ /ril_0/context2 ]
AccessPointName = mms
MessageCenter = http://mmss/
Name = Yoigo MMS
Password =
Protocol = ip
MessageProxy = 193.209.134.141:80
IPv6.Settings = { }
Type = mms
Active = 0
Username =
Settings = { }
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not
attached
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
/ril_0 1
Additional info:
- I didn't see any error in the messaging app.
- Couldn't send nor receive MMS.
- 3G connection is activated, but usually after a reboot. After a while, it
looses it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300709] Re: Empty areas in scopes produce haptics feedback without triggering any other action
Why is this marked incomplete? The issue is still valid. To reproduce tap on an empty space in the dash. It will produce haptics feedback even though no action is happening. ** 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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: New Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323960] Re: Camera does not work on device on Qt 5.3 (works on desktop)
** Changed in: qtvideo-node (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 qtvideo-node in Ubuntu. https://bugs.launchpad.net/bugs/1323960 Title: Camera does not work on device on Qt 5.3 (works on desktop) Status in “qtvideo-node” package in Ubuntu: Fix Released Bug description: Possibly related to the media playing bug #1321319, camera is just black on Qt 5.3 and does not allow taking pictures. camera-app does work on the desktop however with Qt 5.3 too, although there's a strong green tint which may be give some hint on what's wrong on armhf/Android too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtvideo-node/+bug/1323960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1321319] Re: mediaplayer video playback does not work with Qt 5.3 on armhf
** Changed in: qtvideo-node (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 qtvideo-node in Ubuntu. https://bugs.launchpad.net/bugs/1321319 Title: mediaplayer video playback does not work with Qt 5.3 on armhf Status in Media Hub: Invalid Status in “qtvideo-node” package in Ubuntu: Fix Released Bug description: With Qt 5.3 the video player does start its UI but the video screen says black and the playback doesn't start. media-hub.log: http://pastebin.ubuntu.com/7492720/ After GST_DEBUG=*:4 CORE_UBUNTU_MEDIA_SERVICE_VIDEO_SINK_NAME=mirsink media-hub-server: http://pastebin.ubuntu.com/7492743/ + http://pastebin.ubuntu.com/7492754/ --- Refer to kept-update info on the front page of https://launchpad.net /~canonical-qt5-edgers/+archive/qt5-beta2 regarding where/how to get Qt 5.3. Note that it's not necessarily that PPA itself. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1321319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376461] Re: unity8 AP test failures with Mir 0.8.0 silo
Working from the test failures downward, I can't yet see where or if Unity8 gets any focus notifications from Mir at all: Unity8: assert_current_focused_application self.main_window.get_current_focused_app_id self._get_shell().focusedApplicationId ApplicationManager.focusedApplicationId ApplicationManager::focusApplication ApplicationInfo::focused() ApplicationInfo::setFocused() ... ? Instead it appears that Unity8 and QtMir dictate focus between themselves. This makes me suspicious of QtMir which has received two focus-related changes in the past 24 hours. ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: mir Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376461 Title: unity8 AP test failures with Mir 0.8.0 silo Status in Mir: Incomplete Status in Qt integration with the Mir display server: New Status in “unity8” package in Ubuntu: New Bug description: The following unity8 AP tests are failing with the Mir 0.8.0 silo PPA : unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_app_icon_on_dash_must_focus_it unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_focus unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_dash_icon_must_unfocus_application It's easily reproducible. This was seen on the stable device with ubuntu-touch/ubuntu-rtm/14.09-proposed plus the 0.8.0 rtm-20 silo. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375805] Re: Lightdm fails to start in VirtualBox
@ apw - always nice to confirm something's working - updated a non- booting install - got the new systemd - boots properly now - thanks -- 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/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Fix Released Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1232130] Re: Uninstalling an app doesn't stop it
Thanks Colin and sorry for the trouble. I looked into this now and reworked the way that the stopping happens. It seems to be reliable now and gets the correct appid that is then passed to app-launch-stop. However the app still does not stop because ubuntu-app-stop needs to talk to the users session bus. When click runs as root (or via PK) it does not have access to it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1232130 Title: Uninstalling an app doesn't stop it Status in “click” package in Ubuntu: Triaged Status in “ubuntu-touch-meta” package in Ubuntu: Fix Released Bug description: Hi, Launch an installed app, uninstall it. Not only is it still listed in the list of installed apps (bug #1232129), it's also still in the running app lists, and if you press on the installed app icon or slide right, you get back to the running app. I think any running instance of this app should be killed along the removal. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1232130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376054] Re: Scope Registry fails when aggregating an aggregator
** Tags added: touch-2014-10-09 -- 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/1376054 Title: Scope Registry fails when aggregating an aggregator Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: When trying to aggregate and aggreagator scope. many many queries are fired off at once, which seems to cause the scope registry to hang. To reproduce: 1) Install krillin rtm image 2) Install attached dashboard.click 3) Note scope registry seems to hang when adding News to the Dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375718] Re: Manage Dash page doesn't refresh when scopes are installed or removed
** Tags removed: touch-2014-10-16 ** Tags added: touch-2014-10-09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1375718 Title: Manage Dash page doesn't refresh when scopes are installed or removed Status in “unity-scopes-shell” package in Ubuntu: In Progress Bug description: The 'All' section of Manage Dash page is not refreshed when new scopes are installed or uninstalled. To reproduce, install a scope from a click package - it will appear in Manage Dash only after reboot. This is most likely caused by Scopes::getScopeById() returning null for scopes scope, which breaks the refreshing of results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1375718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376461] Re: unity8 AP test failures with Mir 0.8.0 silo
P.S. Why are we testing 0.8 with RTM? I thought RTM should be staying on a stable and proven series (0.7)? -- 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/1376461 Title: unity8 AP test failures with Mir 0.8.0 silo Status in Mir: Incomplete Status in Qt integration with the Mir display server: New Status in “unity8” package in Ubuntu: New Bug description: The following unity8 AP tests are failing with the Mir 0.8.0 silo PPA : unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_app_icon_on_dash_must_focus_it unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_focus unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_click_dash_icon_must_unfocus_application It's easily reproducible. This was seen on the stable device with ubuntu-touch/ubuntu-rtm/14.09-proposed plus the 0.8.0 rtm-20 silo. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376500] Re: [regression] thumbnails and image previews displayed wrong
This is a bug in the camera app. It produces jpg files whose exif thumbnails have incorrect aspect ratio. Attached is a raw thumbnail extracted from a jpg produced with the camera. Thumbnailer uses the embedded exif image if it exists (this is the change mentioned above) because scaling the full image is way too slow and resource hungry. ** Attachment added: incorrect_aspect_thumb.jpg https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1376500/+attachment/4222125/+files/incorrect_aspect_thumb.jpg ** Changed in: camera-app Status: Invalid = Confirmed ** Changed in: thumbnailer (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1376500 Title: [regression] thumbnails and image previews displayed wrong Status in Camera App: Confirmed Status in Gallery App: Invalid Status in Ubuntu UI Toolkit: Invalid Status in “thumbnailer” package in Ubuntu: Invalid Bug description: build 76 rtm-proposed on krillin Take a picture with camera-app swipe to the right to display it it looks squashed and like it's being displayed at the wrong aspect ration open the gallery-app and view the photo and it looks equally bad share the photo to messaging-app, and the preview of the photo is black copy the photo to your desktop and open there and the photo looks fine these are all new regressions, not sure what layer it's in bug guessing a low layer as gallery, camera and messaging-app have not changed in this regard To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1376500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372276] Re: Nested server crashes with SIGSEGV on shutdown in eglDestroyContext()
** Changed in: mir/0.7 Status: Fix Committed = Fix Released -- 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/1372276 Title: Nested server crashes with SIGSEGV on shutdown in eglDestroyContext() Status in Mir: Fix Committed Status in Mir 0.7 series: Fix Released Status in “mir” package in Ubuntu: Triaged Bug description: Start a host server and nested server. Ctrl+C ... crash. Test case: 1. sudo -s sh -c bin/mir_demo_server_minimal -f /tmp/outer sleep 2 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. Ctrl+C (gdb) bt #0 0x7f9e628cb2e6 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #1 0x7f9e628c313a in eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7f9e6453c9ef in mir::graphics::EGLContextStore::~EGLContextStore ( this=0x113a7a0, __in_chrg=optimised out) at /home/dan/bzr/mir/dev/src/platform/graphics/egl_resources.cpp:40 #3 0x7f9e648e8b54 in mir::graphics::SurfacelessEGLContext::~SurfacelessEGLContext (this=0x113a770, __in_chrg=optimised out) at /home/dan/bzr/mir/dev/src/server/graphics/surfaceless_egl_context.cpp:175 #4 0x7f9e648e8ba0 in mir::graphics::SurfacelessEGLContext::~SurfacelessEGLContext (this=0x113a770, __in_chrg=optimised out) at /home/dan/bzr/mir/dev/src/server/graphics/surfaceless_egl_context.cpp:178 #5 0x7f9e64869032 in std::default_deletemir::graphics::GLContext::operator() (this=0x1255058, __ptr=0x113a770) at /usr/include/c++/4.9/bits/unique_ptr.h:76 #6 0x7f9e648675b3 in std::unique_ptrmir::graphics::GLContext, std::default_deletemir::graphics::GLContext ::~unique_ptr (this=0x1255058, __in_chrg=optimised out) at /usr/include/c++/4.9/bits/unique_ptr.h:236 #7 0x7f9e6487598f in mir::scene::GLPixelBuffer::~GLPixelBuffer ( this=0x1255050, __in_chrg=optimised out) at /home/dan/bzr/mir/dev/src/server/scene/gl_pixel_buffer.cpp:66 #8 0x7f9e648732df in __gnu_cxx::new_allocatormir::scene::GLPixelBuffer::destroymir::scene::GLPixelBuffer (this=0x1255050, __p=0x1255050) at /usr/include/c++/4.9/ext/new_allocator.h:124 #9 0x7f9e64872f4d in std::allocator_traitsstd::allocatormir::scene::GLPixelBuffer ::_S_destroymir::scene::GLPixelBuffer (__a=..., __p=0x1255050) at /usr/include/c++/4.9/bits/alloc_traits.h:282 #10 0x7f9e64872b25 in std::allocator_traitsstd::allocatormir::scene::GLPixelBuffer ::destroymir::scene::GLPixelBuffer (__a=..., __p=0x1255050) at /usr/include/c++/4.9/bits/alloc_traits.h:411 #11 0x7f9e64871d4f in std::_Sp_counted_ptr_inplacemir::scene::GLPixelBuffer, std::allocatormir::scene::GLPixelBuffer, (__gnu_cxx::_Lock_policy)2::_M_dispose (this=0x1255040) at /usr/include/c++/4.9/bits/shared_ptr_base.h:524 #12 0x7f9e647c7980 in std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_release (this=0x1255040) at /usr/include/c++/4.9/bits/shared_ptr_base.h:149 #13 0x7f9e647c76e9 in std::__shared_count(__gnu_cxx::_Lock_policy)2::~__shared_count (this=0xf782a0, __in_chrg=optimised out) at /usr/include/c++/4.9/bits/shared_ptr_base.h:666 #14 0x7f9e64866368 in std::__shared_ptrmir::scene::PixelBuffer, (__gnu_cxx::_Lock_policy)2::~__shared_ptr (this=0xf78298, __in_chrg=optimised out) at /usr/include/c++/4.9/bits/shared_ptr_base.h:914 #15 0x7f9e64866382 in std::shared_ptrmir::scene::PixelBuffer::~shared_ptr (this=0xf78298, __in_chrg=optimised out) at /usr/include/c++/4.9/bits/shared_ptr.h:93 #16 0x7f9e64892acc in mir::scene::ThreadedSnapshotStrategy::~ThreadedSnapshotStrategy (this=0xf78290, __in_chrg=optimised out) at /home/dan/bzr/mir/dev/src/server/scene/threaded_snapshot_strategy.cpp:122 #17 0x7f9e6487329b in __gnu_cxx::new_allocatormir::scene::ThreadedSnapshotStrategy::destroymir::scene::ThreadedSnapshotStrategy (this=0xf78290, __p=0xf78290) at /usr/include/c++/4.9/ext/new_allocator.h:124 #18 0x7f9e64872ef5 in std::allocator_traitsstd::allocatormir::scene::ThreadedSnapshotStrategy ::_S_destroymir::scene::ThreadedSnapshotStrategy ( __a=..., __p=0xf78290) at /usr/include/c++/4.9/bits/alloc_traits.h:282 #19 0x7f9e64872ac1 in std::allocator_traitsstd::allocatormir::scene::ThreadedSnapshotStrategy ::destroymir::scene::ThreadedSnapshotStrategy ( __a=..., __p=0xf78290) at /usr/include/c++/4.9/bits/alloc_traits.h:411 #20 0x7f9e64871bcf in std::_Sp_counted_ptr_inplacemir::scene::ThreadedSnapshotStrategy, std::allocatormir::scene::ThreadedSnapshotStrategy, (__gnu_cxx::_Lock_policy)2::_M_dispose (this=0xf78280) at /usr/include/c++/4.9/bits/shared_ptr_base.h:524 #21 0x7f9e647c7980 in std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_release (this=0xf78280) at
[Touch-packages] [Bug 1372300] Re: [regression] Moving/resizing clients in a nested server is very jerky/stuttery
** Changed in: mir/0.7 Status: Fix Committed = Fix Released -- 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/1372300 Title: [regression] Moving/resizing clients in a nested server is very jerky/stuttery Status in Mir: Fix Committed Status in Mir 0.7 series: Fix Released Status in “mir” package in Ubuntu: Triaged Bug description: [regression] Moving/resizing clients in a nested server is VERY jerky/stuttery. Test case: 1. sudo -s sh -c bin/mir_demo_server_minimal -f /tmp/outer sleep 2 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. sudo bin/mir_demo_client_egltriangle -m /tmp/inner 3. Move/resize it with Alt+left/middle_buttons Expected: The client moves/resizes smoothly Observed: Severe jerkiness To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1372300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375349] Re: Can't launch videos on mako utopic #261
** Tags removed: lt-age-20140929 ** Tags added: lt-date-20140929 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1375349 Title: Can't launch videos on mako utopic #261 Status in Media Hub: Fix Released Status in Unity Media Scanner Scope: Fix Released Status in “unity-scope-mediascanner” package in Ubuntu: Fix Released Bug description: Copy videos to device. Scroll to video scope Tap on video Nothing happens. Crash file created, video doesn't play. ProblemType: RecoverableProblem DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140926-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf BadURL: file:///home/phablet/Videos/big_buck_bunny_480p_MPEG4_MP3_25fps_1600K.AVI CurrentDesktop: Unity Date: Mon Sep 29 17:23:14 2014 DuplicateSignature: url-dispatcher-bad-url ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2014-09-29 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-020204) LocalLibraries: /android/system/lib/libm.so /android/system/lib/liblog.so /android/system/lib/libsync.so /android/system/lib/libgccdemangle.so /android/system/lib/libadreno_utils.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/libEGL.so /android/system/lib/libc.so /android/system/lib/libutils.so /android/system/lib/libui.so /android/system/lib/libdsyscalls.so /android/system/lib/libcorkscrew.so /android/system/lib/libmemalloc.so /android/system/lib/libGLESv1_CM.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libstlport.so /android/system/lib/libz.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libsc-a3xx.so /android/system/lib/libcutils.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libGLESv2.so /android/system/lib/libqdutils.so /android/system/lib/libGLES_trace.so /android/system/lib/libstdc++.so /android/system/lib/libhardware.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/libgsl.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1375349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300709] Re: Empty areas in scopes produce haptics feedback without triggering any other action
oops... sorry, wrong tab :D -- 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/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300709] Re: Empty areas in scopes produce haptics feedback without triggering any other action
* Did you perform an exploratory manual test run of the code change and any related functionality? yep * Did CI run pass? If not, please explain why. nope, seems offline :/ * Did you make sure that the branch does not contain spurious tags? yes -- 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/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300709] Re: Empty areas in scopes produce haptics feedback without triggering any other action
Turns this seems to be caused by a disabled AbstractButton that still produces haptics feedback even though its disabled. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345653] Re: apport-gtk crashed with EOFError in _read_exact(): Compressed file ended before the end-of-stream marker was reached
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- 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/1345653 Title: apport-gtk crashed with EOFError in _read_exact(): Compressed file ended before the end-of-stream marker was reached Status in “apport” package in Ubuntu: Confirmed Bug description: upgrade from 10.04 to 12.10 ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: apport-gtk 2.14.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CrashReports: 640:0:128:33732:2014-07-20 13:38:34.401147127 -0400:2014-07-20 13:38:35.401147127 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash 640:0:128:1093249:2014-07-20 13:38:33.744819164 -0400:2014-07-20 13:38:34.744819164 -0400:/var/crash/cgmanager.0.crash Date: Sun Jul 20 13:38:35 2014 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2013-12-21 (211 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) PythonArgs: ['/usr/share/apport/apport-gtk'] SourcePackage: apport Title: apport-gtk crashed with EOFError in _read_exact(): Compressed file ended before the end-of-stream marker was reached UpgradeStatus: Upgraded to utopic on 2014-07-20 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1345653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370008] Re: url-dispatcher-bad-url
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gallery-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1370008 Title: url-dispatcher-bad-url Status in “gallery-app” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gallery-app. This problem was most recently seen with version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1370008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345569] Re: recoverable_problem crashed with ValueError in add_proc_info(): invalid process
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- 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/1345569 Title: recoverable_problem crashed with ValueError in add_proc_info(): invalid process Status in “apport” package in Ubuntu: Confirmed Bug description: Well, I'm not a system engineer and I haven't knowlegde why that trouble happen here. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: apport 2.14.4-0ubuntu2 Uname: Linux 3.16.0-031600rc4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 13:54:54 2014 ExecutablePath: /usr/share/apport/recoverable_problem InstallationDate: Installed on 2014-07-05 (15 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/recoverable_problem -p 14110 ProcEnviron: PATH=(custom, no user) LANGUAGE=pl XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/share/apport/recoverable_problem', '-p', '14110'] SourcePackage: apport Title: recoverable_problem crashed with ValueError in add_proc_info(): invalid process UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1345569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365186] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@148:collect_info:process_report
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- 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/1365186 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@148:collect_info:process_report Status in “apport” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6dcf56089700281d1f9a22242799e14f4c7c60ab contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1365186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376283] Re: Process of init --user gradually eats all RAM then the system starts using swap and hangs.
Please can you run 'apport-collect 1376283' (ideally when your system is experiencing the issue). Also, assuming you have not created any jobs yourself that might contain confidential information (?), it would be extremely useful if you could run the following when experiencing the problem and attach upstart.state.gz to this report: $ wget http://people.canonical.com/~jhunt/upstart/scripts/get_state.sh $ sh ./get_state.sh | json_pp | json_pp | gzip -9 /tmp/upstart.state.gz Thanks! -- 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/1376283 Title: Process of init --user gradually eats all RAM then the system starts using swap and hangs. Status in “upstart” package in Ubuntu: New Bug description: Process of init --user gradually eats all RAM then the system starts using swap and hangs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Wed Oct 1 18:06:48 2014 InstallationDate: Installed on 2013-11-09 (325 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016) SourcePackage: upstart UpgradeStatus: Upgraded to trusty on 2014-07-20 (72 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 2 UpstartRunningSystemVersion: init (upstart 1.12.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1376283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376606] [NEW] inappropriate statistical parameters in ping output
Public bug reported: The output of the ping command gives to the user several statistical paramters of the measured values (seen, in statistical sense, as a sample of a statistical population) e.g. rtt min/avg/max/mdev = 423.152/728.492/1306.341/220.001 ms, pipe 2 One of them is surely not appropriate in order to describe data in that case, one is probably inappropriate. First, the mean of a sample is a good estimator (in statistical sence) for the mean of an underlying statistical distribution (in statistical sense). But, this is only true for statistical distributions that do possess a so-called first moment (or expectation value) or mean. Some do not. And for that cases, giving the mean of the sample is misleading, because it is only an unreliable, fluctuating property of the random sample - and not of the statistical population! The mean of the random sample does not converge (e.g. with increasing sample size) to a location paramter of the underlying population or distribution. An user will interprete the given value as information of some kind of middle of the latencies, that will occure in the data conneciton. And this interpretation is wrong. Therefor, the statistical parameter avg, mean of the sample, is misleading and therefor inappropriate. Latency measurements are a standard case, where distrubutions occure, that do not possess first moments or expectation values (or, at least, do contain a large amount of outliers). In such cases, the more robust (and easier) measure of location, called median should be used, see http://en.wikipedia.org/wiki/Median http://en.wikipedia.org/wiki/File:Comparison_mean_median_mode.svg (As a second reason, the skew of the latency measurements also indicates, that a sample mean is not a good choice for an estimator for the measure of location of the distribution.) Second, a better measure of dispersion should be used. Wikipedia: When the median is used as a location parameter in descriptive statistics, there are several choices for a measure of variability: the range, the interquartile range, the mean absolute deviation, and the median absolute deviation. I would argue for the median absolute deviation. (I wrote probalby inappropriate, because mdev does not indicate a specific statistical technical term, so I do not know, what ist calculated. If it is (square root of) sample variance or estimator for standard deviation, then it is surely inappropriate.) Ubuntu release: 14.04.1 LTS iputils-ping: 3:20121221-4ubuntu1.1 ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Summary changed: - inappropriate statistical paramters in ping output + inappropriate statistical parameters in ping output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1376606 Title: inappropriate statistical parameters in ping output Status in “iputils” package in Ubuntu: New Bug description: The output of the ping command gives to the user several statistical paramters of the measured values (seen, in statistical sense, as a sample of a statistical population) e.g. rtt min/avg/max/mdev = 423.152/728.492/1306.341/220.001 ms, pipe 2 One of them is surely not appropriate in order to describe data in that case, one is probably inappropriate. First, the mean of a sample is a good estimator (in statistical sence) for the mean of an underlying statistical distribution (in statistical sense). But, this is only true for statistical distributions that do possess a so-called first moment (or expectation value) or mean. Some do not. And for that cases, giving the mean of the sample is misleading, because it is only an unreliable, fluctuating property of the random sample - and not of the statistical population! The mean of the random sample does not converge (e.g. with increasing sample size) to a location paramter of the underlying population or distribution. An user will interprete the given value as information of some kind of middle of the latencies, that will occure in the data conneciton. And this interpretation is wrong. Therefor, the statistical parameter avg, mean of the sample, is misleading and therefor inappropriate. Latency measurements are a standard case, where distrubutions occure, that do not possess first moments or expectation values (or, at least, do contain a large amount of outliers). In such cases, the more robust (and easier) measure of location, called median should be used, see http://en.wikipedia.org/wiki/Median http://en.wikipedia.org/wiki/File:Comparison_mean_median_mode.svg (As a second reason, the skew of the latency measurements also indicates, that a sample mean is not a good choice for an estimator for the measure of location of the distribution.) Second, a better measure of dispersion should be used. Wikipedia: When the median is
[Touch-packages] [Bug 1376612] [NEW] package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Error during update, however update went ok the next day so can probably be closed. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Wed Oct 1 10:24:40 2014 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu5:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2014-02-08 (235 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208) SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to utopic on 2014-08-28 (34 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1376612 Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in “systemd” package in Ubuntu: New Bug description: Error during update, however update went ok the next day so can probably be closed. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Wed Oct 1 10:24:40 2014 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu5:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2014-02-08 (235 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208) SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to utopic on 2014-08-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1376612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376611] [NEW] AppArmor: cupsd not allowed to send signals to third_party
Public bug reported: The cups 1.7.5-3 AppArmor profile has this rule which seems to be ineffective: signal (receive, send) peer=third_party, I get this denial log entry when (re)installing cups: audit: type=1400 audit(1412239287.417:110): apparmor=DENIED operation=signal profile=/usr/sbin/cupsd pid=28964 comm=cupsd requested_mask=send denied_mask=send signal=term peer=/usr/sbin/cupsd//third_party Changing it to the absolute profile name seems to work: signal (receive, send) peer=/usr/sbin/cupsd//third_party, I guess apparmor_parser can't distinguish between a profile named third_party and a subprofile named third_party. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor ** Tags added: apparmor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1376611 Title: AppArmor: cupsd not allowed to send signals to third_party Status in “cups” package in Ubuntu: New Bug description: The cups 1.7.5-3 AppArmor profile has this rule which seems to be ineffective: signal (receive, send) peer=third_party, I get this denial log entry when (re)installing cups: audit: type=1400 audit(1412239287.417:110): apparmor=DENIED operation=signal profile=/usr/sbin/cupsd pid=28964 comm=cupsd requested_mask=send denied_mask=send signal=term peer=/usr/sbin/cupsd//third_party Changing it to the absolute profile name seems to work: signal (receive, send) peer=/usr/sbin/cupsd//third_party, I guess apparmor_parser can't distinguish between a profile named third_party and a subprofile named third_party. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1376611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359153] Re: YouTube labels and categories are not localized
Here's the response I got from the StackOverflow question from a member of Google's Developer Relations team: Internationalization in the Data API v3 is something YT started supporting recently, and it's limited now. But there is a work going on to bring this support to the all functionalities in the API really soon. So it isn't clear how we can progress on this until something changes in the API. I'm lowering the importance to take this into account. Please change it again if you disagree. ** Changed in: unity-scope-youtube (Ubuntu) Importance: High = Medium -- 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/1359153 Title: YouTube labels and categories are not localized Status in Ubuntu Rest Scopes: Invalid Status in Ubuntu Translations: Triaged Status in “unity-scope-youtube” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Invalid Bug description: YouTube scope shows untranslated categories and labels. Test case. - Switch Ubuntu Phone to Spanish, reboot. - Go to YouTube scope. Expected result. - Labels and categories must be displayed in Spanish. Actual result. - Best of YouTube and its categories are displayed in English. - Sports, Gaming, number of views and other labels are displayed also in English. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1359153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***
Our experience clearly differs. I find that it is often the second free of a block that triggers the error. As the occasions when the free list has previously been corrupted take disproportionately more time to solve I'm hoping this is an easy one. ;) -- 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/1376324 Title: /usr/sbin/unity-system-compositor:*** Error in `unity-system- compositor': free(): invalid pointer: ADDR *** Status in Mir: Incomplete Status in Unity System Compositor: Incomplete Status in “mir” package in Ubuntu: Incomplete Status in “unity-system-compositor” package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+14.10.20140917-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376612] Re: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1376612 Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in “systemd” package in Ubuntu: New Bug description: Error during update, however update went ok the next day so can probably be closed. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Wed Oct 1 10:24:40 2014 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu5:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2014-02-08 (235 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140208) SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to utopic on 2014-08-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1376612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1012358] Re: Problem report is damaged, 'incorrect padding'
** Summary changed:
- blueman applet crashed with DBusException in call_blocking():
org.openobex.Error.InvalidArguments: Invalid path
+ Problem report is damaged, 'incorrect padding'
--
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/1012358
Title:
Problem report is damaged, 'incorrect padding'
Status in “apport” package in Ubuntu:
Confirmed
Bug description:
$ uname -a
Linux t420 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
Virtual Machine manager
- Open win7 vm
- When i try and open the display after win booted up to gui, something
crashes. And VM dies.
- Same happens if i close Gui vnc window and try and open later.
I get dialogue asking if i want to report the problem, I answer yes,
and provide root credentials.
After a little while i get a dialogue.
[x] Invalid problem report
(-) This problem report is damaged and cannot be processed.
TypeError(Error('incorrect padding',),)
https://launchpadlibrarian.net/122356767/1012358-incorrect-padding.png
See also bug 999264, IOError(13, 'Permission denied').
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1012358/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362160] Re: Card's implicitHeight calculated wrong if summary is missing
** Branch unlinked: lp:~unity-team/unity8/fix-vertical-journal ** Branch linked: lp:~unity-team/unity8/fix-card-implicitHeight -- 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/1362160 Title: Card's implicitHeight calculated wrong if summary is missing Status in “unity8” package in Ubuntu: In Progress Bug description: As can be seen in the music scope after choosing an artist from My Music carousel (see attachment) the implicit height on a card is calculated wrong if summary is declared but empty. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140825.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 27 14:39:33 2014 SourcePackage: unity8 SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1202824] Re: Apport fails with 'the problem report is damaged'
For the 'Incorrect padding' issue, Bug #1012358. (Leaving this as non-
duplicate, since the reporter has other 'damaged' errors besides that
one.)
--
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/1202824
Title:
Apport fails with 'the problem report is damaged'
Status in “apport” package in Ubuntu:
Confirmed
Bug description:
Whenever a crash occurs, apport attempts to generate a report but has
been failing for the past few weeks, usually stating that there is a
CRC inconsistency. Other reasons include (the current bug report):
This problem report is damaged and cannot be processed:
TypeError(Error('Incorrect padding',),)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu17.3
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Uname: Linux 3.2.0-49-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
Date: Fri Jul 19 07:56:32 2013
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-04-28 (446 days ago)
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
Package: apport 2.0.1-0ubuntu17.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Tags: precise
Uname: Linux 3.2.0-49-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-28 (446 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev
powerdev sambashare staff vboxusers video www-data
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
Package: apport 2.0.1-0ubuntu17.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Tags: precise
Uname: Linux 3.2.0-49-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-28 (446 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev
powerdev sambashare staff vboxusers video www-data
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
Package: apport 2.0.1-0ubuntu17.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Tags: precise
Uname: Linux 3.2.0-49-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-28 (449 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev
powerdev sambashare staff vboxusers video www-data
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
Package: apport 2.0.1-0ubuntu17.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Tags: precise
Uname: Linux 3.2.0-49-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-28 (449 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev
powerdev sambashare staff vboxusers video www-data
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386
(20100429.4)
MarkForUpload: True
Package: apport 2.0.1-0ubuntu17.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic-pae 3.2.46
Tags: precise
Uname: Linux 3.2.0-49-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-28 (450 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev
powerdev sambashare staff vboxusers video www-data
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1202824/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***
It would depend entirely on how much the code touches the heap. In a reasonably efficient project, the heap (structure not content) doesn't change that much. You always have to assume malloc/free/new/delete are slow and should avoid them. So the offending corruption could have happened some time ago. -- 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/1376324 Title: /usr/sbin/unity-system-compositor:*** Error in `unity-system- compositor': free(): invalid pointer: ADDR *** Status in Mir: Incomplete Status in Unity System Compositor: Incomplete Status in “mir” package in Ubuntu: Incomplete Status in “unity-system-compositor” package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+14.10.20140917-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300709] Re: Empty areas in scopes produce haptics feedback without triggering any other action
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Albert Astals Cid (aacid) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Invalid ** Changed in: unity8 (Ubuntu) Status: New = In Progress ** Branch linked: lp:~aacid/unity8/base_not_clickable -- 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/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278729] [NEW] hplip-gui showing wrong character settings - guess greeek
You have been subscribed to a public bug: afterwards hplip gui chrashed - I unstalled hlplip-gui ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.1-1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Feb 11 08:18:06 2014 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2014-02-08 (2 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP_LaserJet_M1522nf_MFP: hp:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 device for HP_LaserJet_M1522nf_MFP_fax: hpfax:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: HP_LaserJet_M1522nf_MFP: HP LaserJet m1522nf MFP pcl3, hpcups 3.14.1 HP_LaserJet_M1522nf_MFP_fax: HP Fax2 hpcups ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=a46d1948-9e5d-4e51-964b-e5de7b76a7a3 ro SegvAnalysis: Segfault happened at: 0x5b169d:mov0x10(%rax),%rdi PC (0x005b169d) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction() UpgradeStatus: Upgraded to trusty on 2014-02-08 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd02/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: hplip Importance: Undecided Status: Confirmed ** Affects: gtk+2.0 (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-crash trusty utopic -- hplip-gui showing wrong character settings - guess greeek https://bugs.launchpad.net/bugs/1278729 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376315] Re: Unable to add image in Yelp webapp, but can on m.yelp.com in the browser
*** This bug is a duplicate of bug 1376639 *** https://bugs.launchpad.net/bugs/1376639 ** This bug has been marked a duplicate of private bug 1376639 -- 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/1376315 Title: Unable to add image in Yelp webapp, but can on m.yelp.com in the browser Status in “webbrowser-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the 'Yelp' application 2. From the home screen click on a review (under Hot New Businesses Nearby) 3. Click on the 'Add Photo' button on the businesses page Expected result: Content hub opens and offers e.g. Camera and Gallery as sources Actual result: Content hub opens with message 'Sorry there aren't currently any apps installed that can provide this type of content' Repeating the same test case by replacing step 1 with 'Open the browser and navigate to m.yelp.com' gives the Expected result ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140926-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Oct 1 15:17:45 2014 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141001-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1376315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359204] Re: Padlock shape is inconsistent in standlone icon vs. Wi-Fi emblem
** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) = Matthieu James (tiheum) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1359204 Title: Padlock shape is inconsistent in standlone icon vs. Wi-Fi emblem Status in “ubuntu-themes” package in Ubuntu: New Bug description: Ubuntu 14.10 r179 1. From System Settings, or the first-run setup, choose a closed Wi-Fi network. 2. Observe the padlock icons in the network list vs. the authentication dialog. What you see: * The standalone icon has a thin shackle, while the network emblem has a thick shackle. * In the standalone icon, the shackle is inset from the edge, while in the network emblem it's flush with the edge. * The standalone icon has a keyhole, while the network emblem does not. What you should see: The icons are exactly the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1359204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376530] [NEW] GTK apps crashing with Attempt to unlock mutex that was not locked
You have been subscribed to a public bug: Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in an immediate crash, with the message Attempt to unlock mutex that was not locked. https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the relevant upstream bug, and there is a patch here: https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec To some extent, this seems to be the result of individual projects using GTK incorrectly, and some fixes have been made to those individual projects. *However*, I am also seeing this bug occur in a closed source third party application, Stata 13. As Emmanuele Bassi mentions in the Gnome bug thread, there are probably a lot of applications out in the wild affected by the same issue, that in some cases cannot be fixed, so it would be good if a fix could be included in the versions of GTK that Ubuntu ships. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgtk-3-0 3.12.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 2 10:05:20 2014 InstallationDate: Installed on 2014-04-24 (160 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago) ** Affects: gtk+2.0 (Ubuntu) Importance: High Status: Fix Committed ** Tags: amd64 apport-bug utopic -- GTK apps crashing with Attempt to unlock mutex that was not locked https://bugs.launchpad.net/bugs/1376530 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376644] [NEW] Some qtpim tests start failing when built against Qt 5.3.2
Public bug reported: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing-archive- extra I've also updated to the latest git snapshot but unfortunately it doesn't fix the problems: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451510/+listing-archive- extra We shouldn't be disabling additional tests, so the root causes should be found. You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: qtpim-opensource-src (Ubuntu) Importance: High Assignee: Renato Araujo Oliveira Filho (renatofilho) Status: New ** Tags: qt5.3 ** Tags added: qt5.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1376644 Title: Some qtpim tests start failing when built against Qt 5.3.2 Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing- archive-extra I've also updated to the latest git snapshot but unfortunately it doesn't fix the problems: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451510/+listing- archive-extra We shouldn't be disabling additional tests, so the root causes should be found. You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354362] Re: Removed department stays in the shell
This bug was fixed in the package unity-scopes-shell - 0.5.4+14.10.20141002-0ubuntu1 --- unity-scopes-shell (0.5.4+14.10.20141002-0ubuntu1) utopic; urgency=low [ Pete Woods ] * Remove missing departments (LP: #1354362) [ Pawel Stolowski ] * Remove missing departments (LP: #1354362) * Iterate over temprary dash pages of every scope to find matching scope when dbus signal for results invalidation was received. This is only done if there was no match among favorite scopes. (LP: #1365544) * Fix signature of the deleteLater slot when scheduling scope for removal after un-favoriting. * Send build number, release name and package versions of unity8, shell plugin and scopes api with user-agent hint in SearchMetadata and PreviewMetadata. (LP: #1372834) [ Marcus Tomlinson ] * Handle scopes scope invalidation by re-populating the overview scope. (LP: #1375718) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 02 Oct 2014 07:18:26 + ** Branch linked: lp:ubuntu/utopic-proposed/unity-scopes-shell ** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1354362 Title: Removed department stays in the shell Status in “unity-scopes-shell” package in Ubuntu: Fix Released Bug description: It's seems like the plugin doesn't notice when one of the departments disappears (is no longer returned by the scope) and doesn't notify shell about it, so that department is still displayed. This is visible with the following branch of click scope: https://code.launchpad.net/~stolowski/unity-scope-click/no-empty- departments/+merge/230077 The case is as follows - consider we're always in the root of all departments in the dash. 1) scope responds with A and B sub-departments of All departments; A and B are shown when you open the departments menu. 2) scope content is refreshed somehow (e.g. you redo a search), and now it responds with A only. Result: both A and B are still shown. Expected result: only A is shown. Steps to reproduce with the above branch of click scope: 1) Go to Ubuntu Store and install an app from a department, that was previously not shown in Apps. 2) After installation completes, go back to Apps - search results are refreshed (new app appears), and new department appears in the departments menu. 3) Uninstall that app: search results are refreshed, but the department that is now empty doesn't disappear (you can verify with scopes-cli that it's not returned anymore by the scope); after reboot however the department is not shown anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1354362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372834] Re: SmartScopesProxy needs to send version numbers to the server
This bug was fixed in the package unity-scopes-shell - 0.5.4+14.10.20141002-0ubuntu1 --- unity-scopes-shell (0.5.4+14.10.20141002-0ubuntu1) utopic; urgency=low [ Pete Woods ] * Remove missing departments (LP: #1354362) [ Pawel Stolowski ] * Remove missing departments (LP: #1354362) * Iterate over temprary dash pages of every scope to find matching scope when dbus signal for results invalidation was received. This is only done if there was no match among favorite scopes. (LP: #1365544) * Fix signature of the deleteLater slot when scheduling scope for removal after un-favoriting. * Send build number, release name and package versions of unity8, shell plugin and scopes api with user-agent hint in SearchMetadata and PreviewMetadata. (LP: #1372834) [ Marcus Tomlinson ] * Handle scopes scope invalidation by re-populating the overview scope. (LP: #1375718) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 02 Oct 2014 07:18:26 + ** Branch linked: lp:ubuntu/utopic-proposed/unity-scopes-shell ** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1372834 Title: SmartScopesProxy needs to send version numbers to the server Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu: Fix Released Bug description: Shell plugin needs to report versions of important components (scopes- api, shell-plugin and unity8) with search and preview request, and they need to be passed to from SmartScopesProxy to Smart Scopes Server via UserAgent string. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1372834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375718] Re: Manage Dash page doesn't refresh when scopes are installed or removed
This bug was fixed in the package unity-scopes-shell - 0.5.4+14.10.20141002-0ubuntu1 --- unity-scopes-shell (0.5.4+14.10.20141002-0ubuntu1) utopic; urgency=low [ Pete Woods ] * Remove missing departments (LP: #1354362) [ Pawel Stolowski ] * Remove missing departments (LP: #1354362) * Iterate over temprary dash pages of every scope to find matching scope when dbus signal for results invalidation was received. This is only done if there was no match among favorite scopes. (LP: #1365544) * Fix signature of the deleteLater slot when scheduling scope for removal after un-favoriting. * Send build number, release name and package versions of unity8, shell plugin and scopes api with user-agent hint in SearchMetadata and PreviewMetadata. (LP: #1372834) [ Marcus Tomlinson ] * Handle scopes scope invalidation by re-populating the overview scope. (LP: #1375718) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 02 Oct 2014 07:18:26 + ** Branch linked: lp:ubuntu/utopic-proposed/unity-scopes-shell ** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1375718 Title: Manage Dash page doesn't refresh when scopes are installed or removed Status in “unity-scopes-shell” package in Ubuntu: Fix Released Bug description: The 'All' section of Manage Dash page is not refreshed when new scopes are installed or uninstalled. To reproduce, install a scope from a click package - it will appear in Manage Dash only after reboot. This is most likely caused by Scopes::getScopeById() returning null for scopes scope, which breaks the refreshing of results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1375718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365544] Re: Non-favorited scopes are not refreshed
This bug was fixed in the package unity-scopes-shell - 0.5.4+14.10.20141002-0ubuntu1 --- unity-scopes-shell (0.5.4+14.10.20141002-0ubuntu1) utopic; urgency=low [ Pete Woods ] * Remove missing departments (LP: #1354362) [ Pawel Stolowski ] * Remove missing departments (LP: #1354362) * Iterate over temprary dash pages of every scope to find matching scope when dbus signal for results invalidation was received. This is only done if there was no match among favorite scopes. (LP: #1365544) * Fix signature of the deleteLater slot when scheduling scope for removal after un-favoriting. * Send build number, release name and package versions of unity8, shell plugin and scopes api with user-agent hint in SearchMetadata and PreviewMetadata. (LP: #1372834) [ Marcus Tomlinson ] * Handle scopes scope invalidation by re-populating the overview scope. (LP: #1375718) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 02 Oct 2014 07:18:26 + ** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1365544 Title: Non-favorited scopes are not refreshed Status in “unity-scopes-shell” package in Ubuntu: Fix Released Bug description: How to reproduce: - Go to the store scope. - Make sure it's not favorited. If it is favorited, unfav it then leave the scope and return to it. - Tap on the icon of some FREE app that is not installed. - On the preview of the app, tap on Install, and wait for the installation to finish. - Click on the button on the preview header to go back to the results. What happens: - The icon attributes still show FREE What should happen: - The scope should have been refreshed, and ✔INSTALLED should be shown instead This works ok for scopes that are favorited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1365544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376530] Re: GTK apps crashing with Attempt to unlock mutex that was not locked
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided = High ** Package changed: gtk+3.0 (Ubuntu) = ubuntu ** Changed in: ubuntu Status: New = Fix Committed ** Package changed: ubuntu = gtk+2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1376530 Title: GTK apps crashing with Attempt to unlock mutex that was not locked Status in “gtk+2.0” package in Ubuntu: Fix Committed Bug description: Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in an immediate crash, with the message Attempt to unlock mutex that was not locked. https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the relevant upstream bug, and there is a patch here: https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec To some extent, this seems to be the result of individual projects using GTK incorrectly, and some fixes have been made to those individual projects. *However*, I am also seeing this bug occur in a closed source third party application, Stata 13. As Emmanuele Bassi mentions in the Gnome bug thread, there are probably a lot of applications out in the wild affected by the same issue, that in some cases cannot be fixed, so it would be good if a fix could be included in the versions of GTK that Ubuntu ships. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgtk-3-0 3.12.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 2 10:05:20 2014 InstallationDate: Installed on 2014-04-24 (160 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369644] Re: [enhancement] Should be possible to take a screen shot on the phone from the phone itself
will/would -- 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/1369644 Title: [enhancement] Should be possible to take a screen shot on the phone from the phone itself Status in Mir: Opinion Status in Qt integration with the Mir display server: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “mir” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: In Progress Bug description: Currently, the only way to take a screenshot is to attach the phone to a computer via USB and use phablet-screenshot. There should be a way to take a screenshot from the phone. Otherwise, it will be hard for people to share how great their phone is on social media, as well as other functions. Proposed design: For triggering: Volume Up + Volume Down To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1369644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339792] Re: Panel network icon - too much latency when network type changes
** Tags removed: touch-2014-10-09 ** Tags added: touch-2014-10-16 -- 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/1339792 Title: Panel network icon - too much latency when network type changes Status in “indicator-network” package in Ubuntu: New Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi - 3G - WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click Previous Networks - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to 3G. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369644] Re: [enhancement] Should be possible to take a screen shot on the phone from the phone itself
I would skip a notification, but I will add something to the notification center (screenshot taken, tap to open gallery...) -- 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/1369644 Title: [enhancement] Should be possible to take a screen shot on the phone from the phone itself Status in Mir: Opinion Status in Qt integration with the Mir display server: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “mir” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: In Progress Bug description: Currently, the only way to take a screenshot is to attach the phone to a computer via USB and use phablet-screenshot. There should be a way to take a screenshot from the phone. Otherwise, it will be hard for people to share how great their phone is on social media, as well as other functions. Proposed design: For triggering: Volume Up + Volume Down To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1369644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278729] Re: hplip-gui showing wrong character settings - guess greeek
That looks like a gtk bug/fixed with that commit https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24id=1d0e2d58385bd01fdb753bf40ba2f4c32ccd0cc8 ** Package changed: hplip (Ubuntu) = gtk+2.0 (Ubuntu) ** Changed in: gtk+2.0 (Ubuntu) Importance: Medium = High ** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1278729 Title: hplip-gui showing wrong character settings - guess greeek Status in HP Linux Imaging and Printing: Confirmed Status in “gtk+2.0” package in Ubuntu: Fix Committed Bug description: afterwards hplip gui chrashed - I unstalled hlplip-gui ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.1-1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Feb 11 08:18:06 2014 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2014-02-08 (2 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP_LaserJet_M1522nf_MFP: hp:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 device for HP_LaserJet_M1522nf_MFP_fax: hpfax:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: HP_LaserJet_M1522nf_MFP: HP LaserJet m1522nf MFP pcl3, hpcups 3.14.1 HP_LaserJet_M1522nf_MFP_fax: HP Fax2 hpcups ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=a46d1948-9e5d-4e51-964b-e5de7b76a7a3 ro SegvAnalysis: Segfault happened at: 0x5b169d: mov0x10(%rax),%rdi PC (0x005b169d) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction() UpgradeStatus: Upgraded to trusty on 2014-02-08 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd02/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1278729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
The problem here is with the U1 account plugin, which doesn't add unconfined to the initial list of ACL. After a quick look at the source code, I believe that the code which needs to be changed is here: http://bazaar.launchpad.net/~ubuntuone-control-tower/ubuntuone-credentials/trunk/view/head:/libubuntuoneauth/keyring.cpp#L161 The change is about adding info.setAccessControlList(QStringList() unconfined); before storing the info object. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1376445 Title: Addition of signon-apparmor-extension causes token lookup problems Status in The Savilerow project: New Status in “ubuntuone-credentials” package in Ubuntu: Triaged Status in “ubuntuone-credentials” package in Ubuntu RTM: Triaged Bug description: As of image ~264 of ubuntu-touch, the signon-apparmor-extension package is included. As a result, apps like pay-ui cannot find the token any longer, and are not being notified that they are not allowed to access the token. The following error appears in the payui log file: 2014-10-01 19:15:51,550 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot QDBusError(com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied, Client has insuficient permissions to access the service.Method:getAuthSessionObjectPath) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1376445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358750] Re: [Video aggregator] New videos are added to the video scope only after reboot
** Changed in: mediascanner2 Status: In Progress = Fix Released ** Changed in: mediascanner2 Assignee: (unassigned) = James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1358750 Title: [Video aggregator] New videos are added to the video scope only after reboot Status in Media Scanner v2: Fix Released Status in “mediascanner2” package in Ubuntu: Fix Released Status in “mediascanner2” package in Ubuntu RTM: Fix Released Bug description: New videos are added to the video scope only after reboot. They should be added immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1358750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325230]
I am re-assigning this bug report to fontconfig. Dear fontconfig-devs, now that a proper fix for the missing ligature glyphs in Tex Gyre Termes has made it into poppler [0,1], could you please revert the commit [2] to fontconfig that disabled Termes as a metric alias for Times? Thank you so much! Fabian [0] https://bugs.freedesktop.org/show_bug.cgi?id=80093#c16 [1] http://cgit.freedesktop.org/poppler/poppler/commit/?id=01723aa17e836e818158dbdc56df642a290be300 [2] http://cgit.freedesktop.org/fontconfig/commit/conf.d/30-metric-aliases.conf?id=c6aa4d4bfcbed14f39d070fe7ef90a4b74642ee7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1325230 Title: evince does not display ligatures Status in Fontconfig - Font Configuration Library: Confirmed Status in “fontconfig” package in Ubuntu: Fix Released Status in “fontconfig” source package in Trusty: Fix Released Bug description: [ Description ] When a document uses a Times font, the 'fi' ligature may not be displayed. The TeX Gyre Termes font is aliased to Times in fontconfig and does not display this correctly. [ Development fix ] Identical package uploaded to Utopic. [ QA ] Install fonts-texgyre, then download the PDF in comment #1 and check that 'file' is displayed incorrectly (no 'fi') before and correctly after. [ Regression potential ] Some files might display better with TeX Gyre Termes. Check a few Times documents to see that they are still okay. [ Original description ] The following pdf file does not display ligatures for fi. Open the file and search for file. http://ceph.com/papers/weil-crush-sc06.pdf I have attached an image of the rendering of the file, showing the word file, though not displaying fi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 31 09:07:41 2014 InstallationDate: Installed on 2013-06-02 (362 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-04-24 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1325230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
So, an iteration gives me the following log:
QStandardPaths: wrong permissions on runtime directory /run/user/32011
[StateSaver] No XDG_RUNTIME_DIR path set, cannot create appstate file.
The code prints this out is:
QStringList runtimeDirs =
QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation);
QString runtimeDir = runtimeDirs.size() 0 ? runtimeDirs[0] :
qgetenv(XDG_RUNTIME_DIR);
if (runtimeDir.isEmpty()) {
qWarning() [StateSaver] No XDG_RUNTIME_DIR path set, cannot create
appstate file.;
return;
}
Which means that runtimeDirs string list is empty. If I do change the code to
QStringList runtimeDirs =
QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation);
QString runtimeDir = (runtimeDirs.size() 0 !runtimeDirs[0].isEmpty())
? runtimeDirs[0] : qgetenv(XDG_RUNTIME_DIR);
if (runtimeDir.isEmpty()) {
qWarning() [StateSaver] No XDG_RUNTIME_DIR path set, cannot create
appstate file.;
return;
}
then I get the path correctly, because qgetenv() will be used to fetch the
path. So, all in all seems QStandardPaths is just not good for this folder :/
--
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/1363112
Title:
StateSaver is not working on devices
Status in Ubuntu UI Toolkit:
Confirmed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Fix Released
Status in “camera-app” package in Ubuntu:
Fix Released
Bug description:
build 212
The StateSaver is not working anymore on devices, so apps saved state is no
longer restored when they are relaunched after being killed by oom killer (or
manually via kill -2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325230] Re: evince does not display ligatures
** Bug watch added: freedesktop.org Bugzilla #80093 https://bugs.freedesktop.org/show_bug.cgi?id=80093 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1325230 Title: evince does not display ligatures Status in Fontconfig - Font Configuration Library: Confirmed Status in “fontconfig” package in Ubuntu: Fix Released Status in “fontconfig” source package in Trusty: Fix Released Bug description: [ Description ] When a document uses a Times font, the 'fi' ligature may not be displayed. The TeX Gyre Termes font is aliased to Times in fontconfig and does not display this correctly. [ Development fix ] Identical package uploaded to Utopic. [ QA ] Install fonts-texgyre, then download the PDF in comment #1 and check that 'file' is displayed incorrectly (no 'fi') before and correctly after. [ Regression potential ] Some files might display better with TeX Gyre Termes. Check a few Times documents to see that they are still okay. [ Original description ] The following pdf file does not display ligatures for fi. Open the file and search for file. http://ceph.com/papers/weil-crush-sc06.pdf I have attached an image of the rendering of the file, showing the word file, though not displaying fi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 31 09:07:41 2014 InstallationDate: Installed on 2013-06-02 (362 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-04-24 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1325230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376344] Re: MTP can access locked device data after rebooting
I re-tested this on a fresh install. In this case it takes 2 reboots of the device at the locked greeter screen to show this problem. It is still possible to access device data over MTP without unlocking the device. -- 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/1376344 Title: MTP can access locked device data after rebooting Status in “mtp” package in Ubuntu: New Bug description: ENVIRONMENT: Device: ubuntu-rtm/14.09 build 3 Desktop: Ubuntu 14.10 SUMMARY: MTP can access locked device data after rebooting STEPS: 1) Ensure device is locked with PIN/passphrase and showing locked greeter 2) Insert USB cable and try to access device content over MTP - No content is displayed as expected 3) Reboot device, leaving USB cable connected 4) When device is rebooted and still locked, try and access device content over MTP again EXPECTED RESULT: It should not be possible to view device content using MTP whilst the device is locked ACTUAL RESULT: You can copy and view all content on device using MTP whilst device is still locked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1376344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302885] [NEW] Media keyboard shortcuts not working
You have been subscribed to a public bug: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 ** Affects: unity (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug trusty -- Media keyboard shortcuts not working https://bugs.launchpad.net/bugs/1302885 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
Well, the kernel issue is now defintily fixed, so it shouldn't be a problem in the future, libv4l2 can now be disabled, so we can workaround any issues with it. As for libavcodec, they don't offer any garanties on the API, so it usually causes some breakdowns from time to time, but this is true for all aplications. I actually tend to fix things rather quickly, unfurtunately in the case of Ubuntu they can take some time to upgrade, so you are left with a non working version until the next release. For debian it's easier since it's a rolling realease, I just contact the mantainer and he upgrades to the current (fixed) version. In the case of ubuntu, the only option is to use one of my ppa's for 14.10, the current testing version is now working fine, I've fixed all issues with both libavcodec and uvcvideo, so I'll release the new version both in sourceforge and in my stable ppa. Regards, Paulo 2014-10-01 20:02 GMT+01:00 Alberto Salvia Novella es204904...@gmail.com: Paulo Assis: 1.7.3 won't work with kernels =3.16, you will need a newer version, uvcvideo suffered a regression that will only be fixed (hopefully) in 3.18, the developer already posted a patch to fix it. I'll make a new release (2.0.1) in the next couple of days with a workaround for this. you will need this version to get guvcview up and running with uvcvideo devices. Note: libv4l2 (1.4.0 and 1.5.0) is also broken, a fix is expected in 1.6.0, but you will be able to disable its use in guvcview in this version. What are you plans to guvcview not to be affected by these breakdowns in future? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() Status in GTK uvc viewer: Confirmed Status in One Hundred Papercuts: Triaged Status in libv4l v4l-utils: Confirmed Status in “guvcview” package in Ubuntu: Triaged Status in “v4l-utils” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Launch guvcview EXPECTED BEHAVIOUR: - The application to start normally. REAL BEHAVIOUR: - The application crashes. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: guvcview 1.7.3-1.1build2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 24 06:35:20 2014 ExecutablePath: /usr/bin/guvcview InstallationDate: Installed on 2013-05-21 (490 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: guvcview SegvAnalysis: Segfault happened at: 0x42d970: mov0x0,%eax PC (0x0042d970) ok source 0x0 (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: guvcview StacktraceTop: ?? () ?? () ?? () ?? () __libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208, init=optimised out, fini=optimised out, rtld_fini=optimised out, stack_end=0x7fff32c341f8) at libc-start.c:287 Title: guvcview crashed with SIGSEGV in __libc_start_main() UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
I think the linked branch will fix this problem. ** Branch linked: lp:~laney/unity/keygrabber-xf86 ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) = Iain Lane (laney) ** Package changed: unity-control-center (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in “unity” package in Ubuntu: Confirmed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359831] Re: Apps incorrectly perform a chmod on XDG_RUNTIME_DIR
Actually, there is a setPermissions() call so seems the XDG_RUNTIME_DIR permission are detected to differ from the wanted ones! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1359831 Title: Apps incorrectly perform a chmod on XDG_RUNTIME_DIR Status in Camera App: Confirmed Status in Ubuntu Reminders app: Invalid Status in Sudoku game for Ubuntu Touch: Invalid Status in “qtbase-opensource-src” package in Ubuntu: Confirmed Bug description: From bug #1351041: [Thu Jul 31 21:04:20 2014] type=1400 audit(1406837062.464:97): apparmor=DENIED operation=chmod profile=com.ubuntu.reminders_reminders_0.5.203 name=/run/user/32011/ pid=12954 comm=reminders requested_mask=w denied_mask=w fsuid=32011 ouid=32011 From irc: Aug 21 15:47:20 ubuntu-phablet kernel: [ 251.843308] type=1400 audit(1408636040.346:137): apparmor=DENIED operation=chmod profile=com.ubuntu.camera_camera_3.0.0.355 name=/run/user/32011/ pid=4172 comm=camera-app requested_mask=w denied_mask=w fsuid=32011 ouid=32011 AppArmor policy is correct on this denial-- apps should not be able to change the permissions on the /run/user/32011/ (XDG_RUNTIME_DIR) directory. I filed this against camera-app and reminders, but my guess is this is an underlying library that is causing this. I don't know if the denial is causing errors with the app, but it is causing confusion for users and developers who see the denial. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1359831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/statesaver_path -- 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/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Bug description: build 212 The StateSaver is not working anymore on devices, so apps saved state is no longer restored when they are relaunched after being killed by oom killer (or manually via kill -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Bill, I have ARM packages for the attached toolkit branch, could you also test with it? Camera app works for me, I can see the states restored (again) and also the state file created. https://launchpad.net/~ubuntu-sdk- team/+archive/ubuntu/testing/+build/6427230 -- 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/1363112 Title: StateSaver is not working on devices Status in Ubuntu UI Toolkit: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Bug description: build 212 The StateSaver is not working anymore on devices, so apps saved state is no longer restored when they are relaunched after being killed by oom killer (or manually via kill -2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311899] Re: Popup is too small to display Facebook authorization
Issue exist on Debian Wheezy as well (Gnome) with the same description. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1311899 Title: Popup is too small to display Facebook authorization Status in “gnome-online-accounts” package in Ubuntu: Confirmed Bug description: Description of problem: Unable to grant permissions to Gnome application on Facebook due to window size. Version-Release number of selected component (if applicable): gnome-online-accounts-3.8.5-7.el7.x86_64 How reproducible: always Steps to Reproduce: 0. Remove Gnome from: https://www.facebook.com/settings?tab=applications 1. Login to Facebook through Online Accounts Actual results: Your popup is too small to display this page. Please enlarge it to proceed. see screenshot Expected results: Webview dialog asking to give permissions to Gnome application on Facebook. This bug report is copied from: https://bugzilla.redhat.com/show_bug.cgi?id=1081520 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-online-accounts 3.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 23 23:47:07 2014 InstallationDate: Installed on 2012-12-07 (502 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1311899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
For Skype (at least) there should be a workaround using notification scripts and switching profiles as in https://wiki.archlinux.org/index.php/Bluetooth_headset#Switch_between_HSV_and_A2DP_setting for ex.: pacmd set-card-profile 2 a2dp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/508522 Title: Mic is not available with A2DP Bluetooth profile Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles HSP/ HFP Telephony duplex and A2DP High Fidelity Playback. For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or telephone quality with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
diff -urN powerpc.py.old powerpc.py --- powerpc.py.old 2014-09-04 06:33:16.0 -0400 +++ powerpc.py 2014-09-10 10:28:18.824002770 -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: ** Changed in: apport (Ubuntu) Assignee: (unassigned) = Canonical Taco Screen Team (canonical-taco-screeners) -- 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 Status in “apport” package in Ubuntu: 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 -0400 +++ powerpc.py2014-09-10 10:28:18.824002770 -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: Initial Launchpad bug id #1336462 implemented feature support To manage notifications about this bug go to:
[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@Sergio I can't get this to work, only the error Read-only file system. -- 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/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in “network-manager” package in Ubuntu: New Status in “nuntium” package in Ubuntu: Incomplete Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368826] Re: [Launcher] [design] Remove the recent apps from the launcher
** Description changed: Recent apps live and can be accessed already via right edge. Them appearing in the Launcher is duplication. Also mixing recent apps with favourite ones is a concept that users has difficulties to grasp. Launcher should only contain user's favourite apps, and possibly apps that are asking for attention. Removing recent apps from the launcher means that there is no way to add favourite apps to the launcher any more and we need to do that from somewhere else. App preview page would a quick fix. Longpressing an app icon in dash would be more elegant solution. We could easily add longpress functionality to items in spread to do favoriting. + This bug should be fixed together with: + https://bugs.launchpad.net/ubuntu-ux/+bug/1368831 + Proper design is still missing. -- 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/1368826 Title: [Launcher] [design] Remove the recent apps from the launcher Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: New Bug description: Recent apps live and can be accessed already via right edge. Them appearing in the Launcher is duplication. Also mixing recent apps with favourite ones is a concept that users has difficulties to grasp. Launcher should only contain user's favourite apps, and possibly apps that are asking for attention. Removing recent apps from the launcher means that there is no way to add favourite apps to the launcher any more and we need to do that from somewhere else. App preview page would a quick fix. Longpressing an app icon in dash would be more elegant solution. We could easily add longpress functionality to items in spread to do favoriting. This bug should be fixed together with: https://bugs.launchpad.net/ubuntu-ux/+bug/1368831 Proper design is still missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368287] Re: [App switcher] Different drag behaviour between items that can and cannot be closed
** Changed in: ubuntu-ux
Status: Triaged = Fix Committed
--
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/1368287
Title:
[App switcher] Different drag behaviour between items that can and
cannot be closed
Status in Ubuntu UX bugs:
Fix Committed
Status in “unity8” package in Ubuntu:
New
Bug description:
Drag to close is a great feature in application spread. In user
testing it had a great success rate and users understood it and knew
how to use it. The problem is the Dash item that's part of the spread
but is the only item which cannot be closed. Currently the Dash item
drag movement is similar to the movement of the items that actually
can be closed.
We want to make Dash drag different from others by restricting the
movement while still responding to user's drag.
Desired solution
Use restriction algorithm for dash item so that it moves along the
drag but soon starts restricting the movement indicating that it's an
item that cannot be closed.
Here is quite nice elastic function that can be used:
function elastic( currentPosition, limit ) {
return limit * ( 1 - Math.pow( ( limit - 1 ) / limit, currentPosition ) )
}
Where:
limit is the highest value that ever can be returned by the function
current position is the value to be limited
It's a bit hard to describe the parameters, therefore I created a prototype
that should explain the usage.
Find it from: lp:~willow-team/willow/elasticRestriction
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1368287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368831] Re: [Launcher] [design] Change pin/un-pin terminology to Add/Remove
** Description changed: Change the pin/un-pin terminology to Add to Launcher or Remove from Launcher. Remove all traces of the word Pin. This was the original terminology but since it caused confusion with the recent applications in launcher. That's because a favourite app that was recent wasn't really removed from the launcher but unfavourited/unpinned when Remove from Launcher was selected. - As we now propose getting rid of recent apps from the launcher (bug - 1368826) we should move back using Add/Remove terminology which is - easier to understand than pin/un-pin. + This bug should be fixed together with bug 1368826. ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- 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/1368831 Title: [Launcher] [design] Change pin/un-pin terminology to Add/Remove Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Incomplete Bug description: Change the pin/un-pin terminology to Add to Launcher or Remove from Launcher. Remove all traces of the word Pin. This was the original terminology but since it caused confusion with the recent applications in launcher. That's because a favourite app that was recent wasn't really removed from the launcher but unfavourited/unpinned when Remove from Launcher was selected. This bug should be fixed together with bug 1368826. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libxml2 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1375637 Title: Premature end of data in tag file line 247651 with libxml2 Status in “libxml2” package in Ubuntu: Confirmed Bug description: Hello, I'm getting the following behaviour of createrepo on Ubuntu 14.04.1 LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main). createrepo -g /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml \ -o /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ I/O error : No such file or directory (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 246828 (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Spawning worker 0 with 54 pkgs Spawning worker 1 with 54 pkgs Spawning worker 2 with 54 pkgs Spawning worker 3 with 54 pkgs Spawning worker 4 with 54 pkgs Spawning worker 5 with 54 pkgs Spawning worker 6 with 54 pkgs Spawning worker 7 with 54 pkgs Spawning worker 8 with 54 pkgs Spawning worker 9 with 54 pkgs Spawning worker 10 with 53 pkgs Spawning worker 11 with 53 pkgs Spawning worker 12 with 53 pkgs Spawning worker 13 with 53 pkgs Spawning worker 14 with 53 pkgs Spawning worker 15 with 53 pkgs Spawning worker 16 with 53 pkgs Spawning worker 17 with 53 pkgs Spawning worker 18 with 53 pkgs Spawning worker 19 with 53 pkgs Spawning worker 20 with 53 pkgs Spawning worker 21 with 53 pkgs Spawning worker 22 with 53 pkgs Spawning worker 23 with 53 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File /usr/share/createrepo/genpkgmetadata.py, line 308, in module main(sys.argv[1:]) File /usr/share/createrepo/genpkgmetadata.py, line 280, in main mdgen.doRepoMetadata() File /usr/lib/python2.7/dist-packages/createrepo/__init__.py, line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File /usr/lib/python2.7/dist-packages/sqlitecachec.py, line 55, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 247651 Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid. Comparing patchsets in debian package sources between 2.9.1+dfsg1 and 2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one of them helps in my problem: 2.9.1+dfsg1-3ubuntu4.3: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-Fix-an-error-in-xmlCleanupParser.patch 0003-Fix-missing-break-on-last-function-for-attributes.patch 0004-xmllint-memory-should-fail-on-empty-files.patch 0005-properly-quote-the-namespace-uris-written-out-during.patch 0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0006-fix-python-multiarch-includes.patch 0007-Fix-XPath-optimization-with-predicates.patch CVE-2014-0191.patch lp1321869.patch xmllint_pretty.patch 2.9.1+dfsg1: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-fix-python-multiarch-includes.patch 0003-Fix-an-error-in-xmlCleanupParser.patch 0004-Fix-missing-break-on-last-function-for-attributes.patch 0005-xmllint-memory-should-fail-on-empty-files.patch 0006-properly-quote-the-namespace-uris-written-out-during.patch 0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0008-missing-else-in-xlink.c.patch 0009-Catch-malloc-error-and-exit-accordingly.patch 0010-Fix-handling-of-mmap-errors.patch 0011-Avoid-crash-if-allocation-fails.patch 0012-Fix-a-possible-NULL-dereference.patch 0013-Clear-up-a-potential-NULL-dereference.patch 0014-Fix-XPath-optimization-with-predicates.patch 0015-xmllint-pretty-crashed-without-following-numeric-arg.patch 0016-Fix-potential-NULL-pointer-dereferences-in-regexp-co.patch 0017-Fix-a-potential-NULL-dereference-in-tree-code.patch 0018-Fix-pointer-dereferenced-before-null-check.patch 0019-Fix-a-bug-loading-some-compressed-files.patch 0020-Avoid-a-possibility-of-dangling-encoding-handler.patch
[Touch-packages] [Bug 1219942] Re: Power indicator shows wrong time left to charge on Lenovo Ideapad Y580
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1219942 Title: Power indicator shows wrong time left to charge on Lenovo Ideapad Y580 Status in “upower” package in Ubuntu: Confirmed Bug description: The power indicator shows time left to charge being 5, 4, 3, 2, 1 or Time left unknown instead of the real duration. The time left on battery power is correctly computed. When I remove the power, it takes a little bit until it switches from the wrong duration to charge to the real time left on battery power, sometimes going to sleep as a result of thinking it has little power left. See the screenshot for the displayed value. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.03.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Mon Sep 2 21:11:00 2013 InstallationDate: Installed on 2013-01-09 (236 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-09-01 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1219942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340511] Re: man page contains wrong default history size
Man page contains the text: HISTSIZE The number of commands to remember in the command history (see HISTORY below). The default value is 500. I think that means that if HISTSIZE isn't set at all, then Bash will act as though HISTSIZE had been set to 500. If you have HISTSIZE set, then the default doesn't apply. $ grep HISTFILESIZE ~/.bashrc HISTFILESIZE=2000 That's HISTFILESIZE, not HISTSIZE. They are different variables, to control different (albeit related) things. However, skel.bashrc does also set HISTSIZE, to 1000. But that doesn't make the manpage wrong. Ubuntu gives new users a HISTSIZE variable, but it's still the case that a user who removes that will get a default size of 500. So I think this is invalid. ** Changed in: bash (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1340511 Title: man page contains wrong default history size Status in “bash” package in Ubuntu: Invalid Bug description: man page contains wrong default history size Steps to reproduce: 1.$ man bash 2. Search for HISTSIZE (press /then type HISTSIZE and press ENTER) Actual result: Man page contains the text: --- HISTSIZE The number of commands to remember in the command history (see HISTORY below). The default value is 500. --- Expected result The default value is 2000. Additional information: $ wc -l ~/.bash_history 2000 /home/user/.bash_history $ grep HISTFILESIZE ~/.bashrc HISTFILESIZE=2000 $ apt-get source bash $ cd bash-4.2/ $ grep -nr HISTFILESIZE . ./debian/skel.bashrc:20:HISTFILESIZE=2000 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bash 4.2-5ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Fri Jul 11 11:41:58 2014 InstallationDate: Installed on 2014-02-18 (143 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Beta i386 (20130926) MarkForUpload: True SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1340511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278729] Re: hplip-gui showing wrong character settings - guess greeek
** Branch linked: lp:ubuntu/utopic-proposed/gtk+2.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1278729 Title: hplip-gui showing wrong character settings - guess greeek Status in HP Linux Imaging and Printing: Confirmed Status in “gtk+2.0” package in Ubuntu: Fix Committed Bug description: afterwards hplip gui chrashed - I unstalled hlplip-gui ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.1-1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Feb 11 08:18:06 2014 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2014-02-08 (2 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP_LaserJet_M1522nf_MFP: hp:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 device for HP_LaserJet_M1522nf_MFP_fax: hpfax:/usb/HP_LaserJet_M1522nf_MFP?serial=00CNDT8BMHL7 MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: HP_LaserJet_M1522nf_MFP: HP LaserJet m1522nf MFP pcl3, hpcups 3.14.1 HP_LaserJet_M1522nf_MFP_fax: HP Fax2 hpcups ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=a46d1948-9e5d-4e51-964b-e5de7b76a7a3 ro SegvAnalysis: Segfault happened at: 0x5b169d: mov0x10(%rax),%rdi PC (0x005b169d) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction() UpgradeStatus: Upgraded to trusty on 2014-02-08 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd02/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1278729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
Here is patch for pulseaudio which fixing this problem: http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-September/021844.html Patch automatically switch between a2dp and hsp profiles based on number of recording streams. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/508522 Title: Mic is not available with A2DP Bluetooth profile Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles HSP/ HFP Telephony duplex and A2DP High Fidelity Playback. For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or telephone quality with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
Came up after installing the nvidia 331.89 driver from the Driver tool, in Ubuntu Gnome 14.10 ** Also affects: ubuntu-gnome Importance: Undecided Status: New ** No longer affects: ubuntu-gnome -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe Status in “init-system-helpers” package in Ubuntu: Confirmed Bug description: [ 16.934379] init: Error while reading from descriptor: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: init 1.20ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 2 17:23:15 2014 InstallationDate: Installed on 2014-04-27 (128 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1364630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices
Jamie, I tried to add the following code to log the file permissions:
QStringList runtimeDirs =
QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation);
QString runtimeDir = (runtimeDirs.size() 0 !runtimeDirs[0].isEmpty())
? runtimeDirs[0] : qgetenv(XDG_RUNTIME_DIR);
if (runtimeDir.isEmpty()) {
qWarning() [StateSaver] No XDG_RUNTIME_DIR path set, cannot create
appstate file.;
return;
}
QString path =
QString(%1/%2/statesaver.appstate).arg(runtimeDir).arg(applicationName);
qDebug() [StateSaver] PATH path;
// log permissions
QFile::Permissions wanted = QFile::ReadUser | QFile::WriteUser |
QFile::ExeUser;
QFile xdg(runtimeDir);
qDebug() QString([StateSaver] PERMISSIONS %1 WANTED
%2).arg(xdg.permissions(), 0, 16).arg(wanted, 0, 16);
And I'm getting the following result:
QStandardPaths: wrong permissions on runtime directory /run/user/32011
[StateSaver] PATH /run/user/32011/com.ubuntu.camera/statesaver.appstate
[StateSaver] PERMISSIONS 7700 WANTED 700
So, QFile::permissions() return 0x7700 for XDG_RUNTIME_DIR, which is
weird!
--
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/1363112
Title:
StateSaver is not working on devices
Status in Ubuntu UI Toolkit:
Confirmed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Fix Released
Status in “camera-app” package in Ubuntu:
Fix Released
Bug description:
build 212
The StateSaver is not working anymore on devices, so apps saved state is no
longer restored when they are relaunched after being killed by oom killer (or
manually via kill -2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1363112/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376688] [NEW] Punctuation-only functions give error messages in subshells
Public bug reported: I have Bash functions defined with punctuation-only names, such as - and .., which now give errors when starting nested shells. After a recent Shellshock patch, env shows these functions as having names like BASH_FUNC_-(), and starting a second Bash in some way, such as running a shell script, yields error messages like: bash: error importing function definition for `BASH_FUNC_-' With a double-nested Bash, each error message is displayed twice. So far as I can tell the error message is spurious: the action function - is being imported correctly. But it's irritating to have the terminal clogged up with these messages, especially when just running utilities which I didn't even know were written in Bash. This is with bash 4.3-7ubuntu1.4. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1376688 Title: Punctuation-only functions give error messages in subshells Status in “bash” package in Ubuntu: New Bug description: I have Bash functions defined with punctuation-only names, such as - and .., which now give errors when starting nested shells. After a recent Shellshock patch, env shows these functions as having names like BASH_FUNC_-(), and starting a second Bash in some way, such as running a shell script, yields error messages like: bash: error importing function definition for `BASH_FUNC_-' With a double-nested Bash, each error message is displayed twice. So far as I can tell the error message is spurious: the action function - is being imported correctly. But it's irritating to have the terminal clogged up with these messages, especially when just running utilities which I didn't even know were written in Bash. This is with bash 4.3-7ubuntu1.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1376688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376687] Re: Google Chrome crashes in i965_dri.so
Removed core dump from the crash report, for security / privacy reasons. Feel free to request by email. ** Attachment added: 01_opt_google_chrome_chrome.1000.crash.nocore https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1376687/+attachment/466/+files/01_opt_google_chrome_chrome.1000.crash.nocore -- 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/1376687 Title: Google Chrome crashes in i965_dri.so Status in “mesa” package in Ubuntu: New Bug description: Since installing the Ubuntu 14.10 beta update, I see Google Chrome crash on startup. This happens about 1/3 of the time. The issue doesn't exist with same Chrome version, on same hardware, in Fedora 20 -- and did not exist prior to updating to Ubuntu 14.10 beta (i.e. 14.04). There have been a few large Ubuntu updates since I installed the beta, but the issue continues to happen. Hardware: Intel 4770 with built-in video, dual monitor, 16 GB RAM, SSDs, 64-bit mode. Software: XUbuntu A detailed crash report is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1376687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1285783] Re: Right panel has a transparent background
Hmm, the patch along with the one from gtk+ https://git.gnome.org/browse/gtk+/commit/?id=02ccfb5d62430590b11b2d3e34b6100e4a6ddcda doesn't fix it for me - does it for you? I also noticed that gtk3-widget-factory is also transparent. Is that the same? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in “gtk+3.0” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Fix Committed Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1285783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343242] Re: Departments break if going to a subdepartment of Store
I've just re-checked this bug, and it does affect store after all, but symptoms are slightly different, so I've updated the description. ** Description changed: Departments get confused / break when going from a subdepartment of Apps - (click scope) to same subdepartment of Store (click store scope) via a - canned query. Department ids of both scopes are the same (if this is - significant at all). - - UPDATED: this problem cannot be reproduced anymore with Ubuntu Store - because it now has flat hierarchy of departments; and as far as I know, - there are no other scopes affected by it at the moment. However, the - problem is valid and will affect scopes with deep hierarchy of - departments whenever a canned query attempts to perform search in a - subdepartment. + (click scope) to same subdepartment of Store via Get more apps like + this orange Store button. Steps to reproduce: 1) Open Apps. - 2) Go to Internet department - 3) Click the orange 'Ubuntu store' icon at the bottom (its category title should say Get more apps like thisfrom the Store). - 4) You should be presented with the 'Top interent Apps' category of the store, and department tree has only All Departments and Internet subdepartment. It's not possible to navigate to the root of the store from it. + 2) Go to Games department + 3) Click the orange 'Ubuntu store' icon at the bottom (its category title should say Get more apps like this from the Store). + 4) You should be presented with the 'Top Games' category of the store, and department tree has only All and Games subdepartment. It's not possible to navigate to the root of the store from it, as UI thinks All is the current department. Clicking Games department, and then All restores the correct departments menu. -- 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/1343242 Title: Departments break if going to a subdepartment of Store Status in “unity-scopes-shell” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: Departments get confused / break when going from a subdepartment of Apps (click scope) to same subdepartment of Store via Get more apps like this orange Store button. Steps to reproduce: 1) Open Apps. 2) Go to Games department 3) Click the orange 'Ubuntu store' icon at the bottom (its category title should say Get more apps like this from the Store). 4) You should be presented with the 'Top Games' category of the store, and department tree has only All and Games subdepartment. It's not possible to navigate to the root of the store from it, as UI thinks All is the current department. Clicking Games department, and then All restores the correct departments menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1343242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***
** Branch linked: lp:~alan-griffiths/mir/fix-1376324 ** Changed in: mir Status: Incomplete = In Progress -- 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/1376324 Title: /usr/sbin/unity-system-compositor:*** Error in `unity-system- compositor': free(): invalid pointer: ADDR *** Status in Mir: In Progress Status in Unity System Compositor: Incomplete Status in “mir” package in Ubuntu: Incomplete Status in “unity-system-compositor” package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+14.10.20140917-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1092905] Re: incorrect placement on multimonitor systems with focus-follow on
** Changed in: hundredpapercuts Status: New = Fix Released -- 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/1092905 Title: incorrect placement on multimonitor systems with focus-follow on Status in One Hundred Papercuts: Fix Released Status in Unity: Invalid Status in “notify-osd” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: When changing the volume via the mouse scroll wheel over the volume indicator, the libnotify pop-up displaying the current volume is placed a little too high, obscuring all the indicators. The volume bubble should be placed lower. Screenshot will be attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,resize,move,gnomecompat,snap,mousepoll,wall,imgpng,regex,place,commands,grid,session,unitymtgrabhandles,animation,fade,workarounds,expo,scale,ezoom,unityshell] Date: Fri Dec 21 14:46:22 2012 InstallationDate: Installed on 2012-05-10 (225 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-19 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1092905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
Uhm erong bug report. Disregard my last comment please -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe Status in “init-system-helpers” package in Ubuntu: Confirmed Bug description: [ 16.934379] init: Error while reading from descriptor: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: init 1.20ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 2 17:23:15 2014 InstallationDate: Installed on 2014-04-27 (128 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1364630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
This also happens on systems that neither have nvidia graphic cards nor the nvidia driver installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe Status in “init-system-helpers” package in Ubuntu: Confirmed Bug description: [ 16.934379] init: Error while reading from descriptor: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: init 1.20ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 2 17:23:15 2014 InstallationDate: Installed on 2014-04-27 (128 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1364630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@Sergio OK, I feel like a real hacker. Managed to install the network-test-sessions after a while modyfying some of your suggested commands. Pls see attached file after sending MMS and trying to receive an MMS. Sending goes through, but nothing happens when receiving. ** Attachment added: network-test-session_10-02-2014_14:07:10.tar.gz https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1370376/+attachment/496/+files/network-test-session_10-02-2014_14%3A07%3A10.tar.gz -- 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/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in “network-manager” package in Ubuntu: New Status in “nuntium” package in Ubuntu: Incomplete Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359815] Re: virt-manager crashed with SIGSEGV in _pygi_argument_from_object()
** Changed in: pygobject Status: Unknown = Fix Released ** Changed in: pygobject Importance: Unknown = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1359815 Title: virt-manager crashed with SIGSEGV in _pygi_argument_from_object() Status in Python bindings for GObject: Fix Released Status in Virtual Machine Manager: Unknown Status in “pygobject” package in Ubuntu: Fix Released Bug description: Double click in conection ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: virt-manager 1:1.0.1-0ubuntu2 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 CurrentDesktop: GNOME Date: Thu Aug 21 11:07:33 2014 ExecutablePath: /usr/share/virt-manager/virt-manager InstallationDate: Installed on 2014-04-27 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager SegvAnalysis: Segfault happened at: 0x7f1a2f269fb7:mov(%rax),%rax PC (0x7f1a2f269fb7) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: virt-manager StacktraceTop: ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_cell_renderer_get_preferred_width () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: virt-manager crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1359815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376701] [NEW] invalid key/value pair in file /lib/udev/rules.d/
Public bug reported:
from a fully updated Utopic (proposed enabled), the syslog file shown
these errors:
(following that linux-boot-prober: debug: running /usr/lib/linux-boot-
probes/50mounted-tests)
Oct 2 08:36:16 u32 systemd-udevd[241]: GOTO 'libgphoto2_usb_end' has no
matching label in: '/lib/udev/rules.d/40-libgphoto2-6.rules'
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/40-usb-media-players.rules on line 26,starting at character
25 ('m')
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1 ('n')
That has happened while upgrading some packages from synaptic: purging
an old kernel, installing a newest one
Then later, after grub2 processes ended, get these errors:
linux-boot-prober: debug: linux detected by
/usr/lib/linux-boot-probes/50mounted-tests
Oct 2 08:43:15 u32 systemd[1]: Reloading.
Oct 2 08:43:15 u32 systemd[1]:
[/lib/systemd/system/friendly-recovery.service:14] Executable path is not
absolute, ignoring: dmesg --console-off
Oct 2 08:43:15 u32 systemd[1]: [/lib/systemd/system/rtkit-daemon.service:32]
Unknown lvalue 'ControlGroup' in section 'Service'
Oct 2 08:43:15 u32 systemd[1]: Cannot add dependency job for unit
systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service
failed to load: No such file or directory.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu7
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Thu Oct 2 14:10:08 2014
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 utopic
** Description changed:
- from an fully updated Utopic (proposed enabled), the syslog file shown
+ from a fully updated Utopic (proposed enabled), the syslog file shown
these errors:
(following that linux-boot-prober: debug: running /usr/lib/linux-boot-
probes/50mounted-tests)
Oct 2 08:36:16 u32 systemd-udevd[241]: GOTO 'libgphoto2_usb_end' has no
matching label in: '/lib/udev/rules.d/40-libgphoto2-6.rules'
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/40-usb-media-players.rules on line 26,starting at character
25 ('m')
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1 ('n')
-
- That has happened while upgrading some packages from synaptic: purging an old
kernel, installing a newest one
+ That has happened while upgrading some packages from synaptic: purging
+ an old kernel, installing a newest one
Then later, after grub2 processes ended, get these errors:
linux-boot-prober: debug: linux detected by
/usr/lib/linux-boot-probes/50mounted-tests
Oct 2 08:43:15 u32 systemd[1]: Reloading.
Oct 2 08:43:15 u32 systemd[1]:
[/lib/systemd/system/friendly-recovery.service:14] Executable path is not
absolute, ignoring: dmesg --console-off
Oct 2 08:43:15 u32 systemd[1]: [/lib/systemd/system/rtkit-daemon.service:32]
Unknown lvalue 'ControlGroup' in section 'Service'
Oct 2 08:43:15 u32 systemd[1]: Cannot add dependency job for unit
systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service
failed to load: No such file or directory.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu7
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Thu Oct 2 14:10:08 2014
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1376701
Title:
invalid key/value pair in file /lib/udev/rules.d/
Status in “systemd” package in Ubuntu:
New
Bug description:
from a fully updated Utopic (proposed enabled), the syslog file shown
these errors:
(following that linux-boot-prober: debug: running /usr/lib/linux-
boot-probes/50mounted-tests)
Oct 2 08:36:16 u32 systemd-udevd[241]: GOTO 'libgphoto2_usb_end' has no
matching label in: '/lib/udev/rules.d/40-libgphoto2-6.rules'
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/40-usb-media-players.rules on line 26,starting at character
25 ('m')
Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file
/lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1 ('n')
That has happened while upgrading some packages from synaptic: purging
an old
[Touch-packages] [Bug 1370571] Re: Read-only text field doesn't look read-only
So read only text fields should always look as if they have focus? That seems very confusing to me. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- 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/1370571 Title: Read-only text field doesn't look read-only Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: Ubuntu 14.10 r244 1. Connect the phone to a Wi-Fi network if it isn't already. 2. Navigate to System Settings Wi-Fi the chevron next to the current network. 3. Tap in the IP address field. What you see: 2. The field is grey. 3. The field is white. What you should see: Since the field is read-only, it should look exactly the same when it isn't focused as when it is. (The use of a read-only text field is a workaround for bug 1286282.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1370571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356864] Re: Button with strokeColor does not change font colour
The stroke button is not meant to have the same border and font color. Not per the latest design. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete ** 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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1356864 Title: Button with strokeColor does not change font colour Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: Given the attached QML, there is no way to change the font color inside the button, which should basically be the same as the stroke color. I don't think it's necessary to allow overriding the font color alone in the case of a stroke button, everything should be the same. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1181+14.10.20140806-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 14 14:49:47 2014 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1356864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 970038] Re: Launcher do not want to appear
I can reproduce it 90% of the times using the attached html file in both Chrome and Firefox (just one pre tag with enough text to show the horizontal scrollbar). In my case, scrolling it to the right and all the way back to the left, so that the mouse pointer is in the panel's area, cause unity panel to fail to reveal. As I also found out, it doesn't have to be a web browser - text editor like GEdit will result in the same behavior, when a line is long enough to reveal the horizontal scrollbar. ** Attachment added: Horizontal scrolling causes unity panel to fail to reveal. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/970038/+attachment/4222332/+files/unity_panel_not_revealing.html -- 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/970038 Title: Launcher do not want to appear Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: All time testing new U 12.04 I have the same problem. After enabling the Auto-hide the Launcher I have problem to reach that Launcher appears again. I move the pointer lo left, but just the margin of screen gets darker - thats all. I have to repeat moving pointer right - left many times (sometimes 4x, sometimes 15x) before I get finally Launcher visible again. To let pointer at border longer don't help. I have Intel's G840 CPU with Sandy HD graphic (if it matters). I hope, it will be corrected before final release. Thanks --kapetr ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Mar 31 13:17:50 2012 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120331) ProcEnviron: TERM=xterm LANG=en_US.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/970038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1232130] Re: Uninstalling an app doesn't stop it
I pushed a version that correctly gets the dbus session bus and stops the app for click unregister in lp:~mvo/click/lp1232130-kill-on- remove-2/ - however its not yet working under PK I'm looking into this now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1232130 Title: Uninstalling an app doesn't stop it Status in “click” package in Ubuntu: Triaged Status in “ubuntu-touch-meta” package in Ubuntu: Fix Released Bug description: Hi, Launch an installed app, uninstall it. Not only is it still listed in the list of installed apps (bug #1232129), it's also still in the running app lists, and if you press on the installed app icon or slide right, you get back to the running app. I think any running instance of this app should be killed along the removal. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1232130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
@mardy I'm also seeing this in other account plugins (namely fitbit and flickr). Is there any way to add unconfined to the ACL there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1376445 Title: Addition of signon-apparmor-extension causes token lookup problems Status in The Savilerow project: New Status in “ubuntuone-credentials” package in Ubuntu: Triaged Status in “ubuntuone-credentials” package in Ubuntu RTM: Triaged Bug description: As of image ~264 of ubuntu-touch, the signon-apparmor-extension package is included. As a result, apps like pay-ui cannot find the token any longer, and are not being notified that they are not allowed to access the token. The following error appears in the payui log file: 2014-10-01 19:15:51,550 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot QDBusError(com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied, Client has insuficient permissions to access the service.Method:getAuthSessionObjectPath) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1376445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376707] Re: Launcher needs to dynamically respond to reset
System settings will need to remove the text instructing the user that a reboot is required -- 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/1376707 Title: Launcher needs to dynamically respond to reset Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Currently the reset launcher action initiated from the system settings app requires the user to reboot the device. The intended design is for the launcher to dynamically reset to the initial state and briefly reveal itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1376707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376707] [NEW] Launcher needs to dynamically respond to reset
Public bug reported: Currently the reset launcher action initiated from the system settings app requires the user to reboot the device. The intended design is for the launcher to dynamically reset to the initial state and briefly reveal itself. ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (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/1376707 Title: Launcher needs to dynamically respond to reset Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Currently the reset launcher action initiated from the system settings app requires the user to reboot the device. The intended design is for the launcher to dynamically reset to the initial state and briefly reveal itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1376707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
