Windows/QXL/Spice virtual machine suddenly unusable?
by Tom Horsley
I suspect I have to blame this on Windows 10 somehow
because it is only the Windows 10 virtual machine that
is screwed up, but when I tried to use it today,
the mouse pointer was just horrible. Flickering
on an off, leaving little images of itself when I try
to move it, disappearing completely when I get close
to something I want to click on.
Anyone ever seen this in a Windows virtual machine
and know how to fix it?
This is on a fully updated Fedora 24 host, and the
Windows 10 machine is also fully updated. An old Windows
XP KVM as well as a Centos KVM operate totally
smoothly, no pointer problems at all.
7 years, 9 months
httpd fails to start
by David A. De Graaf
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.
7 years, 9 months
Re: Fascinating mailing list bug
by Richard
> Date: Saturday, July 02, 2016 13:46:19 -0700
> From: jdow <jdow(a)earthlink.net>
>
. . .
> I looked at the headers of one of the updates emails and found this
> sequence:
> ===8<---
. . .
> List-Unsubscribe:
> <https://lists.fedoraproject.org/admin/lists/package-announce@lists
> .fedoraproject.org>,
> <mailto:package-announce-leave@lists.fedoraproject.org>
> ===8<---
>
> So I dutifully emailed
> mailto:package-announce-leave@lists.fedoraproject.org.
>
> ===8<---
> To: "mailto:package-announce-leave"@lists.fedoraproject.org
> From: jdow <jdow(a)earthlink.net>
> Subject: unsubscribe
>
> unsubscribe
> ===8<---
>
> That was apparently the wrong thing to do. I got this in reply:
>
> ===8<---
> <"mailto:package-announce-leave"@lists.fedoraproject.org>: host
> mailman01.vpn.fedoraproject.org[192.168.1.118] said: 550 5.1.1
> <mailto:package-announce-leave@lists.fedoraproject.org>:
> Recipient address
> rejected: User unknown in local recipient table (in reply to
> RCPT TO
> command)
> ===8<---
>
> Either correct your headers, make lists.fedoraproject.org grow the
> proper username, or otherwise rectify your error before one loses
> her basic faith in the integrity of RedHat's basic bug elimination
> 101 abilities.
>
> Shame on you.
>
No bug here. "mailto" is the URI for email addresses (just as "http"
is for urls). The problem was your including that as part of the
address you were sending to. From the information provided, the
correct address is (simply):
package-announce-leave(a)lists.fedoraproject.org
Email clients and web browsers understand the "mailto" URI and handle
things automatically. When doing a copy/paste you simply need to
strip the mail URI.
7 years, 9 months
Fascinating mailing list bug
by jdow
After some years of no activity the packages list came alive with a noisier than
LKML level of messages. So I decided to vanish from the list.
I looked at the headers of one of the updates emails and found this sequence:
===8<---
List-Id: Fedora Package Announcements <package-announce.lists.fedoraproject.org>
Archived-At:
<https://lists.fedoraproject.org/archives/list/package-announce@lists.fedo...>
List-Archive:
<https://lists.fedoraproject.org/archives/list/package-announce@lists.fedo...>
List-Help: <mailto:package-announce-request@lists.fedoraproject.org?subject=help>
List-Post: <mailto:package-announce@lists.fedoraproject.org>
List-Subscribe:
<https://lists.fedoraproject.org/admin/lists/package-announce@lists.fedora...>,
<mailto:package-announce-join@lists.fedoraproject.org>
List-Unsubscribe:
<https://lists.fedoraproject.org/admin/lists/package-announce@lists.fedora...>,
<mailto:package-announce-leave@lists.fedoraproject.org>
===8<---
So I dutifully emailed mailto:package-announce-leave@lists.fedoraproject.org.
===8<---
To: "mailto:package-announce-leave"@lists.fedoraproject.org
From: jdow <jdow(a)earthlink.net>
Subject: unsubscribe
Message-ID: <a35cdcb5-a8c3-d3eb-f876-d8d5346d2124(a)earthlink.net>
Date: Sat, 2 Jul 2016 13:34:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace:
bb89ecdb26a8f9f24d2b10475b571120570d22d52f4c61f59279cb3af55292e2d8ba5666b9b3d6db350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.183.58.6
unsubscribe
===8<---
That was apparently the wrong thing to do. I got this in reply:
===8<---
This is the mail system at host smtp-mm-ib01.fedoraproject.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<"mailto:package-announce-leave"@lists.fedoraproject.org>: host
mailman01.vpn.fedoraproject.org[192.168.1.118] said: 550 5.1.1
<mailto:package-announce-leave@lists.fedoraproject.org>: Recipient address
rejected: User unknown in local recipient table (in reply to RCPT TO
command)
===8<---
Either correct your headers, make lists.fedoraproject.org grow the proper
username, or otherwise rectify your error before one loses her basic faith in
the integrity of RedHat's basic bug elimination 101 abilities.
Shame on you.
{o.o}
7 years, 9 months
Intel Core i5-6200U laptop issue
by Richard Shaw
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/jh...
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
7 years, 9 months
Nouveau, Oh No!
by Tom Horsley
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).
7 years, 9 months
Marching 5's again
by Jon LaBadie
Has there been any resolution to the "marching 5's" syndrome?
As I recall it seemed to be kernel release specific.
After 6-9 months of no extraneous 5's, I've got the problem
again on F22 with kernel 4.4.13-200.
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
7 years, 9 months
Cannot ping6
by Juan Orti Alcaine
Hi,
I'm having a network problem with my Fedora 24 Workstation. I cannot
ping6 other hosts in the same LAN or on the Internet because it fails
with Address unreachable. From other machine in the same LAN (F24
Server) it works fine. In the tcpdump I have the impression that the
neighbor solicitations don't succeed. The IPv6 is otherwise working
fine as I can do browsing, P2P and everything on it.
I'm going to show you my tests to see if anyone can give me any hint.
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
master br-lan state UP group default qlen 1000
link/ether f4:6d:04:61:ab:b4 brd ff:ff:ff:ff:ff:ff
3: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether f4:6d:04:61:ab:b4 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.100/24 brd 192.168.10.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 2001:470:7950:10::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::108f:1ae:a4ba:a348/64 scope link
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0
valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state
DOWN group default qlen 1000
link/ether 52:54:00:6e:af:89 brd ff:ff:ff:ff:ff:ff
$ ip -6 r
2001:470:7950:10::/64 dev br-lan proto kernel metric 256 pref medium
fe80::/64 dev br-lan proto kernel metric 256 pref medium
default via 2001:470:7950:10::1 dev br-lan proto static metric 425
pref medium
# brctl show
bridge name bridge id STP enabled interfaces
br-lan 8000.f46d0461abb4 yes enp5s0
virbr0 8000.000000000000 yes
# firewall-cmd --list-all
FedoraWorkstation (default, active)
interfaces: br-lan enp5s0
sources:
services: dhcpv6-client mdns samba samba-client ssh
ports: 5298/tcp 1900/udp 8333/tcp 8200/tcp
protocols:
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
$ ping6 -n www.google.com
PING www.google.com(2a00:1450:4003:808::2004) 56 data bytes
From 2001:470:7950:10::100 icmp_seq=1 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=2 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=3 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=4 Destination unreachable: Address
unreachable
^C
--- www.google.com ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
$ ping6 -n gateway
PING gateway(2001:470:7950:10::1) 56 data bytes
From 2001:470:7950:10::100 icmp_seq=1 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=2 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=3 Destination unreachable: Address
unreachable
From 2001:470:7950:10::100 icmp_seq=4 Destination unreachable: Address
unreachable
^C
--- gateway ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
This is a tcpdump while the ping was running:
# tcpdump -n -i br-lan icmp6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
15:41:54.990240 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:41:55.992056 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:41:56.994060 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:41:57.643074 IP6 fe80::5054:ff:fee1:2f75 > 2001:470:7950:10::100:
ICMP6, neighbor solicitation, who has 2001:470:7950:10::100, length 32
15:41:57.643148 IP6 2001:470:7950:10::100 > fe80::5054:ff:fee1:2f75:
ICMP6, neighbor advertisement, tgt is 2001:470:7950:10::100, length 24
15:41:58.991235 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:41:59.992058 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:42:00.994060 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:42:02.660074 IP6 fe80::108f:1ae:a4ba:a348 >
fe80::5054:ff:fee1:2f75: ICMP6, neighbor solicitation, who has
fe80::5054:ff:fee1:2f75, length 32
15:42:02.660497 IP6 fe80::5054:ff:fee1:2f75 >
fe80::108f:1ae:a4ba:a348: ICMP6, neighbor advertisement, tgt is
fe80::5054:ff:fee1:2f75, length 24
15:42:02.992244 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
15:42:03.994060 IP6 2001:470:7950:10::100 > ff02::1:ff00:1: ICMP6,
neighbor solicitation, who has 2001:470:7950:10::1, length 32
^C
12 packets captured
12 packets received by filter
0 packets dropped by kernel
Thank you.
--
Juan Orti
https://apuntesderootblog.wordpress.com/
7 years, 9 months