This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Segfaulting llike crazy

Tags: None
(comma "," separated)
lunixer
Registered Member
Posts
23
Karma
0

Segfaulting llike crazy

Fri Feb 03, 2012 12:18 am
Pretty much every single time I launch the program now, I get a segmentation fault. I run it under Gnome 3, but I have all of the requisite libraries installed, at least as far as I know. Ubuntu 11.10. When I launch the debug thing, it always says that no useful information is there. Does anybody else know what might be causing this?
cristian.onet
KDE Developer
Posts
253
Karma
2
OS

Re: Segfaulting llike crazy

Fri Feb 03, 2012 6:33 am
Try the following:

Code: Select all
$export QT_ACCESSIBILITY=0 && kmymoney

As you can see Bug #284371 had quite a few reports.


cristian.onet, proud to be a member of KDE forums since 2008-Oct.
lunixer
Registered Member
Posts
23
Karma
0

Re: Segfaulting llike crazy

Fri Feb 03, 2012 10:23 pm
cristian.onet wrote:Try the following:

Code: Select all
$export QT_ACCESSIBILITY=0 && kmymoney

As you can see Bug #284371 had quite a few reports.


Code: Select all
ross@ross-Laptop:~$ $export QT_ACCESSIBILITY=0 && kmymoney
QT_ACCESSIBILITY=0: command not found
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS

Re: Segfaulting llike crazy  Topic is solved

Fri Feb 03, 2012 10:47 pm
It's either

Code: Select all
QT_ACCESSIBILITY=0 kmymoney
on a single line or

Code: Select all
export QT_ACCESSIBILITY=0
kmymoney
on two separate lines of the shell


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5
lunixer
Registered Member
Posts
23
Karma
0

Re: Segfaulting llike crazy

Fri Feb 03, 2012 10:48 pm
ipwizard wrote:It's either

Code: Select all
QT_ACCESSIBILITY=0 kmymoney
on a single line or

Code: Select all
export QT_ACCESSIBILITY=0
kmymoney
on two separate lines of the shell


Thanks, that seems to have worked better. It normally segfaults at launch and then I have to kill it and start it again multiple times, but it didn't segfault this time. I'm going to mark this solved, but I hope no one minds if I post a new thread later if the problem crops up again.


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot]