beagle doesn't look for liferea feed in ~/.liferea_1.2 folder

Bug #103295 reported by VF
6
Affects Status Importance Assigned to Milestone
Beagle
Fix Released
Medium
beagle (Ubuntu)
Fix Released
Undecided
Kevin Kubasik

Bug Description

Binary package hint: beagle

Used to work with 1.0 pre-Feisty, guess it's the new cache format mentioned in the message: "Liferea 1.2 uses a new cache format and has migrated your feed cache."

Revision history for this message
VF (vfiend) wrote :

Huh, seems to work okay now after manually removing the beagle liferea index directory, closing

Changed in beagle:
status: Unconfirmed → Rejected
Changed in beagle:
status: Unknown → Rejected
Revision history for this message
Rafał Próchniak (burlap) wrote :

Doesn't work for me with a clear feisty install.

After I do (with exercise the dog):

beagled --debug --fg --backend Liferea

I get nothing (see youserlf below):

Always: Starting Beagle Daemon (version 0.2.16.3)
Always: Running on Mono 1.2.3.1
Always: Using sqlite version 3
Always: Command Line: /usr/lib/beagle/BeagleDaemon.exe --debug --fg --backend Liferea
Debug: Established a connection to the X server
Debug: Starting main loop
Debug: Beginning main loop
Debug: Starting messaging server
Debug: Starting QueryDriver
Debug: Found 0 backends in /usr/lib/beagle/Backends/EvolutionBackends.dll
Always: BEAGLE_EXERCISE_THE_DOG is set.
Debug: Found index helper at /usr/lib/beagle/beagled-index-helper
Debug: Found 1 backends in /usr/lib/beagle/BeagleDaemonLib.dll
Debug: Reading mapping from filters
Debug: Loading system static indexes.
Debug: Found 0 system-wide indexes.
Debug: Found 0 user-configured static indexes..
Debug: Starting queryables
Debug: Starting backend: 'Liferea'
Debug: Starting Scheduler thread
Debug: Starting Inotify threads
Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
Debug: Daemon initialization finished after ,21s
Debug: Memory usage: VmSize=55,2 MB, VmRSS=16,4 MB, GC.GetTotalMemory=962560
Debug: Caught ResponseMessageException: Connection refused
Debug: InnerException is SocketException -- we probably need to launch a helper
Debug: Launching helper process
Debug: IndexHelper PID is 6831
Always: Starting Index Helper process (version 0.2.16.3)
Always: Running on Mono 1.2.3.1
Always: Using sqlite version 3
Always: Extended attributes are supported
Always: Command Line: /usr/lib/beagle/IndexHelper.exe
Always: BEAGLE_EXERCISE_THE_DOG is set
Debug: Found IndexHelper (6831) in ,51s

No liferea feeds are indexed... Should I reopen?

Revision history for this message
VF (vfiend) wrote :

Try running beagle-shutdown
then "rm -rf ~/.beagle/Indexes/LifereaIndex/
then starting beagle again.

That's what fixed it for me.

Revision history for this message
Rafał Próchniak (burlap) wrote :

I did it before I reported my results here.

I started beagle with Liferea backend only without liferea index folder. I have this folder again, as empty as before. I refreshed all the feeds too...

Do you have fresh feisty or upgraded from edgy? What's the name of the liferea folder (in my feisty it's ".liferera_1.2")

Revision history for this message
VF (vfiend) wrote :

Fresh feisty, but I kept my home folder.
Have you tried removing the .liferea directory? After running Liferea 1.2 it says you should do that. Maybe beagle's getting confused by the fact that there are two different liferea profile directories. Though, after running liferea again, it gave me a .liferea symlink to .liferea_1.2.

I'd run beagle-shutdown, put .liferea in the trash, run liferea again, remove the LifereaIndex, then try running beagle again. I think that's what I did.

Revision history for this message
Rafał Próchniak (burlap) wrote :

I created a .liferea symlink to .liferea_1.2 folder and it works now, so it looks like a bug. However, I'm not sure whether it's beagle that should look in .liferea_1.2 folder or liferea that should create a symlink. Seems to be a bug anyway.

Changed in beagle:
status: Rejected → Needs Info
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

Liferea 1.2 has a new cache format, while beagle can still parse some of the cache files properly, the Liferea backend is in need of a rewrite. I've taken the assignment for the moment, but if someones interested, get in touch with me and its all yours.

Changed in beagle:
assignee: nobody → kkubasik
status: Needs Info → Confirmed
Revision history for this message
Félix Velasco (felix-velasco) wrote :

From liferea migration code (see http://sourceforge.krugle.com/kse/files/svn/svn.sourceforge.net/liferea/liferea/src/fl_sources/default_source.c lines 223+), the only modified file is the sources list, feedlist.opml. Both feeds and favicons folders are just copied in moving from either liferea 1.0 or 1.1 to liferea 1.2.

Since the only modified file is not and indexed one, I suppose the only patch should be checking for the right directory, either .liferea_1.2, .liferea_1.1 or just .liferea. Am I missing something?

Revision history for this message
dBera (dbera-web) wrote :

Someone above said "Have you tried removing the .liferea directory? After running Liferea 1.2 it says you should do that. ... Though, after running liferea again, it gave me a .liferea symlink to .liferea_1.2." - can anyone else confirm if this is the case ? If liferea indeed creates the symlink, then liferea is properly taking care of its data location. Beagle would work w/out any change.

Revision history for this message
VF (vfiend) wrote :

I may have created the symlink myself when I was trying to solve the problem, I don't remember.

Revision history for this message
Rafał Próchniak (burlap) wrote :

I'm sure I created the symlink myself. On clean Feisty liferea creates a .liferea_1.2 folder only.

Revision history for this message
Félix Velasco (felix-velasco) wrote : Re: [Bug 103295] Re: beagle doesn't look for liferea feed in ~/.liferea_1.2 folder

Liferea 1.2 creates .liferea_1.2, and, if upgrading, asks the user to
delete .liferea. It neither creates a symlink nor erases anything.

2007/5/9, Rafał Próchniak <email address hidden>:
> I'm sure I created the symlink myself. On clean Feisty liferea creates a
> .liferea_1.2 folder only.
>
> --
> beagle doesn't look for liferea feed in ~/.liferea_1.2 folder
> https://bugs.launchpad.net/bugs/103295
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
dBera (dbera-web) wrote :

Ok. Can someone re-open the upstream bug please ?
Thanks.

Revision history for this message
VF (vfiend) wrote :

It's my bug so I reopened it, commented with clarification, and changed the title to something more descriptive.

Changed in beagle:
status: Rejected → Unconfirmed
Revision history for this message
VF (vfiend) wrote :

Fixed upstream

Changed in beagle:
status: Confirmed → Fix Committed
Changed in beagle:
status: Unconfirmed → Fix Released
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

Fix in hardy release

Changed in beagle:
status: Fix Committed → Fix Released
Changed in beagle:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.