users November 2019

users@lists.fedoraproject.org

97 participants
123 discussions

Core for a netbook??
by Beartooth 17 Nov '19

17 Nov '19

I have an old System76 netbook "starling," I think one of the first ones ever, whenever that was. Years ago. They were an Ubuntu shop then, and afaik still are; but I'm not. The first thing I did with it was to install the then current Fedora release. F30 is on it now, but I can't say it runs. It boots up, and then freezes. Local people who know things tell me it just isn't big enough any more. I got it to do email in waiting rooms; but I found I usually got my turn before I got into my email. That proved true even when the netbook was still quick; wifi in the places I waited was slow. So I guess I can afford a risk: would CoreOS be able to handle Alpine (formerly Pine from UW) and a browser or two? Maybe even Pan?? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

4 6

Someone here using restic (Backup)
by sixpack13 17 Nov '19

17 Nov '19

hallo currently I'm doing backup's with rsync. Today "restic" got my attention and I'm thinking to move to it, cause of it's ability to verify the backup (somehow). https://github.com/restic/restic/ Is someone here who is using it and can share some experiences ?

5 16

4877 packages to update... Time to clean house?
by Richard Shaw 17 Nov '19

17 Nov '19

Working on downloading all the packages to update to Fedora 31 and noticed that I have 4877 packages (and 6GB) to update (excluding a handful of new weak dependencies). Anyone have a good workflow they use to remove unneeded packages? Thanks, Richard

5 7

Silly Web UI on Server?
by John M. Harris Jr 17 Nov '19

17 Nov '19

Does anyone know if it's possible to install the Server spin without getting Cockpit? I like the hardware support group, but I have no idea why I don't get an option to turn off that useless web UI. -- John M. Harris, Jr. Splentity

6 13

The system printing service doesn't seem to be available
by Simon Colston 17 Nov '19

17 Nov '19

Fedora 31 Workstation I installed Xfce to give it a try, didn't like it so I removed it. Unfortunately, since then, when I go to Settings -> Devices -> Printers I get the message "Sorry! The system printing service doesn't seem to be available" I did some googling and found out that CUPS is responsible for printing. The timestamp on the file /etc/cups/subscriptions.conf.O is the time I installed Xfce and the timestamp on /etc/cups/subscriptions.conf.rpmsave is the time I removed Xfce. So that's how I broke it, I guess. I now only have 2 CUPS packages installed: cups-libs.x86_64 cups-pk-helper.x86_64 Can I just install cups.x86_64 package or is there anything else I need to do to get printing working again? -- Simon

3 4

Bridged connection MAC address change after F31 update
by Sam Varshavchik 16 Nov '19

16 Nov '19

I have a fixed IP address assigned via DHCP to a machine that I just updated to F31. After the update, I was slightly surprised when it didn't come up on its fixed IP address. After looking through the logs, the DHCP server is now apparently getting a DHCP request from a different MAC address, apparently the bridge's MAC address. I updated the DHCP config, and brought the network connection down/up, and it came up on its fixed IP address, normally. In F30, the kernel was kernel-5.3.11-200.fc30.x86_64, and it's now kernel-5.3.11-300.fc31.x86_64, of course; so this doesn't look like a kernel change. The relevant data is: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vnet0 state UP group default qlen 1000 link/ether 00:30:48:fc:83:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::230:48ff:fefc:83fa/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:30:48:fc:83:fb brd ff:ff:ff:ff:ff:ff 4: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 96:03:13:50:00:eb brd ff:ff:ff:ff:ff:ff inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic vnet0 valid_lft 603710sec preferred_lft 603710sec inet6 fe80::9403:13ff:fe50:eb/64 scope link valid_lft forever preferred_lft forever Up until F30, the DHCP server was seeing requests from 00:30:48:fc:83:fa, and now the DHCP server is seeing requests from 96:03:13:50:00:eb. I'm hoping that, at least, the bridge won't be getting random MAC addresses with every boot?

3 5

What to do with a non-NM managed bridge, now
by Sam Varshavchik 16 Nov '19

16 Nov '19

A very long time ago I stumbled my way into setting up a virtual bridge so that a qemu-hosted Windows 10 VM could have a static IP address assigned from my LAN's DHCP server, and be reachable from my LAN, directly. This was a while ago; to the best of my recollection at that time NetworkManager did not support bridges; or the there was some other reason the bridge had to be set up that way. Well, for a reason that I'll describe separately, after updating to F31 it was necessary to manually ifdown/ifup the bridge in order to fix something. And I'm told that ifdown/ifup is being retired and I should use nmcli. But nmcli doesn't see it, of course. So, what are my options? Reconfigure my monkey-patched configuration to a NM- managed one? What I currently have is: # cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Intel Corporation 82573E Gigabit Ethernet Controller (Copper) DEVICE=eth0 BRIDGE=vnet0 HWADDR=00:30:48:FC:83:FA ONBOOT=yes OPTIONS=layer2=1 TYPE=Ethernet NM_CONTROLLED=no USERCTL=no IPV6INIT=yes DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no NAME="System eth0" #UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 BOOTPROTO=dhcp ETHTOOL_OPTS="advertise 030" and # cat ifcfg-vnet0 DEVICE=vnet0 TYPE=Bridge BOOTPROTO=dhcp ONBOOT=yes IPV6INIT=no USERCTL=no ZONE=FedoraWorkstation NM_CONTROLLED=no Currently, NetworkManager sees /something/: # nmcli c show NAME UUID TYPE DEVICE virbr0 65a32109-d944-40b1-abf8-15458f81585c bridge virbr0 And when everything's up, "ip addr" shows: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vnet0 state UP group default qlen 1000 link/ether 00:30:48:fc:83:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::230:48ff:fefc:83fa/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:30:48:fc:83:fb brd ff:ff:ff:ff:ff:ff 4: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 96:03:13:50:00:eb brd ff:ff:ff:ff:ff:ff inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic vnet0 valid_lft 604185sec preferred_lft 604185sec inet6 fe80::9403:13ff:fe50:eb/64 scope link valid_lft forever preferred_lft forever 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 02:23:42:87:19:5d brd ff:ff:ff:ff:ff:ff Is this as simple as manually changing NM_CONTROLLED=yes in both initscripts? That's easy enough to do, test, and roll it back, if it blows up, but can anyone think of anything else that needs to be tweaked.

3 3

akmod nvidia
by Amadeus WM 16 Nov '19

16 Nov '19

I have an older nvidia card and I'm using the proprietary drivers with akmod from rpmfusion. akmod-nvidia-340xx-340.107-8.fc30.x86_64 xorg-x11-drv-nvidia-340xx-kmodsrc-340.107-4.fc30.x86_64 xorg-x11-drv-nvidia-340xx-libs-340.107-4.fc30.x86_64 xorg-x11-drv-nvidia-340xx-340.107-4.fc30.x86_64 kmod-nvidia-340xx-5.2.18-200.fc30.x86_64-340.107-8.fc30.x86_64 Every time the kernel gets updated, akmod does its thing, builds the kmod-nvidia rpm and all is well. Except for 5.3 kernels, akmod fails to build. For instance, in /var/cache/akmods/nvidia-340xx/340.107-8-for-5.3.11-200.fc30.x86_64.failed.log I see 2019/11/15 21:07:34 akmodsbuild: /tmp/akmodsbuild.LuUtkSzx/BUILD/nvidia-340xx-kmod-340.107/_kmod_build_5.3.11-200.fc30.x86_64/nv-linux.h: In function 'nv_execute_on_all_cpus': 2019/11/15 21:07:34 akmodsbuild: /tmp/akmodsbuild.LuUtkSzx/BUILD/nvidia-340xx-kmod-340.107/_kmod_build_5.3.11-200.fc30.x86_64/nv-linux.h:903:21: error: void value not ignored as it ought to be 2019/11/15 21:07:34 akmodsbuild: 903 | int __ret = on_each_cpu(func, info, wait); | ^~~~~~~~~~~ So I guess in kernel 5.3 on_each_cpu() no longer returns int, but void. The nvidia driver has not been updated to reflect that. Do I need to wait for nvidia to fix that (if they ever do, given that this is the legacy driver) or does anyone on the fedora side do any kind of back porting that can fix it? Do I file a bug with bugzilla?

3 3

Fedora 31, nextcloud-client always asking for kde wallet password after logging in
by Matti Pulkkinen 16 Nov '19

16 Nov '19

Hello! Whenever I log in to Fedora 31, nextcloud-client asks for the password for a KDE wallet. The Nextcloud client on Ubuntu never asks for a password like this, so what's different here, and how can I make it stop? -- Regards, Matti Pulkkinen

2 4

Tip: WoeUSB and FC31
by ToddAndMargo 15 Nov '19

15 Nov '19

Hi All, If you go to cut a Windows installer flash drive from iso with WoeUSB under Fedora 31, you are in for some surprises. It crashes on exit. But the good new is that the drive comes out perfectly. And it boots both Legacy and EUFI. Very sweet! After WoeUSB crashed, you need to do a DF and a umount on the open loop drive and anything else it left mounted after it crashes. I opened the following bug report on it: https://bugzilla.redhat.com/show_bug.cgi?id=1773142 -T

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
13
Older →

Jump to page: