Bug 453761 - Juk Crash, if application is opened using media from unmounted partition [before mount]
Summary: Juk Crash, if application is opened using media from unmounted partition [bef...
Status: REPORTED
Alias: None
Product: juk
Classification: Applications
Component: general (other bugs)
Version First Reported In: 21.12.3
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-13 21:27 UTC by Charlie Ramirez Animation Studios MX
Modified: 2022-05-13 22:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
KCrash Handler Generated Backtrace (3.00 KB, text/plain)
2022-05-13 21:27 UTC, Charlie Ramirez Animation Studios MX
Details
kde error Handler Screen after crash (38.76 KB, image/png)
2022-05-13 21:32 UTC, Charlie Ramirez Animation Studios MX
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Ramirez Animation Studios MX 2022-05-13 21:27:02 UTC
Created attachment 148807 [details]
KCrash Handler Generated Backtrace

SUMMARY
***
Using Juk Defaults in Debian 11 With Testing Repositories.

Juk usually opens by default on startup [Function expected correct]. and remains in the background until the user needs it.

-If Juke is configured to Read media or use a default music folder from a secondary Drive or unmounted partition, Juk will boot normally but will not show the playlist, If the source drive is mounted while juk is already open , at the time of scanning or pressing the play button the program will close suddenly, launching the error reporting wizard. If Juk is opened again (already with the media drive mounted) it will operate normally. And the playlist visible from the beginning 
***
-Inverse trace generated by the assistant is attached. But apparently not useful.

STEPS TO REPRODUCE
1. Using a default installation of juk on debian 11 start it.
2. Open the Juk folder settings and configure a Media Folder as a single folder located on a secondary disk or Partition that is not mounted by default when booting debian, save changes and scan. [play some music, juk should work fine so far]
3. Reboot or shutdown Debian. (it doesn't matter if Juk is closed or stays in the background).
Upon reboot, open an instance of juk [the partition or drive configured as source should not be mounted at this point yet].

4. With juk open (as is), mount the drive with the media folder and hit the play button or try scanning the folder. [Juk should close and pop up a notification to generate a crash report].

OBSERVED RESULT
The report assistant will only tell you that the generated backtrace is useless. or it lacks data to generate a report, or it must be done manually. giving the option to close or restart Juk.

If Juk is rebooted (remember the media drive is already mounted now). juke will show the list of songs and work normally

EXPECTED RESULT
juk should not hang when mounting media and trying to play if media is not mounted before juk starts.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.17.0-1-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics

ADDITIONAL INFORMATION
Probably unrelated, the media partition is on NTFS (Dualboot System -Windows). reason why it is not usually mounted by default on boot.

-Inverse trace generated by the assistant is attached.
-there is a secondary bug where juk in the same version, starts with the volume at 0% [But displayed as a volume number too large or tending to infinity, which must be manually raised in the frontend to return to zero or desired level and operate normally, I will open a separate Bug for this. ]
Comment 1 Charlie Ramirez Animation Studios MX 2022-05-13 21:32:48 UTC
Created attachment 148808 [details]
kde error Handler Screen after crash