Summary: | kaudiocreator allows the user to select a temporary directory the user does not have write access to, resulting in a crash | ||
---|---|---|---|
Product: | [Applications] kaudiocreator | Reporter: | Tim Wunder <tim> |
Component: | general | Assignee: | Gerd Fleischer <gerdfleischer> |
Status: | RESOLVED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tim Wunder
2006-06-19 06:02:20 UTC
Can confirm this. Version 1.13, KDE 3.5.2 Testcase: + Start kaudiocreator, assign a different tmp directory, close kaudiocreator. + Now remove write permissions from tmp dir OR fill disc space up until 0 bytes left for user. + Start kaudiocreator (starts normal), insert CDaudio (ok), start ripping (not ok). 2 messages are shown for a fraction of a second, then kaudiocreator crashes. Maybe a timer event tries to work on deleted memory? Error message is OK, application should not crash. since 1.2.90 tmp is checked for write access, can you please test (if you still still using kaudiocreator). No crash using current kaudiocreator 1.2.90 on Fedora 14. On 06/05/2011 04:13 PM, Gerd Fleischer wrote: > https://bugs.kde.org/show_bug.cgi?id=129402 > > > > > > --- Comment #2 from Gerd Fleischer<gerdfleischer web de> 2011-06-05 22:12:58 --- > since 1.2.90 tmp is checked for write access, can you please test (if you still > still using kaudiocreator). > Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Much like comment #3, made in 2011, there is no longer a crash when the default temp directory defined becomes un-writable, using 1.3 on Fedora 28. Essentially followed the steps outlined in comment #1. Attempting to mark status as RESOLVED/FIXED |