balloon wrote:james c:
I am worried about a message"Puppy Linux Discussi(on Forum)" in the screenshot lower left. __{{emoticon}}__

I might rarely be found over on the Puppy forum....... __{{emoticon}}__

Successful install on the ever-trusty Athlon XP box. No troubles.

Unable to get past populating dev during boot on live USB or frugal install.

For those of you having boot issues, could you try the various F cheats and disable fbsplash in F7 ie chosse safe

Just to add, it is very likely an issue with the kernel. What exactly is causing boot failure is what we need to find out so we can get it fixed.

On my PIII it boots fine.

Could those that managed to get it to boot ok, please post any bugs you find and see how deaves-desktop works.
I'm sure Dave knows best and whether I have included all the parts on the cd or not.

afab4 - what if you leave it for a while? (I mean a long while)

Is there a list of what the new desktop-session is supposed to contain. I see the menu tweaks...

anticapitalista wrote:afab4 - what if you leave it for a while? (I mean a long while)

I booted the USB again and after 10 minutes it had not advanced past populating dev.
This rig has always booted any debian based distro without problems.

I was able to successfully boot using the F7 SAFE boot option. I am posting from a2 Live.
I still am unable to connect wirelessly using ceni as in a1. I have to use WICD.

Md5sum checked downloaded Iso. Burned on Memorex -CDR at about 8.2 speed since 10 was the lowest I could select on this laptop burner.
I am just booting on this unit to make sure no problems with cd boot on my P3 units.
Found a funny glitch running live in JWM-ROX DESKTOP. I was just switching desktops from Menu>Desktop>Alternate Desktops to test things a little before I posted. Anyhows. Running inxi -Fxz in JWM-roxdesktop. When you get to the Capital F in inxi -F. It prompts for root
password to open rox filer. I typed in"root" and still after rox-filer opened. I typed in F again and was brought back to the password prompt.

Somebody else test this running live or installed to make sure this is not just isolated to me. I will be booting this cd later on my P3 IBM laptop and maybe install to the Amrel P4 Laptop. After pulling them off the moth ball shelf. This laptop has 2gig of ram so inxi report on ram?
Touchpad Tap, Webcam, Sound, Screen Resolution, Wifi, All work just fine running live on the Compaq CQ 57.
Like I said. Just more of a test for my older laptops to make sure the cd came out OK before I post anything
on those latops, concerning any problems maybe later.

CD looks OK to me.

Edit: JWM is buggy even posting in this edit. Hittng the Capital f key prompts for root password even in browser during this reply edit.
I tested this across all JWM possible Desktops. So bug may be JWM specific. Capital t also causes this behavior also.

.

anticapitalista wrote:Could those that managed to get it to boot ok, please post any bugs you find and see how deaves-desktop works. I'm sure Dave knows best and whether I have included all the parts on the cd or not.

dolphin_oracle wrote:Is there a list of what the new desktop-session is supposed to contain. I see the menu tweaks...

yes I suppose there should be __{{emoticon}}__
I will try to write down a list here of what is changed / what needs testing....
Item | Needs Testing | What it does.
desktop-session | YES | Builds and starts a session based on a selected window manager, it should always run so nothing special needs to take place for testing.
etc/desktop-session/desktop-session.conf | YES | Enables and disables some items when desktop-session is run, please test various options in the file. I recommend copying this file to a test user under ~/.desktop-session/desktop-session.conf to avoid problems for every user if missconfigured. Specifically test:
-if the session seems to fail to load items (like spacefm desktop) increase the STARTUP_DELAY.
-Enable LOAD_CONKY option to see if it will load different conkys from ~/.conky based on the session. Conky rc's must be named like WM-conkyrc... so for icewm, icewm-conkyrc.
-Enable XDG_AUTOSTART to see if applications that comply with xdg autostart will actually autostart.
-Change SCREEN_BLANK_TIME to see if the screen blanking time actually changes (either in this config or through set-screen-blank which should now alter)
etc/desktop-session/startup | YES | Allows normal text file startup just the same as adding items to ~/.xinitrc used to do. Please try adding startup items here for all users and window managers as well as in ~/.desktop-session/startup for per user multiple window manager startup.
etc/file_compare | If Adventurous | Will replace user files with global equivelents if the global equivelent is newer (package update). The user can be protected from this by the existance of the ~/.desktop-session/user-protect file. If the file is there no user files will be replaced by their global counter parts, if it is not there the files should be updated.
etc/desktop-defaults.conf | YES | when OVERRIDE_SESSION_FM is enabled the chosen default file manager should override the file manager that the session uses. For example if you install thunar and set it as your choosen file manager, but use space-icewm, then when enabled thunar should open rather than spacefm (as is the case with it disabled) also test per user in ~/.desktop-session/desktop-defaults.conf.
usr/share/desktop-menu/.* | YES | System wide menus. (what the user menu is symlinked to) this allows for the updating of the menu when an application is installed. You can test this by installing an application that has a menu entry (which should be permanent) or adding a manual entry to the menu files (should show in the user menu, but will be lost on logout / login / application install)
usr/share/desktop-menu/templates |TEST ONLY IF VERY ADVENTUROUS | Template files for the menu building of various window managers. If one is very adventurous, one could take a look at the default three as examples and try to make their own template for another window manager. Example: openbox.
usr/share/desktop-session/wm-menus | YES | No editing required, should be updated when a new window manager is installed or desktop-session-update-wm-menus is run.
usr/share/desktop-session/first-run-script. | YES | Runs certain items only on the users first run. Typically only good for showing help docs, or setting up a session. Can test by adding something to the script, then adding a new user and logging in as the user, or removing ~/.desktop-session/finished-first-run.
usr/local/bin/add-desktop | YES | See if this adds items to the application menu, spacefm desktop, and personal menu.
usr/local/bin/add-start | YES | See if this still adds startup items to the appropriate window manager startup. Will be adding desktop-session startup in the future.
usr/local/bin/add-key | YES | See if this still adds key bindings to the appropriate window manager key file.
usr/local/bin/change-*-theme.sh |NO | Should be removed
usr/local/bin/desktop-defaults-run | YES | Should be tested anyway every time you use quite a few menu / toolbar / cc items. But please try from command line as well if you would like.
usr/local/bin/desktop-defaults-set | YES | Sets the sessions default applications (and some mime types as well). Please try changing the defaults with this and see if the menu /toolbar / CC / desktop-defaults-run reflects these changes.
usr/local/bin/desktop-menu* | YES | Install a new application and see if it automatically appears in the menu, if it follows the gtk theme, and if ambitious adding another template file from above works. There are a bunch new options with this, so it is probably best to glance at desktop-menu --help.
usr/local/bin/desktop-session* | SHOULD NOT NEED MANUAL TESTING | Just use the new setup, if anything quirky please note it. You should not need to play with the desktop-session * scripts with the exception of the above configs, desktop-session-exit(.sh), and desktop-session-wallpaper (which is the backend of wallpaper.py).
usr/local/bin/edit-wm-settings. | YES | Please run and see if it opens the appropriate config files for the window manager that is running.
usr/local/bin/exitantix.sh | NO |Could be removed.
usr/local/bin/remove-desktop | YES | After adding a desktop item through add-desktop try removing it through remove-desktop. It does not appear to have a menu entry (probably my fault) but should receive one.
usr/local/bin/set-screen-blank | YES | See if it changes the screen blank time locally using ~/.desktop-session/desktop-session.conf as stated above
usr/local/bin/speedtest-cli | SURE | Not sure how this was included, I guess I packaged it accidentally but it is a neat script to test your internet speed. Would not be hurt if it is removed or kept either way __{{emoticon}}__
usr/local/bin/update-default-desktop | MAYBE | Not sure this has any use anymore but not sure if it does..... desktop-session should auto detect that a window manager was installed and update slim accordingly.
usr/local/bin/wallpaper.py | YES | Make sure it is functioning with the new desktop-session stuff.
usr/local/bin/xfce4-session-logout | UHM....| UHM.... New to me, why is it existing but xfce not installed????
usr/local/bin/antiX-FileManager.sh | NO | Save to remove, replaced by desktop-defaults-run
usr/local/bin/conky-toggle.sh | SURE | Should be replaced by desktop-session.conf but it is setup to start conky via the startup file rather than desktop-session....

Other than that as noted the new menu stuff has been noticed, so it appears self explanatory, but if there was one thing to single out it is try the 'menu -> desktop -> alternate desktops' submenu. Another 2 are the 'menu -> desktop' submenu and along with that the 'menu -> personal' submenu. There are some other things but I think that they are covered a touch by the above scripts / programs testing.

Note: the control center still seems hard coded, so the chosen defaults I do not think will show in the control center.
There is probably some stuff that I missed at the moment, this should be a good start for now. I hope that anything I missed shows up when I review this later, or through the testing.

