Ubuntu
vnc4 package

vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick

Bug #247669 reported by Bill Loucks
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
vnc4 (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Hardy by gcc
Nominated for Intrepid by Bill Loucks

Bug Description

Binary package hint: vnc4server

Using the libvnc.so module in Xorg 1.4.

On first keypress or mouseclick by vnc client, Xorg log on vnc server
side shows:

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x483d5a]
1: /lib/libc.so.6 [0x2aeb4a768100]
2: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop8keyEventEjb+0x8b) [0x2aeb4cd1838b]
3: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST8keyEventEjb+0x103) [0x2aeb4cd2f213]
4: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST15processMessagesEv+0x30) [0x2aeb4cd2f300]
5: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop13wakeupHandlerEP6fd_seti+0xf6) [0x2aeb4cd17c06]
6: /usr/lib/xorg/modules/extensions//libvnc.so [0x2aeb4cd0fdd9]
7: /usr/bin/X11/X(WakeupHandler+0x4e) [0x4526ee]
8: /usr/bin/X11/X(WaitForSomething+0x204) [0x560e04]
9: /usr/bin/X11/X(Dispatch+0x9a) [0x44e8aa]
10: /usr/bin/X11/X(main+0x47d) [0x436c1d]
11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2aeb4a7541c4]
12: /usr/bin/X11/X(FontFileCompleteXLFD+0x279) [0x435f59]

Fatal server error:
Caught signal 11. Server aborting

From the Debian bug 444697, there apparently is an ABI change in Xorg 1.4 that breaks this. The xorg-xerver bits in this package are too old (1.0.2) to work with 1.4.1 that is in the xserver-xorg-core package now.

Be advised that Debian bug 444697 "fixes" this bug by REMOVING libvnc.so. Quote:
"Removed libvnc.so that do not work with recent xorg. This is a workaround but solves the grave fault, closes: #444697."

This tacitly suggests that Xorg does not support libvnc.so at this time. In any case bug 444697 does not solve the problem. Debian merely removed the feature that fails and closed the bug. From a project management standpoint, the non-working libvnc.so is now orphaned and completely untracked (there is no bug I can find that tracks non-working libvnc.so). The closing of Debian bug 444697 implies it was fixed when it was not.

Revision history for this message
In , Aleksey (aleksey-redhat-bugs) wrote :
Download full text (4.1 KiB)

Description of problem:

I have the vnc module enabled in my xorg.conf. If I use VNC from the beginning
of an X session, everything works fine. If I use X on the console for a while
and then connect to that same session via VNC, the session crashes...

Version-Release number of selected component (if applicable):

vnc-server-4.1.2-9.el5
xorg-x11-server-Xorg-1.1.1-48.13.0.1.el5

How reproducible:
Close to 100%. I have been doing this on 3 machines - a work machine with RHEL5
and two home machines with CentOS 5 and see this on all 3 (even though xorg.conf
are all somewhat different).

Steps to Reproduce:
1. Include the vnc module in xorg.conf
2. Restart X and use in on the console for a while
3. Make sure the right VNC parameters are enabled to allow VNC logins (use
vncconfig, if necessary)
4. Open a VNC connection to the X session.

Actual results:
X.org crashes. Here is the crash report in Xorg.0.log on the RHEL5 machine with
all updates:

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80bc1b1]
1: [0x302420]
2: /lib/libc.so.6(memcpy+0x1c) [0x4af9ca6c]
3: /usr/lib/xorg/modules/libfb.so(fbBlt+0x90e) [0x3fb39e]
4: /usr/lib/xorg/modules/libfb.so(fbBltStip+0x73) [0x3fb8c3]
5: /usr/lib/xorg/modules/libfb.so(fbGetImage+0x23a) [0x40b11a]
6: /usr/lib/xorg/modules/libxaa.so [0x1be2a2]
7: /usr/bin/Xorg [0x81088e8]
8: /usr/bin/Xorg [0x815b2a3]
9: /usr/bin/Xorg [0x811d4fd]
10:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN14XserverDesktop10grabRegionERKN3rfb6RegionE+0x12a)
[0x291c9a]
11:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb11VNCServerST11checkUpdateEv+0x1b7)
[0x29d457]
12:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST22writeFramebufferUpdateEv+0x5c)
[0x2ac8ec]
13:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST24framebufferUpdateRequestERKNS_4RectEb+0xbf)
[0x2ad1ef]
14:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb10SMsgReader28readFramebufferUpdateRequestEv+0x14f)
[0x2b3bcf]
15:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb12SMsgReaderV37readMsgEv+0x14a)
[0x2a83da]
16:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb11SConnection10processMsgEv+0x14f)
[0x2a7d7f]
17:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST15processMessagesEv+0x48)
[0x2abf18]
18:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN3rfb11VNCServerST18processSocketEventEPN7network6SocketE+0x3f)
[0x29d20f]
19:
/usr/lib/xorg/modules/extensions/libvnc.so(_ZN14XserverDesktop13wakeupHandlerEP6fd_seti+0xd4)
[0x291154]
20: /usr/lib/xorg/modules/extensions/libvnc.so [0x2893ec]
21: /usr/bin/Xorg(WakeupHandler+0x59) [0x808c169]
22: /usr/bin/Xorg(WaitForSomething+0x1b9) [0x81a0849]
23: /usr/bin/Xorg(Dispatch+0x8d) [0x8087f9d]
24: /usr/bin/Xorg(main+0x485) [0x806fa35]
25: /lib/libc.so.6(__libc_start_main+0xdc) [0x4af44dec]
26: /usr/bin/Xorg(FontFileCompleteXLFD+0x1e9) [0x806ed71]

Fatal server error:
Caught signal 11. Server aborting

Expected results:
VNC session starts

Additional info:
My xorg.conf:

Section "ServerLayout"
   Identifier "Default Layout"
   Screen 0 "Screen0" 0 0
   InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
   Identifier "Keyboard0"
   Driver...

Read more...

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

I'm not able to reproduce this one. Could you tell me if crash is reproducible
without "dri" module, please? Also better should be specify vnc module options
in Screen section.

Section "Screen"
        Identifier "..."
        Device "..."
        DefaultDepth ...
        Option "SecurityTypes" "VncAuth"
        Option "PasswordFile" "/root/.vnc/passwd"
        SubSection "..."
        EndSubSection
EndSection

Also attach your complete /var/log/Xorg.<display>.log and specify your
architecture, please

Thanks, Adam

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

I am seeing this issue as well, very reproducible on my Dell 2950 server with
the stock RHEL5.1 ati driver and vnc-server packages.

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x4a0921]
1: /lib64/libc.so.6 [0x315ac300b0]
2: /usr/bin/Xorg [0x4c28aa]
3: /usr/lib64/xorg/modules/libxaa.so [0x2aaaada10da7]
4: /usr/bin/Xorg [0x510449]
5: /usr/bin/Xorg [0x4d5ebc]
6:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN14XserverDesktop10grabRegionERKN3rfb6RegionE+0x106)
[0x2aaaac26e346]
7:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN3rfb11VNCServerST11checkUpdateEv+0x182)
[0x2aaaac2782a2]
8:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST22writeFramebufferUpdateEv+0x96)
[0x2aaaac285ee6]
9:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST24framebufferUpdateRequestERKNS_4RectEb+0xa6)
[0x2aaaac286606]
10:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN3rfb10SMsgReader28readFramebufferUpdateRequestEv+0x180)
[0x2aaaac28bb80]
11:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN3rfb16VNCSConnectionST15processMessagesEv+0x30)
[0x2aaaac285520]
12:
/usr/lib64/xorg/modules/extensions/libvnc.so(_ZN14XserverDesktop13wakeupHandlerEP6fd_seti+0xf0)
[0x2aaaac26dcc0]
13: /usr/lib64/xorg/modules/extensions/libvnc.so [0x2aaaac265ae9]
14: /usr/bin/Xorg(WakeupHandler+0x51) [0x44daa1]
15: /usr/bin/Xorg(WaitForSomething+0x1d4) [0x5509c4]
16: /usr/bin/Xorg(Dispatch+0x9a) [0x449b4a]
17: /usr/bin/Xorg(main+0x455) [0x4325b5]
18: /lib64/libc.so.6(__libc_start_main+0xf4) [0x315ac1d8a4]
19: /usr/bin/Xorg(FontFileCompleteXLFD+0x231) [0x4318a9]

