>> If I understand things correctly there is no data lost because
>> the write to disk happens when logging in is that correct? If
>> so then this doesn't seem necessary to fix in natty.
Right, the only data that is lost is information on which data-sources
logged events recently. This information
** Changed in: zeitgeist (Ubuntu)
Importance: Undecided => Medium
** Changed in: zeitgeist (Ubuntu Natty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Ti
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
** Branch linked: lp:~zeitgeist/zeitgeist/zeitgeist-0.7.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such f
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
** Also affects: zeitgeist (Ubuntu Natty)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _wri
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such file or directory:
'/home/royg
If I understand things correctly there is no data lost because the write
to disk happens when logging in is that correct? If so then this
doesn't seem necessary to fix in natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** 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
OK so a primary solution for this was putting the content of _write_to_disk
in datasource_registery.py in a normal " try - catch " block
My primary fear was that the next extension or zeitgeist would crash trying
to write to the disk. This was not the case and the error was caught.
To explain why t
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-ba
So this looks to me like a problem not only Zeitgeist is facing but anything
that is running and wants to write to disk upon session end.
On Thu, Apr 21, 2011 at 5:07 PM, Seif Lotfy
<738...@bugs.launchpad.net>wrote:
> So as Markus said, the crash report comes from the session before.
> This impli
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 writ
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 ar
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with I
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
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 Ubunt
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
handle_exit()
File "/usr/bin/zeitgeist-daemon", line 126, in handle_exit
interface.Quit()
File "/usr/share/zeitgeist/_zeit
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such file or directory:
'/hom
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 Ubuntu
Bugs, which is subscri
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgei
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 into ~/.Private)
Thanks in advance,
Markus
** Changed in: zei
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 r
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
26 matches
Mail list logo