Re: QCad

2023-09-15 Thread Onyeibo Oku
I would do exactly that (report bug against qcad component at 
bugzilla.redhat.com). Don't forget it's a Fedora product.

You are welcome all the same

Regards
Onyeibo (@twohot)

On September 14, 2023 5:59:31 PM GMT+01:00, ppadilcdx  
wrote:
>
>I'm new to Fedora so not sure if this is the correct list to send this 
>to or if I should open a bug report.
>
>Regards
>
>Pete

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Rawhide Nightlies crashes on reaching Graphical Environment

2023-09-15 Thread Onyeibo Oku
Hi Adam,

Check out the bug report at https://bugzilla.redhat.com/show_bug.cgi?id=2238995

I successfully booted Fedora Sway from https://getfedora.org on the same 
machine.  There has to be something off in recent composes.  The error occurs 
when anaconda wants to start a chronyd service. 

Hoping someone can replicate this on a similar machine or any other physical 
machine. 

Regards
Onyeibo (@twohot)


On September 14, 2023 5:50:54 PM GMT+01:00, Adam Williamson 
 wrote:
>On Thu, 2023-09-14 at 16:18 +0100, Onyeibo Oku wrote:
>> Greetings everyone
>> 
>> I am trying to install Fedora Server Edition using netinstall images from 
>> https://openqa.fedoraproject.org/nightlies.html
>> 
>> So far, I have not been successful. I tried the installation with 
>> yesterday's image and today's image (few minutes ago). I got the same error 
>> message as soon as it reaches graphical environment.
>> 
>> After few traceback lines, the last line says:
>> pyanaconda errors.ExitError: gnome_kiosk exited on signal 5
>> 

>It's probably hardware-specific. "Last Known Good" means the image
>passed all its tests in openQA, which tests in a virtual machine.
>
>Are you able to test on other hardware?
>
>Has anyone else encountered this problem trying to boot F39 or Rawhide
>installer images?
>
>Thanks folks!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Rawhide Nightlies crashes on reaching Graphical Environment

2023-09-14 Thread Onyeibo Oku
Greetings everyone

I am trying to install Fedora Server Edition using netinstall images from 
https://openqa.fedoraproject.org/nightlies.html

So far, I have not been successful. I tried the installation with yesterday's 
image and today's image (few minutes ago). I got the same error message as soon 
as it reaches graphical environment.

I used images from the "Last Known Good" (green) column in the "Server boot" 
table/section.

After few traceback lines, the last line says:
pyanaconda errors.ExitError: gnome_kiosk exited on signal 5

That was surprising. The box is a Dell Optiplex 3050 though.

I tried exporting a comprehensive report but the box has no internet yet. I 
might be able to fire off nmcli if I can get a shell.

I am open to ideas as I suspect this is peculiar. Otherwise those images won't 
be on the "Last Known Good" column.

Regards
Onyeibo (@twohot)___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: DNF 5 Test Week starts today!

2023-08-11 Thread Onyeibo Oku

Yes! This is something I'd like to do, considering that DNF5 frustrated me last
week.  Do we get badges for this one?


On Fri Aug 11, 2023 at 4:26 AM WAT, Sumantro Mukherjee wrote:
> Hey Folks,
>
> DNF 5 landed in rawhide sometime back and has now been taken off F39
> schedule. DNF 5 awaits testing and feedback before it can be
> considered stable for Fedora users. DNF and Fedora Quality are hosting
> a week-long testing period from Friday, August 11th through Thursday,
> August 17th.
>
> The wiki[0] contains all information and the results can be submitted
> by the test days app[1]
>
>
> [0] http://fedoraproject.org/wiki/Test_Day:2023-08-11_Fedora_39_DNF_5
> [1] https://testdays.fedoraproject.org/events/163
>
> Happy Testing!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Not seeing "check" in dnf5

2023-07-25 Thread Onyeibo Oku
On Tue, 25 Jul 2023 17:59:46 +0100
Onyeibo Oku  wrote:

> On Mon, 24 Jul 2023 08:17:27 -0700
> stan via test  wrote:
> 
> > On Mon, 24 Jul 2023 08:54:56 +0100
> > Onyeibo Oku  wrote:
> >   
> > > Any ideas?
> > 
> > 
> > Then I would run a 
> > dnf --distro-sync
> > to ensure that everything is at the latest available version and
> > remove all the older versions.
> 
> 
> Apart from the Kernel Panics,. it appears something went wrong while
> updating Python.

dnf ls --installed | grep python3

tells me I have the recent Python3 (and Python3-libs, Python3-tkinter)
with copies of py3.11 (as Python3.11-libs, Python3.11-tkinter etc) on
the list. This should be fine since the packages bear different names

However, when I run:
dnf update

I get conflicts as exemplified in my previous reply.  The update path
goes on to involve python3.11-libs when it should not.  Somehow python3,
python3-libs, and python3-tkinter picks up both 3.12 and 3.11 while
processing the update. The two packages share something in common and
dnf is confused.


I can remove the older Python via:
dnf remove python3.11-libs 

It pulls sudo-python-plugin and python-setuptools-wheel for removal as
well.  How safe is that?

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Not seeing "check" in dnf5

2023-07-25 Thread Onyeibo Oku
On Mon, 24 Jul 2023 08:17:27 -0700
stan via test  wrote:

> On Mon, 24 Jul 2023 08:54:56 +0100
> Onyeibo Oku  wrote:
> 
> > Any ideas?  
> 
> 
> Then I would run a 
> dnf --distro-sync
> to ensure that everything is at the latest available version and
> remove all the older versions.  

dnf distro-sync
Updating and loading repositories:
 Fedora - Rawhide - Developmental packages for the next Fedora release
   100% |  22.3 KiB/s |
42.3 KiB |  00m02s Repositories loaded. Problem 1: cannot install both
python3-3.11.3-2.fc39.x86_64 and python3-3.12.0~b4-1.fc39.x86_64
  - cannot install the best update candidate for package
python3.11-3.11.4-2.fc39.x86_64
  - cannot install the best update candidate for package
python3-3.12.0~b4-1.fc39.x86_64 Problem 2: cannot install both
python3-libs-3.11.3-2.fc39.x86_64 and
python3-libs-3.12.0~b4-1.fc39.x86_64
  - cannot install the best update candidate for package
python3.11-libs-3.11.4-2.fc39.x86_64
  - cannot install the best update candidate for package
python3-libs-3.12.0~b4-1.fc39.x86_64 Problem 3: cannot install both
python3-tkinter-3.11.3-2.fc39.x86_64 and
python3-tkinter-3.12.0~b4-1.fc39.x86_64
  - cannot install the best update candidate for package
python3.11-tkinter-3.11.4-2.fc39.x86_64
  - cannot install the best update candidate for package
python3-tkinter-3.12.0~b4-1.fc39.x86_64

Apart from the Kernel Panics,. it appears something went wrong while
updating Python.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Not seeing "check" in dnf5

2023-07-24 Thread Onyeibo Oku
Greetings

I am getting kernel panics after recent updates.  Strangely, lots of
things are also broken (e.g. Python 3.12 getting mixed up with 3.11,
virtual environments, etc.).  I suspect the update did not conclude
properly because dnf5 tends to stop midway when it encounters an issue.

So, I ran a "dnf check".

What do you know?  "check" command appears to be absent in dnf5. I
think my local repo (RPMs) are in a bad state.  I am running Rawhide.

Any ideas?

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Last known Good for Rawhide (Server Edition) -- Not Good

2022-12-11 Thread Onyeibo Oku
On Sat, 10 Dec 2022 08:51:14 -0800
Adam Williamson  wrote:

> On Sat, 2022-12-10 at 12:01 +0100, Onyeibo Oku wrote:
> > On Sat, 10 Dec 2022 11:47:39 +0100
> > Frantisek Zatloukal  wrote:
> >   
> > > o/ ,
> > > 
> > > Please note that "last known good" for rawhide nightlies actually
> > > means that it installs to VM, not via usb.  
> > 
> > Interesting.  That should be explicit on the page then.  Some people
> > still run server editions outside the cloud.  
> 
> It is.
> 
> "This is not as strong an indication of quality as official Alpha or
> Beta status, but at least indicates that the image successfully boots,
> completes a system installation, and boots to the installed system, in
> a straightforward virtual machine configuration."
> 
> That's right there at the top of the page.

How did I miss that? 


