|
Bugzilla – Full Text Bug Listing |
| Summary: | vnc Server sigabrt by connection with client | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Martin Funke <mf> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <kde-maintainers> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Martin Funke
2007-01-11 11:27:55 UTC
Could you please more verbose what you are doing exactly? I installed a new system suse 10.1 (so 10.2) with KDE. The VNC Server running under KDE and I configured krfb for further activities. But in the moment when I've logged in (from Windows XP with real VNC or Tight VNC) the issue appears and the connection brakes. This Issue first appeared with #10.1 followed by #10.2. A connection with VNC what's not krfb (vncserver started from console) is no problem. BR Martin Funke Since it only occurs with krfb and not with plaing VNC it's KDE specific. Reasssiging. Subject: https://bugzilla.novell.com/show_bug.cgi?id=233567 From: Martin Funke <mf@protokolltester.de> To: "sndirsch@novell.com" <sndirsch@novell.com> Date: Mon, 15 Jan 2007 10:48:00 +0000 https://bugzilla.novell.com/show_bug.cgi?id=233567 Hello, the issue is only under KDE with krfb. Please close this case if needed. Please give me an info, where I have to report the issue to, that it will be solved? Thank's and regards Martin Funke I tried to use krfb under kde. does the kde machine run nvidia driver? there was another bugreport about it that I could reproduce with the nvidia driver (it seems it doesn't like to get polled about mouse cursor position too often). I have an "ATI 3D RAGE IIC AGP" - Card. I don't use a special driver. With version 10.0 krfb ran. The Issue began with 10.1 / 10.2 *** This bug has been marked as a duplicate of bug 192419 *** |