View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003631 | ardour | bugs | public | 2010-12-28 16:13 | 2020-04-19 20:15 |
| Reporter | ycollet | Assigned To | cth103 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Summary | 0003631: ardour 3 gui doesn't shows up under 64 bits | ||||
| Description | Hello, I've download the latest svn repo of ardour 3. I compiled it under mandriva 2010.1 64 and 32 bits. Under 64 bits, ardour 3 gui doesn't shows up (I started jackd using qjackctl). But under mandriva 2010.1 32 bits, the gui shows up. I don't know if it is a known bug ... Your sincerely, YC | ||||
| Tags | No tags attached. | ||||
|
|
this must be a mandriva issue because several ardour3 developers and alpha testers use 64 bit distros and always have. that includes me, for instance. |
|
|
Yes, but which one ? It works fine under mandriva 2010.1 32 bits - 1 core. It doesn't work under mandriva 2010.1 64 bitts - 4 Cores. Do you have any hints to track donw this problem ? |
|
|
The last stable release of ardour (2.8.11) works fine under mandriva 2010.1 64 and 32 bits. The gui shows up. |
|
|
ardour2 and ardour3 should not be considered the same program. you need to run it inside a debugger (see http://ardour.org/debugging_ardour) if this makes no sense to you, then you probably should not be using ardour3 at this point in time. |
|
|
I finally managed to start the ardour3 gui. The problem of ardour gui start is in fact related to some popup. For example, I started ardour with a 48000 hz sampling frequency and I tryed to open a session for which the sampling frequency was 44100. So, a popup shows up while ardour was starting. I clicked on the OK button and then nothing happened. So, if I started ardour correctly (which the good sampling frequency, etc ...) then the gui shows up. Now, if I try to quit ardour (session->quit) ardour seems to freeze. |
|
|
Hi, as Paul says, if you want to debug the freeze you will need to run Ardour under gdb as described in the link above. |
|
|
I'll mark this as resolved. ycollet: if you can run Ardour under gdb as described, and you get a backtrace, please re-open this bug. Thanks! |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-12-28 16:13 | ycollet | New Issue | |
| 2010-12-28 16:53 | paul | Note Added: 0009711 | |
| 2010-12-28 19:12 | ycollet | Note Added: 0009713 | |
| 2010-12-28 19:33 | ycollet | Note Added: 0009716 | |
| 2010-12-28 19:37 | paul | Note Added: 0009717 | |
| 2010-12-28 21:08 | cth103 | cost | => 0.00 |
| 2010-12-28 21:08 | cth103 | Target Version | => 3.0-alpha1 |
| 2010-12-30 12:31 | ycollet | Note Added: 0009745 | |
| 2010-12-30 16:11 | cth103 | Note Added: 0009747 | |
| 2011-02-15 01:44 | cth103 | Note Added: 0010090 | |
| 2011-02-15 01:44 | cth103 | Status | new => resolved |
| 2011-02-15 01:44 | cth103 | Resolution | open => unable to reproduce |
| 2011-02-15 01:44 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:15 | system | Note Added: 0022324 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
