** Branch linked: lp:~zeitgeist/zeitgeist/zeitgeist-0.7.2
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in
** Tags added: iso-testing
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such file
** Also affects: zeitgeist (Ubuntu Natty)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon
I managed to replicate it and tring to fix the issue
On Thu, Apr 21, 2011 at 2:15 PM, amay82 738...@bugs.launchpad.net
wrote:
Have an encrypted $HOME too... but I don't know how to reproduce, it
just occurs sometimes when logging in
--
You received this bug notification because you are
So as Markus said, the crash report comes from the session before.
This implies that the home directory is unmounted or encrypted again before
zeitgeist can write something to it when it receives a SIGHUB or SIGTERM signal.
The solution to this either to not allow the datasource register y to
I found an easier way to replicate the error.
1) Open Terminal (terminal1) and run zeitgeist-daemon --replace
2) Open another terminal (terminal2) and do cd ~/.local/share/ then mv
zeitgeist zeitgeist-backup
3) In terminal1 then do Ctrl+c to quit Zeitgeist
(remember to move the zeitgeist-backup
** Branch linked: lp:~seif/zeitgeist/fix-738555
** Changed in: zeitgeist
Status: Triaged = In Progress
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) = Seif Lotfy (seif)
** Changed in: zeitgeist
Milestone: None = 0.7.2
--
You received this bug notification because
Hey guys,
Can someone tell us how to reproduce this. It will help us fix the issue.
Thanks
Seif
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
I was investigating on this bug a bit further. All Tracebacks are
looking like
Traceback (most recent call last):
File /usr/bin/zeitgeist-daemon, line 180, in module
handle_exit()
File /usr/bin/zeitgeist-daemon, line 126, in handle_exit
interface.Quit()
File
On Fri, 2011-04-08 at 06:37 +, Markus Korn wrote:
So this leads to a simple question: How do we want zg to behave
I'd like zg to connect to the gnome-session signal for shutdown and save
before the disk gets unmounted.
--
You received this bug notification because you are a member of
Just to confirm what was said earlier in the timeline, I got this crash
message and I also use encrypted homedirs on natty updated daily.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
It's the same as for Ted here, i have an encrypted /home which makes zeitgeist
crash on boot, maybe because the /home is not yet ready...
Is there a way to delay zeitgeist-daemon to check this theory?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team,
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such
Hi @all,
we discussed this issue in the #zeitgeist IRC channel, our theory is: it's
related to encrypted homedirs, and that this dirs get unmounted before the
zeitgeist daemon stops. So the daemon is unable to write to $XDG_DATA_HOME.
We'll investigate further, and keep you updated.
Thanks for
Markus this doesn't seem to happen when ZG stops, but when it starts up
or something. At least that's what I gather from the dupes
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
On Thu, 2011-03-31 at 13:44 +, Markus Korn wrote:
In order to find a way to fix this bug I would like to know from someone who
is affected by this bug
- which files/dirs get encrypted?
- esp.: are files in ~/.locale or ~/.local/zeitgeist encrypted (for example
by symlinking them
This looks *very* weird to me, I'll investigate later this week.
** Visibility changed to: Public
** Changed in: zeitgeist (Ubuntu)
Status: New = Triaged
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Assignee: (unassigned) = Markus
17 matches
Mail list logo