My first suspicion, is that our upgade instructions were still trying to pulling in dev version (-d etc). For that, I apologise and we will not get caught again.
@ Julien For the screensaver options that is one for the boss to check up on. @all, don't leave this to Erick... Get a work around, and get it soon! I've cc'd this issue also to xubuntu dev people. As to if it will be accepted... who knows :) Regards, Phill. On 29 April 2013 21:51, Erick Brunzell <[email protected]> wrote: > On 04/29/2013 03:16 PM, Phill Whiteside wrote: > > Erick, > > > > quite possibly. I am aware of setting up time-outs to be extended for > > screen saver (I think that's the issue here), but no one has posted up > > a work-around, which is important be on 'old machines' section. If > > anyone has one and is not familiar with wiki pages, please email it to > > me and I'll add it. > > Filing a bug is vital, and will be looked at; but as 13.04 is already > > out in the wild., a work around is important. > > > > Thanks, > > > > Phill. > > > > > > > Hi Phill, > > Bug #966451 does not effect only older hardware. It effects all upgrades > ........... including those initiated using either "update-manager -d" > or "update-manager -d -c" during a dev cycle, and also upgrades that are > initiated by the software-updater (previously update-manager). > > An example of what happens: > > If you have either Lubuntu or Xubuntu Quantal installed and you get the > notice to upgrade to Raring, as you will unless you've chosen to never > upgrade, then when Xscreensaver activates (at 10 minutes if you're using > the default settings) during the upgrade you get this warning: > > "One or more running instances of xscreensaver or xlockmore have been > detected on this system. Because of incompatible library changes, the > upgrade of the GNU libc library will leave you unable to authenticate to > these programs. You should arrange for these programs to be restarted or > stopped before continuing this upgrade, to avoid locking your users out > of their current sessions." > > If you ignore it and click on Forward the upgrade completes > successfully, but if you freak out and click on the close button (X) in > the upper right hand corner the upgrade fails horribly resulting in a > borked system. > > So I think the release upgrader needs to look for xscreensaver (and > possibly xlockmore) and disable them before continuing with the > dist-upgrade. > > I think what I'll do is run a repeat test so apport can collect the > appropriate info and file a new bug where I can then call it a > release-upgrader bug. Then I can include two different work-arounds > along with instructions on how to reproduce the bug. And I'll mention > that it is actually a duplicate of that old bug report. > > Lance > > PS: This may take a couple of days because I'm trying to clean up some > storm damage. > -- https://wiki.ubuntu.com/phillw
_______________________________________________ Mailing list: https://launchpad.net/~xubuntu-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~xubuntu-dev More help : https://help.launchpad.net/ListHelp
