Public bug reported:
See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
cannot-exceed-16777216/4856/5
In containers, the limits.kernel.memlock cannot exceed 16777216 when the
container is bionic. The memlock setting is set to 16M in systemd and
cannot be bumped up in an unprivi
** Patch added: "fix-memlock-bump.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5267179/+files/fix-memlock-bump.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
The clock in the panel freezes after running for (at least sometimes) a
few seconds.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-gene
Added strace of same process after a while (still no updates of time in
panel, i.e. still freezed)
** Attachment added: "strace log after freeze"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1294580/+attachment/4032082/+files/indicator-datetime-service.strace.continued.log
I added this to my crontab:
# m h dom mon dow command
* * * * * killall indicator-datetime-service
Now it seems consistable freezing within 3 or 4 seconds (I have seconds
displayed also and it stops at hh:mm:03 or hh:mm:04)
--
You received this bug notification because you are a member of
Nope. Is already installed and newest version. This error doesn't occur
on every restart of indicator-datetime-service (from the cron).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294580
Title:
i
I did as described at
https://wiki.ubuntu.com/Backtrace#Already_running_programs
One differenc: Hitting ^C didn't work, so I've used 'kill -SIGINT ' to get back to the gdb prompt.
** Attachment added: "gdb output"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1294580/+att
Yeah, that's what I see in the strace log.
I think that the problem/symptom is that the poll just times out and
doesn't get data on the event-fd.
tail of indicator-datetime-service.strace.log:
11:00:28 eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 22
11:00:28 write(22, "\1\0\0\0\0\0\0\0", 8) = 8
11:00:28 w
It appears to be related to my EWS account in evolution. When I remove
that, all works fine. When I added that account again (all default
settings, except for checking mail every 10 minutes in stead of 60 and
disabeling the 'apply filters'), the clock stopped after a short while
(but several second
BTW. I noticed yesterday that the calendar items of the EWS account are
not displayed in the evolution calendar interface and that the calendar
interface/evolution seems to hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Well, the items apear, but only after about 15 minutes (while evolution
is unresponsive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294580
Title:
indicator-datetime-service panel clock freezes
In outlook, I've archived all events before this year (that didn't help)
and then removed about 30 yearly events. The latter made evolution
responsive again.
I guess we can change this bug to a feture request: Make clock going on
when timeouts/errors occur in calendar.
--
You received this bug n
12 matches
Mail list logo
