On Saturday 27 July 2002 10:08 am, you wrote: > On July 26, 2002 07:49 am, Maks Orlovich wrote: > > On Friday 26 July 2002 04:51 am, Geoffrey Lee wrote: > > > > I thought was hi-color KDE, but going in and switching it > > > > helped. And if I switch it to KDE Default, it fails with: > > > > > > > > fcntl: Bad file descriptor > > > > fcntl: Bad file descriptor > > > > IIRC, this one is a Qt buglet; there is a patch in qt-copy in KDE CVS > > for that. > > > > > A quick search of the qt-gui and Licq daemon source code: > > > > > > The only place I could find with a fcntl() call was in the main > > > Licq daemon $(topdir)/src to set a non-blocking socket. Nope. Most > > > probably it's not this one. > > > > And I just realized why default can be behaving this way; in short, > > can you please try to rename /usr/lib/kde3/plugin/styles/highcolor.so > > to default.so and try to see whether if you turn on the plain default > > it still crashes? > > Moved highcolor.so to default.so, changed the style to 'Default KDE > style' and it doesn't crash. Switch it back and it does.
Thanks, that kind of makes sense. The partial explanation: when Qt is told to load a style, it tries to do a similarity check, to try to guess the correct one. "default" and "highcolor" are normally both in highcolor.so -- so when opening highcolor, guessing the right plugin is no big deal, but "default" looks like nothing like highcolor.so, so likely a couple incorrect tries are first made; the renaming has reversed that... The plugin likely getting opened is kthemestyle.so (which I maintain), the pixmap style engine, which is the only one that links to kdecore -- doing which tends to trigger a whole bunch of ld.so bugs, some of which are worked around in the plugin's code... An important question to ask is thus: what version of the glibc package do you have installed? Thanks, Maks Orlovich