xorg.conf (relevant parts):
Section "Module"
        Load "dbe"
        Load "extmod"
        Load "fbdevhw"
        Load "glx"
        Load "record"
        Load "freetype"
        Load "type1"
        Load "dri"
        Load "vnc"
EndSection

Section "Device"
        Identifier "Videocard0"
        Driver "ati"
        VendorName "Videocard vendor"
        BoardName "ATI ES1000"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device "Videocard0"
        Monitor "Monitor0"
        DefaultDepth 16
        SubSection "Display"
                Viewport 0 0
                Depth 16
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        Option "SecurityTypes" "VncAuth"
        Option "passwordFile" "/etc/vnc/passwd"
EndSection

Pretty much makes VNC unusable.

Revision history for this message
In , Aleksey (aleksey-redhat-bugs) wrote :

Tom, could you try responding to Adam's questions (dri, etc) in comment #1? I
did not have a chance to test that (I ended up switching to x11vnc instead of
using the vnc module). Thanks!

P.S. Marking "Version: 5.1" per Tom's comment.

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

I disable the dri and glx modules in my xorg.conf and so far it hasn't crashed.
 I guess I'll need to test with each one disabled individually and spend a few
hours without it crashing before I know for sure.

Thanks,
Tom

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Created attachment 280481
Patch to fix crash in vnc.so module

I lifted the patch directly from the vnc-server-4.1.2-19.fc7.src.rpm. This
single patch applied to the tree seems to resolve the issue for me.

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

(In reply to comment #4)
> I disable the dri and glx modules in my xorg.conf and so far it hasn't crashed.
> I guess I'll need to test with each one disabled individually and spend a few
> hours without it crashing before I know for sure.

Unfortunately disable DRI didn't completely fix the issue. However, I've got a
nearly perfectly reproducible test case with one of our applications. The
application is nothing special, just a commercial backup program (Netvault from
a company called Bakbone). Opening the job window in this application,
maximizing it, and then closing the window causes the crash every time.

I've attached a patch which I pulled from the most recent FC7 version of the
package which seems to fix the issue for me. After rebuilding the RHEL5 4.1.2-9
version of the vnc package with only this single patch added I've found the
server to run stable.

I've got a patched src.rpm and binaries for x86 and x86_64 if anyone else wants
to test.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

Thank you for your report. I think best should be rebase RHEL5 Xvnc to F7 vnc
(bug #385241) because it is more stable. I'm going to try put attached patch to
next vnc update.

Adam

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

(In reply to comment #7)
> Thank you for your report. I think best should be rebase RHEL5 Xvnc to F7 vnc
> (bug #385241) because it is more stable. I'm going to try put attached patch to
> next vnc update.

I'm sure it's probably true that the better option is to rebase, however, you
also state in that bug that this is not likely to happen before RHEL5U3. From a
user perspective that's likely to be a year away and potentially longer (U1 took
9 months).

I would hope that a bugfix can get in faster as the vnc.so module as currently
shipped is basically unusable. It's unrealistic to expect customers to wait for
two years for a working VNC, especially when it worked fine with previous
releases of RHEL.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

*** Bug 251165 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Alan (alan-redhat-bugs) wrote :

I'd like to add my voice to those requesting a workaround for this issue. I can
reproduce this issue pretty much at will, and have tried recompiling the EL5.1
vnc-server package with the above patch from Tom S. In my case, it did not
resolve the issue that I'm having.

I don't have the DRI module in my xorg.conf, and I've tried with and without the
GLX module loading. No difference. In my case, I can crash the X server on the
VNC server machine within about 10 seconds of logging in.

I concur that although a rebase is the best solution, the fact that it won't
come before U3 and U2 isn't even out yet means that we need some other workaround.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

Workaround for this bug doesn't exist. I have experience that disable composite
and render extension sometimes help but sometimes no. I'm going to attach patch
for this issue which lives in Fedora and solves this problem

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

Created attachment 299134
Patch which validates framebuffer bounds before framebuffer dump

Anyone can apply this patch with above patch to solve this problem. Final patch
might differ (some optimizations etc)

Revision history for this message
In , Alan (alan-redhat-bugs) wrote :

I recompiled from the vnc-4.1.2-9.el5.src.rpm incorporating the above patch
(id=299134 from comment #13) and I'm happy to report that it seems to have
resolved my issue. I tried the resulting RPM on two machines which had been
crashing within 10-15 seconds of login and both stayed up for the 5 minutes that
I tested them.

Thanks for your diligence! Hopefully this patch can make it into a release
version soon, and the mentioned rebase will happen in the none-too-distant future.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

Thanks for your positive feedback. But this update is not scheduled to 5.2 . I
think it will be in 5.3

Revision history for this message
In , RHEL (rhel-redhat-bugs) wrote :

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
release.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

*** Bug 240379 has been marked as a duplicate of this bug. ***

Revision history for this message
Ben (abnormaliti) wrote :

Red Hat have patches in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=282661

gcc (chris+ubuntu-qwirx)
Changed in vnc4:
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in vnc4:
status: Unknown → Fix Committed
Revision history for this message
ivanbev (ivan-beveridge) wrote :

Is there any news on this yet? I hate to add a 'me too' comment to things, but haven't seen any follow-up to the comment that redhat seem to have patches that fix the issue.

Thanks in advance - Ivan

Revision history for this message
Bill Loucks (biloucks) wrote :

On September 30, 2008, Mike Milligan wrote to me saying, "Neither one of those patches [in Red Hat Bug 282661] appear to address the INPUT module ABI change that is the problem in Ubuntu/Debian. With Hope in my back pocket, I did pull the RealVNC 4.1.2 source and tried to build it on Intrepid, but there are a ton of problems with it. I've also in the past tried to build xf4vnc, but that also has a ton of build problems related to Xorg 1.4 restructuring. I just don't have time to deal with this, the build issues are more than just "tweaks", much as I'd like to get it working too. I'm just using vino-server in the meantime, which suites my needs."

Revision history for this message
In , errata-xmlrpc (errata-xmlrpc-redhat-bugs) wrote :

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0119.html

Bug Watch Updater (bug-watch-updater)
Changed in vnc4:
status: Fix Committed → Fix Released
Revision history for this message
Bill Loucks (biloucks) wrote :

Regarding the status change to "Fix Released in vnc4 (Fedora)": As an Ubuntu 8.04 Hardy user, I'd like to know when the Fedora fix will be put into Ubuntu 8.04 (Hardy) and Ubuntu 8.10 (Intrepid).

Revision history for this message
Bill Loucks (biloucks) wrote :

TigerVNC ( http://www.tigervnc.com/ ) appears to be doing exactly what we need: providing a libvnc.so which works with the newer modular Xorg versions (1.4 and higher). TigerVNC is planned for release with Fedora Core 11. Let's just hope we can interest some Ubuntu developers in building it against Ubuntu 8.04 "Hardy" and 8.10 "Intrepid" and 9.04 "Jaunty".

Revision history for this message
goblinhack (goblinhack) wrote : Re: [Bug 247669] Re: vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick

Sounds great - thanks for highlighting it

Neil

2009/3/23 William Loucks <email address hidden>:
> TigerVNC ( http://www.tigervnc.com/ ) appears to be doing exactly what
> we need: providing a libvnc.so which works with the newer modular Xorg
> versions (1.4 and higher). TigerVNC is planned for release with Fedora
> Core 11. Let's just hope we can interest some Ubuntu developers in
> building it against Ubuntu 8.04 "Hardy" and 8.10 "Intrepid" and 9.04
> "Jaunty".
>
> --
>  vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
> https://bugs.launchpad.net/bugs/247669
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “vnc4” source package in Ubuntu: Confirmed
> Status in “vnc4” source package in Fedora: Fix Released
>
> Bug description:
> Binary package hint: vnc4server
>
> Using the libvnc.so module in Xorg 1.4.
>
> On first keypress or mouseclick by vnc client, Xorg log on vnc server
> side shows:
>
> Backtrace:
> 0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x483d5a]
> 1: /lib/libc.so.6 [0x2aeb4a768100]
> 2: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop8keyEventEjb+0x8b) [0x2aeb4cd1838b]
> 3: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST8keyEventEjb+0x103) [0x2aeb4cd2f213]
> 4: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST15processMessagesEv+0x30) [0x2aeb4cd2f300]
> 5: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop13wakeupHandlerEP6fd_seti+0xf6) [0x2aeb4cd17c06]
> 6: /usr/lib/xorg/modules/extensions//libvnc.so [0x2aeb4cd0fdd9]
> 7: /usr/bin/X11/X(WakeupHandler+0x4e) [0x4526ee]
> 8: /usr/bin/X11/X(WaitForSomething+0x204) [0x560e04]
> 9: /usr/bin/X11/X(Dispatch+0x9a) [0x44e8aa]
> 10: /usr/bin/X11/X(main+0x47d) [0x436c1d]
> 11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2aeb4a7541c4]
> 12: /usr/bin/X11/X(FontFileCompleteXLFD+0x279) [0x435f59]
>
> Fatal server error:
> Caught signal 11. Server aborting
>
> >From the Debian bug 444697, there apparently is an ABI change in Xorg 1.4 that breaks this. The xorg-xerver bits in this package are too old (1.0.2) to work with 1.4.1 that is in the xserver-xorg-core package now.
>
> Be advised that Debian bug 444697 "fixes" this bug by REMOVING libvnc.so. Quote:
> "Removed libvnc.so that do not work with recent xorg. This is a workaround but solves the grave fault, closes: #444697."
>
> This tacitly suggests that Xorg does not support libvnc.so at this time. In any case bug 444697 does not solve the problem. Debian merely removed the feature that fails and closed the bug. From a project management standpoint, the non-working libvnc.so is now orphaned and completely untracked (there is no bug I can find that tracks non-working libvnc.so). The closing of Debian bug 444697 implies it was fixed when it was not.
>

Revision history for this message
Bill Loucks (biloucks) wrote :

Adam Tkac of Red Hat, Inc. writes: "I think binary packages for [TigerVNC for] Ubuntu will be available when 1.0.0 will be released. Unfortunately I can't guarantee that libvnc.so will be available as well. Situation around libvnc.so is very difficult because it depends on distribution Xorg so the most preferred way how to get libvnc.so working is open the bug report (or RFE, not sure how Ubuntu community calls it). Then your distributor will tune TigerVNC to match distribution Xorg and ship prebuild packages."

Revision history for this message
Steve Dodd (anarchetic) wrote :

I've just built the latest tightvnc (1.2.x) for lucid, and the included libvnc.so seems to be working fine. I had to apply a couple of tiny patches to the xserver:

http://cgit.freedesktop.org/xorg/xserver/commit/?id=626f97688a89dbc5da80390d822d21b1a737de0e
http://cgit.freedesktop.org/xorg/xserver/commit/?id=2f29b163bbdebe384c24f781bb97b446959e8f4c

I did my build by hand, and the process as it stands seems to involve adding the vnc module to a copy of the xserver source tree and rebuilding. If someone better acquainted with the xserver source could get the above patches applied to the Ubuntu tree and package tightvnc, that would be fantastic..

I will try to attach a copy of my xserver binary package and the libvnc.so..

Revision history for this message
Steve Dodd (anarchetic) wrote :

In above comment, please read "tigervnc" for "tightvnc", sorry. Attached is the libvnc.so I built..

Revision history for this message
penalvch (penalvch) wrote :

Bill Loucks, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. If this is reproducible in a supported release, 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 && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in vnc4 (Ubuntu):
status: Confirmed → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in vnc4 (Fedora):
importance: Unknown → High
penalvch (penalvch)
no longer affects: vnc4 (Ubuntu)
affects: vnc4 (Fedora) → vnc4 (Ubuntu)
Changed in vnc4 (Ubuntu):
importance: High → Undecided
status: Fix Released → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.