Audacity Forum

Hi, all.

In the most recent versions of Audacity(*), I am noticing a(n annoying) new behavior -- If I close 1 window/project -- now it closes all windows/projects

That is, If I have more than 1 Audacity window open (for different projects), and I close one project (either by the window's 'X' control in title bar, or by choosing "Close" from the project's File menu), then it automatically closes the other project's window(s) as well. This behavior holds even if the other project was not yet saved!

It is as if by clicking Close (Ctrl-W), I am really clicking on Exit (Ctrl-Q), except that it is worse than Exit, because with Exit, I at least get prompted for any unsaved projects.

I have had to recover projects several times now as it is taking this old dog a while to learn this new behavior.

Is this intentional? Or a bug? Or just something I'm missing? (It didn't used to do this for all the years I've used Audacity.)

Thanks!
Jeff (androclus)

(*) I am using Audacity 2.3.3-alpha-Nov 25 2019, on Linux OpenSUSE Tumbleweed, from the Tumbleweed distro main repository, package name "audacity-2.3.3-1.1.x86_64". This is the latest version available on my repo. But I am not sure how long it has been up, and/or how many other versions recently have had this problem. But I've only noticed this behavior in say, the last month or two. I run KDE Plasma 5, and have not changed my desktop settings.

Hi,

I think this must be related to your environment. I'm running Audacity-2.3.3 and I can open multiple instances and close them individually.

Are you running KDE and do you have Window Grouping enabled? That could be a possible influencer.

ATB,
Neil

I'm also running Audacity-2.3.3 / Audacity 2.4.0 alpha (Ubuntu with Xfce) and I can open multiple instances and close them individually.
On closing a project that has not just been saved, I get a prompt to save the project - do you get that?

androclus wrote: ↑

Fri Jan 10, 2020 3:02 am

In the most recent versions of Audacity(*), I am noticing a(n annoying) new behavior -- If I close 1 window/project -- now it closes all windows/projects

Use File > Close or the window "X" to close just the current Audacity Window

File > Exit or shortcut Ctrl + Q - will close all Audacity windows.

WC

I have the same problem : using Audacity 2.3.3-alpha-Nov 25 2019
OS = Opensuse Tumbleweed, KDE, updated to version 20200110, but this problem exists since 25/11/2019
Previously I could
- open an existing project
- copy part of the audio via Ctrl-C
- create a new project window via Ctrl-N
- paste in the new windows via Ctrl-V
- export this via Shift-Ctrl-E
- finally close the newly created project with Ctrl-W, without closing the originally opened project.
Since audacity version 2.3.3, this final Ctrl-W also closes the original project, without warning.
It's actually a crash : when starting audacity from the command line, the log on screen shows after the Ctrl-W "Segmentation fault (core dumped)"
There is no difference between running Ctrl-W and Ctrl-Q : both end with "Segmentation fault (core dumped)"
Thanks for any support
Bart

Works on Windows

I just tested again on W10 with 2.3.3 and the latest alpha test build I have for 2.4.0

1) launch Audacity
2) Ctrl+N
3) observe second project opens on top
4) Ctrl+W
5) Observe 2nd top project closes leaving first project open

In contrast Ctrl+Q closes both projects.

Peter.

Is this problem specific to KDE?

>> Is this problem specific to KDE?
That's very well possible, I've quick means to test on gnome, sorry.
Below you can find the stacktrace of the system jounald log.
But now I see that the same crash also occurs after simply starting audacity and closing it immediately via Ctrl-Q or Ctrl-W

13/01/2020 21:33 systemd-coredump Process 12906 (audacity) of user 1000 dumped core.

Stack trace of thread 12906:
#0 0x00007faf88b21324 _ZN12wxEvtHandler18SafelyProcessEventER7wxEvent (libwx_baseu-suse-nostl.so.3.0.4)
#1 0x00007faf890d4e5a n/a (libwx_gtk2u_core-suse-nostl.so.3.0.4)
#2 0x00007faf86eceb4b n/a (libgtk-x11-2.0.so.0)
#3 0x00007faf86bb1eb2 g_closure_invoke (libgobject-2.0.so.0)
#4 0x00007faf86bc52ab n/a (libgobject-2.0.so.0)
#5 0x00007faf86bcdc21 g_signal_emit_valist (libgobject-2.0.so.0)
#6 0x00007faf86bcebcf g_signal_emit (libgobject-2.0.so.0)
#7 0x00007faf86dbc070 n/a (libgtk-x11-2.0.so.0)
#8 0x00007faf86ed645b gtk_main_do_event (libgtk-x11-2.0.so.0)
#9 0x00007faf86c5f5c6 n/a (libgdk-x11-2.0.so.0)
#10 0x00007faf86ac9ff8 g_main_context_dispatch (libglib-2.0.so.0)
#11 0x00007faf86aca380 n/a (libglib-2.0.so.0)
#12 0x00007faf86aca653 g_main_loop_run (libglib-2.0.so.0)
#13 0x00007faf86ed2a9a gtk_main (libgtk-x11-2.0.so.0)
#14 0x00007faf890dba85 _ZN14wxGUIEventLoop5DoRunEv (libwx_gtk2u_core-suse-nostl.so.3.0.4)
#15 0x00007faf88bcd96d _ZN15wxEventLoopBase3RunEv (libwx_baseu-suse-nostl.so.3.0.4)
#16 0x00007faf89092510 _ZN8wxDialog9ShowModalEv (libwx_gtk2u_core-suse-nostl.so.3.0.4)
#17 0x00007faf8940dc2f _ZNK23wxDebugReportPreviewStd4ShowER13wxDebugReport (libwx_gtk2u_qa-suse-nostl.so.3.0.4)
#18 0x000055a197d8c7d3 _ZN11CrashReport8GenerateEN13wxDebugReport7ContextE (audacity)
#19 0x000055a197dcf420 _ZN11AudacityApp16OnFatalExceptionEv (audacity)
#20 0x00007faf88b2b202 n/a (libwx_baseu-suse-nostl.so.3.0.4)
#21 0x00007faf8966a150 __restore_rt (libc.so.6)
#22 0x00007faf891e5c48 _ZTI11wxMiniFrame (libwx_gtk2u_core-suse-nostl.so.3.0.4)
#23 0x0000000000000000 n/a (n/a)

Neil Darlow wrote: ↑

Fri Jan 10, 2020 9:17 am

Hi,

I think this must be related to your environment. I'm running Audacity-2.3.3 and I can open multiple instances and close them individually.

Are you running KDE and do you have Window Grouping enabled? That could be a possible influencer.

ATB,
Neil

Hi, Neil, thanks for your questions.

Yes I am running KDE.

I did have Window Grouping enabled.

To test your idea, I went into Configure Task Manager (by right-clicking on Plasma panel), then Behavior. I changed "Group" drop-down to "Do not Group", clicked Apply and OK. Then logged out of my session and back in, and checked that Do Not Group was still the setting.

Now, as before -- but now without Grouping -- I can open Audacity. Just a blank window. Now click on File->New to create a second (also blank) project. Clicking Ctrl-W (or window's "X" control) within either project will kill both projects with prejudice -- i.e., indeed with what looks like a flickering SegFault.

I am including:

a) a screencast of this behavior (as an .mp4 since this interface would not accept my original .mkv file), and on my Google Drive (since again this interface said my .mp4 -- 3.6MB -- was too large):

issue-108405-vokoscreenNG-2020-01-14_21-48-12.mp4
https://drive.google.com/open?id=18K7PI ... 04x71rkiAW

b) a screenshot of the window that flips up really quickly but which I could not see or read without going back through the screencast and going through frame-by-frame to get the screenshot

issue-108405-vlcsnap-2020-01-14-21h55m35s331.png

c) once i had this, i could now see that the debug logs were in /tmp. So I am including also a .zip file of everything in that dir

issue-108405-Audacity_dbgrpt-9097-20200114T212945.zip

So it appears Grouping does not have an influence. I wish it had :-/

Let me know if there is anything else you would like me to test. Hope this additional info helps.

-a

bdeceulaer wrote: ↑

Mon Jan 13, 2020 8:45 pm

Below you can find the stacktrace of the system jounald log.

@bdeceulaer - can you help me out? what exact line command did you use to get that systemd journal log? i will do same on my end, for comparison. -a