Re: Can't create volatile files... -- What is "gluster"?
On 01/02/2018 10:19 PM, Jonathan Ryshpan wrote: Can someone tell me what this is about? A message in the journal shortly after a boot reads: Failed to start Create Volatile Files and Directories which leads me to the following systemd status query. Jan 02 21:34:31 amito.localdomain systemd-tmpfiles[860]: [/usr/lib/tmpfiles.d/gluster.conf:2] Unknown user 'gluster'. gluster is a distributed file system. I wouldn't expect it to be installed by default and somehow there's a config file installed without the user being created. What is the output of the following two commands? rpm -qf /usr/lib/tmpfiles.d/gluster.conf rpm -qa | grep gluster ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Can't create volatile files... -- What is "gluster"?
Can someone tell me what this is about? A message in the journal shortly after a boot reads: Failed to start Create Volatile Files and Directories which leads me to the following systemd status query. $ systemctl status systemd-tmpfiles-setup.service ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-01-02 21:34:31 PST; 30min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Main PID: 860 (code=exited, status=1/FAILURE) Jan 02 21:34:31 amito.localdomain systemd[1]: Starting Create Volatile Files and Directories... Jan 02 21:34:31 amito.localdomain systemd-tmpfiles[860]: [/usr/lib/tmpfiles.d/gluster.conf:2] Unknown user 'gluster'. Jan 02 21:34:31 amito.localdomain systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Jan 02 21:34:31 amito.localdomain systemd[1]: Failed to start Create Volatile Files and Directories. Jan 02 21:34:31 amito.localdomain systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Jan 02 21:34:31 amito.localdomain systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: gthumb failing to show jpeg/gif/png thumbnails in browser window [SOLVED]
On Tue, 2 Jan 2018, Max Pyziur wrote: Greetings, Suddenly, gthumb has stopped showing thumbnails of jpegs and other types of files in the browser window. If I do something like -O, I can open a file directly to view it. However, when I do a -R in a directory, the window doesn't refresh. Instead, othe types of files (*.txt, *.svg, e.g.) show up. I can view the contents of directories using other image viewing software. I know that I was typing quickly, and perhaps something caused the jpegs and other files to be masked through an inadvertant configuration procedure. However, as yet, I haven't been able to restore gthumb to my preferred configuration. I've looked of the ~/.thumbnails directories; found one, deleted it. The new thumbnails that appear are referenced to the *.txt, *svg files only. None of the other files or thumbnails get recreated. Any advice in this situation would be appreciated. In the meantime, I'll keep looking and fiddling. Thank you. Max Pyziur p...@brama.com Apologies for the disruption. In the Browser window along the bottom is a dropdown with the prefix "Show:" Mine showed "All". However, when I went to "Personalize" I saw that the "General Filter" was set for "Text Files." (Don't know how that happened). Setting it for "All Images" restored my usual configuration. The confounding part was that in accessing this webpage: https://help.gnome.org/users/gthumb/stable/gthumb-filtering.html.en It indicates to go to "View->Filger," something which I couldn't find. fyi, MP p...@brama.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
gthumb failing to show jpeg/gif/png thumbnails in browser window
Greetings, Suddenly, gthumb has stopped showing thumbnails of jpegs and other types of files in the browser window. If I do something like -O, I can open a file directly to view it. However, when I do a -R in a directory, the window doesn't refresh. Instead, othe types of files (*.txt, *.svg, e.g.) show up. I can view the contents of directories using other image viewing software. I know that I was typing quickly, and perhaps something caused the jpegs and other files to be masked through an inadvertant configuration procedure. However, as yet, I haven't been able to restore gthumb to my preferred configuration. I've looked of the ~/.thumbnails directories; found one, deleted it. The new thumbnails that appear are referenced to the *.txt, *svg files only. None of the other files or thumbnails get recreated. Any advice in this situation would be appreciated. In the meantime, I'll keep looking and fiddling. Thank you. Max Pyziur p...@brama.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: samba, deleting non-empty dir fails
OK I'm pretty sure this is either a gvfs-smb bug, or maybe even a libsmbclient bug. And the reason why is because this problem doesn't happen when I change the client to Windows 10, and macOS 10.13. The target directory does delete in those two cases. Weird bug though. Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
samba, deleting non-empty dir fails
The gist is, whenever a directory has one or more files in it, it can't be deleted. And it's pretty damn screwy that I can't figure this out with a Google search. F27 Server, F27 Workstation, i.e. Nautilus as well as smbclient With Nautilus, I click on the target dir, click the delete button, I get a dialog asking if I want it deleted permanently, and a red delete button. I click the red delete button, the target dir vanishes but a.) behind the scenes ssh'd into the server, the dir is still there b.) if in Nautilus I click on a parent dir and then back to the containing directory (refresh the directory that contains the directory I want deleted) the target dir is still there. When I do it with smbclient's rmdir command, no error. But it also isn't deleted. No errors are logged on the server or the client. I can do 'rm -rf' while logged in as the user (chris) who owns the directory and the directory and contents are then deleted. The target directory has the most permissive permissions I can imagine: drwxrwxrwx. 1 chris chris 266 Jan 2 16:06 test The directory which contains this directory: drwxrwx---. 1 chris smbusers 286 Jan 2 16:06 scratch [chris@f27s scratch]$ ls -la test total 16 drwxrwxrwx. 1 chris chris 72 Jan 2 16:41 . drwxrwx---. 1 chris smbusers 218 Jan 2 16:42 .. -rwxrwxrwx. 1 chris chris 54 Nov 21 13:14 test1.txt -rwxrwxrwx. 1 chris chris 529 Dec 17 00:19 test2.txt -rwxrwxrwx. 1 chris chris 749 Dec 14 20:19 test3.txt -rwxrwxrwx. 1 chris chris1399 Dec 5 16:50 test4.txt [chris@f27s scratch]$ So no hidden files. And yes the mount point (and everything under it) has samba_share_t:s0 so this is not an selinux problem (and there are no AVC errors). If I delete the test$.txt files, select all the delete, they really delete. And now I can delete the empty directory. Haha! What the hell?! Maybe it's a feature that users can create directories and files but can't effectively recursively delete a whole directory?? I honestly cannot wait for the OMFG moment on this... -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Device or resource busy when trying to do a software update
OK just a thought. On Tue, Jan 2, 2018 at 2:23 PM, Martin Wagner wrote: > On Tue, 2018-01-02 at 14:12 -0500, Terry Polzin wrote: > > Any NFS or CIFS mounts active? > > > > Yes, but it doesn't make any difference even if I manually umount the > nfs shares before trying to do a software update. > > > > On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner > > > > wrote: > > > > > Since some time back I can no longer do a software update using > > > Gnome > > > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum > > > update' > > > works fine. What happens is that when I hit the 'Restart & Update' > > > button the system is going down and there are some log messages > > > that > > > flicker by really quickly. Then at bootup after unlocking the disk > > > there are again some log messages that flicker by quickly. What I > > > managed to see from the messages is the the phrase 'Device or > > > resource > > > busy'. After that the system reboots and comes up normally but > > > without > > > any software updates applied. > > > > > > I'll attach the end of journald when the system is going down first > > > time. There are some error, but I don't know what to make of > > > them... > > > > > > My biggest concern is not really about software update, as yum > > > update > > > works fine, but about doing a fedup to Fedora 27 at some point. > > > That > > > would probably not work? > > > > > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev- > > > disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 > > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > > terminal=? > > > res=success' > > > systemd[1]: Stopped File System Check on /dev/disk/by- > > > uuid/d1a72941- > > > eb0a-4d82-96ae-f837c572b875. > > > systemd[1]: Removed slice system-systemd\x2dfsck.slice. > > > systemd[1]: Stopped target Local File Systems (Pre). > > > systemd[1]: Stopped Create Static Device Nodes in /dev. > > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup- > > > dev > > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > > terminal=? > > > res=success' > > > systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. > > > using > > > dmeventd or progress polling... > > > systemd[1]: Stopped Remount Root and Kernel File Systems. > > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs > > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > > terminal=? > > > res=success' > > > lvm[1124]: 3 logical volume(s) in volume group "fedora" > > > unmonitored > > > systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. > > > using > > > dmeventd or progress polling. > > > audit[1]: SERVICE_STOP 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' > > > juno systemd[1]: Stopping LVM2 metadata daemon... > > > juno lvmetad[839]: Failed to accept connection errno 11. > > > systemd[1]: Stopped LVM2 metadata daemon. > > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > > subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad > > > comm="systemd" > > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > > res=success' > > > juno systemd-cryptsetup[1099]: Failed to deactivate: Device or > > > resource > > > busy > > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > > x2d9442\x2da7cd6a73b46c.service: Control process exited, > > > code=exited > > > status=1 > > > systemd[1]: Stopped Cryptography Setup for luks-862c1862-0497-442f- > > > 9442- > > > a7cd6a73b46c. > > > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 > > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@ > > > luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c > > > comm="systemd" > > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > > res=failed' > > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > > x2d9442\x2da7cd6a73b46c.service: Unit entered failed state. > > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > > x2d9442\x2da7cd6a73b46c.service: Failed with result 'exit-code'. > > > systemd[1]: Reached target Unmount All Filesystems. > > > systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. > > > kernel: kauditd_printk_skb: 102 callbacks suppressed > > > kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 > > > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > > > msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d94 > > > 42\x2da7cd6a73b46c > > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
Re: Device or resource busy when trying to do a software update
On Tue, 2018-01-02 at 14:12 -0500, Terry Polzin wrote: > Any NFS or CIFS mounts active? > Yes, but it doesn't make any difference even if I manually umount the nfs shares before trying to do a software update. > On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner > > wrote: > > > Since some time back I can no longer do a software update using > > Gnome > > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum > > update' > > works fine. What happens is that when I hit the 'Restart & Update' > > button the system is going down and there are some log messages > > that > > flicker by really quickly. Then at bootup after unlocking the disk > > there are again some log messages that flicker by quickly. What I > > managed to see from the messages is the the phrase 'Device or > > resource > > busy'. After that the system reboots and comes up normally but > > without > > any software updates applied. > > > > I'll attach the end of journald when the system is going down first > > time. There are some error, but I don't know what to make of > > them... > > > > My biggest concern is not really about software update, as yum > > update > > works fine, but about doing a fedup to Fedora 27 at some point. > > That > > would probably not work? > > > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev- > > disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? > > res=success' > > systemd[1]: Stopped File System Check on /dev/disk/by- > > uuid/d1a72941- > > eb0a-4d82-96ae-f837c572b875. > > systemd[1]: Removed slice system-systemd\x2dfsck.slice. > > systemd[1]: Stopped target Local File Systems (Pre). > > systemd[1]: Stopped Create Static Device Nodes in /dev. > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup- > > dev > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? > > res=success' > > systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. > > using > > dmeventd or progress polling... > > systemd[1]: Stopped Remount Root and Kernel File Systems. > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? > > res=success' > > lvm[1124]: 3 logical volume(s) in volume group "fedora" > > unmonitored > > systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. > > using > > dmeventd or progress polling. > > audit[1]: SERVICE_STOP 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' > > juno systemd[1]: Stopping LVM2 metadata daemon... > > juno lvmetad[839]: Failed to accept connection errno 11. > > systemd[1]: Stopped LVM2 metadata daemon. > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad > > comm="systemd" > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > res=success' > > juno systemd-cryptsetup[1099]: Failed to deactivate: Device or > > resource > > busy > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > x2d9442\x2da7cd6a73b46c.service: Control process exited, > > code=exited > > status=1 > > systemd[1]: Stopped Cryptography Setup for luks-862c1862-0497-442f- > > 9442- > > a7cd6a73b46c. > > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@ > > luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c > > comm="systemd" > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > res=failed' > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > x2d9442\x2da7cd6a73b46c.service: Unit entered failed state. > > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > > x2d9442\x2da7cd6a73b46c.service: Failed with result 'exit-code'. > > systemd[1]: Reached target Unmount All Filesystems. > > systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. > > kernel: kauditd_printk_skb: 102 callbacks suppressed > > kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 > > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > > msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d94 > > 42\x2da7cd6a73b46c > > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? > > res=failed' > > systemd[1]: Reached target Shutdown. > > systemd[1]: Reached target Final Step. > > systemd[1]: Starting Reboot... > > systemd[1]: Shutting down. > > systemd[1]: Hardware watchdog 'iTCO_wdt', version 0 > > systemd[1]: Set hardware watchdog to
Re: Device or resource busy when trying to do a software update
Any NFS or CIFS mounts active? On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner wrote: > Since some time back I can no longer do a software update using Gnome > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum update' > works fine. What happens is that when I hit the 'Restart & Update' > button the system is going down and there are some log messages that > flicker by really quickly. Then at bootup after unlocking the disk > there are again some log messages that flicker by quickly. What I > managed to see from the messages is the the phrase 'Device or resource > busy'. After that the system reboots and comes up normally but without > any software updates applied. > > I'll attach the end of journald when the system is going down first > time. There are some error, but I don't know what to make of them... > > My biggest concern is not really about software update, as yum update > works fine, but about doing a fedup to Fedora 27 at some point. That > would probably not work? > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev- > disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d1a72941- > eb0a-4d82-96ae-f837c572b875. > systemd[1]: Removed slice system-systemd\x2dfsck.slice. > systemd[1]: Stopped target Local File Systems (Pre). > systemd[1]: Stopped Create Static Device Nodes in /dev. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using > dmeventd or progress polling... > systemd[1]: Stopped Remount Root and Kernel File Systems. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > lvm[1124]: 3 logical volume(s) in volume group "fedora" unmonitored > systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using > dmeventd or progress polling. > audit[1]: SERVICE_STOP 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' > juno systemd[1]: Stopping LVM2 metadata daemon... > juno lvmetad[839]: Failed to accept connection errno 11. > systemd[1]: Stopped LVM2 metadata daemon. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > juno systemd-cryptsetup[1099]: Failed to deactivate: Device or resource > busy > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > x2d9442\x2da7cd6a73b46c.service: Control process exited, code=exited > status=1 > systemd[1]: Stopped Cryptography Setup for luks-862c1862-0497-442f-9442- > a7cd6a73b46c. > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@ > luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > x2d9442\x2da7cd6a73b46c.service: Unit entered failed state. > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\ > x2d9442\x2da7cd6a73b46c.service: Failed with result 'exit-code'. > systemd[1]: Reached target Unmount All Filesystems. > systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. > kernel: kauditd_printk_skb: 102 callbacks suppressed > kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=failed' > systemd[1]: Reached target Shutdown. > systemd[1]: Reached target Final Step. > systemd[1]: Starting Reboot... > systemd[1]: Shutting down. > systemd[1]: Hardware watchdog 'iTCO_wdt', version 0 > systemd[1]: Set hardware watchdog to 10min. > kernel: watchdog: watchdog0: watchdog did not stop! > systemd-shutdown[1]: Sending SIGTERM to remaining processes... > systemd-journald[821]: Journal stopped > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send a
Device or resource busy when trying to do a software update
Since some time back I can no longer do a software update using Gnome Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum update' works fine. What happens is that when I hit the 'Restart & Update' button the system is going down and there are some log messages that flicker by really quickly. Then at bootup after unlocking the disk there are again some log messages that flicker by quickly. What I managed to see from the messages is the the phrase 'Device or resource busy'. After that the system reboots and comes up normally but without any software updates applied. I'll attach the end of journald when the system is going down first time. There are some error, but I don't know what to make of them... My biggest concern is not really about software update, as yum update works fine, but about doing a fedup to Fedora 27 at some point. That would probably not work? audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d1a72941-eb0a-4d82-96ae-f837c572b875. systemd[1]: Removed slice system-systemd\x2dfsck.slice. systemd[1]: Stopped target Local File Systems (Pre). systemd[1]: Stopped Create Static Device Nodes in /dev. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... systemd[1]: Stopped Remount Root and Kernel File Systems. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' lvm[1124]: 3 logical volume(s) in volume group "fedora" unmonitored systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. audit[1]: SERVICE_STOP 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' juno systemd[1]: Stopping LVM2 metadata daemon... juno lvmetad[839]: Failed to accept connection errno 11. systemd[1]: Stopped LVM2 metadata daemon. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' juno systemd-cryptsetup[1099]: Failed to deactivate: Device or resource busy systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Control process exited, code=exited status=1 systemd[1]: Stopped Cryptography Setup for luks-862c1862-0497-442f-9442-a7cd6a73b46c. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Unit entered failed state. systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Failed with result 'exit-code'. systemd[1]: Reached target Unmount All Filesystems. systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. kernel: kauditd_printk_skb: 102 callbacks suppressed kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: Reached target Shutdown. systemd[1]: Reached target Final Step. systemd[1]: Starting Reboot... systemd[1]: Shutting down. systemd[1]: Hardware watchdog 'iTCO_wdt', version 0 systemd[1]: Set hardware watchdog to 10min. kernel: watchdog: watchdog0: watchdog did not stop! systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[821]: Journal stopped ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
USB Broadband mobile
Hello, When I try to add a connection, I get No plugin supported adding this connection (by using Network Manager) nmcli dev DEVICE TYPE STATE CONNECTION virbr0 bridgeconnected virbr0 ttyUSB4 gsm disconnected -- mmcli -m 0 /org/freedesktop/ModemManager1/Modem/0 (device id '4e4f258144d47542008fa77aaf6bd481f2ca0f09') - Hardware | manufacturer: 'TCT Mobile International Limited' | model: 'HSPA+ Data Card' | revision: 'GX120K00XX' | supported: 'gsm-umts' |current: 'gsm-umts' | equipment id: '356698042474859' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-4' |drivers: 'option1' | plugin: 'X22X' | primary port: 'ttyUSB4' | ports: 'ttyUSB3 (at), ttyUSB4 (at)' - Numbers | own : 'unknown' - Status | lock: 'ph-net-puk' | unlock retries: 'unknown' | state: 'locked' |power state: 'on' |access tech: 'unknown' | signal quality: '0' (cached) - Modes| supported: 'allowed: any; preferred: none' |current: 'allowed: any; preferred: none' - Bands| supported: 'unknown' |current: 'unknown' - IP | supported: 'none' - SIM | path: '/org/freedesktop/ModemManager1/SIM/0' - Bearers | paths: 'none' mmcli -m 0 --simple-connect="pin=6837,apn=3G" error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NetworkPuk: Device is locked: 'ph-net-puk'' Any idea? Thank === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: XPS 13 (9360)
Yes, indeed, this is the so-called developer edition and tends to run about $100 cheaper than the one with the Windows tax. I got that four years ago and stripped off the Ubuntu and off we went. I am still pleased with this purchase (in June 2013). Ranjan On Tue, 2 Jan 2018 10:04:24 -0500 Tom H wrote: > On Tue, Jan 2, 2018 at 9:00 AM, Danishka Navin wrote: > > > > Does anyone use Fedora on XPS 13 (9360) [1] ? > > http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc=w51785746sgw10&model_id=xps-13-9360-laptop > > > > I wonder if device drivers available for this model. > > Dell sells an XPS 13 with Ubuntu pre-installed [1] so you'd be better > off buying one of those models if they exist in Singapore (you might > need to enable rpm fusion for non-free stuff). > > [1] > http://www.dell.com/en-us/work/shop/sfc/sf/xps-laptops?~ck=mn&appliedRefinements=7692 > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: XPS 13 (9360)
I have been running Fedora since Fedora 19-20 on my trusty XPS13. Have been doing so for the past four and a half years, in fact this e-mail is written on that machine running F27. No problems at all. Same story for two of my students who bought their laptops two years ago upon seeing my positive experience (getting rid of their over-priced, useless and deceptive Macbook Airs in the process). HTH! Ranjan On Tue, 2 Jan 2018 07:59:55 -0700 InvalidPath wrote: > I use it on an Xps 15 9550... if that helps. Works 100% > > On Jan 2, 2018 7:01 AM, "Danishka Navin" wrote: > > Hi there, > > Does anyone use Fedora on XPS 13 (9360) [1] ? > http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc= > w51785746sgw10&model_id=xps-13-9360-laptop > > I wonder if device drivers available for this model. > > Regards, > -- > 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 -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: XPS 13 (9360)
On Tue, Jan 2, 2018 at 9:00 AM, Danishka Navin wrote: > > Does anyone use Fedora on XPS 13 (9360) [1] ? > http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc=w51785746sgw10&model_id=xps-13-9360-laptop > > I wonder if device drivers available for this model. Dell sells an XPS 13 with Ubuntu pre-installed [1] so you'd be better off buying one of those models if they exist in Singapore (you might need to enable rpm fusion for non-free stuff). [1] http://www.dell.com/en-us/work/shop/sfc/sf/xps-laptops?~ck=mn&appliedRefinements=7692 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: XPS 13 (9360)
I use it on an Xps 15 9550... if that helps. Works 100% On Jan 2, 2018 7:01 AM, "Danishka Navin" wrote: Hi there, Does anyone use Fedora on XPS 13 (9360) [1] ? http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc= w51785746sgw10&model_id=xps-13-9360-laptop I wonder if device drivers available for this model. Regards, -- 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 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not just rpcbind, but man db update as well
On Mon, Jan 1, 2018 at 9:42 AM, Patrick O'Callaghan wrote: > On Mon, 2018-01-01 at 09:19 -0500, Tom H wrote: >> >> rpcbind should not enable itself: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1087951 > > Thanks, I added a comment to the BZ report and disabled > rpcbind.service, however it's also necessary to disable and stop > rpcbind.socket. Does Fedora's packaging policy allow a package to disable units on upgrade? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: autofs error : setautomntent: lookup(sss): setautomntent: No such file or directory
Allegedly, on or about 2 January 2018, Angelo Moreschini sent: > I am trying with autofs, I'll preface my reply by saying although I use autofs, I use it for automatic mounting of NFS shares. In my case, my routine for getting autofs to work is to: 0. su - 1. dnf install autofs 2. mkdir /net (this is the path I'll access my NFS servers through) 3. systemctl enable autofs 4. systemctl start autofs I make no alterations to the autofs configuration files. And, as far as I recall, that went off without any error messages. So, my guess would be that you've asked it to do something, but there's a step missing, or syntax error, in your configuration. My first suggestion would be to revert your config files to the original condition, and see if autofs starts up without any error notices. Then do one modification at a time. > but I get this error when I check the status of the service: > > "setautomntent: lookup(sss): setautomntent: No such file or > directory" > the full output is: > > [angelo_dev@localhost ~]$ sudo systemctl status autofs > ● autofs.service - Automounts filesystems on demand >Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled) >Active: active (running) since Tue 2018-01-02 08:28:29 IST; 7min ago > Process: 5722 ExecStart=/usr/sbin/automount $OPTIONS --pid-file > /run/autofs.pid (code=exited, status=0/SUCCESS) > Main PID: 5724 (automount) >CGroup: /system.slice/autofs.service >└─5724 /usr/sbin/automount --pid-file /run/autofs.pid > > Jan 02 08:28:29 localhost.pluto automount[5724]: setautomntent: lookup(sss): > setautomntent: No such file or directory > > > I also cannot enter (with command) the directories located on a > USB HD that I try to mount automatically. > > > > To configure autofs I made this : > > I added this line to the file /etc/auto.master (that was created at > installation of autofs) : > /-/etc/auto.misc > > and these lines to file /etc/auto.misc : > /media/BKx_programmingntfs PRTZ_programming > /media/BKx_data-commonntfs PRTZ_data-common This (above) may be a problem. The /media directory is used by an automounting system in some desktops, without autofs. You could be clashing with it. And I don't see entries with that syntax in my default /etc/auto.misc and /etc/auto.master files. Usually, when you plug in something like a USB drive, it'll appear as a directory in /media, by itself, in the manner of: /media/ You don't need autofs for that. And it can handle a few different filing systems automatically, though there are probably some prerequisites. For sensible /media auto-mounting, perhaps even successful auto- mounting, the partitions need to have volume names. And giving everything unique volume names certainly helps. It may be necessary that the partition types match the filesystem (e.g. you can create an ext3 partition, but then format it as fat; your partition type just set a default filesystem to use, it doesn't exclude other types), but I suspect this isn't needed. > I also created the partitions > PRTZ_programming , PRTZ_data-common on the USB HD that I try to > mount > and the mounting points : > /media/BKx_data-common > /media/BKx_programming That ought to simply work without autofs (it does here). Try leaving autofs disabled, do not create any folders inside /media, and see what happens when you connect your drive. They should pop-up as folders within /media, using their own partition names. I do this all the time with USB drives, or camera memory cards, formatted with EXT3, FAT, FAT32, & NTFS. But you haven't said what desktop, if any, you are using. If this is a server with nobody logged into it, what worked for me, may not in that circumstance. My success with the /media directory has been using Gnome or Mate desktops. -- [tim@localhost ~]$ uname -rsvp Linux 4.13.16-202.fc26.x86_64 #1 SMP Thu Nov 30 15:39:32 UTC 2017 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: XPS 13 (9360)
no, I would like to go for this model if fedora support. On Tue, Jan 2, 2018 at 7:57 PM, Terry Polzin wrote: > If you already own this device, try a live CD > > On Tue, Jan 2, 2018 at 9:00 AM, Danishka Navin wrote: > >> Hi there, >> >> Does anyone use Fedora on XPS 13 (9360) [1] ? >> http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc=w51785746s >> gw10&model_id=xps-13-9360-laptop >> >> I wonder if device drivers available for this model. >> >> Regards, >> -- >> 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 >> >> > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > > -- 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
Re: XPS 13 (9360)
If you already own this device, try a live CD On Tue, Jan 2, 2018 at 9:00 AM, Danishka Navin wrote: > Hi there, > > Does anyone use Fedora on XPS 13 (9360) [1] ? > http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc= > w51785746sgw10&model_id=xps-13-9360-laptop > > I wonder if device drivers available for this model. > > Regards, > -- > 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 > > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
XPS 13 (9360)
Hi there, Does anyone use Fedora on XPS 13 (9360) [1] ? http://www.dell.com/sg/p/xps-13-9360-laptop/pd?oc=w51785746sgw10&model_id=xps-13-9360-laptop I wonder if device drivers available for this model. Regards, -- 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
Re: fc26 immediate kernel panic on reboot to 4.14.5-200 - subject updated
On 18/12/17 14:34, John Pilkington wrote: On 18/12/17 10:20, John Pilkington wrote: On 16/12/17 18:10, John Pilkington wrote: On 13/12/17 11:57, John Pilkington wrote: software-updates just upgraded 82 packages. On reboot, immediate kernel panic. 4.13.16-202 is running ok. yumex-dnf shows two instances of the new kernel packages ?? nvidia 387.22 ... 4.14.5-200.fc26 panics too for me. A quick search didn't find other posts like this. It happens very early and I don't know if anything is captured on disk. On screen the most reader-friendly line is: RIP: acpi_ex_system_memory_space_handler and acpi warnings have flashed up with earlier kernels. HP core2duo box, 4GB memory, with a history of several Fedora version upgrades. What else should I report? John P A search for the RIP line gives https://bugzilla.redhat.com/show_bug.cgi?id=1520265 from 2017-12-04 Also HP BIOS 786F2, mine is an earlier version, 1.04 1/31/2008 A BIOS update to v01.60 seems to have fixed this. Details in the BZ. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Not just rpcbind, but man db update as well
Sam Varshavchik: >> I'm sure that folks running on a UPS would appreciate a system >> shutdown triggered by a power failure, by a low power alert from >> the UPS, now having to wait until the man page cache gets updated. Tom Horsley: > Or someone trying to shutdown their laptop to board a plane :-). Or simply wanting to shutdown the computer and leave the house in a hurry. I detest things which *STUPIDLY* prolong start-up and shut-down times. Things like man or locate database updating can be done in the background when the system is running, and should be quickly and cleanly interruptible (whether that be an abort, or making use of some kind of resuming bookmark). -- [tim@localhost ~]$ uname -rsvp Linux 4.13.16-202.fc26.x86_64 #1 SMP Thu Nov 30 15:39:32 UTC 2017 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. Evolution keeps on telling me that it's refreshing, but I still want to go and get a drink. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Fwd: Re: multi-head config question
Tony Nelson: >> Fiddle with the screen's DPI setting. François Patte: > I don't understand what you mean: is it possible to change a screen > resolution localy? It changes the scaling of the rendering done by the graphics engine, and affects anything that would render to an absolute size. In other words, if you do any computer aided design, and want something generated on screen at a specific size (such as graphics measured in mm or inches, fonts at point sizes, page renderings at 100% actual size, etc), you can't do it any more. They'll be incorrectly sized. What you (and many others) really need is a GUI where the GUI size (icons, windows, etc) are user-adjustable in the same manner as you can customise fonts. I don't know if Fedora has one. Fortunately, for me, whoever set up the GUI size seems to have to picked one that is usable with the usual screen resolutions my monitors support, excepting the annoyance of trying to find the invisible tiny amount of space used to resize windows. But for those with low or very high resolution screens, not so lucky. -- [tim@localhost ~]$ uname -rsvp Linux 4.13.16-202.fc26.x86_64 #1 SMP Thu Nov 30 15:39:32 UTC 2017 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. Television should really come with an intelligence knob. I've tried adjusting the brightness, but it didn't help. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
