Lite 2.2 Beta Feedback

[mdavies5]

1. Set Calculator Hotkey to Galculator. I know it can be setup but setting it as default would be nice.
2. Make login screen lighter to fit in with default theme. Currently the black screen is not very welcoming.
3. Make default installation similar to Live ISO. My live ISO had panel at the bottom, welcome screen, wallpaper and attractive fonts. The full install had the panel at the top, no welcome screen, no wallpaper and spidery fonts. Booting the live ISO was impressive but I felt very disappointed when booting into the full install for the first time.

[Valtam]

3. Make default installation similar to Live ISO. My live ISO had panel at the bottom, welcome screen, wallpaper and attractive fonts. The full install had the panel at the top, no welcome screen, no wallpaper and spidery fonts. Booting the live ISO was impressive but I felt very disappointed when booting into the full install for the first time.

The default installation is exactly the same as the Live iso. You must have a corrupt image, or there is some other issue. Try an install in Virtualbox and see if you get the same result. First check the md5sum of the LL iso.

[mdavies5]

Jerry, I downloaded linux-lite-2.2-beta1-64bit.iso from Sourceforge. No MD5 sum is published. Also I do not use VirtualBox, I prefer to install on a spare partition. I have gone back to the Live ISO to see why it looks so polished compared to the full install. I have mentioned elsewhere about the indicator plug-in which is activated by default in the Live ISO, but the biggest change is in the fonts. The Live ISO defaults to Droid Sans 10 but this font is not installed in the full version which defaults so "sans".
I installed the Droid family of fonts via Synaptic and set Droid Sans 10 as the default. It is like I am now looking at a different system and it is fantastic. As you know this default feeds through to so many other areas and apps. I am a developer but not an install expert. Could it be anything to do with the error message and lockup just before the install ended. I reported this today and I have seen other posts with the same problem.
I can re-install on a spare partition to see if there are any changes.

[sysdrum]

I found the error is do to the build script when building a special location for the install.
So I have found that if you use a split /home(on another drive/part) it will break LL for some reason I avoid when testing to put LL on anything that does not have a inline "/" which means no spares or side by sides. Either a solo install or a virtualbox. as most installs for new users will happen in a single drive with only LL as the os there is no need to to build a side script rebuild syblic links to work with a non inline setup. if you want that do a inline and then move the /home afterwards to your new location and then update the fstab to the new  /home location.
Even if you run LL inline there will some times be an issue with the system and then the install fails and breaks the installer if you are not running it as the the only install.
That is just what I have found with both 2.0 and 2.2
But I don't think the issue is LL fault I have found that it is in the Xubuntu installer that LL uses to push the system to disk.
The glib error is the same on both. I would fix it if I knew the best way without breaking everything.
Anyway I have already submitted up the chain in Xubuntu the issue with the installer.

[Valtam]

Jerry, I downloaded linux-lite-2.2-beta1-64bit.iso from Sourceforge. No MD5 sum is published.

The md5sum is both on the Sourceforge (click the 'I' next to the 64bit iso) page and in the release announcement.

https://www.freecinema2022.gq/forums/index...pic=1143.0

[mdavies5]

Thanks Jerry,
I re-installed with 1 minor change. On the first install I did not follow the advice on the welcome screen and run Updates. I couldn't you couldn't run updates on a system running in memory and I didn't think it would affect the install. On the second install I did run updates then ran install. Now the install looked exactly the same as the Live ISO. Also during the second install I checked "Download updates while installing". After completion I ran updates again and it downloaded the same 16 updates it did during the Live ISO demo. My only suggestion now is the calculator hotkey I mentioned earlier. I look forward to the final release.
Once again, congratulations and I hope my little faux pas did not cause you too much work.
Mike

[Wirezfree]

I found the error is do to the build script when building a special location for the install.
So I have found that if you use a split /home(on another drive/part) it will break LL for some reason I avoid when testing to put LL on anything that does not have a inline "/" which means no spares or side by sides.

Hi Sysdrum,

On my first couple of installs, on a Laptop I just allowed it to do it's own thing(It was all new to me then) and use whole disk.
Subsequently I then got a little more adventurous and put things in different partitions

Code:

/
/swap
/home
/data

Since then I have now installed it on 2 PC's which have 2 drives

Code:

SDA=
/
/swap
SDB =
/home
/data
/vms
/backup

I have had some anomalies with Whisker menu items moving & showing/not showing and installing Themes/Icons.?
Could this be related to your comments, I'm not an expert, I'm learning.
I split the drives/partitions because I understood it had some benefits & simplified backups & restores.

Dave

[gold_finger]

Thanks Jerry,
I re-installed with 1 minor change. On the first install I did not follow the advice on the welcome screen and run Updates. I couldn't you couldn't run updates on a system running in memory and I didn't think it would affect the install. On the second install I did run updates then ran install. Now the install looked exactly the same as the Live ISO.

Don't know what happened on first installation, but something unusual went wrong with it.  Running updates in the live environment is not something you need to do to have a proper installation.  As a matter of fact, I'm surprised that doing so didn't freeze up your live system.  I'm guessing that you have a decent amount of RAM on the system for it to have even been able to handle updating the live environment.

I found the error is do to the build script when building a special location for the install.
So I have found that if you use a split /home(on another drive/part) it will break LL for some reason I avoid when testing to put LL on anything that does not have a inline "/" which means no spares or side by sides.

I'm really curious about this.  Can you elaborate a bit more on what you mean by "it will break LL" when doing anything other than standard install?  Did you have boot problems?  Or were there other types of problems and what were they?  Did problems only occur when trying to set-up a dual-boot system?  Also, what "glib" error were you referring to?

I have done several installs of LL2.0 on my own systems and those of a few other people.  On my own, I don't use a separate /home, but always use a separate data partition.  Sometimes I set up that partition after install and sometimes during install.  I think (but am not 100% sure) that I have setup separate /home for others.  Also, I'd hazard a guess that I have probably guided a few people through installations with separate /home here on the forum.  From my experiences, there has never been any problem setting up and using a non-standard partition arrangement.

When I get around to installing beta LL2.2, I'm going to set-up separate /home and maybe one or two other partitions during install just to see if I can duplicate any problems like you are describing.  I'd imagine that some (probably small) percentage of people who have installed LL2.0 before did do so with a separate /home partition; yet yours is the first post I've seen stating that doing so causes a failure.  I get the impression that you are not a "newbie", which makes me want to look deeper into this to see if there is a situation that I may not have known about or run into myself.  If you can recall (close to) exact details of an example installation that failed, I'd like to attempt install in same manner to see what happens.

I have had some anomalies with Whisker menu items moving & showing/not showing and installing Themes/Icons.?
Could this be related to your comments, I'm not an expert, I'm learning.

I kind of doubt that problems are due to separate partitions, but as stated above I'm planning to run a few install tests to see if I can duplicate problems described above.  Can you please specify what Whisker menu problems you've run into and what extra themes you may have installed?  I'll see if I can duplicate your problems on the test runs also.

[Wirezfree]

[quote author=Wirezfree link=topic=1153.msg7123#msg7123 date=1416140559]
I have had some anomalies with Whisker menu items moving & showing/not showing and installing Themes/Icons.?
Could this be related to your comments, I'm not an expert, I'm learning.

I kind of doubt that problems are due to separate partitions, but as stated above I'm planning to run a few install tests to see if I can duplicate problems described above.  Can you please specify what Whisker menu problems you've run into and what extra themes you may have installed?  I'll see if I can duplicate your problems on the test runs also.
[/quote]
Hi gold_finger,

Some previous posts/screenshot:

Menu Labels edited it menu editor, but they do not show correctly in the menu.!!
https://www.freecinema2022.gq/forums/index...97#msg6197

Icons Theme error:
https://www.freecinema2022.gq/forums/index...00#msg6200

I get this "warning" in the Icons selector, running the suggested command does not fix it.!!


Dave

[gold_finger]

I get this "warning" in the Icons selector, running the suggested command does not fix it.!!

Hi Wirezfree,

Just run that command again with "sudo" and it should work.

Code:

sudo gtk-update-icon-cache ...

(substitute correct rest of command in place of "...")

If doesn't work, go to /usr/share/icons/Win7-icons and delete the cache file that is there now.  (Need to be root when doing that.)  Then run command again.

Will check out your Whisker menu stuff a bit later.