/runuser -l pdupre -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/pdupre/.vnc/%H%i.pid
That's your problem. You shouldn't be touching that file. That
document is bad... It does appear to have been removed in the current
release.
You modify /etc/tigervn
On Feb 16, 2025, at 05:26, Patrick Dupre via users
wrote:
>
> Feb 16 11:09:32 homere systemd[1]: vncserver@:2.service: Can't convert PID
> files /home/pdupre/.vnc/homere:2.pid O_PATH file descriptor to proper file
> descriptor: Permission denied
Systemd services running as p
metry 1280x1024"
PIDFile=/home/pdupre/.vnc/%H%i.pid
systemctl daemon-reload
vncpasswd
systemctl start vncserver@:2.service
AUTHENTICATING FOR org.freedesktop.systemd1.manage-units
Authentication is required to start 'vncserver@:2.service'.
Authenticating as: Patrick Dup
Hello,
I can connect to a remote machine (fedora 38) via vnc or remmina (ssh or vnc)
but I just have black screen.
Here is my ~/.vnc/xstartup
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
#exec /etc/X11/xinit/xinitrc
gnome-session --session=gnome-classic &
I also tried
ld vary to what you need.
Other things.
/etc/firewalld/services
[root@setzco services]# cat vnc-server.xml
Virtual Network Computing Server (VNC)
A VNC server provides an external accessible X
session. Enable this option if you plan to provide a VNC server
with direct access. The acce
T
> Initiating SYN Stealth Scan at 23:58
> Scanning localhost (127.0.0.1) [11 ports]
> Completed SYN Stealth Scan at 23:58, 0.01s elapsed (11 total ports)
> Nmap scan report for localhost (127.0.0.1)
> Host is up (0.13s latency).
> Other addresses for localhost (not scanned): :
report for localhost (127.0.0.1)
Host is up (0.13s latency).
Other addresses for localhost (not scanned): ::1
PORT STATE SERVICE
5900/tcp closed vnc
5901/tcp closed vnc-1
5902/tcp closed vnc-2
5903/tcp closed vnc-3
5904/tcp closed ag-swim
5905/tcp closed asmgcs
5906/tcp closed rpas-c2
5907
I am trying to set up a vnc server on Fedora 31 (GDM, GNOME-Wayland).
I've tried 2 separate routes
1) XDCMP: via xvnc.socket (as documented here
/usr/lib/systemd/system/xvnc@.service)
Super simple, just run
systemctl enable xvnc.socket
Then from either the same machine or a RPI I connec
I have tried 3 different resolution settings with no difference. Well,
the size of the vnc client window changes but the screen remains black
in all cases.
Again the odd thing is that the Welcome Window shows up for a new user.
So, if you can tell it to run a GUI app it seems it will. It&#
g a blank
screen...and it was somehow?the resolution that was "proposed" as
opposed to what it "really" was that was causing an issue.just throwing
this out there. It probably doesn't factor into your situation...
EGO II
On Sun, Mar 17, 2019, 1:21 AM Chris Kottarid
I am trying to get Tiger VNC working on a home machine running Fedora 29
with latest patches applied.
I can connect and provide user's password but the screen is blank.
On initial connection I got the Welcome Window that asked for keyboard
style and such, but when I closed that window no
On 10/5/18 11:57 AM, francis.montag...@inria.fr wrote:
On Fri, 05 Oct 2018 11:07:28 -0400 Robert Moskowitz wrote:
Type=simple
...
Replace thus:
ExecStart=/usr/bin/vncserver -autokill %i
by:
ExecStart=/usr/bin/vncserver -fg %i
-autokill is useless with -fg
Thank you. I will review
On Fri, 05 Oct 2018 11:07:28 -0400 Robert Moskowitz wrote:
>> Type=simple
...
>> Replace thus:
>>ExecStart=/usr/bin/vncserver -autokill %i
>> by:
>>ExecStart=/usr/bin/vncserver -fg %i
>> -autokill is useless with -fg
> Thank you. I will review this.
> I updated bug 1633805
> Actua
On 10/5/18 1:58 AM, francis.montag...@inria.fr wrote:
On Fri, 05 Oct 2018 07:42:16 +0200 francis.montag...@inria.fr wrote:
Can you try to set Type to simple and thus get rid of the pid stuff.
So try:
[Service]
Type=simple
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
ExecStartPr
On Fri, 05 Oct 2018 07:42:16 +0200 francis.montag...@inria.fr wrote:
> Can you try to set Type to simple and thus get rid of the pid stuff.
> So try:
> [Service]
> Type=simple
> WorkingDirectory=/home/rgm
> User=rgm
> Group=rgm
> PAMName=login
> ExecStartPre=/bin/sh -c '/usr/bin/vncserver -ki
orking
> WorkingDirectory=/home/rgm
> User=rgm
> Group=rgm
> PAMName=login
> PIDFile=/home/rgm/.vnc/%H%i.pid
> ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
> ...
> stopped and restarted vncserver and it failed:
...
> (
@.service, in the [service] section, may solve that problem:
PAMName=login
I changed my service file to have:
[Service]
Type=forking
WorkingDirectory=/home/rgm
User=rgm
Group=rgm
PAMName=login
PIDFile=/home/rgm/.vnc/%H%i.pid
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/n
On 10/1/18 9:34 AM, Rex Dieter wrote:
francis.montag...@inria.fr wrote:
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
Robert Moskowitz wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome.
..
Is this documented anywhere, ideally in a bug report?
francis.montag...@inria.fr wrote:
>
> Hi
>
> On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
>
>> Robert Moskowitz wrote:
>
>>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>>> gnome.
..
>> Is this documented anywhere, ideally in a bug report?
>
> I don't know.
On Sun, 30 Sep 2018 09:35:06 -0400 Robert Moskowitz wrote:
> On 9/30/18 2:56 AM, francis.montag...@inria.fr wrote:
>> On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
>> PAMName=login
>> UtmpIdentifier=%I
>> UtmpMode=user
> where are those 3 variables defined and documented?
On 9/30/18 2:56 AM, francis.montag...@inria.fr wrote:
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
Robert Moskowitz wrote:
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome.
I think that adding the following in the vncserver@.service and/or
xvnc@.servic
Hi
On Wed, 26 Sep 2018 10:32:43 -0500 Rex Dieter wrote:
> Robert Moskowitz wrote:
>> It seems Tiger-vncserver is broken WRT polkit for any spin other than
>> gnome.
I think that adding the following in the vncserver@.service and/or
xvnc@.service, in the [service] section, may solve that proble
Robert Moskowitz wrote:
> It seems Tiger-vncserver is broken WRT polkit for any spin other than
> gnome.
Is this documented anywhere, ideally in a bug report?
-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email t
Per the instructions from the Fedoraforum. Took a bit, but I am
mounting USB drive. Polkit is prompting me for my password and that
lets me mount the drive. Probably because I am in group wheel.
So call is off for alternative to vnc and to remember how to do it with
SysV. I am staying
eplace my
> decades-old connection to VNC?
>
I was having problems with vnc not always being able to connect. I have
now switched to x2go. It has been working well for about 2 weeks.
One note -- sometimes I have to change the window size for the text to look
good. It has not been enough of a p
Il giorno mer, 26/09/2018 alle 10.25 -0400, Robert Moskowitz ha
scritto:
> So it is time to look at the alternatives.
Xpra ?
https://www.xpra.org/
Xpra is an open-source multi-platform persistent remote display server
and client for forwarding applications and desktop screens.
It gives you r
On 9/27/18 9:28 AM, Robert Moskowitz wrote:
> Per the instructions from the Fedoraforum. Took a bit, but I am mounting USB
> drive. Polkit is prompting me for my password and that lets me mount the
> drive.
> Probably because I am in group wheel.
>
> So call is off for alte
connection to VNC?
As discussed on the test list, the actual problem with tiger vncserver and
polkit
arises when it is started via the supplied vncserver@.service systemd file.
If started manually that problem doesn't exist.
Just like in all things Linux, there are multiple ways to accom
a SCREEN and
> just
> forget about that screen session...
>
> So it is time to look at the alternatives. I know they are out there and
> have been
> talked about on this list, but my search foo is weak (as always). So can I
> have a
> bit of help in figuring out what to repl
about that screen session...
So it is time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
thanks
I use
On 9/26/18 12:43 PM, Tom Horsley wrote:
On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:
So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
I use x2go, but it operates in a completely different fashion
from VNC (and I don't think i
On Wed, 26 Sep 2018 10:25:45 -0400
Robert Moskowitz wrote:
> So can I have a bit of help in figuring out what to replace my
> decades-old connection to VNC?
I use x2go, but it operates in a completely different fashion
from VNC (and I don't think it can allow you to share the
phys
time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
thanks
___
users
On 9/20/18 7:51 PM, Ed Greshko wrote:
On 9/21/18 7:45 AM, Robert Moskowitz wrote:
On 9/20/18 7:19 PM, Rick Stevens wrote:
On 9/20/18 3:58 PM, Ed Greshko wrote:
On 9/20/18 11:37 PM, Robert Moskowitz wrote:
I have Xfce over vnc mostly working. Thanks to posts here.
I have a couple of open
On 9/21/18 8:13 PM, Patrick O'Callaghan wrote:
> On Fri, 2018-09-21 at 06:58 +0800, Ed Greshko wrote:
>> I have just installed F29 Beta 1.5 in an VM on an x86_64 system. (Sorry poc)
> Don't mind me. Of course people on the Test List will not see this
> thread unless they are also on this list (man
On Fri, 2018-09-21 at 06:58 +0800, Ed Greshko wrote:
> I have just installed F29 Beta 1.5 in an VM on an x86_64 system. (Sorry poc)
Don't mind me. Of course people on the Test List will not see this
thread unless they are also on this list (many of them aren't).
poc
_
On 9/21/18 7:45 AM, Robert Moskowitz wrote:
>
>
> On 9/20/18 7:19 PM, Rick Stevens wrote:
>> On 9/20/18 3:58 PM, Ed Greshko wrote:
>>> On 9/20/18 11:37 PM, Robert Moskowitz wrote:
>>>> I have Xfce over vnc mostly working. Thanks to posts here.
>>>>
On 9/20/18 7:19 PM, Rick Stevens wrote:
On 9/20/18 3:58 PM, Ed Greshko wrote:
On 9/20/18 11:37 PM, Robert Moskowitz wrote:
I have Xfce over vnc mostly working. Thanks to posts here.
I have a couple of open items.
My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have altered the
On 9/20/18 3:58 PM, Ed Greshko wrote:
> On 9/20/18 11:37 PM, Robert Moskowitz wrote:
>> I have Xfce over vnc mostly working. Thanks to posts here.
>>
>> I have a couple of open items.
>>
>> My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have al
On 9/20/18 11:37 PM, Robert Moskowitz wrote:
> I have Xfce over vnc mostly working. Thanks to posts here.
>
> I have a couple of open items.
>
> My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have altered the
> xstartup to end with:
I have just installed F29 Beta
On 9/20/18 3:49 PM, Patrick O'Callaghan wrote:
On Thu, 2018-09-20 at 11:37 -0400, Robert Moskowitz wrote:
My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have altered
the xstartup to end with:
In that case you want the Fedora Test list, not this one. F29 is
unreleased.
No respon
On Thu, 2018-09-20 at 11:37 -0400, Robert Moskowitz wrote:
> My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have altered
> the xstartup to end with:
In that case you want the Fedora Test list, not this one. F29 is
unreleased.
poc
___
users
I have Xfce over vnc mostly working. Thanks to posts here.
I have a couple of open items.
My environment is Fedora29-beta 1.2 for armv7 with Xfce. I have altered
the xstartup to end with:
# exec /etc/X11/xinit/xinitrc
exec /bin/sh /etc/xdg/xfce4/xinitrc
xrdb $HOME/.Xresources
startxfce4
Il giorno ven, 27/04/2018 alle 15.33 -0700, Samuel Sieb ha scritto:
> The change has been reverted so VNCI will be back whenever the
> Fedora
> packager updates remmina next.
Ok.
Thanks!
--
Dario Lesca
(inviato dal mio Linux Fedora 27 Workstation)___
On 04/27/2018 03:28 PM, Dario Lesca wrote:
Il giorno gio, 19/04/2018 alle 09.48 -0700, stan ha scritto:
Open a bugzilla against remmina package at the address below.
Open:
https://bugzilla.redhat.com/show_bug.cgi?id=1572701
The change has been reverted so VNCI will be back whenever the Fedor
Il giorno gio, 19/04/2018 alle 09.48 -0700, stan ha scritto:
> Open a bugzilla against remmina package at the address below.
Open:
https://bugzilla.redhat.com/show_bug.cgi?id=1572701
--
Dario Lesca
(inviato dal mio Linux Fedora 27 Workstation)___
users
bug", and then select
> Fedora until you have received a new bug entry page. Select the
> component (remmina) at the top, and then pretty much fill it in with
> what you have put in your emails.
I use VNC as the remote desktop server. You can use Remmina with the VNC
plugin or vncviewer
On Thu, 19 Apr 2018 14:29:43 +0200
Dario Lesca wrote:
> IMHO
> I think Fedora must buil the remmina package with this option enabled
>
> If this plugin is enable, and sometime and in some circumstance not
> work, is better than it's not enable and alway do not work.
>
> What is the best way to
ild it and reinstall only the remmina-plugins-vnc rpm and now the
VNC incoming connection work great again
IMHO
I think Fedora must buil the remmina package with this option enabled
If this plugin is enable, and sometime and in some circumstance not
work, is better than it's not enable and a
On 04/18/2018 10:49 AM, Dario Lesca wrote:
After last remmina update (1.2.0-0.51.20180408.git.6b62986) the VNC
incoming connection (Plugin VNCI) is go away.
Now it's any more possible to start a reverse connection, like previous
version (1.2.0-0.42.20170908git205df66) allow to do (I have
After last remmina update (1.2.0-0.51.20180408.git.6b62986) the VNC
incoming connection (Plugin VNCI) is go away.
Now it's any more possible to start a reverse connection, like previous
version (1.2.0-0.42.20170908git205df66) allow to do (I have do a "sudo
dnf downgrade remmina --al
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
since Mon 2017-07-10 17:04:20 PDT; 1s ago
>Listen: 10.76.185.91:5901 (Stream)
> Accepted: 0; Connected: 0
>
> Jul 10 17:04:20 server systemd[1]: Listening on XVNC Server.
> Jul 10 17:04:20 server systemd[1]: Starting XVNC Server.
>
>> Without any clients connected/connec
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
ng XVNC Server.
> Without any clients connected/connecting can you check to see if Xvnc is
> running? I only have a running /usr/bin/Xvnc when a client is connected.
Without a connection, "ps -ef | grep vnc" shows only the grep. During an
attempted connection, Xvnc is running with
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
ally don't want xvnc@.service to be enabled or started. The connection
to
the socket triggers starting of Xvnc
On my system with no VNC clients connected.
[root@f25f system]# ps -eaf | grep vnc
root 3523 1251 0 10:04 pts/000:00:00 grep --color=auto vnc
[root@f25f system]# systemc
gt; 7. If you've not already done it "systemctl --force enable kdm"
Done previously.
> 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 present
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
issive. If you don't do that
then
Xvnc won't be able to bind to port 5900.
6. Enable port 5900 on your firewall.
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 shou
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&
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
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
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
xstartup file generated in my user's ~/.vnc
directory when running vncpasswd:
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec /etc/X11/xinit/xinitrc
Got this info from:
http://forums.fedoraforum.org/showthread.php?t=313406
Thanks MrRonMan wherever you are!
I assume thi
on and have since added gnome desktop package groups and
>>> others.
>>>
>>> On the console I get a standard non-graphical login prompt and from
>>> there I can type startx and get into gnome just fine.
>>>
>>> I don't want to change that.
>&g
prompt and from
there I can type startx and get into gnome just fine.
I don't want to change that.
I do want to use VNC to connect in over net and run gnome. I have
[snip]
Before any of the exec lines those apps seem to be running.
Just no window manager.
Any pointers would be apprec
prompt and from
there I can type startx and get into gnome just fine.
I don't want to change that.
I do want to use VNC to connect in over net and run gnome. I have
everything setup but when I connect into the VNC I initially got a blank
screen. I can get more than a blank screen by changing my
from
> there I can type startx and get into gnome just fine.
>
> I don't want to change that.
>
> I do want to use VNC to connect in over net and run gnome. I have
[snip]
> Before any of the exec lines those apps seem to be running.
>
> Just no window manager.
&g
can type startx and get into gnome just fine.
>
> I don't want to change that.
>
> I do want to use VNC to connect in over net and run gnome. I have
> everything setup but when I connect into the VNC I initially got a blank
> screen. I can get more than a blank screen by chan
hange that.
I do want to use VNC to connect in over net and run gnome. I have
everything setup but when I connect into the VNC I initially got a blank
screen. I can get more than a blank screen by changing my local user's
xstartup script. For example if I add "gnome-terminal &&
On Sun, Jan 08, 2017 at 11:16:23AM -0400, George N. White III wrote:
> On 7 January 2017 at 18:32, wrote:
>
> > Is there a way to VNC (or similar) to another system running Fedora 25?
> >
>
> Do you need to see the same desktop you have when sitting at the system or
On Sat, Jan 07, 2017 at 02:32:23PM -0800, pat...@aracnet.com wrote:
> Is there a way to VNC (or similar) to another system running Fedora 25?
Sure - run vncserver from the tigervnc-server package on the target
system, and connect with the vinagre client (preferably using SSH
forwarding).
>
On 7 January 2017 at 18:32, wrote:
> Is there a way to VNC (or similar) to another system running Fedora 25?
>
Do you need to see the same desktop you have when sitting at the system or
can you use a separate Xvnc server (probably with some limits, e.g., no or
limited
OpenGL)?
> Do
Is there a way to VNC (or similar) to another system running Fedora 25?
Do I have to switch from XWayland to Xorg?
-- Patrick
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Hi All, I got fed up with vnc failing on Fedora 23 and figured it would
be better under fedora 24 KDE, well it wasn't so I decided what the
heck, I haven't seen Gnome is a while and it's the default, maybe it
will work better.
I followed the destructions at:
https://docs.fedor
ets are included, then the full IP with each
colon, then a colon outside the brackets and a 1.
2. nmap -6 -A -T4 IP
Where IP is just the IP with colons, no brackets, was able to find the
open 5901 port for vnc. So it was definitely working the whole time, I
just had the wrong formatting for IPv6 in Ti
On Wed, Jan 27, 2016 at 1:47 PM, Gordon Messmer
wrote:
> On 01/26/2016 08:44 PM, Chris Murphy wrote:
>>
>> 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.
>
>
> Is "ss
On 01/26/2016 08:44 PM, Chris Murphy wrote:
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.
Is "ss"?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or
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 &#x
On 10/30/2015 06:01 PM, Rick Stevens wrote:
On 10/30/2015 04:25 PM, Chris Kottaridis wrote:
I don't seem to get sound. It doesn't seem to come out on my VNC client
or on the VNC server's sound card. My remote machine is close enough
that I could run a wire from it's sound
On 10/30/2015 04:25 PM, Chris Kottaridis wrote:
I am running Fedora 22 on a machine that is off in a closet and am using
VNC to access it from a machine at my desk. I followed the instructions
in System Admin guide chapter 8:
https://docs.fedoraproject.org/en-US/Fedora/22/html
I am running Fedora 22 on a machine that is off in a closet and am using
VNC to access it from a machine at my desk. I followed the instructions
in System Admin guide chapter 8:
https://docs.fedoraproject.org/en-US/Fedora/22/html/System_Administrators_Guide/ch-TigerVNC.html
I successfully got
Hello,
Is there a way to recognize that I ma connected through a vnc (remmina)
connection?
Actually, the that the shell have a different behavior. Probably
by probing a variable environment, I cannot guess.
Or, maybe there is a special shell which is run when the
remmina connection is established
On 07/23/2014 07:00 PM, poma wrote:
On 23.07.2014 10:40, poma wrote:
$ grep -v ^# $HOME/.vnc/xstartup
startxfce4
$ grep -v ^# /etc/systemd/system/vncserver@\:1.service
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target
[Service]
Type=simple
ExecStartPre=/bin
On 23.07.2014 10:40, poma wrote:
$ grep -v ^# $HOME/.vnc/xstartup
startxfce4
$ grep -v ^# /etc/systemd/system/vncserver@\:1.service
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target
[Service]
Type=simple
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -ki
On 23.07.2014 16:32, Ed Greshko wrote:
On 07/23/14 22:25, Robert Moskowitz wrote:
And this is not a bug with the default xstartup script?
No. I'd classify it as a deficiency. It works as it is designed. It just
doesn't have what you need for xfce.
The reason why 'startxfce4' exists.
Wh
On 07/23/14 22:25, Robert Moskowitz wrote:
> And this is not a bug with the default xstartup script?
No. I'd classify it as a deficiency. It works as it is designed. It just
doesn't have what you need for xfce.
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing
1 - 100 of 185 matches
Mail list logo
