Re: EXTERNAL: Re: hundred percent cpu load

[Tony Nelson]

On 20-08-14 09:14:51, Wells, Roger K. via devel wrote:

On 8/14/20 8:45 AM, Przemek Klosowski via devel wrote:


So, what is kernel doing? what does your system log say? type  
'dmesg' or 'journalctl -e' and look at the end of the data.


The following repeats at the end of journalctl:
In the last second of the journal there are 14688 individual entries.

Aug 13 18:23:51 rwells-x280 kernel: Hardware name: LENOVO  
20KFCTO1WW/20KFCTO1WW, BIOS N20ET55W (1.40 ) 06/01/2020
Aug 13 18:23:51 rwells-x280 kernel: Workqueue: events_freezable  
ieee80211_restart_work [mac80211]
Aug 13 18:23:51 rwells-x280 kernel: RIP:  
0010:drv_sta_state+0x26e/0x3e0 [mac80211]
Aug 13 18:23:51 rwells-x280 kernel: Code: 0b 45 31 ed e9 44 fe ff ff  
48 8b 83 78 04 00 00 48 8d b3 98 04 00 00 48 c7 c7 80 46 f2 c0 48 85  
c0 48 0f 45 f0 e8 c9 bf 23 d2 <0f> 0b 41 bd fb ff ff ff e9 1b fe ff  
ff 65 8b 05 be fc 16 3f 89 c0
Aug 13 18:23:51 rwells-x280 systemd-journald[928]: Missed 44 kernel  
messages
Aug 13 18:23:51 rwells-x280 kernel:  iTCO_wdt mac80211  
iTCO_vendor_support snd_hda_intel irqbypass intel_rapl_msr  
snd_intel_dspcfg rapl snd_hda_codec libarc4 snd_hda_core uvcvideo  
intel_cstate iwlwifi snd_hwdep btusb videobuf2_vmalloc snd_seq  
intel_uncore videobuf2_memops btrtl videobuf2_v4l2 btbcm  
snd_seq_device btintel snd_pcm pcspkr cfg80211 mei_me wmi_bmof  
intel_wmi_thunderbolt videobuf2_common i2c_i801 snd_timer thunderbolt  
videodev bluetooth mei intel_pch_thermal mc thinkpad_acpi ucsi_acpi  
joydev typec_ucsi processor_thermal_device ecdh_generic  
intel_rapl_common ledtrig_audio ecc intel_xhci_usb_role_switch roles  
intel_soc_dts_iosf typec snd soundcore rfkill int3403_thermal  
int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad  
ip_tables dm_crypt i915 i2c_algo_bit cec crct10dif_pclmul  
crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel nvme drm  
serio_raw e1000e uas nvme_core usb_storage wmi video hid_multitouch  
fuse
Aug 13 18:23:51 rwells-x280 kernel: CPU: 0 PID: 5 Comm: kworker/0:0  
Tainted: GW 5.7.12-200.fc32.x86_64 #1


There is a problem with your WIFI adapter (what mac80211 is referring
to).  I don't think you can unplug and replug the adapter, which would
likely help, so don't just reset the computer, but power-cycle it.

Sometimes dmesg has messages that don't make it into the log due to
rate-limiting.  Not sure how to see dmesg when things are jammed up.

Do you know if the problem depends on a particular kernel?  Ususally
an older kernel will work, even if it isn't for the current version of
Fedora.  If that helps, try to narrow it down to a particular kernel.
If you find a boundary where it starts happening, report it on the
kernel bugzilla. You won't be able to properly report the bug, since
your kernel is tainted, but reporting it improperly may still be worth
something to kernel developers.

I suspect the hardware, but I'm often wrong.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: A few questions about a package update / policy questions / GCC 9 error

[Tony Nelson]

On 20-06-10 14:22:53, Simo Sorce wrote:

On Wed, 2020-06-10 at 14:16 -0400, Simo Sorce wrote:
> On Wed, 2020-06-10 at 20:01 +0200, Dan Čermák wrote:
> > "Nathanael D. Noblet"  writes:
> >
> > > Hello,
> > >
> > >   I maintain beanstalkd which is a message server of sorts. It  
recently
> > > released a new version however some changes I'm not 100% sure  
about.

