Re: Who moved my journald.conf?

[Michael Schwendt]

On Thu, 9 May 2024 15:12:57 -0400, Tom Horsley wrote:

> I mean, what if [Journal] means
> "Forget everything, we're starting journal options now"? The last
> thing you'd want to do is put in a [Journal] line in that case and
> forget all the previous settings :-).

That's an odd thought in my opinion, since [Foo] typically is an .INI-style
section specification that doesn't reset any variable=value assignments
within that named section.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Who moved my journald.conf?

[Michael Schwendt]

On Wed, 08 May 2024 10:49:12 +0100, Patrick O'Callaghan wrote:

> As stated earlier, it hasn't been modified by me.
> 
> > What is in your /etc/systemd/journald.conf file compared with the
> > default in /usr/lib/systemd/journald.conf?  
> 
> They are identical except for comments:

That proves my point. The file contents don't come from within the systemd
package where the file is just a %ghost.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Who moved my journald.conf?

[Michael Schwendt]

On Tue, 07 May 2024 23:22:53 +0100, Patrick O'Callaghan wrote:

> In that case I assume it was put there under F39. Seems very odd that
> the upgrade just kept it in addition to the one in /usr/lib/systemd.

Depends.

You cannot rely on just "rpm -qf ..." since that only queries the package
file list regardless of what the file contents are. And that includes
%ghost files which possibly don't exist. Also, it is not only a %ghost
file but also still marked as %config, and if it has been modified by you,
RPM package upgrades would handle it like a config file.

What is in your /etc/systemd/journald.conf file compared with the
default in /usr/lib/systemd/journald.conf?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Who moved my journald.conf?

[Michael Schwendt]

On Tue, 07 May 2024 21:38:47 +0100, Patrick O'Callaghan wrote:

> It's there on my system, updated from F39:
> 
> # rpm -qf /etc/systemd/journald.conf
> systemd-255.4-1.fc40.x86_64

No, it's not:

$ rpm -qcv systemd|grep conf$
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/X11/xorg.conf.d/00-keyboard.conf
-rw-r--r--1 root root   21 Mar  1 01:00 
/etc/dnf/protected.d/systemd.conf
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/locale.conf
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/systemd/journald.conf
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/systemd/logind.conf
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/systemd/system.conf
-rw-r--r--1 root root0 Mar  1 01:00 
/etc/systemd/user.conf

It's a %ghost config file, which means it is marked as belonging to the
package (even if it doesn't exist in the directory), so it can be handled
appropriately on package removal/updates.

The default file has been moved to /usr/lib/systemd/journald.conf.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 and breaking file command change

[Michael Schwendt]

On Fri, 3 May 2024 05:30:21 -0400, Jeffrey Walton wrote:

> I thought the same thing about the file program. The change should have
> caused a regression when running its self tests. The authors should  have
> known there was a problem with what they did.

It's more likely that the file program's test-suite would ensure that
recognizing CSV files still works for a limited set of test files. And
even that would not be entirely safe, since the same files would classify
also as other file types. The printed types are not carved into stone
forever. What about the difference between ASCII text and UTF-8 text, for
example? Regardless of what file format it may be.

Perhaps use file --mime-type instead. It would print "text/csv".

Either way, I would not rely on "file" when trying to detect CSV files.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 and breaking file command change

[Michael Schwendt]

On Wed, 1 May 2024 23:10:18 -0400, Jeffrey Walton wrote:

> I was amazed the file project broke the command. The projects I contribute
> to will move mountains to avoid breaking established behavior. We don't
> want to screw our users like that.

In such a case, your script ought to apply some safety measures.
Like putting some guards in front that verify that the printed type for
specific files matches your expectations. It wouldn't take much to maintain
your own small set of input files as an automatic test-suite.

The "file" type output has changed before. And the printed types are better
not parsed as a full sentence but as individual keywords in a set. Your
primary interest seems to be in detecting the term "CSV".

Various scripts that rely on console output have broken before, mistakenly
expecting specific status/error/whatever messages.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Where is the source code for a Koji build?

[Michael Schwendt]

On Thu, 22 Feb 2024 04:13:18 -0500, Jeffrey Walton wrote:

> I'm new to working with Fedora's Release Engineering. I ran across a
> package that Failed To Build From Source (FTBS) for Fedora 40 at
> . I have C and
> C++ experience, and I believe I can help.
> 
> I'm having trouble making my way around Koji. I can't find the source
> code for wcm-0.20.0-22.fc39 to repro and fix the bug. (The Source
> field does not provide the source files. After cloning, there's only
> one file called 'dead.package').
> 
> Where does one find the source code? Or where do I find the package
> sources that Fedora used?

That's an unmaintained package. It has been orphaned some months ago. You
would need to check out a prior commit in git or fetch an older src.rpm
for that package from a successful build. In Fedora Koji, files for failed
builds expire eventually.

https://src.fedoraproject.org/rpms/wcm
https://koji.fedoraproject.org/koji/packageinfo?packageID=20817
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: emacs is hopeless

[Michael Schwendt]

On Sun, 12 Nov 2023 20:50:04 -0500, Jeffrey Walton wrote:

> I have not encountered any problems (yet?).

Fedora 39 Workstation installation (so Wayland based), launching Emacs
from GNOME Shell as well as terminals. No problems yet. I apply some
font face customizations in ~/.emacs though.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Sound synthesizer for Linux

[Michael Schwendt]

On Sun, 22 Oct 2023 19:59:56 -0400, Fulko Hew wrote:

> About 15 years or so ago, I was using a sound synthesizer on Fedora
> that was GUI drag-n-drop sound modules, and draw wires between them
> There were VCOs, filters, ADSR, mixers, etc.
> 
> It looks like I never wrote down what I installed back then.
> Can anyone remember or think of what that software was called?
> Nothing I've been able to Google now resembles that simple/powerful tool.

Ardour?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: systemd-oomd insanely aggressive with non-DE logins

[Michael Schwendt]

On Sun, 12 Mar 2023 13:37:46 -, Andre Robatino wrote:

> I have 3 machines with clean F37 installs.

Dunno yet whether it's also F37 or just F38, but here on F38 even
gnome-terminal is getting killed when running a simple tar command in it
that works on creating a ~20 GB archive.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: directories in /usr

[Michael Schwendt]

On Tue, 27 Dec 2022 14:31:16 -0800, Samuel Sieb wrote:

> If they are installed by the package manager, you shouldn't be deleting 
> them.
> Do you mean "x86_64-w64-mingw32" and "i686-w64-mingw32"?
> Did you install wine?

Those files and directories are related to mingw not wine.

And there are tons of files/dirs in there, which get created without
belonging to any RPM package. Which is a packaging mistake somewhere.
Run "rpm -qf" on a file in those dirs to check whether it belongs into an
RPM package.

Example:

$ rpm -qf 
/usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES/gtk-vnc.mo
gvnc-1.3.0-5.fc37.x86_64
gvncpulse-1.3.0-5.fc37.x86_64

$ rpm -qf /usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES
file /usr/x86_64-w64-mingw32/sys-root/mingw/share/locale/en_GB/LC_MESSAGES
is not owned by any package
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: mp4 to dvd

[Michael Schwendt]

On Fri, 24 Dec 2021 14:17:57 -0600 (CST), Michael Hennebry wrote:

> Any suggestions for converting mp4 files to VOB?
> Even an example with mencoder might be useful.
> Long long ago, I used mencoder for making DVD video files.
> Lost track of the script I used.
> I tried it again recently,
> but getting all the options right was making my head swim.
> 
> At least one of the files I want to convert is 480x360@24 .

Have you used package "dvdstyler" from RPMFusion Free before?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 pipewire no audio after updates

[Michael Schwendt]

On Thu, 19 Aug 2021 12:30:36 -0700, Jack Craig wrote:

> i too have this problem after f34 install. (fresh, not updated).given
> michael's status, what is the
> next thing to try?

Between GDM screen and logging in, something falls flat on its nose and
sends errors to the logs, but the three pipewire processes are running:

Aug 25 12:17:45 localhost.localdomain pipewire-media-session[2103]: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply
Aug 25 12:20:34 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db79010: error no node available
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db49e70 [eSpeak]: ERROR command:-1 (invalid) tag:2 error:25 
(Input/output error)
Aug 25 12:20:34 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db5c1e0: error no node available
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db67740 [speech-dispatcher-espeak-ng]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
Aug 25 12:20:34 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db5c1e0: error no node available
Aug 25 12:20:34 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db88610 [speech-dispatcher-dummy]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
Aug 25 12:23:02 localhost.localdomain pipewire-media-session[2103]: no node 
found for 43
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db5c1e0: error no node available
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db6d350 [eSpeak]: ERROR command:-1 (invalid) tag:2 error:25 
(Input/output error)
Aug 25 12:23:02 localhost.localdomain pipewire-media-session[2103]: no node 
found for 43
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db5c1e0: error no node available
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10dab91e0 [speech-dispatcher-espeak-ng]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
Aug 25 12:23:02 localhost.localdomain pipewire-media-session[2103]: no node 
found for 43
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db79010: error no node available
Aug 25 12:23:02 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db6d190 [speech-dispatcher-dummy]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
Aug 25 12:24:52 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:24:52 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db366b0: error no node available
Aug 25 12:24:52 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db4a640 [eSpeak]: ERROR command:-1 (invalid) tag:2 error:25 
(Input/output error)
Aug 25 12:24:52 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:24:52 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10dfb5c50: error no node available
Aug 25 12:24:52 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10dfba9a0 [speech-dispatcher-espeak-ng]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
Aug 25 12:24:53 localhost.localdomain pipewire-media-session[2103]: no node 
found for 44
Aug 25 12:24:53 localhost.localdomain pipewire-pulse[2088]: stream 
0x55b10db32640: error no node available
Aug 25 12:24:53 localhost.localdomain pipewire-pulse[2088]: client 
0x55b10db48d40 [speech-dispatcher-dummy]: ERROR command:-1 (invalid) tag:2 
error:25 (Input/output error)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 pipewire no audio after updates

[Michael Schwendt]

On Wed, 28 Jul 2021 13:14:03 +0200, Michael Schwendt wrote:

> Am I the only one where audio is missing after recent updates to F34?
> The three pipewire processes are running, but no sound. No volume control
> in GNOME Shell either.

It's been a week or so without such problems, but today it's back.

$ ps axuw|grep pipe
ms342042  0.0  0.1 266652  9780 ?Shttps://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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

F34 pipewire no audio after updates

[Michael Schwendt]

Am I the only one where audio is missing after recent updates to F34?
The three pipewire processes are running, but no sound. No volume control
in GNOME Shell either.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Troubles with the claws-mail

[Michael Schwendt]

On Sun, 6 Jun 2021 12:00:11 +0200, Bob Marcan wrote:

> Fedora 33 up to date (Sun Jun  6 11:47:43 CEST 2021)
> claws-mail-3.17.8-1.fc33.x86_64)
> 
> In claws-mail keyboard key "k" is ignored.
> Same key is working in all other applications.
> So it is not a keyboard problem. :-)
> Does anybody have an idea where is the problem?

Where exactly? Inside the message compose window?
In other editable GUI input fields like "To", "Cc", "Subject" lines?

That would render the program unusable, which would be very odd
given that it is used on a daily basis.

Which graphical desktop environment do you use?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: dnf exclude option not working

[Michael Schwendt]

On Tue, 29 Dec 2020 19:00:30 +0200, Kostas Sfakiotakis wrote:

> [root@Orion ~]# dnf repoquery --whatrequires libcpuid
> 
> Last metadata expiration check: 0:52:55 ago on Tue 29 Dec 2020 06:01:13 
> PM EET.
> cpu-x-0:4.0.1-5.fc33.x86_64
> i-nex-0:7.6.1-4.fc33.x86_64
> i-nex-0:7.6.1-6.fc33.x86_64
> libcpuid-devel-0:0.4.1-3.fc33.i686
> libcpuid-devel-0:0.4.1-3.fc33.x86_64
> libcpuid-devel-0:0.5.0-1.fc33.i686
> libcpuid-devel-0:0.5.0-1.fc33.x86_64
> 
> The only package from the above that i was using was cpu-x ( deleted it 
> since ) , i am not using i-nex , so by deleting the cpu-x package i was 
> indeed getting rid off the
> problem you mentioned with libcpuid . That's what i was trying to say .

You had written "[...] and then reinstall or abandon the cpu-x package
for the moment [...]", which prompted me to point out that reinstalling
the package would not fix anything, since it would not fix the dependency
breakage.

Of course, if you don't need cpu-x at all, you can keep it removed.
Reinstalling is what would not fix anything with regard to the libcpuid
test update breakage.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: dnf exclude option not working

[Michael Schwendt]

On Tue, 29 Dec 2020 18:46:05 +0200, Kostas Sfakiotakis wrote:

> root@Orion ~]# dnf repoquery --whatrequires cpu-x
> 
> Last metadata expiration check: 0:07:22 ago on Tue 29 Dec 2020 06:01:13 
> PM EET.
> cpu-x-data-0:4.0.1-5.fc33.noarch

That query isn't helpful, because it doesn't show what you are interested
in. Instead, you want to run

  dnf repoquery --requires cpu-x

as to examine what the cpu-x package depends on. Among the libraries it
depends on is the offending "libcpuid" package.

> I deleted the cpu-x package and then
> 
> 
> dnf  upgrade -x=elementary-planner did the magic and the above upgrades 
> were performed
> 
> So my immediate problem ( not being able to upgrade packages at all ) 
> was resolved .  Though i think that i understand what you are suggesting .

That is a fallacy. As soon as cpu-x would be installed again, the problem
would return, since nothing has changed, and as long as the incompatible
test update of libcpuid remains available, you cannot update that package
since it would break dependencies. The way forward would be to either
rebuild cpu-x and offer it as an update, or to withdraw the incompatible
libcpuid package from the updates-testing repo.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: dnf exclude option not working

[Michael Schwendt]

Kostas Sfakiotakis  schrieb am Mo., 28. Dez.
2020, 23:25:

>
> Στις 28/12/20 8:15 μ.μ., ο/η Michael Schwendt έγραψε:
> > On Mon, 28 Dec 2020 19:57:05 +0200, Kostas Sfakiotakis wrote:
> >
> >> Error:
> >>Problem: problem with installed package cpu-x-4.0.1-5.fc33.x86_64
> >> - cannot install the best update candidate for package
> >> cpu-x-4.0.1-5.fc33.x86_64
> >> - package cpu-x-4.0.1-5.fc33.x86_64 requires
> libcpuid.so.14()(64bit),
> >> but none of the providers can be installed
> >> - cannot install the best update candidate for package
> >> libcpuid-0.4.1-3.fc33.x86_64
> >> - cannot install both libcpuid-0.5.0-1.fc33.x86_64 and
> >> libcpuid-0.4.1-3.fc33.x86_64
> >> - cannot install both libcpuid-0.4.1-3.fc33.x86_64 and
> >> libcpuid-0.5.0-1.fc33.x86_64
> >> (try to add '--skip-broken' to skip uninstallable packages)
> > As you can conclude from the version-release numbers shown for the
> > libcpuid package, you strictly need libcpuid-0.4.1 for your already
> > installed cpu-x package. But the updates-testing repository offers an
> > incompatible upgrade to libcpuid-0.5.0, which breaks existing
> > dependencies. You may choose to ignore (= exclude) that package,
> > and of course, you will not be able to install anything that strictly
> > requires this newer but incompatible package.
>
> Well that's the problem . I am not able to exclude cpu-x . No matter
>
> how i try to syntax the dnf command , cpu-x doesn't get excluded and
>
> the whole update fails . The only "solution" that comes to mind is
>
> delete the cpu-x package , perform the upgrades and then reinstall or
>
> abandon the cpu-x package for the moment .
>

The cpu-x package is installed already. You cannot exclude it. Erasing and
reinstalling it would not avoid dependency breakage as long as the
incompatible libcpuid pkg is offered in the repos.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: dnf exclude option not working

[Michael Schwendt]

On Mon, 28 Dec 2020 19:57:05 +0200, Kostas Sfakiotakis wrote:

> Error:
>   Problem: problem with installed package cpu-x-4.0.1-5.fc33.x86_64
>    - cannot install the best update candidate for package 
> cpu-x-4.0.1-5.fc33.x86_64
>    - package cpu-x-4.0.1-5.fc33.x86_64 requires libcpuid.so.14()(64bit), 
> but none of the providers can be installed
>    - cannot install the best update candidate for package 
> libcpuid-0.4.1-3.fc33.x86_64
>    - cannot install both libcpuid-0.5.0-1.fc33.x86_64 and 
> libcpuid-0.4.1-3.fc33.x86_64
>    - cannot install both libcpuid-0.4.1-3.fc33.x86_64 and 
> libcpuid-0.5.0-1.fc33.x86_64
> (try to add '--skip-broken' to skip uninstallable packages)

As you can conclude from the version-release numbers shown for the
libcpuid package, you strictly need libcpuid-0.4.1 for your already
installed cpu-x package. But the updates-testing repository offers an
incompatible upgrade to libcpuid-0.5.0, which breaks existing
dependencies. You may choose to ignore (= exclude) that package,
and of course, you will not be able to install anything that strictly
requires this newer but incompatible package.

The corresponding ticket in the Fedora Updates System already tells
that this Test Update causes problems:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-e0923ba04b
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: dnf exclude option not working

[Michael Schwendt]

On Mon, 28 Dec 2020 14:07:19 +0200, Kostas Sfakiotakis wrote:

> Στις 28/12/20 2:36 π.μ., ο/η Ed Greshko έγραψε:
> > On 28/12/2020 08:05, Kostas Sfakiotakis wrote:  
> >> Can someone please tell me the correct syntax of the exclude option ( 
> >> the -x option will not work as well ) ??
> >>
> >> dnf upgrade  --best --allowerasing --exclude=cpu-x-4.0.1-5.fc33.x86_64  
> >
> > Have you tried just
> >
> > dnf upgrade  --best --allowerasing  --exclude=cpu-x  
> 
> Yes it will not work either . Also
> 
> dnf upgrade --best --allowerasing -x=cpu-x will not work .
> 
> I have tried all the variations that i could think off .
> 
> Even
> 
> dnf  upgrade --best --allowerasing -exclude=cpu-x-4.0.1-5.fc33.x86_64.rpm
> 
> will not work .

That quoted line makes no sense, since it contains multiple errors.
Correct would be: --exclude=PACKAGENAME
Not: -exclude=PACKAGENAME.rpm
And PACKAGENAME may include version, release and arch, but not ".rpm"
if you work with repositories.

Please show full output of what you're trying to do.
Don't just write "will not work" without telling details.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: smartd log alert

[Michael Schwendt]

On Sun, 27 Dec 2020 17:56:56 +0100, François Patte wrote:

> What is a "fairly low rate"? And beyond which rate do I have to be scared?

Usually, you would want the displayed value to be high, since the
underlying "rate" is mapped. If the shown value drops much, that would
be reason to be concerned. The smartctl tool displays the last "worst"
value, and if it drops below the displayed threshold, such as 50% or 30%
but hardware/firmware dependent, things could go worse soon.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: smartd log alert

[Michael Schwendt]

On Sun, 27 Dec 2020 14:36:54 +0100, François Patte wrote:

> I have this alert in my watchlog report:

Have you used the smartctl tool from the smartmontools package yet as
to examine SMART data and perhaps run self-tests?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: The (bad) state of Qt on GNOME / Wayland

[Michael Schwendt]

Thread is old, but makes me wonder, is there any current status on Qt with
Wayland?

In F33 with GNOME Workstation, several Qt applications don't work correctly
with Wayland, but do work if switching to Xorg.

avidemux-qt, for example, displays a video preview area that doesn't
update.

