SolydXK 10 Testing [updated: 31-07-2019]

[tek10]

Check out the solution at this forum topic.

viewtopic.php?f=7&t=7577#p70491

[troypulk]

Check out the solution at this forum topic.

viewtopic.php?f=7&t=7577#p70491

Thanks, that did the trick.

[palimmo]

quick question:
would it be feasible to wait just a few weeks and integrate Xfce 4.14 in SolydX 10?
Xfce 4.14 will be released by mid-August. https://wiki.xfce.org/releng/4.14/roadmap
Some others distros, like MX, are going to do that before releasing their own new version based on Debian 10.

Since new releases of Xfce come out not really often, this chance to integrate it now would be nice

[ilu]

Xfce 4.14 hasn't made it into debian10, so that's a problem because SolydX is based on stable. XFCE 4.14pre1 hasn't even arrived in experimental yet. It will take more than a month and including it would need a lot of testing. The SolydX10 ISO is already very good so I would not postpone it.Depending on how things go XFCE 4.14 will arrive in testing sometime in autumn so you can always use SolydX-EE.

That being said, if you install and test the packages and tell us what needs a change, that would be great. There's probably a way to provide the packages for SolydX10. Is there anything dealbreaking included in 4.14?

[Arjen Balfoort]

I have updated the OP with a TODO list for when I get back from holidays

[ilu]

You've seen that I found the cause of the installer bug, right? It's a 30 sec change.

[Arjen Balfoort]

Yes, I have seen it. The break is still needed but has to be caught within an if-statement and the actual bug needs to be caught much earlier in the code.

[kurotsugi]

AFAIK that xfce bug won't get fixed soon. please correct me if I'm wrong. those are low level stuff and seems only intel guys could fix it. considering the workflow, it will takes quite amount of time until we fix it. I think you can drop this item from the initial release iso

EDIT : I mean that blinking cursor/blank screen issue which happened on xfce/lightdm

[Arjen Balfoort]

Ah, thanks, but I still have to find out if I can upgrade my HP Stream without rendering it useless.

If I can find out that a simple downgrade of lightdm would fix that issue, other users might find it useful as well. Of course, such a workaround is not for the ISO.

[kurotsugi]

the workaround is quite easy. simply press ctrl+alt+f1 and it should trigger the screen. after that, press ctrl+alt+f7 to return to our working screen. it is a well-known issue for most xfce user but they ignored it since the workaround is easy (sadly, that including me). well...most of debian user also ignored it. even the devs ignored it until someone mentioned it on the mailing list. no one seems bothered to file a bug report on upstream. IIRC it was on june, right before the release

[Arjen Balfoort]

That workaround does not work on my HP Stream. ctrl-alt-f7 always shows the black screen of death

[Arjen Balfoort]

I have updated the TODO list in the OP: viewtopic.php?f=78&t=7537&p=70116

There are a few that need proper configuration and no programming.
I could use some help with that. So, if you have some time and would like to help out with some of these things, please let me know.

[EDIT]
For most I have found cause and solution. Only the Chromium issue (asking for password) not.

[EDIT2]
It seems that purging gnome-keyring solves the keyring issue. Can anyone confirm that?

[ilu]

If you remove gnome-keyring chromium will save passwords in plain text. You don't want that. Also deinstalling doesn't help in the long run because some packages rely on gnome-keyring and will make the problem reappear. I've moved this to its own topic here: viewtopic.php?f=79&t=7585

[GGerson]

I am trying to install SolydK x64 on the hard disk, the ISO is revised with sha256 and the sum is correct, the USB recorded with Rufus 3.6 starts without problem, live all the programs work but when I want to install this image error appears.
How is it corrected?

[ilu]

It's a know bug with "localized install" boot option. Arjen did not get around to fix it (holiday time!). To avoided it either choose the first boot option or - if you boot into "localized" - manually choose language, timezone and keyboard. Double check it before you proceed. Automatic time zone selection doesn't work at the moment.

[Arjen Balfoort]

I have updated several packages (OP updated).
The changes for the Chromium issue needs to be tested and usb-creator/solydxk-welcome are more complicated than I thought but on their way.

[ilu]

About Solydxk-welcome: You could put all packages on one screen and move the explanation into tooltips. Or, even easier: make one long scrollable screen like modern mobile-first webpage layouts. Then one install button at the top and at the bottom, both doing the same. I don't fancy those everything-on-one-page layouts but in this case it makes sense.

Just an idea, it would make the programming part much easier.

[ilu]

I'm trying to boot the 190724 ISO in a VM, I checked the hash but I'm getting errors:

1. First boot option: Live system loads but starting installer updates and then hangs with a black screen. Sometimes an error message as attached shows up. And a lot of SquashFS errors.

SolydX10-190724b.png (2.15 KiB) Viewed 521 times

2. Second boot option: Live system boots but there's an error with the panel. The flag panel item doesn't show, sometimes silently, sometimes with error.

SolydX10-190724a.png (26.03 KiB) Viewed 521 times

Just to be ckear: This was online. Starting installer same result as above.

Edit: started option 1 offline and installer started. Option 2 same result. Maybe a regression in the updated version or during the update?
- Localization bug seems to be fixed.
- Offline installation went without problems.
- I did not check welcome because it did not look changed.
- Seahorse needs to be added.
- The login.keyring needs to be a "real" keyring file.

[Arjen Balfoort]

solydxk-welcome is fixed and uploaded: asking user to install selected packages when switching pages.

systemd decided to run live-installer-3-stop service when updating live-installer-3 and thus shutting down the system (and not finding squashfs). I removed the script and accompanying systemd service. It was just a nice to have and I don't have the time to debug.

I have to wait building new ISOs until it's less hot...system shuts down when I do.

[Arjen Balfoort]

I have released the RCs and updated the OP.

I have also included an upgrade script to upgrade solydxk-9 to solydxk-10.

Only the the gnome-keyring isssue is still open.
I still haven't figured out to generate a protected keyring at login without user input.