[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 205234] Not prepared to run in multiple sessions in parallel -
From:       Josef Spillner <spillner () kde ! org>
Date:       2010-05-25 7:16:10
Message-ID: 20100525071610.57DE54169D () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=205234





--- Comment #2 from Josef Spillner <spillner kde org>  2010-05-25 09:16:07 ---
As I said, I did disable kmix in systemsettings, but it didn't help because the
mixer window still appeared again on each session. What else should I have
done? This particular sub-problem doesn't seem to exist in KDE 4.4 anymore,
though, using the exact same configuration files in an isolated environment.

About the main issue here which is cross-session sharing of information about
inherently unique items such as hardware: Admittedly this is a difficult area.
I thought this is what the system dbus bus was about, as opposed to the session
bus, so one mixer could always find out if it's the primary one or not and only
override the primary one if this is intentionally a good idea (e.g., within
full-screen games, which also override the desktop resolution and then restore
when finished). Does this sound feasible or too much off the possible
behaviour?

Given that so much time has passed since the bug report, I suggest to downgrade
to wishlist and I will look into testing the whole workflow again with the most
recent KDE version. To me, it would still be a bug if starting a user's first
KDE session would suddenly turn up the volume of a background instance of for
example mplayer without the user having requested this to happen.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]