P.S. @ anti,
I noticed that the desktop-session appears to be an slightly older version than my most recent. Probably because it was the last fully packaged version rather than the latest version that I think I emailed separately. Anyway, I will make a full package but keep it open for any improvements that are seen from this testing.

rokytnji wrote: Edit: JWM is buggy even posting in this edit. Hittng the Capital f key prompts for root password even in browser during this reply edit.
I tested this across all JWM possible Desktops. So bug may be JWM specific. Capital t also causes this behavior also.

Probably a misstype on the keys file.
It sounds like my suggested key mappings, but with a bit of a twist as I use"super + f" for file manager and"super + Shift + f" for root file manager. Likewise for terminal"super + t" and root terminal"super + shift + t". It appears as though the super portion is missing for the root options and thus asking for a root password when pressing"shift + f" and"shift + t"

boot/syslinux/syslinux.msg
bootscreen instructions state"type one of the label names below..."
Actually, user must select one (not type)

LiveUSB session bootscreen
previously available Fkey desktop chooser is absent. A bug, or is this the new planned design?
Instead, a Console dimensions chooser is provided. Bug: upon choosing, and saving... at next boot, the saved choice is ignored and"S 800x600" is displayed as bootscreen value

LiveUSB session, init console message"root persistence recently enabled... choose root password"
^----- something buggy here
When user types password string and presses enter, looooooooong delay...
(user wonders whether it is hung, wonders"was my 'enter' keypress not recognized?")
...followed by msg"AUTHORIZATION TOKEN MANIPULATION ERROR" then immediately followed by prompt to choose user password

Control Centre }} Configure mouse
previously reported bug still exists.
Each time the dialog is opened, current value for acceleration is ignored and, instead, a value of"5" is preselected

Control Centre }} antix wallpaper chooser
intermittent (seems consistently repeatable only under iceWM): the control to select stretch/fit/center is absent

change-default-desktop script
(seems to work as expected, but) when"Restart Xwindows" is clicked, a dialog msg is displayed stating"The default dm was not found. Will search for any..."

Under fluxbox, at start of session the conky output seems to be blinking/flickering.
Changed to sans font and saved config --} flicker ceases. Reverted to gentium font and saved config --} flicker does not return. I'm stumped.

JWM menu } Applications
the submenu is initially empty
logout/in to fix? Run 'update menus' to fix?

shutdown
previously reported bug still exists.
after X session ends, must login as root to 'halt'.
Also, (also not new) error message complaining something about"another instance of persist-save is already running..."

skidoo wrote: Control Centre }} antix wallpaper chooser
intermittent (seems consistently repeatable only under iceWM): the control to select stretch/fit/center is absent

Could you elaborate on this one?
Is it only with icewm... or is it fine with icewm but not rox-icewm and space-icewm?
I am confused by the"(seems consistently repeatable only under iceWM)" bit.
What is repeatable? the missing stretch/fit/center option?

the stretch/fit/center option should only exist when running a blank window manager. (icewm / fluxbox / jwm) as with any of the variants (rox-* space-*) the wallpaper setting options does not have the ability to stretch/fit/center, only scale.

re: wallpaper chooser

In this alpha (LiveUSB session) no bootscreen DE chooser is displayed, so during first boot I found myself in iceWM, w egg-shaped globe displayed in the background image. When I entered Control Centre to fix, the control for stretch/fit/center was absent. I logged out, chose fluxbox at SLiM menu and relaunched the wallpaper chooser. The stretch/fit/center control WAS now displayed. Hmm, headscratcher. Logged out and then into a JWM session ~~ as with iceWM, the same control was absent. Ran update-default-desktop script and rebooted. Rechecked, the control was still displayed during fluxbox session, was still NOT displayed when I rechecked from an IceWM session, and now (on 2nd attempt) WAS displayed during JWM session.

Is that more clear? What I'm reporting should be consistently repeatable from within an iceWM session and, per my testing, happens inconsistently (I'm stumped as to why) under other WMs.

the stretch/fit/center option should only exist when running a blank window manager. (icewm / fluxbox / jwm) as with any of the variants

Yep,"blank fluxbox" session is what I chose and found it working. The others, I didn't think to check every SLiM:F1 permutation

Maybe"wallpaper chooser" should be conditionally suppressed from the menu (if"non blank WM session")
otherwise, from user POV... dat fing is busted.