users June 2016

users@lists.fedoraproject.org

137 participants
129 discussions

httpd fails to start
by David A. De Graaf 03 Jul '16

03 Jul '16

On a newly installed F24 I have a /home/... directory with a collection of movie files - *.m4v and such, that I want to googlecast to a TV for viewing. I've configured a private httpd setup to display this directory listing when the local machine name is entered in the address line of google-chrome, and when a file is clicked, it plays and can be "cast" to the TV. Neat! However, when the machine boots (quiet, without rhgb) the messages include [FAILED] Failed to start The Apache HTTP Server. See 'systemctl status httpd.service' for details. and, sure enough, httpd isn't running. journalctl -b shows this: Jun 27 10:33:17 garfield httpd[1100]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 192.168.10.99:80 Jun 27 10:33:17 garfield httpd[1100]: no listening sockets available, shutting down Jun 27 10:33:17 garfield httpd[1100]: AH00015: Unable to open logs ... Jun 27 10:33:17 garfield systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE Jun 27 10:33:17 garfield systemd[1]: Failed to start The Apache HTTP Server. Jun 27 10:33:17 garfield systemd[1]: httpd.service: Unit entered failed state. Jun 27 10:33:17 garfield systemd[1]: httpd.service: Failed with result 'exit-code'. It can be started manually later, readily enough, with systemctl start httpd but that's a PITA. So, why could httpd not "make_sock: could not bind to address 192.168.10.99:80" Could it just be that the network isn't up yet? Why isn't httpd more patient and persistent? This seems like yet another systemd problem. Can anyone suggest how to fix this? -- David A. De Graaf DATIX, Inc. Hendersonville, NC dad(a)datix.us www.datix.us "Flint must be an extremely wealthy town: I see that each of you bought two or three seats." -Victor Borge, playing to a half-filled house in Flint, Mich.

5 8

Intel Core i5-6200U laptop issue
by Richard Shaw 02 Jul '16

02 Jul '16

I recently upgraded my wife's laptop to an Acer with a fairly stock i5-6200U system using the UFEI boot (that was an adventure) About a month ago I started getting strange issues. Not lockups per se but it seems that the drive is somehow going into read only. Since that's the case after it starts nothing is getting written to disk (includes journal entries). Also the virtual terminals are useless: https://lh4.googleusercontent.com/-L6zfYtxT5y8/V283nqZgbEI/AAAAAAAABys/jhiE… Interestingly enough, a program already open will kind of work but any attempt to launch a new program from gnome shell fails. Because of the lack of log entries this has been extremely difficult to troubleshoot. Any ideas? Thanks, Richard

3 12

Nouveau, Oh No!
by Tom Horsley 02 Jul '16

02 Jul '16

I was so happy when the nouveau driver finally worked on my nvidia maxwell card in fedora 24, but now after about a week, this happened: https://bugzilla.redhat.com/show_bug.cgi?id=1351286 Total screen freeze :-(. At least it took as long as a week. If it happens a lot, I may have to go back to nvidia binaries (I hate the pain of installing them).

11 15

[OT] Tim, Gil, et. al. (e-mail address settings)
by Joel Rees 01 Jul '16

01 Jul '16

To keep this off-list as much as possible, the rant is here: http://reiisi.blogspot.com/2016/07/to-gil-tim-fedora-et-al.html (The blame lies elsewhere. I wish I had the network and social cred to get a real movement started, away from the current faceless CA system and towards a different identity assurance system that depends on actual, existing day-to-day trust relationships.)

8 12

No akmod nvidia yet in rpmfusion?
by Tom Horsley 30 Jun '16

30 Jun '16

