[Ubuntugnome-qa] [Beta 1 Testing] Your Help Is Needed
Tim
darkxst at fastmail.fm
Thu Feb 25 06:44:29 UTC 2016
On 25/02/16 16:28, Ali/amjjawad wrote:
> Hi all,
>
> On Thu, Feb 25, 2016 at 7:47 AM, Tim <darkxst at fastmail.fm <mailto:darkxst at fastmail.fm>> wrote:
>
> Images are re-spinning again now, hopefully upower/ubiquity is all fixed on them.
>
>
> Yes, it is gone.
>
> However, I see other bugs:
> http://iso.qa.ubuntu.com/qatracker/milestones/357/builds
>
> @Lance
> I can't see this bug:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
>
> On Oracle VirualBox and I'm chatting with Tim at the moment on #ubuntu-release
plymouth is pretty broken atm from what I can tell, since it is not displaying properly it is causing a bunch of the reported bugs. Not sure it
can be fixed in time for beta 1 though.
>
> I am loving this channel. Very useful at such times ;)
>
>
>
>
> On 24/02/16 16:33, Tim wrote:
> > Ali's respins failed. I retried and now there is a i386 image with the upower bug fix, no amd64 image as yet though
> >
> > On 24/02/16 12:26, Ali/amjjawad wrote:
> >> Hi Lance and everyone else,
> >>
> >> On Wed, Feb 24, 2016 at 10:53 AM, Erick Brunzell <lbsolost at yahoo.com <mailto:lbsolost at yahoo.com> <mailto:lbsolost at yahoo.com
> <mailto:lbsolost at yahoo.com>>> wrote:
> >>
> >> On 02/23/2016 05:42 PM, Ali/amjjawad wrote:
> >>> Hi,
> >>>
> >>> I am extremely busy in real life and not in good health (back/neck problems) as I'm about to shift houses for the 4th or 5th times
> in 2
> >>> years so you can imagine :)
> >>>
> >>> However, living in pain is easier than NOT supporting Ubuntu GNOME. So please, do help us!
> >>>
> >>> http://iso.qa.ubuntu.com/qatracker/milestones/357/builds
> >>>
> >>> In case you don't know:
> >>> https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
> >>>
> >>> Please test and as you may know, report any bug to the ISO Tracker.
> >>>
> >>> If you're new to all this, here is a good place to start from:
> >>> https://wiki.ubuntu.com/UbuntuGNOME/Testing
> >>>
> >>> The release notes:
> >>> https://wiki.ubuntu.com/XenialXerus/Beta1/UbuntuGNOME
> >>>
> >>> Please update the release notes whenever possible.
> >>>
> >>> I see, yet again, no one is paying attention to i386 so I'll do my best in that area.
> >> I am paying attention.
> >>
> >>
> >> Yes, I know you do ;)
> >>
> >>
> >>
> >> As you can see from my posted results both the amd64 and i386 images are basically junk! I also encountered an installation failure but
> >> ubuntu-bug ubiquity complained about a lack of space on the live DVD, how is that possible?
> >>
> >> Anyway I'll try and reproduce that behavior as time allows but right now I'm trying to recover from a failed Trusty -> Xenial
> upgrade so I
> >> can file a release-upgrader bug the smart way. If that fails I'll have to file a must less useful bug report the dumb way.
> >>
> >>
> >> These are mess so here is what I was doing just a while ago:
> >>
> >> <amjjawad> Oh, launchpad is down/broken for some reason! why such things happen during before a milestone release?!
> >> <amjjawad> infinity, I'm testing Ubuntu GNOME images and these are true mess :(
> >> <infinity> amjjawad: Security updates, it's only temporary.
> >> <wxl> amjjawad: for more info on that, see #canonical-sysadmin.
> >> <amjjawad> infinity, the installation is broken and I just can't install anything.
> >> <amjjawad> wxl, "Technically, this is a 503 error and has been caused by our database being temporarily offline. " but thanks for your
> advice :)
> >> <wxl> amjjawad: have you read the topic at #canonical-sysadmin?
> >> <amjjawad> infinity, http://iso.qa.ubuntu.com/qatracker/milestones/357/builds/113126/testcases
> >> <infinity> amjjawad: I'm staying far away from this milestone.
> >> <wxl> amjjawad: you can see who is involved in this milestone here https://wiki.ubuntu.com/XenialXerus/ReleaseTaskSignup
> >> <wxl> suffice it to say, flocculant is asleep
> >> <wxl> i believe stgraber is handling the canonical side of things, right, infinity ?
> >> <amjjawad> Thanks infinity and wxl then guess I have to wait as there is nothing I can do except confirming bugs.
> >> <wxl> amjjawad: you do know you can get around the upower bug by running off ac power only, right?
> >> <infinity> The upower bug was fixed, it just needs a respin.
> >> <amjjawad> wxl, I'm testing on Oracle VB. Not sure if that applies to that as well?!
> >> <infinity> (which stgraber left up to the flavours to do themselves)
> >> <wxl> infinity: not true. flocculant triggered a respin and doesn't work.
> >> <amjjawad> how can I know if I have access to do a re-spin or not? can I try?
> >> <amjjawad> to be more accurate: a re-spin for Ubuntu GNOME images only.
> >> <wxl> amjjawad: if you have an SSO login to the tracker and you have an LP membership that allows you to, for example, mark images as
> ready,
> >> you can select a rebuild in the same area there
> >> <wxl> amjjawad: just click the right images, and click rebuild. bvut again, i don't think it will help
> >> <amjjawad> wxl, indeed, I have access to mark them as ready but never touched "re-spin" as of now.
> >> <infinity> lftp cdimage.ubuntu.com:/ubuntu-gnome/daily-live/20160222.2> cat xenial-desktop-amd64.manifest | grep upower
> >> <wxl> amjjawad: and yes, if your host has a battery, remove the battery and run off of AC power and your vm will work.
> >> <infinity> gir1.2-upowerglib-1.0 0.99.4-1
> >> <infinity> The latest version isn't in those images.
> >> <infinity> libupower-glib3:amd64 0.99.4-1
> >> <infinity> upower 0.99.4-1
> >> <infinity> wxl: It'll help.
> >> <wxl> infinity: it isn't in the xubuntu images?
> >> * anpok has quit (Ping timeout: 252 seconds)
> >> <amjjawad> darkxst, I'll give it a go!
> >> * kenvandine has quit (Ping timeout: 240 seconds)
> >> <infinity> wxl: The newest xubuntu images have -2.
> >> <cyphermox> infinity: jibel asked me to do a respin earlier too, but I have no access to do that
> >> <wxl> infinity: --which is supposedly the fix, right?
> >> <infinity> wxl: Yes.
> >> <wxl> infinity: and what i'm telling you is dear flocculant already tested it and no dice.
> >> <wxl> infinity: i know the bug is fix released. i know pitti worked on it. it didn't fix it.
> >> <amjjawad> is there any harm if one does a re-spin?!
> >> <infinity> Or the testing methodology was lacking. I'm happy to believe both.
> >> <infinity> amjjawad: No.
> >> <wxl> amjjawad: no harm. go for it.
> >> <amjjawad> perfect :D
> >> <wxl> amjjawad: if you DO get success, let me know.
> >> <amjjawad> wxl, sure ;)
> >> <wxl> amjjawad: but the battery removal WILL work.
> >> <amjjawad> request a rebuild, right?
> >> <wxl> do it
> >> <amjjawad> wxl, yes, will remember the battery thing.
> >>
> >>
> >>
> >>
> >> Lance
> >>
> >> PS: the 20160221 amd64 image had far fewer problems so something got borked in the last 48 hours or so.
> >>
> >>
> >>
> >> I requested a re-build:
> >> http://iso.qa.ubuntu.com/qatracker/milestones/357/builds
> >>
> >>
> >>
> >>> Thank you!
> >>>
> >>> --
> >>> Remember: "All of us are smarter than any one of us."
> >>>
> >>> Best Regards,
> >>> Ali/amjjawad <https://wiki.ubuntu.com/amjjawad>
> >>>
> >>>
> >>>
> >>
> >> I will keep you posted/updated (hopefully) in any case whether all is good or not.
> >>
> >> Thanks!
> >>
> >>
> >> --
> >> Remember: "All of us are smarter than any one of us."
> >>
> >> Best Regards,
> >> Ali/amjjawad <https://wiki.ubuntu.com/amjjawad>
> >>
> >>
> >>
> >
>
>
> --
> Ubuntu-GNOME mailing list
> Ubuntu-GNOME at lists.ubuntu.com <mailto:Ubuntu-GNOME at lists.ubuntu.com>
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome
>
>
>
>
> --
> Remember: "All of us are smarter than any one of us."
>
> Best Regards,
> Ali/amjjawad <https://wiki.ubuntu.com/amjjawad>
>
>
>
More information about the Ubuntu-GNOME
mailing list