In 60 seconds, one can observe:
% time seconds usecs/call callserrors syscall
-- --- --- - -
44.512.252139 1052 poll
28.031.416574 366 3871 epoll_wait
24.331.23
Test scenario:
Clean install with developer mode so I can access the device via adb
shell. Device is on the lock screen, sitting idle, so essentially is
should be doing not a lot.
I ran eventstat to see which processes are generating the most wakeups:
root@ubuntu-phablet:~# eventstat 60 1
Hi Jason,
Can I close this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356952
Title:
System76: Guidance on `fwts syntaxcheck` failures
To manage notifications about this bug go to:
Just for clarification, what is /dev/sda1 mounted as?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald prevents unmounting /dev/sda1 in recovery mode
To manage notifications
I'm inclined to think that in single user and/or recovery mode, dbus is
generally not running, and thermald depends on this. So perhaps we
should only start thermald on run levels 2,3,4,5. Can you change the
/etc/init/thermal.conf file start line to be:
start on runlevel [2345] and started dbus
)
Importance: Undecided = Medium
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294895
Title:
“start
Great! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364464
Title:
unity8-dash has a thread that is polling rather rapidly on epoll wait
To manage notifications about this bug go to:
** Changed in: thermald (Ubuntu)
Status: In Progress = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294895
Title:
“start on dbus” condition may start thermald too early
To
** Changed in: thermald (Ubuntu)
Status: In Progress = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald prevents unmounting /dev/sda1 in recovery mode
To
I can't reproduce this with the latest version of fwts 14.09.00 and the
3.13.0-37 kernel. Can you re-test this for me with the latest fwts and
kernel?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: fwts
Status: Confirmed = Incomplete
--
You received
This bug has not been updated since December 2012. Marking it as won't
fix. If the issue occurs again, please re-open the bug.
** Changed in: linux (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Correction, I can see the failure now, I didn't observe the final
hwclock was timing out after 10 seconds since I was using utopic
userspace and not trusty userspace hwclock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a note:
1. The utopic version of hwclock has a 10 second timeout but does not report a
timeout error (which is misleading)
2. The trusty version reports the timeout, but prints the errno from the
previous system call, so the error message is misleading
3. When I get hwclock time-out the
Indeed, this does seem to be an upstart/init config issue rather than a
thermald issue per se. I'll add that to the affects part of the bug
report.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James
BTW, I'm going to slip the run level changes into thermald to address
another thermald bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald prevents unmounting /dev/sda1 in
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
** Changed in: fwts
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1333569
Title:
Fix sent upstream for review. https://lkml.org/lkml/2014/9/26/701
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1333569
Title:
Hibernate with fwts will cause hwclock command to time out
To manage
** Changed in: thermald (Ubuntu)
Status: Incomplete = 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/1294895
Title:
“start on dbus” condition may start thermald too early
To
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** No longer affects: fwts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1333569
Title:
Hibernate with fwts will cause hwclock
@Srinivas, I think it's probably the easiest safeguard for this kind of
case, we've not come up with a solution that's any simpler or more
elegant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@James, any idea why dbus is starting?
** Changed in: upstart (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/1348784
Title:
thermald prevents unmounting
The High temperature of temp1: +90.0°C (crit = +103.0°C) probably kicked
in passive cooling (via thermald) and this will clock down the CPU hence
it will run slower to try and reduce the temperature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from (to try to reduce flash writes and hence reduce power
consumption) and I spotted that /home/phablet/.cache/upstart/indicator-
network.log is being written to rather often (every minute or so) (tail
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from (to try to reduce flash writes and hence reduce power
consumption) and I spotted that /home/phablet/.cache/upstart/account-
polld.log is being written to periodically with a rather pointless
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from (to try to reduce flash writes and hence reduce power
consumption) and I spotted that the dbus log on my phone is being hit by
messages from process 2046:
root@ubuntu-phablet:~# ps -ef | grep 2046
Yep, still polling at the same rate doing inotify add watches:
root@ubuntu-phablet:~# strace -f -p 2078
Process 2078 attached with 4 threads
[pid 2091] restart_syscall(... resuming interrupted call ... unfinished ...
[pid 2081] restart_syscall(... resuming interrupted call ... unfinished ...
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce
power
consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the
same debug message written to every every 300
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce
power
consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the
same debug message written to every every 300
Tested on:
Linux ubuntu 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux, the perl script now does not exit
and works as expected.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug
@Daniel, these commits are present in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242812
Title:
ext4 random block I/O write performance regression with 3.11 Saucy
Kernel
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
OK, so it's starting because dbus has started, where as on my test
machines dbus is not running in recovery mode. I wonder why that is so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Can you inform me what the following shows when in recovery mode:
ls -al /proc/$(pidof thermald)/fd
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald prevents
I believe I have found a solution to this problem and I've got some
kernel packages containing the fix for you to try out at:
http://kernel.ubuntu.com/~cking/lp-1349028/
Please give these a test and let me know if it resolves the issue for
you.
** Changed in: linux (Ubuntu)
Status:
SRU Justification:
Impact:
The CONFIG_CONTEXT_TRACKING_FORCE should be disabled for
various reasons:
1. As described in the Kconfig this option brings an
overhead that you don't want in production and also
Say Y only if you're working on the development of an
architecture backend for the
Public bug reported:
I've observed that location service is waking up ~10 times per second
due to a 100ms sleep
ps -ax | grep 2295
2295 ?Ssl0:00 /usr/bin/ubuntu-location-serviced --bus system
--provider gps::Provider
eventstat shows it's the top waking userspace process on the
** Changed in: location-service (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350871
Title:
location service is waking up at 10Hz causing possible unwanted
This is blocking the QA boot tests, so I'm raising it to critical
** Changed in: bootchart (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381177
Title:
@Srinivas, any ideas
** Changed in: thermald (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366541
Title:
System hangs when thermald is running
To manage
Timothy, can you elaborate on what kind of issues you had, re: I have
had issue in the pass witht he Kernel causing system hangs when it tried
to take adavantage of certaion BIOS features (My BIOS is fully
patched).
So we can get some better idea of the hardware, can you run: apport-
collect
Can you run apport-collect 1367131 so I can get some more system
specific information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367131
Title:
thermald throttles cpu to minimal frequency at
A quick workaround is to edit /etc/thermald/thermal-conf.xml and change
line 25
Temperature55000/Temperature
..to a higher threshold. Meanwhile, I'll see what the upstream
developer thinks about this default skin temperature threshold.
--
You received this bug notification because you are a
I forgot to mention; restart thermald after changing the threshold,
using sudo restart thermald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367131
Title:
thermald throttles cpu to minimal
Ignore my comments in #3, I misunderstood the issue. Apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367131
Title:
thermald throttles cpu to minimal frequency at 45°
To manage
The /sys/class/hwmon/hwmon0 Digital Temperature Sensor data appears to
be from the asus_atk0110 driver which in turn is getting the data from
ACPI controls, so this limit seems to be hard-coded into your machine's
firmware. As it stands, for a AMD Phenom(tm) II X4 955 Processor the
125W version
Can you run sensors and paste the entire output into the bug report.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367131
Title:
thermald throttles cpu to minimal frequency at 45°
To
@Srinivas,
it seems thermad is triggering on the motherboard (MB) temperature,
rather than the CPU temperature. Is there a way to address this in
thermald?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've built a new version of thermald containing the fixes from Srinivas
for testing:
http://kernel.ubuntu.com/~cking/lp-1367131/
Install the appropriate package, it will restart the new thermald. Let
us know if this helps.
--
You received this bug notification because you are a member of
I've built a new version of thermald containing the fixes from Srinivas
for testing:
http://kernel.ubuntu.com/~cking/lp-1367131/
Install the appropriate package, it will restart the new thermald. Let
us know if this helps.
--
You received this bug notification because you are a member of
This bug was fixed in the package thermald - 1.3-4
---
thermald (1.3-4) unstable; urgency=medium
* Fix assumption about hwmon0 (LP: #1366541)
* Use correct nfds to not rely on memset 0 to pollfds
-- Colin King colin.k...@canonical.com Tue, 9 Sep 2014 16:32:00
--
You
** Changed in: thermald (Ubuntu)
Status: New = Fix Released
** Changed in: thermald (Ubuntu)
Importance: Undecided = High
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member
)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366541
Title:
System hangs when thermald is running
To manage notifications about this bug go
@Srinivas, I don't have any modern AMD kit. What kind of sensor
information do you require on the AMD platform?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366541
Title:
System hangs when
I guess running strace on sensors and capturing the output will show us
which paths it is reading.
Any chance of doing that Timothy and attaching the output to the bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Timothy, thanks, that sounds like a good idea. I'll close this bug as
fixed right away.
** Changed in: thermald (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thermald has been updated since this bug was reported. Is it still an
issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald prevents unmounting /dev/sda1 in recovery mode
To
So the issue is in libubuntu_application_api; so is it related to bug
#1206146
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364353
Title:
unity8 leaking memory on idle phone
To manage
@Srinivas,
From a previous bug report (bug 1366541) relating to this AMD based
system, the discussion was:
On Wed, 2014-09-10 at 17:33 +, Colin Ian King wrote:
@Srinivas, I don't have any modern AMD kit. What kind of sensor
information do you require on the AMD platform?
Since sensors
Public bug reported:
While trying to figure out what's keeping the phone busy when idle
(trying to save power), I noticed that unity8 is performing a lot of
frequent poll() system calls with timeouts of 85-195 ms and it times out
on these the majority of times.Wakeups keep a phone busy, so
Public bug reported:
Looking at the wakeups stats recently on mako, I spotted that the new
pay-service is one of the top wakeup contributors to an idle system, cf:
http://ci.ubuntu.com/power/eventstat/image/3435/machine/6/task_type/all/details/
I ran health-check against this (see the attached
We've been exercising the rtm images that include the latest workaround
now for a considerable amount of time repeating the test that originally
triggered the issue.
On mako, 2 devices running:
device #1, 329 iterations - no corruption observed
device #2, 251 iterations - no
** Changed in: linux-mako (Ubuntu)
Assignee: Colin Ian King (colin-king) = Paolo Pisati (p-pisati)
** Changed in: linux-mako (Ubuntu RTM)
Assignee: Colin Ian King (colin-king) = Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
I'm seeing crashes every 24 seconds because of a free on an invalid
pointer.
Attached is a strace using: strace -v -s 8192 -p $(pidof unity-settings-
daemon) -o strace.log
This is slowly driving me nuts.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package:
Wasn't this code being statically analysed with CoverityScan to avoid
this kinds of bugs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397232
Title:
unity-settings-deamon is continually crashing
@Ricardo,
I'm added copious amounts of debug into the kernel and a shim on umount
too and I can't see /dev/mmcblk023 being unmounted anywhere. Can you
inform me where to expect this umount is actioned on shutdown. I just
can't see it.
With full journaling on I'd expect this to cope with a
So just to re-iterate:
1. I believe the file system is not being cleanly umounted.
2. data=journal saved us from disaster because it works so well.
My recommendation is to keep data=journal because a user can power off
the device (battery death, pulling out battery, random kernel reboot,
etc)
I don't thing we're seeing many writes to that partition, most of it's
probably data pages being flushed out in the background so it's not
going to bite too hard. We do have tools to figure out how much is
being written if it needs some analysis.
--
You received this bug notification because
Did we conclude this is more of a misconfiguration rather than a
thermald issue pe se, if so, I may remove thermald from the bug and
rename it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348784
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384711
Title:
btrfs oops on current 3.13
To manage
I've added a futex stressor that rapidly does wait wait timeout and wake
futex calls to stress-ng. My intention is not to add too much complexity
to stress-ng as the core intention of stress-ng is to rapidly exercise
the interface in a specific way, rather than be a thorough and wide per-
system
run time stats.
** Affects: stress-ng (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: stress-ng (Ubuntu)
Status: New = In Progress
** Changed in: stress-ng (Ubuntu)
Importance: Undecided = Medium
** Changed
** Changed in: stress-ng (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/1387104
Title:
stress-ng: when running with a large number of stressors
** Changed in: stress-ng (Ubuntu Vivid)
Status: In Progress = Fix Committed
** Changed in: stress-ng (Ubuntu Vivid)
Importance: Undecided = Low
** Changed in: stress-ng (Ubuntu Vivid)
Milestone: None = ubuntu-14.11
--
You received this bug notification because you are a member of
We've moved to the intel-pstate driver by default for 14.10 which is an
improved frequency scaling driver. On some hardware we've had evidence
of this pushing the CPU a little harder and some machines were running
hot, so we've also included thermald to stop thermal overruns.
Also, thermald has
I forgot to mention that thermald does exit if the H/W or visualized H/W
does not support the necessary thermal controls, so on these systems
it's more like a no-op.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- thermald prevents unmounting /dev/sda1 in recovery mode
+ dbus invoked while in recovery mode
** Changed in: thermald (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Made some progress today.
On the phone, I am seeing:
/var/lib/apparmor/profiles/click_com.ubuntu.filemanager_filemanager_0.3.275
containing a pathname and all zeros. The start is always on a page
boundary and the end is always on a page boundary.
I copied the entire partition /dev/mmcblk0p23
The corruption to
/var/lib/apparmor/profiles/click_com.ubuntu.filemanager_filemanager_0.3.275
survives multiple reboots. I'll take another 6GB snapshot of the
underlying partition and see if that's now corrupted.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After several reboots, the data still appears corrupted on the phone,
but copying the underlying raw device /dev/mmcblk0p23 to my laptop and
loop mounting it and then loop mounting ubuntu.img shows an uncorrupted
var/lib/apparmor/profiles/click_com.ubuntu.filemanager_filemanager_0.3.275.
I'm now
Ruled out the bind mount of /var/lib/apparmor/profiles on /userdata
/system-data/var/lib/apparmor/profiles, still see corruption there on
the device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sanity checked the raw data from /dev/mmcblk0p23:
1. copied raw data off the phone to may laptop
2. using sshfs, mounted the directory containing the raw data snapshot back on
the phone
3. loop mounted it
4. loop mounted ubuntu.img from this
5. /ubuntu/var/lib/apparmor/profiles is sane, no
On the phone:
debugfs /userdata/ubuntu.img
cat /var/lib/apparmor/profiles/click_com.ubuntu.filemanager_filemanage
# vim:syntax=apparmor
#include tunables/global
# Define vars with unconfined since autopilot rules may reference them
# Specified profile variables
@{APP_APPNAME}=filemanager
I've searched the entire block device for the string
/usr/share/click/preinstalled/com.ubuntu.music/1.3.625/apparmor.json and
tagged it in such a way as it is obvious it that it has been modified on
the flash drive. I rebooted and double checked - the modified data is
still modified on disk
What does the following command report:
which thermald
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
So try re-installing it and seeing if that fixes things for you:
sudo apt-get --reinstall install thermald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389062
Title:
Failed to spawn thermald
After a lot of deep digging into the bind mount, loop driver, and buffer
cache and tracking the corrupt pages back down the layers of the stack
we've sanity checked this down to the image. The smoking gun was the
kernel message:
Nov 6 12:15:16 ubuntu-phablet kernel: [3.940485] do_mount:
I did originally think Btrfs: check file extent type before anything
else may have been a suitable fix for this
(https://bugzilla.kernel.org/show_bug.cgi?id=60834) however the kernel
you were using included that fix. Hrm.
** Bug watch added: Linux Kernel Bug Tracker #60834
Looks like we have a bad src page when doing the memcpy():
memcpy:
48 89 f8mov%rdi,%rax
48 89 d1mov%rdx,%rcx
f3a4 rep movsb %ds:(%rsi),%es:(%rdi)
// e.g. rep on *rdi++ = *rsi++
c3
Public bug reported:
Follwing ISO testing test I tried to select OEM install from the f4
option but I could not select any options on that menu. I could select
options from other menus.
Testcase: http://iso.qa.ubuntu.com/qatracker/testcases/1305/info
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
Testing ISO, testcase Install (manual paritioning re-using home
partition) in Ubuntu Desktop i386 for Trusty Daily, I can't see the
Upgrade Ubuntu option in the Installation type section of the
installer. Has this be removed/deprecated or is the test case out of
date?
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
** Changed in: thermald (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I'm unabled to reproduce this, thermald is not running when I booted
into recovery mode on 14.10. Can you reproduce this every time? If
so, can you report which processes are running on the system.
** Changed in: thermald (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
I think also we need to consider security of data is the ultimate goal.
Quite frankly, unpredictable things happen users can do all kinds of
things like yank out the battery and trip kernel panics. Nobody has
formally verified that the kernel is perfect so there is always the
possibility of the
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1399131
Title:
package thermald 1.3-7 failed to install
I've tried to reproduce this with an upgrade from 1.3-6 to 1.3-7 in a VM
and can't reproduce this. Since there is no thermal controls available
in a virtualised environment thermald will normally just exit and not
run, so perhaps this is what is happening.
Can you attach to the bug report the
Thanks, a fix will be available in 1.3-8 hopefully withing the next 12 or so
hours. I was able to reproduce the error (the error only happens on systemd
based systems in a VM where thermal sensors don't exist).
** Changed in: thermald (Ubuntu)
Status: Confirmed = Fix Committed
**
** Changed in: thermald (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/1399131
Title:
package thermald 1.3-7 failed to install/upgrade:
Public bug reported:
I've tracked memory utilisation of maliit-server over a 12 hour period
and can see that the heap is growing at about 1700 bytes a second. One
can see this by strac'ing the process and seeing glib's malloc
performing 4K mprotects every ~2.4 seconds and the occasional 1MB
To show the heap growth, run:
smemstat -p $(pidof maliit-server) 10
..and one sees ~1640 bytes per second heap growth.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364368
Title:
maliit-server
This seems to be leaking at the same rate as the leak in bug 1364368, so
it may be a common library that's leaking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364380
Title:
unity8-dash is
1 - 100 of 3501 matches
Mail list logo
