Re: Xscreensaver daemon does not start on boot after last update

Also resolved by installing xfce4-screensaver On Tue, Jun 29, 2021 at 4:14 PM Joe Zeff wrote: > On 6/29/21 1:23 PM, Terry Polzin wrote: > > I'm running XFCE > > In Xfce, open your main menu, go to Applications->Settings->Session and > Startup and open the tab for Application Autostart. If Xscre

Re: Xscreensaver daemon does not start on boot after last update

On 6/29/21 1:23 PM, Terry Polzin wrote: I'm running XFCE In Xfce, open your main menu, go to Applications->Settings->Session and Startup and open the tab for Application Autostart. If Xscreensaver isn't already listed, add it and set it to be triggered by login. If it's listed but not chec

Re: Xscreensaver daemon does not start on boot after last update

I'm running XFCE On Tue, Jun 29, 2021 at 3:00 PM Jonathan Billings wrote: > On Tue, Jun 29, 2021 at 11:05:39AM -0400, Terry Polzin wrote: > > > > It seems I have to start it manually. It's not part of systemd > > > > systemctl enable xscreensaver > > Failed to enable unit: Unit file xscreensave

Re: Xscreensaver daemon does not start on boot after last update

On Tue, Jun 29, 2021 at 11:05:39AM -0400, Terry Polzin wrote: > > It seems I have to start it manually. It's not part of systemd > > systemctl enable xscreensaver > Failed to enable unit: Unit file xscreensaver.service does not exist. Xscreensaver doesn't have a systemd unit, and it certainly sh

Xscreensaver daemon does not start on boot after last update

It seems I have to start it manually. It's not part of systemd systemctl enable xscreensaver Failed to enable unit: Unit file xscreensaver.service does not exist. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to us

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 16:48, Jerome Lille wrote: On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied b

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: > On Sun, 21 Feb 2021 at 12:46, Jerome Lille > wrote: > > I tried to simply change type from nfs to nfs4 in the fstab in the > > client. Unfortunately I then get the response > > > > mount.nfs4: access denied by server while mounting

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 07:38, George N. White III wrote: So, I still can't find a way to duplicate the OP's problem without specifically changing a config file. There is always the possibility of some "invisible character" error in a config file. The OP has said he hadn't modified any config f

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 18:11, Ed Greshko wrote: > On 26/02/2021 04:21, George N. White III wrote: > > On Thu, 25 Feb 2021 at 14:03, Ed Greshko > wrote: > > > > On 26/02/2021 01:19, George N. White III wrote: > > > I haven't used CentOS7 for several years, s

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 04:21, George N. White III wrote: On Thu, 25 Feb 2021 at 14:03, Ed Greshko mailto:ed.gres...@greshko.com>> wrote: On 26/02/2021 01:19, George N. White III wrote: > I haven't used CentOS7 for several years, so I was ignoring this > thread in the hope others could answer.

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 14:03, Ed Greshko wrote: > On 26/02/2021 01:19, George N. White III wrote: > > I haven't used CentOS7 for several years, so I was ignoring this > > thread in the hope others could answer. > > > > My not very trustworthy memory is that "/etc/exports" on > > the server needs

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 01:19, George N. White III wrote: I haven't used CentOS7 for several years, so I was ignoring this thread in the hope others could answer. My not very trustworthy memory is that "/etc/exports" on the server needs the "insecure" option for NFS4 to work, see: https://access.redhat.co

Re: New kernel errors after last update, Fedora 33

On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: > I tried to simply change type from nfs to nfs4 in the fstab in the > client. Unfortunately I then get the response > > mount.nfs4: access denied by server while mounting ... > > There is nothing in the server logs about this. And it is not the >

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 07:40 +0800, Ed Greshko wrote: > > Well, I'm sorry but I'm out of ideas. > > I can mount file systems hosted on a Centos7 server from an F33 > client with no problems with nfsv4. > I can't figure out how to create the problems you're seeing without > modification to configur

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 22:22, Jerome Lille wrote: On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: What is the output of cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" Oh, also, do you happ

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: > > What is the output of > > cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" > Oh, also, do you happen to have a /etc/nfs.conf.d direc

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 05:41, Ed Greshko wrote: That polkitd message occurs here as well.  So, not an issue. What is the output of cat /run/sysconfig/nfs-util Oh, also, do you happen to have a /etc/nfs.conf.d directory? -- People who believe they don't make mistakes have already made one. __

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 04:41, Jerome Lille wrote: On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to have the line # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) RPCNFSDARGS="--no-nfs-version 4" You should check that as well.

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: > > The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to > have the line > > # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) > RPCNFSDARGS="--no-nfs-version 4" > > You should check that as well. > > Bottom line, NFSv4 is

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 00:27, Jerome Lille wrote: On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: [mountd] debug=all And then restart the server. After doing the mount from the client, check the journal for rpc.mountd messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it trie

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: > [mountd] > debug=all > > And then restart the server. > > After doing the mount from the client, check the journal for rpc.mountd > messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it tried v4 first then succeeded on v

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 21:58, Jerome Lille wrote: On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: On 23/02/2021 00:27, Jerome Lille wrote: My nfs.conf is untouched. You do mean that file on the nfs server side, right? Exactly OK Modify that file to have # [mountd] debug=all And then

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: > On 23/02/2021 00:27, Jerome Lille wrote: > > My nfs.conf is untouched. > > You do mean that file on the nfs server side, right? Exactly > > When I do the following command > > mount -v server:/path /path > > > > I get the following > > I

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 00:27, Jerome Lille wrote: On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/ nfs.conf so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.

Re: New kernel errors after last update, Fedora 33

On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: > On 22/02/2021 08:24, Ed Greshko wrote: > >  have not made any changes to the nfs server configuration file /etc/ > > nfs.conf so the defaults are > > in effect. > > > > # vers2=n > > # vers3=y > > # vers4=y > > # vers4.0=y > > # vers4.1=y > >

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/nfs.conf  so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.1=y # vers4.2=y Check to make sure these haven't been altered. FWIW, I did do a test and modi

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 00:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied by server while mounting ... There is nothing in the server logs about this. And it is not the firewall, because ev

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 14:23 -0800, Gordon Messmer wrote: > On 2/18/21 8:38 AM, Jerome Lille wrote: > > But as I said the nfs shares seem to work fine, I can read and > > write to > > files on them. > > > Yep, everything will look fine until an application on your client > tries > to lock a file,

Re: New kernel errors after last update, Fedora 33

On 2/18/21 8:38 AM, Jerome Lille wrote: But as I said the nfs shares seem to work fine, I can read and write to files on them. Yep, everything will look fine until an application on your client tries to lock a file, and then it will hang forever. Locking files during editing is pretty common

Re: New kernel errors after last update, Fedora 33

On 19/02/2021 00:38, Jerome Lille wrote: On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: > On 18/02/2021 03:07, Jerome Lille wrote: > > 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora > > desktop that produces these error messages has some shares from it > > mounted. No errors on the NFS server and the nfs shares

Re: New kernel errors after last update, Fedora 33

On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the NFS server and the nfs shares seems to work fine. Are you using NFSv3 or NFSv4 to mount the s

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 12:08 PM Jerome Lille wrote: > Thanks for the suggestion. I did get more logging > > RPC: 5d78dc3a connect status 107 connected 0 sock state 7 > xs_tcp_setup_socket: connect returned unhandled error -107 > RPC: xs_tcp_state_change client 5d78dc3a

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-17 at 11:43 -0700, Jerry James wrote: > On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille > wrote: > > After the latest update there are some errors in the log that I > > haven't > > seen before. > > > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > > > There

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are two of those per minute continuously. I haven't noticed any > other pro

Re: New kernel errors after last update, Fedora 33

On Wed, 17 Feb 2021 10:10:23 -0800 Clifford Snow wrote: > I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. Same here. Sounds like some application is running that causes that error and I'm not running that app. ___ users mailing list

Re: New kernel errors after last update, Fedora 33

I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. On Wed, Feb 17, 2021 at 9:34 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are tw

New kernel errors after last update, Fedora 33

After the latest update there are some errors in the log that I haven't seen before. kernel: xs_tcp_setup_socket: connect returned unhandled error -107 There are two of those per minute continuously. I haven't noticed any other problems with the system, but wondering about those messages are abou

Re: Display Manager Lagging After Last Update

On 03/06/18 05:08, Stephen Morris wrote: > On 5/3/18 7:36 am, Ed Greshko wrote: >> On 03/05/18 04:18, Stephen Morris wrote: >>> As a matter of interest, which version of the nvidia drivers are you using? >> >> 390.25-3   And I don't use wayland as performance in KDE is horrible > > From the negativ

Re: Display Manager Lagging After Last Update

On 5/3/18 7:36 am, Ed Greshko wrote: On 03/05/18 04:18, Stephen Morris wrote: As a matter of interest, which version of the nvidia drivers are you using? 390.25-3   And I don't use wayland as performance in KDE is horrible From the negativo17 repositories I'm using the source code for the sa

Re: Display Manager Lagging After Last Update

