Posts made by TrialAndError

I guess there is only a small minority who tests the working branch. In the moment a new version is tested after release when users do an upgrade.

So I think of something like the Debian or Libreoffice release plan. This would mean for FOG in the time of writing that a very stable product like FOG 1.4 (at least for my use case) would receive further bug fixing without any new features.

Of course that would slow down the development of new features. But FOG is a software “for production” by nature so stabilty is very important not only for me I guess.

FOG is a great peace of software! Many people appreciate it a lot and use it for “production” - and many of us often are in a hurry. Sometime bugs in software like FOG are a big problem in my daily work. So I would kindly suggest a different release plan for FOG.

As I know there are two branches now. One for experimenting (dev) and one for releasing (master). The new release is prepared in the working branch where bugs get fixed and new features are introduced from the dev branch (which brings new bugs necessarily).

Therefore I suggest introducing a third branch (stable, production). In stable only very small bugs get fixed with a high probability that no new bugs are introduced. A problem that cannot be addressed without the risk of causing new problems could be published as a known issue. So as a user I could decide if I wanted or needed the new features - bug fixings in the master/working branch.

@george1421
It is Ubuntu 16.04. (But I cannot answer more questions because I downgraded to 1.4.3 )

I would like to suggest publishing “known issues” like that obiviously known multicast problem. It would be VERY helpful.

@george1421

This is worth to be reported as an bug! As you know a solution already you should report it.

(For me only switching back to the apache php engine helped. Otherwise the web inteface did not respond, even not with normal imaging.)

@trialanderror said in FOG 1.5.2.11 GUI bug in Host and Group Membership Edit:

If I tick a group/host (to remove a host from a group) and click “Remove” not the ticked but another (random) goup/host will be removed.

Obviously my English is too bad. Another try:

For example:

1. Navigate to Group Mangement Edit: ‘groupname’
2. Tick off (?) a host of your choice.
3. Left click on ‘Remove’
4. Wonder

FOG 1.5.2.20

Not fixed yet.

Sorry, cannot check that.

1.5.2.11 had a critical bug while imaging (kernel panic, something with init not present). I pulled 1.5.2.11 only to check whether the problem was still there. I immediately returned to 1.5.2.2

If I tick a group/host (to remove a host from a group) and click “Remove” not the ticked but another (random) goup/host will be removed.

Hi,

i have got machines on different subnets. Everything (except WOL) works perfectly over my router (ipfire).

Therefore I directly connected the FOG server to the second subnet with a second interface: still no WOL on the second subnet.
Then I activated and installed the plugin wolbroadcast: still no WOL on the second subnet (broadcast address configured in /etc/network/interfaces).

Any Tips? Help is appriciated.

@tom-elliott
I pulled the working branch: FIXED!
Thanks.

It is the “latest” working branch pulled yesterday. Nevertheless FOG shows 1.5.2 as the version number.

FOG 1.5.2 (working-branch)

If I click on a host name in order to edit the host actually the host directly above of the chosen host ist openend for editing.

FOG 1.5.2 (working-branch)

Tested - works as expected. Thanks.

@tom-elliott
FOG 1.5.0

Tested it, same behaviour with the other buttons in the group menu:

hitting “Update display resolution” changes the values under module configuration and auto-logout time too,
hitting “Update auto-logout time” changes the values under module configuration and display resolution too.

I will test the working branch as soon as possible.

@tom-elliott
Yes.

Tested it again. Seconds before.

@tom-elliott

What do you mean, overwrites the default values?

overwrites WITH the default values

They should be in their own form elements though, so if you update the modules, it doesn’t update the display/autologout.

It DOES. - I tested several times. This is definitely no feature …

FOG 1.5.0
Firefox 59.0.2

Clicking on the button “Group Management - Update module configurations - Update” updates screen resolution and auto logout too (overwrites with the default values).

client 0.11.15

Power events are executed on many (most?) machines again! Thank you for your work!

On the “fresh” Win10 1709 switching to “Delayed” worked. The client 0.11.14 executed power events again.

On the “old” Win 10 - no change. And either with 0.11.14 nor the nightly any events a logged in the Windows log files around the time the error is logged in fog.log.

Same problem again: 1135

I started with a fresh Windows 10 1709. In the beginning the client initiated power events successfully.
Then I started to rebuild my machine. And now after a couple of apps like browsers, java, office (no regedit or something comparable at all) the reboot fails again.

--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 17.02.2018 23:45 Client-Info Client Version: 0.11.14
 17.02.2018 23:45 Client-Info Client OS:      Windows
 17.02.2018 23:45 Client-Info Server Version: 1.5.0-RC-13
 17.02.2018 23:45 Middleware::Response Success
 17.02.2018 23:45 HostnameChanger Checking Hostname
 17.02.2018 23:45 HostnameChanger Hostname is correct
 17.02.2018 23:45 HostnameChanger Attempting to join domain
 17.02.2018 23:46 HostnameChanger Success, code =  0
 17.02.2018 23:46 Power Creating shutdown request
 17.02.2018 23:46 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 17.02.2018 23:46 Bus Emmiting message on channel: Power
 17.02.2018 23:46 Power Attempt 1/6 to shutdown computer
 17.02.2018 23:46 Power --> API call returned 0, will re-attempt in 5 minutes```