Re: Upgrading from F30 to F31 beta reboot issue

2019-10-07 Thread alan
> On 10/7/19 12:33 PM, a...@clueserver.org wrote: >> If you use --allowerasing, the upgrade transaction works, but since >> that >> flag does not get passed to the upgrade after the reboot, the process >> fails because it tries to upgrade those packages and they were never >> downloaded. > >

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-07 Thread alan
> On 10/7/19 10:51 AM, Alan wrote: >> On Sat, 2019-10-05 at 13:37 +, Rodger Etz wrote: >>> Thanks, Chris! I did so, but reboot did not create a debugdata dir. >>> Therefore I have uploaded the dnf logs. >>> >>> From what I have seen so far,

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-07 Thread Alan
On Sat, 2019-10-05 at 13:37 +, Rodger Etz wrote: > Thanks, Chris! I did so, but reboot did not create a debugdata dir. > Therefore I have uploaded the dnf logs. > > From what I have seen so far, it still seems the best option to > modify system-upgrade so it safes the transaction before

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-03 Thread alan
> Yes, thanks. > > As the pkgs are pretty fundamental I prefer to keep them. I had bad > eyperiences in the past with this approach. Before I go through dependency > hell, I'd rather quickly reinstall the whole box. > And as it is just a system-upgrade test for me, it can wait. It still needs

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-03 Thread Alan
On Wed, 2019-10-02 at 19:13 -0600, Chris Murphy wrote: > On Wed, Oct 2, 2019 at 6:14 PM Samuel Sieb wrote: > > On 10/2/19 5:03 PM, Chris Murphy wrote: > > > On Wed, Oct 2, 2019 at 3:32 PM Alan wrote: > > > > This is interesting... I am going to do a heavy

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-03 Thread Alan
On Wed, 2019-10-02 at 18:03 -0600, Chris Murphy wrote: > On Wed, Oct 2, 2019 at 3:32 PM Alan wrote: > > This is interesting... I am going to do a heavy clean of the > > packages > > and try again. > > > > Oct 02 11:22:23 daimajin dnf[1390]: Transaction Summary

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-03 Thread Alan
On Wed, 2019-10-02 at 14:34 -0700, Samuel Sieb wrote: > On 10/2/19 2:31 PM, Alan wrote: > > Oct 02 11:23:19 daimajin dnf[1390]: Error opening file for > > checksum: > > /var/lib/dnf/system-upgrade/fedora- > > 3589ee8a7ee1691d/packages/plasma- > > desktop-5.16.4-1

Re: Upgrading from F30 to F31 beta reboot issue

2019-10-02 Thread Alan
On Wed, 2019-10-02 at 15:23 -0600, Chris Murphy wrote: > On Wed, Oct 2, 2019 at 3:02 PM Alan wrote: > > I have a laptop (Lenovo W540) running Fedora 30. I have preped it > > for > > upgrade using dnf. > > > > I get to the reboot step is where it gets interes

Upgrading from F30 to F31 beta reboot issue

2019-10-02 Thread Alan
I have a laptop (Lenovo W540) running Fedora 30. I have preped it for upgrade using dnf. I get to the reboot step is where it gets interesting. I reboot and enter the drive password. It goes into the install, says it is preparing and then before it installs anything, it reboots. Any idea what

How do I get a change made to a getfedora.org web page?

2019-04-08 Thread alan
The page https://getfedora.org/workstation/prerelease/ mentions using the fedora media writer to write ISOs to USB drives. It says you can download it using dnf, but it does not give the package name. The package name is "mediawriter". It would be nice it it actually said that next to where it

Re: Problems after upgrade from F29 to F30-beta [FIXED}

2019-04-08 Thread alan
> You should be able to uninstall them using dnf from the command line, > assuming you can get to a TTY. If you manually installed any (e.g. > dash2dock) check the git repository to see if it comes with a makefile > rule to uninstall the extension. I mention dash2dock specifically because > I

Re: Problems after upgrade from F29 to F30-beta

2019-04-08 Thread alan
> You kinda have to fix or mitigate those in order, because gnome-shell > could be crashing due to either a) or b); or even d) which are the > gnome-shell extensions. Maybe the easiest way to test that is to > create a new user on the cli, and attempt to login as that new user. I > think gnome

Re: Problems after upgrade from F29 to F30-beta

2019-04-08 Thread alan
> On Mon, Apr 8, 2019 at 10:55 AM wrote: >> >> >> I upgraded from Fedora 29 to Fedora 30 beta on my laptop. >> >> The system boots, asks for the drive password, and then brings up my >> login >> in GDM. I select my user account and then enter my password. The screen >> goes black and then goes

Re: Problems after upgrade from F29 to F30-beta

2019-04-08 Thread alan
> On Mon, 2019-04-08 at 09:54 -0700, a...@clueserver.org wrote: >> I upgraded from Fedora 29 to Fedora 30 beta on my laptop. >> >> The system boots, asks for the drive password, and then brings up my >> login >> in GDM. I select my user account and then enter my password. The screen >> goes

Problems after upgrade from F29 to F30-beta

2019-04-08 Thread alan
I upgraded from Fedora 29 to Fedora 30 beta on my laptop. The system boots, asks for the drive password, and then brings up my login in GDM. I select my user account and then enter my password. The screen goes black and then goes back to the gdm login screen. If I try XFCE, it just hangs.

Re: Please consider adding a QA test case for shutdown, which gives more time to see error mesages - i.e. uses "halt"

2019-01-12 Thread Alan Jenkins
Alan provided additional input for the proposed new shutdown test. I have updated the document and attached it. This test case (https://fedoraproject.org/wiki/QA:Testcase_base_shutdown/reboot) does not seem to be in the Base test matrix anymore. We should consider adding it back

Re: Please consider adding a QA test case for shutdown, which gives more time to see error mesages - i.e. uses "halt"

2019-01-11 Thread Alan Jenkins
of ext4, etc. One alternative approach might be to add a new, separate test case where you 1) use "halt" 2) have specific instructions about how to boot and check the `fsck` logs afterwards. Anyway, I should be able to attend the Monday meeting as suggested, so you'll see

Re: Please consider adding a QA test case for shutdown, which gives more time to see error mesages - i.e. uses "halt"

2019-01-11 Thread Alan Jenkins
On 11/01/2019, pmkel...@frontier.com wrote: > > On 1/11/19 7:26 AM, Alan Jenkins wrote: >> Hi QA people! >> >> In the past few years I've seen four shutdown bugs. The problem is that >> the screen turns off too quickly, so even if it shows error messages, most >

Please consider adding a QA test case for shutdown, which gives more time to see error mesages - i.e. uses "halt"

2019-01-11 Thread Alan Jenkins
a halt, reboot or shutdown operation, the system successfully boots without error. All expected disk partitions are cleanly mounted. Boot logs do not show any "fsck" (filesystem repair) operations, or "recovering journal" (ext3/4 journal recovery). Thanks for all the testing :-)

Introduction

2017-04-07 Thread Alan McGeoch
Hi everyone, I've used Fedora for a good long while, and i imagine i should have got involved a long time ago. I've started testing updates, and hope to get a bit more involved in other testing areas, and other areas of Fedora as time goes on. I've applied to join the QA group as well. You

Self-introduction: Alan Ernhart

2016-06-20 Thread Alan Ernhart
Hi, I'm Alan Ernhart and reside in the USA. I've a couple decades in software test automation, including performance testing at IBM and development of a Python framework for testing of REST APIs. I've used RHEL a fair amount in that, but Fedora's been my laptop machine for about 9 years. So I can

Re: My Fedora 15 beta experiences so far

2011-05-22 Thread Alan
On Fri, 2011-05-13 at 22:44 -0700, Adam Williamson wrote: On Sat, 2011-05-14 at 09:47 +0600, Angel wrote: If you click the network icon of the panel then Network Settings, that ´s the different thing (dumbed down to absolute worthlessness). yeah - it's so worthless you can only connect

My Fedora 15 beta experiences so far

2011-05-13 Thread alan
I have to admit, this is the most painful Fedora installation I have ever done. (And I have used them all.) The networking came up as IPv6 *only*. My router does not do IPv6 and my ISP (Qwest) does not know when their network ever will. In order to get it to work I had to hack files in