Re: Failed to start Load Kernel Modules.

[Sudhir Khanger]

On Mon, Jun 18, 2018 at 5:58 PM Ed Greshko  wrote:

> On 06/18/18 19:19, Sudhir Khanger wrote:
> > I get *Failed to start Load Kernel Modules* during the boot.
> >
> > Everytime Kernel is updated VirtualBox modules fail I have to reboot
> into the new
> > Kernel, run the following commands and then it starts working.
> >
> > $ sudo akmods --force
> > $ sudo dracut -v -f
> > $ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> >
> > Then everything starts working again and the boot error goes away. You
> can found
> > the background of the issue in the link below.
> >
>
> You are using the VirtualBox packages from rpmfusion, yes?
>
> I don't, but I seem to recall they operate differently than the packages
> from
> Oracle.  The Oracle packages don't rely on  akmod and don't put the
> modules in the
> initramfs.  The vbox modules are checked for existence when
> vboxdrv.service is run
> and if they don't exist for the running kernel they are built at that time.
>
> Assuming akmods is being used to build the modules when the kernel is
> updated there
> should be some sort of log file in /var/cache/akmods just like there is
> for nvidia.
> Have you checked?
>
> Also, have you considered asking about this on the rpmfusion user's list
> since it is
> their package?
>
> --
> Conjecture is just a conclusion based on incomplete information. It isn't
> a fact.
>
> ___
> 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/PBBOWO6LMVOECYNPRFX6VVZ6VOMAYYRI/


Thanks. I will try Oracle's package for now.
___
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/WHKCL6LUK2JRJJHTPDICNGYOTZVS35GU/

Re: Redshift has an issue with geoclue2

[ToddAndMargo]

On 06/22/2018 05:00 PM, Ed Greshko wrote:

On 06/23/18 05:24, ToddAndMargo wrote:

Hi All,

Fedora 28, x64

redshift-gtk-1.11-8.fc28.x86_64
redshift-1.11-8.fc28.x86_64
geoclue2-libs-2.4.10-2.fc28.x86_64
geoclue2-2.4.10-2.fc28.x86_64

When starting Redshift, I get the following error

$ redshift
     Trying location provider `geoclue2'...
     Using provider `geoclue2'.
     Unable to start GeoClue client:
     GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
     recipient disconnected from message bus without replying.
     Unable to connect to GeoClue.
     Unable to get location from provider.

the pop up says:
     GDBus.Error" org.freedesktop.DBus.Error.AccessDenied

Any word of wisdom?  It worked under Fedora 27.


I don't have an answer for you.  But, the problem you're seeing doesn't appear 
to be
specific to fedora.

https://github.com/jonls/redshift/issues/158

And, FWIW, the last comment didn't make things work for me.  At least not in a 
KDE VM.


Did not help me either.

I signed up for both

https://bugzilla.redhat.com/show_bug.cgi?id=1585970
https://github.com/jonls/redshift/issues/318




___
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/HZ7YL7D3NT5TVV7QHOBIBF6BTPY4MLO5/

Re: Redshift has an issue with geoclue2

[Ed Greshko]

On 06/23/18 05:24, ToddAndMargo wrote:
> Hi All,
>
> Fedora 28, x64
>
> redshift-gtk-1.11-8.fc28.x86_64
> redshift-1.11-8.fc28.x86_64
> geoclue2-libs-2.4.10-2.fc28.x86_64
> geoclue2-2.4.10-2.fc28.x86_64
>
> When starting Redshift, I get the following error
>
> $ redshift
>     Trying location provider `geoclue2'...
>     Using provider `geoclue2'.
>     Unable to start GeoClue client:
>     GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
>     recipient disconnected from message bus without replying.
>     Unable to connect to GeoClue.
>     Unable to get location from provider.
>
> the pop up says:
>     GDBus.Error" org.freedesktop.DBus.Error.AccessDenied
>
> Any word of wisdom?  It worked under Fedora 27.

I don't have an answer for you.  But, the problem you're seeing doesn't appear 
to be
specific to fedora. 

https://github.com/jonls/redshift/issues/158

And, FWIW, the last comment didn't make things work for me.  At least not in a 
KDE VM.



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
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/EKMW55OS7ZJFUHV7FOGVLFRHSHWJIO6A/

Redshift has an issue with geoclue2

