Qt::SystemTrayIcon::isSystemTrayAvailable() segfault

[Marc Bowes]

$ irb
irb(main):001:0> require 'Qt4'
=> true
irb(main):002:0> Qt::SystemTrayIcon::isSystemTrayAvailable()
(irb):2: [BUG] Segmentation fault
ruby 1.8.7 (2009-06-12 patchlevel 174) [i486-linux]

ProblemType: Bug
Architecture: i386
Date: Sun Oct 18 13:38:38 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: libqt4-ruby 4:4.3.2-0ubuntu3
PackageArchitecture: all
ProcEnviron:
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdebindings
Uname: Linux 2.6.31-14-generic i686

[Terence Simpson (tsimpson)]

This seems to be caused by a NULL pointer being passed as a Display*. I'm not sure this counts as a bug though, as a QApplication was not created, so it was not initialized.

irb(main):001:0> require 'Qt'
=> true
irb(main):002:0> app = Qt::Application.new []
=> #<Qt::Application:0xb61f6a60 objectName="irb">
irb(main):003:0> Qt::SystemTrayIcon::isSystemTrayAvailable()
=> true
irb(main):004:0>

[Terence Simpson (tsimpson)]

This is a backtrace from ruby

[Marc Bowes (marcbowes)]

What is the C++ behaviour if no QApplication is made? Surely it doesn't segfault as well?

[Terence Simpson (tsimpson)]

This is an issue with Qt not being properly initialized before using a QObject, however it would be better if Ruby did not crash on this.
For that reason I'm closing this bug, but I have reported it to KDE: http://bugs.kde.org/show_bug.cgi?id=210991

[Terence Simpson (tsimpson)]

Actually, the C++ version does segfault:
#include <QtGui>

int main(int argc, char** argv) {
    QSystemTrayIcon::isSystemTrayAvailable();
}

$ ./a.out
Segmentation fault

[Marc Bowes (marcbowes)]

Thanks. That sounds reasonable to me.