[arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

older
[arch-general] Does anyone find...

Nigel Henry

5 Mar 2008 5 Mar '08

7:06 p.m.

Hi Folks. When I open Qsynth, I can rotate the various controls, but clicking on any of the buttons causes it to crash. For example I click on the "Options" button, the options window opens momentarily, but is blank, then Qsynth goes out to lunch. When Qsynth is opened without messing with the buttons, Qjackctl shows fluidsynth available as an input port, so that bit is working ok. Starting Qsynth on the CLI gives me this output, see below. [djmons@myhost ~]$ qsynth Warning: no locale found: /usr/share/locale/qsynth_en_US.qm Segmentation fault [djmons@myhost ~]$ I'm totally clueless about locales, but could this be the problem? Looking in /usr/share/locale there is no en_US locale. There are a bunch of en locales though (en, en@boldquot, en@quot, en_CA, en_GB) Looking at when I started Qsynth on the CLI as above, it shows a segfault, but the GUI for Qsynth is still showing. It's only when I click on a button that it crashes. Can anyone confirm that they have Qsynth working as expected? I don't want to post a bug report if this problem has something to do with locales on my install. Thanks for any help on this problem. Nigel.

Show replies by date

charly

5 Mar 5 Mar

7:19 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

Hi, All works fine here. I've got the locale warning also, but no segfault. Im using qtmod-4.3.3 from kdemod. You could check if it works with this patched version of qt. Regards, Charly On Wednesday 05 March 2008 20:06:13 Nigel Henry wrote:

...

Hi Folks.

When I open Qsynth, I can rotate the various controls, but clicking on any of the buttons causes it to crash. For example I click on the "Options" button, the options window opens momentarily, but is blank, then Qsynth goes out to lunch.

When Qsynth is opened without messing with the buttons, Qjackctl shows fluidsynth available as an input port, so that bit is working ok.

Starting Qsynth on the CLI gives me this output, see below. [djmons@myhost ~]$ qsynth Warning: no locale found: /usr/share/locale/qsynth_en_US.qm Segmentation fault [djmons@myhost ~]$

I'm totally clueless about locales, but could this be the problem? Looking in /usr/share/locale there is no en_US locale. There are a bunch of en locales though (en, en@boldquot, en@quot, en_CA, en_GB)

Looking at when I started Qsynth on the CLI as above, it shows a segfault, but the GUI for Qsynth is still showing. It's only when I click on a button that it crashes.

Can anyone confirm that they have Qsynth working as expected?

I don't want to post a bug report if this problem has something to do with locales on my install.

Thanks for any help on this problem.

Nigel.

Nigel Henry

7:55 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

On Wednesday 05 March 2008 20:19, charly wrote:

...

Hi,

All works fine here. I've got the locale warning also, but no segfault. Im using qtmod-4.3.3 from kdemod. You could check if it works with this patched version of qt.

Regards,

Charly

Hi Charly. Have you got a link as to where I get this patched version of qt? I'm downloading a load of KDE updates at the mo (on dialup), so will have to go for this tomorrow, and see if it works. Thanks for the feedback. Nigel.

...

On Wednesday 05 March 2008 20:06:13 Nigel Henry wrote:

...
Hi Folks.

When I open Qsynth, I can rotate the various controls, but clicking on any of the buttons causes it to crash. For example I click on the "Options" button, the options window opens momentarily, but is blank, then Qsynth goes out to lunch.

When Qsynth is opened without messing with the buttons, Qjackctl shows fluidsynth available as an input port, so that bit is working ok.

Starting Qsynth on the CLI gives me this output, see below. [djmons@myhost ~]$ qsynth Warning: no locale found: /usr/share/locale/qsynth_en_US.qm Segmentation fault [djmons@myhost ~]$

I'm totally clueless about locales, but could this be the problem? Looking in /usr/share/locale there is no en_US locale. There are a bunch of en locales though (en, en@boldquot, en@quot, en_CA, en_GB)

Looking at when I started Qsynth on the CLI as above, it shows a segfault, but the GUI for Qsynth is still showing. It's only when I click on a button that it crashes.

Can anyone confirm that they have Qsynth working as expected?

I don't want to post a bug report if this problem has something to do with locales on my install.

Thanks for any help on this problem.

Nigel.

Denis Alessandro Altoe Falqueto

8:06 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

Hi Nigel. I think you are using the default KDE from Arch. I strongly recommend KDEmod (http://kdemod.ath.cx/), a tweaked version of KDE made by community volunteers (brave ones, at that). This is the project that ships qtmod, as it is patched for some features not in the default arch's qt package. It is very flexible, as only what you need is actually installed and there are some very cool extra patches. So, if you are using dialup connection, it is even more usefull. HTH. On Wed, Mar 5, 2008 at 4:55 PM, Nigel Henry wrote:

...

On Wednesday 05 March 2008 20:19, charly wrote:

...
Hi,

All works fine here. I've got the locale warning also, but no segfault. Im using qtmod-4.3.3 from kdemod. You could check if it works with this patched version of qt.

Regards,

Charly

Hi Charly. Have you got a link as to where I get this patched version of qt? I'm downloading a load of KDE updates at the mo (on dialup), so will have to go for this tomorrow, and see if it works.

Thanks for the feedback.

Nigel.

...
On Wednesday 05 March 2008 20:06:13 Nigel Henry wrote:

...
Hi Folks.

When I open Qsynth, I can rotate the various controls, but clicking on any of the buttons causes it to crash. For example I click on the "Options" button, the options window opens momentarily, but is blank, then Qsynth goes out to lunch.

When Qsynth is opened without messing with the buttons, Qjackctl shows fluidsynth available as an input port, so that bit is working ok.

Starting Qsynth on the CLI gives me this output, see below. [djmons@myhost ~]$ qsynth Warning: no locale found: /usr/share/locale/qsynth_en_US.qm Segmentation fault [djmons@myhost ~]$

I'm totally clueless about locales, but could this be the problem? Looking in /usr/share/locale there is no en_US locale. There are a bunch of en locales though (en, en@boldquot, en@quot, en_CA, en_GB)

Looking at when I started Qsynth on the CLI as above, it shows a segfault, but the GUI for Qsynth is still showing. It's only when I click on a button that it crashes.

Can anyone confirm that they have Qsynth working as expected?

I don't want to post a bug report if this problem has something to do with locales on my install.

Thanks for any help on this problem.

Nigel.

-- ------------------------------------------- Denis A. Altoe Falqueto -------------------------------------------

charly

6 Mar 6 Mar

12:46 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

If it works with qt-mod and not arch-provided qt, let us know cause maybe there's a problem with our binary On Wednesday 05 March 2008 21:06:48 Denis Alessandro Altoe Falqueto wrote:

...

Hi Nigel.

I think you are using the default KDE from Arch. I strongly recommend KDEmod (http://kdemod.ath.cx/), a tweaked version of KDE made by community volunteers (brave ones, at that). This is the project that ships qtmod, as it is patched for some features not in the default arch's qt package. It is very flexible, as only what you need is actually installed and there are some very cool extra patches. So, if you are using dialup connection, it is even more usefull.

HTH.

On Wed, Mar 5, 2008 at 4:55 PM, Nigel Henry wrote:

...
On Wednesday 05 March 2008 20:19, charly wrote:

...
Hi,

All works fine here. I've got the locale warning also, but no segfault. Im using qtmod-4.3.3 from kdemod. You could check if it works with this patched version of qt.

Regards,

Charly

Hi Charly. Have you got a link as to where I get this patched version of qt? I'm downloading a load of KDE updates at the mo (on dialup), so will have to go for this tomorrow, and see if it works.

Thanks for the feedback.

Nigel.

...
On Wednesday 05 March 2008 20:06:13 Nigel Henry wrote:

...
Hi Folks.

When I open Qsynth, I can rotate the various controls, but clicking on any of the buttons causes it to crash. For example I click on the "Options" button, the options window opens momentarily, but is blank, then Qsynth goes out to lunch.

When Qsynth is opened without messing with the buttons, Qjackctl shows fluidsynth available as an input port, so that bit is working ok.

Starting Qsynth on the CLI gives me this output, see below. [djmons@myhost ~]$ qsynth Warning: no locale found: /usr/share/locale/qsynth_en_US.qm Segmentation fault [djmons@myhost ~]$

I'm totally clueless about locales, but could this be the problem? Looking in /usr/share/locale there is no en_US locale. There are a bunch of en locales though (en, en@boldquot, en@quot, en_CA, en_GB)

Looking at when I started Qsynth on the CLI as above, it shows a segfault, but the GUI for Qsynth is still showing. It's only when I click on a button that it crashes.

Can anyone confirm that they have Qsynth working as expected?

I don't want to post a bug report if this problem has something to do with locales on my install.

Thanks for any help on this problem.

Nigel.

Nigel Henry

6:29 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

On Thursday 06 March 2008 13:46, charly wrote:

...

If it works with qt-mod and not arch-provided qt, let us know cause maybe there's a problem with our binary

Hi Charly. Looked at the kde-mod site, but as you have do remove all the current KDE packages, before installing kde-mod, I passed on that option, especially as Archlinux is working just fine apart from Qsynth, and a litle problem with Jacman, which I believe is being worked on. If I had another instance of Archlinux installed (and I'm sure I could do that, as I've several ancient distros on my drives), I'd be happy to try ked-mod, but that will have to wait for another day. Anyway. Back to the Qsynth problem. I thought I'd try installing the source file for Qsynth from sourceforge.net. Built, and installed it in /usr/local, but with the same results. Clicking on anything in Qsynth caused it to crash. Ok. Now I su to root (which I don't like doing, unless some permissions problem appears to be causing the problem) , and now Qsynth(with jack already started) complains that it can't connect to jack. Anyway Qsynth's GUI doesn't crash when I click on the settings button, and I change the audio to Alsa, then restart Qsynth. Then make the connection in Qjackctl from my midi keyboard to fluidsynth, and can play some notes (although they are a bit stuttery). So far so good, and Qsynth is sort of working without crashing, but only as root. Going back to the sourceforge site where I got the Qsynth tarball from, it mentions that Qsynth's settings are kept in ~/.config. Looking at that file, it's padlocked, and only accessable as root. It contained 2 directories, gtk-2.0, and mcbc.org, and one file Trolltech.conf. The mcbc.org directory contains the Qsynth.conf file. Going for it, I change the ownership of this directory to User: djmons, and Group: djmons. Now I open Qjackctl, start jack, and open Qsynth, and Qsynth works like clockwork, and my keyboard plays the sounds with no stuttering, as they had when Qsynth was started as root. I don't think this is a problem with Qsynth, but more to do with which program creates the .config directory in the /home/user directory, and makes it only accessable as root. Incidentally ~/.config has the mcbc.org directory, and the Trolltech.conf file now accessable by the user, but the gtk-2.0 directory is still padlocked ( only accessable as root) Just a bit of info from trying to resolve a problem. Nigel.

charly

7:22 p.m.

New subject: [arch-general] Qsynth crashes when clicking on buttons (Don't Panic)

Hi Henry, Having config files in your user home dir only accessible as root surely is a problem. Since files in .config are typically created on the first run, don't you have the (bad) habit to run programs as root? Do the test. Remove your Qsynth.conf file and start it as root (sudo qsynth). I don't see how these files coiuld have been owned by root any other way. You should make sure you own every file in your home dir (man chown) and to run programs as normal user. Regards, Charly On Thursday 06 March 2008 19:29:49 Nigel Henry wrote:

...

On Thursday 06 March 2008 13:46, charly wrote:

...
If it works with qt-mod and not arch-provided qt, let us know cause maybe there's a problem with our binary

Hi Charly. Looked at the kde-mod site, but as you have do remove all the current KDE packages, before installing kde-mod, I passed on that option, especially as Archlinux is working just fine apart from Qsynth, and a litle problem with Jacman, which I believe is being worked on.

If I had another instance of Archlinux installed (and I'm sure I could do that, as I've several ancient distros on my drives), I'd be happy to try ked-mod, but that will have to wait for another day.

Anyway. Back to the Qsynth problem.

I thought I'd try installing the source file for Qsynth from sourceforge.net. Built, and installed it in /usr/local, but with the same results. Clicking on anything in Qsynth caused it to crash.

Ok. Now I su to root (which I don't like doing, unless some permissions problem appears to be causing the problem) , and now Qsynth(with jack already started) complains that it can't connect to jack. Anyway Qsynth's GUI doesn't crash when I click on the settings button, and I change the audio to Alsa, then restart Qsynth. Then make the connection in Qjackctl from my midi keyboard to fluidsynth, and can play some notes (although they are a bit stuttery). So far so good, and Qsynth is sort of working without crashing, but only as root.

Going back to the sourceforge site where I got the Qsynth tarball from, it mentions that Qsynth's settings are kept in ~/.config. Looking at that file, it's padlocked, and only accessable as root. It contained 2 directories, gtk-2.0, and mcbc.org, and one file Trolltech.conf. The mcbc.org directory contains the Qsynth.conf file.

Going for it, I change the ownership of this directory to User: djmons, and Group: djmons.

Now I open Qjackctl, start jack, and open Qsynth, and Qsynth works like clockwork, and my keyboard plays the sounds with no stuttering, as they had when Qsynth was started as root.

I don't think this is a problem with Qsynth, but more to do with which program creates the .config directory in the /home/user directory, and makes it only accessable as root.

Incidentally ~/.config has the mcbc.org directory, and the Trolltech.conf file now accessable by the user, but the gtk-2.0 directory is still padlocked ( only accessable as root)

Just a bit of info from trying to resolve a problem.

Nigel.

5899

Age (days ago)

5900

Last active (days ago)

List overview

Download

6 comments

3 participants

participants (3)

charly
Denis Alessandro Altoe Falqueto
Nigel Henry