** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/827934
Title:
colord crashed with SIGABRT in raise()
Status in “colord” package in Ubuntu:
Confirmed
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/905686
Title:
nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
Assertion `ret !=
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1018534
Title:
Missing icons on g-c-c with High Contrast theme
Status in
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1045666
Title:
Style differs if ubiquity is started directly from 'Install Ubuntu' or
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/960649
Title:
vino-server SIGABRT, buffer overflow detected in clipboard handling
code
Status in “vino”
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liferea in Ubuntu.
https://bugs.launchpad.net/bugs/1032172
Title:
liferea crashed with signal 5 in db_item_load()
Status in “liferea” package in Ubuntu:
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to indicator-weather in Ubuntu.
https://bugs.launchpad.net/bugs/765397
Title:
indicator-weather assert failure: *** glibc detected ***
/usr/bin/python:
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to indicator-weather in Ubuntu.
https://bugs.launchpad.net/bugs/817672
Title:
indicator-weather crashed with SIGSEGV in
dbusmenu_menuitem_get_children()
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/934531
Title:
gnome-settings-daemon crashed with SIGSEGV in unpress_keys()
Status in
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1041169
Title:
custom keyboard shortcuts not migrated after upgrade to compiz
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to indicator-weather in Ubuntu.
https://bugs.launchpad.net/bugs/857505
Title:
indicator-weather crashed with SIGABRT in raise()
Status in “indicator-weather”
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1040885
Title:
gnome-terminal auto-restores its size
Status in “gnome-terminal” package in
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1042223
Title:
test_purchase_backend.TestPurchaseBackend.test_add_license_key_backend
failed
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1056849
Title:
gedit crashed with signal 5 in _XReply()
Status in “gedit” package in Ubuntu:
New
Bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1057010
Title:
gwibber-service crashed with OSError in makedirs(): [Errno 17] File
exists:
Public bug reported:
This crash occurs consistently during the upgrade from Lucid to precise.
https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job
/precise-upgrade-lucid-desktop/ARCH=amd64,LTS=lts,PROFILE=ubuntu,label
=upgrade-test/
** Affects: gvfs (Ubuntu)
Public bug reported:
This crash happens consistently during Lucid to Precise upgrades on
amd64
https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job
/precise-upgrade-lucid-main/248/ARCH=amd64,LTS=lts,PROFILE=main-
all,label=upgrade-test/
** Affects:
** Summary changed:
- gvfs fuse deamon crash during Lucid to Precise desktop upgrade
+ gvfs fuse daemon crash during Lucid to Precise desktop upgrade
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
** Tags added: qa-testing-manual
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1029000
Title:
nautilus crashed with SIGABRT in raise()
Status in
*** This bug is a duplicate of bug 971353 ***
https://bugs.launchpad.net/bugs/971353
** Tags added: iso-testing qa-manual-testing rls-q-incoming
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Tags added: iso-testing q-manual-testing q-rls-incoming
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1045773
Title:
This occurred again when quantal-desktop-amd64+mac.iso of 20120905.2
during a live session. Just tried to do some settings change during the
live session, such as changing the keyboard layout, timezone change. If
it does not occur leave it for some time and this would occur.
ALSO, reported a
The same again during the live session on amd64 hardware. 20120905.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/971353
Title:
power : gnome-settings-daemon crashed
Public bug reported:
quantal- i386 and amd64,
/etc/pkcs11/modules/gnome-keyring-module is left after precise to
quantal upgrade
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1049057
Title:
Obsolete config files -gnome keyring module-left after precise to
quantal upgrades
Status in “gnome-keyring”
Public bug reported:
The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr
' after the precise to quantal upgrades leaving the two factor authorisation
impossible.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: signon-ui 0.11-0ubuntu1
ProcVersionSignature: Ubuntu
** Attachment added: dist-upgrade.tar.gz
https://bugs.launchpad.net/bugs/1060851/+attachment/3367787/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon-ui in Ubuntu.
Apparently this issue is not about quantal upgrade. I must have been
pressing it during either shorter or longer not in the middle. Closing
the bug since.
** Changed in: signon-ui (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
** Tags removed: rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1060851
Title:
Yubikey input is wrongly read after precise to quantal upgrade
Status in “signon-ui”
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1062191
Title:
gsettings-data-convert crashed with SIGSEGV in
g_settings_backend_path_changed()
** Visibility changed to: Public
** Tags added: qa-manual-testing
** Description changed:
- Occurred on armhf with 20121006 desktop when terminal application was
- closed
+ Occurred on quantal-desktop-armhf+omap4.img of 20121006 desktop when
+ terminal application was closed
ProblemType:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1063742
Title:
evolution-calendar-factory crashed with SIGFPE in
Public bug reported:
Occurred on a virt-manager vm running amd64 20121009 on a quantal
running 20121009.
1. A terminal window was opened and was moved to the bottom right hand corner
2. The workspace switcher was clicked *** at this point the vm logged out and
logged in by itself
3. Went to the
Occurrs in an i386 vm with 20121009 on a different amd64 host as well.
** Description changed:
Occurred on a virt-manager vm running amd64 20121009 on a quantal
running 20121009.
1. A terminal window was opened and was moved to the bottom right hand corner
- 2. The workspace switcher
Public bug reported:
Occurred during screen reader testing for amd64 quantal 20121010 soon
after the installer started
1. Start your machine with the install media in place
1.1 Wait to hear the drums
2. Press Ctrl+s to start the screen-reader
3. Press Alt+Tab to change to the installer
4.
The above occurred in
s-c version-5.4.1.1, arch- i386, Uname-Linux3.5.0-17-generic i686
** Tags added: quantal rls-q-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
Public bug reported:
On the first reboot to finish wubi installation of (both amd64 and i386) trying
to connect one of the listed wifi networks failed with the following message
Failed to add/activate connection: (32) insufficient privileges.
It was not possible to select a network inorder to
Public bug reported:
Fatal server error: Can not run in framebuffer mode error occurs on the 2nd
reboot onwards on a mac with external display.
The first reboot after a fresh installation is working fine and from the second
attempt the desktop fails to start on the standard graphics mode and
The above logs were taken from the first boot, hence does not have the
error information. The attached tar contains the log after the failure
** Attachment added: log.tar.gz
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3398945/+files/log.tar.gz
--
You received
Reproducible with 20121015.2 as well, after entire disk fresh
installation
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
Fatal server error: Can not run in framebuffer
When attempted with plymouth-splash disabled I am able to bring up the
desktop in the standard graphics mode. When plymouth-splash was re-
enabled, the issue is reproducible with mainline kernel 3.5.5.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Was able to reproduce with 3.5.4 mainline kernel version as well
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
Fatal server error: Can not run in framebuffer mode on
Occurs with 3.5.3 mainline kernel as well with plymouth-splash enabled
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
Fatal server error: Can not run in framebuffer mode
A fresh install with quantal desktop - amd+mac 20121011 also has the
same issue. First boot after the installation went well but the
subsequent ones do not boot in standard graphics mode.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
When tried with 20120724.2 amd+mac quantal desktop, this issue was not
reproducible (with ~10 reboots). Hence looking at bug 1066228 it appears
be a regression that occurred between alpha3 and beta 1.
--
You received this bug notification because you are a member of Desktop
Packages, which is
So here is the list of test runs,
20120724.2 - worked
20120918.1-worked
20121001 - worked
20121011 - FAILED
The kernel was updated to the latest on top of a working 20121001 and it
still worked
--
You received this bug notification because you are a member of Desktop
Packages, which is
@apw
Rebooted many times (more than 20) after updating the kernel to the latest on a
known (20121001) good image, it worked ok, no failures could be observed.
Removing /var/lib/ureadahead/pack from the known bad image seem to solve
the issue.
When it was made sure the file is removed before
** Attachment added: dmesg_good_first_boot
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401554/+files/dmesg_good_first_boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: dmesg_bad_second_boot
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401556/+files/dmesg_bad_second_boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Failure was observed in the second boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal server error: Can not run in framebuffer mode on
reboot
This only occurs with with KVM and not with VBox. The installation of
20121210 on VBox came up with correct desktop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
This is probably the expected behaviour. Marking the bug as invalid
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
The crash is occurring in a live system even where the installed version
on libglib2.0-bin is 2.35.4-0ubuntu5. This was observed on 20130128
raring desktop images.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
The latest traces are attached from an installation with 20130129
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505562/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Desktop
Packages,
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505564/+files/ThreadStacktrace.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
Public bug reported:
The attached crash occurred when the display resolution was changed soon
after the installation of 20130208 precise desktop amd64+mac image on a
Mac min 5.1
The following are the steps involved.
1. Install precise desktop amd64+mac 20130208 as given in
** Description changed:
The attached crash occurred when the display resolution was changed soon
after the installation of 20130208 precise desktop amd64+mac image on a
Mac min 5.1
The following are the steps involved.
1. Install precise desktop amd64+mac 20130208 as given in
Public bug reported:
This crash occurred during quantal to raring desktop auto-upgrades
amd64. The crash occurred only once and the consecutive run has passed.
A manual upgrade of an updated quantal desktop installation to raring
did not produce this crash either.
The testing was done in an
** Attachment added: with-1-1-5-2.png
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3482830/+files/with-1-1-5-2.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
xserver-xorg-video-cirrus 1:1.5.2-0ubuntu1 has NOT fixed the issue.
Please see the screenshot attached above. Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
Tried with quantal final image and i could not reproduce this after more
than 5 attempts.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1065113
Title:
Xorg crashed with SIGABRT
Right, thanks for the workaround. Raring VMs work fine when started with
-vga std.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
[QEMU] Corrupted desktop screen for
Confirmed with ubuntu-desktop-amd64 and ubuntu-desktop-i386 when using
VirtualBox. Did not see this issue on virt-manager using KVM and on
hardware.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
It is impossible to ssh to a raring desktop vm using the hostname except
the ip. It is required to manually edit /etc/hostname and /etc/hosts to
include the domain name (.local) inorder for the ssh connection using
the hostname to succeede.
1. Install raring desktop
Logs related to avahi-daemon using the host name with (.local) domain
name is attached
ubuntu@ubuntu2-virtual-machine:/var/log$ cat syslog | grep '\.local'
Nov 28 12:37:36 ubuntu2-virtual-machine avahi-daemon[643]: Server startup
complete. Host name is ubuntu2-virtual-machine.local. Local
** Summary changed:
- hostname of raring desktop vm does not match the entries in /etc/hostname
/etc/hosts
+ Can not ssh to raring VM's using hostname
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
@bryce:
Booting with quantal kernel does not work around the problem. The desktop is
still corrupted. Please see attached image
** Attachment added: with_quantal_kernel.png
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3446108/+files/with_quantal_kernel.png
**
** Description changed:
It is impossible to ssh to a raring desktop vm using the hostname except
the ip. It is required to manually edit /etc/hostname and /etc/hosts to
include the domain name (.local) inorder for the ssh connection using
the hostname to succeede.
- 1. Install raring
What I am trying to do is to ssh to VMs installed using libvirt from
precise/ quantal hosts. I have updated the steps to be clearer.
I am able to ssh to a VM with 20121108.2 i386 raring image installed using
libvirt without any issues .
'ssh ubuntu@ubuntu-virtual-machine' connects fine to
OK, here's what I have found lately,
To the VM's created using an old image raring-desktop-i386 -20121108.2 i386
(using libvirt on quantal host) I can ssh fromt he same host using
ssh ubuntu@ubuntu-virtual-machine
But to the VM's crated using the latest images
Public bug reported:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
** Attachment added: Preference Settings.png
https://bugs.launchpad.net/bugs/1001211/+attachment/3152107/+files/Preference%20Settings.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1001211
Title:
No preference setting is available to open messages in an existing tab
Status in
** Summary changed:
- No preference setting is available to open messages in an existing tab
+ No preference setting is available in thunderbird to open messages in an
existing tab
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have tried a few times today to reproduce this without success. I'll
keep trying and would add the trace once i hit the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1065113
Public bug reported:
Precise alternate preseeded installations fail with unmet deps due to
the following:
Jul 31 08:54:29 in-target: The following information may help to resolve the
situation:
Jul 31 08:54:29 in-target:
Jul 31 08:54:29 in-target: The following packages have unmet
This (or a similar issue to bug 1321627) was impacting the wifi network
setup on mako devices for smoke test with image 123. When I tried the
workaround suggested in
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627/comments/17,
the wifi became active and useable
--
You received
@gunnarhj: Yes, The calendar that I refer in this bug report is the one
that shows up when I click the time indicator at the top right corner of
the screen. Please see attachment 7 (Screen_1). Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is
locale returns the following
ubuntu@ubuntu-Inspiron-N4010:~$ locale
LANG=fr_FR.UTF-8
LANGUAGE=
LC_CTYPE=fr_FR.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_COLLATE=fr_FR.UTF-8
LC_MONETARY=en_GB.UTF-8
LC_MESSAGES=fr_FR.UTF-8
LC_PAPER=en_GB.UTF-8
LC_NAME=en_GB.UTF-8
LC_ADDRESS=en_GB.UTF-8
I can confirm again that the ppa does not fix the issue that I reported.
i.e. even after installing the ppa and rebooting, the calendar entries
were still in English.
Here follows the package installed
ubuntu@ubuntu-Inspiron-N4010:~$ dpkg -l | grep indicator-datetime
ii indicator-datetime
Public bug reported:
Description later
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evince 3.8.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Jul 18 11:09:08 2013
** Description changed:
- Description later
+ This crash occurs when running the autopilot tests using utah.
+ Attempting to find an easy way to reproduce. The information will be
+ added later.
+
+
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evince 3.8.2-0ubuntu4
** Description changed:
- This crash occurs when running the autopilot tests using utah.
- Attempting to find an easy way to reproduce. The information will be
- added later.
+ This crash occurs when running the autopilot tests using an ssh
+ connection.
+
+
Public bug reported:
The precise alternate installations of i386 and amd64 have the
following installation error reported. Probably a known issue since
report.html lists this package as uninstallable. Bug is required to
account the smoke test failure.
Install error:
** Description changed:
The precise alternate installations of i386 and amd64 have the
- following installation error reported. Probably a known issue since
- report.html lists this package as uninstallable. Bug is required to
- account the smoke test failure.
+ following installation error
Public bug reported:
This crash occurred soon after an oem installation of saucy desktop i386
image of 20131016.
Steps:
1. Perform and oem installation
2. Reboot after the installation.
3. This crash was reported soon after the reboot.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package:
This is the reason for maguro failures as well..
https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-maguro-smoke-gallery-app-autopilot/16/artifact/clientlogs/top_after.log/*view*/
--
You received this bug notification because you are a member of Desktop
Packages,
The issue does not occur with friends-0.2.0+13.10.20130926-0ubuntu1:
https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-maguro-smoke-friends-app-autopilot/14/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Marking this fix-released since the crash has not been reproduced after
the fix in glib. Please re-open it if it's needed.
** Changed in: network-manager (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is
This is occurring on both i386 and amd64 VM's. The description has been
updated to this effect.
** Description changed:
- This is noticed during health-check's tests on trusty (mostly i386)
- ISO's.
+ This is noticed during health-check's tests on trusty (mostly i386 but
+ also on amd64) ISO's.
Public bug reported:
This is noticed during health-check's tests on trusty (mostly i386)
ISO's.
The failed builds in
https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job
/trusty-desktop-i386-smoke-health-check/ are all due to this issue.
The following is excerpts from cking's
91 matches
Mail list logo
