Using the repo as a whole looked fairly stable to me. However, I did no deliberate testing, just used it for a time.
WARNING: I do not recommend using only the lxpanel package from the repos. There have been various changes which will make it misbehave in the old environment.
NOTE: For a live distro with no internet, you can e.g. pre-cache the packages and have them installed by a script after startup, or rebuild the livecd with fixed packages. For a smaller footprint, try finding a build that works for you just after the fix was committed into the relevant branch.
Hope this helps.
p.s.: +1 on propagating the fix into the trusty repos, especially into the lubuntu trusty livecd.
As a workaround...
The Trusty repos of one or both of the following Lubuntu-dev PPA-s contain a/the fix for this issue for quite some time now: dev/staging https:/ /launchpad. net/~lubuntu- dev/+archive/ ubuntu/ staging dev/lubuntu- daily https:/ /launchpad. net/~lubuntu- dev/+archive/ ubuntu/ lubuntu- daily
- ppa:lubuntu-
- ppa:lubuntu-
Using the repo as a whole looked fairly stable to me. However, I did no deliberate testing, just used it for a time.
WARNING: I do not recommend using only the lxpanel package from the repos. There have been various changes which will make it misbehave in the old environment.
NOTE: For a live distro with no internet, you can e.g. pre-cache the packages and have them installed by a script after startup, or rebuild the livecd with fixed packages. For a smaller footprint, try finding a build that works for you just after the fix was committed into the relevant branch.
Hope this helps.
p.s.: +1 on propagating the fix into the trusty repos, especially into the lubuntu trusty livecd.