[ToddAndMargo]

Hi All,

Fedora 28, x64

redshift-gtk-1.11-8.fc28.x86_64
redshift-1.11-8.fc28.x86_64
geoclue2-libs-2.4.10-2.fc28.x86_64
geoclue2-2.4.10-2.fc28.x86_64

When starting Redshift, I get the following error

$ redshift
Trying location provider `geoclue2'...
Using provider `geoclue2'.
Unable to start GeoClue client:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
recipient disconnected from message bus without replying.
Unable to connect to GeoClue.
Unable to get location from provider.

the pop up says:
GDBus.Error" org.freedesktop.DBus.Error.AccessDenied

Any word of wisdom?  It worked under Fedora 27.

-T
___
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/FXGKLLCL56ZTWFDPFU3E7766FSUSCFFJ/

Re: Could LightDM be bad?? (LONG)

[Rick Stevens]

On 06/22/2018 01:57 PM, Beartooth wrote:
> On Mon, 21 May 2018 05:48:24 +0800, Ed Greshko wrote:
> 
>> In actuality you just need one command.
>>
>> systemctl -f enable sddm   (or whatever new dm you want)
>>
>> -f = force   which means "When used with enable, overwrite any existing
>> conflicting symlinks."
>>
>> and no need to use ".service"
> 
>   Bless you, SIR, bless you again, and bless you some more!
> 
>   First I launched dnfdragora on the one machine that still gives 
> me a graphical interface (by running F26 Rescue -- 26 no typo, *not* 28), 
> and used the GUI to install as many display managers as I could find.
> 
>   I noticed that lxdm seemed to be included in many groups. So I 
> did dnf install with the console (from Ctrl-Alt-F2) on my #2 machine, 
> which had been denying me any GUI, for love nor electrons. Then systemctl 
> -f enable lxdm, and rebooted.
> 
>   IT WORKED!! 
> 
>   It's not quite working on #3 yet, but I bet it will be in a day 
> or three. I've already stopped feeling like I'm riding a bicycle along 
> the edge of a cliff. Champagne is definitely indicated.

And just a warning: The lightdm display manager has issues with
pam_kwallet and pam_kwallet5 if they're installed. If you decide to use
lightdm, edit the /etc/pam.d/lightdm file and comment out any lines
that reference pam_kwallet*.so.

Since you're using lxdm you should be fine, but I just wanted to put
that warning out there. The bugzilla I opened on it hasn't been resolved
yet to my knowledge.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   If the enemy's in range...so are you!-
--
___
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/WI3WOXCHTKAROHABDJAPJFZIX5I3XI46/

Re: SSH private keys?

[Gordon Messmer]

On 06/22/2018 01:04 PM, Tom Horsley wrote:

On Fri, 22 Jun 2018 12:45:08 -0700 Gordon Messmer wrote:


There is an open bug concerning the fact that if there is an invalid
.pub file in .ssh, GNOME keyring won't automatically unlock *any* keys,
so remove any old key files.

Yep, some forms of keys are no longer supported because security geeks decided 
they were insecure (like DSA and RSA version 1 keys). When this change first 
appeared I spent a lot of time getting rid of old keys and updating the 
authorized_keys file on lots of systems. This did happen a few fedora's ago, 
but if you didn't upgrade for a while, this may be the first time you've seen 
it.


RSA1 and DSA keys were dropped back in OpenSSH 7 (Fedora 23), in late 
2015.  I *hope* this isn't anyone's first experience with a system that 
doesn't support them.


The bug is new, though.  If you had any old files sitting around, in the 
past they'd just be ignored.  At the moment, they actually block 
gnome-keyring from loading *any* keys, including new keys that are 
supported.

___
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/ICWXZWQXRHSMEO34ABFHS6KNC4Q3WEW5/

Re: Could LightDM be bad?? (LONG)

[Beartooth]

On Mon, 21 May 2018 05:48:24 +0800, Ed Greshko wrote:

> In actuality you just need one command.
> 
> systemctl -f enable sddm   (or whatever new dm you want)
> 
> -f = force   which means "When used with enable, overwrite any existing
> conflicting symlinks."
> 
> and no need to use ".service"

Bless you, SIR, bless you again, and bless you some more!

First I launched dnfdragora on the one machine that still gives 
me a graphical interface (by running F26 Rescue -- 26 no typo, *not* 28), 
and used the GUI to install as many display managers as I could find.

