users December 2017

users@lists.fedoraproject.org

106 participants
85 discussions

Install on Zotac Zbox CI327?
by wwp 11 Dec '18

11 Dec '18

Hello there, (after a looong time not using Fedora, just back to it!) I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron N3450 inside) but this happens to fail. I've tried F25 but it has not the right kernel to make it (I've read about 4.10 minimum), then tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could reach the graphical login. They both boot, some steps take a lot of time and I end up in a state I don't understand but which is not friendly ;-). Here's a link to a rdsosreport.txt file generated using Rawhide, I must admit that I don't know what to do now.. https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRLiv… BTW, I could install and run a Ubuntu 17.10 daily (artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly - and that gave me hope! Any hint or experience w/ such hardware? Regards, -- wwp

2 3

How to turn on networking from rescue boot
by vendor＠billoblog.com 30 Oct '18

30 Oct '18

So... I did a "sudo dnf upgrade" and things seemed to do well. However, when I rebooted, it hangs on bootup with the statment "Holding until bootup processes complete" or something like that -- I'm doing this from memory. I tried with a couple of older kernels, but they also hung. I assume that this is some transient thing associated with the upgrade. Over the years, I've had glitches appear on an upgrade and disappear on the next upgrade. Accordingly, I'd like to boot into rescue mode and see if I can upgrade again. However, I've forgotten how to turn on wifi networking from rescue mode. Can anybody point me to a tutorial? Thanks, billo

6 5

suspends shutdowns system instead of suspending
by Sudhir Khanger 21 Jul '18

21 Jul '18

Hi, A new bug has cropped up on my system Dell Precision 5510 running Fedora 25 Plasma Desktop. Anytime I suspend my device it shutdowns and obviously I lose all my unsaved work. I have tried all the kernel currently installed on my system 4.10.10-200.fc25.x86_64, 4.10.9, and 4.10.8. I have also tried downgrading systemd to systemd-231-10.fc25.x86_64. I continue to have the problem. sysinfo - https://paste.fedoraproject.org/paste/9nY1-YH4IKXt4wJhyIbMGV5M1UNdIGYhyRLiv… dmesg - https://paste.fedoraproject.org/paste/WK2NAqy3PRxrR6Fze2baIl5M1UNdIGYhyRLiv… What I can do to troubleshoot the problem?

8 17

Fonts in F27
by Gordon Messmer 11 May '18

11 May '18

After upgrading to F27, I noticed that fonts looked "off". I made a screenshot of Thunderbird and gnome-terminal displaying roughly identical contents on Fedora 25, 26, and 27. The older two releases are identical, but F27's fonts (both fixed-width and variable-width) appear to be the same width as they were previously, but taller. Characters like monospace 'o' used to be round and are now oblong. Everything seems slightly heavier as a result of the additional pixels. Does anyone know if this change was intentional? Personally, I think it's worse than before.

5 6

F26 update: gnome-terminal doesn't launch; locale issues
by Mike Zingale 07 May '18

07 May '18

I just did an update from F25 to F26 via dnf. After it boots, I can no longer start gnome terminal (nothing shows). If I ssh into the machine and try it remotely, I see the following: $ gnome-terminal (process:3586): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached So it looks like there is a locale issue in my update. Does anyone know how to fix this?

2 2

how to correctly log without journald (and its blobs)?
by Franta Hanzlík 09 Apr '18

09 Apr '18

In previous Fedora distros was (IMHO) right way to log only to syslog, without journald and its (for me) unwanted annoying binary logs, by using configuration as: *) Set systemd log target to syslog: systemd.log_target=syslog (syslog-or-kmsg) ---- on kernel cmdline systemd.default_standard_output=syslog --/ and LogTarget=syslog ---- in systemd.conf DefaultStandardOutput=syslog --/ *) configuring rsyslog to listen on /dev/log unix socket: $SystemLogSocketName /dev/log ------ in rsyslog.conf $ModLoad imuxsock ----/ $OmitLocalLogging off ---/ $AddUnixListenSocket /run/systemd/journal/syslog --/(legacy directives) $AddUnixListenSocket /run/systemd/journal/socket -/ $AddUnixListenSocket /run/systemd/journal/stdout / (not sure when all last three directives needed) *) prevent to run journald: systemctl mask systemd-journald.service (and maybe mask systemd-journal-flush.service) And it works fine. But in actual Fedora 24 in systemd man page values syslog-or-kmsg and syslog are missing in LogTarget option. As systemd/journald man pages say hardly anything about exact mean of appropriate configuration for this purpose, then please when someone more knowledgeable can advise: - where to direct the systemd output? Maybe to kmsg an then read it in rsyslog via imklog? (rsyslog should have also imkmsg module, but is not in rsyslog-8.12.0-3.fc24) - what about /run/log/journal/.../system.journal ? On my test F24 system it have open rsyslogd, abrt-dump-journal-oops and abrt-dump-journal-xorg (no need for these last two) processes. Uses it also something else? - what about /run/systemd/journal/{dev-log,socket,stdout} unix sockets? Should rsyslogd listen on them? - /dev/log seems be now symlink to /run/systemd/journal/dev-log socket (as defined by systemd-journald-dev-log.socket) Should it be left (because now something sends to /run/systemd/journal/dev-log), or can be /run/systemd/journal/dev-log removed? Thanks in advance for some clarification about this. Franta Hanzlik

