Bug 218005 - Application linked against KDE libs DBus Hal interfere on calls
Summary: Application linked against KDE libs DBus Hal interfere on calls
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-09 17:15 UTC by Andreas Marschke
Modified: 2023-01-12 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Marschke 2009-12-09 17:15:14 UTC
Version:            (using KDE 4.3.2)
Compiler:          gcc 4.3.3 x86_64 
OS:                Linux
Installed from:    Debian testing/unstable Packages

Dbusand hal clash against each other. The bug described here 
http://code.google.com/p/bangarangissuetracking/issues/detail?id=27#makechanges
Appears in more than one application seems to happen when more than one application is trying to contact the CD-Tray.
Comment 1 Andrew Lake 2009-12-09 18:20:08 UTC
This bug really needs some clarification.  The reproduced problem from the Bangarang issue report is as follows:

1. Play an item in a KDE media application (Dragon Player, Juk, Amarok, Bangarang, etc.) 
2. Start up RhythmBox and attempt to play an item.  RythmBox is unable to start its own playback of media files.  
3. Close the KDE app and RhythmBox starts playback.  

The reverse appears to be true as well (play in RhythmBox then a KDE media app). This was observed on Kubuntu 9.10. 

Andreas appears to have experienced a crash accessing the CD drive.  However, from the attached backtrace on the linked Bangarang issue report, this crash occurred in code that has nothing to do with playback or HAL.  The CD drive crash may be related, but it is not entirely clear to me that it is.

The problem may well be lower in the stack than KDE, or perhaps a Kubuntu specific problem, but I'm really not sure.

Hope this helps.
Comment 2 Andrew Crouthamel 2018-11-02 22:59:14 UTC
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!
Comment 3 Andrew Crouthamel 2018-11-16 05:35:17 UTC
Dear Bug Submitter,

This is a reminder that 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?

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-13 02:53:24 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-28 05:24:34 UTC
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
mark the bug 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!
Comment 6 Bug Janitor Service 2023-01-12 05:17:32 UTC
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!