> > >
> > >   When compiling I got the following GCC error.
> > >
> > > usr/include/bits/string_fortified.h:106:10: error:  
'__builtin_strncpy'

> > > specified bound 201 equals destination size [-Werror=stringop-
> > > truncation]
> > >   106 |   return __builtin___strncpy_chk (__dest, __src, __len,  
__bos

> > > (__dest));
> > >   |   
^~

> > > 
> > >
> > > Results via google says that strncpy needs to have the third  
argument

> > > less than the 2nd, so I've got this patch, similar to others:
> > >
> > > --- beanstalkd-1.12/tube.c.org  2020-06-10 09:37:35.129224346  
-0600
> > > +++ beanstalkd-1.12/tube.c  2020-06-10 09:37:42.761138035  
-0600

> > > @@ -12,7 +12,7 @@
> > >  if (!t)
> > >  return NULL;
> > >
> > > -strncpy(t->name, name, MAX_TUBE_NAME_LEN);
> > > +strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
> > >  if (t->name[MAX_TUBE_NAME_LEN - 1] != '\0') {
> > >  t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
> > >  twarnx("truncating tube name");
> > >
> > > You'll notice it was already checking the len-1 for null. Can  
anyone

> > > verify that my change won't cause some un-intended bug I don't
> > > understand?
> >
> > If I understand it correctly, then you are now invoking undefined
> > behavior: you copy at most MAX_TUBE_NAME_LEN-1 bytes to t->name  
and then
> > check whether the following byte (that was never written to) is  
not
> > equal to 0. I have not checked the code of beanstalkd, but the  
contents
> > of t->name[MAX_TUBE_NAME_LEN - 1] will be zero if it was  
allocated via
> > calloc() at best or random at worst. Irrespectively of that, the  
check
> > now no longer does what it *should*: null terminate the string if  
it is
> > not null terminated. It will now randomly null terminate it or  
not at

> > all.
>
> strncpy() is a truly awful API unfortunately, the change is
> meaningless, but it is not random as Dan says.
>
> The original form is more correct though, because now you can get
> spurious warnings that the string have been truncated when that is  
not
> true. (If t->name is not zeroized you will get the spurious warning  
for

> any string shorter than MAX_TUBE_NAME_LEN, which is the opposite of
> what the warning says.
>
> The third argument to strncpy can be as long as the size of the  
buffer
> you are writing into, the additional check you have there insures  
that

> the string is terminated (even if that requires truncation).
>
> So I would say you should drop your change and stop believing in  
random

> google results :)

Sorry, hit send prematurely.

If you really want to avoid the warning instead of ignoring it, you
should change the code this way:

strncpy(t->name, name, MAX_TUBE_NAME_LEN-1);
if (t->name[MAX_TUBE_NAME_LEN - 2] != '\0') {
t->name[MAX_TUBE_NAME_LEN - 1] = '\0';
twarnx("truncating tube name");
}

NOTE: the -2 in the condition, this is needed because memory locations
start counting from 0, so if you write N-1 bytes the Nth-1 byte is at
the N-2 position when you start counting from 0.
And that is the last position your strncpy wrote to, and if that is  
not

0 then potentially string truncation occurred.

You still want to zero the last available byte in that case and not  
the

N-1 available byte, so you set N-1 to 0, not N-2.

N-1 is the Nth byte when you start counting from 0 and N is the size  
of

the array.

HTH,
Simo.


I prefer to not look outside of the string's data into apparently
uninitialized memory.  Was t->name initialized elsewhere?  I would
write:

t->name[0] = 0;
strncat(t->name, name, MAX_TUBE_NAME_LEN-1);
if (strcmp(t->name, name)) {
...

strncat always writes a terminating NUL.

strcmp only looks at the string data, not past its end.

BTW, a better name for MAX_TUBE_NAME_LEN would be MAX_TUBE_NAME_SIZ.

C, bah.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Supporting hibernation in Workstation ed., draft 1

[Tony Nelson]

On 20-05-30 21:02:11, Chris Murphy wrote:
 ...

Full disk encryption doesn't adequately secure the hibernation image
either. Authenticated encryption (signing as well as encryption) is
needed to verify the image hasn't been tampered.


What can an attacker do other than corrupt the data?  It is encrypted.

With tamper detection, does a single bit changed deny the use of the
hibernated image?

In either case, what can an attacker accomplish?



The upstream work, cited in the document, gets into the details,
and what additional work is needed for the next revision.


Which reference is that?  #5?  It seemed short.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

[Tony Nelson]

On 20-03-21 08:45:09, Andreas Tunek wrote:
I sidegraded my rawhide install to F32 a couple of weeks ago and from  
the
start I noticed that booting F32 was really slow. I assumed this was  
some

kind of bug or some devel stuff and would get solved.

However, I still have the problem and I wonder if this a problem  
unique to
my hardware or a general bug when you move from rawhide to a version.  
If it
is a bug, does anyone know if there is a "slow boot on F32" bug  
somewhere?


Here is my "systemd-analyse blame" output:

 ...

I think your system is using the graphical boot.  Try the text boot, by
removing "rhgb" and "quiet" from the kernel command line during boot
(you may need to set a non-zero grub timeout once booted and try again).
I expect you will see some "a start job is running" text animations.
The longest one is probably your problem.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Debates/back and forths

[Tony Nelson]

On 19-08-28 07:03:00, Danny Lee wrote:

Hi all,

I'm new to the devel list and fedora in general, but i was wondering
if these kind of back and forths between a few people is a frequent
occurrence.  I came to Fedora to volunteer what little spare time I
have to help the Fedora project in some little ways. I don't feel
that should include wading through dozens of emailed back and forths
between individuals who seem to have strong, immovable opinions, I
just don't have time for that.

 ...

Perhaps you would prefer the low traffic of the Devel Announce list?

Check in the list archives first.


There were suggestions that your email provider might do mail filtering
into folders.  That is usually a function of the email client that
you use to read email, and if yours doesn't do it well, you can choose
another.  Thunderbird and Evolution come to mind (I use balsa myself,
but I don't necessarily recommend it).

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Fedora Workstation and disabled by default firewall

[Tony Nelson]

On 19-08-28 01:03:51, Chris Murphy wrote:
On Tue, Aug 27, 2019 at 10:26 PM Christopher  
 wrote:

>
> On Tue, Aug 27, 2019 at 9:27 PM Chris Murphy  
 wrote:

>
> > The Workstation technical specification document says in part:
>
> Where is the full technical specification document, so one can read  
it

> not in part, but in full?

https://fedoraproject.org/wiki/Workstation/Technical_Specification

The discussion and decision to not include firewall-config (GUI
configuration application for firewalld) by default, five years ago
https://lists.fedoraproject.org/archives/list/desk...@lists.fedoraproject.org/thread/QROJ6LHGT5UUMNTBXEIJTPHPI3IWGFRY/

What's changed since then? It's fine to have purposeful re-evaluation
of any requirements or specification, but someone or a group need to
look through the prior history, and clearly articulate why that
history is obsolete, and produce a compelling case why this should be
re-evaluated.

 ...

Well, they promised to be responsible and it is asserted that an open
firewall is not responsible, and they said they would develp solutions
but they opened the firewall instead, and they haven't shown an actual
example of software available through gnome-software (the only supported
way to install software on Gnome and Fedora Workstation) that needs the
firewall to be already open.  Properly packaged Fedora software uses
either the D-Bus interface at runtime or firewall-cmd in a scriptlet at
install time to open any needed ports, so an example of software that
works only because the ports are already open would be good.

Note that software needing open inbound ports will usually need ports
opened (or a service enabled) on some router, along with setup to direct
incoming connections to the correct internal IP, so it can't work OOB.
It's possible that there is some confusion here, and Gnome thinks that
outbound ports need to be opened and that that is what they have done.

I haven't needed to do anything with firewalld on my machines in the
last few years, and my zone is "public", so I'm not very familiar with
firewalld.  (I use XFCE, not Workstation.)

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Fedora Workstation and disabled by default firewall

[Tony Nelson]

On 19-08-27 19:58:15, Chris Murphy wrote:
 ...

I definitely do not want to pester developers, or make their day to
day life difficult. If there's no satisfactory GUI right now to manage
it, it's difficult to even experiment with different policies. The
original firewalld proposal considered the graphical tool the main way
of interacting with the firewall, and it was the cli tool that came
later, yet as far as I recall, Workstation never shipped with this GUI
tool.


The package is firewall-config.  On XFCE, App menu -> Administration ->
Firewall.  Perfectly normal graphical firewall configurator.  I've
never used it, because I haven't had to.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Fedora Lifecycles: imagine longer-term possibilities

[Tony Nelson]

On 18-11-18 16:29:45, Richard W.M. Jones wrote:

I'm not for or against a longer Fedora lifecycle, but I think we need
a stronger statement of what the problem is we're trying to address.

From your email:

On Tue, Nov 13, 2018 at 06:36:38PM -0500, Matthew Miller wrote:
> But there are some good cases for a longer lifecycle. For one thing,
> this has been a really big blocker for getting Fedora shipped on
> hardware. Second, there are people who really could be happily  
running
> Fedora but since we don't check the tickbox, they don't even look  
at us

> seriously. I'd love to change these things. To do that, we need
> something that lasts for 36-48 months.

this sounds like a very valid problem.

But if this was fixed, what number of manufacturers would adopt Fedora
and how many installations do they ship (eg per year)?  Could it be
fixed in another way, like a special OEM Fedora release?

Is this the only problem that we're trying to solve or are there  
others?


I would suggest fixing the "problem" in a completely different way.
There seems to be a class of customer that wants the very latest thing,
often, but for each such thing to hold still and be maintained for 3 to
7 years.  That isn't Fedora, or even RHEL.

Fedora can be updated and upgraded with good reliablility now.  So,
instead, continue to make updates and version upgrades more and more
reliable, and revertable when they don't work, as MSWindows has been
doing.  Get more users within those customers so they trust that
reliablility.  Then those customers can choose, in a business way, to
install Fedora for their customers, who will get and keep the latest
and greatest, and Fedora has captialized on its strengths.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: hibernation — does it work for you?

[Tony Nelson]

On 18-10-03 11:38:20, Zbigniew Jędrzejewski-Szmek wrote:
 ...

If you perform hibernation (systemctl hibernate, or the equivalent
through the GUI), does _your_ system suspend and resume correctly?

 ...

Yes.

Acer Aspire E 15 (Aspire ES1-512-P9GT)

For several kernels it wouldn't power off after hibernating[1], but
that seems fixed now.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1602808

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: What does 141 mean?

[Tony Nelson]

On 18-09-16 17:53:08, Björn Persson wrote:

I have a Kerberos authentication problem.

On one computer running Fedora 27, I run kinit to authenticate to the
Fedora servers. After I enter my passphrase, kinit returns exit status
141. Then I run "fedpkg build", and get these error messages:

Kerberos authentication fails: (-1765328352, 'Ticket expired')
Could not execute build: Could not login to  
https://koji.fedoraproject.org/kojihub


On another computer also running Fedora 27, I run the exact same kinit
command. After I enter my passphrase, kinit returns exit status 0. I  
can

then run "fedpkg build" successfully.

There is no error message from kinit, no indication that anything is
wrong other than the exit code 141. I can't find any documentation of
exit codes from kinit. Thus I have no hint at what the problem might  
be.

Does anyone know what this code means?


No, but googling "kinit 141" leads to
https://bugzilla.redhat.com/show_bug.cgi?id=1537866
which suggests trying the kinit command twice in a row.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F28 balsa email client can't send email

[Tony Nelson]

I just upgraded from F26 to F28.  The balsa email client is not able
to send mail through my server because it doesn't try to authenticate.
This is probably because it doesn't STARTTLS, likely because of
incompatibility between libesmtp (which balsa uses to send mail) and
openssl 1.1, which results in libesmtp building without ssl support.
Supposedly this is fixed in Rawhide, but not in F28.  I have hacked
the libesmtp rpm to use compat-openssl10 and now have balsa working --
patch in bug 1483350 below.

I also rebuilt balsa with my patches to make the Queue toolbar button
not send immediately and to allow self-signed certificates so I can
use my mail server.

Since these issues existed in F26, I expect that there are no other
balsa users left, and this is just informational.

See closed Bug 1479177 - since upgrade balsa is no longer able to send  
emails


and Bug 1483350 - libesmtp built w/o SSL support -- compat-openssl10  
required



Bug 1483354 - balsa message window Queue toolbar button sends  
immediately



Bug 1483649 - balsa no longer accepts mail server self-signed  
certificate



--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZWY5C6J2ZJE5JMH4E4VIGS3HVOYM6BZJ/

Re: Re: Broken system upgrade due to rich dependencies

[Tony Nelson]

On 18-03-07 14:14:38, Nicolas Mailhot wrote:

Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit :
> On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot
>  wrote:
> > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a  
écrit

> > :
> > >
> > > I don't know if this is useful but in the RHL and early Fedora
> > > days,
> > > the way to do inplace upgrades was to first update just the  
'core'

> > > tools needed by rpm.
>
> This is a totally unrelated comment, but I will personally send you  
$5

> if you can configure your email client to stop adding  in the
> Subject line for every thread you reply to.

I'm pretty sure that's added by one of the MTAs in the chain between
Fedora SMTP and my ISP MTA, to attest they did DKIM verification,  
since

I see it already positioned on some received messages before I ever
replied to them.


Presumably by bastion01.phx2.fedoraproject.org (Postfix), which adds the
lines:

DKIM-Filter: OpenDKIM Filter v2.11.0 bastion01.phx2.fedoraproject.org
 2E4116051DFD
Authentication-Results: bastion01.phx2.fedoraproject.org;	 
dkim=fail
 reason="signature verification failed" (2048-bit key)  
header.d=laposte.net

 header.i=@laposte.net header.b="bKrmUuvt"

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Need help debugging hedgewars

[Tony Nelson]

On 17-12-17 14:33:43, John Reiser wrote:
 ...

At this point I suggest to file a bugzilla report against the compiler
for not keeping %rsp 16-byte aligned.  Include the traceback and
the register info from the gdb session at SIGSEGV, and the identities
(.so name, build-id, .rpm name) of the shared libraries that were  
loaded

at the time of SIGSEGV.

 ...

As somebody mentioned sending the binary to a user of another distro,
where it worked properly, isn't the problem likely to be how some Fedora
build of a shared library is compiled?

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Bug 921430 - Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)

[Tony Nelson]

On 17-09-14 10:01:21, Przemek Klosowski wrote:

On 09/13/2017 09:43 PM, Tony Nelson wrote:

For some reason, `dnf list libatasmart` says "Error: No matching
Packages to list", but `rpm -q libatasmart` returns the installed
version.  I've done `dnf clean all` twice, installed the update with
`rpm -U`, and rebuilt the RPM database with no change.  `dnf  
repoquery

libatasmart\*` only finds the devel packages.  Hopefully this is just
something about my own system.


maybe dnf sees that you have newer packages or packages installed
outside of the repos? try dnf distro-sync and/or dnf clean all.


No, I'm just careless.  Only a month ago when I was patching
libatasmart, I noted that the bug hadn't been fixed in 5 years, so I
added an "exclude" and then forgot about it.  yum would remind me if
I did that ("why is that red?"), but dnf doesn't.

--

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Bug 921430 - Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)

[Tony Nelson]

On 17-09-13 14:10:06, Kevin Fenzi wrote:

On 09/09/2017 09:48 AM, Tony Nelson wrote:
> Could someone apply the patch in this bug[1], languishing since  
2013?

> According to "freedesktop.org Bug 61998 - Fails to read status from
> WD raptors"[2] the patch is in Debian/Ubuntu.  Lennart Poettering  
did

> the last upstream[3] commit 7 years ago, but seems to be busy now.
>
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=921430
> [2]: https://bugs.freedesktop.org/show_bug.cgi?id=61998
> [3]: https://github.com/Rupan/libatasmart

Patch seems simple and tons of people say it's working for them, so  
sure.


Please test and upkarma the updates:

https://bodhi.fedoraproject.org/updates/FEDORA-2017-412adfa2d6
https://bodhi.fedoraproject.org/updates/FEDORA-2017-aad2676f0b
https://bodhi.fedoraproject.org/updates/FEDORA-2017-9126f38bc2


Thank you.  I have installed the update and it didn't break anything,
but, as I had previously installed my own version I didn't expect it
to.  There is nothing in the journal from libatasmart, but it's hard
to know if it's really working unless a drive fails.

For some reason, `dnf list libatasmart` says "Error: No matching
Packages to list", but `rpm -q libatasmart` returns the installed
version.  I've done `dnf clean all` twice, installed the update with
`rpm -U`, and rebuilt the RPM database with no change.  `dnf repoquery
libatasmart\*` only finds the devel packages.  Hopefully this is just
something about my own system.

--

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Bug 921430 - Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)

[Tony Nelson]

Could someone apply the patch in this bug[1], languishing since 2013?
According to "freedesktop.org Bug 61998 - Fails to read status from
WD raptors"[2] the patch is in Debian/Ubuntu.  Lennart Poettering did
the last upstream[3] commit 7 years ago, but seems to be busy now.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=921430
[2]: https://bugs.freedesktop.org/show_bug.cgi?id=61998
[3]: https://github.com/Rupan/libatasmart

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: ssl is not being compiled on dillo on F26

[Tony Nelson]

On 17-09-07 09:47:36, Globe Trotter wrote:

Hello,
I posted this on the F26 mailing list but the issue may be deeper  
requiring some more knowledge from the developers so I thought that I  
would also put it here.

There is a bug report on this here:
 Bug 1470354 – dillo appears to not have been compiled with ssl in F26

 ...

From the user's list:

On 17-09-06 14:03:44, Rick Stevens wrote:

On 09/06/2017 09:40 AM, Ranjan Maitra wrote:
> Hi,
>
> Dillo's ssl support seems to be broken in F26 (and has been since  
the day it was released). Here is what happens:

>
> Go to https://www.nytimes.com/
>
> The webpage says that Dillo's prototype plugin for https support is  
disabled.

>
> I downloaded the src.rpm to see what the problem was with the .spec  
file and found that nothing has changed. Specifically, the following  
is there (as it was for the F25 spec):

