Comments you submit will be routed for moderation. If you have an account, please log in first.

Opened 3 years ago

Closed 2 years ago

#361 closed bug (invalid)

YAm 2.8 beta, build from 20.12.12 on AROS. Open window problem.

Reported by: nikos Owned by:
Priority: undecided Milestone:
Component: undefined Version: nightly build
Severity: major Keywords:
Cc: marust OS Platform:
Blocked By: Blocking:
Release Notes:


If I click button for new mail or try to open the config window nothing happens.
I ran sashimi and got a message:

Could not create object of Groub.mui
Couldn-t find Group.mui

With YAM 2.7 it works as normal. Is there something new with 2.8 that AROS does
not support, group.mui class ?

Attachments (2)

log.txt (22.9 KB) - added by anonymous 3 years ago.
debug.txt (636.8 KB) - added by nikos 3 years ago.

Download all attachments as: .zip

Change History (20)

comment:1 Changed 3 years ago by damato

To investigate the problem it would be helpful if you could run some tests with the debug version of YAM 2.8-dev. Please download it at the same position like the normal nightly builds. In addition, please start yam from the command-line and use the following command before starting yam:

setenv yamdebug stdout gui

then catch the debug output when trying to open the config window and upload it here for investigation.

Changed 3 years ago by anonymous

comment:2 Changed 3 years ago by anonymous

Added debug. Hope it helps.

comment:3 Changed 3 years ago by damato

Thanks. However, the debug info doesn't contain all the info we need for identifying the problem. Can you please elaborate at which point you tried to open the config window? In addition please try to recreate the log with the following setenv call before starting yam:

setenv yamdebug stdout all @all

This will generate a huge debug log so be prepared that YAM will get quite slow. Please outline at which point you tried to open the config window and where the error window was presented to you.

comment:4 Changed 3 years ago by damato

BTW: please also create yourself an account here on the webpage so that we don't have to moderate each post and you get directly notified of changes of the tickets.

comment:5 Changed 3 years ago by nikos


The last debug you got from me I got using sashimi.

Using the command " setenv yamdebug stdout all @all " works and I got a lot of debug output from shell, but it is not saved to anywhere ?

comment:6 Changed 3 years ago by damato

Well, if you use "stdout" in the setenv call it will be put on the command-line. If you omit it it will be sent to the serial line, thus you can catch it via sashimi. However, you can also add "file:ram:debug.txt" and it will save the debug output to "ram:debug.txt". See for more information on how to create proper debug output using the "yamdebug" environment variable.

comment:7 Changed 3 years ago by damato

  • Reporter changed from nik-tom@… to nikos

comment:8 Changed 3 years ago by nikos

For some strange reason debug.txt is created but file size is 0k so nothing is saved to it.

This is my command line before running YAM.debug

setenv yamdebug stdout all @all file:ram:debug.txt

comment:9 Changed 3 years ago by damato

Well, you have to remove "stdout" from the command-line if you want to save to a file. Then it should work.

Changed 3 years ago by nikos

comment:10 Changed 3 years ago by nikos

Hope this one can help you detecting the problem.

comment:11 Changed 3 years ago by damato

Thanks for the log file. However, it is hard to identify the problem from that file. Can you please tell me at which line you tried to open the config window? All I can see is that you seem to have tried to open a write window and that failed also. However, no definite error message is written. Can you please also state which AROS version you are running?

comment:12 Changed 3 years ago by nikos

I'm using latest AROS night build. I also the autour of AspireOS distribution. As said with YAM 2.7 I have no problem at all. The problem with 2.8 is that even if the program is running and seams normal, nothing happen if I try to write mail pushing the new button and if I try to push the config. button AROS freeze. It is little difficult to debug pressing config button since AROS freeze. I could always save the debug to sys: but don't know if it will catch the error ?

comment:13 Changed 3 years ago by damato

Hmm. unfortunatley I don't have a working AROS installation myself. Is there still a VirtualBox version of Icaros or something like that? That would allow me to debug things on my own. Apart from that we really rely on you supplying enough information to debug why YAM 2.8 doesn't seem to work with the latest versions of AROS.

comment:14 Changed 3 years ago by nikos

I have little experience with virtualbox, but know that many run Icaros desktop with it.
If you have a Linux installation running it is quite easy to run AROS hosted.

Here is a direct link to the AROS, Linux hosted version

comment:15 Changed 3 years ago by damato

I am on OSX here, so I would prefer to have an OSX hosted version somehow (e.g. using virtualbox)

comment:16 Changed 3 years ago by damato

  • Cc marust added

adding Matthias Rustler to this ticket as he is partly our AROS maintainer and has already done quite some changes. Matthias, can you please elaborate if YAM 2.8+ really doesn't work on AROS anymore?

comment:17 Changed 3 years ago by damato

Matthias? Are you listening?

comment:18 Changed 2 years ago by damato

  • Resolution set to invalid
  • Status changed from new to closed

After discussion with thore it seems that the reason for that issue have been caused by a bug in the MUI/zune implementation of AROS. However, in the meantime the issue seem to be fixed and thus the ticket shouldn't be valid anymore.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Matthias Rustler(Subscriber)
  • Nikolaos Tomatsidis(Reporter, Participant)