I noticed that lxdm seemed to be included in many groups. So I 
did dnf install with the console (from Ctrl-Alt-F2) on my #2 machine, 
which had been denying me any GUI, for love nor electrons. Then systemctl 
-f enable lxdm, and rebooted.

IT WORKED!! 

It's not quite working on #3 yet, but I bet it will be in a day 
or three. I've already stopped feeling like I'm riding a bicycle along 
the edge of a cliff. Champagne is definitely indicated.
-- 
Beartooth Implacable, Curmudgeon On Line
Who shall gather the smoke of the dead wood burning,
Or behold the flowing years from the Sea returning?
___
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/NZ7X5LQGFBDYGHG5CSIR5GXBOQZFP4HT/

Re: SSH private keys?

[Tom Horsley]

On Fri, 22 Jun 2018 12:45:08 -0700
Gordon Messmer wrote:

> There is an open bug concerning the fact that if there is an invalid 
> .pub file in .ssh, GNOME keyring won't automatically unlock *any* keys, 
> so remove any old key files.

Yep, some forms of keys are no longer supported because
security geeks decided they were insecure (like DSA and
RSA version 1 keys). When this change first appeared
I spent a lot of time getting rid of old keys and
updating the authorized_keys file on lots of systems.
This did happen a few fedora's ago, but if you didn't
upgrade for a while, this may be the first time you've seen it.
___
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/BA77OG556PSZTTWJ6EUQLNI4TDZGOEF6/

Re: SSH private keys?

[Gordon Messmer]

On 06/22/2018 04:37 AM, Jeffrey Ross wrote:
Fast forward to today, the system had been reinstalled (new hardware, 
new disks, etc) and I no longer have that ability.  I'm currently runn 
Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter of 
installing/configuring/running the correct application but which one? 


That's handled by gnome-keyring and, as of this version of GNOME, 
ssh-agent.  As far as I can tell, those are both required components, so 
they're probably not missing on your workstation. The problem *might* be 
that GNOME keyring will only automatically unlock private keys if there 
is a valid public key with the same name, and a .pub suffix.  So, you 
might not have the public keys. Or, you might have a .pub file that's 
*really* old and no longer valid.


There is an open bug concerning the fact that if there is an invalid 
.pub file in .ssh, GNOME keyring won't automatically unlock *any* keys, 
so remove any old key files.


https://bugzilla.redhat.com/show_bug.cgi?id=1568895
___
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/AOOGXAJJUVT4LAPHVIBD7LCYM4235IAL/

Re: better subject

