| Summary: | juk creates zero length files with names like "jukrcXXXXXX.new" on exit | ||
|---|---|---|---|
| Product: | [Applications] juk | Reporter: | Antonis <linuzonix> |
| Component: | general | Assignee: | Scott Wheeler <wheeler> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | rakuco |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version First Reported In: | 2.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Antonis
2005-11-22 15:15:09 UTC
All of the time? And only juk? If so, then maybe JuK is crashing on exit? I keep getting a glibc memory corruption bug but I can't track it down in valgrind and no one else seems to get it so I haven't had much luck tracking it down. But then again, I don't have any jukrcXXXXX files laying around either since about 6 weeks ago. Yes all of the time and only juk. And it doesn't crash. --- Thiago Macieira <thiago@kde.org> wrote: [bugs.kde.org quoted mail] __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com I found how to reproduce the bug on other computers. 1. open juk and go to Settings->Tag Guesser 2. Select a file name scheme and move it up or down in the list. 3. press OK. Now every time you quit juk you will get a new file jukrcXXXXXX.new and a file jukrc.lock in ~/.kde/share/config directory Reporter: Have you tried this with KDE 3.5? I just now got around to trying to reproduce using your instruction and I can't seem to manage to do so. yes the bug exists in kde 3.5 also. Make sure you quit juk and not just close the window (closing the window puts juk in the system tray) Yes, I tried Quitting JuK instead of just closing the window, the result is always the same. :-/ Well I'm using Arch Linux binaries. I don't know if that's the problem. Can you please confirm if this bug is still valid with KDE4? Closing as there has been no response. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |