stop
by dcooke@efn.org
> Send users mailing list submissions to
> users(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> users-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> users-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of users digest..."
>
> Today's Topics:
>
> 1. Re: Samba config - (Bob Goodwin)
> 2. Re: Output text color (was dnf list color bad) (Todd Zullinger)
> 3. Re: Samba config - (Ed Greshko)
> 4. Re: setting up PPPoE on fedora with recent network tools
> (Patrick Mansfield)
> 5. Re: Output text color (was dnf list color bad) (Beartooth)
>
>
> ----------------------------------------------------------------------
>
> Date: Sun, 5 Jul 2020 12:46:52 -0400
> From: Bob Goodwin <bobgoodwin(a)fastmail.us>
> Subject: Re: Samba config -
> To: users(a)lists.fedoraproject.org
> Message-ID: <16d9a7a5-ba27-5769-a694-fffffed28d72(a)fastmail.us>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>
> On 2020-07-05 10:48, Ed Greshko wrote:
>>> Check the settings on 192.168.50.149
>> Also, what do you get when you do....
>>
>> smbclient -L 192.168.50.149 -U bobg
>>
>> You will be prompted for your smb password on the remote system.
> .
>> [bobg@WS1 ~]$ smbclient -L 192.168.50.149 -U bobg
>> Enter SAMBA\bobg's password:
>>
>>    Sharename      Type     Comment
>> Â Â Â ---------Â Â Â Â Â Â ----Â Â Â Â Â -------
>>    print$         Disk     Printer Drivers
>> Â Â Â IPC$Â Â Â Â Â Â Â Â Â Â Â IPCÂ Â Â Â Â Â IPC Service (Samba
>> 4.12.3)
>>    bobg           Disk     Home Directories
>> SMB1 disabled -- no workgroup available
>
> Not sure what it wants from SMB1 or why whatever it is is disabled? I
> probably need to enter something for that but do not have any Windows to
> deal with here ...
>
> --
> Bob Goodwin - Zuni, Virginia, USA
> http://www.qrz.com/db/W2BOD
> FEDORA-32/64bit LINUX XFCE Fastmail POP3
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 12:59:10 -0400
> From: Todd Zullinger <tmz(a)pobox.com>
> Subject: Re: Output text color (was dnf list color bad)
> To: users(a)lists.fedoraproject.org
> Message-ID: <20200705165910.GN6611(a)pobox.com>
> Content-Type: multipart/signed; micalg=pgp-sha256;
> protocol="application/pgp-signature"; boundary="Z58pRedRDwOEwTeD"
>
>
> --Z58pRedRDwOEwTeD
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Beartooth wrote:
>> On Fri, 03 Jul 2020 12:02:40 -0700, Samuel Sieb wrote:
>>> On 7/3/20 11:59 AM, Beartooth wrote:
>>>> That one is the color dnf upgrade uses to list what it proposes to
>>>> change. (What it reports while making the changes is fine.) At present
>>>> it shows bright chartreuse on pale blue -- which just fuzzes out.
>>>=20
>>> If the only problem is the one color from dnf, then either disable dnf
>>> colors or use the information from the last thread to adjust the color
>>> that's causing the problem.
>>=20
>> I found /etc/dnf/DIR_COLORS, /etc/dnf/DIR_COLORS.256color, and=20
>> /etc/dnf/DIR_COLORS.lightbgcolor.
>
> I'm pretty sure those are in /etc, not /etc/dnf. If they're
> in the latter, can you confirm that and check what package
> provides them (rpm -qf /etc/dnf/DIR_COLORS*)? I don't see
> anything providing them.
>
>> In the first one, I found among much else=20
>> # If you use DOS-style suffixes, you may want to uncomment the
>> following:
>> #.cmd 01;32 # executables (bright green) I changed 32 to 31; removed=20
>> both hashmarks; no joy; rebooted; still no joy.
>>=20
>> Am I editing the wrong file? That comment about suffixes doesn't=20
>> quite sit right, but I didn't see anything else that looked likelier.
>
> Assuming you really meant /etc/DIR_COLORS*, then to be
> clear, 1) that will affect ls rather than dnf; and 2) you
> _are_ most likely editing the wrong file if you edit
> /etc/DIR_COLORS.
>
> The logic for which of the 3 files is used is in
> /etc/profile.d/colorls.sh (for bourne-style shells like
> bash). Most modern terminal support 256 colors (at least),
> so they'll most likely use /etc/DIR_COLORS.256color.
>
> After you edit it, you must source /etc/profile.d/colorls.sh
> to pick up the changes.
>
> You can also copy the proper DIR_COLORS* file to your home
> dir to avoid having a clean install overwrite your changes
> in /etc. The paths which the colorls.sh script uses are:
>
> $HOME/.dir_colors.$TERM
> $HOME/.dircolors.$TERM
> $HOME/.dir_colors
> $HOME/.dircolors
>
> The first one found is used.
>
> --=20
> Todd
>
> --Z58pRedRDwOEwTeD
> Content-Type: application/pgp-signature; name="signature.asc"
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iQFEBAEBCAAuBQJfAgbeJxhodHRwczovL3d3dy5wb2JveC5jb20vfnRtei9wZ3Av
> dG16LmFzYwAKCRBDJZOLvq8M495uCAC1ibv9QCPF4jp2BcTrefdlhhYzv8uwftLl
> LYoPtnPBjND/BoPnQnWmR7fGEQIeS7wvxwsFJWZolbJ4sj0PEXRD6/P9liUn2fu1
> zrbFAPwX7mkVE0ek52iw9oGYclycrrRerJSx7SgGAoYnWy+thMtgvG0d04nDXg6A
> yqRtDykVmIBXGcvmH/WzGQCDroRihvIxrcEBmSnHLbWcpB+TYR2sEw485wRxaKjE
> zyeMv2ly5+LFzu+0+tbw1qXLUv8Y18SYnF+t/u9ypGvVqwosLXCKQGJcULiHyP/3
> nDBZ2NSibiSVscMeh7RS/sgFiaOrCSF4YgbYVZMcn55haUwhboWl
> =ZoDG
> -----END PGP SIGNATURE-----
>
> --Z58pRedRDwOEwTeD--
>
> ------------------------------
>
> Date: Mon, 6 Jul 2020 01:02:17 +0800
> From: Ed Greshko <ed.greshko(a)greshko.com>
> Subject: Re: Samba config -
> To: users(a)lists.fedoraproject.org
> Message-ID: <05252b8e-2848-4fac-67b2-72503fd79219(a)greshko.com>
> Content-Type: text/plain; charset=utf-8
>
> On 2020-07-06 00:46, Bob Goodwin wrote:
>>
>>
>> On 2020-07-05 10:48, Ed Greshko wrote:
>>>> Check the settings on 192.168.50.149
>>> Also, what do you get when you do....
>>>
>>> smbclient -L 192.168.50.149 -U bobg
>>>
>>> You will be prompted for your smb password on the remote system.
>> .
>>> [bobg@WS1 ~]$ smbclient -L 192.168.50.149 -U bobg
>>> Enter SAMBA\bobg's password:
>>>
>>>    Sharename      Type     Comment
>>> Â Â Â ---------Â Â Â Â Â Â ----Â Â Â Â Â -------
>>>    print$         Disk     Printer Drivers
>>> Â Â Â IPC$Â Â Â Â Â Â Â Â Â Â Â IPCÂ Â Â Â Â Â IPC Service (Samba
>>> 4.12.3)
>>>    bobg           Disk     Home Directories
>>> SMB1 disabled -- no workgroup available
>>
>> Not sure what it wants from SMB1 or why whatever it is is disabled? I
>> probably need to enter something for that but do not have any Windows to
>> deal with here ...
>>
>
> That's not important.
>
> What is is Sharename=bobg.
>
> So, on WS1 the command would be....
>
> mount -o uid=bobg,credentials=/home/bobg/cred //192.168.50.149/bobg
> /media/smb
>
> And back to sleep I go.....
>
> --
> The key to getting good answers is to ask good questions.
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 10:29:02 -0700
> From: Patrick Mansfield <patmans(a)yahoo.com>
> Subject: Re: setting up PPPoE on fedora with recent network tools
> To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> Message-ID: <20200705172902.GA1121049@umbrella>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Sat, Jul 04, 2020 at 10:19:32AM +0800, Ed Greshko wrote:
>> On 2020-07-04 04:19, Patrick Mansfield via users wrote:
>> > Anyone know where to find details setting up and using a PPPoE client
>> on fedora with
>> > current network tools?
>> >
>> > I used nm-connection-editor to add one, but haven't figured out how to
>> actually bring
>> > it up nor if it's actually working.
>> >
>> > I installed rp-pppoe, I'm not sure if it's needed or if it's
>> integrated with NM.
>>
>> Well, if you've set it up then you should be able see it in the list
>> when you issue
>>
>> nmcli connection
>>
>> The details will be shown if you do...
>>
>> nmcli connection show name-of-connection
>>
>> And then....
>>
>> nmcli connection up
>>
>> will attempt to bring up the connection.� The results should be
>> displayed and you can check the
>> journal for any error messages.
>
> Ah, thanks: I had tried to bring it up using nmcli, but missed this error:
>
> Jul 04 10:53:23 umbrella NetworkManager[1183]: <warn> [1593885203.4348]
> device (wan0): PPPoE failed to start: the PPP plugin
> /usr/lib64/NetworkManager/1.20.12-1.fc31/libnm-ppp-plugin.so is not
> installed
>
> I installed it:
>
> dnf install NetworkManager-ppp
>
> And was able to get PPPoE working.
>
> I don't think rp-pppoe is needed, but have left it installed for now.
>
> PITA as I'm trying to get rid of my combined modem router (actiontech
> C3000A) with
> new Centurylink internet service, and I can't modify the modem settings
> once I put
> it in bridge mode - it has to be physically reset if I want to change
> anything, like
> put it back to PPPoE mode, or to disable the VLAN.
>
> -- Patrick
>
> ------------------------------
>
> Date: Sun, 5 Jul 2020 17:52:56 -0000 (UTC)
> From: Beartooth <Beartooth(a)comcast.net>
> Subject: Re: Output text color (was dnf list color bad)
> To: users(a)lists.fedoraproject.org
> Message-ID: <rdt41o$2i6$2(a)ciao.gmane.io>
> Content-Type: text/plain; charset=UTF-8
>
> On Sun, 05 Jul 2020 12:59:10 -0400, Todd Zullinger wrote:
> [....]
>> I'm pretty sure those are in /etc, not /etc/dnf. If they're in the
>> latter, can you confirm that and check what package provides them (rpm
>> -qf /etc/dnf/DIR_COLORS*)? I don't see anything providing them.
>
> You're right. My bad. They're in /etc. And I get # rpm -qf /etc/
> dnf/DIR_COLORS*
> error: file /etc/dnf/DIR_COLORS*: No such file or directory
>
>
>>> In the first one, I found among much else
>>> # If you use DOS-style suffixes, you may want to uncomment the
>>> following:
>>> #.cmd 01;32 # executables (bright green) I changed 32 to 31; removed
>>> both hashmarks; no joy; rebooted; still no joy.
>>>
>>> Am I editing the wrong file? That comment about suffixes doesn't
>>> quite sit right, but I didn't see anything else that looked likelier.
>>
>> Assuming you really meant /etc/DIR_COLORS*, then to be clear, 1) that
>> will affect ls rather than dnf; and 2) you _are_ most likely editing the
>> wrong file if you edit /etc/DIR_COLORS.
>>
>> The logic for which of the 3 files is used is in
>> /etc/profile.d/colorls.sh (for bourne-style shells like bash). Most
>> modern terminal support 256 colors (at least), so they'll most likely
>> use /etc/DIR_COLORS.256color.
>
> Am I remembering wrong? Istr that I could tell a given machine
> *once* that I want to see dot files, and it would *always* display them.
>
>> After you edit it, you must source /etc/profile.d/colorls.sh to pick up
>> the changes.
>
> "source" is a verb?? Sorry -- you lost me. What does it mean?
>
>> You can also copy the proper DIR_COLORS* file to your home dir to avoid
>> having a clean install overwrite your changes in /etc. The paths which
>> the colorls.sh script uses are:
>>
>> $HOME/.dir_colors.$TERM $HOME/.dircolors.$TERM $HOME/.dir_colors
>> $HOME/.dircolors
>>
>> The first one found is used.
>
> Sigh. The curse of the autodidact strikes again. I know that
> "HOME" in all upper case has a standard meaning, and I suppose "TERM"
> must, too. But I can never remember what it is, nor where to look it up.
>
> --
> Beartooth Staffwright, Not Quite Clueless Power User
> Remember I know little (precious little!) of where up is.
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
>
> ------------------------------
>
> End of users Digest, Vol 197, Issue 33
> **************************************
>
3 years, 9 months
Radeon 5700 XT: Wayland/X11 not using amdgpu
by Braden McDaniel
Searching a bit, it looks like some folks are having success with the Radeon 5700 (XT) and Fedora 32.
Not me. :-/
I first posted on ask.fedoraproject.org; and while I was able to drill down and get a bit more information, responses there seem to have tapered off.
A few data points:
> $ lspci -k | grep -EA3 'VGA|3D|Display'
> 09:00.0 **VGA** compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
> Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b36
> Kernel modules: amdgpu
> 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
While that checks out, for some reason amdgpu isn’t listed in the lsmod output:
> $ sudo lsmod | grep amd
> edac_mce_amd 32768 0
> kvm_amd 114688 0
> kvm 806912 1 kvm_amd
> ccp 102400 1 kvm_amd
> amd_iommu_v2 20480 0
> pinctrl_amd 32768 0
I don’t get Wayland when I log in; I get the X11 fallback. Looking at the Xorg log, it never even tries the amdgpu driver. It tries the radeon driver; and when that fails, I get the generic framebuffer fallback.
Any suggestions for next steps to take?
--
Braden McDaniel
<braden(a)endoframe.com>
3 years, 9 months
where does virsh-manage keep its settings?
by ToddAndMargo
Hi All,
I want to move virsh-manager from root to todd.
Where does virsh-manager keep its configuration
settings?
Not having much luck with "ls -a" and "find".
Many thanks,
-T
3 years, 9 months
Qt_5_PRIVATE_API?
by ToddAndMargo
Hi All,
Anyone know who provides the 64 bit version of
"libQt5Gui.so.5: Qt_5_PRIVATE_API"?
$ /opt/master-pdf-editor-5/masterpdfeditor5
/opt/master-pdf-editor-5/masterpdfeditor5: /lib64/libQt5Gui.so.5:
version `Qt_5_PRIVATE_API' not found (required by
/opt/master-pdf-editor-5/masterpdfeditor5)
# dnf whatprovides libQt5Gui.so.5
Last metadata expiration check: 1:31:22 ago on Sun 05 Jul 2020 01:15:43
PM PDT.
qt5-qtbase-gui-5.13.2-4.fc32.i686 : Qt5 GUI-related libraries
Repo : fedora
Matched from:
Provide : libQt5Gui.so.5
qt5-qtbase-gui-5.14.2-5.fc32.i686 : Qt5 GUI-related libraries
Repo : updates
Matched from:
Provide : libQt5Gui.so.5
But only the 385 version. I need the 64 bit version
Many thanks,
-T
3 years, 9 months
Samba config -
by Bob Goodwin
L am struggling with the configuration of the new server. Presently my
problem is that I attempted to create a link an made an error, I do not
understand perfectly what I have read!
[root@smb bobg]# ln -s /home/share /media/dd2
"# rm linkfile" is clear enough but,
[root@smb bobg]# ll /media/dd2
total 0
lrwxrwxrwx. 1 root root 11 Jun 29 17:25 share -> /home/share
Which one is the link name to be removed, what is the exact command to
do that and NOT DESTROY or damage the files in /media/dd2?
I could unplug the data cable on the drive while doing the removal but
even then Might there be something lurking to finish the removal when
restarted with the drive plugged in? I am confused and worried about
doing the removal correctly, some advice appreciated. Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
FEDORA-32/64bit LINUX XFCE Fastmail POP3
3 years, 9 months
Output text color (was dnf list color bad)
by Beartooth
Back on April 23, I started a thread on the color of dnf's output,
which petered out without reaching any conclusion. I let it age. Having
now gone back and re-examined the problem, I'd like to start over, and
maybe do better.
Part of the problem, and one of the things I failed to make clear,
is that I don't use pat colors. I began, long years ago, by setting
several different soft colors as backgrounds on different terminal tabs,
which were supposed to be easier on the eyes. Not seeing the colors I
wanted in the canned array, I invoked the GUI slider.
EXAMPLE: Editing a profile named bbi, I click on the color tab,
then on background. Up pops a box offering an array and also a button
with a + on it. Clicking that gets me a new box, with a vertical bar and
a square. The bar shows a spectrum; clicking anywhere on it colors the
square, and moving a dot around in the square determines both the shade
and the intensity of the background. Having done that, and accepted a
background color, I click on text, and go through the same process to get
a good contrast.
Until F32, this process worked like a charm. I can log into any of
my computers, go to any tab on the Mate terminal, and see at a glance who
and where I am.(Since my domain is hosted on a remote machine, the where
is not trivial.)
Until F32, when I entered a command on such a terminal tab, its
output came in the same color as what I had typed. Now it differs, and
that is fine. But the default is unreadable against my background.
Might we (pretty please!) get one more choice on the screen for
choosing colors? It could be labelled "output" and work just like text,
background, and (optionally) bold; or it could use the bold color by
default.
Am I making sense this time??
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
3 years, 9 months
setting up PPPoE on fedora with recent network tools
by Patrick Mansfield
Hi -
Anyone know where to find details setting up and using a PPPoE client on fedora with
current network tools?
I used nm-connection-editor to add one, but haven't figured out how to actually bring
it up nor if it's actually working.
I installed rp-pppoe, I'm not sure if it's needed or if it's integrated with NM.
-- Patrick
3 years, 9 months
newbie question about appimages
by David
I know zero about appimages.
Today, I downloaded the very latest development version of Chromium as an
appimage, and tried unsuccessfully to run it.
Is that feasible ?
My understanding is that if the app is marked executable, then you just
click
on run in the properties.
David Locklear
3 years, 9 months
Cinnamon 4.6 makes my display flickering
by Marco Guazzone
Hi,
I have just upgraded Cinnamon to the new 4.6 version with dnf and then
rebooted the system.
When I log in, Cinnamon makes my screen flickering, with half screen blue
and the other half screen showing (a half of) my background image.
Just for testing, I created a new user to start Cinnamon with a fresh new
configuration. Same problems experienced
If I use Gnome shell (Classic), then I log out, and then I use Cinnamon the
problem disappears, apparently.
Any idea?
Thanks for your help.
Marco
3 years, 9 months