Re: Sound-setup with alsa and pulseaudio [was: Re: pulseaudio MUST DIE!]

2017-11-25 Thread Mike Wright
On 11/24/2017 01:02 PM, Wolfgang Pfeiffer wrote: Doug, Philip, and Everyone I started a new thread with the quotes below to make sure to not hijack the thread where they were taken from ... Short version: The whole thing isn't that important - if in doubt, ignore it ... :) The main reason I

Re: AH01257: unable to connect to cgi daemon after multiple tries

2017-11-25 Thread Richard Shaw
I know you got your workaround in place by changing back to prefork MPM but just an FYI, I've filed an issue upstream to see if it can be fixed properly... https://github.com/backuppc/backuppc/issues/170 Thanks, Richard ___ users mailing list --

Re: systemctl openvpn won't start

2017-11-25 Thread Neal Becker
Ulf Volmer wrote: > On 23.11.2017 13:34, Neal Becker wrote: > >> sudo systemctl enable openvpn-client@ibecker2.service >> Failed to enable unit: Unit file openvpn-client@ibecker2.service does not >> exist. > > interesting. Could you post the output of > > rpm -ql openvpn|grep service > > best

Cursor lagging and freezing on MacBook Pro

2017-11-25 Thread Joakim Forøysund
Hi! I pulled out my MacBook Pro from back in 2008 and installed F26 on it. It worked fine the first couple of days (except from wifi), but then the cursor started lagging and freezing up. I can move it slowly about an inch on the screen before it freezes. Then I can wait a couple of seconds and

Re: cups-browsed regression?

2017-11-25 Thread David A. De Graaf
On 11/25/17 11:20, Richard Shaw wrote: On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf > wrote: I've freshly installed Fedora 27 on two machines;  neither have a printer directly connected, but rely on cups-browsed to display the LAN's

Re: Core XFCE utils freezing up

2017-11-25 Thread Konstantin Svist
On 11/21/2017 09:22 AM, Konstantin Svist wrote: > Hi, > > Since last update I've been seeing freezing up behavior, mostly in the > xfce4-power-manager. > > Specifically, this is the behavior I see when starting it up in command > line ($ xfce4-power-manager --no-daemon --debug --dump): >

Re: Sound-setup with alsa and pulseaudio [was: Re: pulseaudio MUST DIE!]

2017-11-25 Thread Wolfgang Pfeiffer
On Sat, 25 Nov 2017 07:32:53 +0800 Ed Greshko wrote: > On 11/25/17 05:02, Wolfgang Pfeiffer wrote: > >[ ... ] namely to feed > > sound on a Linux machine to two audio systems at the same time: to > > internal speakers on the computer and to external ones like, e.g., > >

Re: cups-browsed regression?

2017-11-25 Thread Richard Shaw
On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf wrote: > I've freshly installed Fedora 27 on two machines; neither have a printer > directly connected, but rely on cups-browsed to display the LAN's printers > that are attached to, and managed by other (F26) machines. > > Not

Re: docker update errors with recently upgraded f27 system

2017-11-25 Thread John Mellor
On Sat, 2017-11-25 at 06:29 -0500, Robert P. J. Day wrote: > just did a full upgrade to fedora 27 a few days ago, first couple > updates worked fine, then this .. thoughts? should i just wait for > upstream to fix itself? > > > Problem 1: cannot install the best update candidate for package >

Re: docker update errors with recently upgraded f27 system

2017-11-25 Thread Robert P. J. Day
On Sat, 25 Nov 2017, Ed Greshko wrote: > What do you get when you add  '--best --allowerasing' to command > line to force their upgrade? that did it, thank you kindly. rday -- Robert P. J. Day

Re: docker update errors with recently upgraded f27 system

2017-11-25 Thread Ed Greshko
On 11/25/17 19:29, Robert P. J. Day wrote: > just did a full upgrade to fedora 27 a few days ago, first couple > updates worked fine, then this .. thoughts? should i just wait for > upstream to fix itself? > > > Problem 1: cannot install the best update candidate for package >

docker update errors with recently upgraded f27 system

2017-11-25 Thread Robert P. J. Day
just did a full upgrade to fedora 27 a few days ago, first couple updates worked fine, then this .. thoughts? should i just wait for upstream to fix itself? Problem 1: cannot install the best update candidate for package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 - nothing provides