on Monday, July 10, Rick Stevens wrote:
> I'd suggest booting your system using a live CD (which will use nouveau)
> and see how it behaves. If it's OK, then simply comment out your
> blacklist stuff and rebuild grub to go back to nouveau.
After getting the system to boot from the May failures,
On 07/11/17 08:46, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>> I found that if I have ListenStream=192.168.1.198:5901 in my
>> xvnc.socket file I also get a failure on boot. I thought it could
>> have been due to my using DHCP on that VM. I changed it back to
>> ListenStream=5901. Can you try jus
On 07/10/2017 05:42 PM, CLOSE Dave wrote:
> On 07/10/17 17:32, Ed Greshko wrote:
>
>> Odd that you're getting an IPV6 error message. I don't have a global
>> IPv6 address and only show
>>
>> [egreshko@f25f system]$ ip address show enp0s3
>> 2: enp0s3: mtu 1500 qdisc fq_codel state
>> UP gro
Ed Greshko wrote:
> I found that if I have ListenStream=192.168.1.198:5901 in my
> xvnc.socket file I also get a failure on boot. I thought it could
> have been due to my using DHCP on that VM. I changed it back to
> ListenStream=5901. Can you try just having that?
The socket now reports that
On 07/11/17 08:42, CLOSE Dave wrote:
> On 07/10/17 17:32, Ed Greshko wrote:
>
>> Odd that you're getting an IPV6 error message. I don't have a global
>> IPv6 address and only show
>>
>> [egreshko@f25f system]$ ip address show enp0s3
>> 2: enp0s3: mtu 1500 qdisc fq_codel state
>> UP group
>>
On 07/10/17 17:32, Ed Greshko wrote:
> Odd that you're getting an IPV6 error message. I don't have a global
> IPv6 address and only show
>
> [egreshko@f25f system]$ ip address show enp0s3
> 2: enp0s3: mtu 1500 qdisc fq_codel state UP
> group
> default qlen 1000
> link/ether 08:00:27:15
Ed Greshko wrote:
> You have a line in the Service segment of "Type". I do not have that
> and it isn't in the original file in /lib/systemd/system. Did you
> add that?
Rick Stevens wrote:
> I believe "Type=simple" is the default if you have "ExecStart="
> defined, but it wouldn't hurt to add
On 07/11/17 08:18, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>>> HOWEVER, when I connect with "vncviewer server::5901", I get a blank
>>> screen with a momentary F8 prompt. I do not see the normal greeting
>>> screen. Something is still missing.
>> Then I noticed one thing which seems off or odd do m
On 07/10/2017 04:38 PM, Ed Greshko wrote:
> On 07/11/17 05:42, CLOSE Dave wrote:
>>
>> # cat /etc/systemd/system/xvnc@.service
>> [Unit]
>> Description=XVNC per Connection Daemon
>> After=syslog.target
>>
>> [Service]
>> Type=simple
>> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024
Ed Greshko wrote:
>> HOWEVER, when I connect with "vncviewer server::5901", I get a blank
>> screen with a momentary F8 prompt. I do not see the normal greeting
>> screen. Something is still missing.
> Then I noticed one thing which seems off or odd do me.
>
> When you do "systemctl -l status x
On 07/11/17 05:42, CLOSE Dave wrote:
>
> # cat /etc/systemd/system/xvnc@.service
> [Unit]
> Description=XVNC per Connection Daemon
> After=syslog.target
>
> [Service]
> Type=simple
> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768
> -depth 24 -once -SecurityTypes=None -fp /usr/s
On 07/11/17 05:42, CLOSE Dave wrote:
>
> This was caused because the old service, vncserver@:1, was still
> running. After I stopped it (and deleted the files, just to be sure),
> status looks correct.
>
> ---
>
> # systemctl -l status xvnc.socket
> xvnc.socket - XVNC Server
>Loaded: loaded (
I've filed a bug upstream.
https://bugzilla.gnome.org/show_bug.cgi?id=784770
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Ed Greshko wrote:
> You actually don't want xvnc@.service to be enabled or started. The
> connection to the socket triggers starting of Xvnc
I realized that a while ago but forgot. It is presently not enabled.
> I find it odd that you get this "Listen: 10.76.185.91:5901" when
> your file below
Hi All
I have a strange behaviour since upgrading from F24 to F25 a few days
ago: the mini display port on my laptop doesn't connect me anymore to
the external second screen, a TV monitor. This connection worked like a
charm on F24. And the mini display port cable is OK: I can see pre-login
messa
On 07/10/2017 10:23 AM, Rick Stevens wrote:
> On 07/08/2017 06:08 PM, Stephen Morris wrote:
>> On 7/8/17 4:43 AM, Rick Stevens wrote:
>>> On 07/07/2017 02:04 AM, Stephen Morris wrote:
On 7/6/17 8:50 AM, Rick Stevens wrote:
> On 07/05/2017 03:25 PM, Stephen Morris wrote:
>> On 6/24/17 4
On 07/08/2017 06:08 PM, Stephen Morris wrote:
> On 7/8/17 4:43 AM, Rick Stevens wrote:
>> On 07/07/2017 02:04 AM, Stephen Morris wrote:
>>> On 7/6/17 8:50 AM, Rick Stevens wrote:
On 07/05/2017 03:25 PM, Stephen Morris wrote:
> On 6/24/17 4:03 PM, Samuel Sieb wrote:
>> On 06/23/2017 05:
On 07/07/2017 07:07 PM, William wrote:
> On Friday, July 07, Rick Stevens wrote:
>
>> Ye gods! That was a LONG time ago.
>
> It took me a few hours of groping around to find that thread!
>
>> Nouveau has gotten better. It just didn't work well on some
>> chipsets way back when dinosaurs walked t
Talk: @@Norton support number +44-800-014-8285 norton phone number&& Norton
toll free number& Norton customer number)(call us)
Official Norton™ Support is FREE for customers.+44-800-014-8285 Norton users
from UK can contact Official Norton™ Technical Support to connect with a live
Norton Cha
https://opensource.com/article/17/7/how-linux-containers-evolved
If you like it, please social Media this message out.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
20 matches
Mail list logo
