Bug 90322 - konqueror doesn't start on displays without all extensions.
Summary: konqueror doesn't start on displays without all extensions.
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-27 13:37 UTC by Erik forsberg
Modified: 2004-10-12 13:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik forsberg 2004-09-27 13:37:15 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    SuSE RPMs
OS:                Linux

Running konqueror via Xvnc, konqueror won't start. Instead, it hangs with the following message:

# konqueror
Xlib:  extension "XInputExtension" missing on display ":1.0".
Failed to get list of devices

The display's xdpyinfo is appended later in this report.

konqueror doesn't display any window, but instead hangs for a very long time, possibly forever.

According to some reports on the net, this problem also occurs when running konqueror via X forwarding in ssh, when the display is on a Mac OS X display. This leads to the theory that konquerorer needs some X extension that isn't available. See the xdpyinfo output below for a list of available X extensions.

This bug is a problem in Linux Terminal Server solutions based on Xvnc. Upgrading to KDE 3.3 seems to solve the problem, but that is not an option in some cases (bug also exists on SuSE Linux Enterprise Server 9, and a lot of sites want to run a supported release of KDE on that platform).

name of display:    :1.0
version number:    11.0
vendor string:    AT&T Laboratories Cambridge
vendor release number:    3332
maximum request size:  4194300 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    2
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x380000b, revert to PointerRoot
number of extensions:    7
    BIG-REQUESTS
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    SHAPE
    SYNC
    XC-MISC
    XTEST
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1024x760 pixels (347x257 millimeters)
  resolution:    75x75 dots per inch
  depths (1):    16
  root window id:    0x25
  depth of root window:    16 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x21
  default number of colormap cells:    64
  preallocated pixels:    black 0, white 65535
  options:    backing-store YES, save-unders YES
  largest cursor:    1024x760
  current input event mask:    0xda4031
    KeyPressMask             EnterWindowMask          LeaveWindowMask          
    KeymapStateMask          StructureNotifyMask      SubstructureNotifyMask   
    SubstructureRedirectMask PropertyChangeMask       ColormapChangeMask       
  number of visuals:    1
  default visual id:  0x22
  visual:
    visual id:    0x22
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    8 bits
Comment 1 Erik forsberg 2004-10-04 10:56:57 UTC
By removing 

Patch57:      konq-init-XThreads.diff

..from the source rpm and rebuilding, or by setting XMODIFIERS to something bogus, this problem can be worked around.

This seems to be a SuSE-only bug.
Comment 2 Lubos Lunak 2004-10-12 13:33:09 UTC
Not KDE problem. Also, the patch seems to have been removed from latest SUSE packages.