On 03/05/18 04:18, Stephen Morris wrote: > As a matter of interest, which version of the nvidia drivers are you using? 390.25-3   And I don't use wayland as performance in KDE is horrible -- If simple questions can be answered with a simple google query then why are there sso many of them?

Re: Display Manager Lagging After Last Update

On 4/3/18 9:02 pm, Ed Greshko wrote: On 03/04/18 16:16, Stephen Morris wrote: Thanks Ed, I made that change and it rectified the lagging issues with gdm and gnome. Now to work out why dkms hasn't compiled the nvidia driver under the new kernel. FWIW, the lagging issues may be a byproduct of yo

Re: Display Manager Lagging After Last Update

On 03/04/18 16:16, Stephen Morris wrote: > Thanks Ed, I made that change and it rectified the lagging issues with gdm and > gnome. Now to work out why dkms hasn't compiled the nvidia driver under the > new > kernel. FWIW, the lagging issues may be a byproduct of your video driver. Anyway, whil

Re: Display Manager Lagging After Last Update

On 04/03/2018 13:39, Ed Greshko wrote: On 03/04/18 09:57, Stephen Morris wrote: Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the problem description, even though gnome shell lags with gdm, when gnome under Xorg is started the lag disappears. The only difference in my case

Re: Display Manager Lagging After Last Update

On 03/04/18 09:57, Stephen Morris wrote: > Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the > problem > description, even though gnome shell lags with gdm, when gnome under Xorg is > started the lag disappears. The only difference in my case is that the issue > was > not c

Re: Display Manager Lagging After Last Update

On 4/3/18 11:37 am, Ed Greshko wrote: On 03/04/18 08:25, Stephen Morris wrote: My issue starts with gdm, with gnome shell taking up to 800% of the cpu and causing, ctrl+alt+F2 to switch to another login to time out, and if I launch gnome from gdm the issue with gnome shell continues and causes

Re: Display Manager Lagging After Last Update

On 03/04/18 08:25, Stephen Morris wrote: > My issue starts with gdm, with gnome shell taking up to 800% of the cpu and > causing, ctrl+alt+F2 to switch to another login to time out, and if I launch > gnome > from gdm the issue with gnome shell continues and causes gnome itself to lag. > If I > lo

Re: Display Manager Lagging After Last Update

On 2/3/18 4:45 am, Jon LaBadie wrote: I had very slow logins from sddm and lightdm. Not as bad from gdm, but still not good. My culprit was staring an Xvnc server gnome session from my Mate autostart. Clue was 50 gnome processes I owned after logging into a Mate session. jl My issue starts

Re: Display Manager Lagging After Last Update

On 01/03/18 08:45, Ed Greshko wrote: On 03/01/18 05:16, Stephen Morris wrote: On 28/2/18 10:11 am, Ed Greshko wrote: On 02/28/18 04:37, Stephen Morris wrote: I might be getting confused with Ubuntu, but I thought there was a .conf file somewhere that held the specification of the default displ

Re: Display Manager Lagging After Last Update

On 03/01/18 05:16, Stephen Morris wrote: > On 28/2/18 10:11 am, Ed Greshko wrote: >> On 02/28/18 04:37, Stephen Morris wrote: >>> I might be getting confused with Ubuntu, but I thought there was a .conf >>> file >>> somewhere that held the specification of the default display manager that >>> cou

Re: Display Manager Lagging After Last Update

On 28/2/18 10:11 am, Ed Greshko wrote: On 02/28/18 04:37, Stephen Morris wrote: I might be getting confused with Ubuntu, but I thought there was a .conf file somewhere that held the specification of the default display manager that could easily be edited to swap between any of the available disp

Re: Display Manager Lagging After Last Update

On 02/28/18 05:37, Stephen Morris wrote: > > If I remember correctly, I think in F25 or F26 lightdm was the display > manager used > by default No. It depended on the "spin" or Desktop you installed.    If you installed "Workstation"  aka GNOME it has always been gdm.  If you installed the KDE

Re: Display Manager Lagging After Last Update

On 02/28/18 04:37, Stephen Morris wrote: > I might be getting confused with Ubuntu, but I thought there was a .conf file > somewhere that held the specification of the default display manager that > could > easily be edited to swap between any of the available display managers that > you > happen

Re: Display Manager Lagging After Last Update

On 28/2/18 7:46 am, Joe Zeff wrote: On 02/27/2018 12:37 PM, Stephen Morris wrote: I'm not using sddm because when I tried it, I didn't like its presentation layer, and the same applies to kdm. Have you tried lightdm? If I remember correctly, I think in F25 or F26 lightdm was the display m

Re: Display Manager Lagging After Last Update

On 02/27/2018 12:37 PM, Stephen Morris wrote: I'm not using sddm because when I tried it, I didn't like its presentation layer, and the same applies to kdm. Have you tried lightdm? ___ users mailing list -- users@lists.fedoraproject.org To unsubscri

Re: Display Manager Lagging After Last Update

On 26/2/18 9:50 pm, Ed Greshko wrote: On 02/26/18 18:47, Ed Greshko wrote: ll /etc/systemd/system/display-manager.service   will point to what you're using. systemctl status display-manager also will tell you Thanks Ed, that tells me I'm using gdm. I might be getting confused with Ubuntu,

Re: Display Manager Lagging After Last Update

On 02/26/18 18:47, Ed Greshko wrote: > ll /etc/systemd/system/display-manager.service   will point to what you're > using. systemctl status display-manager also will tell you -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature

Re: Display Manager Lagging After Last Update

On 02/26/18 18:39, Stephen Morris wrote: >     I have forgotten whether I'm running gdm or kdm, and I've forgotten where > to > look to find out, but since the last system update I did two days ago, when > the > display manager is displaying the list of user who can log in, cursor > movements an

Display Manager Lagging After Last Update

Hi,     I have forgotten whether I'm running gdm or kdm, and I've forgotten where to look to find out, but since the last system update I did two days ago, when the display manager is displaying the list of user who can log in, cursor movements and mouse movements lag something cronic, but wh

Re: wifi won't start after last update f26

On 01/11/18 18:15, François Patte wrote: > Le 11/01/2018 à 09:28, Ed Greshko a écrit : >> On 01/11/18 16:16, François Patte wrote: >>> Le 10/01/2018 à 17:30, stan a écrit : >>>> On Wed, 10 Jan 2018 12:18:09 +0100 >>>> François Patte wrote: >>>&g

Re: wifi won't start after last update f26

Le 11/01/2018 à 09:28, Ed Greshko a écrit : > On 01/11/18 16:16, François Patte wrote: >> Le 10/01/2018 à 17:30, stan a écrit : >>> On Wed, 10 Jan 2018 12:18:09 +0100 >>> François Patte wrote: >>> >>>> Bonjour, >>>> >>>> Aft

Re: wifi won't start after last update f26

On 01/11/18 16:16, François Patte wrote: > Le 10/01/2018 à 17:30, stan a écrit : >> On Wed, 10 Jan 2018 12:18:09 +0100 >> François Patte wrote: >> >>> Bonjour, >>> >>> After last update of f26, the wifi does not start on a laptop. >> Have you

Re: wifi won't start after last update f26

Le 10/01/2018 à 17:30, stan a écrit : > On Wed, 10 Jan 2018 12:18:09 +0100 > François Patte wrote: > >> Bonjour, >> >> After last update of f26, the wifi does not start on a laptop. > > Have you checked what was in the last update? Look in /var/log for the >

Re: wifi won't start after last update f26

On Wed, 10 Jan 2018 12:18:09 +0100 François Patte wrote: > Bonjour, > > After last update of f26, the wifi does not start on a laptop. Have you checked what was in the last update? Look in /var/log for the latest dnf.rpm.log and check which packages were updated. It is possible that

Re: wifi won't start after last update f26

Le 10/01/2018 à 12:39, Patrick O'Callaghan a écrit : > On Wed, 2018-01-10 at 12:18 +0100, François Patte wrote: >> Bonjour, >> >> After last update of f26, the wifi does not start on a laptop. >> >> The wifi card is a Broadcom 4312 [14e4:4315]. >>

Re: wifi won't start after last update f26

On Wed, 2018-01-10 at 12:18 +0100, François Patte wrote: > Bonjour, > > After last update of f26, the wifi does not start on a laptop. > > The wifi card is a Broadcom 4312 [14e4:4315]. > > 1- The driver b43 is there but not loaded during the boot sequence. > >

wifi won't start after last update f26