5 14

how to (re-?)construct grub menu?
by William 22 Feb '18

22 Feb '18

Good afternoon, I found out the rather hard way what caused those boot failure problems that were the subject of a threat starting last month. After my weekly "dnf upgrade" last Thursday, I checked my root e-mail, and found the hard drive had 8 bad sectors, then 16 bad sectors. A smartctl short test showed several parameters "pre-fail", and the others "old-age". I obtained a new drive. My Cray Research friend gave me a USB stick with "Clonezilla-Live-Version" on it. That duplicated the old hard drive onto the new one, but apparently not 100%. After the old drive was removed and the new drive installed, I could not boot. The system was being put into a grub shell(?). (It displayed the "grub> " prompt.) After beating out heads against the wall (or the phone), my Cray research friend gave me another USB stick with "Boot-Repair-Disk" on it. That rebuilt a grub file, but not correctly. But at least I got a grub menu when booting, and I was able to edit the shell that the grub menu entry would run. I had to take the "efi" off the commands "linuxefi" and "initrdefi". That allows me to boot up Fedora. But the menu is missing an entry for windows, and I still have to edit that script every time. I want the grub menu to offer the three most recent patches of Fedora, the most recent Fedora rescue shell, and windows-7, in that order. (This is a dual-boot system.) And I want the shells launched by the menu entries to be correct. How do I get that accomplished - the correct Fedora-25 way? If it matters, the motherboard uses UEFI bios. Thank-you in advance. Bill.

11 60

Old peeve still in 27
by Beartooth 19 Jan '18

19 Jan '18

Is it me?? I keep three or four PCs on my desk (behind a Trendnet KVM switch), plus other machines elsewhere; the desk trio are all running F 27, Mate/Compiz. One old bad thing and a similar new one, irritating at best, are happening. The old one is that the size of my Mate Terminal, particularly its font, often changes when I reboot. So I have to re-edit half a dozen profiles before I can use them: the new size is usually either eye- splittingly small to read, or so big that no ordinary sentence will stay on a single line. The new and worse one is that the same thing has started happening to my panels. (I keep four, with lots of launchers on each.) Enlarging a panel makes several launchers disappear; as it is, I have to keep a couple smaller than I like in order to make stuff fit. If something in my configs is doing this, what, and how can I fix it? If it's Fedora, let me know what more data to supply, please! -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

4 7

F27 - fail2ban not adding iptables chains
by John Horne 09 Jan '18

09 Jan '18

Hello, I recently upgraded my PC from F26 to F27, and noticed that fail2ban was not adding the configured chains to iptables. This worked fine at F26. There are no error messages in the log files (dmesg, /var/log/messages, /var/log/fail2ban.log). I have tried disabling SELinux, then restarting fail2ban but the chains still do not appear. I do not use firewalld so removed the fail2ban-firewalld package. I set the fail2ban log level to debug, and that showed the relevant iptables commands that would add the chains, but otherwise gave no indication of any error. (I used the logged iptables commands to manually add the chains, and all the commands worked fine.) If I log (using logger) appropriate log messages - such as an SSH failed authentication attempt - then that particular chain does appear in iptables. If I unban the logged IP address, then the chain remains in iptables. If I restart fail2ban, then the chain is no longer in iptables. I'm now a bit stumped as to what might be the problem. Anyone any ideas? Thanks, John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

1 1

Failure with Intel wireless on Dell XPS 17
by Go Canes 09 Jan '18

09 Jan '18

After a dnf update today, I was unable to bring up my normal wireless connection on a Dell XPS 17 laptop. I was able to get a connection via my cellphone, and did a "dnf downgrade iwl*-firmware NetworkManager*", and after a reboot I am back online. From info in /var/log/messages, it looks like the relevant firmware packages are iwl7260-firmware-1:25.30.13.0-76.fc25.noarch which was downgraded to iwl7260-firmware-1:25.30.13.0-68.fc25.noarch. I'm happy to open a bugzilla if there isn't one on this issue, but it seems to me I should have more info than what I posted above, and so am looking for advice/guidance from the list. Thanks in advance!

2 2

← Newer
1
2
3
4
5
6
7
8
9
Older →