I had to back up one kernel release to get kmod-nvidia to work :-(. The rpmfusion repos don't seem to have an akmod-nvidia package for fedora 24.

2 3

Sound card Focusrite Scarlett 2i2 not working after update to F24
by Matthew Colton 30 Jun '16

30 Jun '16

Hi all, as the subject says my sound card stopped working after the update to F24. The sound card worked like a charm in F22 and F23. Now the situation is as following: After booting the card is NOT listed by lsusb, yet the LED auf the 2i2 is on. After replugging the device it is listed by lsusb: Bus 001 Device 011: ID 1235:8016 Focusrite-Novation Now it gets wierd. As long as I do NOT log into a desktop session the card works fine in the console and is listed by lsusb. The card is selected in alsamixer and aplay works as expected. The card works and audio files can be played. As soon as I log in to a desktop session (standard GNOME in my case) the sound card doesn't work. Seems to be some kind of a pulseaudio problem. It is still selected in alsamixer, but not available in pacmd list-sinks: ******************************************** 1 sink(s) available. * index: 1 name: <auto_null> driver: <module-null-sink.c> flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 1000 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 344 KiB max rewind: 344 KiB monitor source: 2 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms module: 26 properties: device.description = "Dummy-Ausgabe" device.class = "abstract" device.icon_name = "audio-card" ******************************************** And aplay fails with: ******************************************** ALSA lib pcm_direct.c:1027:(snd1_pcm_direct_initialize_slave) unable to install hw params ALSA lib pcm_dmix.c:1041:(snd_pcm_dmix_open) unable to initialize slave aplay: main:786: Fehler beim Öffnen des Gerätes: Input/output error ******************************************** cat /proc/asound/cards ******************************************** 0 [USB ]: USB-Audio - Scarlett 2i2 USB Focusrite Scarlett 2i2 USB at usb-0000:00:1a.0-1.6, high speed ******************************************** "dmesg | grep usb" shows loads of USB errors, all the same, this is the last one after more than ten minutes after booting: ******************************************** [ 681.631063] usb 1-1.6: 1:1: usb_set_interface failed (-71) ******************************************** I'd be glad for any help Cheers, Mat

3 7

dnf update tries to install yum
by Walter Cazzola 30 Jun '16

30 Jun '16

Dear Experts, I've a Fedora 23 installed on my laptop and I keep it updated (even if I'm not going through the upgrade process yet). Yesteday when I checked which packages need to be updated, dnf proposed me to install this packages: Installing: yum noarch 3.4.3-507.fc23 fedora 1.2 M yum-metadata-parser x86_64 1.1.4-15.fc23 fedora 39 k yum-utils noarch 1.1.31-508.fc23 updates 117 k This sounds weird, as far as I know, dnf completely replaced yum so why I need to install it? Is this generating some conflicts with dnf or breaking something on my fedora? Walter --

4 6

F24: gnome crashing after nvidia driver install
by Kevin 29 Jun '16

29 Jun '16

Hi, After a fresh F24 install nouveau was freezing my screen intermittently so I removed it in favor of the nvidia drivers (367.27). It seems that Ive now traded one problem for another. With these divers in place and nouveau removed, gnome itself crashes and when it does the first message in the journal is: “X Error of failed request: BadMatch (invalid parameter attributes)”. Upon researching that error, all i could find was screen resolution issues but when gnome does start the resolution is fine. Has anyone else had this problem? https://paste.fedoraproject.org/385261/98226514 > nvidia-installer -v |grep version nvidia-installer: version 367.27 (buildmeister@swio-display-x64-rhel04-12) Thu Jun 9 19:24:47 PDT 2016 > uname -a Linux 4.5.7-300.fc24.x86_64 #1 SMP Wed Jun 8 18:12:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > lspci |grep -i VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) Thanks for you help Kevin

3 4

installing via VNC over ipv6
by Chris Murphy 29 Jun '16

29 Jun '16

This suggests installation using vnc over ipv6 is supported: https://fedoraproject.org/wiki/Anaconda/Features/Ipv6OnlyInstallation But when I use inst.vnc boot option, I get an text screen that says to connect to an ipv4 address, an ipv6 address isn't listed. When I go to a shell and use 'ip addr' there is a global ipv6 address, but no formatting for tigervnc I've come up with will connect, it won't connect: vncviewer.desktop[12590]: CConn: unable connect to socket: Invalid argument (22) If I boot Fedora 23 Server on this same hardware, the 'ip addr' address can be used successfully to ssh into the server, and also point a browser to https://[ipv6]:9090 to reach the Cockpit interface successfully. root 1744 0.0 0.9 251060 36468 pts/0 Sl+ 03:29 0:00 Xvnc :1 -depth 16 -br IdleTimeout=0 -auth /dev/null -once DisconnectClients=false desktop=Fedora rawhide installation on host 10.0.0.15 SecurityTypes=None rfbauth=0 I can't tell if -InTransports needs to explicitly specify ipv6 for it to work. But at this point I'm stumped and can't tell if it's user error or a bug. And netstat isn't on non-live media apparently so I don't have access to that while xvnc is running to see if it's listening over something other than just an ipv4 address. -- Chris Murphy

3 4

F24: Warning for Italian virt-manager users (broken it.po causes: KeyError: 'nome-mv' )
by Dario Lesca 29 Jun '16

29 Jun '16

See this: "broken it.po causes: KeyError: 'nome-mv'" https://bugzilla.redhat.com/show_bug.cgi?id=1350185 workaround: LANG=en_US.utf8 virt-manager -- Dario Lesca (inviato dal mio Linux Fedora 24 Workstation)

1 0