[Patrick O'Callaghan]

On Fri, 2018-06-22 at 13:08 -0500, Rex Dieter wrote:
> Patrick O'Callaghan wrote:
> 
> > On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote:
> > > François Patte wrote:
> > > 
> > > > Bonjour,
> > > 
> > > such inflammatory subject lines are not welcome, please do better next
> > > time.
> > 
> > I know you were joking, but that was a greeting rather than a Subject
> > line.
> 
> I simply quoted the first line of the original post, no joke intended.
> 
> And I changed the Subject of my post (and these followups) on purpose to not 
> perpetuate the problem.

That's what confused me. More conventional would have been to prefix
the subject, e.g.

Subject: Inflammatory subject line (Was: ... etc.)

poc
___
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/4OW2TWP45W6U2ZSJN2YU3MNLGXSMGKES/

Re: better subject

[Rex Dieter]

Patrick O'Callaghan wrote:

> On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote:
>> François Patte wrote:
>> 
>> > Bonjour,
>> 
>> such inflammatory subject lines are not welcome, please do better next
>> time.
> 
> I know you were joking, but that was a greeting rather than a Subject
> line.

I simply quoted the first line of the original post, no joke intended.

And I changed the Subject of my post (and these followups) on purpose to not 
perpetuate the problem.

-- Rex
___
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/FOZYMOSUTXN2Z37GMGRQM3OPRGHBGGN6/

Re: F28 suspend

[Berend De Schouwer]

On Tue, 2018-05-29 at 08:56 -0700, Samuel Sieb wrote:
> On 05/29/2018 01:53 AM, Berend De Schouwer wrote:
> > I've got a laptop that has started misbehaving on suspend.
> > 
> > About 1 in 10 suspends the laptop fails to fully suspend.  It
> > switches
> > mostly off (screen off, etc.) but some of the motherboard keeps
> > running.  I know some of the motherboard keeps running because:
> > - the wifi light remains on
> > - the laptop will get hot because the fans don't start
> > 
> > The laptop does not respond to the power button to wake up.  It's
> > necessary to force halt & reboot the laptop by holding the power
> > button
> > down for a few seconds.
> 
> Do you still have a 4.14 kernel available?  If you boot that does it
> work?

I didn't, but I did actually try and install F27 kernel.  Seems to be
Meltdown fixes related:

https://bugzilla.redhat.com/show_bug.cgi?id=1593105
___
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/DOQQODE2Q2FWAC4Q3RC5QKLV5GBJHFOX/

Re: better subject

[Patrick O'Callaghan]

On Fri, 2018-06-22 at 17:22 +0100, John Pilkington wrote:
> On 22/06/18 16:28, Patrick O'Callaghan wrote:
> > On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote:
> > > François Patte wrote:
> > > 
> > > > Bonjour,
> > > 
> > > such inflammatory subject lines are not welcome, please do better next 
> > > time.
> > 
> > I know you were joking, but that was a greeting rather than a Subject
> > line.
> > 
> > poc
> 
> I was bemused at first, but I think you'll find Rex was not thinking of 
> the French-style greeting but of the original Subject line, which 
> expressed some irritation.

OK, makes sense.

poc
___
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/IF4QJRG3EDLH2MQFMZY53IIYHMERBVFB/

Re: better subject

[John Pilkington]

On 22/06/18 16:28, Patrick O'Callaghan wrote:

On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote:

François Patte wrote:


Bonjour,


such inflammatory subject lines are not welcome, please do better next time.


I know you were joking, but that was a greeting rather than a Subject
line.

poc


I was bemused at first, but I think you'll find Rex was not thinking of 
the French-style greeting but of the original Subject line, which 
expressed some irritation.


John P
___
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/T464NVCQXACPZ2WQKZTBAWL6GHZ3EO4E/

Re: Createrepeo faild with error on Fedora 28

[Danishka Navin]

On Fri, Jun 22, 2018 at 9:36 PM, Todd Zullinger  wrote:

> Hi,
>
> Danishka Navin wrote:
> > I noticed that createrepo failed on Fedora 28 under SELinux permissive as
> > well.
> >
> >  createrepo /data/dist/localrepo/h28/norach/
> > Spawning worker 0 with 1 pkgs
> > Spawning worker 1 with 1 pkgs
> > Worker 0: Error: Could not open local rpm file:
> > /data/dist/localrepo/h28/norach//generic-logos-18.0.0-
> 900.fc28.noarch.rpm:
> > RPM Error opening Package
> > Worker 1: Error: Could not open local rpm file:
> > /data/dist/localrepo/h28/norach//generic-logos-httpd-
> 18.0.0-900.fc28.noarch.rpm:
> > RPM Error opening Package
> > Workers Finished
> > Failed to process 2 package(s).
> >
> > [root@hanthana localrepo]# ls -l /data/dist/localrepo/h28/norach/
> > total 12
> > -rw-r--r--. 1 root root  131 Jun 22 21:09
> > generic-logos-18.0.0-900.fc28.noarch.rpm
> > -rw-r--r--. 1 root root  130 Jun 22 21:09
> > generic-logos-httpd-18.0.0-900.fc28.noarch.rpm
> > drwxr-xr-x. 2 root root 4096 Jun 22 21:14 repodata
>
> Are those packages valid rpm's?  The sizes look way too
> small, particularly for logo packages.  Check that rpm can
> parse them, using rpm -K or another rpm query command.
>


Thanks Todd!
Seems issue is with rpms.

[root@hanthana localrepo]# rpm -K
/data/dist/localrepo/h28/norach//generic-logos-18.0.0-900.fc28.noarch.rpm
/data/dist/localrepo/h28/norach//generic-logos-18.0.0-900.fc28.noarch.rpm:
NOT OK
[root@hanthana localrepo]# rpm -K
/data/dist/localrepo/h28/norach//generic-logos-httpd-18.0.0-900.fc28.noarch.rpm
/data/dist/localrepo/h28/norach//generic-logos-httpd-18.0.0-900.fc28.noarch.rpm:
NOT OK
[root@hanthana localrepo]#


> --
> Todd
> ~~
> The trouble with being punctual is that nobody's there to appreciate
> it.
> -- Franklin P. Jones
>
>
> ___
> 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/3Z7RHP3DVZ3LFY2QDWPXMVV7JEIKDNHU/
>
>


-- 
Danishka Navin
http://danishkanavin.blogspot.com
http://twitter.com/danishkanavin
___
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/PIL24KZ3R7PEYHVRFWOR2OWRISA5XYZR/

Re: Createrepeo faild with error on Fedora 28

[Todd Zullinger]

Hi,

Danishka Navin wrote:
> I noticed that createrepo failed on Fedora 28 under SELinux permissive as
> well.
> 
>  createrepo /data/dist/localrepo/h28/norach/
> Spawning worker 0 with 1 pkgs
> Spawning worker 1 with 1 pkgs
> Worker 0: Error: Could not open local rpm file:
> /data/dist/localrepo/h28/norach//generic-logos-18.0.0-900.fc28.noarch.rpm:
> RPM Error opening Package
> Worker 1: Error: Could not open local rpm file:
> /data/dist/localrepo/h28/norach//generic-logos-httpd-18.0.0-900.fc28.noarch.rpm:
> RPM Error opening Package
> Workers Finished
> Failed to process 2 package(s).
> 
> [root@hanthana localrepo]# ls -l /data/dist/localrepo/h28/norach/
> total 12
> -rw-r--r--. 1 root root  131 Jun 22 21:09
> generic-logos-18.0.0-900.fc28.noarch.rpm
> -rw-r--r--. 1 root root  130 Jun 22 21:09
> generic-logos-httpd-18.0.0-900.fc28.noarch.rpm
> drwxr-xr-x. 2 root root 4096 Jun 22 21:14 repodata

Are those packages valid rpm's?  The sizes look way too
small, particularly for logo packages.  Check that rpm can
parse them, using rpm -K or another rpm query command.

-- 
Todd
~~
The trouble with being punctual is that nobody's there to appreciate
it.
-- Franklin P. Jones



signature.asc
Description: PGP signature
___
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/3Z7RHP3DVZ3LFY2QDWPXMVV7JEIKDNHU/

Createrepeo faild with error on Fedora 28

[Danishka Navin]

Hi,

I noticed that createrepo failed on Fedora 28 under SELinux permissive as
well.

 createrepo /data/dist/localrepo/h28/norach/
Spawning worker 0 with 1 pkgs
Spawning worker 1 with 1 pkgs
Worker 0: Error: Could not open local rpm file:
/data/dist/localrepo/h28/norach//generic-logos-18.0.0-900.fc28.noarch.rpm:
RPM Error opening Package
Worker 1: Error: Could not open local rpm file:
/data/dist/localrepo/h28/norach//generic-logos-httpd-18.0.0-900.fc28.noarch.rpm:
RPM Error opening Package
Workers Finished
Failed to process 2 package(s).

[root@hanthana localrepo]# ls -l /data/dist/localrepo/h28/norach/
total 12
-rw-r--r--. 1 root root  131 Jun 22 21:09
generic-logos-18.0.0-900.fc28.noarch.rpm
-rw-r--r--. 1 root root  130 Jun 22 21:09
generic-logos-httpd-18.0.0-900.fc28.noarch.rpm
drwxr-xr-x. 2 root root 4096 Jun 22 21:14 repodata

Appreciate if someone can support.

-- 
Danishka Navin
http://danishkanavin.blogspot.com
http://twitter.com/danishkanavin
___
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/CJ7UODICPTUUZLM226ZQEOG444XKYBYD/

Re: better subject

[Patrick O'Callaghan]

On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote:
> François Patte wrote:
> 
> > Bonjour,
> 
> such inflammatory subject lines are not welcome, please do better next time.

I know you were joking, but that was a greeting rather than a Subject
line.

poc
___
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/G7OH6FTLVGEEQX3CUC25XLLSPVNYXHPN/

Re: SSH private keys?

[Patrick O'Callaghan]

On Fri, 2018-06-22 at 13:54 +0200, Berend De Schouwer wrote:
> On Fri, 2018-06-22 at 07:37 -0400, Jeffrey Ross wrote:
> > At one point Fedora had something (keyring?) that would allow me to 
> > unlock my SSH private keys and it would keep the unlocked key
> > available 
> > so I could ssh without having to unlock my key every time.  I
> > typically 
> > run a simple "terminal" window and then "ssh " since my key
> > is 
> > not retained unlocked I'm prompted for a password.
> > 
> > Fast forward to today, the system had been reinstalled (new
> > hardware, 
> > new disks, etc) and I no longer have that ability.  I'm currently
> > runn 
> > Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter
> > of 
> > installing/configuring/running the correct application but which
> > one?
> 
> You're *probably* missing the gnome-keyring package.
> 
> you'll need:
> - ssh-agent (to remember)
> - an app that processes your passphrase (gnome-keyring or pinentry-gtk)
> 
> ssh-agent is part of openssh-clients.  It's usually run by gnome-
> keyring-daemon.  Look in the process list for it.  It should be
> running.
> 
> ssh-add is a cli app that will let you add the key and trigger a
> passphrase without a GUI.
> 
> You can see if a key is being remembered by running 'ssh-add -l'
> 
> gnome-shell should prompt for the key (the prompt will be themed like
> gnome-shell), but so can pinentry/pinentry-gtk (themed like a Gtk2 app)

See also seahorse(1).

poc
___
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/DHCDZV4JI3EPETMAQZZROZS324EDYMWF/

better subject

[Rex Dieter]

François Patte wrote:

> Bonjour,

such inflammatory subject lines are not welcome, please do better next time.

-- Rex
___
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/TCN7RJX4KC5IT6NHLXZOFPE7CPBWYVPU/

Re: SSH private keys?

[Berend De Schouwer]

On Fri, 2018-06-22 at 07:37 -0400, Jeffrey Ross wrote:
> At one point Fedora had something (keyring?) that would allow me to 
> unlock my SSH private keys and it would keep the unlocked key
> available 
> so I could ssh without having to unlock my key every time.  I
> typically 
> run a simple "terminal" window and then "ssh " since my key
> is 
> not retained unlocked I'm prompted for a password.
> 
> Fast forward to today, the system had been reinstalled (new
> hardware, 
> new disks, etc) and I no longer have that ability.  I'm currently
> runn 
> Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter
> of 
> installing/configuring/running the correct application but which
> one?

You're *probably* missing the gnome-keyring package.

you'll need:
- ssh-agent (to remember)
- an app that processes your passphrase (gnome-keyring or pinentry-gtk)

ssh-agent is part of openssh-clients.  It's usually run by gnome-
keyring-daemon.  Look in the process list for it.  It should be
running.

ssh-add is a cli app that will let you add the key and trigger a
passphrase without a GUI.

You can see if a key is being remembered by running 'ssh-add -l'

gnome-shell should prompt for the key (the prompt will be themed like
gnome-shell), but so can pinentry/pinentry-gtk (themed like a Gtk2 app)
___
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/CUBJ7HVHIMMSFRV5EJAQ25XIGZB5WVG4/

Re: >60gb of reserved memory??

[Wolfgang Pfeiffer]

On Thu, Jun 21, 2018 at 09:13:00PM +0300, Susi Lehtola wrote:

On 06/21/2018 07:51 PM, Patrick O'Callaghan wrote:

AFAIK Fedora uses the available RAM as a) buffer space, and b) the /tmp
filesystem.

BTW a slightly more user-friendly way to get that info is with the
free(1) command.


The joke is, the >60GB of missing memory doesn't even show up in free:

$ free
 totalusedfree  shared  buff/cache 
available

Mem:2400708 1093732  284844  121920 1022132 957848
Swap:  62499836   062499836

For some reason the kernel marks it as reserved.

On 06/21/2018 07:55 PM, Rick Stevens wrote:

Try installing htop ("$ sudo dnf install htop"), run it, press F6 and
select which memory item you want to sort by. That'll tell you what
process is sucking up memory.


Same goes for htop. It's showing I have 2.29G of memory.


Update: I upgraded from Fedora 27 to Fedora 28, and the same issue 
persists. Of course, the kernel is almost the same.


I'd try a newer kernel from the 4.17 series from the non-official
kernel repo for Fedora, just to narrow down the issue and see, whether
it's really a kernel thing:

https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories

I've had issues here, too, on F27, and at least one of them seems to
be gone with such a kernel:

% uname -r
4.17.2-250.vanilla.knurd.1.fc27.x86_64

HTH, and Regards.

Good luck!
Wolfgang
___
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/AAPXUQ6LNO5IHPKMPZLXRWEPIYQVJRTG/

SSH private keys?

[Jeffrey Ross]

At one point Fedora had something (keyring?) that would allow me to 
unlock my SSH private keys and it would keep the unlocked key available 
so I could ssh without having to unlock my key every time.  I typically 
run a simple "terminal" window and then "ssh " since my key is 
not retained unlocked I'm prompted for a password.


Fast forward to today, the system had been reinstalled (new hardware, 
new disks, etc) and I no longer have that ability.  I'm currently runn 
Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter of 
installing/configuring/running the correct application but which one?


Thanks, Jeff

___
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/MXAKLZZTP2FT7YRDLXOL7RGQG2KO7OGQ/

Re: problem with cups-pdf and spool directory under wine

[Berend De Schouwer]

On Wed, 2018-06-20 at 08:54 +0200, Saša Janiška wrote:
> Now, there are no more alerts, but where is the output?

How are you using cups-pdf?  Did you configure a PDF printer, or are
you trying to run cups-pdf on the command line?

Can you use it on the command line, but not in Wine?  Or can you not
use it anywhere?

If you run 'lpstat -t' do you see a line like:
device for Cups-PDF: cups-pdf:/

> I've the following in my /etc/cups/cups-pdf.conf:
> 
> Out ${DESKTOP}
> 
> but the output is generated in:
> 
> /var/spool/cups

It goes here *before* it's finished printing.  This is for pre-
processing, and so that the document isn't lost if you reboot before
printing has finished.  This is a temporary location.

> so, I do wonder why the setting from *.conf file above is not
> honoured?

It's not being honoured because for now it's running cups, which uses
cupsd.conf.  Cups will then run cups-pdf, and cups-pdf will honour it's
cups-pdf.conf file.

> /var/spool/cups is 710 root:lp
> 
> while
> 
> /var/sppol/cups-pdf is 755 root:root

same here.

> Moreover, status for cups service gives:
> 
> systemctl status cups
> ● cups.service - CUPS Scheduler
>Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled;
> vendor preset: disabled)
>Active: active (running) since Wed 2018-06-20 08:36:53 CEST; 11min
> ago
>  Docs: man:cupsd(8)
>  Main PID: 7571 (cupsd)
>Status: "Scheduler is running..."
> Tasks: 1 (limit: 4915)
>Memory: 2.8M
>CGroup: /system.slice/cups.service
>└─7571 /usr/sbin/cupsd -l
> 
> lip 20 08:36:53 mydomain.dyndns.net systemd[1]: Starting CUPS
> Scheduler...
> lip 20 08:36:53 mydomain.dyndns.net cupsd[7571]: Filter "pstopdf" not
> found.

On earlier Fedoras, cups.rpm created /usr/lib/cups/filter/pstopdf

On my Fedora 28 laptop it works *without* /usr/lib/cups/filter/pstopdf

I've had a look at the filters and ppds, and new cups seems to rely on
/usr/bin/gs (ghostscript), so make sure that is installed.

> lip 20 08:36:53 mydomain.dyndns.net systemd[1]: Started CUPS
> Scheduler.
> 
> so I also wonder if this is OK?
> 
> What do I miss?

Can you check /etc/cups/ppd/Cups-PDF.ppd?  If you can, please report
the FormatVersion, FileVersion and cupsFilter lines.  For me:
*% cupsFilter:"application/vnd.cups-postscript 0 pstitleiconv"
___
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/QITLOOH3QR76A2N5TTK2SCUVV52KH6EU/

[389-users] Re: Master-slave replication procedure

[Michal Medvecky]

Hello,

> 19. 6. 2018 v 23:43, Thomas E Lackey :
> 
> By happy timing, we (Bozeman Pass) just added one of our in-house tools for 
> configuring replication to GitHub: https://github.com/bozemanpass/replform 
> .

I had a look at this but I don’t like the fact you need to statically define 
the configuration. I have variable number of masters and variable number of 
slaves and if I understand this correctly, adding a new backend server would 
need copypasting the replform config.

Have you considered creating LDAP providers for Terraform itself?

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