World: r3wp

The SQLite group is broken ... I suspect a corrupt file on the server.

Symptoms: if you've recently re-installed AltME, then the program 
runs continuously, endlessly resyncing that group.


This happened before, and the workaround was to copy over a good 
copy of the 439.set file (thanks to Peter Wood for the good copy). 
But that no longer seems to work.


I am going to delete the group and set up a new one with the same 
name. The archive  of past postings will remain available here:
    http://www.rebol.org/aga-display-posts.r?post=r3wp439x1

Is anyone using AltMe from linux (like a recent Ubuntu)? I moved 
to linux for 90% of things but I can't run altme there, and rebol 
view crashes also. I didn't look into depth of why..

works here with ubuntu 10.10

Been using the Linux versions as much as possible (which isn't always 
the case) since they exist

It works fairly well on recent Ubuntu, although the fonts are better 
on some other distros

File sharing still suffers greatly from the daylight savings bug, 
though

To work around that, you can run AltME on WINE, although that is 
slower

altme 1.2.25 works ok with debian 6 and ubuntu 10.10 for me. fonts 
are so-so, but at least usable

Been using it on Ubuntu 8.04 and now 10.04 (AltMe versions 1.1.29 
and currently 1.2.21)

I had to install libstdc++5_3.3.6-18_i386.deb for rebol to work

(At least, I think it was that one.  I still have it sitting in my 
home directory)

That was for the ancient 1.1.29

The font issue could be fixed easily if AltME would allow to specify 
font name or path to font in its settings.

What drives me nuts with AltME is, that when it's reconnecting, that 
it switches display and don't just stay at the group and message 
where I am. It resets the list etc.

Because of this switch all messages are set to read... really dumb.

Agreed.

Altme works on my linux now ! Great

Possible bug in Altme: I connect to world rebol3 then click on world 
name on the top-left corner that opens a combobox to select other 
worlds which I connected previously, but non-existing worlds anymore. 
When I choose one of them Altme tries to connect and fails, then 
when I click on Return to World button altme get closed immediately 
without showing the message "Disconnecting".

hmm... I just experienced AltME in the Rebol 3 world with a memory 
leak and eating CPU. It was upward of 150 MB RAM usage, and then 
I killed the process.

That memory use is unfortunately normal after running a while

Got a few error message in the terminal session that AltME always 
opens (and leaves open after quitting.):


altme(6254,0xa038c620) malloc: *** mmap(size=3021340672) failed (error 
code=12)
*** error: can't allocate region
*** set a breakpoint in 
malloc_error_break to debug

It seems to try to allocate a 3 GB file or area there. It's not surprising 
that fails, but it's surprising it would try that

Did it crash or were they just operational messages?

Just operational messages - four of them in total. It's happenned 
a couple of times before but is very infrequent.

I've made the Red group [web-public] a few weeks ago, but I still 
don't see it been exported: http://www.rebol.org/aga-index.r, does 
it require some admin validation?

Sunanda has to ok it

to make sure it's not an error

but I guess there might be some issue with hosting on rebol.org a 
group which is competition with Rebol??

Thanks Doc -- I had not noticed that Red is flagged [web-public].

Theoretically, [web-public] gets you:

....automatically published on REBOL.net (though that appears to 
no longer be updated):
       http://www.rebol.net/altweb/rebol3/index.html

....and published on REBOL.org at the discretion of the Library Team. 
       http://www.rebol.org/aga-groups-index.r?world=r3wp


As Graham suggests there may be some issues, especially as REBOL.org 
is funded by RT. I'll ask the Library team to discuss.

The Red group is now published on REBOL.org -- my thanks to Library 
Team for the discussion:
    http://www.rebol.org/aga-display-posts.r?post=r3wp840x0

Thanks to the Library Team.

In another AltME world I'm participating in, AltME file sharing is 
used to share 103 files, all of which I have downloaded. Every time 
I (re)connect, AltME offers me to re-download 63 of them. Irrespective 
of whether I re-download or not, I'm again offered this each and 
every time I connect.

I faintly recall having heard of this problem before, anyone has 
a clue what's going on (and more importantly: how to fix it?). I'm 
using AltME 1.2.25 on Linux.

It may be the daylight savings time bug, where that changeover makes 
all the file times apparently an hour off. This is because the AltME 
file time handling isn't converted to UTC.

Any known fixes/workarounds?

Once a year, go through and redownload every file in the world. And 
be careful to not repost those files, which is hard to do because 
of UI problems.

I deleted and re-downloaded all files several times already, so I 
guess it's a different problem.

No, this is the yearly daylight savings time problem. It's just not 
fixable. Redownloading doesn't help

Thanks. Sucks.

As usual, the non-Windows versions such more. In the winter, you 
can use AltME Linux version. In the summertime, you can switch to 
running the Windows version on WINE...

suck more

That only fixes the redownloading, though. (For every changed file 
you want to fetch, you have to download all of them.) In the winter, 
files that you created in the summer will have the wrong status. 
In the summer, files that you created in any winter will have the 
wrong status

Gotta love it

Can't you just set the PCs all to GMT?

You can, if you want to make your problems worse

It will corrupt all other programs that use time. It won't fix AltME's 
problems. We've tried

Is there a way to change the port that an altme world uses?

I think so, you can specify it as a command-line parameter. But port 
numbers are limited, IIRC.

there is a config.txt file in same folder with altme.exe but I'm 
not sure if there is an option like that.
there is a line "host-port: 5400" but this is for client.