users December 2018

users@lists.fedoraproject.org

100 participants
112 discussions

luks root partition and grub opens it using usb - how to?
by lejeczek 04 Dec '18

04 Dec '18

hi guys I wonder if it is possible to have a passphrase to the root partition on a usb/sd and tell the grub to check and use it and if that fails then fall back to user providing the passphrase, as normally by the means of keyboard. Would you know if that works and if there is any doc/manual for it? many thanks, L.

1 0

Strange firewalld error from fail2ban
by Patrick O'Callaghan 04 Dec '18

04 Dec '18

$ sudo systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-12-03 10:10:44 GMT; 8h ago Docs: man:firewalld(1) Main PID: 844 (firewalld) Tasks: 2 (limit: 4915) Memory: 32.1M CGroup: /system.slice/firewalld.service └─844 /usr/bin/python3 /usr/sbin/firewalld --nofork --nopid Dec 03 10:10:43 bree systemd[1]: Starting firewalld - dynamic firewall daemon... Dec 03 10:10:44 bree systemd[1]: Started firewalld - dynamic firewall daemon. Dec 03 10:10:45 bree firewalld[844]: ERROR: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.0 (legacy): Set fail2ban-sshd doesn't exist. Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Dec 03 10:10:45 bree firewalld[844]: ERROR: COMMAND_FAILED: Direct: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.0 (legacy): Set fail2ban-sshd doesn't exist. Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Not sure where to look for this. It's probably been around for a while but I've only just noticed it. poc

2 2

ssh between el7 and fc28 boxes
by John Pilkington 03 Dec '18

03 Dec '18

Hi: I have two boxes connected to the same router. One runs SL7.5, from tomorrow probably SL7.6, which is an el7 clone, and the other runs Fedora 28. I can ssh and rsync from F28 to SL7, but permission is denied in the opposite direction. Port 22 is open. I now have copies of both versions of /etc/sshd and intend to examine diffs. Google provides many links but nothing that looks authoritative or, preferably, authoritative and simple. Any help wpuld be appreciated. John P

5 12

kernel 4.19.5 crashes in Xen DomU
by Markus Schönhaber 03 Dec '18

03 Dec '18

Hi, I'm running Fedora 28 in a Xen DomU on a Debian Stretch Dom0. This used to work fine but kernel 4.19.5 crashes on boot (see console output below) - 4.19.4 and earlier don't show any problems. Is anyone else seeing this? Is there a workaround? Regards mks Output of # xl create /etc/xen/fedora.cfg -c > ┌────────────────────────────────────────────────────────────────────────┐ > │ Fedora (4.19.5-200.fc28.x86_64) 28 (Twenty Eight) │ > │ Fedora (4.19.4-200.fc28.x86_64) 28 (Twenty Eight) │ > │ Fedora (4.19.3-200.fc28.x86_64) 28 (Twenty Eight) │ > │ Fedora (0-rescue-ff8e39e06b0946d4b8aef0daeb33efb0) 28 (Twenty Eight) │ > │ │ > │ │ > │ │ > │ │ > └────────────────────────────────────────────────────────────────────────┘ > Use the ^ and ┴ keys to select which entry is highlighted. > Press enter to boot the selected OS, 'e' to edit the > commands before booting, 'a' to modify the kernel arguments > before booting, or 'c' for a command line. > > > > > Will boot selected entry in 1 seconds > > > [ 1.919053] BUG: unable to handle kernel paging request at ffff88884b969000 > [ 1.919061] PGD 220c067 P4D 220c067 PUD 0 > [ 1.919067] Oops: 0000 [#1] SMP NOPTI > [ 1.919072] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.19.5-200.fc28.x86_64 #1 > [ 1.919080] RIP: e030:ptdump_walk_pgd_level_core+0x21a/0x4f0 > [ 1.919085] Code: b8 00 00 00 00 00 40 00 00 49 83 c7 08 49 01 c5 4c 3b 7c 24 40 0f 84 c2 02 00 00 4c 89 e8 48 c1 f8 10 48 89 84 24 80 00 00 00 <49> 8b 3f 48 f7 c7 9f ff ff ff 0f 85 22 ff ff ff 41 b8 03 00 00 00 > [ 1.919094] RSP: e02b:ffffc90000717e68 EFLAGS: 00010286 > [ 1.919099] RAX: ffff800000000000 RBX: ffffffff8191c029 RCX: 0000000000000000 > [ 1.919104] RDX: 0000000000000101 RSI: ffffffff8220a000 RDI: 000000084b969067 > [ 1.919109] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 > [ 1.919114] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 > [ 1.919118] R13: 8000000000000000 R14: 0000000000000000 R15: ffff88884b969000 > [ 1.919128] FS: 0000000000000000(0000) GS:ffff88807d400000(0000) knlGS:0000000000000000 > [ 1.919133] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 1.919137] CR2: ffff88884b969000 CR3: 000000000220a000 CR4: 0000000000042660 > [ 1.919144] Call Trace: > [ 1.919151] ? printk+0x58/0x6f > [ 1.919157] ? rest_init+0xaa/0xaa > [ 1.919161] kernel_init+0x31/0x107 > [ 1.919166] ret_from_fork+0x35/0x40 > [ 1.919170] Modules linked in: > [ 1.919175] CR2: ffff88884b969000 > [ 1.919179] ---[ end trace a85adfe208024c43 ]--- > [ 1.919185] RIP: e030:ptdump_walk_pgd_level_core+0x21a/0x4f0 > [ 1.919190] Code: b8 00 00 00 00 00 40 00 00 49 83 c7 08 49 01 c5 4c 3b 7c 24 40 0f 84 c2 02 00 00 4c 89 e8 48 c1 f8 10 48 89 84 24 80 00 00 00 <49> 8b 3f 48 f7 c7 9f ff ff ff 0f 85 22 ff ff ff 41 b8 03 00 00 00 > [ 1.919199] RSP: e02b:ffffc90000717e68 EFLAGS: 00010286 > [ 1.919204] RAX: ffff800000000000 RBX: ffffffff8191c029 RCX: 0000000000000000 > [ 1.919209] RDX: 0000000000000101 RSI: ffffffff8220a000 RDI: 000000084b969067 > [ 1.919214] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 > [ 1.919218] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 > [ 1.919223] R13: 8000000000000000 R14: 0000000000000000 R15: ffff88884b969000 > [ 1.919231] FS: 0000000000000000(0000) GS:ffff88807d400000(0000) knlGS:0000000000000000 > [ 1.919237] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 1.919241] CR2: ffff88884b969000 CR3: 000000000220a000 CR4: 0000000000042660 > [ 1.919261] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 > [ 1.919261] > [ 1.919269] Kernel Offset: disabled

3 4

Changing mount options without restarting
by Patrick O'Callaghan 03 Dec '18

03 Dec '18

I'm getting "filesystem not responding" messages from an NFS-mounted NAS which I suspect is just slow (it spins down its disks when not in use). I'm using automount and that appears to be related as it never used to happen with normal mounting. I've changed the 'timeo' parameter in the /etc/fstab line and run 'mount -a' but the mount parameters for the filesystem have not changed. I've also restarted anything that seems relevant from systemd: systemctl restart storage-Backups.mount and systemctl restart proc-fs-nfsd.mount and systemctl restart proc-sys-fs-binfmt_misc.automount to no effect. How can I get this to work without rebooting? poc

6 18

Optical track ball finally arrived
by Robert Moskowitz 03 Dec '18

03 Dec '18

Thanks to all. The kensington Expert Track ball arrived today. Crazy Michigan no-fault... It had to be ordered via a doctors order for workstation modification and then through an approved medical supply house that could only order it directly from Kensington... But it is here and I CAN work with it left-handed. This keeps my right hand on the keyboard with less stress not having to reach for a right-hand mouse (I just could not control a regular mouse left-handed). This is going to make a difference in my work and my recovery. BTW, I am taking my first steps without a cane and am 'graduating' to out-patient PT for the walking. But the dislocated shoulder has another 3 weeks to go... Take care

4 3

incomplete boot after Fc26-27 upgrade
by Jon LaBadie 03 Dec '18

03 Dec '18

My primary system was still running Fedora 26 and I'm in the process of updating stepwise using the dnf-system-upgrade plugin. The download and update to F27 seemed to go fine. But reboots fail and put me in "emergency/rescue" mode. Once I've logged in as root and su'ed to my personal account, I can turn networking on, run startx or mate-session for a desktop session. VirtualBox also works in the desktop. Hardware if pertainent: MB Gigabyte X79-UP4 CPU Intel 3930K at 3.8GHz MEM 32GB VID nVidia GTX 660 Ti DISK 4, Mix of SSD and rotating, all but /boot managed by LVM KERN 4.18.19-100.fc27.x86_64 I've cut and pasted the error messages from 'journalctl -b' (i.e., the ones colored red) and include a little context on some. I do not see the problem, hopefully others will. Error output from "journalctl -b". There were 12 pairs of these messages varying only in the string "_SB.C00X". The "X" was hex 0-B. Fedora 24, 25, and 26 gave these same messages but ran ok. Nov 30 18:29:22 cyber.jgcomp.com kernel: ACPI BIOS Error (bug): Could not resolve [\TST0], AE_NOT_FOUND (20180531/psargs-330) Nov 30 18:29:22 cyber.jgcomp.com kernel: ACPI Error: Method parse/execution failed \_SB.C000._TPC, AE_NOT_FOUND (20180531/psparse-516) The vbox modules mentioned in these message were loaded into the kernel at another point. VirtualBox (Windows 7) runs ok. Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxdrv Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxnetflt Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxnetadp Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxpci Nov 30 18:29:24 cyber.jgcomp.com systemd-udevd[825]: Specified group plugdev unknown These messages are correct, I'm not using ECC memory. Fedora 26 had same messages but worked fine. Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with error -19. ... Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with error -19. Only last line colored red by 'journalctl (hold queue overflow)' Nov 30 18:29:30 cyber.jgcomp.com kernel: kauditd_printk_skb: 115 callbacks suppressed Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: type=1131 audit(1543620570.726:96): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit= Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: audit_lost=38 audit_rate_limit=0 audit_backlog_limit=64 Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow As above, only the "hold queue overflow" lines were colored Nov 30 18:29:34 cyber.jgcomp.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.804:97): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: audit_lost=39 audit_rate_limit=0 audit_backlog_limit=64 Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow Nov 30 18:29:34 cyber.jgcomp.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.816:98): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: audit_lost=40 audit_rate_limit=0 audit_backlog_limit=64 Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1131 audit(1543620574.816:99): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' This may be after login as root to "rescue mode" and "su-ing to my personal account. Nov 30 18:29:54 cyber.jgcomp.com su[1727]: pam_systemd(su-l:session): Failed to connect to system bus: No such file or directory Any ideas? Jon

1 2

night light mode
by Patrick Dupre 02 Dec '18

02 Dec '18

Hello, Since I set the night light mode in manual, I cannot return to automatic mode. How can I change this set up to default? Thank. =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================

5 6

Re: DNF problems
by Frank McCormick 01 Dec '18

01 Dec '18

On 12/1/18 7:21 PM, stan wrote: > On Sat, 1 Dec 2018 09:08:45 -0500 > Frank McCormick <beacon(a)videotron.ca> wrote: > >> I would assume DNF would update the 6 files from rpm-fusion ?? > > Probably dependency errors. Try > dnf update --best > That should show you any package conflicts. > I'll try that when I get back into Fedora...I am also currently dealing with a kernel problem on Debian Sid. Thanks

1 0

DNF problems
by Frank McCormick 01 Dec '18

01 Dec '18

Running Fedora 29, a fresh installation. When I run dnf check-update this is what I get : [root@localhost ~]# dnf check-update unitedrpms 29 - x86_64 133 kB/s | 1.0 MB 00:07 Fedora Modular 29 - x86_64 314 kB/s | 1.5 MB 00:04 Fedora Modular 29 - x86_64 - Updates 768 kB/s | 1.6 MB 00:02 Fedora 29 - x86_64 - Updates 2.8 MB/s | 15 MB 00:05 Fedora 29 - x86_64 3.8 MB/s | 62 MB 00:16 google-chrome 3.0 kB/s | 3.6 kB 00:01 RPM Fusion for Fedora 29 - Free - Test Updates 13 kB/s | 36 kB 00:02 RPM Fusion for Fedora 29 - Free - Updates 60 kB/s | 112 kB 00:01 RPM Fusion for Fedora 29 - Free 778 kB/s | 759 kB 00:00 faad2-libs.x86_64 1:2.8.8-2.fc29 rpmfusion-free libaacs.x86_64 0.9.0-5.fc29 rpmfusion-free libbdplus.x86_64 0.1.2-6.fc29 rpmfusion-free libmpeg2.x86_64 0.5.1-16.fc29 rpmfusion-free opencore-amr.x86_64 0.1.5-5.fc29 rpmfusion-free vo-amrwbenc.x86_64 0.1.3-8.fc29 rpmfusion-free [root@localhost ~]# dnf update Last metadata expiration check: 0:00:54 ago on Sat 01 Dec 2018 09:05:08 AM EST. Dependencies resolved. Nothing to do. I would assume DNF would update the 6 files from rpm-fusion ?? Thanks

2 1