> > > Just to be sure, did you create the usb media via Fedora Media
> > > Writer? 
> > 
> > Kinda saw this coming.  Short Answer:  NO
> > I used Rufus and never had issues with that prior to this image.
> > The last Server edition I tried in November worked.  
> 
> Please try with straight dd or Fedora Media Writer. We can't be sure
> how any other tool writes images or if it's causing the problem.


So I did.  I created the USB with Fedora Media Writer and it worked!
I am sending this mail from the box.  I now have added respect for
Fedora Media Writer, more than ever before.  I always ran to Rufus in
the past.

On that note,  I tender my apologies to the QA team for my baseless
complaints.  It is was all good.

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Last known Good for Rawhide (Server Edition) -- Not Good

2022-12-10 Thread Onyeibo Oku
On Sat, 10 Dec 2022 11:47:39 +0100
Frantisek Zatloukal  wrote:

> o/ ,
> 
> Please note that "last known good" for rawhide nightlies actually
> means that it installs to VM, not via usb.

Interesting.  That should be explicit on the page then.  Some people
still run server editions outside the cloud.

> Just to be sure, did you create the usb media via Fedora Media Writer?
> 

Kinda saw this coming.  Short Answer:  NO
I used Rufus and never had issues with that prior to this image.
The last Server edition I tried in November worked.


Thanks for the heads-up

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Last known Good for Rawhide (Server Edition) -- Not Good

2022-12-10 Thread Onyeibo Oku
Good Morning,

I'd like to bring something to attention.  I just downloaded Server
Boot Media (Netinstall) from:
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20221209.n.0/compose/Server/x86_64/iso/Fedora-Server-netinst-x86_64-Rawhide-20221209.n.0.iso

I made a USB boot disk out of that and it failed to boot.

Here is what I get after choosing to install at the GRUB Menu:

error: ../../grub-core/fs/fshelp.c:257:file '/images/pxeboot/vmlinuz'
not found
error: ../../grub-core/loader/i386/efi/linux.c:258:you need to load the
kernel first.

Press any key to continue ...


The ISO was registered as "last known good". This can't be good.

Which one really works?

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Cannot reach Bugzilla

2022-11-12 Thread Onyeibo Oku
Greetings everyone,

Is it just me or is Bugzilla offline?  I have been trying that site for the past
2 hours.  What's happening?

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Something is not right (Fc37-Rawhide)

2022-02-27 Thread Onyeibo Oku

I eventually reinstalled from latest nightly image and the following issue
disappeared:

On Sat Feb 26, 2022 at 2:08 PM WAT, Onyeibo Oku wrote:
> Hi,
>
> All of a sudden I am getting the following out put for every package i
> update with dnf:
>
> 2022-02-25T20:51:14+0100 INFO /sbin/ldconfig: /lib64/libnss_compat.so.2
> is not a symbolic link
> /sbin/ldconfig: /lib64/libutil.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libresolv.so.2 is not a symbolic link
> /sbin/ldconfig: /lib64/libnss_dns.so.2 is not a symbolic link
> /sbin/ldconfig: /lib64/libthread_db.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libanl.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libdl.so.2 is not a symbolic link
> /sbin/ldconfig: /lib64/librt.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libmvec.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libm.so.6 is not a symbolic link
> /sbin/ldconfig: /lib64/libc.so.6 is not a symbolic link
> /sbin/ldconfig: /lib64/libc_malloc_debug.so.0 is not a symbolic link
> /sbin/ldconfig: /lib64/libpthread.so.0 is not a symbolic link
> /sbin/ldconfig: /lib64/libBrokenLocale.so.1 is not a symbolic link
> /sbin/ldconfig: /lib64/libnss_files.so.2 is not a symbolic link
>
> Is anyone else seeing this?  Most of those messages point to
> glibc-2.35.9000-5.fc37.x86_64.  I have tried reinstalling
> glibc-2.35.9000-5.fc37.x86_64.  The output persists.  Any ideas?
>

I got glibc-2.35.9000-6.fc37.x86_64 instead.  Perhaps that fixed it.
Strangely I am unable to install Firefox after the fresh installation.

Output:
---
Fedora rawhide openh264 (From Cisco) - x86_64
155 kB/s | 1.6 kB 00:00
GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-rawhide-x86_64
(0x5323552A) is already installed
The GPG keys listed for the "Fedora rawhide openh264 (From Cisco) - x86_64"
repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing
package is: mozilla-openh264-2.1.1-3.fc36.x86_64
 GPG Keys are configured as:
 file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-rawhide-x86_64
 Public key for openh264-2.1.1-3.fc36.x86_64.rpm is not installed. Failing
 package is: openh264-2.1.1-3.fc36.x86_64
  GPG Keys are configured as:
  file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-rawhide-x86_64
  Error: GPG check FAILED

Is it safe to add --nogpgcheck dnf parameter for this installation? 
Otherwise, the keys are out of sync.

Regards
Onyeibo

___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Something is not right (Fc37-Rawhide)

2022-02-26 Thread Onyeibo Oku
Hi,

All of a sudden I am getting the following out put for every package i
update with dnf:

2022-02-25T20:51:14+0100 INFO /sbin/ldconfig: /lib64/libnss_compat.so.2
is not a symbolic link
/sbin/ldconfig: /lib64/libutil.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libresolv.so.2 is not a symbolic link
/sbin/ldconfig: /lib64/libnss_dns.so.2 is not a symbolic link
/sbin/ldconfig: /lib64/libthread_db.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libanl.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libdl.so.2 is not a symbolic link
/sbin/ldconfig: /lib64/librt.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libmvec.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libm.so.6 is not a symbolic link
/sbin/ldconfig: /lib64/libc.so.6 is not a symbolic link
/sbin/ldconfig: /lib64/libc_malloc_debug.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libpthread.so.0 is not a symbolic link
/sbin/ldconfig: /lib64/libBrokenLocale.so.1 is not a symbolic link
/sbin/ldconfig: /lib64/libnss_files.so.2 is not a symbolic link

Is anyone else seeing this?  Most of those messages point to
glibc-2.35.9000-5.fc37.x86_64.  I have tried reinstalling
glibc-2.35.9000-5.fc37.x86_64.  The output persists.  Any ideas?

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: tty broken after "latest" upgrade

2021-04-25 Thread Onyeibo Oku
You beat me to it.

I can confirm your observation.  I was set to post the draft below:

I updated my Rawhide 24-hours ago.  Since then, I lost textual output.
I can see the GRUB menu and the Plymouth screen.  After those, no texts
show up any more -- only the blinking cursor remains.  I can tell that
there is activity on the machine because the cursor keeps moving around
(changing lines like it is printing out stuff, only I can't see any
texts).  Some commands execute as expected (without visuals, that is).
For example, "clear" sends the cursor back to the top-left corner of
the screen; but I do not see the text while typing.  The phenomenon is
strange.

So, I went on to download the latest rawhide ISO
(Fedora-Server-dvd-x86_64-Rawhide-20210424.n.0.iso).   The installation
went fine (graphics and all).  However, after installing, I am back to
the same phenomena.  This behaviour implies that one or more recent
packages in rawhide repositories have bugs.  Has anyone experienced
this recently?  Perhaps I should investigate further.

Regards
Onyeibo


On Sun, 25 Apr 2021 21:38:59 + (UTC)
George R Goffe via test  wrote:

> Hi,
> 
> I ran a system upgrade late last night and at reboot noticed a major
> problem with tty (possibly).
> 
> I run this system with the multi-user target active, which means I
> get a text based invitation to login and have to start X manually.
> This is NOT a new change.
> 
> Instead of seeing text "printed" on the screen, I see nothing. It's
> like the text is invisible. This situation happens near the time of
> the font change for the various boot messages. After this change,
> nothing appears except for a blinking "text" cursor. This happens
> with and without the "nomodeset" boot command line operand present.
> All the ttys are affected so I doubt that it's an X problem. Hitting
> enter acts like I entered a blank userid. I visualize logging in and
> then starting X. This works and I get an X session, windowmaker in my
> case. ALL the other ttys behave the same... no characters appear
> except for the cursor. I don't see anything obvious in the output of
> "journalctl -x -b0".
> 
> This system is at the "latest" Fedora 35 (x86_64) upgrades installed.
> 
> I'm kinda lost as to just where this problem "lives". Any/all help,
> hints, tips, suggestions would be greatly appreciated.
> 
> Best regards,
> 
> George...
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
> Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Strange performance on Rawhide this morning (UTC+1)

2021-01-20 Thread Onyeibo Oku
Good morning,

After powering down my box to change power source, I attempted to boot
again.  I noticed that the process hangs after selecting Kernel.  For a
moment, I couldn't boot.

Then I chose the test kernel (5.10.5-200.fc33.x86_64) and it went well.
 I figured the kernel was the culprit so I ran an update.  I got the
 following:

Cleanup : btrfs-progs-5.9-1.fc34.x86_64 265/266
Cleanup : SDL2-2.0.12-4.fc33.x86_64 266/266
Running scriptlet: kernel-core-5.11.0-0.rc4.129.fc34.x86_64 266/266

sort: fflush failed: 'standard output': Broken pipe sort: write error
gzip: stdout: Broken pipe
gzip: stdout: Broken pipe
sort: write failed: 'standard output': Broken pipe
sort: write error

.

Huh?

Should I be worried?
Previous kernel was kernel-5.11.0-0.rc3.122.fc34.x86_64

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: heads up: nss 3.59 breaks firefox add-ons

2021-01-07 Thread Onyeibo Oku
Is this still active?  My Firefox plugins are getting disabled and I
cannot install new ones (they are reported as corrupt).  Is there a new
instance of this bug?

Regards
Onyeibo

On Fri Dec 18, 2020 at 5:30 PM WAT, Adam Williamson wrote:
> On Fri, 2020-12-18 at 07:33 -0700, James Szinger wrote:
> > On Tue, 15 Dec 2020 11:17:21 -0800
> > Kevin Fenzi  wrote:
> > 
> > > If you upgrade in f33 or rawhide to nss 3.59, all your firefox add-ons
> > > will stop working. Worse they will appear corrupted, so you will have
> > > to remove them and re-install them (after downgrading nss). 
> > > 
> > > For now, downgrade nss or avoid updating to it until things can get
> > > sorted out. 
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1908018
> > > 
> > > kevin
> > 
> > I see nss.x86_64 3.59.0-3.fc33 in today’s updates.  Is this fixed or
> > are there going to be a lot of unhappy Firefox users?
>
> It's fixed.
>
> >   The bug is still open.
>
> Because we still need to do something (or, rather, get Mozilla to do
> something) about the underlying situation.
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: Rawhide users: don't update to 20201208.n.0 packages (fprintd 1.90.6), console login and su are broken

2020-12-17 Thread Onyeibo Oku
So that's what's wrong with my Firefox addons.  Downgrading ...

--
Onyeibo


On Tue Dec 15, 2020 at 7:37 PM WAT, Adam Williamson wrote:
> On Tue, 2020-12-15 at 10:17 +0100, Onyeibo Oku wrote:
> > Update was a success!  Everything is running fine.
>
> Great. Now, don't update to nss 3.59.0 if you like your Firefox add-ons
> to work. :)
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: Rawhide users: don't update to 20201208.n.0 packages (fprintd 1.90.6), console login and su are broken

2020-12-15 Thread Onyeibo Oku
Update was a success!  Everything is running fine.

Much regards
Onyeibo

On Sun Dec 13, 2020 at 8:27 AM WAT, Adam Williamson wrote:
> On Sun, 2020-12-13 at 07:43 +0100, Onyeibo Oku wrote:
> > Greetings.
> > 
> > Looking to run an installation (and update perhaps).  Is it now safe?
> > 
> > Maybe:
> > sudo dnf update --exclude=fprintd 
> > 
> > Regards and thanks for the early warning.
>
> Hi Onyeibo! We had trouble getting a successful compose with the fixes
> for a bit, but one just got through today. openQA testing shows
> 20201212.n.0 has the glibc and fprintd bugs fixed and looks generally
> OK, there are some test failures that will need looking into but
> nothing super-critical. So as long as your mirror has synced to that
> compose you should be OK to install/update. If you want to be sure,
> wait another few hours first. The fixed versions are glibc-2.32.9000-
> 20.fc34 and fprintd-1.90.7-1.fc34 or higher (I think the compose got 8-
> 1.fc34).
>
> Thanks!
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: Rawhide users: don't update to 20201208.n.0 packages (fprintd 1.90.6), console login and su are broken

2020-12-12 Thread Onyeibo Oku

Greetings.

Looking to run an installation (and update perhaps).  Is it now safe?

Maybe:
sudo dnf update --exclude=fprintd 

Regards and thanks for the early warning.

Onyeibo


On Wed Dec 9, 2020 at 9:53 PM WAT, Adam Williamson wrote:
> On Wed, 2020-12-09 at 12:02 -0800, Adam Williamson wrote:
> > On Wed, 2020-12-09 at 10:34 -0800, Adam Williamson wrote:
> > > Hey folks!
> > > 
> > > Just a heads up that the most recent Rawhide compose (20201208.n.0)
> > > seems badly broken; console login doesn't work and 'su' segfaults. I
> > > think the most likely cause of these issues is the new glibc 2.32.9000-
> > > 19.fc34 build.
> > > 
> > > So if you're running Rawhide I'd recommend holding off on updating, and
> > > especially on updating glibc, if you didn't do it already. If you've
> > > updated glibc you may want to downgrade it (if you still have a root
> > > shell somewhere :>)
> > 
> > Still looking into this, but it seems kinda complex. Downgrading glibc
> > on my test VM didn't fix the issues. I thought sssd might be the
> > culprit, but downgrading that didn't help either.
> > 
> > It seems like the console login bug at least doesn't happen with a
> > minimal package install:
> > https://openqa.fedoraproject.org/tests/737305
> > passed, including console login as user and root, and I verified that
> > it used the packages from the 1208.n.0 compose. But it seems to
> > reliably happen on Server, Workstation and KDE installs. So it's
> > apparently caused by something present in those installs but not in
> > minimal...
> > 
> > Still looking into this, my advice for now is still not to upgrade past
> > the 1207.n.0 package state until it's figured out :)
>
> OK, further update: culprit seems to be fprintd. fprintd 1.90.6 is the
> bad version. A 1.90.7 build is done which should fix it:
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1656747
>
> A libfprint 1.90.6 is also done, not sure if that's also needed:
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1656771
>
> There were bug reports already that I hadn't found as I was looking for
> glibc bugs:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1905667
> https://bugzilla.redhat.com/show_bug.cgi?id=1905964
>
> so, skip fprintd 1.90.6!
> --
> Adam Williamson
> Fedora QA
> IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: Self-introduction: Onyeibo Oku

2020-08-09 Thread Onyeibo Oku
On Sun, 09 Aug 2020 19:10:29 +0200
Alessio  wrote:

> Welcome Onyeibo! 
> Are you the twohot helping on Ask Fedora?

Hi @alciregi

Yes sir! That's me.

Regards
@twohot 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Re: Getting dumps from coredumpctl

2020-08-08 Thread Onyeibo Oku
On Sat, 08 Aug 2020 12:58:36 +0800
Ian Kent  wrote:

> I don't think you need to change that behaviour.

You're right. I eventually extracted the core dump without touching
systemcd-coredump settings.

> Have a look at the man page for coredumpctl(1).

Actually, I only needed to set soft limits for ulimit.

Thanks for the cue.

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Getting dumps from coredumpctl

2020-08-07 Thread Onyeibo Oku

Greetings,

I am trying to supply core dump for a bug report.  The app segfaults and 
coredumpctl sees the entry.  However, the dump is not written to disk so 
there's nothing to attach to the report.  How do I change this behaviour?

Regards
Onyeibo
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Self-introduction: Onyeibo Oku

2020-08-05 Thread Onyeibo Oku
Hi,

I am stepping forward to contribute to the Fedora Community as
part of the Quality Assurance Team and its not for the love of badges.
I already report bugs at bugzilla.redhat.com.  Occasionally, I hang
around #fedora-qa at freenode ... mostly to confirm current observations
in Rawhide.  So, yes, Rawhide is my preferred Fedora-version because it
provides more challenges to fast-track my understanding of Linux.  I
like learning and computers make it exhilarating.

I am Nigerian. I studied architecture (houses etc.). There is more
about me on my Fedora wiki too
(https://fedoraproject.org/wiki/user:twohot). I hope to make new
friends here.

Regards to you all.

Onyeibo
twitter: @onyetwo
irc: t2hot or twohot
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org