Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17040 - [kdemultimedia-kscd] KsCD fails to start playing after upgrade to 4.3.3-1 from 4.3.2-1
Attached to Project:
Arch Linux
Opened by Andrew Munkres (amunkres) - Saturday, 07 November 2009, 02:18 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 11 January 2010, 19:24 GMT
Opened by Andrew Munkres (amunkres) - Saturday, 07 November 2009, 02:18 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 11 January 2010, 19:24 GMT
|
DetailsDescription:
When pressing the play button in KsCD, usually nothing happens. (The drive light remains off and the slider does not move.) Sometimes restarting the program and trying again will cause it to start playing, but usually not. I'm using the gstreamer Phonon backend. Other Phonon-based players, such as Dragon Player and Kaffeine for KDE4 (AUR package kaffeine-kde4-svn), are able to play CDs. Additional info: * package version(s) kdemultimedia-kscd 4.3.3-1 * config and/or log files etc. Steps to reproduce: Put an audio CD in the drive, run KsCD, press the play button. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Monday, 11 January 2010, 19:24 GMT
Reason for closing: Works for me
Additional comments about closing: see comments
Monday, 11 January 2010, 19:24 GMT
Reason for closing: Works for me
Additional comments about closing: see comments
Comment by Gerardo Exequiel Pozzi (djgera) -
Saturday, 07 November 2009, 02:37 GMT
- Field changed: Status (Unconfirmed → Waiting on Response)
- Field changed: Category (Packages: Extra → Upstream Bugs)
Looks like upstream issue rahter than a packaging issue. Please report to upstream if not already reported. Thanks.
Comment by Andrew Munkres (amunkres) -
Monday, 14 December 2009, 02:06 GMT
The problem seems to be gone after upgrading to 4.3.4-1.