v2.2.7 Library Import Directory bug (fixed)

[Opus4]

A bug has been found in the recent v2.2.7 SageTV release:

When running as a service, SageTV will not see your Library Import Directories. The import directories will be ignored and removed from the list when SageTV restarts, which will also remove all library files from view inside SageTV. (The files will still be on your drive, but not visible to SageTV.)

This only happens when the SageTV service mode is used, when it restarts. If you do not use the service mode, you should not be affected by this. If you want to use the service and keep your library import directories, use v2.2.6 for now.

As usual, an update with the fix will be released in the future, after further testing to make sure this is fixed and after checking for other issues.

- Andy

[mdmint]

Didn't check that after upgrading yesterday. Yup, can't see Library. Geeze, seems like using service mode & using library directory rather common configuration to miss such a bug in a "release" version. Oh well, just glad it doesn't really make much difference to us, if we want to watch a movie stored in our Library will use another application.

[ToxMox]

I'm not having this problem with 2.2.7 in service mode. I didn't have any directories set before upgrading. I always add my library directories temporarily to watch an import then remove the directory afterwards.

After seeing this thread I tried adding a dir and it worked fine. Does it remove the directories after a certain amount of time?

[Opus4]

Sorry, I didn't make that clear: It gets cleared when SageTV restarts. I'll go update the first post to mention that.

- Andy

[korben_dallas]

Must be specific to 2.2(.7) because I'm on 2.2.6 w/ service mode, and all my import directories are still there after many reboots.

[Opus4]

Yes, it is specific to the v2.2.7 release... which is why the first post says to stick with v2.2.6 for now if you want to use library imports with service mode.

- Andy

[stanger89]

Data point:

My library is just fine with 2.2.7

[abasu2003]

data point, my library list got cleared with 2.2.7

but its a very minor problem since the fix is so easy: just add your libraries into sage again.

i guess its bad if it does that every time you restart the service though.

[mdmint]

Originally Posted by abasu2003

data point, my library list got cleared with 2.2.7

but its a very minor problem since the fix is so easy: just add your libraries into sage again.

i guess its bad if it does that every time you restart the service though.

Data Point:
After upgrading to 2.2.7 Library was gone, running service mode. Added Library back, verified Library seen and playback ok from Client. Stopped and restarted service, closed and reopened Client and Library gone again...

[mdmint]

Originally Posted by stanger89

Data point:

My library is just fine with 2.2.7

Is your Library local drive partition or unc? Mine unc and goes bye-bye if stop & restart service.

[stanger89]

Never mind, I'm not running what I thought I was.

[src666]

I ran into an odd and possibly unrelated issue. From my remote Sage Client, I noticed that the Library mappings were gone. I tried to re-create them, but they are UNC paths and the dialog box wouldn't let me enter any backslashes (\) to properly form the path. I went to the server's instance of Sage, and was able to enter them without any problems. Anyone else run into this?

[Opus4]

Did you map the '\' key to some SageTV command?

- Andy

[src666]

Nope, and I went to Unmap to clear it just in case. Even then, it still wasn't accepted in the dialog. I figured it was a unique wierdness (I seem to generate a pretty strong UW field), but thought I would mention it just in case.

[mkkawamo]

Hmm... somehow I missed 2.2.6 and since 2.2.5 has been working fine for me, and I do run Sage as a service, I think I'll just stick with 2.2.5 until there's a fix for this Library import bug.

[mayamaniac]

I just upgraded too, bummer. Oh well, I don't use media library much anyway. So where's 2.2.8 fix? :P

[Stuntman]

This seems like a pretty big bug.. it is to me anyhow.. yet I see no official word as to it's status.. Anybody have any idea when this issue will be resolved and available to us? Or has it already been fixed and the 2.2.7 release that is currently available a 'replacement' of the original release?

Thanks!

[nielm]

See the first post in this thread:

As usual, an update with the fix will be released in the future, after further testing to make sure this is fixed and after checking for other issues.

and watch the Announcements forum for details.

[Stuntman]

Originally Posted by nielm

See the first post in this thread:and watch the Announcements forum for details.

Yes.. "In the Future"... when else would an update be released?

It's been almost a week.. and with this type of bug in a released version I had expected a much quicker fix.. and I realize it needs to be tested, but as far as I see no beta test has been released either.. which made me wonder what the status was..

I'll simply wait and watch a bit longer.. no worries.. "Shortly", "Soon", "This Weekend" and "Tonight" are all subject to interpretation when it comes to release times, right Nielm? (Just kidding!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)

[mayamaniac]

Originally Posted by Stuntman

This seems like a pretty big bug.. it is to me anyhow.. yet I see no official word as to it's status..

The odd thing is Frey is still releasing 2.2.7 with this bug on the download page. For those people wanting to test out sagetv for the first time, but with a bug like this, they might get frustrated and stop using it. Or imagine if someone is writing a review on Sage based on 2.2.7. You would think Frey should release 2.2.6 as trial instead for the moment until 2.2.7 is fixed.