Patch merged into fwts and sent to the mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050475
Title:
fwts: segfaults on --disassemble-aml with some ACPI tables.
To manage notifications
Also getting this on the OEM "System Configuration display", see
attached photo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032178
Title:
ubiquity: scroll bars on installer display even though t
Apologies, forgot to attach the photo.
** Attachment added: "Photo of the issue"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1032178/+attachment/3312652/+files/lp-1032178.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
This is a regression on 12.10 beta1 + daily updates. Tested on a
Lenovo X220i and a Dell Inspiron 6400.
In the "Brightness and Lock" settings, I un-tick the "Dim screen to save
power" option and set the "Turn screen off when inactive for: " to
"Never" to turn off screen di
I've given this a good soak testing on Quantal, Precise + applied the
patches to Oneiric and for each tested it against ext2, ext3, ext4, xfs
and btrfs lower file systems, and it does solve this bug. Thanks Tyler.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Changed in: fwts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050475
Title:
fwts: segfaults on --disassemble-aml with some ACPI tables.
To
I've given this a good soak testing on Quantal, Precise + applied the
patches to Oneiric and for each tested it against ext2, ext3, ext4, xfs
and btrfs lower file systems, and it does solve this bug. Thanks Tyler.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
SRU for Oneiric and Precise, and apply to Quantal too.
== SRU Justification ==
== Impact ==
A regression was caused by commit:
821f749 eCryptfs: Revert to a writethrough cache model
That patch reverted some code (specifically, 32001d6f) that was
necessary to properly handle open() -> mmap() ->
SRU for Oneiric and Precise, and apply to Quantal too.
== SRU Justification ==
== Impact ==
This bug is the result of existing eCryptfs inodes not
being evicted when they are the target of a rename()
syscall. The existing inodes are left around, meaning
that the lower inodes are also left around
Marking it invalid against linux since it wasn't a kernel bug - it was a
bug in my eCryptfs test script for btrfs specific tests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Changed in: linux (Ubuntu Lucid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926292
Title:
automake distdir.test fails because of an EPERM error
To
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947270
Title:
eCryptfs: Make truncate path killable
To manage notifications
evaluating the method.
..but for some reason it seems to happen non-deterministically.
Probably a race somewhere. Needs fixing.
** Affects: fwts (Ubuntu)
Importance: Medium
Assignee: Colin King (colin-king)
Status: In Progress
** Changed in: fwts (Ubuntu)
Status: New =>
Fix committed:
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=7ec7c2589e53b91d5bda68f806ca15dab6ad9995
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=002ea32da4b03ce9b5683765311ba033bb9803af
This fix will be released soon in fwts V0.25.04
** Changed in: fwts (Ubuntu)
Statu
Please can run apport-collect on this bug? Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017841
Title:
[Thinkpad Edge 15] register is already in use for vector 0xf9 on
another cpu
To man
Is this a regression or something we missed when it was enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017841
Title:
[Thinkpad Edge 15] register is already in use for vector 0xf9 on
anoth
Incidentally, why has this machine got init_call debug enabled on boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017841
Title:
[Thinkpad Edge 15] register is already in use for vector 0xf9 on
@Brendand, comment #6 you said this is the first time you are running
this test? Are you referring to the s3 test or s3 with the --s3-device-
check option?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
So, the meta question is as follows: Now that one is using fwts to do
s3 testing we are actually being more rigorous and finding more issues.
These may not be s3 failures per se, but they are issues found when
doing S3 testing.
--
You received this bug notification because you are a member of Ub
** Changed in: fwts
Status: Fix Committed => Fix Released
** Changed in: fwts
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971886
Title:
QA: warning: dere
differences in device
as one can see, the Dell WMI hotkeys and AT Translated Set 2 keyboard are
swapped causing the check to fail. We should probably sort these and the
compare the sorted order.
** Affects: fwts (Ubuntu)
Importance: Medium
Assignee: Colin King (colin-king
We also need to filter out the pactl Latency information as this is a new field
that we don't want to compare because it is always
changing.
** Changed in: fwts (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
..and also because Notify() calls are being spawned off and we're not
waiting for these pthreads to complete before we do the lock accounting.
Patches to address this are pending on the mailing list too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I've updated the dmi decode test with some improved advice information
to help explain these kind of errors,
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=fe3ba4850c78281bf5f720b5d361e6506f69f17b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Fixed with commit:
http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=db44f7ee5f01827ce8275ecde9c4e3d5123e5660
** Changed in: fwts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: fwts
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021674
Title:
DMIInvalidHardwareEntry - Unmatched Chassis Type
To manage notification
** Changed in: fwts (Ubuntu)
Status: New => In Progress
** Changed in: fwts (Ubuntu)
Importance: Undecided => Medium
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
You received this bug notification because you are a member of Ub
Bug caused in regex scanning. I have a fixed version available for
testing on your i386 machine:
http://kernel.ubuntu.com/~cking/lp-1028031/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028031
Titl
Patch sent to fwts-devel, fix should land in version 0.25.06
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028031
Title:
fwts crashed with SIGSEGV in fwts_klog_scan()
To manage notifications about
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
You received this bug notification because you are a member of Ub
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
You received this bug notification because you are a member of Ub
So, the inode-race-stat.sh test will fail on Lucid and Natty as
backporting commit 3b06b3ebf44170c90c893c6c80916db6e922b9f2 was deemed
too intrusive to backport and had a high risk in causing further
regressions.
We can either put it back on my list of patches to backport and
thoroughly test, or d
As for the directory-concurrent test failing, it may be due to the host
machine having too many CPUs. How many processors does the test host
machine have?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
The inode-race-stat.sh test will fail on Lucid and Natty as backporting
commit 3b06b3ebf44170c90c893c6c80916db6e922b9f2 was deemed too intrusive
to backport and had a high risk in causing further regressions.
We can either put it back on my list of patches to backport and
thoroughly test, or drop
The inode-race-stat.sh test will fail on Lucid and Natty as backporting
commit 3b06b3ebf44170c90c893c6c80916db6e922b9f2 was deemed too intrusive
to backport and had a high risk in causing further regressions.
We can either put it back on my list of patches to backport and
thoroughly test, or drop
Fix landed as commit, a1dc6acab1c09788d997baa58660e7f51851a3e0. will be
released in V0.25.05
** Changed in: fwts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Released in https://launchpad.net/~firmware-testing-team/+archive/ppa-
fwts-devel
** Changed in: fwts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Bug occurs because of non-serialized control methods incrementing and
decrementing the semaphore counts and not being protected by a mutex.
Patch sent to the mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
We encountered this error when running certification tests in a HP Proliant
ML110 G5:
FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x09
while accessing entry
'Base Board Information (Type 2)' @ 0x000dc082, field 'Asset Tag', offset 0x08
So, basically this means that
A newer 2010.10.25 BIOS is available:
http://h2.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3577708&swItem
=MTX-
8a03a95409d541848a5622a22d&prodNameId=3577715&swEnvOID=4006&swLang=8&taskId=135&mode=4&idx=2
However, the bug isn't exact
Public bug reported:
Testing today's daily ISO image http://cdimage.ubuntu.com/daily-
live/20120704/quantal-desktop-amd64.iso on a Dell Inspiron 6400, failed
to install - got a ubiquity install error message.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.8
ProcVersionSignatu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021230
Title:
installation failed on daily iso AMD 64 desktop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u
Public bug reported:
Booting on today's ISO test I got a kernel panic,
How to reproduce:
ISO image: http://cdimage.ubuntu.com/daily-live/20120704/quantal-
desktop-amd64.iso
On ISO boot menu, select language and then hit F4 (modes) and selected
"OEM install (for manufacturers)" and then "Instal
** Attachment added: "panic.jpg"
https://bugs.launchpad.net/bugs/1021284/+attachment/3214002/+files/panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021284
Title:
panic on __queue_work+0x
Public bug reported:
Tried out today's ISO image: http://cdimage.ubuntu.com/daily-
live/20120705/quantal-desktop-amd64.iso and I can't install because
ubiquity fails.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.8
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Una
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021330
Title:
ubiquity aborts with an error on daily ISO (20120705 quantal-desktop-
amd64.iso)
To manage notifications about this bug go to:
https://
fwts is flagging up a DMI table field that is not strictly conforming to
the DMI specification,
http://dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf
Section 7.21, page 93, offsect 10h, "Partition Row Postion" states:
"Identifies the position of the referenced Memory Device i
Assignee: Colin King (colin-king)
Status: In Progress
** Changed in: fwts (Ubuntu)
Status: New => In Progress
** Changed in: fwts (Ubuntu)
Importance: Undecided => Low
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
You received
I'm pretty sure this is just a bug in the eCryptfs tests that don't
cater for meta data space used on btrfs and so we get caught out. I will
see if I can fix the test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
Following the instructions as per "Install (OEM setup) in Ubuntu Desktop
amd64 for Quantal Alpha 1" ISO testing
http://testcases.qa.ubuntu.com/Install/DesktopOem test-case: "Case ID:
uoi-003", I got screen corruption on an HP Mini-210 - see attached
photo
This disappeared wh
** Attachment added: "Photo of artifacts on the display"
https://bugs.launchpad.net/bugs/1010001/+attachment/3179195/+files/DSCF2136.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010001
Title
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+bug/1010001/+attachment/3179201/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010001
Title:
Corruption on ba
** Attachment added: "lspci-vvnn.txt"
https://bugs.launchpad.net/ubuntu/+bug/1010001/+attachment/3179200/+files/lspci-vvnn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010001
Title:
Corrup
Just to clarify, this is not a btrfs or eCryptfs bug at all, but just a
test failure because the tests could not correctly estimate the maximum
file size on the lower btrfs mount, causing the tests to fail when the
unexpectedly run out of space.
Fix: lp:~colin-king/ecryptfs/lp-1007159
--
You
Since the posting was on a private list, I'm putting a link into the
results and spreadsheet data that covers the analysis:
Results:
http://zinc.canonical.com/~cking/power-benchmarking/pm-utils-results/results.txt
Data:
http://zinc.canonical.com/~cking/power-benchmarking/pm-utils-results/pm-test
Public bug reported:
function set_sata_alpm prints "Setting SATA APLM on %s to %s...", in fact this
should be "Setting SATA ALPM on %s to %s...".
(APLM --> ALPM).
set_sata_alpm() {
# see kernel commit 6013efd8860bf15c1f86f365332642cfe557152f
kv="$(uname -r)"
[ "$kv" ] || exit $NA #f
** Changed in: pm-utils (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Changed in: pm-utils (Ubuntu)
Milestone: None => precise-alpha-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hi Steve, I will re-rerun journal-commit on an idle system tomorrow and
get back to you. Any ideas of scenarios that are typical and may
generate typical I/O patterns?
As for the 600 second setting, it is a little scary to see it set so
high and cause potential data loss risk. But, that's kinda
Steve, agreed, it's a minor overhead - I just wanted to ensure that the
HAL left over cruft was being flagged up as redundant and causing some
extra overhead. Just wanted to save a bunch more fork/exec calls (e.g.
on boot and AC/battery actions) and a few more bytes of space on the
disk. I jus
Steve, I've re-instrumented the journal-commit tests this time using the
following test methodology:
Start banshee playing some classical music (mp3)
Sleep 60 seconds
Start firefox, open tab on a blog containing flash adverts
Sleep 60 seconds
Open 2nd tab on firefox on a blog with lots of images,
Sorry, forgot the spreadsheet data
** Attachment added: "pm-utils-journal-commit-apps-test.ods"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/900923/+attachment/2623324/+files/pm-utils-journal-commit-apps-test.ods
--
You received this bug notification because you are a member of Ub
@Steve, also attached are the results from pm-utils readahead tests run
with the same testing scenarios as in #5
I suspect that readahead is marginally beneficial for systems with
spinning media (within the margins of measurement error), and with SSDs
(like my HP mini 10) it is definitely less pow
** Changed in: fwts (Ubuntu)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853875
Title:
fwts: battery test should sanity check _BTP via
/proc/acpi/battery/*/alarm
** Summary changed:
- fwts: ASPM PCI-express incorrect BIOS seeting detection
+ fwts: ASPM PCI-express incorrect BIOS setting detection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872325
Title:
f
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906987
Title:
syndaemon polls 5 times a second even though it is
strace shows:
open("/var/lib/NetworkManager/timestamps", O_RDONLY) = 20
fstat(20, {st_mode=S_IFREG|0644, st_size=1646, ...}) = 0
read(20, "\n[timestamps]\n3c32aa58-a2ed-44e7"..., 4096) = 1646
read(20, "", 4096) = 0
close(20) = 0
open("/var/lib/Net
Public bug reported:
Network Manager is periocially creating dirty pages that are being
written back to disk and causing uncessary drive wakeups.
Using SystemTap I was able to observe the following dirty pages being
created on the following files
0 7951 NetworkManager sd
The culprit is periodic_update_active_connection_timestamps() which is
being called every 300 seconds because of:
/* Update timestamps in active connections */
priv->timestamp_update_id = g_timeout_add_seconds (300, (GSourceFunc)
periodic_update_active_connection_timestamps, manag
** Tags added: battery-power-consumption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913856
Title:
NetworkManager periodically writes to the disk causing wakeups
To manage notifications about thi
So, I only see a single timestamps file too, the timestamps.096F6V
filename is probably a short lived temp filename. As for the
configuration, it was a clean install and connected via wireless (and
possibly ethernet).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 818830 ***
https://bugs.launchpad.net/bugs/818830
Unfortunately the i915 RC6 patch was dropped with commit
371de6e4e0042adf4f9b54c414154f57414ddd37 because the RC6 fix still seems
to make some systems freeze and as yet we've not got a reliable list of
hardwar
Well, if ethtool isn't going to consume lots of space then I'm happy for
it to be seeded too.The moot point is that it doesn't appear to save
much power (the measurements were close to the noise levels of the
readings). So, it's one of those cases that either we seed it and it
works as expecte
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/446657
Title:
Bluetooth's on/off status doe
** Changed in: pm-utils (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Martin
Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900930
Title:
pm-utils: typo
Public bug reported:
avahi-daemon on a network with many clients is doing poll() with a zero
timeout and timing out immediately. This looks like a busy wait to me.
poll([{fd=6, events=POLLIN}, {fd=17, events=POLLIN}, {fd=16, events=POLLIN},
{fd=15, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13
** Also affects: ubuntu-power-consumption
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915261
Title:
avahi-daemon: polling with zero timeout
To manage n
Public bug reported:
I upgraded from Oneiric to Precise and now thunderbird is consuming >50%
of my CPU all the time.
Attached is a strace of the busy process.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 10.0~b2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15+mouseh
** Attachment added: "Thunderbird strace log"
https://bugs.launchpad.net/bugs/915324/+attachment/2669534/+files/thunderbird-trace.log
** Tags added: battery-power-consumption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
@Chris, I think this may be a false bug report - after ~30 minutes of
grinding away it is now settled down. I have no idea how to re-trigger
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/91
On 12/01/12 15:11, Chris Coulson wrote:
> Is it a fairly fresh account, or new-ish profile? It could have been the
> indexing
>
This is an existing account with *thousands* of messages. Perhaps moving
to the new thunderbird from Oneiric to Precise forced a re-index.
Colin
--
You received this b
@Chris, that makes sense. Not a bug then. Thanks for looking at this
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915324
Title:
thunderbird is consuming too much CPU
To manage notificatio
Steve a few simple things to try:
1. Can this be reproduced with a previous kernel?
2. Can this be reproduced with power connected?
3. What kind of failure rate are you seeing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Yep. It's kinda invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915324
Title:
thunderbird is consuming too much CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Public bug reported:
Running Precise with all of today's updates I'm observing that the
desktopcouch-service is polling at about 9.9Hz, running strace on the
process shows:
poll([{fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=17, events=POLLIN}], 4, 101) = 0 (Timeout)
*** This bug is a duplicate of bug 571648 ***
https://bugs.launchpad.net/bugs/571648
** Also affects: ubuntuone-client
Importance: Undecided
Status: New
** Also affects: ubuntu-power-consumption
Importance: Undecided
Status: New
** Summary changed:
- ubuntuone-syncdaemon
HI Vadim, thanks for picking this up so quickly. Attached is a gzip'd
log as requested.
** Attachment added: "gzip'd indicator-weather.log"
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/917253/+attachment/2678503/+files/indicator-weather.log.gz
--
You received this bug notificati
Daniel, I'm able to measure wakeup events using a tool I wrote called
eventstat in my PPA https://launchpad.net/~colin-
king/+archive/powermanagement - alternatively use powertop.
Colin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@Daniel, incidentally, how does one set the default mouse polling
interval to 500ms?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917210
Title:
compiz+unity3d generates > 50 wakeups a second on idl
Great! Many thanks Vadim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917253
Title:
indicator-weather applet is writing debug messages frequently to disk
To manage notifications about this bug go
The fact that users aren't complaining about the line being logged
doesn't mean it's not unwanted - users just don't know about it. We do
get users complaining a lot about power consumption issues, and things
like logs periodically being updated will keep the disk from going into
an idle state.
S
@Matt, thanks for that data point. I will see if I can get any sense out
of contacts we have in Lenovo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904261
Title:
Lenovo U300s does not suspend
To
Thanks Daniel, great work! Any idea when this will land in Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917210
Title:
compiz+unity3d generates > 50 wakeups a second on idle system
To man
Most excellent! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917210
Title:
compiz+unity3d generates > 50 wakeups a second on idle system
To manage notifications about this bug go to:
https
Public bug reported:
When enabled Bluetooth can typically consume ~1 Watt of power. The
Gnome bluetooth-applet always has this enabled on login from a clean
boot.
Turning off Bluetooth temporarily disables Bluetooth during the session
and also if one logs off and logs back in again. However, it
Well, there are some different ways of approaching this. Either we
physically state the machine is meant to be a specific machine type
using a command line option or we try to infer it (e.g. has it got a
battery, then 'probably' it's a mobile platform of some sort).
Perhaps we should have a comma
** Changed in: notify-osd (Ubuntu)
Milestone: None => precise-alpha-2
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904835
Ti
Public bug reported:
notify-osd append each notify message to a log in .cache/notify-osd.log.
Looking at the code I suspect this is for debugging purposes only,
however, I don't seem to have debug turned on and it is still appending
data to the log. I have examined this under the current Oneiric
** Description changed:
notify-osd append each notify message to a log in .cache/notify-osd.log.
Looking at the code I suspect this is for debugging purposes only,
however, I don't seem to have debug turned on and it is still appending
data to the log. I have examined this under the curr
So, this basically means that the S3 test script observed that the
kernel wrote to the power management registers which then transitions
the machine into the S3 state.
The kernel doesn't do much more after this it is waiting for the machine
to suspend. So a hang like this is quite curious. If S
1501 - 1600 of 2168 matches
Mail list logo
