Tristan Greaves, thank you for reporting this and helping make Ubuntu better.
However, your crash report is missing. Please follow these instructions to have
apport report a new bug about your crash that can be dealt with by the
automatic retracer. First, execute at a terminal:
cd /var/crash
I downloaded the source for 1.3.10, built it using the instructions in
the documentation section under linux/unix installation, installed the
xutils-dev, libx11-dev and was able to build Xvnc which I copied into
/usr/bin/Xtightvnc. This seemed to provide a more reliable experience.
I do not
Yes, tightvnc-1.3.9 has problems with its handling of some 64-bit
values. See patch
http://sourceforge.net/tracker/?func=detailaid=2570977group_id=14067atid=314067
for details. The patch was incorporated into 1.3.10.
** Bug watch added: SourceForge.net Tracker #2570977
Follow on to above.
The tightvnc web site has a more recent version than what's in Ubuntu --
version 1.3.10. Newest in Ubuntu is 1.3.9. I downloaded the 1.3.10
tightvncserver source directly from
http://www.tightvnc.com/download.html and it seems to have fixed the
crashing problem.
If you go
I get this tightvncserver crash all the time and it's really annoying.
Typically the server will run from 1 to 24 hours before crashing. I've
verified that it happens on my machine (x86_64 running Ubuntu 8.04 LTS,
icewm window manager) with both the tightvncserver version 1.2.9-22 that
ships with
I am running Xtightvnc as a subproces to Xrdp on a 64bit machine. I am
seeing the same problem as Tristan. The connection is established and
everything is working fine. Until, for no apparent reason, Xtightvnc
crashes, taking the connection and all started programs with it. I had
it happen to
** Package changed: metacity (Ubuntu) = ubuntu
--
Crashes under tightvncserver, brings down X session
https://bugs.launchpad.net/bugs/344264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Interestingly, adjusting the /usr/bin/tightvncserver script back to its
default geometry of 1024x768 appears to have fixed this issue. I do,
however, need to start metacity manually still to get the ability to
move windows. But it does not crash...
The geometry was 1280x1024 with a dept of 24
I spoke too soon. It just took longer to crash. THis time when in the
middle of entering something into a text field.
Mar 17 15:16:43 petrucci bonobo-activation-server (tmg-29940): could not
associate with desktop session: Failed to connect to socket /tmp/dbus-
DcGBNpuwrS: Connection refused
[
crash occurs on tightvnc not in metacity. rejecting this task.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
Crashes under tightvncserver, brings down X session
https://bugs.launchpad.net/bugs/344264
You received this bug notification because you are a member of Ubuntu
Bugs,
10 matches
Mail list logo
