python3 and gnome packages
by Paolo Galtieri
Folks,
about a week ago I posted an email regarding bindings to libgnome,
but I never did see the post on the list, just one person's response.
The issue is that the program I use for doing backups, sbackup, fails
with python 3. The 2 main failures are in regard to the following:
import gnome.ui
and
import gnome.vfs
or more specifically the packages:
gnome-python2-gnomevfs-2.28.1-23.fc29.x86_64
gnome-python2-gnome.x86_64
so my question is how do I get the same features in python 3?
The gnome.vfs failure occurred after I upgraded from F31 to F32. Under
F31 the front end of sbackup fails because of the lack of gnome.ui.
Under F32 the back end now fails due to the lack of gnome.vfs.
Any help is appreciated.
Paolo
3 years, 11 months
NetworkManager stymies me again
by Tom Horsley
I was finally going to try to setup my network using nm
in fedora 32. I figured after 10 years or so all the
bits I use might finally work :-).
But, I've defined a bridge with (seemingly) all the
same properties as the fedora 31 bridge I created
with network-scripts, yet my virtual machines using
bridge networking never get an IP address, as if the
router dhcp server never sees them.
Is there some magic I'm missing to make things on the
bridge visible on the physical network?
Here's the commands I used to setup the bridge:
nmcli con show
nmcli con add ifname br0 type bridge con-name br0
nmcli con add type bridge-slave ifname eth0 master br0
nmcli con mod br0 ipv4.ignore-auto-dns yes
nmcli con mod br0 bridge.mac-address xx:xx:...
nmcli con modify br0 bridge.stp no
nmcli con down "Wired connection 1"
nmcli con up br0
nmcli con show
The bridge gets an IP address from the router, but virtual
machines do not:
<interface type="bridge">
<mac address="52:54:00:1c:57:9f"/>
<source bridge="br0"/>
<model type="virtio"/>
<address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
</interface>
3 years, 11 months
homed
by Javier Perez
Reading this article, I am beginning to really detest systemd....
Why does it have to hang its tentacles on the home directory?
https://www.techrepublic.com/article/linux-home-directory-management-is-a...
If we continue like this, soon Linux will have a "Registry" and "Registry
Editor"
JP
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
3 years, 11 months
minor gnome annoyance
by Tom Horsley
They finally got rid of the "you have to scroll the screen all the
way up from the bottom" to get out of the lock screen.
Now it says click or hit any key.
If you hit a key, it does get you out of the lock screen, but that
key also winds up being passed to the password entry field as the
first character of your password, so then you type your actual
password and get a login error :-).
Stick to clicking.
3 years, 11 months
Re: Upgrade to 32 stymied
by Frank
On 2020-05-03 2:10 p.m., Ranjan Maitra wrote:
> So, it appears based on your description that rxvt on F32 is behind rxvt on F31. I suspect that in this situation I would do one of two things.
>
> 1. Wait a few days and let the problem take care of itself as the F32 package gets updated.
>
> 2. dnf erase rxvt and upgrade. Then, after the system comes back with F32, dnf install rxvt. Of course, this assumes that you have some terminal window option.
>
> HTH,
>
> Many thanks and best wishes,
> Ranjan
>
>
>
> On Sun, 3 May 2020 12:24:22 -0400 Frank <beacon(a)videotron.ca> wrote:
>
>> I am blocked upgrading my 31 to 32. Updated 31, and did the "sudo dnf
>> system-upgrade download --releasever=32 --allowerasing". It dl 1.2 gigs of
>>
>> packages, and at the very end told me rxvt was being blocked because of
>> a conflict with the newer version.
>>
>> I then ran "sudo dnf system-upgrade reboot" and it said system is not
>> ready for upgrade.
>>
>> I am stumped!
>>
>> Any suggestions??
>>
>>
That's what I ended up doing. It appeared after close examination
that RXVT was the only
thing blocking the upgrade. DNF had not removed the old one even though
I ran DNF with
allow-erasing on the command line.
After I removed RXVT and re-ran DNF system-upgrade with an additional
--setopt=keepcache=1 on the command
line when it finished quite quickly....then dnf system-upgrade reboot
worked fine. A long time later I had my F32 desktop
back. Since then I've had a few crashes but nothing serious.
Thanks
3 years, 11 months
Re: homed
by J.Witvliet@mindef.nl
From: "Javier Perez" <pepebuho(a)gmail.com<mailto:pepebuho@gmail.com>>
Date: Sunday, 3 May 2020 at 08:02:29
To: "Community support for Fedora users" <users(a)lists.fedoraproject.org<mailto:users@lists.fedoraproject.org>>
Subject: Re: homed
I wonder about that "encryption". They are encrypting MY home directories with a key that I do not know. I imagine it will be somewhat associated to my login password, but still, what could go wrong?
Encrypting you’re data with a key unknown to you? What could go wrong?
Well, it’s party time at the NSA & CIA.
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
3 years, 11 months
Upgrade to 32 stymied
by Frank
I am blocked upgrading my 31 to 32. Updated 31, and did the "sudo dnf
system-upgrade download --releasever=32 --allowerasing". It dl 1.2 gigs of
packages, and at the very end told me rxvt was being blocked because of
a conflict with the newer version.
I then ran "sudo dnf system-upgrade reboot" and it said system is not
ready for upgrade.
I am stumped!
Any suggestions??
Thanks
3 years, 11 months
How to turn of Intel VGA controller?
by William Oliver
I am running Fedora 31 on an HP Envy 17t laptop with a NVIDIA MX250
gpu. I have installed the NVIDIA driver downloaded from NVIDA, and it
seems to have installed just fine. I have installed CUDA, as far as I
can tell.
I am trying to use the GPU rendering capabilities of Blender, a 3D
modeling package. However, the package does not believe there is a
CUDA compatible GPU installed.
I *think* it's because I'm actually running the Intel VGA controller.
So, if I'm right, my question is, how do I disable the Intel VGA
controller (or not make it the default) so it uses the NVIDIA
controller.
Some more information:
First, of course, graphics seems to work in general. Blender runs
fine, but (for those of you who might use blender), when using the
Cycles renderer, I can only render using the CPU.
I'm using KDE as my desktop.
There's nothing in my BIOS setup screen (when I hit ESC on bootup and
then F10 for BIOS settings) about graphics controller or intel
I have secure boot turned off.
$ uname -aLinux localhost.localdomain 5.6.8-200.fc31.x86_64 #1 SMP Wed
Apr 29 19:10:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ grep '/usr/s\?bin' /etc/systemd/system/display-
manager.serviceExecStart=/usr/bin/sddm
$hwinfo | grep VGA7: PCI 02.0: 0300 VGA compatible controller (VGA)
Model: "Intel VGA compatible controller" Attached to: #37 (VGA
compatible controller) Attached to: #37 (VGA compatible controller)
$hwinfo | grep "3D controller" E: ID_PCI_SUBCLASS_FROM_DATABASE=3D
controller22: PCI 200.0: 0302 3D controller Model: "nVidia 3D
controller"
$lshw... *-pci description: Host bridge product:
Intel Corporation vendor: Intel Corporation physical
id: 100 bus info: pci@0000:00:00.0 version:
0c width: 32 bits clock: 33MHz *-
display description: VGA compatible
controller product: UHD Graphics vendor: Intel
Corporation physical id: 2 bus info: pci@0000:0
0:02.0 version: 02 width: 64
bits clock: 33MHz capabilities: pciexpress msi
pm vga_controller bus_master cap_list rom configuration:
driver=i915 latency=0 resources: irq:141 memory:b2000000-
b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-
dffff...
*-pci:1 description: PCI bridge product:
Intel Corporation vendor: Intel
Corporation physical id: 1c.4 bus info:
pci@0000:00:1c.4 version: f0 width: 32
bits clock: 33MHz capabilities: pci pciexpress
msi pm normal_decode bus_master cap_list configuration:
driver=pcieport resources: irq:123 ioport:4000(size=4096)
memory:b3000000-b3ffffff ioport:a0000000(size=301989888) *-
display description: 3D
controller product: GP108M [GeForce
MX250] vendor: NVIDIA
Corporation physical id: 0 bus info:
pci@0000:02:00.0 version: a1 width: 64
bits clock: 33MHz capabilities: pm msi
pciexpress bus_master cap_list configuration:
driver=nvidia latency=0 resources: irq:16
memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-
b1ffffff ioport:4000(size=128)
$lsmod | grep
nvidianvidia_drm 53248 0nvidia_modeset 1118208 1
nvidia_drmnvidia 20504576 4
nvidia_modesetipmi_msghandler 118784 1
nvidiadrm_kms_helper 237568 2
nvidia_drm,i915drm 598016 13
drm_kms_helper,nvidia_drm,i915
The following is a little odd. This used to load, but while
floundering about, I removed and reinstalled the Nvidia driver from
NVIDIA. Now it won't load:
$ nvidia-settings
ERROR: Unable to load info from any available system
$ nvidia-smi
nvidia-smiSat May 2 13:52:58 2020 +-----------------------------
------------------------------------------------+| NVIDIA-SMI
440.82 Driver Version: 440.82 CUDA Version: 10.2 ||--
-----------------------------+----------------------+----------------
------+| GPU Name Persistence-M| Bus-Id Disp.A |
Volatile Uncorr. ECC || Fan Temp Perf Pwr:Usage/Cap| Memory-
Usage | GPU-Util Compute M.
||===============================+======================+==============
========|| 0 GeForce MX250 Off | 00000000:02:00.0 Off
| N/A || N/A 48C P0 N/A / N/A | 0MiB
/ 4042MiB | 0% Default |+-------------------------------+---
-------------------+--------------------
--
+
+-------------------------------------------------------------
----------------+|
Processes: GPU
Memory || GPU PID Type Process
name Usage ||=========================
====================================================|| No running
processes found |
I assume the tainting stuff below is because I'm using the driver
downloaded from NVIDIA.$dmesg
[ 3.106647] i915 0000:00:02.0: fb0: i915drmfb frame buffer
device[ 3.824513] nvidia: loading out-of-tree module taints
kernel.[ 3.824525] nvidia: module license 'NVIDIA' taints
kernel.[ 3.824526] Disabling lock debugging due to kernel
taint[ 3.829796] nvidia: module verification failed: signature
and/or required key missing - tainting kernel[ 3.839347] nvidia-
nvlink: Nvlink Core is being initialized, major device number
239[ 3.839692] nvidia 0000:02:00.0: enabling device (0006 ->
0007)[ 4.039633] NVRM: loading NVIDIA UNIX x86_64 Kernel
Module 440.82 Wed Apr 1 20:04:33 UTC 2020[ 4.090987] nvidia-
modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
platforms 440.82 Wed Apr 1 19:41:29 UTC 2020[ 4.094488] [drm]
[nvidia-drm] [GPU ID 0x00000200] Loading driver[ 4.094490] [drm]
Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 1
3 years, 11 months