Bug 24884

Created attachment 11038 [details]
how appears the audacity GUI in HiDPI

Created attachment 11039 [details]
How the audacity GUI should appear with GDK_SCALE=1

Created attachment 11040 [details]
How the audacity GUI should appear with GDK_SCALE=2

Created attachment 11041 [details]
Quick fix

Here is a quick fix. Reverting to internal wxgtk (and upgrade it to latest wxgtk 3.0.4 as well as to audacity 2.3.2) would fix the problem, though the old audacity-*-widgets-create-room.patch that was removed should be re-enabled and probably rediffed. Without that patch in fact the "Hz" widget in the bottom left is partially overlapped by the drop menu button (see screenshot in attach).

Created attachment 11042 [details]
audacity 2.3.2 with the internal wxgtk (still to be fixed the Hz widget)

Created attachment 11043 [details]
new spec file diff

New fix. This one adds a little bit more room for the project rate string

Attachment 11041 is obsolete: 0 => 1

Created attachment 11044 [details]
rediffed patch

Created attachment 11045 [details]
rediffed patch

Created attachment 11046 [details]
Screenshot after the new fixes

Assigning to our registered audacity maintainer.

Assignee: bugsquad => lists.jjorge
CC: (none) => marja11
Keywords: (none) => PATCH

Please Giuseppe, why use builtin wxgtk wchile it is the same version MGA7 provides?

Because the system wxgtk is probably broken or compiled without GTK3 support. This bug occurs also in current audacity-2.3.2-1.mga7 in updates_testing.

The testing is simple even on a non-HiDPI desktop: just run from command line: "GDK_SCALE=2 audacity" or "GDK_SCALE=3 audacity", if the GUI scales then it's OK, if it doesn't then it's broken.

(In reply to Giuseppe Ghibò from comment #12)
> Because the system wxgtk is probably broken or compiled without GTK3
> support. This bug occurs also in current audacity-2.3.2-1.mga7 in
> updates_testing.

Ok, but we package wxgtk, why don't you fix it's build options to enable GTK3?
We must remove as many bundled libs as we can...

I have no idea what could/should be done to fix the issue but I just wanted to confirm the bug described in Comment 1.
Also, audacity takes ages to start. This is what I get when running it from Konsole (see attached file).

$ rpm -qa | grep audacity
audacity-2.3.1-1.mga7

CC: (none) => sebsweb

Created attachment 11116 [details]
audacity-2.3.1-1.mga7 run from Konsole

(In reply to José Jorge from comment #13)
> (In reply to Giuseppe Ghibò from comment #12)
> > Because the system wxgtk is probably broken or compiled without GTK3
> > support. This bug occurs also in current audacity-2.3.2-1.mga7 in
> > updates_testing.
> 
> Ok, but we package wxgtk, why don't you fix it's build options to enable
> GTK3?
> We must remove as many bundled libs as we can...

When I spotted the bug, there was already deep freeze, so I preferred to propagate the fixes only inside one single package.

(In reply to Giuseppe Ghibò from comment #16)
> (In reply to José Jorge from comment #13)
> > (In reply to Giuseppe Ghibò from comment #12)
> > > Because the system wxgtk is probably broken or compiled without GTK3
> > > support. This bug occurs also in current audacity-2.3.2-1.mga7 in
> > > updates_testing.
> > 
> > Ok, but we package wxgtk, why don't you fix it's build options to enable
> > GTK3?
> > We must remove as many bundled libs as we can...
> 
> When I spotted the bug, there was already deep freeze, so I preferred to
> propagate the fixes only inside one single package.

AS this will not go before release, it will need to be an update. I prefer to do the changes in the MGA7 package, and keep in cauldron the current one, as system wxgtk3 is coming shortly.

Ok, anyway I placed the whole fixed version with bundled wxgtk here: 

https://copr.fedorainfracloud.org/coprs/ghibo/audacity

What is the state currently of the bug?
with GDK_SCALE=2, I see problems with 3 drop down lists for Recording device, Recording channels and Playback device.

CC: (none) => yves.brungard_mageia