** Changed in: vnc4 (Fedora)
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/119982
Title:
amd64 vncconfig crashes
To manage notifications about this bug go to:
In precise, the version is 4.1.1+xorg4.3.0-37ubuntu4, so the fix that
Zoide and wind mention is in Ubuntu. I cannot reproduce it with this
version on amd64. Can someone confirm that this is fixed for them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Many thanks to wind!!!
His workaround works perfectly and is the easiest solution so far.
For the record, I used a more recent version of the Debian package
(http://ftp.us.debian.org/debian/pool/main/v/vnc4/vnc4server_4.1.1%2bX4.3.0-37_amd64.deb)
and it worked.
--
amd64 vncconfig crashes
On Linux nihao 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC
2009 x86_64 GNU/Linux
From the log
X Error of failed request: BadLength (poly request too large or internal Xlib
length error)
Major opcode of failed request: 134 (VNC-EXTENSION)
Minor opcode of failed request: 1 ( )
Serial
workaround on Ubuntu 9.10
apt-get remove vnc4server
rm -rf ~/.vnc
wget
http://ftp.us.debian.org/debian/pool/main/v/vnc4/vnc4server_4.1.1+X4.3.0-31_amd64.deb
dpkg -i vnc4server_4.1.1+X4.3.0-31_amd64.deb
Every works
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received
I unsubscribe ubuntu-universe-sponsors for now. Please resubscribe them,
when there is a debdiff that builds and works (see comment #32).
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this bug is still present in 9.10:
d...@linux13 193# uname -m
x86_64
d...@linux13 194# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 9.10
Release:9.10
Codename: karmic
d...@linux13 195# cat .vnc/linux13:1.log
Xvnc Free
Bug is still present.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: vnc4 (Debian)
Status: New = Fix Released
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: vnc4 (Ubuntu)
Assignee: Miguel Ruiz (mruiz) = (unassigned)
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, here's the story. At one point, Debian's maintainer decided to
embed XFree86 into the package because it didn't quite work with xorg.
But when that version percolated to Ubuntu, we decided we'd rather use
xorg, so we rebased vnc4 on xorg. (the particulars are not clear to me
-- I'm scraping
** Bug watch added: Debian Bug tracker #551278
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551278
** Changed in: vnc4 (Debian)
Status: Fix Released = Unknown
** Changed in: vnc4 (Debian)
Remote watch: Debian Bug tracker #536203 = Debian Bug tracker #551278
--
amd64 vncconfig
** Changed in: vnc4 (Debian)
Status: Unknown = New
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: vnc4 (Debian)
Status: Unknown = Fix Released
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: vnc4 (Ubuntu)
Assignee: (unassigned) = Miguel Ruiz (mruiz)
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
After walking away last night angry and disgusted about the state of
vnc4 support in Ubuntu, it occurred to me that I could the regular
Debian version of the package.
I obtained the Debian source package for vnc4 for lenny from:
http://packages.debian.org/source/lenny/vnc4
I then manually
On Sun, 2009-08-16 at 10:52 +, Iain Lane wrote:
Doesn't build for me. Can you have a look?
Checking for source dependency conflicts...
E: Couldn't find package mesa-swx11-source
Installing positive dependencies: debhelper zlib1g-dev automake1.9 autoconf
xserver-xorg-dev xutils
Has anyone been able to build this package on Jaunty? How did a package
that doesn't even build end up in the distribution? This should be
embarrassing for Canonical.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of
Iain: See Tomer's comment above (#21) on how to handle the mesa-
swx11-source dependency issue.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Doesn't build for me. Can you have a look?
Checking for source dependency conflicts...
E: Couldn't find package mesa-swx11-source
Installing positive dependencies: debhelper zlib1g-dev automake1.9 autoconf
xserver-xorg-dev xutils pkg-config x11proto-bigreqs-dev x11proto-composite-dev
Ok so in the mean time, I have a debdiff based on the patch that Dossy
Shiobara upleaded. Hopefully it can be included for Karmic. It needs to
be tested on AMD64 (the original patch works, so it should be fine, but
this was my first packaging job so who knows?) and approved by the
Ubuntu Sponsors.
Ok so in the mean time, I have a debdiff based on the patch that Dossy
Shiobara uploaded. Hopefully it can be included for Karmic. It needs to
be tested on AMD64 (the original patch works, so it should be fine, but
this was my first packaging job so who knows?) and approved by the
Ubuntu Sponsors.
It seems that even debian hasn't had a newer version of vnc4 for a
while, thus a sync request from debian is currently not possible. I'll
forward this bug to debian and see what happens.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because
** Bug watch added: Debian Bug tracker #536203
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536203
** Also affects: vnc4 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536203
Importance: Unknown
Status: Unknown
--
amd64 vncconfig crashes
Does anyone have the fix/workaround for Ubuntu 9.04? tomer t's
procedure for involves downloading mesa-swx11-source for 8.10, but there
is no mesa-swx11-source for 9.04.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member
** Bug watch added: Red Hat Bugzilla #179635
https://bugzilla.redhat.com/show_bug.cgi?id=179635
** Also affects: vnc4 (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=179635
Importance: Unknown
Status: Unknown
** Tags added: bitesize patch
--
amd64 vncconfig crashes
** Changed in: vnc4 (Fedora)
Status: Unknown = Fix Released
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you, Tomer!
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On my system
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION=Ubuntu 8.10
Here's a modified procedure based on the above that successfully created the
package
The build-dep command aborted complaining about unmet dependency of package
I'm unable to build the vnc4server source on Intrepid, following Patrick's
procedure (the Hardy procedure should not be that different from Intrepid).
I get the following error:
ccess.c: In function 'LocalClientCredAndGroups':
access.c:1459: error: storage size of 'peercred' isn't known
I applied the Fedora patch, built from source, and installed, and now
everything works -- many, many thanks.
However, now the Update Manager is convinced that I need to update
vnc4server. Is there a way to convice it that vnc4server is up-to-date?
--
amd64 vncconfig crashes
The problem is still there in Intrepid. The version hasn't changed, so I
guess that would explain it. :p
This bug renders the vnc4server package useless.
Thanks for the patch though, Patrick. It allows me to run vnc4server
anyway. (However, 8-bit characters in the clipboard - åäö - doesn't seem
Thanks Patrick, we followed your instructions for the Dossy patch and
it's working fine now.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks Patrick. That fixed the problem. Still cannot understand why
we're waiting for an official fix given the fact a solution has existed
since April 2008!!
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Thankfully, since nothing has changed in vnc4server, Dossy Shiobara's
Gutsy patch (above) also works just fine for Hardy. I followed a
slightly different procedure:
- Download Dossy's vnc4-amd64-vncconfig-bug-119982.patch above
- Become root
- Make sure /etc/apt/sources.list has a deb-src line
Ditto. This is (still!) broken on amd64 Hardy. Even though the bug was
diganosed and fixed in Fedora in Oct 2006 and on this ticket Oct 2007.
Does Ubuntu have a VNC maintainer?
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are
It was actually reported on June 12, 2007 (ie a year and a day ago). I
don't know how you actually get bugs like this fixed where the program
crashes so any changes won't make things worse. (I have another bug in
another package again with a one line fix otherwise the program crashes
and it too
Is there a patch for this failure (vncconfig) for amd64 Hardy?
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu 8.04
I'm still seeing this problem with all the updates applied.
--
amd64 vncconfig crashes
I just applied the patch on Gutsy amd64, and I'm happy to say that after
restarting vnc4server, vnc4config now works as expected. Thanks for
linking to the patch!
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of
It would be nice if the Ubuntu folks actually applied the fix. The
program is obviously broken, enough people have seen it, and Redhat have
confirmed it and the fix. The issue has been present in 3 Ubuntu
releases and now looks like it will also be present in Hardy. Sadly
this isn't an isolated
The vnc4 package no longer builds on Hardy. See bug 184225. That's why
this won't be fixed unless that bug gets fixed.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For folks who at least want this fix on Gutsy, I'm uploading a patch.
To apply, follow these steps:
$ apt-get source vnc4server
$ dpkg-source -x vnc4_4.1.1+xorg1.0.2-0ubuntu6.dsc
$ apt-get build-dep vnc4server
$ patch -p0 /path/to/vnc4-amd64-vncconfig-bug-119982.patch
$ cd vnc4-4.1.1+xorg1.0.2
$
This problem still exists in Gutsy 64 bit. I linked to the two line fix
in the description (move a #include to earlier in the file). I'll try
to update the metadata for this ticket. For importance, the program
doesn't even run. And it is very confirmed - just try running it!
** Changed in:
** Changed in: vnc4 (Ubuntu)
Assignee: Ubuntu Server Team (ubuntu-server) = (unassigned)
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
hm, ok ... so what am I to do to stop my users from complaining?
simply installing a newer package won't work:
dpkg: dependency problems prevent configuration of vnc4server:
vnc4server depends on libc6 (= 2.6-1); however:
Version of libc6 on system is 2.3.6-0ubuntu20.5.
vnc4server depends on
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION=Ubuntu 6.06.1 LTS
neither feisty nor gutsy contains a newer version of vnc. as far as
google took me it seems like there are problems with the amd64 build.
--
amd64 vncconfig crashes
On Thu, Oct 18, 2007 at 03:05:51PM -, Jörn Dreyer wrote:
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION=Ubuntu 6.06.1 LTS
Thanks for that.
neither feisty nor gutsy contains a newer version of vnc. as far as
google took me it
upstream has released a new version. is there a package availiable
somewhere?
** Changed in: vnc4 (Ubuntu)
Assignee: (unassigned) = Ubuntu Server Team (ubuntu-server)
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a
Happens here too:
$ uname -a
Linux shaun 2.6.15-29-amd64-server #1 SMP Wed Aug 29 14:03:12 UTC 2007 x86_64
GNU/Linux
$ dpkg -s vnc4server
Maintainer: Ola Lundqvist [EMAIL PROTECTED]
Architecture: amd64
Source: vnc4
Version: 4.1.1+xorg1.0.2-0ubuntu1.6.06
** Changed in: vnc4 (Ubuntu)
** Changed in: vnc4 (Ubuntu)
Sourcepackagename: None = vnc4
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
50 matches
Mail list logo
