6.1-trunk does not seem to follow symlinks anymore. (This time I _did_
check the bug repository). Quite the showstopper for me as well. On
the bright side - it will probably be patched within 12h :)
C.
___
beta mailing list
beta@lists.slimdevices.com
htt
> Or 5 minutes even. :)
Ladies and gentlemen, we have a new record! ^^
Thanks, C.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/beta
> Hi All - I've checked in a modified patch from 'waka' that supports Unicode
> characters on the SB2 display. This code is in the 08-05-2005 nightlies.
Excellent news - however, no luck yet.
> To use it, you'll need to download a Unicode TrueType Font, and place it in
> the Graphics/
> folder.
> I've just added some debugging to help with this. Use --d_graphics
2005-08-05 23:24:47.1317 Error while trying to load GD Library: [Can't
locate GD.pm ...
Oh well...
# apt-get install libgd-gd2-perl
Fixed. Works beautifully now.
My thanks to you and waka, love you guys :)
C.
___
~24h ago I updated my slimserver from SVN, as I do about once a week.
Since then the server exits silently whenever I try to play a song. I
only tried FLACs, since that's what I have but I can test other
formats if it helps.
Which debug options to set?
C.
_
> The trunk is in a bit of flux right now, fyi.
>
> What error do you see on the command line?
Updated to 5114 which is quite a bit better. I must have caught a
weird build yesterday. Now I get:
- normal playback for plain English or German tagged songs
- crash on anything tagged Japanese, and th
I briefly reported this issue a few weeks ago, when "the trunk was in flux" :)
Seeing as Slimserver still crashes when asked to play a track tagged
with slightly esoteric characters. That is, umlauts and accents are
fine, Japanese is not. On exit, the server leaves the following in the
log:
"Wide
Any news on the original issue?
Thanks, C.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/beta
FW29 from build 6029 on one of the first SB2s:
- wireless is fine (Apple 802.11g UFO. Signal strength is reported ~10
percent points lower than before, no dropouts though)
- Unicode works for me again after months of crashes. (Not FW-related
but still makes me happy.)
- whatever was making the s
Hi all!
A little feedback on the mysql stuff in the trunk ...
I'm using 8468 on Debian testing-amd64, with everything in Bin and
CPAN/Arch provided by native packages, including mysql (5.0.22-3).
Everything works fine thus far, except that I get my very own mysql
zombie when I start slimserver:
Have you opened a web page? I seem to remember seeing a zombie from the
scanner which are reaped as soon as the web page is opened.
Nope, didn't help.
Will try to get slimserver into the main instance.
C.
___
beta mailing list
beta@lists.slimdevices
Everything works fine thus far, except that I get my very own mysql
zombie when I start slimserver:
I "fixed" this by letting slimserver populate a db inside the main
mysql instance.
Even so, slimserver eats a lot of memory ... top output:
PID USER PR NI VIRT RES SHR S %CPU %MEM
[Sorry, somehow this got classified as spam ... ]
Is SlimServer idle during this time? Or are you planing music? Remote or local?
In my case the figures quoted are for a newly started slimserver
process, which is as idle as I can make it - scanner not running, no
music playing, no softsqueezes
Any plugins loaded?
These I actually use:
Date and Time Screensaver
Random Mix
Favorites
These are loaded because I might need them sometime:
Save Playlist
Rescan Music Library
Network Test
RSS News Ticker
Podcasts
Loaded because one or more of these is
> Favorites
With recent changes this latter isn't a plugin any more :-)
Be that as it may, I'm stuck with revision 8703 until Debian ships the
outrageouly recent version of libyaml-syck-perl. (Or maybe until I get
around to building the binary part myself.)
Don't load them until you need them
>Be that as it may, I'm stuck with revision 8703 until Debian ships the
>outrageouly recent version of libyaml-syck-perl. (Or maybe until I get
>around to building the binary part myself.)
It's available at http://debian.slimdevices.com/
Thanks, but that's for "i386-stable" and I'm using "amd64
Hi again!
After a mysql update today slimserver has stopped working - I get the
following in slimserver.log:
Transactions not supported by database at /usr/lib/perl5/DBI.pm line 1666.
The update itself consisted of security and bug fixes, so seemed safe.
Versions are what's current in Debian te
> Transactions not supported by database at /usr/lib/perl5/DBI.pm line
> 1666.
Does your MySQL installation support the InnoDB backend?
It should, but maybe the package is horribly broken - how can I check?
syslog says:
Aug 21 10:56:09 jesus mysqld_safe[21295]: started
Aug 21 10:56:09 jesus m
InnoDB is enabled according to config file and syslog.
That's another problem. If you have installed that module on your system,
then rename /opt/slimserver/CPAN/YAML to be sure SlimServer is using your
version.
Done. That gives
2006-08-21 13:21:18.7398 Use of uninitialized value in concatena
Did you compile DBD & cie. yourself?
No, I'm using the Debian testing packages.
Be sure you're using the same module version as are used/distributed with
Slimserver.
I'll double-check the versions, but it doesn't seem a likely cause
since it was working fine before with an identical perl in
Ok, so I've given up for now and just switched the squeezeboxen over
to an ad-hoc backup server.
Facts thus far:
I'm getting variations of the same error message:
Transactions not supported by database at /opt/slimserver/scanner.pl line 128.
Transactions not supported by database at /usr/lib/pe
just noticed this same problem myself after updating the mysql on debian
testing... don't know if it's a mysql issue or a slimserver issue.
Most likely a combination of the two - I've just opened a Debian bug
(no number yet) against mysql-server-5.0 on the Debian BTS in case
more people run in
I had the same problem. Fixed by reinstalling DBD::MySQL perl module.
Hmm, no change at all. What version of the module are you running?
C.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/beta
Has anyone filed a SlimServer bug on this?
I haven't. Usually Dan just solves any problem within 15 seconds of me
posting it :)
I reverted my mysql deb's to the 5.0.22-4 version that was in my cache and
everything is
working fine again.
You wouldn't happen to be running amd64 testing? Mine
The Debian bug has just been closed - apparently the last version had
introduced an ABI incompatibility. The package has not hit my mirror
yet but I'll report when I've tried it.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384047
C.
___
beta maili
The Debian bug has just been closed - apparently the last version had
introduced an ABI incompatibility.
The mysql packages currently in unstable (5.0.24-2) work again.
Warning: Current slimserver trunk revisons need a POE module that's
not in Debian yet which you'll have to build yourself.
C.
26 matches
Mail list logo
