This is a fairly old bug and also seemed to be in relation with Unity.
I am marking this as invalid but if someone can still reproduce this
issue on a newer system please comment.
** Changed in: diodon
Status: New => Invalid
** Changed in: diodon (Ubuntu)
Status: Confirmed =>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: diodon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405525
Title:
apport information
** Tags added: third-party-packages wily
** Description changed:
For an unknown reason `diodon` turns into a state where adding items to
the list and cleaning the history constantly results in
** (diodon:22537): WARNING **: zeitgeist-clipboard-storage.vala:382:
Thanks Tasos for this additional feedback.
It is certainly not a good thing that zeitgeist-daemon needs to be
started during build which of course can cause issues as in your case.
Something I have noticed in the past as well. I now split integration
tests where Zeitgeist is needed and unit tests
I came across this bug while trying to build Diodon from source.
If I understood correctly, running sudo ./waf install, installs Diodon to the
specified prefix and also executes a build test.
From the waf install log:
[131/131] utest: _build_/tests/diodon-test
This spawns a new instance of
Always takes some time until the issue occurs...
Quitting and restarting `diodon` after running `zeitgeist-daemon
--replace --log-file zg.log --log-level=debug` works :) Still a lot of
work even for a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Meanwhile this issue persist even after reboot, either the original
cause for the blockage being removed after a reboot was not
deterministic, but random or a dependency changed and reintroduced a
bug.
Could it be that you at one point opened a desktop session as root or started
a desktop
apport information
** Tags added: apport-collected vivid
** Description changed:
For an unknown reason `diodon` turns into a state where adding items to
the list and cleaning the history constantly results in
** (diodon:22537): WARNING **: zeitgeist-clipboard-storage.vala:382:
Sure. There's nothing in `zg.log` and
$ zeitgeist-daemon --replace --log-file zg.log --log-level=debug
[08:06:54.968164 DEBUG] utils.vala:67: DATA_PATH =
/home/richter/.local/share/zeitgeist
[08:06:54.968283 DEBUG] utils.vala:86: DATABASE_FILE_PATH =
This is a zeitgeist bug so we have to see whether we get more
information from the zeitgeist service itself, could even be an corrupt
database.
So when you have this error that the database is locked, keep Diodon running
and run the following command:
zeitgeist-daemon --replace --log-file zg.log
so after you have run this command - close Diodon and start it again. Is
error message with database locked still occurring or does it run now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405525
I have created another bug report for showing critical error messages to
user https://bugs.launchpad.net/diodon/+bug/1424236 for better usability
when an error happen.
Concerning your response above - are you saying that the error doesn't
appear anymore or simply after a reboot error is not there
Concerning your response above - are you saying that the error doesn't appear
anymore or simply after a reboot error is not there but reoccurs again after
a while?
No, I meant while initially (at the time of reporting the bug) the blockage was
permantent and could not be fixed at all,
The blockage now no longer survives a reboot. `diodon`'s version is
1.2.0 and `zeitgeist`'s is 0.9.14-2.2ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405525
Title:
database is locked
I'll figure that out as soon as possible. If that's potentially a
problem, maybe you can add a warning in form of a popup dialog
explaining the problem. That would not only help me in further debugging
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That's not something Diodon has under control.
IMO it's sufficient to detect that the external resource is in an illegal or
malfunctional state and forward that information to the user. The check needs
to be included anyway in order to avoid a non-responsive state of `diodon`
regardless of the
That's not something Diodon has under control.
Anyway for now I just want to figure out a way what steps are needed to
reproduce this issue. When we found a reliable way it is then easier to
think about how to fix it.
--
You received this bug notification because you are a member of Ubuntu
zeitgeist-daemon shouldn't run twice and especially not as root so maybe
this is the problem.
I wonder though how this has happened that zeitgeist-daemon started as
root.
Could it be that you at one point opened a desktop session as root or
started a desktop application which potentially uses
I could finally reproduce the issue and `sudo pkill zeitgeist` _and_
restarting `diodon` did the job.
$ ps -ef | grep zeitgeist
richter 8099 6764 0 15:05 ?00:00:00 /usr/bin/zeitgeist-daemon
richter 8152 6764 0 15:05 ?00:00:00
19 matches
Mail list logo
