at-spi2-registryd.conf upstart script missing closing ']'
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| at-spi2-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Saucy |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Impact
At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In addition, the following is shown in the user's local upstart logs for at-spi2-registryd:
/proc/self/fd/9: 2: [: missing ]
Regression potential:
Little to none at all given that this was a typo.
Test case:
1. Install the new at-spi2-core package from saucy-proposed.
2. Remove the at-spi2-core upstart log from ~/.cache/upstart.
3. Log out and back in.
4. The below error should not be present in the at-spi2-core upstart log.
Hi,
I'm seeing a bunch of missing ']' errors in ~/.cache/
pre-start script
[ "$(gsettings get org.gnome.
= "true" || exit 0
end script
It seems like an easy fix but I can't seem to find which LP branch to create a merge proposal against.
Regards,
Haw
---
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 13.10
MarkForUpload: True
Package: at-spi2-core 2.10.0-0ubuntu2 [modified: usr/share/
PackageArchitec
ProcVersionSign
Tags: saucy
Uname: Linux 3.11.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video
modified.
mtime.conffile.
| description: | updated |
| description: | updated |
| Changed in at-spi2-core (Ubuntu Saucy): | |
| status: | New → In Progress |
| description: | updated |

apport information