>
> %configure --disable-dependency-tracking --enable-ipv6 --enable-ssl
>
> So, then I was wondering why this has stopped working with dillo  
with F26. Any ideas for a fix?


It's very odd. I built the source RPM and the configuration failed the
SSL library test saying it can't find SSL_library_init(), thus it  
isn't
enabling SSL (below is culled from the config.log file after a  
"rpmbuild

-bc dillo.spec"):

 ...

| /* Override any GCC internal prototype to avoid an error.
|Use char because int might match the return type of a GCC
|builtin and then its argument prototype would still apply.  */
| #ifdef __cplusplus
| extern "C"
| #endif
| char SSL_library_init ();
| int
| main ()
| {
| return SSL_library_init ();
|   ;
|   return 0;
| }
configure:6208: result: no
configure:6224: WARNING: *** No libssl found. Disabling ssl  
support.***

 ...

Looks like the same sort of problem as with balsa email client, or
actually libesmtp:  not compatible with openssl-1.1 [1].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1483350

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Provide more testing feedback (was: Re: Refining the update queues/process)

[Tony Nelson]

On 10-03-05 17:00:12, Till Maas wrote:
 ...
 But it seems that os.getlogin() is too smart for this purposes, e.g.
 for me it always uses the username that started X, even if I su - 
 or sudo -i into another account.

The Python docs[1] suggest using the environment variable LOGNAME.

[1] http://docs.python.org/library/os.html#os.getlogin

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

[Tony Nelson]

On 10-03-01 15:06:21, Josh Stone wrote:
 On 03/01/2010 11:46 AM, Seth Vidal wrote:
 ...
  yum history undo works pretty well. Not flawless, to be sure - but
  it's not bad for the simple-ish cases.
 ...
 But for rolling back an update, yum requires that the old package is
 still available.  We only keep the very latest version in the 
 updates, so unless your previous version was from the initial 
 release, you're out of luck.  My last yum-update hit 19 packages, and 
 only 7 can be downgraded by yum-history-undo.

Yeah, what's up with that?  I see Failed to downgrade for packages 
that are still present in the yum cache, available with no need to 
fetch them at all.

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

[Tony Nelson]

On 10-02-26 11:07:34, Michael Cronenworth wrote:
 ...
 Yes, this functionality is available in bodhi-client and I use it 
 myself, but isn't it safe to say there are many Fedora users that 
 have no idea what bodhi-client is or even admin.fp.o?
 ...

The bodhi-client package could really use a real description:

Description: Client tools for interacting with bodhi

What is Bodhi?  What does the client allow a user to do with Bodhi?  
That's what a Description needs.  The current Description acts as a 
warning that one shouldn't look at or install the package, as it is 
only for some special use.

The bodhi-client man page has the same issues.  From its list of 
options I conclude that indeed bodhi-client is not for use by mere 
mortal users such as me.  For one thing, I think I'd need a Bodhi 
account.  If all this is not true, then there are severe deficiencies 
in the documentation.

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Final (hopefully) privilege escalation policy draft

[Tony Nelson]

On 10-02-10 15:48:39, Adam Williamson wrote:
 Hi, all. So the privilege escalation policy went to FESco, who
 suggested some minor tweaks and a final run-by the mailing lists 
 before it gets approved.
 
 I have now adjusted the draft -
 https://fedoraproject.org/wiki/User:Adamwill/
 Draft_Fedora_privilege_escalation_policy
 - to reflect all feedback from this list and from FESco. It will be
 reviewed again by FESco next week. Please raise any potential issues
 or further suggestions for adjustments before then. Of course, even 
 if the policy is accepted by FESCo it will not be set in stone and
 changes and exceptions can be added in future as appropriate, but I'd
 like to have it as good as possible at first :) thanks all!

Directly read or write directly to or from system memory has an extra 
(or out of order) directly.

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [RFC PATCH] use sulogin in single-user mode

[Tony Nelson]

On 10-01-22 13:29:11, Bruno Wolff III wrote:
 On Fri, Jan 22, 2010 at 13:15:04 -0500,
   Tony Nelson tonynel...@georgeanelson.com wrote:
  
  Put SELinux into Permissive mode for single-user mode?  Or just
  print a suggestion to do that?  (I'd think that SELinux would 
  normally be perceived as an obstacle to the normal uses of single-
  user mode.)
 
 I think doing it automatically is a bad idea. It doesn't save much
 over typing setenforce 0. It does however reduce the security of 
 the system if you do it by default and there is a vulnerable window 
 before you get setenforce 1 entered.

What external threats is the system vulnerable to in single-user mode?  
Networking is off and there are no other users.  The only threat I know 
of is PEBKAC.


 The notice seems odd, but I don't think it would cause actual
 problems. I just think it would be odd to know to boot to run level 1 
 without knowing how to set selinux to permissive mode.

1) not when you're just starting out.

2) not when you're hurrying because an important system won't boot.

3) not when you forgot about selinux.

The notice should print only when /selinux/enforce exists and contains 
1 (/usr may not be mounted, so we can't depend on /usr/sbin/
sestatus at that time).

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: how to speed up mock?

