On Fri, Apr 3, 2009 at 8:46 PM, Hew McLachlan
wrote:
> vncserver was removed during hardy development, so it is not present in
> the release version. The reason was "dead upstream, superseded by vnc4".
Thanks for getting back to me.
Oddly, synaptic on hardy still shows vnc and vnc4 packages. So
vncserver was removed during hardy development, so it is not present in
the release version. The reason was "dead upstream, superseded by vnc4".
--
vnc4server uses wrong font path
https://bugs.launchpad.net/bugs/3593
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This is still broken in Hardy Heron.
We recently upgraded to Hardy Heron (=8.04 LTS), and now vncserver dies,
logging "Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'". This is NOT
about font path in vnc4sever (as the title states), but the symptom was
reported by Roman Wartel in Bug #34218, which
Ubuntu Edgy Eft is no longer supported, so a SRU will not be issued for
this release. Marking Edgy as Won't Fix.
** Changed in: vnc4 (Ubuntu Edgy)
Status: Fix Committed => Won't Fix
--
vnc4server uses wrong font path
https://bugs.launchpad.net/bugs/3593
You received this bug notification
gutsy & vncserver 3.3.7-14ubuntu1
When I start the server, it looks like it's ok:
[EMAIL PROTECTED]:~$ vncserver -geometry 800x600 -depth 16 :4
New 'X' desktop is slabanderi:4
Starting applications specified in /etc/X11/Xsession
Log file is /home/rhk/.vnc/slabanderi:4.log
[EMAIL PROTECTED]:~$
b
Breezy support is over.. Today it's Breezy End Of Life!
** Changed in: vnc4 (Ubuntu Breezy)
Status: Confirmed => Rejected
--
vnc4server uses wrong font path
https://bugs.launchpad.net/bugs/3593
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct s
Tried the fix (on Edgy)
$ sudo ln -s /usr/share/fonts/X11 /usr/share/X11/fonts
but it only worked until reboot. I now get :-
VNC viewer version 3.3.7 - built Jul 4 2006 10:04:48
Copyright (C) 2002-2003 RealVNC Ltd.
Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
See http://www.realvnc.com f
Since there is a work-around for 3593, it's less critical. Based on the
evidence in 78282, it's not the same bug: the vnc server blows up with
other strange errors (after the font path has been fixed). You can see
this because the font path is fixed in feisty, but 78282 persists there.
:(
Howeve
Kees, are you saying that this fix won't go out until a fix for 78282 is
found? Comment 17 on that bug makes it sound like they are one and the
same.
--
vnc4server uses wrong font path
https://launchpad.net/bugs/3593
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
Fixed in Feisty and Dapper. Still open for Breezy (which goes EOL in
April) and Edgy. If bug 78282 can be solved for Edgy, the fix for this
bug will be included in the security update.
Attached is the diff to apply to the rules that fixes the problem (as
done in Feisty).
** Changed in: vnc4 (Ub
Error persists here, AMD64 platform. As pointed above, fix should be
simple. In my case, editing /etc/vnc/vnc.conf did not work simply
because I didn't have that file. Also, it was ignoring /etc/vnc.conf.
But the soft link worked. Just to make sure everybody understands, what you
need to do i
** Summary changed:
- Xvnc4 (package vnc4server) unable to find fixed font in Breezy
+ vnc4server uses wrong font path
** Changed in: vnc4 (Ubuntu Breezy)
Status: Unconfirmed => Confirmed
--
vnc4server uses wrong font path
https://launchpad.net/bugs/3593
--
ubuntu-bugs mailing list
ubu
12 matches
Mail list logo
