I am getting dreadful warnings about my version of python when I run
pip. So I asked about this with the developers of the script I use
(xml2rfc). I bit of version testing and:
$ pip --version
pip 19.0.3 from /usr/lib/python2.7/site-packages/pip (python 2.7)
$ pip2 --version
pip 19.0.3 from /usr/lib/python2.7/site-packages/pip (python 2.7)
$ pip3 --version
pip 19.0.3 from /usr/lib/python3.7/site-packages/pip (python 3.7)
$ ls -ls /usr/bin/pip*
4 -rwxr-xr-x. 1 root root 408 Jul 17 04:23 /usr/bin/pip
0 lrwxrwxrwx. 1 root root 9 Jul 17 04:23 /usr/bin/pip-2 -> ./pip-2.7
4 -rwxr-xr-x. 1 root root 408 Jul 17 04:23 /usr/bin/pip2
0 lrwxrwxrwx. 1 root root 8 Jul 17 04:23 /usr/bin/pip-2.7 -> ./pip2.7
4 -rwxr-xr-x. 1 root root 408 Jul 17 04:23 /usr/bin/pip2.7
0 lrwxrwxrwx. 1 root root 9 Jul 17 04:23 /usr/bin/pip-3 -> ./pip-3.7
4 -rwxr-xr-x. 1 root root 408 Jul 17 04:23 /usr/bin/pip3
0 lrwxrwxrwx. 1 root root 8 Jul 17 04:23 /usr/bin/pip-3.7 -> ./pip3.7
4 -rwxr-xr-x. 1 root root 408 Jul 17 04:23 /usr/bin/pip3.7
24 -rwxr-xr-x. 1 root root 22816 Jun 19 10:44 /usr/bin/pipewire
so pip does not seem to be a symlink to pip2, but perhaps just a copy?
I suspect I will still be running F30 come Jan 2020 when Python 2.7 gets
DEPRECATION: Python 2.7 will reach the end of its life on January 1st,
2020. Please upgrade your Python as Python 2.7 won't be maintained after
that date. A future version of pip will drop support for Python 2.7.
Do I need to do anything, or will this be self-correcting come the new year?
Hi Fedora World .
I have a maybe stupid question : I use a Fritz-Box 7490 and try to install
Icons on screen : fritz.nas , fritz.mediaserver , myfritz , but one way or
another I do not manage this item .
Is there a solution ?
Kind regards ,
Ger van Dijck .
Using Opera's mail client: http://www.opera.com/mail/
I had a major crash on my F30 laptop a couple of weeks ago. I was able
to boot to emergency mode and use ddrescue to make forensic copies of
all four partitions to an external drive.
After re-installing F30 I can't seem to get five VMs copied back and
working. Is a metadata file for the Virtual Machine Manager stored
somewhere apart from where the VMs were stored that I need to bring
I've got an odd problem that I was hoping for some help on.
The laptop was previously working fine, I am running F30, updated regularly.
I've got an Acer laptop that has been shutting down suddenly. (I
suspect a bad battery, working on that.)
After a sudden shutdown last night, I now get a kernel panic on boot
right after "Starting Switch Root..."
I was able to boot from a USB stick, and was able to read the journal,
but I didn't see anything obvious to help.
I was able to get all of my data off of the (encrypted) disks, so
that's not a problem, but I don't want to just give up, and wash and
reload too quickly.
I got this error on cockpit and I want to fix it:
13:13 [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. kernel
The content of this error is:
[drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
I have a server running fedora that denies access to me as user "bobg."
I can ssh as root and have re-entered the "passwd" for "bobg" and it
reported "passwd: all authentication tokens updated successfully."
I also added an= new user and had the same result.
Am I being prevented from actually changing the password via ssh
perhaps? If so it's strange that it reports tokens updated successfully.
There's no display or keyboard attached,
I can still access view the contents with Samba and the samba password
but need user access for me. I suppose root access would wok but I have
spent all morning at this and don't know what else to do to fix the user
Bob Goodwin - Zuni, Virginia, USA
box10 FEDORA-29/64bit LINUX XFCE Fastmail POP3
i'm trying to configure my samsung laser printer ml-1660
as an (usb) duplex printer, but tis will not succeed anymore.
I'm using the Cinnamon desktop.
Neither the Cinnamon system settings menu entry nor the
system-config-printer (using obviously the splix pckg) command will
All system upgrades are installed.
Each advice would be welcome.
Fedora release 30 (Thirty)
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
My goal is to install nvidia cuda for some machine learning on a new Lenovo Thinkpad P52S laptop
running Fedora 30. The laptop comes with both an integrated intel card and an nvidia quadro P500 card
(I think this is called Optimus). I want to use the intel card for display and the nvidia exclusively
for machine learning.
I've followed various tutorials and blogs on the web, most notably
the rpmfusion howto: https://rpmfusion.org/Howto/NVIDIA
and a recent fedora magazine article: https://fedoramagazine.org/install-nvidia-gpu/
The latter says (in the comments) that there is no need to disable nouveau but I had to do that in
the past every time I installed the nvidia drivers, so I'm trying to do that now as well.
So I did the following:
1. Installed the nvidia rpms:
dnf install xorg-x11-drv-nvidia akmod-nvidia
which installed the following + dependencies:
[root@thinkpad ~]# rpm -qa | grep -i nvidia
2. The dnf install command modified the boot options, to blacklist nouveau:
[root@thinkpad ~]# cat /etc/default/grub
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 resume=UUID=d1406222-e963-4043-a6f9-10c784752ed8 rhgb quiet"
3. I read that is not enough though, as if nouveau is in the initram disk it will still do modeset = 1,
so I blacklisted it in modprobe.d and created a new initram disk:
[root@thinkpad ~]# cat /etc/modprobe.d/blacklist_nouveau.conf
options nouveau modeset=0
# backup nouveau initram disk
[root@thinkpad boot]# cp initramfs-5.2.11-200.fc30.x86_64.img initramfs-5.2.11-200.fc30.x86_64_nouveau.img
# create new one:
[root@thinkpad boot]# dracut --force
[root@thinkpad boot]# lsinitrd initramfs-5.2.11-200.fc30.x86_64.img | grep -i nouveau
-rw-r--r-- 1 root root 44 Feb 14 2019 etc/modprobe.d/blacklist_nouveau.conf
drwxr-xr-x 2 root root 0 Feb 14 2019 usr/lib/modules/5.2.11-200.fc30.x86_64/kernel/drivers/gpu/drm/nouveau
-rw-r--r-- 1 root root 636252 Feb 14 2019 usr/lib/modules/5.2.11-200.fc30.x86_64/kernel/drivers/gpu/drm/nouveau/nouveau.ko.xz
so it picked up the blacklist_nouveau.conf file.
4. set runlevel 3
systemctl set-default multi-user.target
5. I'm running Xorg, not Wayland:
[root@thinkpad ~]# pidof xinit
[root@thinkpad ~]# pidof Xwayland
6. Reboot. Even before starting X, I still get nouveau:
[root@thinkpad ~]# lsmod | grep nouveau
nouveau 2265088 0
mxm_wmi 16384 1 nouveau
ttm 118784 1 nouveau
i2c_algo_bit 16384 2 i915,nouveau
drm_kms_helper 225280 2 i915,nouveau
drm 495616 8 drm_kms_helper,i915,ttm,nouveau
wmi 36864 4 intel_wmi_thunderbolt,wmi_bmof,mxm_wmi,nouveau
video 49152 3 thinkpad_acpi,i915,nouveau
I can, however modprobe -r nouveau and things seem OK.
But what do I do to have it not load on boot? When this happened in the past, as a last resort,
I removed the appropriate rpms, but now the nouveau driver seems to be part of the kernel-modules
[root@thinkpad ~]# rpm -qf /usr/lib/modules/5.2.11-200.fc30.x86_64/kernel/drivers/gpu/drm/nouveau/nouveau.ko.xz kernel-modules-5.2.11-200.fc30.x86_64
Any help on this, anyone? Thanks!