Not a duplicate after all:
<Saviq> bschaefer, about bug #1675448 you say that SDL likes to probe the
display server, how would that affect launching an app? it drops the probing
connection and reconnects from scratch after deciding it's fine?
<bschaefer> yeah, just need to politely mention we dont want to support that
and dont want to support anything mir related long term until we have 1.0
<bschaefer> Saviq, soo with SDL2 (recently upstreamed and not released) and
SDL1.2
<bschaefer> it probes if mir is around by simply attempting to connect to the
mir server
checks if its valid, releases the connection
then runs with the video driver which will re-connect to the display server
in the same process
<bschaefer> Saviq, theres not a good way to cache this connection as well (only
way would be a global variable MirConnection* which i would like to avoid 100%)
<Saviq> dandrader, you might want to have that in mind ↑ when looking at
multi-instance apps, bug #1675448 might not really be a duplicate after all
<dandrader> Saviq, ack
<Saviq> I'm actually not sure how to solve that wrt. splash screens right now
'cause the first connection would be hooked up to the Application object
that's "waiting" for a connection, then that connection gets dropped and we get
a new one
so how do we differentiate that from a new instance altogether? I suppose
through UAL instances maybe?
<bschaefer> hmm
<Saviq> so we maintain a 1:1 mapping between UAL's instance and our
Application, and we collect multiple connections for the same instance under
the same Application object
<dandrader> Saviq, agreed it looks like a separate issue
<dandrader> (that "duplicate "bug)
<bschaefer> yeah i wasnt sure if it was
but if a connection releases it before a new one comes it *its closed* right?
<bschaefer> and any connections after the release would be void
<Saviq> bschaefer, I suppose we can rely on UAL telling us when an application
instance is really gone
<bschaefer> Saviq, that should be a way to do it (though not sure if its *easy*
to do)
<bschaefer> does U8 only know about an application on the first mir_connection?
** This bug is no longer a duplicate of bug 1589637
Unable to open multiple instances of the same app
** Summary changed:
- Unity 8 doesnt allow multiple mir connections in a single client
+ Unity 8 doesnt allow multiple mir connections from an application instance
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Triaged
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Michał Sawicz (saviq)
** Changed in: canonical-devices-system-image
Milestone: None => u8c-2
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Triaged
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Description changed:
Some clients like to probe to see if a mir connection is available such
as SDL2 and SDL1.2.
This is an issue in U8 as it doesnt seem to allow multiple connections
in one process.
Example:
http://paste.ubuntu.com/24235399/
Output on U8:
http://paste.ubuntu.com/24235406/
+
+ ==== Proposed solution ====
+
+ Related to bug #1589637
+
+ We need to accept multiple connections from the same application
+ instance, relying on ubuntu-app-launch to tell us about instances and
+ their lifecycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675448
Title:
Unity 8 doesnt allow multiple mir connections from an application
instance
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675448/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
