Results 1 to 9 of 9

Thread: 'System problem detected' message for about 4 weeks now

  1. #1
    Join Date
    Aug 2006
    Location
    gypsy encampment
    Beans
    542
    Distro
    Lubuntu 18.04 Bionic Beaver

    'System problem detected' message for about 4 weeks now

    This is from my Lubuntu 18.04 32-bit machine.

    I have no clue what to do about this; I don't use kwallet or gnome keyring. A Google search said to look at journalctl -

    Code:
     journalctl -p 3 -b
    
    Aug 15 11:28:21 Flying-Cloud kernel: sd 2:0:0:0: [sdb] No Caching mode page found
    Aug 15 11:28:21 Flying-Cloud kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
    Aug 15 11:28:43 Flying-Cloud kernel: scsi 2:0:0:1: Failed to get diagnostic page 0x1
    Aug 15 11:28:43 Flying-Cloud kernel: scsi 2:0:0:1: Failed to bind enclosure -19
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No 
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM adding faulty module: pam_gnome_keyring.so
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM adding faulty module: pam_kwallet.so
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file 
    Aug 15 11:28:51 Flying-Cloud lightdm[580]: PAM adding faulty module: pam_kwallet5.so
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No 
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM adding faulty module: pam_gnome_keyring.so
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM adding faulty module: pam_kwallet.so
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file 
    Aug 15 11:28:56 Flying-Cloud lightdm[694]: PAM adding faulty module: pam_kwallet5.so
    I would welcome suggestions.
    System76 Serval Pro 7: Lubuntu 18.04; Dell Latitude D800: Lubuntu 18.04; Zotac Z-Box ID45: LinHES 8.5.1

  2. #2
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 'System problem detected' message for about 4 weeks now

    The first command is probably not needed but for the proper (Safety) way, I always make sure to have a back-up.(When mucking about)
    Code:
    sudo cp -a /etc/pam.d /etc/pam.d_bak
    sudo pam-auth-update --force
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags

  3. #3
    Join Date
    Aug 2006
    Location
    gypsy encampment
    Beans
    542
    Distro
    Lubuntu 18.04 Bionic Beaver

    Re: 'System problem detected' message for about 4 weeks now

    Thanks! So this basically forces PAM module to update?

    I also found this in /var/crash -
    Code:
    ~$ ls -l /var/crash
    total 596
    -rw-r----- 1 root whoopsie 607705 Aug 15 10:40 _sbin_plymouthd.0.crash
    Last edited by MoebusNet; 4 Weeks Ago at 06:22 PM.
    System76 Serval Pro 7: Lubuntu 18.04; Dell Latitude D800: Lubuntu 18.04; Zotac Z-Box ID45: LinHES 8.5.1

  4. #4
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 'System problem detected' message for about 4 weeks now

    Ah more to the story, what dose this produce:
    Code:
    apt policy plymouth-x11
    And sometimes as easy as:
    Code:
    sudo chown -R $USER: /lib/plymouth
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags

  5. #5
    Join Date
    Aug 2006
    Location
    gypsy encampment
    Beans
    542
    Distro
    Lubuntu 18.04 Bionic Beaver

    Re: 'System problem detected' message for about 4 weeks now

    Code:
    ~$ apt policy plymouth-x11
    plymouth-x11:
      Installed: (none)
      Candidate: 0.9.3-1ubuntu7.18.04.2
      Version table:
         0.9.3-1ubuntu7.18.04.2 500
            500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages
         0.9.3-1ubuntu7 500
            500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
    System76 Serval Pro 7: Lubuntu 18.04; Dell Latitude D800: Lubuntu 18.04; Zotac Z-Box ID45: LinHES 8.5.1

  6. #6
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 'System problem detected' message for about 4 weeks now

    See if installing it helps.
    Also I left this out:
    A possible solution not mentioned yet is to run:
    Code:
    sudo dpkg-reconfigure Plymouth
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags

  7. #7
    Join Date
    Aug 2006
    Location
    gypsy encampment
    Beans
    542
    Distro
    Lubuntu 18.04 Bionic Beaver

    Re: 'System problem detected' message for about 4 weeks now

    OK, I'll try restarting to see if the error message comes back. Thanks!
    System76 Serval Pro 7: Lubuntu 18.04; Dell Latitude D800: Lubuntu 18.04; Zotac Z-Box ID45: LinHES 8.5.1

  8. #8
    Join Date
    Aug 2006
    Location
    gypsy encampment
    Beans
    542
    Distro
    Lubuntu 18.04 Bionic Beaver

    Re: 'System problem detected' message for about 4 weeks now

    I cleared /var/crash and no longer see the 'System problem detected' error message about plymouth on boot-up.

    journalctl still has the same error messages about kwallet & gnome_keyring, but that doesn't seem to be triggering a 'System problem' error message; maybe because kwallet & gnome_keyring are not installed (I haven't checked) or are unconfigure (I don't use them).

    I think I'll call this SOLVED unless I start getting the error message again. Thanks for the help!
    Last edited by MoebusNet; 4 Weeks Ago at 07:07 PM.
    System76 Serval Pro 7: Lubuntu 18.04; Dell Latitude D800: Lubuntu 18.04; Zotac Z-Box ID45: LinHES 8.5.1

  9. #9
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 'System problem detected' message for about 4 weeks now

    Yep I see other stuff related to my heavy tweaking systems:
    Code:
    Aug 15 07:45:57 arch systemd-udevd[310]: /etc/udev/rules.d/60-scheduler.rules:2: Invalid key/value pair, starting at character 66 (',')
    Aug 15 07:45:57 arch systemd-udevd[310]: /etc/udev/rules.d/60-scheduler.rules:4: Invalid key/value pair, starting at character 69 (',')
    Aug 15 07:45:57 arch systemd-udevd[310]: /etc/udev/rules.d/60-scheduler.rules:8: Invalid key/value pair, starting at character 69 (',')
    Aug 15 07:45:57 arch systemd-udevd[407]: crypto_user: Failed to open ATTR{/sys/module/crypto_user/queue/scheduler} for writing: No such file or directory
    Aug 15 07:45:57 arch systemd-udevd[407]: crypto_user: Failed to open ATTR{/sys/module/crypto_user/queue/scheduler} for writing: No such file or directory
    Glad to hear the message went away though, <Thanks for being the better part of UF. >
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •