Also getting these messages (trying to find useful information in syslog
due to other issues, found these messages spamming).
NVme as well.
uname -a
Linux computer 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
#journalctl -m | grep ureadahead | wc
Thanks, workaround in #19 seem to have removed (thousands of) these
messages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative
Lots of errors etc in syslog, added some notes on top of the obvious
errors.
Kernel keeps spamming syslog with these
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748565):
kernel: [15621.044566] Bluetooth: hci0: last event is not cmd complete (0x0f)
Note: this kernel message disappears
Ubuntu 18.04.1. Jabra Elite Sport v2. Impossible to get A2DP to stick.
Have to go through multiple jumps to get it to work. E.g.,
1) Shut down and start bluetooth a few times after suspend or reboot.
Sometimes i try to shutdown the Jabra device as well.
2) Then connect to the device, which
Sorry, small adjustment. I use wayland as default since 17.10 with gdm
(works well in general for me):
loginctl show-session c1 -p Type
Type=wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard
language does not work either most of the time (Super + Space). Those I
use the most. Extremely annoying after some time, especially when using
dual screens (since the Gnome top bar is only on one monitor which is
even more
The problem went away in 17.10. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status
*** This bug is a duplicate of bug 774071 ***
https://bugs.launchpad.net/bugs/774071
The problem went away in 17.10. Cheers.
** This bug has been marked a duplicate of bug 774071
Indicator-datetime-service renders 100% CPU usage
--
You received this bug notification because you are a
Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:
https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4
Will test 17.10 now.
--
You
Last work-around didn't stick. Did some test and can reproduce the error
now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service
that crashes when its the evolution calendar that is the problem. During
the system overload the problem can be fixed by killing all evolution
processes
(#51 was a mistake)
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime
Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.
I
Public bug reported:
Same as Bug #774071 but with 100% RAM instead. Collected info while the
Indicator-datetime-service was acting up. I.e., writing this with a few
hundred megabytes RAM available..
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: indicator-datetime
PID changes after crash when RAM is depleted. Sceenshoot of RAM usage
attached.
** Attachment added: "Exampel of memory usage"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5008303/+files/Screenshot%20from%202017-11-13%2015-29-41.png
--
You received
This hits me constantly. Why is this bug present years on end and three
major Ubuntu versions? The workaround is easy enough, still for many
users it is rocket science and will break the update procedure (I two
other persons that cant fix it themselves). I.e, thus is a critical
problem. Make a
Got this in 16.04 today, fully updated. Has happened in older releases
as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1542733
Title:
Connect to Hidden
Also getting lots of these (new installation).
Sep 14 21:20:14 boll org.gnome.zeitgeist.Engine[1592]: message repeated 3
times: [ ** (zeitgeist-datahub:2095): WARNING **: zeitgeist-datahub.vala:212:
Error during inserting events:
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument:
*** This bug is a duplicate of bug 1485685 ***
https://bugs.launchpad.net/bugs/1485685
That makes no sense since the workaround in this thread is useful for
those searching for a solution to the problem (this year) and your
description appears to be the duplicate since it was filed later :-)
Don't think i can verify this on the other computer as stated. It seems
to be a different problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd
@Martin,
Sorry for late reply. I spilled juice in my computer and it fried. Never
gets old :-) I have a new computer so I cant do proper debugging
anymore. I will check a friends computer since I think he has the exact
same problem. On Wednesday next week that is (is in transit until then).
Requested syslog attached (for real).
** Attachment added: Syslog for two consecutive boots (systemd,upstart)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412564/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch
Requested syslog attached.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd does not allow to boot with /home on dm-crypt
Status in systemd package
I have a very similar issue. Upstart works but systemd does not. Lucs
encrypted logical volume on a work computer. It has worked flawless with
boot for many versions of Ubuntu (even before upstart I think). I can
produce the syslog with two boots tomorrow. Also have taken a picture of
the actual
Some setup info as previous post:
sda5_crypt UUID=acdea251-1e21-4612-afce-4101e364d6c6 none luks
cryptswap1 /dev/dm-1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
mount -l with upstart
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc
Connectivity issues reported:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/comments/17
Read the full thread with information before making claims. An I wrote
and perhaps connectivity issues as well (which is not unlikely). Nuff
said.
--
You received this bug notification because
Well, bug 57843 does not describe symptoms besides spamming of the
syslog. This bug does describe spamming of syslog and perhaps
connectivity issues for some users. However, the the upstream bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539915 you mention
NoOp seems to be similar to this
Thank you ricklee! Worked on my setup too. Still, this message should
only be visible with verbose debugging. Muted as default for consumers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Any idea how this error message can be muted?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089
Title:
wpa_supplicant writes to syslog every 2 minutes
Status in “wpa”
Note that the bug https://bugs.launchpad.net/cloud-init/+bug/1309079
mentions that the work-around is not good enough. Will test myself
today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
The work-around in https://bugs.launchpad.net/cloud-
init/+bug/1309079/comments/5 did work as expected:
sudo rm /boot/grub/menu.lst
sudo update-grub-legacy-ec2 -y
sudo apt-get dist-upgrade -qq --force-yes
However, as I understand, the prompt will still appear when doing later
upgrades.
--
You
Related bug marked as fixed:
https://bugs.launchpad.net/ubuntu/+bug/1009294
Discussion of workarounds: http://askubuntu.com/questions/146921/how-
do-i-apt-get-y-dist-upgrade-without-a-grub-config-prompt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Why is there no response to this bug? You keep pushing up releases with
this bug for no good reason!
Confirmed in the eu 14.04 ebs ami-cb4986bc version at https://cloud-
images.ubuntu.com/locator/ec2/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
34 matches
Mail list logo
