Summary: | Amarok crash closing USBdevice | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | George Baltz <GeoBaltz> |
Component: | Collections/USB mass storage and MSC | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | aumuell, bart.cerneels |
Priority: | NOR | ||
Version: | 2.2-SVN | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
George Baltz
2010-02-23 18:03:04 UTC
Can you still reproduce this and send us a backtrace in Amarok 2.3-GIT? On Wednesday 24 March 2010 04:54:18 am Sven Krohlas wrote: > https://bugs.kde.org/show_bug.cgi?id=228219 > > > Sven Krohlas <sven@asbest-online.de> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - Status|UNCONFIRMED |NEEDSINFO > CC| |aumuell@reserv.at > Component|general |Media Devices > Version|unspecified |2.2-SVN > Resolution| |BACKTRACE > > > > > --- Comment #1 from Sven Krohlas <sven asbest-online de> 2010-03-24 > 09:54:05 --- Can you still reproduce this and send us a backtrace in > Amarok 2.3-GIT? > Recreated and entered as bug #232051 Also attached STDERR from amarok --debug Mass closing NEEDSINFO bugs with no comment for at least 31 days. Dear reporter, thanks for your feedback. For efficient bug triaging we need not only one report but also constant feedback about the status of an issue, at least when we ask for it. If your request is still valid in our latest release in your opinion (2.3.1 beta 1) DO NOT REOPEN THIS BUG but file a fresh one instead. Developers need clean bug reports to be able to work efficiently. Provide at least a step-by-step guide on how to reproduce the issue, a backtrace in case of a crash and debug output if appropriate. And remember: * One issue per bug. Small, clean bug reports are best to work on. * Search for duplicates. Hint: we have useful categories for that. :) -> RESOLVED INVALID |