Bug 143605 - [KDE3] krfb crashes upon connect to desktop running 1600x1200 resolution
Summary: [KDE3] krfb crashes upon connect to desktop running 1600x1200 resolution
Status: RESOLVED WORKSFORME
Alias: None
Product: krfb
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: George Goldberg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-29 22:12 UTC by James
Modified: 2021-01-02 04:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James 2007-03-29 22:12:09 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

Trying to connect to a Novell SLED (Suse) desktop running at 1600x1200 for the desktop, any vnc client attempting to connect to it has failed in the sense that krfb crashes very very shortly after the connection is made, graphics start to come up and any action is taken. Have tried several different vnc clients (realvnc, tighvnc, trying chicken o0f the vnc when i get home) all resulting in the same crash error. 

It is running with the following options currently, however any variation of this (including NOT running in 1600x1200) has resulted in the same crash. 

:42 -inetd -once -query localhost -geometry 1600x1200 -depth 16

Crash detail it provided is below.


System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232374096 (LWP 6018)]
[New Thread -1263756384 (LWP 6028)]
[New Thread -1255363680 (LWP 6027)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6cd2d11 in ___newselect_nocancel () from /lib/libc.so.6
#2  0xb6e77053 in XProcessInternalConnection () from /usr/X11R6/lib/libX11.so.6
#3  0xb6e773ef in _XRead () from /usr/X11R6/lib/libX11.so.6
#4  0xb6e77e94 in _XReply () from /usr/X11R6/lib/libX11.so.6
#5  0xb6f3fb3e in XShmGetImage () from /usr/X11R6/lib/libXext.so.6
#6  0x08055750 in QFrame::paintEvent ()
#7  0x080aabc0 in ?? ()
#8  0x00000063 in ?? ()
#9  0x08230248 in ?? ()
#10 0x00000000 in ?? ()
Comment 1 Justin Zobel 2020-12-03 21:59:54 UTC
Thank you for the report, James.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 2 Bug Janitor Service 2020-12-18 04:34:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2021-01-02 04:34:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!