** Changed in: ubuntu-docs (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: yelp-xsl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066526
*** This bug is a duplicate of bug 626382 ***
https://bugs.launchpad.net/bugs/626382
** Branch unlinked: lp:help.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687450
Title:
Replace
*** This bug is a duplicate of bug 97507 ***
https://bugs.launchpad.net/bugs/97507
** Branch unlinked: lp:help.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/100049
Title:
[apport]
Thanks for your bug report, however this is not a bug with Ubuntu docs
and therefore will be set to "invalid". Please figure out which package
it should be reported against, change "Affects" to that package, then
set "Status" back to "New".
** Changed in: ubuntu-docs (Ubuntu)
Status: New
Additional information:
After a fresh boot with the bad kernel, turbostat shows: Pkg%pc6 =
97.84%; PkgWatt 4.01; CorWatt 0.28; GFXWatt 0.23.
Then after the first suspend resume, turbostat shows: Pkg%pc6 = 0.00%;
PkgWatt 10.08; CorWatt 3.04; GFXWatt 3.51.
PkgTmp goes up by more than 10 degrees.
Created attachment 118874
an edited version of the file the previous attachment asked for
I edited just to remove many lines of 0's.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504584
Title:
As
(In reply to Jani Nikula from comment #6)
> Did you double check the bisect by running both dc4be6071a24 and
> dc4be6071a24^ ?
Yes, of course, and I said so in my initial e-mail.
Truth be known, this was my second bisection, as I must have made a mistake in
my first attempt, because the double
(In reply to Jani Nikula from comment #8)
> First, run dc4be6071a24 and try suspend/resume
> several times, and see if it's 100% reproducible or not.
Yes, it happens every time. To say 100%, I would have to have a sample
space of about 1000 attempts. I did not do that many.
--
You received this
Created attachment 118873
requested dmesg with drm.debug=14
Possibly relevant excerpt:
[ 399.518389] [drm] stuck on render ring
[ 399.518686] [drm] GPU HANG: ecode 6:0:0xfeff, reason: Ring hung, action:
reset
[ 399.518686] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
For your Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz processor, what is the
normal minimum pstate? I ask because I have only seen on battery power
resume from suspend issues that are related to Clock Modulation becoming
enabled. i.e. I am wondering if 800MHz is a normal minimum frequency or
below the
** Bug watch added: freedesktop.org Bugzilla #92414
https://bugs.freedesktop.org/show_bug.cgi?id=92414
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=92414
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
You don't need the logs. I already figured out the root issue, and already
submitted it upstream.
apport-collect has never worked for me. setting to "Triaged'
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of
Public bug reported:
Note: this bug report is just for local tracking of an upstream issue:
Reference:
http://lists.freedesktop.org/archives/intel-gfx/2015-October/077592.html
also copied below:
This started somewhere between Kernel 4.2 and 4.3-rc1,
but I only noticed it a day ago.
The first
Mokie, Thanks for your bug report. However, this is not an ubuntu-docs
issue, and so will be set to invalid for ubuntu-docs. You should figure
out what project / package it should be set to, and also add a lot more
information, like: Version of Ubuntu; did you re-boot and try again;
hardware
@sanket: My current understanding is that this is not a valid bug, so I am
removing you as the assignee.
@Brendan: I saw some other activity from you yesterday, so conclude you have
had time to reply to this. I'm setting this to invalid, which can be changed
back if required.
** Changed in:
I don't know what is going on with this one or what is expected or
where. setting to invalid to get it off the list of stuff.
** Changed in: serverguide
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, and thanks for your bug report.
Yes, that is correct. There are two paths to navigate to this same endpoint and
therefore two links back trails are shown.
Eventually, I'll set this bug report to "invalid".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, I am having trouble understanding what you saying is wrong. I have
added an arrow and some notes to your screen shot and re-attach herein.
If you are not talking about the link back trails, then what are you
talking about? If you are talking about the link back trail, then they
are correct,
Isn't there another issue within this bug report? Why doesn't the acpi-
cpufreq frequency scaling driver support the higher available clock
frequencies?
Actually, maybe it does. Observe processor 3 from the cpuinfo listing:
processor : 3
...
cpu MHz : 2901.000
It is in turbo mode.
To the best of my knowledge, this specific (resume from suspend,
intel_pstate, performance mode) issue has been fixed in the upstream
kernel. However, I never understood this issue to be specific to battery
mode, an interesting twist.
Note that there are other issues, and sometimes it is hard to
Given that there have now been 3 installation failures today, I'll set
this back to critical and to not fixed.
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: ubiquity (Ubuntu)
Importance: Medium => Critical
--
You received this bug notification
On 2015.09.21 06:00 Will Cooke wrote:
> I'm afraid that the new default wallpaper didn't arrive in time for UI freeze,
> and so I would like to request a UI freeze exception for the uploading of the
> new wallpaper.
It is always extremely late that any new wallpaper shows up,
and we always end
I am getting this error while trying to install Ubuntu desktop using the
64 bit daily of 2015.09.21.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462688
Title:
ubi-timezone failed exit code 1
@Phillip: I would like to get to the root of your issue, but I don't
know that this is the place to do it.
What is your processor? Mine is: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
What kernel version do you run? I am running 4.3RC1 with a modified
intel_pstate driver.
If I start a CPU burning
@Phillip: By the way, for the previous tests, I didn't go back to a
stock kernel because I knew it wouldn't make any difference. However,
you would be correct to challenge that assertion, so I re-did everything
with my stock kernel:
Linux s15 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9
@Phillip: Tell us more about what you trying to do and how you are doing
it.
I assert that the "control knobs" work fine, however, I only use primitives to
control it and never any higher level tool.
For example, I would limit the maximum CPU frequency to 0.75 of maximum with:
echo "75" | sudo
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed
, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:
grep MHz /proc/cpuinfo
to observe CPU frequencies.
The commit that, I think, fixes this issue is:
commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies
, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:
grep MHz /proc/cpuinfo
to observe CPU frequencies.
The commit that, I think, fixes this issue is:
commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies
@Colin:
I am not sure who you are asking to see if these help. For my part of it, I
pretty much only use the most recent RC kernel (well I am still on 4.2RC6), and
pretty much only with a version if the intel_pstate driver that includes a
proposed patch set that I submitted on 2015.04.11, but
Jay: Please also review bug 1225442, which covers the suggestion. The
bug report was set to Won't Fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288593
Title:
Please include SHA256 or SHA512
Requested information. Fresh server installation from Wily daily a
couple of days ago:
doug@serv64-dev:~$ sudo sudo -V | head -1
Sudo version 1.8.12
doug@serv64-dev:~$ sudo sudo -V | grep -e ve: -e HOME
Environment variables to remove:
PYTHONHOME
Environment variables to preserve:
Steve: Via past comments and e-mails with Colin Watson, we (the docs
group) are aware of your position on this. Sorry for the noise on this.
It was raised again via an askubuntu.com question. It wasn't my intent
to have the CD images group added to his bug.
--
You received this bug notification
The kernel configuration is O.K. with respect to this issue as of kernel
4.1, and dmidecode works. Thanks.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Chad wrote:
Xavier wrote that this needs to be moved somewhere else.
Does anyone know how to do that?
If someone can explain to me what needs to happen,
I changed the trusty target from 14.04.2 (which is in the past) to
14.04.3 (which is in the future, albeit, not far off)
** Changed in:
Chad wrote:
Xavier wrote that this needs to be moved somewhere else.
Does anyone know how to do that?
If someone can explain to me what needs to happen,
I changed the trusty target from 14.04.2 (which is in the past) to
14.04.3 (which is in the future, albeit, not far off)
** Changed in:
** Description changed:
There is a relatively new kernel configuration parameter, CONFIG_DEVMEM.
- I do not understand why, but for some reason is not set for Ubuntu, and
therefore dmidecode does not work.
+ I do not understand why, but for some reason is not set for Ubuntu, and
therefore
Public bug reported:
There is a relatively new kernel configuration parameter, CONFIG_DEVMEM.
I do not understand why, but for some reason is not set for Ubuntu, and
therefore dmidecode does not work.
I think that, in general, we want dmidecode to work.
I found this:
You do not need the apport stuff for this bug report, it is not
relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462822
Title:
see also: https://bugzilla.kernel.org/show_bug.cgi?id=90421
particularly the entries from Marien.
This issue does not manifest the same for all i7 processors.
** Bug watch added: Linux Kernel Bug Tracker #90421
http://bugzilla.kernel.org/show_bug.cgi?id=90421
--
You received this bug
Hi David,
Perhaps add that very note to the page itself.
Also, please remember to delete all of the 10.04 information on Friday
(or thereabout) , as 10.04 server goes EOL on Thursday ( a bunch of
10.04 information on the page is already way way past EOL)
--
You received this bug notification
Public bug reported:
Just to separate the variables, use a different Turn screen off when
inactive for time and Lock screen after time under Brightness and
Lock under System Setting.
Leave the system inactive.
The screen goes blank after the appropriate inactive period.
After the additional
On 2015.04.01 02:04 Dimitri John Ledkov [x...@ubuntu.com] wrote:
On 1 April 2015 at 07:34, Ted Cox ted.m@gmail.com wrote:
Hi. New volunteer here.
I made some edits to the introduction.xml document.
I tried to push those edits to my Launchpad account:
bzr push
The mascot creature image, created by Canonical, is only ready very
late in the cycle. It'll be changed when available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434087
Title:
Yelp in Vivid
It turns out that the mascot creature icon is ready, and we got it.
** Changed in: ubuntu-docs (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: ubuntu-docs (Ubuntu)
Assignee: (unassigned) = Doug Smythies (dsmythies)
** Branch linked: lp:ubuntu-docs
--
You received
On 2015.03.14 10:58 Marcin GTriderXC.tk wrote:
Honestly we've got something over 9000 strings to translate in Polish.
Translating this is gonna take me definitely longer than week or two.
I just want to make sure that if I/we translate these strings,
my work will not go in vain and
, Mar 6, 2015 at 1:35 AM, Doug Smythies dsmyth...@telus.net wrote:
On 2015.02.26 16:45 Doug wrote:
Hi all,
Recall that the Serverguide does only LTS releases now.
The Ubuntu Serverguide versions 12.04 and 14.04 are going to do point
release updates.
The string freeze has just been declared
On 2015.02.26 16:45 Doug wrote:
Hi all,
Recall that the Serverguide does only LTS releases now.
The Ubuntu Serverguide versions 12.04 and 14.04 are going to do point release
updates.
The string freeze has just been declared, and the .POT files have been
updated, ready for translation.
O.K. either you stop this or your account will be deleted and you will
be blocked.
You have been asked for more information, several times, from some kind
people willing to help you for your question versions of your same
issue. Go there and supply the information.
This bug report will be set to
Go to this link:
https://answers.launchpad.net/ubuntu/+source/ubuntu-
docs/+question/262575
And only ever go to that link until your issue is resolved.
Do not file new bug reports and do not continue to pester us.
We can not fix your computer. You will have to fix it yourself, with
help form
Hi all,
Recall that the Serverguide does only LTS releases now.
The Ubuntu Serverguide versions 12.04 and 14.04 are going to do point release
updates.
The string freeze has just been declared, and the .POT files have been updated,
ready for translation.
Based on the Italian, which had 0
I do not understand. The status was set to Fix Released, so I assumed
it was done. The documents say it would be set to Fix Committed if it
was at this step: The uploaded backport will then require manual
acceptance by a member of the Ubuntu Archive Administrators team, so
there may be a short
@Gunnar: I do not know what you mean by Software Updates, but I
suspect that is some desktop thing. I run servers. And the backport
lines are present in the /etc/apt/sources.list file. Yes, I did sudo
apt-get update before sudo apt-get dist-upgrade.
I use the Canadian site (I think), so maybe it
Felix: Thanks, yes that works.
But, Oh!! That means the objective of simply having the correct version
yelp-tools and yelp-xsl if one just has an up-to-date 14.04 system has
not been met.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed
** Changed in: ubuntu-docs (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424319
Title:
when am i going to hear from ,see some action or answer get my files
Thank you very much!!
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1411093
Title:
Please backport yelp-tools 3.12.1-1 (main) from utopic
I have no idea what you are talking about. Regardless your issue is not
an Ubuntu Docs issue, which is the reason I set this bug report to
invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I changed this from won't fix and set the importance to high. Why
because it has to be fixed and should actually be critical.
** Changed in: sysvinit (Ubuntu Trusty)
Status: Won't Fix = Confirmed
** Changed in: sysvinit (Ubuntu Trusty)
Importance: Undecided = High
--
You received
I fixed the base index.html pages some time ago. However the
installation guide contents have never been fully updated to the new
theme. There is an open bug report about that somewhere
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why are you not going to do this for Trusty? Many of us (well, O.K. me)
have been forcing the use of the intel_pstate driver in 14.04 and
14.04.1. Now it is my understanding that the intel_pstate driver will be
enabled by default in 14.04.2.
--
You received this bug notification because you are
There has been some regression with this file, because the above
mentioned change was originally done a long time ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411802
Title:
powersave
*** This bug is a duplicate of bug 1411802 ***
https://bugs.launchpad.net/bugs/1411802
** This bug has been marked a duplicate of bug 1411802
powersave governor should be listed as one possible value for the ondemand
init.d script
--
You received this bug notification because you are a
For my post above please note that there is not a regression, as I did
the edit to /etc/init.d/ondemand myself a long time ago, and then forgot
that I had done so.
Since your are changing back from the intel_pstate driver being disabled
by default to enabled by default, this change needs to be
*** This bug is a duplicate of bug 1314653 ***
https://bugs.launchpad.net/bugs/1314653
** This bug has been marked a duplicate of bug 1314653
sysvinit: default cpufreq governor to powersave for intel-pstate driver
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1314653 ***
https://bugs.launchpad.net/bugs/1314653
** This bug is no longer a duplicate of bug 1411802
powersave governor should be listed as one possible value for the ondemand
init.d script
** This bug has been marked a duplicate of bug 1314653
Oh.
I'll fix it.
** Changed in: ubuntu-docs (Ubuntu)
Status: New = In Progress
** Changed in: ubuntu-docs (Ubuntu)
Assignee: (unassigned) = Doug Smythies (dsmythies)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Package changed: ubuntu-docs (Ubuntu) = ubuntu-docs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415896
Title:
Link to cloud documentation incorrectly states US English
To manage
I reviewed the Ubuntu kernel team e-mail thread.
I do not understand why the bug patch submitted upstream on November 6th seems
to have stalled.
I did observe that there wasn't an ACK, that I could find.
So I wondered of the patch had been modified or another solution was found.
Is there any way
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Changed in: trusty-backports
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1411094
Title:
Please
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
Gunnar,
Thanks so much. Your build method works for me also, but only on a fresh
apt-get source yelp.
I'll continue using your method.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions:
** Description changed:
Please backport yelp-xsl 3.12.0-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
Public bug reported:
Under vivid, the serverguide validation script gives and error:
doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh
serverguide/C/serverguide.xml
--Validating serverguide/C/serverguide.xml ...
serverguide/C/serverguide.xml:2: element legalnotice: validity error :
** Description changed:
Please backport yelp-xsl 3.12.0-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
Somewhere I read that I could do this:
apt-get install source yelp
and then do this:
dpkg-buildpackage
So I tried it. Important note: I didn't change yelp-xsl or yelp-tools
yet, they are the standard trusty versions, as I am just trying to
establish that things work properly BEFORE backporting
It works fine for me also. Machine = up to date 14.10 VM guest on a
14.04 server host
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360756
Title:
The URI ‘help:ubuntu-help/index’ does not point to
Apparently it is up to me to do the testing such that each check box is
dealt with.
There isn't a package called libgda5, so what to do for that line
seems unclear. There are many packages listed if the search term is
shortened to libgda, but even then it remains unclear what is the
correct one.
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc Team, had been working on issues with the official
** Description changed:
+ Please backport yelp-xsl 3.12.0-1 from 14.10 to 14.04
+
+ Reason for the backport:
+
+
For many many months prior to the initial release of 14.04 (Trusty) we,
the Ubuntu Doc Team, had been working on issues with the official
documentation
** Description changed:
+ Please backport yelp-tools 3.12.1-1 from 14.10 to 14.04
+
+ Reason for the backport:
+
+
For many many months prior to the initial release of 14.04 (Trusty) we,
the Ubuntu Doc Team, had been working on issues with the official
I made an Ubuntu Desktop virtual machine and submitted new backport requests
using it.
I will close these ones shortly. Sorry for the mess.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions:
Public bug reported:
Please backport yelp-xsl 3.12.0-1 (main) from utopic to trusty.
Reason for the backport:
I'll cut and pste this from my earlier attempt later. I can not do it herein.
Testing:
Mark off items in the checklist [X] as you test them, but please
** Description changed:
Please backport yelp-xsl 3.12.0-1 (main) from utopic to trusty.
Reason for the backport:
- I'll cut and pste this from my earlier attempt later. I can not do it herein.
+ For many many months prior to the initial release of 14.04 (Trusty)
** Changed in: trusty-backports
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1409962
Title:
Please backport
I'm pretty sure this is not correct. Nor can I figure out how to run
requestbackport from a server with no GUI. It just ends up with
jibberish on the screen, similar to when trying to run apport stuff on a
server. Nor can I figure out how to get requestbackport to just put the
information into a
** Description changed:
Please backport yelp-tools 3.12.1-1 (main) from utopic to trusty.
Reason for the backport:
- I'll cut and paste this from my earlier attempt later
+ For many many months prior to the initial release of 14.04 (Trusty) we, the
Ubuntu Doc
** Changed in: trusty-backports
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1409961
Title:
Please backport
Public bug reported:
For many many months prior to the initial release of 14.04 (Trusty) we,
the Ubuntu Doc Team, had been working on issues with the official
documentation and the related higher level tools. Some solutions and
workarounds had been able to be implemented in the documentation,
Public bug reported:
For many many months prior to the initial release of 14.04 (Trusty) we,
the Ubuntu Doc Team, had been working on issues with the official
documentation and the related higher level tools. Some solutions and
workarounds had been able to be implemented in the documentation,
Thanks for your rapid attention on this one.
Just for completeness, I want to expand on this statement from the description:
my system does seem to benefit from blk-mq
That is, unless the IO load is high. With very high disk IO load, things fall
apart. For example I had a single disk seek time
Public bug reported:
In kernel 3.18RC1 this kernel config parameter is: # CONFIG_SCSI_MQ_DEFAULT is
not set
In kernel 3.18RC2 and beyond, the kernel config parameter is:
CONFIG_SCSI_MQ_DEFAULT=y
This results in loss of the ability to set the IO scheduler via
/sys/block/sda/queue/scheduler.
@Coeur: I entered this bug report over 11 months ago, and have simply
ignored the error ever since. I haven't had any problems.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186
I am setting the status of this one to invalid.
It turns out that this never was a problem with the installation-guide
project/package but rather a problem with some long lost process for
converting the installation guide to some themed content for inclusion
in help.ubuntu.com. It is that process
Setting this one to a status of invalid. We have changed our plans and
will continue to post the installation-guide, albeit with no theme, at
least for now.
** Changed in: installation-guide (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
401 - 500 of 977 matches
Mail list logo
