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
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1350871
Title:
location service is waking up at
BTW, which binary blob is the chipset driver? i don't mind looking at
it and seeing if we can tweak it a bit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1350871
Title:
Public bug reported:
I believe this is a change in shutdown tied somehow to systemd, but I am
guessing.
How to reproduce the bug:
sudo shutdown -h now
[ wait a couple of minutes, don't enter in one's password ]
authentication times out and one is left with non-echo on one's tty.
This has to be
Public bug reported:
For reasons I cannot fathom, my development server goes into deep
suspend after ~3 minutes after startup with systemd, however, if I boot
with upstart it does not. This happens everytime I boot with systemd,
the machine just goes into a deep suspend without me requesting
Public bug reported:
I noticed that systemd on my idle Wily desktop is creating very short
lived threads at 1Hz. While these aren't doing much, it still consumes
power doing wakeups to create these periodic threads.
Showing thread creation with forkstat:
$ sudo forkstat
Time Event PID
This affects me, the search does not work, which is a real pain for
large documents of thousands of pages; not being able to search makes
the tool unusable for large docs.
** Changed in: evince (Ubuntu)
Status: Expired => Confirmed
** Changed in: evince (Ubuntu)
Importance: Low =>
Public bug reported:
I've instrumented a kernel so I can clearly see when processes start and
exit, this allows me to see when exactly the kernel has handed off
control to userspace. The time the kernel actually takes to initialize
compared to the time systemd-analyze reports are different.
$
I think this is a systemd/udevd kinda bug isn't it?
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I was running the new stress-ng softlockup stressor and observed that
systemd-journald gets killed with an abort and this corrupts the systemd
journal.
How to reproduce:
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make clean; make
sudo ./stress-ng
I deem that it should be removed, it is too much of a maintenance
overhead and has way too many issues to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1758163
Title:
Public bug reported:
I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gnome-calendar opens
/usr/share/zoneinfo/Europe/London on my machine every minute. This
causes the access time (atime) to be updated causing a metadata
Oh, actually, it was doing 10 accesses in 300 seconds, so it's polling
every 30 seconds, higher than I first thought.
** Summary changed:
- gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds
+ gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds
** Changed in: gnome-calendar
Public bug reported:
I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gsd-color opens
/usr/share/zoneinfo/Europe/London on my machine at regular intervals.
This causes the access time (atime) to be updated causing a
Public bug reported:
gsd-housekeeping is opening /etc/fstab every 60 seconds and because it
is being opened without the O_NOATIME flag the access time updates are
causing regular meta data flushes. On an idle laptop this can cause the
HDD to spin up, flush write and spin down every 60 seconds.
Public bug reported:
At seemingly random intervals throughout the day gnome-shell becomes
very active, the CPU gets very busy and the fans kick in because of the
large load.
I attached health-check to the busy process for 60 seconds and got the
following utilization stats:
sudo health-check -p
** Attachment added: "ASCII log of health-check analysis"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943434/+attachment/5524939/+files/health-check-report.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
17 matches
Mail list logo