Audacious 4, which is based on Qt by default but still includes a GTK+
based UI, too, which can be enabled on demand, fails for its Winamp UI
mode. Windows can't be moved. If switching to the GTK+ UI backend, the
problem with the Winamp mode cannot be reproduced.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Firefox Clear History not clickable / F33

[Michael Schwendt]

This is with default Fedora 33 Workstation x86_64.

Firefox > History > Clear Recent History > Time range to clear

The combobox can be clicked to show the drop-down list, but none of the
shown items can be selected with a mouse-click. Using cursor keys is the
workaround.

Can anyone reproduce that?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: installing wine on F33 wants to downgrade packages

[Michael Schwendt]

On Fri, 23 Oct 2020 15:08:57 -0500, Anil Felipe Duggirala wrote:

> 2. Why is it downgrading my packages?

A likely cause is that you have come from an x86_64-only installation that
has had access to more recent package repositories than what you using
currently. Possibly because you've been assigned to different download
mirrors.

If you examine the repository contents, you will notice that the
version-release of the x86_64 and i686 builds of a multiarch package match
always, and both archs are published into a repo at the same time.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: testing update

[Michael Schwendt]

On Tue, 20 Oct 2020 11:02:23 -0700, Samuel Sieb wrote:

> > Do I need to dnf remove rpmfusion-free-release-32-1.noarch  
> 
> rpmfusion doesn't even have a testing repo.  You need to provide more 
> details.

Of course they still offer a testing repo for updates, and its .repo
file is included within the package shown above.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Strange gpg-agent processes with Fedora 32

[Michael Schwendt]

Has anyone seen the following before and possibly has found out what is going 
on?

Fedora 32 shows a gpg-agent process for each repo but with a non-existant 
".tmp" homedir.
Examples:

root2512  0.0  0.0 161028   900 ?Ss   11:20   0:00 gpg-agent 
--homedir /var/cache/PackageKit/32/metadata/fedora-32-x86_64.tmp/gpgdir 
--use-standard-socket --daemon
root2527  0.0  0.0 161028   896 ?Ss   11:20   0:00 gpg-agent 
--homedir /var/cache/PackageKit/32/metadata/updates-32-x86_64.tmp/gpgdir 
--use-standard-socket --daemon
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rkhunter --update fails.

[Michael Schwendt]

On Thu, 30 Jul 2020 16:55:53 -, home user wrote:

> [10:44:44] Checking file mirrors.dat [ Update failed ]
> [10:44:44] Info: Executing download command '/usr/bin/wget  -q -O 
> "/var/lib/rkhunter/rkhunter.upd.rJwBkFr06W" 
> http://rkhunter.sourceforge.net/1.4/programs_bad.dat 2>/dev/null'
> [10:44:45] Info: Download failed - 1 mirror(s) left.

Were you able to access those URLs manually with your favorite web browser
or download tool like wget/curl?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Steam erroneously marked as "Installed" in Gnome Software

[Michael Schwendt]

On Wed, 1 Jul 2020 01:44:32 +0530, Sreyan Chakravarty wrote:

> Hi,
> 
> I have NEVER installed Steam via Gnome Software on my notebook, in fact 
> I never installed it ever, but on Gnome Software it is marked as 
> "Installed".
> 
> Any way I can remove it from there ? That is mark it as "not installed" ?
> 
> When I click on "Remove" it says "no packages to remove" but it has 
> "Launch" and "Remove" options enabled. "Launch", does nothing.
> 
> Are there any command-line/debugging/troubleshooting options that I 
> should know about for Gnome Software Centre ? Seems like I haven't seen 
> the last of such annoying bugs.

Gnome Software uses PackageKit, so you could start with the command-line
tool "pkgcon":

  pkcon get-packages|grep ^Inst

would list "Installed" packages. And, of course, you are free to
investigate further with "rpm".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Every second GDM login fails

[Michael Schwendt]

On Sun, 28 Jun 2020 19:25:48 +0800, Ed Greshko wrote:

> Next time you do it, count the dots just to make sure all keystrokes are 
> being registered.
> 

I've done that before and have also clicked the "eye" icon to unhide the
entered passphrase, and it is shown correctly but will be rejected.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Every second GDM login fails

[Michael Schwendt]

Has anyone also had this before with GNOME Shell in Fedora 32?
It is new behavior compared with older releases of Fedora.

When I return to a locked screen, my usual habit is to press Return
and then to enter the passphrase. That fails even if unhiding the passphrase
and verifying that it has been entered correctly. The second time I enter
the passphrase, logging in works again. It seems as if the first Return press
breaks something.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Errors compiling

[Michael Schwendt]

On Tue, 23 Jun 2020 21:56:40 -0400, Frank wrote:

> I am trying to compile/install IceWm for my Fedora 32 installation. Ran 
> into some problems I have resolved, but
> I am stumped by these:
> 
> checking for strlcat... no
> checking for C++11 by default... yes
> checking for CORE... no
> configure: error: Package requirements (fontconfig xrender xcomposite 
> xdamage xfixes xext x11) were not met:
> 
> Package 'xdamage', required by 'virtual:world', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> DNF tells me all these programs are installed along with their 
> development files.
> 
> What am I missing ?

What does the "config.log" file tell about this?

Also, if a configure script check uses pkgconfig, it doesn't matter much
what DNF says. You would need to verify that the pkgconfig "*.pc" files
are included in a package and satisfy the requirements of what the
configure script is looking for.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: what was that on f30 ??

[Michael Schwendt]

On Tue, 23 Jun 2020 05:21:46 -0700, Jack Craig wrote:

> yesterday, something came  on screen asking for a repo update & authorised
> access.
> 
> seems to have broken repo access, any insights??

Rule of thumb in such a scenario would be to ask _before_ proceeding,
and to be precise about what exactly came up on screen.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: issue upde fc32 (sagemath)

[Michael Schwendt]

On Sat, 6 Jun 2020 20:33:30 +0200, Patrick Dupre wrote:

> Hello,
> 
> I get the following error message:
> dnf update
> Last metadata expiration check: 0:07:57 ago on Sat 06 Jun 2020 08:23:49 PM 
> CEST.
> Dependencies resolved.
> 
>  Problem 1: package polymake-singular-4.0.1-2.fc32.x86_64 requires 
> perl-interpreter = 4:5.30.2, but none of the providers can be installed
>   - cannot install both perl-interpreter-4:5.30.3-453.fc32.x86_64 and 
> perl-interpreter-4:5.30.2-452.fc32.x86_64

You could have taken a look at the polymake package source, which
mentions a test update that rebuilds against the newer Perl release:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-7b023f0541
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: perl-Math-GSL

[Michael Schwendt]

On Wed, 3 Jun 2020 11:21:43 +0200, Patrick Dupre wrote:

> I could not compile perl-Math-GSL-0.40 because this package does not deal
> with gsl 2.6
> Thus, I installed gsl 2.5 independently of gsl 2.6 (gsl-2.6-2.fc32.x86_64)
> and I was able to build the rpm package which requires libgsl.so.23
> 
> I put a link to this library (provided by gsl 2.5) in /usr/lib64
> and run ldconfig
> 
> But
> dnf install 
> /home/pdupre/rpmbuild/RPMS/x86_64/perl-Math-GSL-0.40-1.fc32.x86_64.rpm
> 
> is not happy
> Last metadata expiration check: 1:53:24 ago on Wed 03 Jun 2020 09:26:44 AM 
> CEST.
> Error: 
>  Problem: conflicting requests
>   - nothing provides libgsl.so.23()(64bit) needed by 
> perl-Math-GSL-0.40-1.fc32.x86_64
> 
> 
> How can I bypass this issue?

Unless you have created and installed an RPM package for GSL 2.5, no RPM
dependency data exists for libgsl.so.23()(64bit). If you are brave and
curious, you could choose to ignore dependencies by installing with
"rpm --nodeps ...", but be warned since it's quite a big hammer.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: build package

[Michael Schwendt]

On Tue, 2 Jun 2020 20:08:16 +0200, Patrick Dupre wrote:

> Can I simulatenously install GSL 2.5 and 2.6?
> 
> or remove GSL 2.6 and intall GSL 2.5?
> 

The library SONAME has changed from libgsl.so.23 to libgsl.so.25, but
libgslcblas.so.0 hasn't changed, and the Fedora packages would conflict
anyway because they include executables and other files. Therefore you
cannot simply install the old Fedora packages of gsl-2.4 and gsl-2.6
in parallel.

Depending on your usage scenario, you could compile GSL 2.4 yourself
and install it into a private path, then build other stuff (like Perl
modules) against it and override $LD_LIBRARY_PATH whenever you want the
runtime linker to find the old GSL libs.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: build package

[Michael Schwendt]

On Tue, 2 Jun 2020 12:36:03 +0200, Patrick Dupre wrote:

> Hello,
> 
> I am rebuilding the perl packages that I need.
> perl-Math-GSL-0.40.tar.gz
> 
> 
> rpmbuild -bb perl-Math-GSL.spec 
> 
> gives an error:
> Checking for GSL using gsl-config
> Found GSL 2.6 (via gsl-config) installed in /usr
> Checking if gcc supports "-Wall"...yes
> Checking if gcc supports "-Wno-sometimes-uninitialized"...yes
> Checking if gcc supports "-Wno-unused-function"...yes
> Checking if gcc supports "-Wno-unused-value"...yes
> Checking if gcc supports "-Wno-unused-function"...yes
> Checking if gcc supports "-Wno-unused-variable"...yes
> Checking if gcc supports "-Wno-gnu"...yes
> Checking if gcc supports "-g"...yes
> unsupported version: 2.6 at Build.PL line 77.
> error: Bad exit status from /var/tmp/rpm-tmp.I4k1Cb (%build)
> 
> Checking on the Build.PL file;
> it seems to be due to
> 
> my $ver2func = Ver2Func->new( $gsl_conf->{gsl_version} );
> 
> 
> The same version of perl-Math-GSL compiled fine with fc30.
> (same version of cpanspec)
> Now the gsl version is 2.6 (2.4 before)
> 
> Do I need to recompile gsl ?

No, that wouldn't change anything as long as GSL 2.5 is the maximum
version that is supported by Ver2Func. You could check the release notes
of GSL 2.6 to figure out how compatible it is.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Michael Schwendt]

On Tue, 02 Jun 2020 19:29:51 +0930, Tim via users wrote:

> Patrick Dupre wrote:
> >> This has been solved by
> >>
> >> rpm -e perl-PDL-LAPACK-0.12-1-1.fc30.x86_64  
> 
> Michael Schwendt:
> > The good old "rpm -e perl-PDL-LAPACK" would have been enough for the
> > most common use case.  
> 
> Don't you have to do up to the first dot?
> 
> i.e.  rpm -q perl-PDL-LAPACK-0

No. The simplified package naming scheme here is N-V-R.A as in
"Name-Version-Release.Arch", and specifying the name would be enough when
only a single package of that name is installed. Even if the name included
one or more characters like '-', '_' or '.'. In dependencies related
output you will also see N:E-V-R.Arch if the Epoch tag is set for a
package, but when using rpm/dnf, specifying the Epoch is only needed in
corner-cases.

Putting a numerical "Version" and '.' characters into the package name can
break quite some tools and scripts that strictly expect a simple N-V-R scheme.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Michael Schwendt]

On Tue, 2 Jun 2020 00:25:59 -0700, Samuel Sieb wrote:

> >> rpm -e perl-PDL-LAPACK-0.12-1-1.fc30.x86_64  
> > 
> > The good old "rpm -e perl-PDL-LAPACK" would have been enough for the
> > most common use case.  
> 
> Maybe you missed the original message where he tried the equivalent of 
> that with dnf.  There's something funny with the package name.  I'm 
> guessing that the version is part of the name for some reason.

Then whoever created that package needs to be told. ;-)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Michael Schwendt]

On Mon, 1 Jun 2020 23:12:06 +0200, Patrick Dupre wrote:

> This has been solved by
> 
> rpm -e perl-PDL-LAPACK-0.12-1-1.fc30.x86_64

The good old "rpm -e perl-PDL-LAPACK" would have been enough for the
most common use case.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Mon, 1 Jun 2020 12:09:36 -0500, Roger Heflin wrote:

> When the policy is not being followed and/or not enforced it means
> nothing.  Only someone who is in love with
> the policy would say otherwise and actively defend it.

You're still not getting it.

> I am going to guess you helped write large parts of the policy
> and that is why you defined it.

???

> Yes, lets enforce the policy against
> the everyone until you have no community.

See above. You're not getting it. You talk about "enforcing" something,
you preach stagnation. That isn't helpful and not a way forward for Fedora.

> Since there are packages going unmaintained it not like they are that
> easily replaceable.

???

> It is you as a "insider"
> that seems to be denying the "perfect" policy is not functioning as
> often as you like and not admitting that it can
> be made to work with the staff you had.  If the maintainer for the
> kernel package is not following it,
> I doubt many are following it.

Please stop guessing. It can't generalized like that. Quite obviously,
there are _many_ packages that are much easier to maintain than the kernel
package (with its ticket linked earlier in this thread). There are
different aspects of maintenance. Handling bug reports is just one of many
tasks.

> And while you are calling me an outsider, I have been using what
> became fedora for years before the first fedora
> version was released, and have been using it almost every version since then.

The question about your "background" was necessary because it becomes
apparent that you comment on things as one who either doesn't know how
things work at the Fedora Project (or how things are supposed to work) or
you deliberately ignore it. You don't seem to care about project policies
and guidelines, and you brush aside what's there as a base. You even ignore
what different levels of maintenance are needed for different packages.

> On the fedora side we should probably be directing anyone with
> software bugs to upstream.

Should? Probably? And you expect upstream to not be understaffed,
especially not if being flooded with bug reports which may be
distribution-specific?

> Don't get me started about [...]

Thread is closed for me.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Looking for a .so

[Michael Schwendt]

On Sun, 31 May 2020 09:02:51 -0700, Geoffrey Leach wrote:

> On Sun, 31 May 2020 16:29:54 +0200
> Andras Simon wrote:
> 
> > 2020-05-31 16:08 UTC+02:00, Geoffrey Leach:  
> > > I have a build that references '-lz'. This fails, because gcc
> > > expects to find libz.so in the library search path. The package
> > > that installs zlib, zlib-1.2.11-21.fc32.x86_64 does not create a
> > > symlink from libz.so.1.2.11
> > 
> > I think that you need to install zlib-devel.
> > 
> > Andras  
> 
> Well, I would have sworn ... but no. Installing fixed the problem.
> Thanks.

"Sworn" what? It's like that for a very, very long time. The .so symlink
is an unversioned build-time file. Hence it's stored in the zlib-devel
subpackage that is needed only when building/developing something based on
zlib. And whereas it can make sense to dlopen that .so at runtime, code that
does that would need to make sure it can handle any API/ABI of the library
the symlink may point at.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Sat, 30 May 2020 16:42:10 -0500, Roger Heflin wrote:

> The policy means nothing when

Only an "outsider" would say that. That policy has been refined multiple
times since the fedora.us era with its strict QA policies. That policy is
also reason why potential "maintainers" shy away from the community
project, because as volunteers they can't tell whether they would be able
to meet the requirements. I could point you at the related "non-responsive
maintainer policy", but so far you aren't listening.

> the staffing is not there to actually do the tasks.

Sweet how you try to dance around the problem. Where bugzilla components
are literally flooded with tickets, automation would be the way to go.
That has been pointed out before. Meaningful, early responses that give
bug reporters some guidance on where and how they could escalate an issue,
where they could discuss an issue in order to gather more details and to
confirm a problem, and and and.

> And clearly there is limited staffing.  And if they are a volenteer
> then tell them they arent doing their job and kick them out.  Repeat until
> there is no community and you have no staff.

Key components are still maintained by Red Hat. That is an essential and
important contribution to this project. Offer a distribution that doesn't
satisfy users, and you lose (or reduce) the user part of the community
including most of the guinea pigs.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Sat, 30 May 2020 11:14:22 -0500, Roger Heflin wrote:

> You really need to understand the devs actual motivations.   And your
> are attributing things to Fedora devels that are being funded outside
> of the Fedora community.

Please, think outside the box. It isn't helpful to the discussion, if
you are stuck with your own guesswork of how it may or may not work on
the distribution maker's side. There are actual policies!
https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Sat, 30 May 2020 07:33:04 -0500, Roger Heflin wrote:

> My background is I have been used Fedora since Core 1, and prior to
> that started with Redhat 5/6/7/8/9 and managed (or was technical lead
> for a team) with >1000 installed running combinations of RHEL, Centos,
> non-enterprise Redhat/Fedora, and/or SLES since around 1998, in
> addition to running a few home systems.

So, that confirms my assumption. For reasons not known yet you ignore why
non-commercial Linux distributions exist and how they try to appeal to a
potential target audience. That is really odd, because you have been a
distribution user already when Red Hat Linux was not a community project
yet and only offered unsatisfying experiments like Red Hat Contrib before
the creation of the independent fedora.us project.

> The distribution also remove a signification number of rpms so only
> cares about supporting maybe 1/2 or less (and that is for the rpms in
> the fedora repos).

??? Where do your numbers come from? Even old Red Hat Linux doubled its
number of source (!) packages from 4.x to 8.0. And the size of the package
collection (in terms of source rpms) has grown a lot to something like
factor 30-50 with/without taking into account 3rd party repositories.

> A lot of single reporter bugs are often something specific odd the
> person is doing wrong, and it takes a lot of time to work through the
> reports to figure out which are which.

Which is not the point.

The point is that submitted bug reports (particularly those that have been
commented on by the bug reporter instead of only dumping data into
bugzilla via ABRT) ought not end up in nirvana. And if somebody decides
that it's a corner-case issue with nobody to look into it due to
insufficient manpower, the automated response could offer some guidance
for the bug reporter.

> I don't believe abrtd collects kernel panic by default, and kernel
> dumps also aren't configured by default.

Have you never noticed the "[abrt]" prefix in the bug summaries?
https://bugzilla.redhat.com/buglist.cgi?component=kernel=Fedora
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Cannot upgrade gnutls with dnf (transaction problems)

[Michael Schwendt]

On Sat, 30 May 2020 09:33:11 +0200, Joachim Backes wrote:

> Error: Transaction test error:
>    file /usr/share/doc/manual/gnutls.html conflicts between attempted 
> installs of gnutls-devel-3.6.13-4.fc32.i686 and 
> gnutls-devel-3.6.13-4.fc32.x86_64
>    file /usr/share/info/gnutls.info-3.gz conflicts between attempted 
> installs of gnutls-devel-3.6.13-4.fc32.i686 and 
> gnutls-devel-3.6.13-4.fc32.x86_64
>    file /usr/share/info/gnutls.info.gz conflicts between attempted 
> installs of gnutls-devel-3.6.13-4.fc32.i686 and 
> gnutls-devel-3.6.13-4.fc32.x86_64
> 
> Anybody has similar problems?

Multilib packaging related conflicts.

Those have been reported in bugzilla already. Click on "Issues" here:
https://src.fedoraproject.org/rpms/gnutls
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Fri, 29 May 2020 21:08:10 -0500, Roger Heflin wrote:

> The maintainers are for the most part about "packaging" kernels.
> They rarely seem to ever work on kernel bugs, nor have the time to do
> such investigate even if they have the time.

If that were true, something would be even more wrong in Fedora land,
since in that case ABRT ought not point at bugzilla.redhat.com by default
for kernel issues. Last time I had a look, Fedora's kernel package
included around a hundred patches. Fedora's kernel is also where things
are tested for RHEL, and therefore any problem report could serve as an
early warning.

> They are not here to answer you questions, and they are overworked.
> If someone is paying them, whoever that is, is setting their
> priorities and their priorities are not to do their job.  If they
> aren't paid well then if they help some ok, but no one is owed a
> response.

??? I don't know your background with regard to the Fedora Project, but
what you write here makes no sense from a distribution maker's perspective.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Fri, 29 May 2020 13:56:34 -0500, Roger Heflin wrote:

> I don't believe the kernel.org developers work out of the fedora
> bugzilla (or any distro's bugzilla), so no one who knows anything is
> likely to find and/or see the bug.
>
> To get a kernel developer you would need to at least post a summary to
> the kernel subsystem list if you know which subsystem or the main
> kernel if you don't.

This makes no sense, given that Fedora introduced ABRT, the automatic bug
reporting tool. Distribution users enter their crash reports into the
distribution's bug tracker, of course, assuming it is the primary point of
contact and that bug reports are appreciated and won't be lost. And in this
case, the bug reporter didn't only dump an uncommented backtrace into
bugzilla.

> And the kernel.org guys do not care about any testing done on a fedora
> delivered kernel as they don't know what code is in it, so you would
> need to install a kernel.org kernel and bot from it and verify you
> have the issue on the newest released one.

??? Which is why Fedora users assume that Fedora developers know the right
thing to do in case of problems, such as suggesting that it could be
fruitful to discuss a problem on some specific mailing-list or where to
report it instead.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Thu, 28 May 2020 21:19:34 -0700, John M. Harris Jr wrote:

> > > https://bugzilla.redhat.com/show_bug.cgi?id=1742960
> > > 
> > > Lately all my bug reports tend to go like this.  
> > 
> > 
> > Why don't you try to reproduce issues with Fedora 31, 32 or Rawhide
> > and then reassign the tickets accordingly?  
> 
> It's quite possible that Suvayu Ali is one of the many users that cannot 
> install Fedora 31, because it doesn't work on their hardware. Fedora 30 was 
> the last release to support i686, so many users are now stuck there forever, 
> unless they move to another distro entirely.

Clearly the ticket is about x86_64, so no, i686 is beyond the scope of
this thread. But when talking about i686, I doubt it is "many users".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Thu, 28 May 2020 18:08:48 +0930, Tim via users wrote:

> Perhaps there should be an automated culling of participants.  If you
> step up the plate to say you'll maintain a package, but don't, *you*
> get dumped from bugzilla.

Please let's not create a thread of doom.

You can't seriously suggest blocking kernel maintainers from bugzilla just
because they don't have the manpower to take a look at every ticket and
perform meaningful, helpful triaging. Some key components are literally
flooded with bug reports. In order to deal with the number of tickets,
using scripts is an obvious thing to do. Yet it isn't done in a proper and
OS user-friendly way.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Thu, 28 May 2020 07:50:16 +, Suvayu Ali wrote:

> It took so long, that the bug report became irrelevant.  I have since
> moved to a different country, with a different job, and don't have
> access to the original machine.  In fact, as mentioned in the bug, I
> could reproduce a similar issue in similar hardware, with Fedora 31.

There is more to it.

Assuming you would have reassigned the ticket to Fedora 31 in response to
the "MASS BUG UPDATE" notification on 2020-03-03, without any clear
and concise reply you cannot tell whether you would be testing a potentially
fixed kernel or just a random kernel rebase that may or may not fix it.
Furthermore, you don't even know whether the reported problem is tracked
anywhere where somebody would look at it _eventually_. The ticket status
is entirely unclear. "Please test [...] and let us know [...]", but nobody
has responded to the feedback.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Wed, 27 May 2020 15:42:39 -0400, Ben Cotton wrote:

> On Wed, May 27, 2020 at 3:23 PM Michael Schwendt wrote:
> >
> > The fundamental problem here is that it has taken a very long time for
> > somebody to respond to the bug reporter. There has been no guidance and
> > no hint whether anyone "somewhere" would be interested in looking into
> > this issue.
> >  
> Exactly. And growing the contributor community is how we can solve that 
> problem.
>

How?

It seems to be you haven't even taken a brief look at the ticket at all.

The bug reporter has contributed more than only dumping a kernel backtrace
into bugzilla. The willingness to provide details or to test potential
fixes has been demonstrated. And yet nobody has shown any willingness to
comment on the actual problem or to point at external place that might be
a suitable place where to discuss it and where interested kernel
developers could give some guidance on how to proceed.

There have always been components with a large number of bugzilla tickets
without a response, but Fedora has turned it into a "man versus machine"
competition. Which is unfortunate. First of all, those automated responses
come _much_ too late. After months, most users have lost patience and have
given up. And for the patient users, the second time somebody gets an
automated response that only threatens with closing a ticket _again_, it
will be a "WTF?" moment and raise motivation to look for a different OS.

Automation is not a bad thing, but there ought to be a clear message that
tells people about the expectations to get a response on the way to a
potential fix or _how_ they could contribute.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Wed, 27 May 2020 12:07:35 -0400, Ben Cotton wrote:

> On Wed, May 27, 2020 at 4:30 AM Suvayu Ali wrote:
> >
> > Lately all my bug reports tend to go like this.  Are others having the
> > same experience?  
> 
> I understand the frustration. My bugs get closed EOL, too. For what
> it's worth, 3633 bugs were closed EOL for Fedora 30. This is
> considerably lower than Fedora 29 (4958) and Fedora 28 (4681).
> 
> The Fedora Join SIG is here to help new contributors get started if
> you're interested:
> https://docs.fedoraproject.org/en-US/fedora-join/index.html

That process would not have helped with this kernel bugzilla ticket
opened in 2019-08-18. But the response in March 2020 suggested reproducing
the issue with Fedora 31 and reassigning the ticket, if the issue is still
reproducible. That has not been done.

The fundamental problem here is that it has taken a very long time for
somebody to respond to the bug reporter. There has been no guidance and
no hint whether anyone "somewhere" would be interested in looking into
this issue.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Wed, 27 May 2020 08:18:48 +, Suvayu Ali wrote:

> > As of the 26th of May 2020, Fedora 30 has reached its end of life for  
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1742960
> 
> Lately all my bug reports tend to go like this.

Why don't you try to reproduce issues with Fedora 31, 32 or Rawhide
and then reassign the tickets accordingly?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Upgrade of F30 to F31 Appears to Have not Worked Correctly

[Michael Schwendt]

On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:

> Hi,
>      I have just upgraded to F31 from F30 using dnf system-upgrade 
> download --releasever=31. Before I did the upgrade I updated F30 to the 
> latest maintenance level.
>      When I booted into Gnome on F31 there was no activities menu to be 
> able to launch any application, the only way I could launch applications 
> (if I knew the application command) was to use alt-f2.

Did you try what happens if you create and use a new user account?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Is This Windows?.....

[Michael Schwendt]

On Mon, 30 Dec 2019 17:57:42 +, Richard Hughes wrote:

> I was the person triaging these bugs for about the last decade. If you
> have a failure rate of 1/1, and you have millions of users, you
> have tens of angry users EVERY DAY filing bugs that their root
> filesystem exploded or that their GUI application crashed while it was
> updated in the background, losing all their work. Offline updates has
> reduced this failure rate by about 3 orders of magnitude.

Active GUI applications crashing during updates of dependencies
is a _real_ problem indeed, only made worse by users dumping ABRT crash
data into bugzilla without even mentioning the yum/dnf update they've done
when the app crashed.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Upgraded F31 system still believes it is living in the past, on F30!

[Michael Schwendt]

On Thu, 26 Dec 2019 19:58:45 -0600, Ranjan Maitra wrote:

> Thanks for pointing this out. Actually, I tried installing the RPMs but got 
> the message that all of them were installed So, I reinstalled
> 
> sudo dnf reinstall 
> https://kojipkgs.fedoraproject.org//packages/fedora-repos/31/1/noarch/fedora-repos-31-1.noarch.rpm
> 
> and this appears to have cleaned out the F30 elves...

You should/could have done a full investigation, starting with a look
at the .repo files and which package they come from. It's too late now,
but it would have turned up something about your "fedora-repos" package
and possibly duplicates.

$ rpm -qf /etc/yum.repos.d/*
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
fedora-repos-31-1.noarch
[...]
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: f31 : pkgconfig.exists( 'uuid-dev' ) false but installed

[Michael Schwendt]

On Tue, 26 Nov 2019 15:44:21 +0100, Adrian Sevcenco wrote:

> > Why are you looking for 'uuid-dev'?  It's just "uuid".  
> sorry this is a typo .. yes i (they) check for uuid
> https://github.com/xrootd/xrootd/blob/master/packaging/wheel/setup.py#L61
> 
> python3
> Python 3.7.5 (default, Oct 17 2019, 12:16:48)
> [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>  >>> import pkgconfig
>  >>> print( pkgconfig.exists( 'uuid' ))  
> False
> 
> Can anybody else just do this simple test and post a feedback?
> I would like to know if this is a fedora problem or just mine..

$ rpm -q --provides uuid-devel
pkgconfig(ossp-uuid) = 1.6.2
uuid-devel = 1.6.2-45.fc31
uuid-devel(x86-64) = 1.6.2-45.fc31
$ rpmls uuid-devel|grep pkg
-rw-r--r--  /usr/lib64/pkgconfig/ossp-uuid.pc

According to the pkgconfig .pc files contained in that -devel package,
you need to check for "ossp-uuid". Don't guess pkgconfig dependency names.
Verify them by examining packaged files.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Time to refresh my hardware

[Michael Schwendt]

On Wed, 09 Oct 2019 23:53:39 -0400, Sam Varshavchik wrote:

> And Nvidia's proprietary driver is another thing I'd rather not deal with.  
> it seems that most vendors ship new Nvidia chipsets that x.org lists as not  
> supported.

One issue with Nvidia chipsets is that Fedora works fine without the
proprietary driver but only after you've rebooted from Windows. It's
like the nouveau driver fails to initialise the hardware.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: F30 GNOME Shell not usable anymore / OsLookupColor(): Segmentation fault

[Michael Schwendt]

On Mon, 29 Jul 2019 23:12:55 +0200, Michael Schwendt wrote:

> Dunno when and why this started recently, but I'm hit hard by segfaults
> taking down GNOME Shell.
> 
> Bugzilla knows tons of duplicate bug reports about it, dating back to
> F29 apparently:
> https://apps.fedoraproject.org/packages/xorg-x11-server/bugs/all
> 
> OsLookupColor(): Segmentation fault at address 0x...
> 
> 
> Has anyone seen this earlier and knows a workaround perhaps?
> F30 isn't usable anymore due to those crashes.

Seems to be specific to Wayland. Choosing Xorg at the login screen, so far
I've not been hit by those crashes again.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

F30 GNOME Shell not usable anymore / OsLookupColor(): Segmentation fault

[Michael Schwendt]

Dunno when and why this started recently, but I'm hit hard by segfaults
taking down GNOME Shell.

Bugzilla knows tons of duplicate bug reports about it, dating back to
F29 apparently:
https://apps.fedoraproject.org/packages/xorg-x11-server/bugs/all

OsLookupColor(): Segmentation fault at address 0x...


Has anyone seen this earlier and knows a workaround perhaps?
F30 isn't usable anymore due to those crashes.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Equalizer for pulseaudio

[Michael Schwendt]

On Sat, 27 Jul 2019 13:13:22 -0500, SternData wrote:

> I just did a clean install of F30 on this system and am trying to get
> things back to work.
> 
> I've got pulseeffects installed because the install of
> pulseaudio-equalizer fails
> 
> $ sudo dnf install pulseaudio-equalizer
> Error:
>  Problem: conflicting requests
>   - nothing provides ladspa-swh-plugins needed by
> pulseaudio-equalizer-2.7-21.fc29.noarch
> (try to add '--skip-broken' to skip uninstallable packages)

See http://bugz.fedoraproject.org/ladspa-swh-plugins

> This is what's available searching on ladspa

Can't be true, because a simple "dnf search ladspa" returns all the
name matches, particularly the packages starting with "ladspa".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: How do I de-blur a picture?

[Michael Schwendt]

On Tue, 23 Jul 2019 14:36:06 -0700, ToddAndMargo via users wrote:

> On 7/23/19 9:45 AM, Kam Leo wrote:
> > Just asking, have you tried the tools in GIMP?  
> 
> Yes.  Does not help.

Which is what the end of the article sums up.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Firmware?

[Michael Schwendt]

On Mon, 22 Jul 2019 20:17:52 - (UTC), Beartooth wrote:

>   When 'dnf upgrade' gives me a list of several items labeled 
> 'firmware', does that mean any or all of them are aimed at my specific 
> hardware? Or just at machines known to run Fedora? 

The latter. You can examine the package descriptions of those firmware packages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: Booting impossible

[Michael Schwendt]

On Tue, 25 Jun 2019 19:20:32 +0200, Patrick Dupre wrote:

> Hello,
> 
> The situation is becoming worst and worst.
> I tried an grub2-install /dev/sda

When did you run that command? Within a running working installation?
And why did you run it?

> Now, I cannot boot at all.
> I just enter in to a grub menu from here I am stuck.
> Can I collect a bit of help?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Fri, 14 Jun 2019 23:38:56 +0200, Patrick Dupre wrote:

> perl-Tk-JBrowseEntry-5.22-1.fc30.noarch

> The solutions that I found are:
> 1) add Provides: perl(Tk::JBrowseEntry) = %{version}-%{release}
> in perl-Tk-JBrowseEntry.spec
> or
> 2) remove 
> BuildRequires:  perl(Tk::JBrowseEntry) >= 4.63
> in
> perl-Tk-JFileDialog.spec

These two steps contradict eachother.

The package created by step 1 meets the build requirements of the package
you want to build. 5.22 >= 4.63, so it is not necessary to remove the
BuildRequires tag in step 2.

In step 1, prefer "BuildRequires: perl-generators" instead of adding
the "Provides" tag manually. A Perl Module package may include more
than a single module.

> In my opinion, I should not have to edit the .spec files

If the output from cpanspec were perfect *and* would meet Fedora's
Packaging Guidelines, too, you would not need to.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Thu, 13 Jun 2019 23:09:58 +0200, Patrick Dupre wrote:

> Maybe, however, some perl packages require packages with a version
> number higher than a certain value.
> Thus, if the Provides/Requires instructions are not set properly,
> all the packages requiring other packages fail, either at the build or
> installation step.

That doesn't make any sense at all.

The Provides/Requires dependencies are set automatically at build-time.
One package _provides_ exactly what is found within in.
Another package _requires_ exactly what it uses in its code.
These automatic dependencies are correct at build-time, if and only if
none of the providing packages is taken away or replaced with something
incompatible (such as failing to satisfy >= requirements due to API changes
or runtime behaviour changes).

If a Perl Module included in an RPM package is version X.Y, the package
must not be used, if a package requires a version higher than X.Y. The
package metadata must only provide exactly the version of the Perl Module
that is included. That is why perl-generators is used to create these
dependencies at build-time. If a newer version of the Perl Module is
needed, an update to the package collection may be needed.

If you hack a spec file with manually added "Provides:" for a higher
version, you are working against the entire system of package dependencies.

> In my opinion, all the perl packages need to be checked
> to go through the distribution without requiring to use
> capnspec by the final user.

That is entirely unrelated to this mailing-list thread. It could be that
there are perl-* RPM packages included in Fedora's package collection,
which are missing the perl-generators build requirement and which are
missing "perl(A::B) = version" provides. If that is the case, file a bug
report. Or step up as co-maintainer, if you depend on such packages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Wed, 12 Jun 2019 22:43:24 +0200, Patrick Dupre wrote:

> Hello,
> 
> Again, I am not sure to understand:
> 
> cpanspec --add-buildrequires perl-generators Tk-JBrowseEntry-5.22.tar.gz
> 
> only add:
> BuildRequires:  perl-generators
> in the .spec file
>
> which does not help.

It helps with automatic creation of Perl Module dependency metadata in
the built packages. It does not add any Provides/Requires to the spec file,
because that would be the wrong thing to do.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Tue, 11 Jun 2019 21:13:10 +0200, Patrick Dupre wrote:

> I am not sure to take the point:

You focus on something else.

> I can run
> cpanspec --add-buildrequires perl-generators Tk-JBrowseEntry-5.22.tar.gz 
> --add-provide "perl(Tk::JBrowseEntry)  %{version}-%{release}"
> 
> If it is correct.

It isn't. You are not supposed to add those Provides yourself.
BuildRequires perl-generators would do it inside the built packages.
Adding both makes no sense.

> Why is it not automatic?

Other have answered that. I only tell you what needs to be present within
the spec file for the built package dependencies to be added on-the-fly.

Instead, you expect the cpanspec generated file to be perfect, which is
a different issue.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Mon, 10 Jun 2019 17:45:23 +0200, Patrick Dupre wrote:

> Sorry, when I run
> cpanspec Tk-JBrowseEntry-5.22.tar.gz 

I referred to _build time_ creation of inter-package dependencies.
The step when rpmbuild adds Requires/Provides to the built packages.
You are not supposed to hack a spec file as to add them manually for
Perl Modules installed in Perl's paths for modules.

> Is there something in my .spec generation?
> 
> Anyway, addition:
> Provides: perl(Tk::JBrowseEntry) = %{version}-%{release}
> 
> fixes this issue

Instead, use "BuildRequires: perl-generators" at build-time.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Mon, 10 Jun 2019 15:35:22 +0200, Patrick Dupre wrote:

> Provides: perl(Tk::JBrowseEntry) = %{version}-%{release}
> 
> seems missing in the .spec file

No. These are automatically created Provides/Requires for Perl Modules.
You need to work with a package that _really_ includes and "Provides"
the Tk:JBrowseEntry module with a sufficient version. If such a package
is installed in the build environment, but doesn't contain the "Provides"
tag, you will need to take a closer look at that package.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: rpmbuild

[Michael Schwendt]

On Sun, 9 Jun 2019 08:38:05 -0700, Gordon Messmer wrote:

> On 6/9/19 7:29 AM, Patrick Dupre wrote:
> > How can I make a rpmbuild and keep the compiled files?  
> 
> 
> Have you tried "rpmbuild --noclean"?

Alternatively, end the building after the %build stage:

  rpmbuild -bc foo.spec

And you will find the compiled files in the build dir. If you want
to keep the installed files, use:

  rpmbuild -bi foo.spec

Then find that the buildroot directory has been installed to.

Also notice the --short-circuit commands covered in the manual page
in case you want to modify individual spec file sections and test
the changes quickly.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: gnuplot

[Michael Schwendt]

On Sun, 9 Jun 2019 18:31:51 +0200, Patrick Dupre wrote:

> I cannot find a gnuplot-latex for fedora 30, and I cannot find a 
> gnuplot-latex.
> Previously, I compiled at the same time as gnuplot (gnuplot-wx, etc..), see
> point 1).

# dnf list gnuplot\*
Available Packages
gnuplot.x86_64   5.0.6-11.fc30fedora
gnuplot-common.x86_645.0.6-11.fc30fedora
gnuplot-doc.noarch   5.0.6-11.fc30fedora
gnuplot-latex.noarch 5.0.6-11.fc30fedora
gnuplot-minimal.x86_64   5.0.6-11.fc30fedora
gnuplot-py.noarch1.8-27.fc30  fedora
gnuplot-wx.x86_645.0.6-11.fc30fedora

So, the packages are available, and that means there is a src.rpm, too,
which you can modify to add extra features.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: xmms2 fails to update

[Michael Schwendt]

On Mon, 3 Jun 2019 12:00:01 -0400, Temlakos wrote:

> Now when I tried to install other xmms2-related files, the system simply 
> didn't install them--especially if they came from RPMfusion. Why not? 
> May I assume that the Fedora System xmms2 package now has everything I 
> need to play just about any sound file I download?

This is Open Source Software. Even if you don't want to examine the
Source RPM package contents, you can query the changelog of the binary
packages. Especially if the packages are installed on your computer.
Example: rpm -q --changelog xmms2|less
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: xmms2 fails to update

[Michael Schwendt]

On Sun, 2 Jun 2019 19:30:01 +0800, Ed Greshko wrote:

> >> Transaction check error: file /usr/lib64/xmms2/libxmms_mad.so from install 
> >> of
> >> xmms2-0.8-60.fc29.x86_64 conflicts with file from package 
> >> xmms2-mad-0.8-24.fc29.x86_64
> >> Error Summary -  
> >
> > Comments? Suggested resolutions?
> >  
> 
> xmms2 is a fedora package
> xmms2-mad is an rpmfusion package 
> 
> Wait until rpmfusion has caught up with fedora.

No, Fedora should have covered this with an "Obsoletes" tag, so "xmms2"
replaces "xmms2-mad", since it contains the "mad" based plugin now.
It is a packaging mistake not to do that.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Claws Mail 3.17.1 with experimental TLS SNI support

[Michael Schwendt]

For Fedora 29 and Rawhide:
https://copr.fedorainfracloud.org/coprs/mschwendt/claws-mail-testing/

If upgrading to these packages, be sure to upgrade also "libetpan"
and not only the "claws-mail*" packages.

As a side-note, the Dillo based HTML rendering plugin package
"claws-mail-plugins-dillo" is back with this release.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: need iptables.conf syntax

[Michael Schwendt]

On Sun, 26 Aug 2018 15:49:06 -0700, ToddAndMargo wrote:

> I am told elsewhere that this is not the proper syntax:
> 
> /etc/modprobe.d/iptables.conf add
> 
>   nf_conntrack_ftp ports=21
> 
> Anyone know what the right syntax is?

man modprobe.d
 and
man modprobe.conf
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org

Re: md5 files - how to use them ?

[Michael Schwendt]

On Wed, 30 May 2018 06:49:46 +0300, Angelo Moreschini wrote:

> I downloaded this file to the link
> http://www.eclipse.org/windowbuilder/download.php.
> There are nothing other that files .zip,MD5.
> 
> 
> Perhaps I misunderstand the instruction because my poor English ?
> That can be.
> 
> But there I could get only a file .zip,MD5.  and no one .zip file.

Of course there is a .zip file on that page, and you've downloaded it before.
If your download is damaged, try again. It works here:

$ md5sum WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip
d876735181a68126b918735859665fd7  WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip

$ cat WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip.MD5 
d876735181a68126b918735859665fd7 
*/shared/tools/windowbuilder/stage/WB/WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org/message/GQGJ2FQAQCCV46YXPDQWJCRWEBKFQHWY/

Re: md5 files - how to use them ?

[Michael Schwendt]

On Tue, 29 May 2018 17:05:33 +0300, Angelo Moreschini wrote:

> I tried this :
> 
> commad
> 
> output
> 
> 
> *md5sum *
> 
> ./WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip
> 
> d06dc1c7000dc910ce4642fc7b09c312 ./WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip
> 
> *cat* ./WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip.MD5
> 
> d876735181a68126b918735859665fd7
> */shared/tools/windowbuilder/stage/WB/WB_v1.8.0_UpdateSite_for_Eclipse4.5.zip
> 
> 
> where I can find the plug-in to use on eclipse  ?

Let's not turn this into a riddle, please. Where did you download the two
files you refer to above? You've downloaded a .zip file already. If it
doesn't pass the MD5 check, perhaps it has been damaged/truncated during
download. You could use a program like "zip" to test integrity of the
file. Or perhaps the MD5 file is out-of-date. In that case you may need
to ask the publisher of those files.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org/message/LS4ZAQ5UJ34JT5ZW723435GNSEWWSRIT/

Re: qucs simulation fail on missing library

[Michael Schwendt]

On Tue, 8 May 2018 08:03:46 -0700, pelican wrote:

> Although I did have a problem compiling freehdl it is available in the
> repos.

You should be able to fetch the src.rpm and rebuild that one, adding the
.la files to the package.

>  I did notice while checking  /usr/lib64 that there are a few examples in
> fc27
> 
> ls *.la
> 
> libguile-gnome-gobject-2.la  libQt5GlxSupport.la
> libgwrap-core-runtime.la libQt5InputSupport.la
> libgwrap-guile-runtime.lalibQt5KmsSupport.la
> libQt5AccessibilitySupport.lalibQt5LinuxAccessibilitySupport.la
> libQt5Bootstrap.la   libQt5OpenGLExtensions.la
> libQt5DeviceDiscoverySupport.la  libQt5PlatformCompositorSupport.la
> libQt5EglSupport.la  libQt5ServiceSupport.la
> libQt5EventDispatcherSupport.la  libQt5ThemeSupport.la
> libQt5FbSupport.la   libQt5UiTools.la
> libQt5FontDatabaseSupport.la

There is a packaging policy about not including .la files, but there may
be exceptions, such as software using a libtool based runtime linker that
needs those .la files. Sometimes package reviewers and/or packagers make
mistakes. If the corresponding package spec files don't tell why these
.la files are included, opening bugzilla tickets about these would be the
thing to do.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: qucs simulation fail on missing library

[Michael Schwendt]

On Mon, 07 May 2018 14:54:59 -, patrick  stanistreet wrote:

> I have been trying out a package  qucs   for electronic circuit design and 
> simulation. 
> I can use the software to create a simple design but the simulation fails on 
> a missing
> library.I tried compiling qucs from source and freehdl is a dependency.   
> I think the
> problem is with freehdl as I tried and failed to get it to compile.  
> 
> qucs simulation fails   on libfreehdl.la   
> 
> I think something in gcc or g++ might not be creating this file   during 
> compilation and
> it might be some kind of policy change?

.la is short for "libtool archive". It is a text based description file
and is not created by GCC. In Fedora's packages, these .la files are not
included because they lead to dependency bloat during compilation. When
you tried to compile freehdl yourself, what happened?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Program won't start

[Michael Schwendt]

On Thu, 12 Apr 2018 08:30:43 -0700, Jonathan Ryshpan wrote:

> > > $ file st
> > > st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> > > dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux
> > > 2.2.5, not stripped
> > > 
> > > $ st
> > > 
> > > bash: ./st: No such file or directory
> > > $ strace st  
> > 
> > What do you get for "ldd st"?  
> 
> $ ldd st
> 
> not a dynamic executable

You've tried that on x86_64 not i686, right? Have you installed basic
runtime packages as to execute i386 programs?  Such as glibc.i686?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Program won't start

[Michael Schwendt]

On Thu, 12 Apr 2018 06:05:12 -0700, Jonathan Ryshpan wrote:

> Seagate's SeaTools for Linux won't start on my system.  The file is
> rather old and in a funky format, but it looks like it ought to
> run.  Nevertheless, it won't run.  Can anyone tell me what's goi
> ng on?  Here's what happens:
> 
> $ ls -l st-rwxr-xr-x. 1 jonrysh jonrysh 180149 Sep 12  2001 st
> $ file st
> st: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux
> 2.2.5, not stripped
> 
> 
> $ st
> 
> bash: ./st: No such file or directory
> $ strace st

What do you get for "ldd st"?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F27 tracker-preferences missing?

[Michael Schwendt]

On Mon, 12 Feb 2018 03:03:49 +, Christopher wrote:

> So... I just did a fresh install of F27, and I can't seem to find
> tracker-preferences, so I can disable the annoying document indexer that
> keeps crawling my drives. Anybody have any insight into why this is missing
> from F27, or a workaround to effectively disable the thing?

Also see:
https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/thread/7JKNFIS26MHKOVBWXUDZQNIKXKBLQ3BI/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Renaming USB WD 2TB drives

[Michael Schwendt]

On Mon, 5 Feb 2018 13:38:32 -0500, Bill Shirley wrote:

> What's the output of
> fdisk -l /dev/sdb
> 
> Bill

Note that fdisk would only show the partition type value, not the
actual fs.

"parted /dev/sdb p" tries to detect the fs type.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: how to convert a ma4 file to other format??

[Michael Schwendt]

On Fri, 26 Jan 2018 18:20:15 +0100, Antonio M wrote:

> I installed sounconverter with a bunch of plugins, lame, ffmpeg, faac --- I
> can convert for example a flac to mp3 but not  a m4a file to a mp3 file??
> what is missing??

Several things possibly.

* Soundconverter features automatic detection of needed GStreamer
plugins and automatic installation of the needed packages. In case
you've not seen a graphical dialog about that, it may be broken,
and manually installing missing gstreamer-plugins* packages from
3rd party repositories may be needed. Explicitly note that the new
gstreamer1-* packages are not compatible.

* What happens if you try to decode an .m4a file to .wav? If that
fails already, you are missing a plugin package.

* Perhaps install a different conversion tool, such as
"audio-convert-mod". It is not based on GStreamer, but is a
graphical frontend that uses command-line tools as backend.
It tells which converters are available, so you get a good overview.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: X driver for old Radeon card

[Michael Schwendt]

On Sat, 13 Jan 2018 19:55:30 -0500, Alex wrote:

> Hi,
> 
> > On Sat, 13 Jan 2018 18:29:29 -0500, Alex wrote:
> >  
> >> Is there a proprietary AMD/ATI driver for a Radeon HD5770? I believe
> >> the one that's shipped with fedora is called nouveau?  
> >  
> >> xorg-x11-drv-nouveau-1.0.15-3.fc27.x86_64  
> >
> > # rpm -qi xorg-x11-drv-nouveau|tail -3
> > Summary : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
> > Description :
> > X.Org X11 nouveau video driver.  
> 
> Yes, I should have been more clear that I realize that's the driver -

No, it isn't. It's the free driver for Nvidia graphics hardware, not
your AMD/ATI Radeon. AMD Catalyst is the proprietary driver with a Linux
version. For newer chipsets it has been replaced with a free open driver
that would not help you.

> my question is what substitute can be used that may work better?

You assume that a proprietary driver will work better when in fact it
is completely uncertain whether that will be true.

First you should figure out whether Xorg still works fine for you as
Samuel Sieb has pointed out in another reply. In case your problems are
specific to Wayland, you may want to report that in bugzilla.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: X driver for old Radeon card

[Michael Schwendt]

On Sat, 13 Jan 2018 18:29:29 -0500, Alex wrote:

> Is there a proprietary AMD/ATI driver for a Radeon HD5770? I believe
> the one that's shipped with fedora is called nouveau?

> xorg-x11-drv-nouveau-1.0.15-3.fc27.x86_64

# rpm -qi xorg-x11-drv-nouveau|tail -3
Summary : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
Description :
X.Org X11 nouveau video driver.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: !#@$**%^ Firefox

[Michael Schwendt]

On Sat, 6 Jan 2018 21:39:56 + (UTC), Beartooth wrote:

>   Hmmm... I get
> 
> [btth@localhost ~]$ rpm -qa |grep -i iridium
> iridium-browser-62.0-1.fc27.x86_64

> but I'm not clear what that tells me. Maybe that I did install it with 
> dnf after all?? If it actually came out of the Fedora shop, that makes 
> heavy odds the pestiferous code was in qutebrowser. Would it then be 
> feasible to cleanse the malware out of that, and re-install it clean? It 
> did seem like a nice little suite of code 

Take a look at:

  rpm -qi iridium-browser

Maybe the fields displayed by that command give a hint about where it
has been built or comes from.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: libgcrypto file conflicts during dnf update

[Michael Schwendt]

On Fri, 24 Nov 2017 18:02:03 + (UTC), Amadeus W.M. wrote:

> I was doing a regular dnf -y update on a F26 and I got this file conflict:
> 
> Error: Transaction check error:
>   file /usr/share/doc/libgcrypt/AUTHORS from install of 
> libgcrypt-1.7.9-1.fc26.i686 conflicts with file from package 
> libgcrypt-1.7.8-1.fc26.x86_64
>   file /usr/share/doc/libgcrypt/NEWS from install of 
> libgcrypt-1.7.9-1.fc26.i686 conflicts with file from package 
> libgcrypt-1.7.8-1.fc26.x86_64
> 
> Error Summary
> -
> 
> 
> It's a 64 bit machine and I don't even know why I have libgcrypt - i686, 
> but trying to remove that triggers a bunch of other i686 packages to be 
> removed and the mess is spreading. 
> 
> How do I force overwriting the AUTHORS and NEWS files? I tried 
> --allowerasing but I got the same error.

Don't. It should just work. The version of both the x86_64 and i686
packages is the same, _normally_, because both builds of the package
are put into the repository at the same time.

What do you get for

  dnf list libgcrypt
  rpm -qa libgcrypt\*

?

The 1.7.9-1.fc26 release is available in updates for two weeks or so.

Unfortunately, you've truncated the dnf output, so not much is known.
It's also interesting that dnf doesn't protect against multilib breakage.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: vi

[Michael Schwendt]

On Fri, 10 Nov 2017 15:58:56 +0100, Dario Lesca wrote:

> Il giorno gio, 09/11/2017 alle 13.37 +0100, Patrick Dupre ha scritto:
> > Can I make 2 substitutions on a single call with sed?  
> 
> Two or more ...
> 
> $ sed -i -e 's/E/e/g' -e 's/Alfa/xx/g' file.txt

No -e option is needed, since you can concatenate multiple
expressions with a ';' character:

   sed -i 's/E/e/g;s/Alfa/xx/g' file.txt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Tweaking Fedora

[Michael Schwendt]

On Thu, 2 Nov 2017 17:02:25 + (UTC), Beartooth wrote:

>   A correspondent on another list says one used to be able to use 
> Mondo Rescue to grab all the settings on an existing install and clone 
> them onto a new one. That would save me vast tedium.
> 
>   But the Mondo Rescue site lists only rpms for Fedora 23 and 
> before. And either I'm garbling my correspondent's directions, or they 
> don't work any more -- or both.

>I tried a few variations on "dnf install Mondo-xyzq". I also 
> downloaded a few .rpms from Mondo's repository and ran "rpm -ivh" against 
> them. Both tries failed.
> 
>   Is there a tutorial somewhere? Has Mondo Rescue forked into 
> something with another name? Have the Fedora Gurux and Alpha Plus 
> Technoids come up with a replacement while I wasn't looking??

The mondo suite of programs is still in the package review for over
10 years, because without people interested in them, the odds that
someone else will do substantial reviewing *and* approve the
packages are low: https://bugzilla.redhat.com/187318
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: error in clamav running clamscan as root from /.

[Michael Schwendt]

On Tue, 10 Oct 2017 18:58:47 -0700, stan wrote:

> For what it's worth, I also have that file on my system with the same
> permissions.  I think these files are created by the ebtables program.

/sys is a "sysfs" mount created at runtime.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to install ytnef?

[Michael Schwendt]

On Wed, 04 Oct 2017 15:43:52 +0200, Ambrogio wrote:

> I'm working hard on migration from my old Fedora to the new Fedora 26,
> and I find everyday a problem (sometimes a very big problem).
> I submitted the question in the evolution mailing list, as I think the
> article is very very old.
> I will update in this thread if I'll found a solution.

Meanwhile I've check the Fedora evolution package spec file.
It builds with this:

-DENABLE_YTNEF=OFF \

Older spec %changelog comments had turned on libytnef as a build
requirement, four years later turned it off again:

Files in evolution-3.26.1/src/modules/tnef-attachment/ include
ytnef.h and libytnef headers conditionally, but if turning it off
and not adding libytnef as build requirement, nothing will be built.

Note that this is not the full story yet.


* Thu Jul 02 2009 Matthew Barnes  mbarnes redhat com  - 2.27.3-4.fc12   
- Add BR for libpst-devel and libytnef-devel (RH bug #493049).  

* Mon Oct 14 2013 Milan Crha  mcrha redhat com  - 3.10.1-1  
- Update to 3.10.1  
- Remove the dependency on libytnef, which apparently isn't needed for  
  the PST importer and disable the experimental TNEF attachments plugin 

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to install ytnef?

[Michael Schwendt]

On Wed, 04 Oct 2017 13:20:36 +0200, Ambrogio wrote:

> Installed... but no integration with Evolution.
> There is a way for enable support to ms-tnef on evo?

Since you seem to be an expert in that area, it would be an opportunity
to contribute.

Is the following guide still accurate?

  https://wiki.gnome.org/Apps/Evolution/Tnef

If so, it refers to a separate plugin, which somebody would need to
package.

Right?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: How to install ytnef?

[Michael Schwendt]

On Wed, 04 Oct 2017 12:27:35 +0200, Ambrogio wrote:

> Tnx for that.
> I can't understand why there are a lot of packages errors and
> dependency issues.
> I know there is a lot of work on maintaining a so big distro, but I
> start thinking Fedora isn't so good as before.
> I hope it's only my impression... but I have a lot of problems with my
> new installation, and I can't find a way to see the light :-(
> 
> I'll update after my test with ytnef.

Somebody has retired the separate "libytnef" package, which is needed by
"ytnef", for multiple dist releases. The new combined "ytnef" package,
which merges the library using an Epoch bump, has only been published for
Rawhide and F27. My bug report about that can be found at:

  https://bugzilla.redhat.com/show_bug.cgi?id=1492367

Since the missing libytnef has also made it impossible to build Claws
Mail, some days ago I've jumped in to fix the mess myself. Hence there is
the current Test Update, which is on its way to stable currently.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: update fails

[Michael Schwendt]

On Tue, 3 Oct 2017 13:10:35 +0200, Patrick Dupre wrote:

> I uninstalled freeipmi, and then
> 
> dnf install nut

That is not the suggested command.

> freeipmi is needed by nut!!
> 
> /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0
> /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0
> /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0
> 
> /etc/yum.repos.d/rpmfusion-free-updates-testing.repo:enabled=0
> /etc/yum.repos.d/rpmfusion-free-updates-testing.repo:enabled=0
> /etc/yum.repos.d/rpmfusion-free-updates-testing.repo:enabled=0
> 
> seem to indicate that the updates-testing packages are no active.
> Am I wrong?

Read my previous mail more slowly.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: update fails

[Michael Schwendt]

On Tue, 3 Oct 2017 09:38:57 +0200, Patrick Dupre wrote:

> dnf update nut

> Package nut available, but not installed.
> No match for argument: nut
>   * Maybe you meant: nut
> Error: No packages marked for upgrade.

Now we're entering the space of "DNF mess", such as hiding some things
from the user or printing odd error messages, because the DNF developers
think that's helpful.

You haven't installed "nut" before, but only "nut-client",
so you cannot "update nut". You would need to install it first.

However, if you visit the ticket in the Fedora Updates System, which
I've linked before,

  https://bodhi.fedoraproject.org/updates/FEDORA-2017-de0f8ded67

somebody points out that "freeipmi" from the updates-testing repo is
needed for the latest "nut", and the packagers have missed that. You
may need to fetch freeipmi from its update ticket manually or enable
the updates-testing repo temporarily.

  dnf --enablerepo=updates-testing install nut

At least you now see the latest nut- package updates. Good. That's
progress.

> dnf list nut\*
> Repository mgeups has no mirror or baseurl set.
> Last metadata expiration check: 0:03:32 ago on Tue 03 Oct 2017 09:30:24 AM 
> CEST.
> Available Packages
> nut.i6862.7.4-14.fc26
> updates
> nut.x86_64  2.7.4-14.fc26
> updates
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: update fails

[Michael Schwendt]

On Mon, 2 Oct 2017 22:28:26 +0200, Patrick Dupre wrote:

> dnf install --refresh nut

It makes no sense to run that command before you see the latest packages
available in the "updates" repo.

Also, adding --refresh again and again only forces dnf to redownload
the repo metadata again and again, which also makes no sense, if the
metadata haven't changed.

Of course you may erase/uninstall packages and start from scratch with
what you see in the repos _currently_ as a workaround, but it doesn't
explain why you don't see the latest nut- updates. Perhaps the mirror
you use currently is out-of-date.

The -14.fc26 nut- updates have been pushed to 'updates' 4 days ago:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-de0f8ded67
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org