Re: dnf segfaulting on 32-bit

2017-07-21 Thread Felix Miata
Samuel Sieb composed on 2017-07-21 21:40 (UTC-0700): > Felix Miata wrote: >> My BRC searches have a habit of either timing out or producing mostly >> summaries >> with what to me is incomprehensible babble, and that only after great >> difficulty >> finding one or more Fedora versions to actual

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Samuel Sieb
On 07/21/2017 05:44 PM, Felix Miata wrote: My BRC searches have a habit of either timing out or producing mostly summaries with what to me is incomprehensible babble, and that only after great difficulty finding one or more Fedora versions to actually select from its endless version select list.

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Adam Williamson
On Sat, 2017-07-22 at 06:04 +0800, Ed Greshko wrote: > On 07/22/17 05:47, Adam Williamson wrote: > > On Fri, 2017-07-21 at 13:41 -0700, Samuel Sieb wrote: > > > On 07/21/2017 12:28 PM, Adam Williamson wrote: > > > > Note that apparently manually rebuilding the DB can result in it having > > > > the

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Adam Williamson
On Fri, 2017-07-21 at 20:16 -0400, Felix Miata wrote: > Adam Williamson composed on 2017-07-21 12:28 (UTC-0700): > > > On Fri, 2017-07-21 at 08:54 -0700, Samuel Sieb wrote: > > > Felix Miata wrote: > > ... > > > > Jul 21 02:18:18 gx280 kernel: dnf[5909]: segfault at ae738a35 ip > > > > b573218e

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Felix Miata
Samuel Sieb composed on 2017-07-21 13:43 (UTC-0700): > Felix Miata wrote: >> On F26 as soon as I sent my OP I rebooted, did dnf clean all, rpm >> --rebuilddb, >> dnf update, dnf distro-sync, then shut down and went to bed. Distro-sync did >> nothing but remove 225 packages. >> I did similar wit

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Felix Miata
Adam Williamson composed on 2017-07-21 12:28 (UTC-0700): > On Fri, 2017-07-21 at 08:54 -0700, Samuel Sieb wrote: >> Felix Miata wrote: ... >> > Jul 21 02:18:18 gx280 kernel: dnf[5909]: segfault at ae738a35 ip b573218e >> > sp >> > bfe6d090 error 4 in libdb-5.3.so (deleted)[b55f2000+1d1000] >> T

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Ed Greshko
On 07/22/17 05:47, Adam Williamson wrote: > On Fri, 2017-07-21 at 13:41 -0700, Samuel Sieb wrote: >> On 07/21/2017 12:28 PM, Adam Williamson wrote: >>> Note that apparently manually rebuilding the DB can result in it having >>> the wrong SELinux label, so you should also run this afterwards (as >>>

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Adam Williamson
On Fri, 2017-07-21 at 13:41 -0700, Samuel Sieb wrote: > On 07/21/2017 12:28 PM, Adam Williamson wrote: > > Note that apparently manually rebuilding the DB can result in it having > > the wrong SELinux label, so you should also run this afterwards (as > > root): > > > > restorecon -RFv /var/lib/rpm

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Samuel Sieb
On 07/21/2017 10:16 AM, Felix Miata wrote: On F26 as soon as I sent my OP I rebooted, did dnf clean all, rpm --rebuilddb, dnf update, dnf distro-sync, then shut down and went to bed. Distro-sync did nothing but remove 225 packages. I did similar with F25, but don't remember particulars other tha

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Samuel Sieb
On 07/21/2017 12:28 PM, Adam Williamson wrote: Note that apparently manually rebuilding the DB can result in it having the wrong SELinux label, so you should also run this afterwards (as root): restorecon -RFv /var/lib/rpm Interesting, I haven't seen that mentioned anywhere else in any of the

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Adam Williamson
On Fri, 2017-07-21 at 08:54 -0700, Samuel Sieb wrote: > On 07/21/2017 12:12 AM, Felix Miata wrote: > > On Intel P4 host gx280 with 2GB RAM tonight this happened about 2/3 through > > dnf > > update on both F25 and F26 installations, F26 the latter. Last package's > > scriptlet completed for udisks

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Felix Miata
Samuel Sieb composed on 2017-07-21 08:54 (UTC-0700): > Felix Miata wrote: >> On Intel P4 host gx280 with 2GB RAM tonight this happened about 2/3 through >> dnf >> update on both F25 and F26 installations, F26 the latter. Last package's >> scriptlet completed for udisks2. Last line before segfaul

Re: dnf segfaulting on 32-bit

2017-07-21 Thread Samuel Sieb
On 07/21/2017 12:12 AM, Felix Miata wrote: On Intel P4 host gx280 with 2GB RAM tonight this happened about 2/3 through dnf update on both F25 and F26 installations, F26 the latter. Last package's scriptlet completed for udisks2. Last line before segfault is upgrading gstreamer1-plugins-bad-free.

report on the Firefox / Electrolysis induced failures

2017-07-21 Thread R P Herrold
This came up in Fedora's most recent testing cycle, but the failure mode was not reliably reproducable, and so did not rise to the level of a blocker. I think I have some insight It looks like there is a missing SELinux ruleset problem, causing the hang ups in Firefox, but not all of them, fo

dnf segfaulting on 32-bit

2017-07-21 Thread Felix Miata
On Intel P4 host gx280 with 2GB RAM tonight this happened about 2/3 through dnf update on both F25 and F26 installations, F26 the latter. Last package's scriptlet completed for udisks2. Last line before segfault is upgrading gstreamer1-plugins-bad-free. Prior to 'dnf update' on both I had run 'dnf