Weird volume issues (PulseAudio?)
by Christopher
Okay, so this has been bugging me for a while now, but I'm not sure
how to fix it, or to troubleshoot it further. Maybe somebody here can
help.
There are two issues, and they may or may not be related. I'm
currently on F29, but it happened before I upgraded, too.
1. In gdm, the volume indicator always indicates the output device is
Headphones, even when headphones aren't plugged in. gdm doesn't make a
lot of noise to debug before logging in, so I'm not sure if it's
trying to play through the wrong device, or if it's a UI problem.
2. When I log in (I'm using Wayland), everything works fine for about
10 seconds. After that, the volume is automatically muted and I have
to manually unmute it again (even if I've previously muted and unmuted
it before it reaches 10 seconds).
I've tried every knob I can find in the gnome settings, pavucontrol,
and even reset the entire ~/.config/pulse directory and rebooted.
Nothing works.
I have no idea what's going on. Can anybody suggest a fix or help me
identify the problem?
5 years, 4 months
- 2
- 3
mate starting messages
by Robert McBroom
Get a bunch of messages when starting mate. I can't find anything that
is missing.
-----
$ mate-session &
$ ** Message: 18:04:22.174: couldn't access control socket:
/run/user/1001/keyring/control: No such file or directory
Window manager warning: Failed to load theme "BlueMenta": Failed to find
a valid file for theme BlueMenta
Window manager warning: Failed to load theme "Simple": Failed to find a
valid file for theme Simple
Window manager warning: Failed to load theme "Simple": Failed to find a
valid file for theme Simple
[1544742291,000,xklavier.c:xkl_engine_start_listen/] The backend does
not require manual layout management - but it is provided by the application
SSH_AUTH_SOCK=/run/user/1001/keyring/ssh
SSH_AUTH_SOCK=/run/user/1001/keyring/ssh
SSH_AUTH_SOCK=/run/user/1001/keyring/ssh
** (zeitgeist-datahub:11553): WARNING **: 18:04:56.683:
kde-recent-document-provider.vala:174: Couldn't find actor for
'userapp-firefox-4hgwzw'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.403:
kde-recent-document-provider.vala:174: Couldn't find actor for 'kwrite'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.439:
kde-recent-document-provider.vala:174: Couldn't find actor for 'kwrite'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.544:
kde-recent-document-provider.vala:174: Couldn't find actor for 'kate'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.576:
kde-recent-document-provider.vala:174: Couldn't find actor for
'userapp-firefox-4hgwzw'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.813:
kde-recent-document-provider.vala:174: Couldn't find actor for
'userapp-firefox-4hgwzw'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:09.867:
kde-recent-document-provider.vala:174: Couldn't find actor for
'userapp-firefox-4hgwzw'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:10.100:
kde-recent-document-provider.vala:174: Couldn't find actor for 'words'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:10.126:
kde-recent-document-provider.vala:174: Couldn't find actor for
'userapp-firefox-4hgwzw'.
** (zeitgeist-datahub:11553): WARNING **: 18:05:10.162:
kde-recent-document-provider.vala:174: Couldn't find actor for
'LibreOffice'.
5 years, 4 months
- 1
- 0
upgrading from f28 to f29 messed up my system...
by François Patte
Bonjour,
Yesterday I upgraded my system from f28 to f29 and the result is not
what I expected! I can't get my "new" system working correctly: no
graphic interface, a lot of errors in the logs....
I previously upgraded this system from f25 to f27, then from f27 to f28
without any problems...
This system uses raid 1 + lvm: here is the result of lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111,8G 0 disk
├─sda1 8:1 0 1G 0 part
│ └─md2 9:2 0 1G 0 raid1 /boot
├─sda2 8:2 0 60G 0 part
│ └─md127 9:127 0 60G 0 raid1
│ └─debian-deb--racine 253:0 0 29,3G 0 lvm /
├─sda3 8:3 0 1G 0 part
└─sda4 8:4 0 49,8G 0 part
└─md11 9:11 0 49,8G 0 raid1
├─fedora-racine 253:2 0 2G 0 lvm
└─fedora-usr 253:3 0 28G 0 lvm
sdb 8:16 0 111,8G 0 disk
├─sdb1 8:17 0 1G 0 part
│ └─md2 9:2 0 1G 0 raid1 /boot
├─sdb2 8:18 0 60G 0 part
│ └─md127 9:127 0 60G 0 raid1
│ └─debian-deb--racine 253:0 0 29,3G 0 lvm /
├─sdb3 8:19 0 1G 0 part
└─sdb4 8:20 0 49,8G 0 part
└─md11 9:11 0 49,8G 0 raid1
├─fedora-racine 253:2 0 2G 0 lvm
└─fedora-usr 253:3 0 28G 0 lvm
sdc 8:32 0 465,8G 0 disk
└─sdc1 8:33 0 465,8G 0 part
└─md1 9:1 0 465,7G 0 raid1
├─annexes-data 253:7 0 260G 0 lvm /commun
└─annexes-sauvegardes 253:8 0 205G 0 lvm /sauvegardes
sdd 8:48 0 465,8G 0 disk
└─sdd1 8:49 0 465,8G 0 part
└─md1 9:1 0 465,7G 0 raid1
├─annexes-data 253:7 0 260G 0 lvm /commun
└─annexes-sauvegardes 253:8 0 205G 0 lvm /sauvegardes
sde 8:64 0 931,5G 0 disk
├─sde1 8:65 0 40G 0 part
│ └─md4 9:4 0 40G 0 raid1
│ ├─systeme-swap 253:1 0 4G 0 lvm [SWAP]
│ ├─systeme-var 253:5 0 15G 0 lvm /var
│ └─systeme-chiffre 253:6 0 15G 0 lvm
└─sde2 8:66 0 891,5G 0 part
└─md5 9:5 0 891,4G 0 raid1
└─data-home 253:4 0 500G 0 lvm /home
sdf 8:80 0 931,5G 0 disk
├─sdf1 8:81 0 40G 0 part
│ └─md4 9:4 0 40G 0 raid1
│ ├─systeme-swap 253:1 0 4G 0 lvm [SWAP]
│ ├─systeme-var 253:5 0 15G 0 lvm /var
│ └─systeme-chiffre 253:6 0 15G 0 lvm
└─sdf2 8:82 0 891,5G 0 part
└─md5 9:5 0 891,4G 0 raid1
└─data-home 253:4 0 500G 0 lvm /home
sr0 11:0 1 1024M 0 rom
sr1 11:1 1 1024M 0 rom
Don't pay attention to the names (debian or fedora) these are the names
I gave a long time ago and I did not change the labels for some volumes.
Now here are the errors I get in the boot logs:
1- déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
déc. 05 11:33:05 dipankar systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
déc. 05 11:33:05 dipankar systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unité (unit) systemd-modules-load.service a échoué
This error occurs several times during the boot process.
2- A lot of errors about lvm also occur:
déc. 05 11:33:06 dipankar lvm[1178]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé<---- busy
déc. 05 11:33:06 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar kernel: device-mapper: table: 253:0: linear:
Device lookup failed
déc. 05 11:33:06 dipankar kernel: device-mapper: ioctl: error adding
target to table
.................
Here are all messages about lvm in the boot logs:
déc. 05 11:33:05 dipankar lvm[909]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:05 dipankar lvm[909]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Not using lvmetad because
cache update failed.
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:05 dipankar lvm[909]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:05 dipankar lvm[909]: 1 logical volume(s) in volume
group "systeme" monitored
déc. 05 11:33:05 dipankar lvm[909]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:05 dipankar lvm[909]: 1 logical volume(s) in volume
group "debian" monitored
déc. 05 11:33:05 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
-- Subject: L'unité (unit) lvm2-monitor.service a terminé son démarrage
-- L'unité (unit) lvm2-monitor.service a terminé son démarrage, avec le
résultat done.
déc. 05 11:33:06 dipankar systemd[1]: Created slice
system-lvm2\x2dpvscan.slice.
-- Subject: L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son
démarrage
-- L'unité (unit) system-lvm2\x2dpvscan.slice a terminé son démarrage,
avec le résultat done.
-- Subject: L'unité (unit) lvm2-pvscan@9:127.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:127.service a commencé à démarrer.
-- Subject: L'unité (unit) lvm2-pvscan@9:4.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:4.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
-- Subject: L'unité (unit) lvm2-pvscan@9:11.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:11.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Autoactivation reading
from disk instead of lvmetad.
-- Subject: L'unité (unit) lvm2-pvscan@9:5.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:5.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1178]: 2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1182]: 2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
-- Subject: L'unité (unit) lvm2-pvscan@9:1.service a commencé à démarrer
-- L'unité (unit) lvm2-pvscan@9:1.service a commencé à démarrer.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1222]: 2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: found device with
duplicate /dev/sdb2
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: found device with
duplicate /dev/md127
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Disabling lvmetad cache
which does not support duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Scan found duplicate PVs.
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Not using lvmetad
because cache update failed.
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Autoactivation reading
from disk instead of lvmetad.
déc. 05 11:33:06 dipankar lvm[1237]: 2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Not using device
/dev/sdb2 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Not using device
/dev/md127 for PV LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG.
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: PV
LjsptA-OrMt-ClBo-ksAo-ZCcO-eAtj-NGGgvG prefers device /dev/sda2 because
of previous preference.
déc. 05 11:33:06 dipankar lvm[1253]: 2 logical volume(s) in volume
group "fedora" now active
déc. 05 11:33:06 dipankar lvm[1178]: 1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1178]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1178]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]: 1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1222]: 1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1237]: 1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1182]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1182]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1182]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]: 1 logical volume(s) in volume
group "data" now active
déc. 05 11:33:06 dipankar lvm[1222]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1222]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1222]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1222]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1237]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1237]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1237]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1237]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]: 3 logical volume(s) in volume
group "systeme" now active
déc. 05 11:33:06 dipankar lvm[1253]: WARNING: Device mismatch detected
for debian/deb-racine which is accessing /dev/md127 instead of /dev/sda2.
déc. 05 11:33:06 dipankar lvm[1253]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1253]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1222]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1222]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1237]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1237]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1253]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1253]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1182]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1182]: Failed to suspend debian/deb-racine.
déc. 05 11:33:06 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:06 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1222]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1182]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1178]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1178]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1222]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1182]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1178]: debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1178]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1178]: 1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1178]: debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1222]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1237]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1237]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1253]: device-mapper: reload ioctl on
(253:0) failed: Périphérique ou ressource occupé
déc. 05 11:33:07 dipankar lvm[1253]: Failed to suspend debian/deb-racine.
déc. 05 11:33:07 dipankar lvm[1182]: debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1182]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1182]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1182]: 1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1182]: debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]: debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1222]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1222]: 1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1222]: debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1237]: debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1237]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1237]: 1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1237]: debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1253]: debian: refresh before
autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1253]: Cannot activate LVs in VG debian
while PVs appear on duplicate devices.
déc. 05 11:33:07 dipankar lvm[1253]: 1 logical volume(s) in volume
group "debian" now active
déc. 05 11:33:07 dipankar lvm[1253]: debian: autoactivation failed.
déc. 05 11:33:07 dipankar lvm[1178]: 2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:127.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:127.service a échoué
-- L'unité (unit) lvm2-pvscan@9:127.service a échoué, avec le résultat
failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:127 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1222]: 2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:11.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:11.service a échoué
-- L'unité (unit) lvm2-pvscan@9:11.service a échoué, avec le résultat
failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:11 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1182]: 2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:4.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:4.service a échoué
-- L'unité (unit) lvm2-pvscan@9:4.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:4 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1237]: 2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:5.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:5.service a échoué
-- L'unité (unit) lvm2-pvscan@9:5.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:5 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
déc. 05 11:33:07 dipankar lvm[1253]: 2 logical volume(s) in volume
group "annexes" now active
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Main
process exited, code=exited, status=5/NOTINSTALLED
déc. 05 11:33:07 dipankar systemd[1]: lvm2-pvscan@9:1.service: Failed
with result 'exit-code'.
-- Subject: L'unité (unit) lvm2-pvscan@9:1.service a échoué
-- L'unité (unit) lvm2-pvscan@9:1.service a échoué, avec le résultat failed.
déc. 05 11:33:07 dipankar audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan@9:1 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
All the boot log (result of journalctl -xb) can be seen here:
http://www.mi.parisdescartes.fr/~patte/journal
I hope that someone could help me.
Thank you.
--
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. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
5 years, 4 months
- 4
- 7
Gnome2 Key Storage
by Robert McBroom
Firefox pops up a window saying
Enter password to unlock the Certificate/Key storage
an application wants access to "Gnome2 Key Storage" but it is locked
Can't cancel or clear the window and none of my passwords work. I've
never accessed such. Where is it and how do I set it or clear it.
5 years, 4 months
- 2
- 4
Unable to use molecule
by Sudheer S
Hello,
I am unable to get molecule to work.
Here's the output when I try to run:
molecule test
--> Validating schema
/home/sudheer/workspace/sudheer-projects/ansible-role-ruby/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix
└── default
├── destroy
├── syntax
├── create
├── prepare
├── converge
├── lint
├── side_effect
├── verify
└── destroy
--> Scenario: 'default'
--> Action: 'destroy'
PLAY [Destroy]
*****************************************************************
TASK [Destroy molecule instance(s)]
********************************************
fatal: [localhost]: FAILED! => {"msg": "An unhandled exception
occurred while templating '{{ lookup('file', molecule_file) |
molecule_from_yaml }}'. Error was a <class
'ansible.errors.AnsibleError'>, original message: template error while
templating string: no filter named 'molecule_from_yaml'. String: {{
lookup('file', molecule_file) | molecule_from_yaml }}"}
PLAY RECAP
*********************************************************************
localhost : ok=0 changed=0 unreachable=0
failed=1
ERROR:
An error occurred during the test sequence action: 'destroy'. Cleaning up.
--> Scenario: 'default'
--> Action: 'destroy'
PLAY [Destroy]
*****************************************************************
TASK [Destroy molecule instance(s)]
********************************************
fatal: [localhost]: FAILED! => {"msg": "An unhandled exception
occurred while templating '{{ lookup('file', molecule_file) |
molecule_from_yaml }}'. Error was a <class
'ansible.errors.AnsibleError'>, original message: template error while
templating string: no filter named 'molecule_from_yaml'. String: {{
lookup('file', molecule_file) | molecule_from_yaml }}"}
PLAY RECAP
*********************************************************************
localhost : ok=0 changed=0 unreachable=0
failed=1
ERROR:
I have installed Docker and molecule packages. I am able to use Docker
outside of molecule on the same host.
I have installed these pacakges.
python3-molecule.noarch 2.19-2.fc29 @updates
python2-docker.noarch 3.5.0-1.fc29 @fedora
docker.x86_64 2:1.13.1-62.git9cb56fd.fc29 @fedora
I have tried removing python2-docker and installing python3-docker.
There's no change in result.
Am I missing something?
-
Sudheer
5 years, 4 months
- 2
- 2
F29 Upgrade Still Boots F27 Kernel - Recommendations Please
by David Dembrow
When I upgraded from F27 to F28 I noticed that it would still boot up
with the F27 kernel. I thought that eventually F28 would catch up with
the periodic updates and it apparently has not. Now that I have
upgraded to F29 and it is still booting with the F27 kernel I would like
to find a resolution.
This is on a few older systems which are using the 32-bit operating
system. I see boot options for a F29 i686, F28 i686, and F27 i686+PAE
available. It looks like the default is the F27 i686+PAE kernel.
I tried booting with the other kernels and the graphic login fails so I
may not have another option. Has my hardware gone obsolete?
Thanks for any suggestions.
---d.dembrow
5 years, 4 months
- 3
- 2
Fwd: Problems with Fedora 29 on my hardware
by Mr Brian Domenick
Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using
nouveau video and wireless works. I tried to upgrade to Fedora 29. After
upgrade with dnf it is fairly broken. Everything came up on the surface,
but it was sluggish and sudo bash was very slow to autheticate and it
was popping multiple oops messages at the top of the screen. I then did
a fresh install of Fedora 29. This seemed to mostly work and no
immediate sluggishness once done. I then upgraded using dnf to the
latest software. This is where the bad behavior came from. After dnf
upgrade sluggishness on sudo again as opposed to instaneous
authentication before dnf, wifi could now nut be shut off. Oops messages
on top of screen and complaining about one of the cpu's in dmesg and
also complaining about nouveau. Wifi became broken and gnome network
manager to shut it off wouldn't do anything. It showed as up but a
browser wouldn't work. When it popped up report screen to report kernel
problem it was populated with no info and all you could really do was
close it. Funny thing is I did a fresh install of 29 first on my samsung
laptop which has strictly intel graphics and different wireless and
everything works 100% on that laptop.
Any thoughts would be appreciated, I put Fedora 28 back on the HP and
its fine with all the latest software there.
Brian
5 years, 4 months
- 1
- 0
persistent name from ifcfg-internal
by sean darcy
I'm trying to get the interface on a multi-homed machine named "internal"
I have ifcfg-internal:
cat ifcfg-internal
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
TYPE=Ethernet
BOOTPROTO=none
DEVICE=internal
ONBOOT=yes
IPADDR=10.10.11.253
PREFIX=24
DEFROUTE=no
IPV4_FAILURE_FATAL=no
IPV6INIT=no
USERCTL=no
HWADDR=50:7b:9d:0b:8a:ab
rebboted, but:
ifconfig
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet)
As I understand, NM scans the ifcfg files for HWADDR's. If there's a
match, it names the interface the DEVICE name.
Why not here?
sean
5 years, 4 months
- 4
- 10
F29 Wail at the Firewall (long; sorry!)
by Beartooth
In the words of the starlet, I try to be cynical [read paranoid]
about security, but I just can't keep up.
I do some of my email and all of my Gmane activity (including
this list) at the address above, from my local access provider, Comcast;
but I do most of my email (and my wife does all of hers) at my own
domain, to which we connect by ssh.
Recently we've been moving machines about physically, from floor
to floor and connection to connection. We've also been getting lots of
timeouts. When I asked my domain host about it, he told me it was my own
firewall cutting us off. It blocks connections out from our IP address
if they fail more than it likes.
I read -- no, I study, hard -- whatever security news comes
across lists and sites I follow; I usually think I understand, more or
less, what the hazard is. I think so this time. It seems the current
default firewall is harder-nosed about failures to connect than it was;
afaict, *we* are doing little if anything different.
But in all my years running Linux (since RedHat 7), I have not
become savvy about writing nor editing code, any more than I've become a
motor mechanic by driving (since about 1955 or so). I understand that it
is necessary to throttle any malware that might try to call home; so I
shouldn't just comment out whatever does the blocking, even if I knew
where it was.
So, I THINK, I ought to enlarge a/o lubricate the opening in the
firewall that lets US out, but not make it any easier than I can help for
supposed malware to get out. Does that make sense?
If so, where do I go (i.e., what file do I open), and what
changes do I make, to accomplish that?
--
Beartooth Codger, Not Quite Clueless
Remember I know little (precious little!)
of which way is up.
5 years, 4 months
- 7
- 26
Strange uptime behavior under qemu-kvm
by Sebastian Himmler
Hi all,
I've experienced some strange behavior on Fedora 28 client systems. I have some of them virtualized on a qemu-kvm hypervisor. All these systems take the hypervisor uptime as their own. This is really annoying, since I can not determine how long a host is up.
If I take a look in the boot log I can see this:
...snip...
[ 0.000000] Hypervisor detected: KVM
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[137891542.045328] kvm-clock: cpu 0, msr c6c01001, primary cpu clock
[137891542.045329] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
...snap...
Is there any possibility to turn this off, so that the VM takes its own uptime?
Really much thanks for any solution / suggestion! Sebastian
5 years, 4 months
- 1
- 0