Bug 314617

Summary:	Running Mixer_Backend destructor
Product:	[Applications] kmix	Reporter:	davidkacerek
Component:	general	Assignee:	Christian Esken <esken>
Status:	RESOLVED FIXED
Severity:	minor	CC:	shubham.chaudhary
Priority:	NOR
Version:	4.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Screenshot of difference in volume level removes debugging line Running Mixer_Backend destructor

Description davidkacerek 2013-02-07 18:02:42 UTC

When inspecting some issues with kmix i ran it from terminal:
$ kmix                                                                                                       
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.                                 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.                                 
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.                
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor                                                                                                      
Running Mixer_Backend destructor 
Running Mixer_Backend destructor

The "QDBusConnection" warning shouldn't be an issue according to google but the "Running Mixer_Backend destructor" warning is not present among the bugs here nor Arch bugtracker. The issues which may be relevant have been discussed here: http://forum.kde.org/viewtopic.php?f=225&t=109454

Comment 1 Łukasz Żarnowiecki 2013-02-27 10:46:03 UTC

Created attachment 77611 [details]
Screenshot of difference in volume level

I came from here http://forum.kde.org/viewtopic.php?f=225&t=109454
I have exactly the same problem.

Comment 2 Shubham Chaudhary 2013-04-11 05:29:22 UTC

Created attachment 78787 [details]
removes debugging line Running Mixer_Backend destructor

Please review the patch and let me know if I can do anything else.

Comment 3 davidkacerek 2013-04-27 23:25:05 UTC

(In reply to comment #2)
> Created attachment 78787 [details]
> removes debugging line Running Mixer_Backend destructor
> 
> Please review the patch and let me know if I can do anything else.

Hi, in KDE 4.10.2 i don't see the error anymore.

Comment 4 Shubham Chaudhary 2013-04-28 09:28:20 UTC

yes, I know it's resolved now, 
just that it was not marked as fixed. It is now. Great.