On 07/13/17 02:13, CLOSE Dave wrote:
> Ed Greshko wrote:
>
>> Oh, and since I think you said you're not using IPv6 for anything you
>> can disable it completely and try again.
>>
>> Adding ipv6.disable=1 to the boot parameters seems to work the best.
>> That way it is disabled from boot time.
> Tha
Ed Greshko wrote:
> Oh, and since I think you said you're not using IPv6 for anything you
> can disable it completely and try again.
>
> Adding ipv6.disable=1 to the boot parameters seems to work the best.
> That way it is disabled from boot time.
That did it! The greeting screen now appears as
On 07/11/17 08:18, CLOSE Dave wrote:
> And when I try to connect,
>
> Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot
> connect to fe80::3617:ebff:feeb:6b02:1, giving up
> Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1
> cannot be opened
Oh, and since
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 (
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
On 07/08/17 09:40, CLOSE Dave wrote:
> Here's my files.
Just to clarify a bit more...
>
> # cd /etc/systemd/system
> # cat xvnc@.service
> [Unit]
> Description=XVNC per Connection Daemon
> After=syslog.target
>
> [Service]
> Type=simple
> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry
On 07/08/17 10:22, Ed Greshko wrote:
> That is 5901 v.s. 5901
Of course I wanted to type 5901 v.s. 5900
--
Fedora Users List - The place to go to speculate endlessly
signature.asc
Description: OpenPGP digital signature
___
users mailing list -- user
On 07/08/17 09:40, CLOSE Dave wrote:
> Almost. But the service isn't starting.
>
> # systemctl status -l xvnc@:.service
> xvnc@:.service - XVNC per Connection Daemon
>Loaded: loaded (/etc/systemd/system/xvnc@.service; enabled; vendor
> preset: disabled)
>Active: failed (Result: resources)
Ed Greshko wrote:
> OK. Sorry to have misunderstood precisely what you want to do. I
> now have it working as I suspect you need it.
Great. Thanks.
> 1. Yes, you need KDM. So, if you've not installed it do so.
>
> 2. Edit /etc/kde/kdm/kdmrc the [Xdmcp] section Enable=true.
>
> 3. Go to /
On 07/08/17 08:32, Ed Greshko wrote:
> 7. If you've not already done it "systemctl --force enable kdm"
>
> 8. Reboot.
>
> Your console should now be showing KDM as your login screen.
>
> And you now should be able to connect with something like remmina using VNC
> protocol
> and get presented wi
On 07/08/17 01:50, CLOSE Dave wrote:
> Unfortunately, no, that doesn't help. I already have a one-user setup
> working and I understand how to extend it to additional users -- so long
> as the list of users is finite and known to me in advance. But the
> extension technique involves using unique
I wrote:
> I'm trying to setup a multi-user VNC server on recent versions of
> Fedora without success thus far. I understand that doing so requires
> a display manager with XDMCP support. The current default DM is SDDM
> which does not include such support (at least so far as I've found).
> That m
On 07/07/17 09:26, CLOSE Dave wrote:
> I'm trying to setup a multi-user VNC server on recent versions of Fedora
> without success thus far. I understand that doing so requires a display
> manager with XDMCP support. The current default DM is SDDM which does
> not include such support (at least s
On 07/07/17 09:26, CLOSE Dave wrote:
> I'm trying to setup a multi-user VNC server on recent versions of Fedora
> without success thus far. I understand that doing so requires a display
> manager with XDMCP support. The current default DM is SDDM which does
> not include such support (at least s
I'm trying to setup a multi-user VNC server on recent versions of Fedora
without success thus far. I understand that doing so requires a display
manager with XDMCP support. The current default DM is SDDM which does
not include such support (at least so far as I've found). That means I
need to c
25 matches
Mail list logo