[Tony Nelson]

On 10-01-18 11:34:44, Ville Skyttä wrote:
 ...
 So instead of modifying specfiles, one can do something like this in 
 /etc/mock/site-defaults.cfg:

 config_opts['macros']['%_smp_mflags'] = '-j3'

Unless `rpmbuild --showrc` shows a bad definition for _smp_mflags, 
you're probably better off letting the macro decide.  IME, using a 
number larger than the actual number of CPUs slows the build a lot, due 
to cache thrashing.  Modern CPUs perform well only with hot caches, and 
each switch to the other build process will replace the cache 
contents.

The OP said that rpmbuild was using the CPUs properly and ran fast, but 
earlier parts of mock were not and ran slowly, and take most of the 
time.  He indicated that most of the time is spent extracting the build 
root from the cache.

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: ABRT frustrating for users and developers

[Tony Nelson]

On 10-01-17 12:32:17, Mail Lists wrote:
 On 01/17/2010 11:57 AM, Christoph Wickert wrote:
  Am Sonntag, den 17.01.2010, 15:53 +0100 schrieb Jiri Moskovcak:
  On 01/16/2010 04:01 PM, Christoph Wickert wrote:
 
 
  I'm open to any ideas how to improve this.
 
 
  Someone else asked this earlier - but why do users need the
 debug-info packages - only the debugger looking at the tracebacks 
 needs this. So seems installing the debug files on every desktop/
 server that has a problem is much less efficient than just on the dev 
 computer who needs the info - no?

Apparently Linux has no mini-dump facility, so the upload of the whole 
core dump file would be onerous as well.

-- 

TonyN.:'   mailto:tonynel...@georgeanelson.com
  '  http://www.georgeanelson.com/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel