Re: I think I broke my BTRFS RAID 1 array

2021-04-14 Thread Richard Shaw
I ran btrfs check without --repair but apparently it fixed some issues and now the rebalance is continuing without exiting... # btrfs check /dev/sdc Opening filesystem to check... Checking filesystem on /dev/sdc UUID: d9a2a011-77a2-43be-acd1-c9093d32125b [1/7] checking root items [2/7] checking ex

Re: puzzling SELinux alert.

2021-04-14 Thread Ed Greshko
On 15/04/2021 05:57, home user wrote: Is your desktop "GNOME" or "GNOME on Xorg"? The desktop menu at login has 4 GNOME entries: GNOME GNOME GNOME Classic GNOME on Xorg I usually use the first GNOME. Side question: What's the difference between the first two entries? I don't know why you'd

Re: puzzling SELinux alert.

2021-04-14 Thread home user
On 4/14/21 3:46 PM, Roger Heflin wrote: really just start caja from the terminal with strace -o caja.out -f `which caja` do what you normally do and exit. then grep pid caja.out and that will should tell you what executable that pid was and some of what it did. That will produce an .out file t

Re: puzzling SELinux alert.

2021-04-14 Thread home user
On 4/14/21 3:18 PM, Ed Greshko wrote: Is your desktop "GNOME" or "GNOME on Xorg"? The desktop menu at login has 4 GNOME entries: GNOME GNOME GNOME Classic GNOME on Xorg I usually use the first GNOME. Side question: What's the difference between the first two entries? Which ever one it is, cou

Re: puzzling SELinux alert.

2021-04-14 Thread Roger Heflin
really just start caja from the terminal with strace -o caja.out -f `which caja` do what you normally do and exit. then grep pid caja.out and that will should tell you what executable that pid was and some of what it did. That will produce an .out file that contains all of the pid's and what tho

Re: puzzling SELinux alert.

2021-04-14 Thread Ed Greshko
On 15/04/2021 05:06, home user wrote: On 4/14/21 12:52 PM, Ed Greshko wrote: On 15/04/2021 00:33, home user wrote: I tried that using "ps -ef | grep [pid]".  The only hit was the ps command  itself. It is not clear to me that you did this immediately after getting the alert. 1. I launched c

Re: puzzling SELinux alert.

2021-04-14 Thread home user
On 4/14/21 1:50 PM, Roger Heflin wrote: He might want to run a strace -o appname.out -f And then do the ausearch and we should be able to see what what the pid was doing and/or what executable it was. What options would you find most helpful? ___ us

Re: puzzling SELinux alert.

2021-04-14 Thread home user
On 4/14/21 12:52 PM, Ed Greshko wrote: On 15/04/2021 00:33, home user wrote: I tried that using "ps -ef | grep [pid]".  The only hit was the ps command itself. It is not clear to me that you did this immediately after getting the alert. 1. I launched caja from the gnome activities dash. Th

Re: puzzling SELinux alert.

2021-04-14 Thread Roger Heflin
He might want to run a strace -o appname.out -f And then do the ausearch and we should be able to see what what the pid was doing and/or what executable it was. On Wed, Apr 14, 2021 at 1:52 PM Ed Greshko wrote: > > On 15/04/2021 00:33, home user wrote: > > I tried that using "ps -ef | grep [pid

Re: puzzling SELinux alert.

2021-04-14 Thread Ed Greshko
On 15/04/2021 00:33, home user wrote: I tried that using "ps -ef | grep [pid]".  The only hit was the ps command  itself. It is not clear to me that you did this immediately after getting the alert. According to the ausearch_out the PID is different at each instance of an alert.  So, it is po

Re: puzzling SELinux alert.

2021-04-14 Thread home user
On 4/14/21 1:26 AM, Ed Greshko wrote: On 14/04/2021 11:41, home user wrote: Last night, in ".bash_profile", I commented out the block of code that launches xeyes, and shut down for the night. This morning, I booted up and logged in, No xeyes. I downloaded a Chinese music video. I then la

Re: How to kickstart a workstation installation?

2021-04-14 Thread Thomas Cameron
On 4/14/21 10:53 AM, Matthew Miller wrote: On Wed, Apr 14, 2021 at 10:33:27AM -0500, Thomas Cameron wrote: I used the F33 Everything DVD image and got closer, but I still don't see a way to use it to kickstart a VM or a desktop. What problems are you having here? I think simply putting @^work

Re: How to kickstart a workstation installation?

2021-04-14 Thread Matthew Miller
On Wed, Apr 14, 2021 at 10:33:27AM -0500, Thomas Cameron wrote: > I used the F33 Everything DVD image and got closer, but I still > don't see a way to use it to kickstart a VM or a desktop. What problems are you having here? I think simply putting @^workstation-product-environment in the %packag

Re: How to kickstart a workstation installation?

2021-04-14 Thread James Szinger
On Wed, 14 Apr 2021 10:33:27 -0500 Thomas Cameron wrote: > > How the heck do I kickstart a workstation? Preferably from the > F33-Everything DVD image so I can set up Xfce. Check out the --kickstart option to livecd-iso-to-disk. The last tiem I did this I used a command like: livecd-iso-t

Re: How to kickstart a workstation installation?

2021-04-14 Thread Qiyu Yan
在 2021-04-14星期三的 10:33 -0500,Thomas Cameron写道: > Right now, if I want a workstation, I use the bootable workstation > image > on a USB thumb drive and choose to install the workstation image to my > hard drive. Then I have to go back afterwards and run a bunch of yum > groupinstall commands to g

Re: I think I broke my BTRFS RAID 1 array

2021-04-14 Thread Qiyu Yan
在 2021-04-14星期三的 06:32 -0500,Richard Shaw写道: > I have been running a 3 disk RAID 1 btrfs array for a few weeks now and > simulated more than a dozen power failures without issue. Yesterday I > decided to add my 4th disk, which was the original media drive. > > I was able to add it to the array eas

How to kickstart a workstation installation?

2021-04-14 Thread Thomas Cameron
Right now, if I want a workstation, I use the bootable workstation image on a USB thumb drive and choose to install the workstation image to my hard drive. Then I have to go back afterwards and run a bunch of yum groupinstall commands to get my machine where I want it. Not ideal for multiple in

Re: F33 -> F34 upgrade resulted in unbootable system

2021-04-14 Thread Ed Greshko
On 14/04/2021 20:30, Jeb Wilkins wrote: Thanks, reposted to test@ Yes, I saw.  I hope the solution given works for you. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To uns

Re: F33 -> F34 upgrade resulted in unbootable system

2021-04-14 Thread Jeb Wilkins
Thanks, reposted to test@ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: h

Re: F33 -> F34 upgrade resulted in unbootable system

2021-04-14 Thread Ed Greshko
On 14/04/2021 19:53, Jeb Wilkins wrote: I thought I'd test the F34 upgrade to look for bugs but its resulted in an non-booting laptop. I've a fairly stock Fedora install on a Dell XPS 13 developer edition. The latop was originally an ubuntu install, its got LVM on top of LUKS created by ubunt

Re: F33 -> F34 upgrade resulted in unbootable system

2021-04-14 Thread Jeb Wilkins
I should have mentioned this was originally installed as F32 and is using Ext4 for root and /home ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https:/

F33 -> F34 upgrade resulted in unbootable system

2021-04-14 Thread Jeb Wilkins
I thought I'd test the F34 upgrade to look for bugs but its resulted in an non-booting laptop. I've a fairly stock Fedora install on a Dell XPS 13 developer edition. The latop was originally an ubuntu install, its got LVM on top of LUKS created by ubuntu, Fedora partitions were later added insi

I think I broke my BTRFS RAID 1 array

2021-04-14 Thread Richard Shaw
I have been running a 3 disk RAID 1 btrfs array for a few weeks now and simulated more than a dozen power failures without issue. Yesterday I decided to add my 4th disk, which was the original media drive. I was able to add it to the array easy enough and then initiated a full balance, however, wh

Re: puzzling SELinux alert.

2021-04-14 Thread Ed Greshko
On 14/04/2021 11:41, home user wrote: Tomorrow morning, I will try the no-xeyes test that you suggest. Ignoring the problem is tempting, but I don't want to give up too easily. Well, pardon me for saying I find that last observation somewhat narrow in scope.  :-) :-) That being said