| Summary: | GREPME MySQLe query failed! (2000) | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | tukkek |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
error message (init)
console output from normal execution relevant output when crashing at song played errmsg.sys as mentioned in the attached error message |
||
Created attachment 103338 [details]
console output from normal execution
Created attachment 103339 [details]
relevant output when crashing at song played
Created attachment 103340 [details]
errmsg.sys as mentioned in the attached error message
I should add for completeness that other audio players are working fine, such as Clementine, VLC, mplayer... (In reply to tukkek from comment #4) > I should add for completeness that other audio players are working fine, > such as Clementine, VLC, mplayer... not needed, as they are not comparable anyway, as none of them uses MySQL database. This is just an old bug showing up again, and it has to do with the MySQL implementation in your distribution, please take this to them. *** This bug has been marked as a duplicate of bug 284810 *** I was only mentioning other players regarding audio playback so as to make sure this isn't a problem with ALSA or any other backend. Are you absolutely positive this is the same as the old bug and not just the same error message but for a different bug? Is there any way in which I can confirm this before submitting a report to downstream (Debian)? I find it hard to believe that this is a regression back from 2011 so please explain it to me briefly if you have the time so I can forward the appropriate information when filing my bug report to them. I don't mean to say I don't believe you, Myriam - it's just that the other bug report is very vague and amarok was working fine until 2 or 3 days ago so I'm not sure how an error from 2011 could be regressing now in 2017. Well, if you read the other report carefully, you can see there is a problem with the package provided by the distribution, same error number, and a quick Google search for that error shows that there is a packaging/compilation error with MySQL in all cases. You must have had an upgrade that triggered the error, but it certainly is not an Amarok bug, we didn't change our dependencies or our tarball. |
Created attachment 103337 [details] error message (init) There are other bugs with similar names to this but they are from 2.5 and Amarok was working fine for me until today so I think this is probably a new bug even if the error message is similar to others. I am attaching the error message in question, which mentions '989 error messages", which sounds pretty grave. This error message shows when opening Amarok. After closing it the application still shows up on the tray and looks normal but when I try to play a song it crashes without further messages or errors. I emptied the loaded playlist (songs shown on the UI) and when trying to activate a dynamic playlist I noticed my collection was gone. I am rescaning it as we speak - it was not marked anymore on the "Local collection" options section. Even after the rescan I still can't generate a dynamic playlist. The error still shows after restarting Amarok. After the restart the options menu remember the folder I've selected but Amarok still shows "0 tracks" for the Local Collection view. My view bookmarks are also gone. My scripts are remembered fine from what I can tell from before the upgrade. This renders the package completely useless for me. I am going to post this to Debian as well in case it's their fault in packaging but as far as I can tell it could be some internal problem as well. I can't reproduce the crash anymore after I cleared the loaded playlist (from previous sessions). Playing songs directly from the internal filesystem browser still cause Amarok to crash though. I'll be attaching the crash output in a separate file. Both reports were taken via the --debug parameter, with some personal information removed.