users April 2020

users@lists.fedoraproject.org

133 participants
180 discussions

Re: BIND 9.16
by David 29 Apr '20

29 Apr '20

I have nunerous Linux newbie questions, just using "bind" as a package example. The new 9.16 test-version of "bind" is considered "upstream.". Right ? Is 9.17 "further upstream" ? What factors will play out by the person choosing to replace the current version of "bind" in the Rawhide repo" with a later version ? Will that version be latest 9.16 described in the author's email. I am assuming that the author of the email, Mr. Menšík, is not the bind package-manager in Fedora. And finally, what would happen in Fedora 32, for "bind" to get a point-relase update ? Any helpful insights related to packaging procedures for newbies would be of interest. I have no clue what one does to compile a or build a package. David Locklear

5 6

AAUGH! More "helpful" software!
by Tom Horsley 29 Apr '20

29 Apr '20

I try to shutdown my new fedora 32 virtual machine. It immediately says: "Installing updates, do not turn off" AAAAAAUGH! I don't want to install frigging updates (yet). How do I reinstall fedora and turn this crap off before I shutdown the next time?

14 25

"dnf upgrade" crashing machine
by George Avrunin 29 Apr '20

29 Apr '20

Fedora 31, fully upgraded (I think...) Summary: twice in the last three days (since getting kernel 5.6.6, though I have no idea if that's related), this machine has hung completely after running "sudo dnf upgrade" while logged in over ssh. It becomes completely unresponsive to the network and to the keyboard, mouse, etc., I go to it to reboot. I've had to use the power button. The only strange things I see in the logs are long strings of null characters (that show as ^@) in the dnf.log when the dnf transactions crash the machine. Here are more details. This is a Dell Precision T1700 that is my university office workstation as well as a IMAP server and web server for my use. Since we're working remotely and discouraged from going on campus, I hadn't been to the office since March 16, but in addition to reading and sending mail, I've been putting stuff on my course web pages, etc., as well as doing regular "sudo dnf upgrade" runs. I got kernel 5.6.6 on Saturday, April 25. On Sunday, I did a dnf upgrade on my home machine, which is almost identically configured to the one in my office. That upgraded some git stuff, python3, samba, webkit2gtk3, etc., a total of 24 packages. That went fine, so I logged into my office machine and did dnf upgrade there. It offered pretty much the same list of packages, I say "y" and did work in another virtual desktop for a while. Then I got an error message saying claws-mail couldn't connect to the account on my office machine. It was dead to the network--I logged in on another machine in our department network and still couldn't connect to my office one. Eventually, I went to campus. The machine was unresponsive and I had to push the power button to get it to fully shut down. It then rebooted apparently normally, and ran fine. I didn't have time then to investigate very carefully, but I didn't see anything in the journalctl output that indicated what the problem was--there was just a complete gap in entries from the dnf transaction to when I rebooted. The next day (yesterday) dnf upgrade worked normally and upgraded 6 packages: darktable, libmwaw, libstaroffice, libwps, openvpn, and python3-click-7.1.1-1.fc31.noarch. Today, I did an upgrade on the home machine again, successfully, and then on the office machine. It offered to upgrade akmods-wireguard, which I realized I should have removed (since wireguard is in the 5.6 kernel). So I removed it and then did the upgrade. dnf wanted to upgrade google-chrome-stable, kde-print-manager and kde-print-manager-libs, libappindicator, libappindicator-gtk3, libuv, some net-snmp stuff, and python[23]-beautifulsoup4, all of which had been upgraded successfully on the home machine. I said yes and it did some deltarpm stuff, downloaded a couple of things, and then apparently froze completely, just like the last time. Again, I had to go in to the office and use the power button to shutdown and restart. But now it seems ok and the rpms that it was supposedly upgrading do seem to have been upgraded--they're at the same versions as on my home machine. I don't see anything very strange in any of the logs. Both times, the basic journalctl output just stops and doesn't start again until I reboot. However, in the dnf.log file after both of the bad upgrade transactions started, there are long strings of null characters (150 or so). These don't show up in the dnf.log on the home machine that has upgraded fine. I've run fsck and rpm -V. There's plenty of disk space available in all partitions. I don't have any idea what's going on and it's very inconvenient (not to mention strongly discouraged by the powers that be) to have to keep going on campus to restart the machine. So I'd be very grateful for suggests about how to figure this out, or at least stop it from happening again. Thanks. George

4 6

franz on Fedora?
by Ranjan Maitra 29 Apr '20

29 Apr '20

Hi, I have been looking around and was wondering if franz exists on Fedora 31? https://github.com/meetfranz/franz There is talk of an rpm in one of the issues, but I can not find how it got resolved: https://github.com/meetfranz/franz/issues/647 Ranjan

6 16

Switching desktops on Fedora 32
by Alan 29 Apr '20

29 Apr '20

Seems the GDM option to switch desktops has been removed on Fedora 32. switchdesk no longer works either. How do you switch desktops on Fedora 32? It has become non-obvious.

3 3

Can I put Fedora on this?
by Richard Shaw 29 Apr '20

29 Apr '20

https://www.zdnet.com/article/raspberry-pi-alternative-new-odroid-c4-underc… Thanks, Richard

2 1

gdk-pixbuf-2.40.0 Build Errors
by Thomas Dineen 28 Apr '20

28 Apr '20

GentlePeople: I am trying to build gdk-pixbuf-2.40.0 out of the box. The directions require the use of meson and ninja, my first experience with both! I am on a Fedora 30 X86 Host, and I want to cross compile to i686 for Windows. I am using the cross tools provided by the Fedora distribution /usr/i686-w64-mingw32. The i686-w64-mingw32 cross compiler dose work on Hello.c, independant of meson's opinion shown below. The Error Messages, Cross File, and Error Log File are presented below: Q1) Why dose meson say "Is cross compiler: False."? Q2) Why dose the sanity check fail? Q3) Please show me the correct Cross File for Cross Compiling to i686 Windows and X86 Windows. I am suffering from google whiplash from internet searching issue and multiple opinions. Q4) Why meson why not configure make? ; ; The Project ; F30-VM% pwd /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0 meson _build . --cross-file ./i686_Cross_File --prefix /usr/i686-w64-mingw32/sys-root/mingw --libdir /usr/i686-w64-mingw32/sys-root/mingw/lib --bindir /usr/i686-w64-mingw32/sys-root/mingw/bin --includedir /usr/i686-w64-mingw32/sys-root/mingw/include The Meson build system Version: 0.52.0 Source dir: /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0 Build dir: /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build Build type: cross build Project name: gdk-pixbuf Project version: 2.40.0 C compiler for the build machine: cc (gcc 9.3.1 "cc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)") C linker for the build machine: GNU ld.bfd 2.31.1-37 000b:fixme:winediag:__wine_start_process Wine Staging 5.0 is a testing version containing experimental patches. 000b:fixme:winediag:__wine_start_process Please mention your exact version when filing bug reports on winehq.org. 002b:err:module:__wine_process_init L"Z:\\home\\tdineen\\gdk-pixbuf-2\\gdk-pixbuf-2.40.0\\_build\\meson-private\\sanitycheckc_cross.exe" not supported on this system meson.build:1:0: ERROR: Executables created by c compiler /usr/bin/i686-w64-mingw32-gcc are not runnable. A full log can be found at /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-logs/meson-log.txt F30-VM% ; ; Cross File ; more i686_Cross_File [host_machine] system = 'windows' cpu_family = 'x86' cpu = 'i686' endian = 'little' [properties] c_args = [] c_link_args = [] [binaries] c = '/usr/bin/i686-w64-mingw32-gcc' cpp = '/usr/bin/i686-w64-mingw32-g++' ar = '/usr/bin/i686-w64-mingw32-ar' strip = '/usr/bin/i686-w64-mingw32-strip' pkgconfig = '/usr/bin/i686-w64-mingw32-pkg-config' windres = '/usr/bin/i686-w64-mingw32-windres' exe_wrapper = 'wine' ; ; Error Log: ; vi /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-logs/meson-log.txt Build started at 2020-04-28T13:16:40.677565 Main binary: /usr/bin/python3 Build Options: -Dprefix=/usr/i686-w64-mingw32/sys-root/mingw -Dbindir=/usr/i686-w64-mingw32/sys-root/mingw/bin -Dincludedir=/usr/i686-w64-mingw32/sys-root/mingw/include -Dlibdir=/usr/i686-w64-mingw32/sys-root/mingw/lib '--cross-file ./i686_Cross_File' Python system: Linux The Meson build system Version: 0.52.0 Source dir: /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0 Build dir: /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build Build type: cross build Project name: gdk-pixbuf Project version: 2.40.0 No CFLAGS in the environment, not changing global flags. No LDFLAGS in the environment, not changing global flags. No CPPFLAGS in the environment, not changing global flags. Sanity testing C compiler: cc Is cross compiler: False. Sanity check compiler command line: cc /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc.c -o /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc.exe -pipe -D_FILE_OFFSET_BITS=64 Sanity check compile stdout: ----- Sanity check compile stderr: ----- Running test binary command: /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc.exe C compiler for the build machine: cc (gcc 9.3.1 "cc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)") C linker for the build machine: GNU ld.bfd 2.31.1-37 Sanity testing C compiler: /usr/bin/i686-w64-mingw32-gcc Is cross compiler: True. Sanity check compiler command line: /usr/bin/i686-w64-mingw32-gcc /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc.c -o /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc_cross.exe -pipe Sanity check compile stdout: ----- Sanity check compile stderr: ----- Running test binary command: /usr/bin/wine /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc_cross.exe meson.build:1:0: ERROR: Executables created by c compiler /usr/bin/i686-w64-mingw32-gcc are not runnable. 38,1 Bot ----- Sanity check compile stderr: ----- Running test binary command: /usr/bin/wine /home/tdineen/gdk-pixbuf-2/gdk-pixbuf-2.40.0/_build/meson-private/sanitycheckc_cross.exe meson.build:1:0: ERROR: Executables created by c compiler /usr/bin/i686-w64-mingw32-gcc are not runnable. 38,1 Bot

2 1

Files: folder and file names not visible since upgrade to f31.
by home user 28 Apr '20

28 Apr '20

(f31, gnome) Starting with the upgrade to f31 earlier this month. "Files" (Nautilus) no longer displays names of folders and files. I have made a screen capture available here: "https://drive.google.com/file/d/1hh_G48m8bm-XWwMIR3mA_jJp9CJ75SvC/view?usp=…". I have done 2 weekly patches since the upgrade; the problem persists. I've checked the man page, and the web page referenced by the man page. No clues. I've checked the preferences; there is nothing there that would affect this. I've checked the "Help". Nothing relevant. I've checked the instructions for upgrading to f31; nothing relevant. How did upgrading to f31 break this, and how do I make the folder/file names visible?

4 10

Tip: dhcp lease file under Fedora32
by ToddAndMargo 28 Apr '20

28 Apr '20

Hi All, Tip: by default the dhcp leases file does not exist under Fedora32. You have to create it firs, then it gets uses -T My notes: DHCP Client leases file: The file does not exist by default. # New to Fedora 32. Set up a leases file if it does not exist: if [ -n /var/lib/dhclient/dhclient.lease]; then touch /var/lib/dhclient/dhclient.lease; # release DHCP address dhclient -r # renew DHCP address dhclient fi

8 33

dnf list color bad
by Beartooth 28 Apr '20

28 Apr '20

I'm running F31 Mate. Today all of a sudden on all four machines on my desk, the list that dnf gives me of what it proposes to do is an unreadable chartreuse color. Could this be something I've done?? How do I fix it? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

7 16

← Newer
1
2
3
4
5
6
7
...
18
Older →

Jump to page: