LinuxQuestions.org - Qt4 designer SIGSEGV on -current

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Qt4 designer SIGSEGV on -current (https://www.linuxquestions.org/questions/slackware-14/qt4-designer-sigsegv-on-current-846842/)

Qt4 designer SIGSEGV on -current

Hi all,
I'm new to the forum, but not to Slackware, that I've been using since 1999.

I have a Slackware -current with the latest updates (2010, nov 22nd at time of writing) and the following packages:

qt-4.7.0_7abde40-i486-1
AlienBob's KDE 4.5.3

On my system, qt4 designer SIGSEGV on start. Running gdb against designer executables gives

Code:

Reading symbols from /usr/bin/designer...(no debugging symbols found)...done.

(gdb) run

Starting program: /usr/bin/designer 

[Thread debugging using libthread_db enabled]

[New Thread 0xb0ad5b70 (LWP 16335)]

[New Thread 0xad8d6b70 (LWP 16336)]



Program received signal SIGSEGV, Segmentation fault.

0xb675af5d in QSettings::allKeys() const () from /usr/lib/qt/lib/libQtCore.so.4

I tried several times to get rid of the problem, deleting TrollTech.conf in $HOME, reinstalling qt, reinstalling kde, with no luck at all.

So, my questions are:
someone can confirm this, or I just broke things somehow?
if it is a general problem, someone was able to get rid of it?
Regards,

G.

I'm not an expert on Qt4 design tools but you could try using the Gnome desktop to see if you get the same error. At least it would narrow down the candidates for the fault.

I'm using slackware64-current with the latest changes up to Nov 22, the same qt version but the KDE 4.5.1 official packages from -current, and I can launch /usr/bin/designer without any crashes as a user.

I run my version of current in Virtualbox and it's up to date with the recent changes. Qt designer works fine on this system so maybe KDE 4.5.3 is affecting things. I run the standard current KDE version 4.5.1.

Edit: Sorry for the duplication with rg3's information. I was typing this as he posted.

Thank you all for your answers.

I guess I'll try to downgrade kde packages to official -current version and see what happens.

Regards,

G.

FYI, designer launches fine also here with latest 64-current and alien's kde 4.5.3.

Well, downgrading kde to official 4.5.1 doesn't resolve the issue, I guess I've
broken something installing some other package (I usually build with my own SlackBuilds).

I'll dig further into it and see what's going on.

Thank you all for your interest.

Regards,

G.