Thanks. That sounds reasonable to me.
--
Qt::SystemTrayIcon::isSystemTrayAvailable() segfault
https://bugs.launchpad.net/bugs/454597
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebindings in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b.
Actually, the C++ version does segfault:
#include
int main(int argc, char** argv) {
QSystemTrayIcon::isSystemTrayAvailable();
}
$ ./a.out
Segmentation fault
--
Qt::SystemTrayIcon::isSystemTrayAvailable() segfault
https://bugs.launchpad.net/bugs/454597
You received this bug notification bec
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
** Bug watch added: KDE Bug Tracking System #2
What is the C++ behaviour if no QApplication is made? Surely it doesn't
segfault as well?
--
Qt::SystemTrayIcon::isSystemTrayAvailable() segfault
https://bugs.launchpad.net/bugs/454597
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebindings
This is a backtrace from ruby
** Attachment added: "backtrace of ruby irb"
http://launchpadlibrarian.net/33904635/backtrace.txt
--
Qt::SystemTrayIcon::isSystemTrayAvailable() segfault
https://bugs.launchpad.net/bugs/454597
You received this bug notification because you are a member of Kubuntu
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 []
=> #
irb(main):003:0> Qt::SystemTrayIcon
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33874367/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33874368/XsessionErrors.txt
--
Qt::SystemTrayIcon::isSystemTrayAvailable() segfault
https://bugs.launchpad.net/bugs/45459