Bonjour, After last update of f26, the wifi does not start on a laptop. The wifi card is a Broadcom 4312 [14e4:4315]. 1- The driver b43 is there but not loaded during the boot sequence. 2- I tried to load it using modprobe, but the wifi indicator does not light up (do I have to reboot the

Re: last update f25 db5 error

On 07/16/17 16:40, François Patte wrote: > Bonjour, > > With last update of kernel (4.11.9-200.fc25.x86_64) akmod is unable to > install nvidia modules. > > Error message: > > erreur : db5 erreur(-30969) de dbenv->open: BDB0091 DB_VERSION_MISMATCH: > Database environ

Re: last update f25 db5 error

On Sun, 2017-07-16 at 10:40 +0200, François Patte wrote: > Bonjour, > > With last update of kernel (4.11.9-200.fc25.x86_64) akmod is unable to > install nvidia modules. > > Error message: > > erreur : db5 erreur(-30969) de dbenv->open: BDB0091 DB_VERSION_MISMATCH: >

last update f25 db5 error

Bonjour, With last update of kernel (4.11.9-200.fc25.x86_64) akmod is unable to install nvidia modules. Error message: erreur : db5 erreur(-30969) de dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch erreur : impossible d'ouvrir l'index Packages en

Re: last update: thunderbird crashes

On 07/02/17 05:14, François Patte wrote: > With last thunderbird update: it often crashes, it is impossible to send > a mail when enigmail is activated I am using F25 with T-Bird 5.2.1 and enigmail 1.9.7. This message is being sent signed. I've also just sent to another account a signed an

last update: thunderbird crashes

Bonsoir, With last thunderbird update: it often crashes, it is impossible to send a mail when enigmail is activated Regards -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél.

Last update an systemd

I have Linux oh1rdf.ampr.org 4.7.4-200.fc24.i686+PAE #1 SMP Thu Sep 15 18:58:19 UTC 2016 i686 i686 i386 GNU/Linux System running, which I admin mostly remote. Now, after last "dnf update" I can't reboot system, or systemd does not response, no service status can't be checked, I get only example t

last update

Hello, Here are 2 warning messages that I got during the last update! warning: file /lib/modules/4.3.6-201.fc22.x86_64/updates: remove failed: No such file or directory Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y Is it normal

Re: last update

On Fri, 18 Mar 2016 17:36:18 +0100 "Patrick Dupre" wrote: > > Here are 2 warning messages that I got during the last update! > > warning: file /lib/modules/4.3.6-201.fc22.x86_64/updates: remove > failed: No such file or directory > > Disabling early microcode,

Extremely slow LXR indexing with mysql after last update

Don't see any errors but indexing a fairly large set of LXR versions of various programs with genxref program now taking extreme time. Previously only took a few minutes to zip though lots of projects/versions. See alternating 100% cpu on cores and what looks like constant disk usage and proce

Re: Fedora 12 Gnome-Desktop since last update very slow

Hello again, Am 08.03.2010 10:09, schrieb Jürgen Dankoweit: > Hello to the list, > > since the last update - look at the protocol at the end of the mail - > Fedora 12 Gnome-Desktop is very slow. Every action takes seconds before > it is executed: > (*) Opening a terminal wind

Re: Fedora 12 Gnome-Desktop since last update very slow

Am 08.03.2010 10:53, schrieb Hiisi: > 2010/3/8 Jürgen Dankoweit : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Hello to the list, >> >> since the last update - look at the protocol at the end of the mail - >> Fedora 12 Gnome-Desktop is

Re: Fedora 12 Gnome-Desktop since last update very slow

2010/3/8 Jürgen Dankoweit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello to the list, > > since the last update - look at the protocol at the end of the mail - > Fedora 12 Gnome-Desktop is very slow. Every action takes seconds before > it is executed:

Fedora 12 Gnome-Desktop since last update very slow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello to the list, since the last update - look at the protocol at the end of the mail - Fedora 12 Gnome-Desktop is very slow. Every action takes seconds before it is executed: (*) Opening a terminal window: 2 sec (*) In the terminal: su root and

Re: Firefox lockup after last update

--- On Sun, 2/21/10, Vincent Onelli wrote: > > From: Patrick Bartek > > > --- On Sat, 2/20/10, Vincent Onelli > wrote: > > > > > Today after last update Firefox lockup every > time. I toke > > > the following > > > steps in try to

Re: Firefox lockup after last update

> Message: 1 > Date: Sat, 20 Feb 2010 20:47:47 -0800 (PST) > From: Patrick Bartek > --- On Sat, 2/20/10, Vincent Onelli wrote: > > > Today after last update Firefox lockup every time. I toke > > the following > > steps in try to fix what ever went wrong, I

Re: Firefox lockup after last update

--- On Sat, 2/20/10, Vincent Onelli wrote: > Today after last update Firefox lockup every time. I toke > the following > steps in try to fix what ever went wrong, I first execute > "yum reinstall > firefox" no change then "yum update firefox" again no > chan

Firefox lockup after last update

Hello, Today after last update Firefox lockup every time. I toke the following steps in try to fix what ever went wrong, I first execute "yum reinstall firefox" no change then "yum update firefox" again no change so I decided to uninstall Firefox and then reinstall it so now