Bug 210989 - ruby Segmentation fault when Qt is uninitialized
Summary: ruby Segmentation fault when Qt is uninitialized
Status: RESOLVED DUPLICATE of bug 210991
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: Ruby (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-18 18:03 UTC by Terence Simpson
Modified: 2009-10-18 18:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Terence Simpson 2009-10-18 18:03:21 UTC 
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

When Qt is not initialized and a static method of a QObject is called, ruby crashes.
First reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/kdebindings/+bug/454597

Example with irb:
$ irb
irb(main):001:0> require 'Qt4'
=> true
irb(main):002:0> Qt::SystemTrayIcon::isSystemTrayAvailable()
(irb):2: [BUG] Segmentation fault
ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux]

Aborted

This bug is not so much about the method not working as Ruby crashing, it should ideally post an error message indicating and error rather than crashing.
Comment 1 Terence Simpson 2009-10-18 18:08:43 UTC 
Sorry, meant to report this against bindings not kdevelop

*** This bug has been marked as a duplicate of bug 210991 ***