Please describe the problem.
Following steps from http://git-annex.branchable.com/assistant/quickstart/ does not get past the first screen.
What steps will reproduce the problem?
- On a nearly fresh Lubuntu system, nearly fresh account, Lubuntu session, run
git-annex
from the start menu. Opens firefox, in
Create a git-annex repository
select my~/Documents
folder, pressMake Repository
.Expected: a new, different page opens.
- Observed: the same page opens, only difference the path displayed is
/home/mylogin/Documents
. PressingMake Repository
again shows the same page again.
I couldn't find any logs at the time. Now I see that they are in .git/annex/daemon.log but content from that time is already gone.
What version of git-annex are you using? On what operating system?
A fresh Ubuntu 14.04 (actually Lubuntu but this shouldn't change anything, right ?), create a user, login.
LC_ALL=C apt-cache policy git-annex
git-annex:
Installed: 5.20140412ubuntu1
Candidate: 5.20140412ubuntu1
Version table:
*** 5.20140412ubuntu1 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
100 /var/lib/dpkg/status
Please provide any additional information below.
# No command line in bug occurrence. This is the transcript of the workaround I found.
# Actually, the PC was rebooted then I went command line.
cd ~/Documents
git status
fatal: This operation must be run in a work tree
# oh I see it's a bare repo
git annex add .
add (my file names... one line for each) ok
(Recording state in git...)
Now the webapp seems to run okay, I can see many pages, schedule checks, etc.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-> Ok but log shows only events after I manually dit git annex add.
[2014-06-08 14:28:46 CEST] main: starting assistant version 5.20140412ubuntu1
[2014-06-08 14:28:46 CEST] Cronner: You should enable consistency checking to protect your data.
dbus failed; falling back to mtab polling (ClientError {clientErrorMessage = "runClient: unable to determine DBUS address", clientErrorFatal = True})
(scanning...) [2014-06-08 14:28:46 CEST] Watcher: Performing startup scan
(started...) [2014-06-08 14:28:47 CEST] Committer: Adding (myfiles)
add (my files...) ok
[2014-06-08 14:32:51 CEST] Committer: Committing changes to git
[2014-06-08 14:34:12 CEST] Committer: Committing changes to git
[2014-06-08 14:34:13 CEST] Committer: Adding (myfiles)
ok
(Recording state in git...)
(Recording state in git...)
(Recording state in git...)
(Recording state in git...)
(Recording state in git...)
add (myfile) ok
add (myfile) [2014-06-08 14:34:13 CEST] Committer: Committing changes to git
[2014-06-08 14:42:48 CEST] Cronner: Consistency check in progress
fsck (myfile) (checksum...)
ok
# End of transcript or log.
Question:
cat /etc/xdg/autostart/git-annex.desktop
[Desktop Entry]
Type=Application
Version=1.0
Name=Git Annex Assistant
Comment=Autostart
Terminal=false
Exec=/usr/bin/git-annex assistant --autostart
Categories=
Should there be a git-annex process whenever I log in even if I don't launch the webapp ? I can check that on next login.
At the moment there is "git-annex webapp" and several child processes.
It sounds rather like the webapp is failing to create the repository. Although I would expect for it to show an error message in red beneath the repository path. OTOH, it also sounds like something (either the webapp or eg a manual git-annex run) set up a git-annex repository in ~/Documents.
git-annex will be started automatically on login as long as
~/.config/git-annex/autostart
lists a repository to use. If that file exists and contains ~/Documents then we'll know that the webapp successfully set up the repository.No message in red at any time.
There was none before the webapp. After the webapp failure, there was one, but without any file. Only after I manually did git annex add, it looked "unlocked".
Can't check now, the machine is off. Should check soon. Thanks.
As told before, there was definitely no git repository there before the webapp tried to create one.
There exists a ~/.config/git-annex/autostart containing one line, the correct /home/mylogin/Documents path to the folder.
There is no process with git or annex in its name when user logs on his desktop session.
git-annex assistant --autostart
?I tried to reproduce the bug on another account on the same machine, same LXDE environment. The bug did not occur again.
To answer that, I went back to the first account. Just logging in. The following git-related processes are automatically launched without running
git-annex assistant --autostart
.So, somehow things went back in order by themselves ?
There were quite a bunch of software upgrades from Ubuntu, including
lxsession
. Perhaps something was wrong in handling autostart desktop files ?Since things appear to work now, should we close the bug ?
Since this is a little strange, I just looked again at the machine. Your software attracts archivist kind of git-annex user, so don't be surprise that I kept logs of the machine.
Short answer: confirmed it was a LXDE issue, now fixed.
From what date has git-annex started to work ?
So I tried to enable it on June 7, reported bug on June 8. The the machine was used on a regular basis but git-annex assistant was ineffective. Then it started working as expected from June 30th.
Any package install near June 30th ?
Updates installed regularly.
Which packages were installed on 2014-06-30 ?
And indeed 0.4.9.2+git20140410-0ubuntu1.1 : “lxsession” package : Ubuntu
So it was indeed a lxde bug.
Diff text
I added a comment there (#69) which may serve as a hint to other people having not updated their system. Bug #1308348 “network settings indicator missing from panel” : Bugs : “lxsession” package : Ubuntu
That lubuntu bug explains why git-annex would not autostart on login.
However, that does not explain the original problem description, which was that the
Make Repository
button seemed to make a repository but not switch to the webapp running in that repository. In the case of making a new repository, the webapp is started in it by git-annex, not by the desktop autostart mechanism.Can you reproduce the original problem?