@pcr
XDMCP is enabled and GDM works well with XMing (windows based X server). I get
a working desktop when I login using Xming from a windows machine.
When I try to connect with UltraVNC or TightVNCViewer from the windows machine,
I get only the grey screen with the X cursor.
This is why I thin
@Soltész András
Have you enable XDMCP in gdm or kdm ?
If you use GDM may be look at :
https://bugs.launchpad.net/ubuntu/gutsy/+source/gdm/+bug/150193.
I personally use KDM (under Kubuntu) and it works well.
--
vnc4server does not start Desktop environment after security update
https://bugs.laun
Has anyone tried this with the final Gutsy?
I have a fresh Gutsy install configured for remote login with xinetd
(not simply starting vncserver with a user) and all I get is a grey
window with the mouse cursor.
No matter what I do, I don't get a Gnome login screen, let alone a
working desktop.
I
** Changed in: vnc4 (Ubuntu Edgy)
Status: Fix Committed => Fix Released
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
vnc4 (4.1.1+xorg1.0.2-0ubuntu4.1) feisty-security; urgency=low
* unix/vncserver: add "-extension XFIXES" (LP: #78282).
-- Kees Cook <[EMAIL PROTECTED]> Tue, 21 Aug 2007 09:04:53 -0700
** Changed in: vnc4 (Ubuntu Feisty)
Status: Fix Committed => Fix Released
--
vnc4server does not s
Fix confirmed; pushing updates for edgy and feisty shortly...
** Changed in: vnc4 (Ubuntu Edgy)
Assignee: (unassigned) => Kees Cook (keescook)
Status: Confirmed => Fix Committed
** Changed in: vnc4 (Ubuntu Feisty)
Assignee: (unassigned) => Kees Cook (keescook)
Status: Conf
This appears FIXED in Gutsy Gibbons!
It seems the
-extension XFIXES
was added. I tested from a user account without an x session nor a $DISPLAY
environment variable.
vncserver :1
Then it requested the password.
Then ...
vncserver -kill :1
In
/home/username/.vnc/xstartup
I commented out t
Hi
Can you put it in "vncserver" which is the wrapper around Xvnc? It
wouldn't fix the problem but it will alleviate it.
With regards
Antony
On Fri, 2007-08-24 at 00:47 +, Kees Cook wrote:
> On Fri, Aug 24, 2007 at 12:20:41AM -, Peter Clifton wrote:
> > Rather than patching scripts which
On Fri, Aug 24, 2007 at 12:20:41AM -, Peter Clifton wrote:
> Rather than patching scripts which call Xvnc, wouldn't a better fix to
> be building Xvnc without the extension in the first place (Or
> determining why it is built in, but doesn't work?)
I'm quite willing to take a patch to do it th
Rather than patching scripts which call Xvnc, wouldn't a better fix to
be building Xvnc without the extension in the first place (Or
determining why it is built in, but doesn't work?)
Its been a while since I last looked at this as I'm no-longer trying to
use VNC for a terminal-server, however I r
vnc4 (4.1.1+xorg1.0.2-0ubuntu5) gutsy; urgency=low
* unix/vncserver: add "-extension XFIXES" (LP: #78282).
-- Kees Cook <[EMAIL PROTECTED]> Tue, 21 Aug 2007 09:04:53 -0700
** Changed in: vnc4 (Ubuntu)
Status: Confirmed => Fix Released
--
vnc4server does not start Desktop environmen
All my vnc4server problems went away when I patched the vnc4server
script as below (after reading the comments above). It would be nice if
someone would make this change in the package itself...
$ diff -uw vnc4server~ vnc4server
--- vnc4server~ 2007-01-07 12:30:09.0 -0500
+++ vnc4server 2
I am getting the same problem here. Everything broke in the upgrade to 7.04,
vnc4server latest is bad, but reverting to edgy (uncomment edgy lines in
apt/sources, and downgrade) fixes it.
Warren
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bu
I have followed this thread but I remain unable to connect either
locally or remotely when using xinetd. Otherwise, launching Xvnc
directly on the command line allows me to connect without any problem.
I'm testing using Feisty as both client and server. The server shows
these errors when I attem
Workaround installing Debian Edgy packages and patching up font paths
enough to work at:
http://badtux.net/2007/06/making-vncserver-work-on-ubuntu.html
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification
I have a similar problem according to ticket 68020. I cannot use
Azureus under VNC4Server, but the above idea of using the TIghtVNCserver
package did the trick for me.
The problem's with VNC4Server that I can see. I've even gone so far as
to try it with external Windows X servers. Mocha X works
I tested upstream (Package: vnc4server (4.1.1+X4.3.0-21) in Debian
Stable/Unstable/Testing) and it works properly other than the font path
being wrong of course (easily worked around with a single symlink, but
easily fixed in the package itself with a simple recompile). I also
tested upstream 4.2.
Chribu solved initial problem but Xvnc worked only first two times...
Very strange. Now, after some seconds, gdm seems to crash (look
attachment).
This is the dump of /var/log/syslog:
May 29 23:21:34 HomeDesk gdm[7368]: Handling user message: 'GET_CONFIG
greeter/SetPosition 127.0.0.1:1'
May 29 2
I LOVE YOU!!!
... Hi, thank you very much... I missed to change xstartup replacing twm
with gnome-session.
Now all is working well.
I'm going to post on launchpad.net...
Thanx again, Alessio
2007/5/29, Chribu <[EMAIL PROTECTED]>:
>
> I managed to get it working following this howto:
>
> First
Thanx to Chribu!
I missed to change /home/myuser/.vnc/xstartup replacing twm with gnome-session.
Just another bogus...
Sorry!
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member o
I managed to get it working following this howto:
First off, the window manager you see (tweed) is the twm window manager.
There is no mouse support, because this window manager isn't fully installed
on your system. Specifically, the menu package is not installed. If you
start aptitude or synaptic
I tried XFIXES fix but after client connection I still can only see a
blank workspace (background is B&W grid, mouse ptr is X). These are
dumps of my .conf files. I have Ubuntu Feisty AMD64 (not x86 on AMD64).
- xinetd.conf -
service Xvnc-myuser
{
type = UNLISTED
disable = no
Thanks Isaac Salsberg and Joe Baker for the fix it make a while that I
wait to fix this bug, The Font Path and XFIXES params added the last
package works for me on Edgy
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this
Now it works with Isaac Salsberg 's comment...
You guys don't know how much time i've wasted on this one ... :(
I think it was the -extension XFIXES that made it work, i'm not using gdm and i
already changed the font path.
--
vnc4server does not start Desktop environment after security update
ht
The posted solution worked for me also. It's time to get this fix
applied to the default package.
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Many thanks to Warren and others...I assumed it must be something
related to multiple logins, but hadn't been able to find where it was
set. Fully functional once again!
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this
There are 3 things that have to be fixed in order to make vnc4server
work.
The first two are options needed to start vnc4server
1. Fix the font path used with -fp option.
The -fp option with the right path in Feisty is:
-fp /usr/share/fonts/X11/misc
2. Add "-extension XFIXES" option
Hubris, the return to login prompt must be, as mentioned by Warren
Butler , because of the default to not allow multiple logins. If you are
using GNOME you can go to System -> Administration -> Login Windows and
then unselect Disable multiple logins for single user in the General
Tab. The -extensio
The return to the login prompt is because Feisty changed the default to
not allow multiple logins for the same user. If you are running
Xubuntu, for example, go to Applications -> Settings -> Login Window and
there is an option on the General tab to disable multiple logins for a
single user. By d
This may not be exactly the same problem as others are having...but
hopefully someone can suggest a solution. I too have found that adding
-extension XFIXES with the latest version of the binary fixes the
immediate disconnection problem - just the same as backdating to an
older version of the bina
As I am not using xinetd daemon, I have just added in /usr/bin/vncserver
(pointing to vnc4server file)
$cmd .= " -extension XFIXES ";
at the end of
$cmd .= " -rfbport $vncPort";
$cmd .= " -pn";
$cmd .= " -extension XFIXES ";
Firefox, thunderbird, etc. are back :)
Thanks for your help !
--
vnc
I confirm the option "-extension XFIXES" resolve the problem on feisty.
it works now.
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
Disregard my last message. Got it working.
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
I have two computers using Feisty, identically configured and had the
same problem. The Xvnc configuration works perfect with the previous
pacakge under Edgy.
Now one works with the XFIXES argument, the other doesn't. What can I do
to debug this problem?
--
vnc4server does not start Desktop envi
Finally I got the bloody vnc4server working. What Roberto Faroline said
on 2007-04-25 DID WORK. They should at least assign someone to fix it (I
was about to install fedora :-o).
Anyway, this is what I did to make it work:
Modify the file /etc/xinetd.d/Xvnc, by adding at the end of the
server_arg
It seems to me that I may be having the same problem.
This may or may not be helpful to you.
I fixed my problem using "-query ".
CANNOT be "localhost" nor "127.0.0.1". It MUST be the actual ip
address of the server or else a name that resolves to this address.
--
vnc4server does not start Desk
F.Y.I. "-extension XFIXES" is supported by
vnc4server_4.1.1+xorg1.0.2-0ubuntu4_i386.deb, previous version like
vnc4server_4.1.1+X4.3.0-21_i386.deb does not support XFIXES.
I had all the problems listed above with vnc4server since I installed
edgy, searching for the solution I upgraded to feisty wi
Heh.. was feeling smug until I discovered -extension XFIXES had already been
suggested at the end of this thread!
I've been working around with -extension XFIXES. I came across this bug looking
to see if the one I'm about to file regarding a Segfault in VNC is a dup.
I discovered this debugging
** Changed in: vnc4 (Ubuntu)
Assignee: (unassigned) => Harshith Aranya
** Changed in: vnc4 (Ubuntu)
Assignee: Harshith Aranya => (unassigned)
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification
Roberto...is that intended to fix the stated issues with applications
starting?
It doesn't have any impact on the "Transport Endpoint errors listed at
the beginning of this bug report". Is it possible that these are 2
separate bugs, each applied to this release of VNC4Server?
--
vnc4server does
"-extension XFIXES" adding this option to my vnc4server command line solved my
problems.
I hope this helps.
Cheers,
Roberto
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of
What I've found is that Gnome applications cannot run on the newer
versions of Xvnc. I get the message described above when starting any
Gnome application:
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 74 error_code 1 request_code 146 minor_code 2)
I
Hi
dpkg -l |fgrep xorg
ii xvnc4viewer4.1.1+xorg1.0.2-0ubuntu4
Virtual network computing client software fo
ii xserver-xorg-core 1.2.0-3ubuntu8
X.Org X server -- core server
It looks like vncserver is comp
Achim J. Latz wrote:
> Charles Twardy 's suggestion above was part of the solution for me:
>
> 1. In /etc/X11/gdm/gdm.conf
> Find the [xdmcp] section in the file, set: Enable=True
>
I would have thought this would have been set to on because I run an
LTSP server, but I'd forgotten that Ubuntu's
Charles Twardy 's suggestion above was part of the solution for me:
1. In /etc/X11/gdm/gdm.conf
Find the [xdmcp] section in the file, set: Enable=True
2. In /etc/xinetd.d/Xvnc
Change: /usr/share/X11/fonts/misc
To: /usr/share/fonts/X11/misc
3. sudo killall Xvnc
4. sudo /etc/init.d/xinetd restart
Hi,
I have just installed Feisty from CD (after a "/" crash)
I have the same problem with vnc4server in Edgy after the update
I can start vnc4server with twm. But I just cannot launch mozilla-
thunderbird
--\ Versions
i4.1.1+xorg1.0.2-0ubuntu1
p4.1.1+xorg1.0.2-0ubuntu4
in Edgy I down
The twm window manager works.
To me this seems like Gnome's inability to deal with a non-GLX display.
This is a show stopper especially for Linux thin clients.
Now on this machine I did have some 3d effects software loaded beryl and
such. Maybe this is leading to certain gnome options enabled
Hmm... some apps work under this vnc4server
firefox
emacs (as an X application)
konqueror
Open Office .org Works...(Font smoothing is not so smooth)
Some apps do not work...
nautilus
gnome-session
gedit
gcalctool (Offers interesting error message)
main.c: WAR
I'm trying to figure out where this file gets generated from
~/.vnc/xstartup
It does not invoke gnome.
The file instructs that for a normal desktop two lines should be commented out.
I tried doing that... still no gnome-session.
I tried adding
gnome-session
at the end, but no joy.
--
This is most likely a problem with /etc/vnc.conf not having some sane
defaults. Maybe the problem is that vncserver and vnc4server can both
be installed at the same time.
I'm looking into this further. Maybe we can patch /etc/vnc.conf from
vnc4-common package.
--
vnc4server does not start De
Hi,
Kees Cook:
> I've tried rebuilds against a more current Xorg[1], but they still fail. :(
>
Bah.
> [1] http://people.ubuntu.com/~kees/feisty/vnc4/
>
I'll try to take a look, but I haven't exactly got much time at the
moment. Right before the release is the exact wrong time to run across
a pr
i've resorted to tightvnc
from console run tightvncserver
it opens a session on :1
it sort of works...
Christian
On 4/10/07, Kees Cook <[EMAIL PROTECTED]> wrote:
> I, unfortunately, don't know how to fix the problems. If someone can
> package a working vnc4, I would be more than happy to sponsor
I, unfortunately, don't know how to fix the problems. If someone can
package a working vnc4, I would be more than happy to sponsor an upload.
I've tried rebuilds against a more current Xorg[1], but they still fail.
:(
[1] http://people.ubuntu.com/~kees/feisty/vnc4/
--
vnc4server does not start
Re-verified with vnc4server=4.1.1+xorg1.0.2-0ubuntu4
The core problem seems to be that any gnome apps fail with the error as
below:
[EMAIL PROTECTED]:~$ gnome-session
The program 'gnome-session' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadReq
vino is also very, very slow compared to vnc4server, at least in my
experience.
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
Is anyboy (kescook?) doing something about this? I'd hate to see a
Feisty release with no good vnc server.
And no, vino doesn't work for me. I am *not* going to leave my server
unattended with an active display session, 100% accessible to anybody
who walks by and turns the monitor on.
--
vnc4ser
PLEASE pull this update. It causes no end to grief for users.
--
vnc4server does not start Desktop environment after security update
https://bugs.launchpad.net/bugs/78282
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Chuck Forsberg wrote:
> Was able to get tightvncserver working with fluxbox on Feisty. When I
> tried to use gnome I got a desktop allright, but the keys in the
> keyboard were mixed up.
>
> Would be nice to get gnome to work with the latest and fastest VNC.
> Vino works but doesn't count because
I recently tried freeNX as an aternative to vnc. I was very impressed
with the performance, so much so I removed vnc4server.
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Was able to get tightvncserver working with fluxbox on Feisty. When I
tried to use gnome I got a desktop allright, but the keys in the
keyboard were mixed up.
Would be nice to get gnome to work with the latest and fastest VNC.
Vino works but doesn't count because it must be manually started.
--
I second the last request. I depend on VNC on my Ubuntu Boxes and don't
want to risk as mistake where I am left locked out of the boxes.
A non-functional security fix is the same as nothing and should be
removed.
--
vnc4server does not start Desktop environment after security update
https://laun
Hi
Can somebody pull 4.1.1+xorg1.0.2-0ubuntu1.6.10.1 out of the
repositories so it doesn't repeatability get flagged by the software
update tool.
Thanks
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-b
Changing the font path (-fp) may help.
Like Stefan, my Xvnc started failing with thousands of "Transport
endpoint is not connected" errors. Downgrading didn't help. What was
happening is that Xvnc kept dying, and Xinetd kept restarting it.
Thousands of times. Running Xvnc manually, I found it was
You could use the vncserver (v.3.3) or tightvnc. However they both are
"much" slower than vnc4server, which is the de facto standard.
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
In addition to having refresh problems with ATI driver as mentionned in
LP 57156 vino provides only a way to control an existing session and not
to create a new one remotely.
Here is on current feisty a step by step reproducer:
1) update to latest version of vnc4server
$ sudo apt-get install vnc4
Any packages that are not part of the main repositories may have
increased delays in security and regular updates. I'd like to know if
there's any reason besides problems with proprietary drivers why you
wouldn'tbe using vino instead (included in the standard Ubuntu Gnome
desktop) ?
I'd like to he
I've done (after uncommenting the first two lines of .vnc/xstartup)
$ sudo chmod 755 /etc/X11/xinit/xinitrc
but still grey screen
I restored xterm, then tried:
$ gnome-session
The program 'gnome-session' received an X Window System error.
This probably reflects a bug in the program.
The error w
I've also encountered this problem here. I'm migrating from a Mandriva
server where we had nearly 30 pre-launched VNC Server sessions to
Ubuntu. I'm eager to see version 4.2.8 deployed in Feistey. Although
Tightvncserver is getting us by for now.
--
vnc4server does not start Desktop environmen
As someone who is also experiencing this fatal bug in vnc4server, a
status update would be great since it has been almost a month and not
assigned to anyone. Thanks :-).
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs maili
Ditto. Please fix this bug or revert the "upgrade". Current vnc4server
is unusable.
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
I agree with Stefan. As it is vnc4server is totally useless.
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Oh, btw, I'm using Edgy 6.10 32-bit, trying to run KDE remotely (I have
kde-core but not full Kubuntu installed). I'm also using it for full
desktop mode - I've uncommented the first two lines in ~/.vnc/xstartup
and commented out the others.
--
vnc4server does not start Desktop environment after
Hi,
I can also confirm that the updated vnc4server has some problems - I can
use the version in edgy just fine, but after trying the update, I can't
log into the VNC server from my Windows machine (using UltraVNC). It
asks for a password and then just dies. If I downgrade it (sudo apt-get
install
I have experienced this also, on two different machines with recent
installs on trying to launch gnome-session or xfce4-session
an older machine that hasn't been updated in a while runs just fine.
I found that switching from vnc4server back to tightvncserver ("fixes"
isn't the right word) removes
Yes, that's correct. I edited the initial description.
Thanks for pointing that out.
** Description changed:
Binary package hint: vnc4server
After the update of vnc4server (vnc4 (4.1.1+xorg1.0.2-0ubuntu1.6.10.1)
- edgy-security) of today 2006-01-06, vnc4server does not start any longer
+ e
Hi
I think the initial description should say "today 2007-01-06" rather
than "today 2006-01-06".
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
I think the startup failures may be related to the errors seen in bug
78294. (Though it is unclear if these are duplicates.)
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Changed in: vnc4 (Ubuntu Edgy)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
vnc4server does not start Desktop environment after security update
https://launchpad.net/bugs/78282
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
4.1.1+xorg1.0.2-0ubuntu1
I'm not running with the update (and now I'm going to hold off for a
while!), but on my fresh Edgy install, xinitrc isn't even executable, so
the exec fails for that reason.
[EMAIL PROTECTED]:~# ls -l /etc/X11/xinit/
total 12
-rw-r--r-- 1 root root 224 2006-08-07 20:01 x
I've isolated the problem a fair bit... xinitrc is run by
~/.vnc/xstartup, which executes `. /etc/X11/Xsession', which in turn
seems to cause any process running it to crash, if it's set to connect
to a Xvnc session. Running an xterm on it manually works fine, and the
Xsession script works fine on
80 matches
Mail list logo
