Mixxx crashed after changing the skin from Deere to Tango

Bug #1885009 reported by Jens
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Critical
Unassigned

Bug Description

used version 2.3 beta 64
OS: UbuntuStudio 20.04 (64bit)

1st issue
After changing the Skins (for example from Deere to Tango), Mixxx is crashing

2nd issue
If I close/finish the programm, Mixxx will restarted again.
sometimes once, sometimes twice

Its my first time to use Mixxx in Ubuntu Studio.
I dont know where could I find the logs in Ubuntu Studio for to provide more helpful information.

Regards

additional comment - this is what I found in the console:

EDIT ronso0: log doesn't contain helpful information, attached below nonetheless

Jens (soundflyer)
description: updated
Revision history for this message
ronso0 (ronso0) wrote :

the skin change issue is tracked elsewhere.

Re: quit/restart issue
I experienced this recently and it happened because there was literally no disk space left. Mixxx froze while trying to write a track waveform to disk and we had to force-quit, which caused Mixxx to try a restart once or twice.
Can you confirm that there's sufficient disk space available?

Revision history for this message
Sni-b (snib) wrote :

Hello,

I use ubuntu Mate 20.04 and I noticed the same issue as described in the bug (1st and 2nd issue).
It is not a problem of disk space in my case. I have 100 gigabytes of space left in /home and 40 gigabytes in /

Revision history for this message
Jens (soundflyer) wrote :

I use space round about 25% of 1TB (SSD) and 8GB RAM.
I think, thats should be OK for to use MIXXX

Revision history for this message
ronso0 (ronso0) wrote :
description: updated
Changed in mixxx:
importance: Undecided → Critical
status: New → Confirmed
milestone: none → 2.3.0
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10030

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.