** Changed in: at-spi2-atk (Ubuntu)
Assignee: Marcus Tomlinson (marcustomlinson) => (unassigned)
** Changed in: orca (Ubuntu)
Assignee: Marcus Tomlinson (marcustomlinson) => (unassigned)
** Changed in: orca (Ubuntu Focal)
Assignee: Marcus Tomlinson (marcustomlinson) => (u
** Changed in: libreoffice (Ubuntu)
Status: Triaged => Fix Released
--
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/1624571
Title:
White lines visible around L
** Changed in: libreoffice (Ubuntu Disco)
Status: New => Fix Released
** Changed in: libreoffice-l10n (Ubuntu Disco)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
htt
** Changed in: libreoffice (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese new era "令
** Changed in: libreoffice-l10n (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: libreoffice (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: libreoffice (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: libreoffice-l10n (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Bug watch added: Document Foundation Bugzilla #46924
https://bugs.documentfoundation.org/show_bug.cgi?id=46924
** Changed in: df-libreoffice
Importance: Medium => Unknown
** Changed in: df-libreoffice
Status: Won't Fix => Unknown
** Changed in: df-libreoffice
Remote watch: freed
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Disco)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: libreoffice (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch s
** Package changed: libreoffice (Ubuntu) => gtk+3.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/1856604
Title:
First char appears twice when searching in "Save
** Summary changed:
- Regression: cannot use impress remote over bluetooth with ubuntu bionic
+ [upstream] Regression: cannot use impress remote over bluetooth with ubuntu
bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Incomplete
--
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/1496875
Title:
smartscopesproxy uses a lo
There is an info() method on SearchReply and PreviewReply objects. This
method informs the shell that some non-fatal, warning condition has
occurred during the query. This method takes a OperationInfo argument
that can be configured to describe a number of warning conditions via an
enum such as: No
I think the bug here is that you are seeing an Unknown status at all.
That shouldn't happen. The shell sets the connectivity status before it
dispatches queries, so you should only get Connected or Disconnected.
Unknown is really more of an uninitialised state.
Could you please point me to the sou
Michi, have a look at http://bazaar.launchpad.net/~unity-team/unity-
scopes-shell/trunk/view/head:/src/Unity/scope.cpp#L745
The scope should actually never receive scopes::SearchMetadata::Unknown.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
The discussion has derailed somewhat from the original issue, please
continue this elsewhere.
Coming back to this particular bug, we only provide the statuses
Connected and Disconnected to the scope from the shell. The Unknown
status is an uninitialised state and should never reach the scope.
Seei
** Changed in: mediascanner2 (Ubuntu)
Status: New => In Progress
--
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/1508142
Title:
Mediascanner crashes and loops
Adding unity8 to affected packages. This sounds like a UI bug
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://
Hey Chris, we have a little more detail on ResultTtl under the
"Deployment" section of our API doc:
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1/index/
("ResultTtl determines how long results should be cached...")
Currently these values are set (in unity-scopes-shell) to:
const int RE
@jibel this was mistakenly set to Fix Released when it was merged to our
intermediate level branch. This has not landed yet. Setting back to Fix
Committed. Jenkins should take care of setting to Fix Released once i
does actually land. Sorry about the confusion.
** Changed in: unity-scopes-api (Ubu
NOTE: This may already be known, but in case it is not, this bug and bug
#1510015 are no doubt related. Perhaps not duplicate, but related none-
the-less.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
U
** Changed in: gallery-app (Ubuntu)
Assignee: (unassigned) => James Henstridge (jamesh)
** Changed in: gallery-app (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Fix Released
--
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/1274635
Title:
Scoperegistry exits if r
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Fix Committed
--
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/1452423
Title:
Typo in tutorial docume
*** This bug is a duplicate of bug 1430918 ***
https://bugs.launchpad.net/bugs/1430918
** This bug has been marked a duplicate of bug 1430918
Enable/disable child scopes error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
So the interesting part is: "terminate called without an active
exception". This usually means a thread was terminated without join().
Looking at a stack trace of the seemingly duplicate bug (Bug #1432725),
looks like that just may be the problem:
Stacktrace:
#0 0xb6b2c8e6 in ?? () from /lib/arm
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1452681
Title:
Incomplete doc
** Changed in: net-cpp (Ubuntu)
Status: In Progress => Fix Released
** Branch linked: lp:unity-scopes-api/staging
--
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/b
** Changed in: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1452681
Title:
Incomplete doc
** Changed in: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1412367
Title:
Show SSS resul
Ok so I can reproduce this issue flawlessly by connecting to a
subscription hotspot nearby and refreshing any remote scope (In fact
there seems to generally be high CPU usage spikes coming from the
smartscopesproxy process even on a working wifi spot). This is on the
mako with:
build: 113
channel:
** Branch linked: lp:~stolowski/unity-scopes-api/settingsdb-use-
timestamp
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Pawel Stolowski (stolowski)
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
You received this bug notification because
*** This bug is a duplicate of bug 1448889 ***
https://bugs.launchpad.net/bugs/1448889
** This bug has been marked a duplicate of bug 1448889
Launch launcher will dismiss Ubuntu Store scope sometimes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
I've attached a .zip containing a scope click package and a
install_loop.sh script that installs and uninstalls the click every 15s.
After a few installs, the phone reboots. (Tested on mako 234)
** Attachment added: "install_loop.zip"
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/
Hmmm, just tried the same thing with an app click package, and no crash.
(zip attached)
** Attachment added: "app_install_loop.zip"
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1450493/+attachment/4419445/+files/app_install_loop.zip
--
You received this bug notification be
Adding 'sudo dmesg' to the app install loop script now produces:
[ 1823.580344] type=1400 audit(1435070740.169:104): apparmor="STATUS"
operation="profile_replace" profile="unconfined"
name="com.viclog.hodor_hodor_0.2" pid=22736 comm="apparmor_parser"
[ 1859.959133] type=1400 audit(1435070776.548
Hmmm, ok so it looks every time the app installs, another
profile_replace call shows up in dmesg.
So after the first install: 1 profile_replace call is shown.
Then when its uninstalled: still 1 profile_replace call is shown.
Then it is installed again: now 2 profile_replace calls are shown.
etc...
** Branch linked: lp:~stolowski/unity-scopes-api/fix-settings-thread
--
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/1430918
Title:
Change setting requires manua
debug a scope on
the desktop.
** Affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Assignee: Marcus Tomlinson (marcustomlinson)
Status: In Progress
** Description changed:
Upon determining whether a scope is in debug mode, the scope must be
located via the registry. The
** Branch linked: lp:~marcustomlinson/unity-scopes-
api/fix_debug_mode_locate_timeout
--
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/1469069
Title:
Two-way reques
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => High
--
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/1469069
Title:
Two-way request for debug
Hardcoded values found in scoperegistry.cpp and ZmqScope.cpp. Search for
"3".
** Description changed:
The process timeout and locate timeouts in debug mode are currently
hardcoded in the source to 30s. These should be moved to
"Debug.Process.Timeout" in the registry config, and a
"Deb
Public bug reported:
The process timeout and locate timeouts in debug mode are currently
hardcoded in the source to 30s. These should be moved to
"Debug.Process.Timeout" in the registry config, and a
"Debug.Locate.Timeout" in the ZMQ config.
Doxygen doc and/or CONFIGFILES should also be updated a
** Branch linked: lp:~marcustomlinson/unity-scopes-
api/debug_timeout_config_params
** Changed in: unity-scopes-api (Ubuntu)
Status: Confirmed => In Progress
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
--
You receive
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1469105
Title:
Debug process a
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1469069
Title:
Two-way request
Public bug reported:
The unity-scope-tool is not handling unix termination signals, and hence
is not cleaning up its scoperegisry child process correctly.
** Affects: unity8 (Ubuntu)
Importance: Undecided
Assignee: Marcus Tomlinson (marcustomlinson)
Status: In Progress
Reopening this bug as disabling the timeouts completely has been decided
to be the better option than lenient timeouts in debug mode.
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => In Progress
** Branch linked: lp:~marcustomlinson/unity-scopes-
api/disable_timeouts_in_de
** Summary changed:
- ZmqConfig / RegistryConfig are missing tests
+ ZmqConfig is missing tests
** Description changed:
- ZmqConfig is missing unit tests (and because of that it doesn't even count
for coverage reports).
- RegistryConfig has very few basic tests - at the very least the new
Debu
Changing status to "Won't Fix" as the linked branch changes were
reverted. It has been decided that we should rather disable timeouts
altogether in debug mode, rather than just using lenient timeouts.
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Won't Fix
--
You recei
The CPU spike is triggered upon uninstalling a scope. A single install /
uninstall cycle reproduces this issue.
--
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/147075
Looking further into this issue, it actually looks related to this bug:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750
This reboot issue seems to occur on the nexus but not the bq. The bug
above describes behaviour experienced on the arale and bq when
uninstalling a scope,
I was able to recreate this on OTA-4 on the Nexus.
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 20
device name: mako
channel: ubuntu-touch/stable/ubuntu
last update: 2015-07-03 14:43:04
version version: 20
version ubuntu: 20150611.3
version device: 20150210
version custom: 2
Ok, we've narrowed this issue down to a single change we made to delay
notifying the dash when a scope is removed. Makes sense that it was
triggered upon uninstalling a scope. A fix is in the pipeline.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Pawel Stolowski (stolowski)
--
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/1470750
Title:
*** This bug is a duplicate of bug 1470750 ***
https://bugs.launchpad.net/bugs/1470750
I have just confirmed that this bug is directly related to bug #1470750.
The proposed fix for that bug fixes this one. Marking as duplicate.
** This bug has been marked a duplicate of bug 1470750
scopere
** Changed in: unity-scopes-api (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-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1469069
Title:
Two-way request
Fix released into lp:unity-scopes-api at revision 343
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a
Bug fixed upstream, setting Status to "Fix Released"
** Changed in: unity-scopes-api (Ubuntu)
Status: Confirmed => Fix Released
--
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.l
** Changed in: unity-scopes-api (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-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1437047
Title:
Scopes API Impor
** Changed in: unity-scopes-api (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/1422700
Title:
'Dash search'
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** Changed in: unity-scopes-api (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
** Changed in: unity-scopes-api (Ubuntu)
Assignee: Alejandro J. Cura (alecu) => Marcus Tomlinson (marcustomlinson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Looks like we are missing some null checks in JsonCppNode. We have this
in only one of the get_node() methods but not in the other 2 overloads.
Looking at the crash report it is definitely one of the get_node()
methods attempting to dereference a null root node. I've linked a branch
to fix this.
*
** Also affects: at-spi2-atk (Ubuntu)
Importance: Undecided
Status: New
** Changed in: at-spi2-atk (Ubuntu)
Status: New => Fix Committed
** Changed in: at-spi2-atk (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** Changed in: at-spi2-atk (
=> Triaged
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** No longer affects: ubuntu-meta (Ubuntu)
** No longer affects: gnome-logs (Ubuntu)
** No longer affects: gnome-characters (Ubuntu)
** No longer affects: gnome-calculator (Ubuntu
This crash looks to be due to an infinite loop between a child and
parent in atk.
This is what I think is happening:
- The loops begins with a call to atk_component_get_extents() on a gtk
notebook page.
- atk_component_get_extents() then calls iface->get_extents() [1]
- which translates to gtk_
This issue is present in atk 2.35.1-1ubuntu1 but not in 2.34.0-1.
Thankfully the diff between these releases is relatively small:
https://paste.ubuntu.com/p/wr93v8kWQ7/
Of particular interest is the introduction of the
atk_socket_component_real_get_extents() function, and the NEWS entry:
"Make At
This crash looks to be due to an infinite loop between a child and
parent in atk.
This is what I think is happening:
- The loops begins with a call to atk_component_get_extents() on a gtk
notebook page.
- atk_component_get_extents() then calls iface->get_extents() [1]
- which translates to gtk_
Upstream bug report: https://gitlab.gnome.org/GNOME/atk/-/issues/18
** Bug watch added: gitlab.gnome.org/GNOME/atk/-/issues #18
https://gitlab.gnome.org/GNOME/atk/-/issues/18
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: ubiquity via
https://gitlab.gnome.org/GNOME/atk/-/issues/18
Importance: Unknown
Status: Unknown
** No longer affects: ubiquity
** Also affects: atk via
https://gitlab.gnome.org/GNOME/atk/-/issues/18
Importance: Unknown
Status: Unknown
** No longer affec
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to atk1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1870508
Title:
ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
Status
** Changed in: atk1.0 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to atk1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1870508
Title:
ubiquity crashed with SIGSEGV in g_type
** Changed in: atk1.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to atk1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1870508
Title:
ubiquity crashed with SIGSEGV in g_
Ah ok, that’s really helpful Alex. I think let’s close this as wontfix
then as you suggested. Thanks for looking into this!
** Changed in: apport (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
1 - 100 of 3752 matches
Mail list logo
