FXAA Antialias Query With Nvida Devices
by Stephen Morris
Hi,
I use an Asus Geforce GTX 1070 nvidia card with 8 GB of memory. I
am also using the nvidia driver source from negativo17 for version
390.25. Within Nvidia X Server Configuration I have selected FXAA
Antialiasing within the opengl settings and that has caused an issue in
my F27 implementation. With that option active, the KDE kicker, active
applications in the taskbar and the system tray contents all get
displayed as white on white, and all applications, irrespective of
whether the application is a native KDE application or a GTK
application, text is displayed out of focus until either I mouse over
them (in some cases) or scroll the window in which case the text is
sharp and readable. If I unselect the FXAA option and set the Anti-alias
option to 16x I don't get the same issue.
Has anyone else experienced a similar issue and identified whether
its an issue with the driver or an issue with F27 routines, and whether
or not they have a resolution?
regards,
Steve
6 years, 1 month
change user id
by Ranjan Maitra
Hi,
I am on a single-account F27 system with an user id 1000. I want to change this user id. From what I understand, I should do the following:
sudo usermod -u 54321 <username>
However, when I do this, I get:
usermod: user <username> is currently used by process 866
I guess that this has to do with the fact that I am logged in (to do this). How do I get around this point? There is no root on the system but I do have sudo access.
Separately, I want all my files and directory owned by 1000 to move to this user id (so that I can have access)? Is this automatic or do I have to run chown -R <username> etc?
Many thanks and best wishes,
Ranjan
--
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.
6 years, 1 month
Replica issue
by kt@a-ng.eu
Hi,
I want to install replica server but I have errors.
Replica server:
System: CentOS Linux release 7.4.1708 (Core)
IPA: VERSION: 4.5.0, API_VERSION: 2.228
What I do:
ipa-client-install --mkhomedir
This process ran without a problem
Next
[root@auth02 ~]# ipa-replica-install
Password for admin(a)IDM.WAN:
Run connection check to master
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.
ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR Connection check failed!
See /var/log/ipareplica-conncheck.log for more information.
If the check results are not valid it can be skipped with --skip-conncheck parameter.
ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
In logs I see the problem is connection form master to replica server. This services are not install yet. Why ipa-replica-install checkt it? How to fix this problem?
2018-03-09T13:57:51Z DEBUG stderr=Check connection from replica to remote master 'auth01.idm.wan':
Directory Service: Unsecure port (389): OK
Directory Service: Secure port (636): OK
Kerberos KDC: TCP (88): OK
Kerberos Kpasswd: TCP (464): OK
HTTP Server: Unsecure port (80): OK
HTTP Server: Secure port (443): OK
The following list of ports use UDP protocoland would need to be
checked manually:
Kerberos KDC: UDP (88): SKIPPED
Kerberos Kpasswd: UDP (464): SKIPPED
Connection from replica to master is OK.
Start listening on required ports for remote master check
Get credentials to log in to remote master
Check RPC connection to remote master
trying https://auth01.idm.wan/ipa/json
[try 1]: Forwarding 'ping/1' to json server 'https://auth01.idm.wan/ipa/json'
Execute check on remote master
[try 1]: Forwarding 'server_conncheck' to json server 'https://auth01.idm.wan/ipa/json'
Check connection from master to remote replica 'auth02.idm.wan':
Failed to connect to port 389 tcp on 10.0.102.56
Directory Service: Unsecure port (389): FAILED
Failed to connect to port 636 tcp on 10.0.102.56
Directory Service: Secure port (636): FAILED
Failed to connect to port 88 tcp on 10.0.102.56
Kerberos KDC: TCP (88): FAILED
Failed to connect to port 88 udp on 10.0.102.56
Kerberos KDC: UDP (88): WARNING
Failed to connect to port 464 tcp on 10.0.102.56
Kerberos Kpasswd: TCP (464): FAILED
Failed to connect to port 464 udp on 10.0.102.56
Kerberos Kpasswd: UDP (464): WARNING
Failed to connect to port 80 tcp on 10.0.102.56
HTTP Server: Unsecure port (80): FAILED
Failed to connect to port 443 tcp on 10.0.102.56
HTTP Server: Secure port (443): FAILED
The following UDP ports could not be verified as open: 88, 464
This can happen if they are already bound to an application
and ipa-replica-conncheck cannot attach own UDP responder.
ERROR: Port check failed! Inaccessible port(s): 389 (TCP), 636 (TCP), 88 (TCP), 464 (TCP), 80 (TCP), 443 (TCP)
ERROR: Remote master check failed with following error message(s):
ipa-replica-conncheck returned non-zero exit code
Best regards
6 years, 1 month
why would "rpm -V setup" show /etc/fstab with changed mode?
by Robert P. J. Day
another question based on something that tripped me up last week
teaching, when i tried a simple demo and was confused by the result.
was demonstrating how "rpm -V" could verify an installed package,
and randomly chose the "setup" package since it consists of numerous
fundamental system files for which some errors in verification would
be cause for concern, and got the following on my F27 system:
$ rpm -V setup
.M....... c /etc/fstab
S.5....T. c /etc/printcap
S.5....T. c /etc/profile
.M....G.. g /var/log/lastlog
$
i have no problem with files whose contents will invariably change
after further configuration, but i was confused about the "M" flag
for /etc/fstab, suggesting that the mode (type/permissions) for that
file were different from the installation values.
as i see it, why should any system config file like /etc/fstab
change its mode after installation? shouldn't a file like that be
installed with the correct mode from the beginning?
i took a look at the spec file for that package here:
https://src.fedoraproject.org/rpms/setup/blob/master/f/setup.spec
and i notice that other files, after being "touch"ed, are chmoded to
0644, but not /etc/fstab/, whose current mode on my system is 0664:
-rw-rw-r--. 1 root root 628 Jan 14 2016 /etc/fstab
as a test, i chmod'ed /etc/fstab to 0644, and the verify diagnostic
went away.
i realize this discrepancy isn't a problem -- things will continue
to work just fine -- but it seems unnecessary to generate a
superfluous "rpm -V" line for /etc/fstab if it were installed with
non-matching mode in the first place.
is there some reason for the above? am i missing something?
rday
6 years, 1 month
can i limit "dnf search/info" to a selected set of architectures?
by Robert P. J. Day
i've pawed over the man page for dnf and i can't figure out how to
do something simple -- i want to restrict the output of commands like
"dnf search" or "dnf info" to just a selected set of architectures.
example:
$ dnf search ftp
ftp.x86_64 : The standard UNIX FTP (File Transfer Protocol) client
lftp-scripts.noarch : Scripts for lftp
vsftpd.x86_64 : Very Secure Ftp Daemon
ftplib.i686 : Library of FTP routines
ftplib.x86_64 : Library of FTP routines
... snip ...
in the above, i'm not interested in seeing any i686 arch packages, but
i can't figure out how to restrict that (if it's even possible).
ideally, i'd like to restrict package arches for these queries to
x86_64 or noarch, and "man dnf" suggests the "--arch" option, but that
doesn't have the effect i'm after:
$ dnf search ftp --arch x86_64
usage: dnf search [-c [config file]] [-q] [-v] [--version]
... snip ...
dnf search: error: unrecognized arguments: --arch x86_64
$
"man dnf" suggests you can do this with the "repoquery" command:
$ dnf repoquery --whatprovides webserver --arch i686
am i overlooking something obvious?
rday
6 years, 1 month
superfluous consultation of /usr/lib/rpm/rpmrc?
by Robert P. J. Day
pedantic nitpickery ... just noticed in the man page for "rpm" the
default path for configuration files:
--rcfile FILELIST
Replace the list of configuration files to be read. Each of the files in
the colon separated FILELIST is read sequentially by rpm for configuration
information. Only the first file in the list must exist, and tildes will
be expanded to the value of $HOME. The default FILELIST is
/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc.
and while both of those first two files exist on my F27 system, the
latter (/usr/lib/rpm/redhat/rpmrc) opens with the line:
include: /usr/lib/rpm/rpmrc
which seems superfluous as that file is already part of the default
FILELIST.
i'm sure it doesn't do any harm, it just seems unnecessary, no?
rday
6 years, 1 month
Re: Problems Pychess, freezes sometimes during playing
by Joerg Lechner
Hi,
I can not close Pychess anymore, and also the rest of the desktop does stopps working after one or two clicks. I don't know the reason, I use level 7 in Pychess, and the error seems to occur, in a situation, where Pychess is forced to "think" more before the next draw, it's not possible to export the data and also not possible to make a screen shot - blocked. I use Pychess white and user black. This situation will occur again in one of the next games. The last play -reason for this post- ended in emergency mode, possibly the reason is not only Pychess but some interworking with Kernel or interworking in the Kernel area.
Kind regards Joerg
-----Ursprüngliche Mitteilung-----
Von: Samuel Sieb <samuel(a)sieb.net>
An: users <users(a)lists.fedoraproject.org>
Verschickt: Mi, 7. Mrz 2018 23:43
Betreff: Re: Problems Pychess, freezes sometimes during playing
On 03/07/2018 05:24 AM, Joerg Lechner wrote:
> Pychess freezes sometimes. During freezing the time counter continues,
> but Pychess doesn't accept a move, it's also not possible to export the
> data.
>
> The only way to get around is a reboot of the system.
> How can I contribute in analyzing this problem?
Why do you have to reboot the system? Does the rest of the desktop not
work as well?_______________________________________________users mailing list -- users(a)lists.fedoraproject.orgTo unsubscribe send an email to users-leave(a)lists.fedoraproject.org
6 years, 1 month
Problems Pychess, freezes sometimes during playing
by Joerg Lechner
Hi,
Pychess freezes sometimes. During freezing the time counter continues, but Pychess doesn't accept a move, it's also not possible to export the data.
System F27,
Name : kernel
Version : 4.15.6
Release : 300.fc27
Arch : x86_64
Name : pychess
Version : 0.12.4
Release : 9.fc27
Arch : noarch
The only way to get around is a reboot of the system.
How can I contribute in analyzing this problem?
Kind regards Joerg
6 years, 1 month