[Desktop-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
Its even a bit more narrow than that, software clients of android work (its just ShmBuffer-backed software clients that would be affected). Furthermore, the nested compositor had to select GL rendering instead of pasthrough (which is probably common in the wild), and the surface had to be larger than 480x480. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1663062 Title: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later Status in Mir: In Progress Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Fix Committed Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: GPU apps seem to work. CPU apps all get black screen. To repro : Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar Under Unity8 : In another terminal, run : mir_demo_client_progressbar Observe that, the window is black. Whereas, egl clients run fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1663062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
** Tags added: mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1663062 Title: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later Status in Mir: Triaged Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Triaged Status in mesa package in Ubuntu: Invalid Bug description: GPU apps seem to work. CPU apps all get black screen. To repro : Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar Under Unity8 : In another terminal, run : mir_demo_client_progressbar Observe that, the window is black. Whereas, egl clients run fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1663062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
Status in Canonical System Image:
Confirmed
Status in Mir:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Under heavy resizing (stress testing under Valgrind), my Mir client
(Xmir) crashed with:
[1444895332.392862] MirBufferStreamAPI: Caught exception at client
library boundary (in mir_buffer_stream_swap_buffers):
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: disconnected: no new buffers
The strange thing is it's only the client that died. The server
survived and I can connect new clients to it.
Duplicate bug reports now show Unity8 is another such client suffering
from this crash. It's occurring on phones in the wild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: Using NBS, X apps under Unity8 need interaction to start in pocket-desktop
** Changed in: mir/0.23 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: Using NBS, X apps under Unity8 need interaction to start in pocket- desktop Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in QtMir: Invalid Status in mir package in Ubuntu: In Progress Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
I targeted to 0.24, should probably have a look, especially if we're
getting error reports from the 'field'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
Status in Canonical System Image:
Confirmed
Status in Mir:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Under heavy resizing (stress testing under Valgrind), my Mir client
(Xmir) crashed with:
[1444895332.392862] MirBufferStreamAPI: Caught exception at client
library boundary (in mir_buffer_stream_swap_buffers):
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: disconnected: no new buffers
The strange thing is it's only the client that died. The server
survived and I can connect new clients to it.
Duplicate bug reports now show Unity8 is another such client suffering
from this crash. It's occurring on phones in the wild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
If there's an issue in the transport in
mclr::MirProtobufRpcChannel::send_message during the sending of the
message, it will trigger the disconnection code.
If the client happens to be mid-mir_buffer_stream_swap_buffers at the
same time that the the connection error trips the disconnection
notification, we'll see that error. In the case of a true disconnection,
the only reasonable thing the client code can do is to throw, as it can
no longer appropriately fulfil the mir_buffer_stream_swap_buffers
requirement.
Also, iirc, there are certain things that the client can try to do that
will cause the server to disconnect it, maybe its an issue like that?
** Changed in: mir
Milestone: None => 0.24.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
Status in Canonical System Image:
Confirmed
Status in Mir:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Under heavy resizing (stress testing under Valgrind), my Mir client
(Xmir) crashed with:
[1444895332.392862] MirBufferStreamAPI: Caught exception at client
library boundary (in mir_buffer_stream_swap_buffers):
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: disconnected: no new buffers
The strange thing is it's only the client that died. The server
survived and I can connect new clients to it.
Duplicate bug reports now show Unity8 is another such client suffering
from this crash. It's occurring on phones in the wild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
Hmm, if the server isn't dying, perhaps we're getting a false
disconnection signal from the rpc code?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
Status in Canonical System Image:
Confirmed
Status in Mir:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Under heavy resizing (stress testing under Valgrind), my Mir client
(Xmir) crashed with:
[1444895332.392862] MirBufferStreamAPI: Caught exception at client
library boundary (in mir_buffer_stream_swap_buffers):
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
boost::exception_detail::clone_impl
std::exception::what: disconnected: no new buffers
The strange thing is it's only the client that died. The server
survived and I can connect new clients to it.
Duplicate bug reports now show Unity8 is another such client suffering
from this crash. It's occurring on phones in the wild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
fix is wip, still testing... hope to get it out the door Tuesday (Monday is US holiday) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
** Changed in: qtmir Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
I didn't include an Xmir stack trace yesterday because it didn't appear stuck, it was submitting buffers (black frames) repeatedly. I compiled Xmir and added some logs. I caught swap_buffers blocking up in Xmir (in the pocket desktop scenario only, seems to be a racy, perhaps on how big the frame size is) but it seems the block triggers the scenario. And from poking around Xmir when the problem occurs, it seems like the "BlockHandler" is only called once, and the system stuck submitting frames repeatedly, instead of servicing the WM+Xapp connection requests. And furthermore, I think that the system only got in this case with libertine+UAL+unity8+pocketdesktop because when UAL's involved, Xmir+WM+Xapp get launched in very close sucession, whereas with the desktop test plan, they're manually launched, so they start "far" apart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
seems matchbox is getting jammed trying to connect to the server too... I'm guessing this is why the map/realize isn't happing. ** Attachment added: "matchbox.txt" https://bugs.launchpad.net/mir/+bug/1584784/+attachment/4670915/+files/matchbox.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
Its very difficult to get backtraces for X apps when running in pocket desktop (had to rewrite puritine scripts to break out of confinement), but got a bt from Xeyes when the problem is occurring; bt is attached. ** Attachment added: "xeyes.txt" https://bugs.launchpad.net/mir/+bug/1584784/+attachment/4670897/+files/xeyes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
Its also interesting that this only happens in pocket desktop mode. The applications start up successfully when in phone-mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
Well, for some reason, this appears to be where the (gedit) window gets realized in our existing release: Atom _NET_WM_NAME = 267 Atom _NET_WM_WINDOW_TYPE = 295 Realize window 0xabaa7a98 "": 985x1093 +0+0 parent=0xab8dadc8 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1 override=1 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil) Atom UTF8_STRING = 268 Realize window 0xabaadca0 "gedit": 985x1093 +0+0 parent=0xabaa7a98 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1 override=0 _NET_WM_WINDOW_TYPE=254 WM_TRANSIENT_FOR=(nil) Realize window 0xabaadfa0 "": 1x1 -1-1 parent=0xabaadca0 depth=0 redir=0 type=2 class=2 visibility=3 viewable=0 override=0 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil) Atom _NET_WM_WINDOW_TYPE_NORMAL = 254 which doesn't happen in the 0.23 silo. The server will continue to schedule redraws, and resizing the window seems to cause it to realize. What events lead up to a window being realized on startup? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
also, havent been able to reproduce the behavior with the demo servers, just qtmir+Xmir on pocket desktop (where its easy to reproduce) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
I think it might be something going on with the focus causing the window not to be realized (perhaps). I've checked that the buffers aren't getting 'stuck' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
** Changed in: mir Status: Fix Committed => Fix Released ** Changed in: canonical-pocket-desktop Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: Fix Released Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/124440 Title: [enhancement] Ubuntu needs a way to set mouse scrolling speed Status in gnome-control-center: Unknown Status in GTK+: Unknown Status in One Hundred Papercuts: Triaged Status in Mir: Fix Released Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
** Changed in: mir/0.18 Status: Fix Committed => Fix Released ** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Fix Released Status in Mir 0.18 series: Fix Released Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
So my problem noted in #8 was just a mis-match of packages on my system. Cannot reproduce with xenial + silo 021, nor with on-system builds of lp:mir, lp:mir/0.18, or lp:mir/0.17. After standup today, it seems like we weren't able to reproduce the problem, provided that we had updated systems, and were using the (unintuitive) --vt switch properly (which became a bit more unintuitive starting at 3098). Hopefully everyone else comments below with further details of their testing. The decision in the standup today was to proceed with release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
Haven't been able to confirm this specific scenario today, but another issue (not a crash, rather incorrect platform loading) was noticed related to rev 3098. Seems best to back out that rev for lp:mir and lp:mir/0.18 release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Incomplete Status in Mir 0.18 series: Incomplete Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Incomplete Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
hmm, and now after doing a reinstall and upgrade of all packages (on xenial), I can no longer reproduce the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
seems to be mesa-specific -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
** Branch linked: lp:~mir-team/mir/revert-3098 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Incomplete Status in Mir 0.18 series: Incomplete Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Incomplete Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
I also can see the nested server crash scenario when connecting mir_demo_client_egltriangle. I haven't seen the client crash yet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
** Branch linked: lp:~kdub/mir/fix-1406725 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
Testing the EGLSyncFence extensions with xmir still has some corruption. Using these extensions stabilizes the mir_demo_client_flicker rendering. So, its looking like there's two problems going on here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
So, we have two issues in this bug. 1) The majority of the xmir corruption was caused by calling mir_buffer_stream_get_graphics_region() when xmir wanted to know the buffer size. On android, this would call down into gralloc, and invalidate/flush the cache when called. Its reasonable to just call into gralloc on once per swapbuffers. 2) The mir_demo_client_flicker corruption was caused by releasing the buffer resource a bit too early on the server side. This could occur in xmir as well, but seems to be rare for xmir's use case. This issue is corrected by using eglSyncFenceKHR extensions to ensure that the texture is uploaded to the gpu before releasing the buffer back to the server. (This is the more extensive A quick fix for both issues is in here: lp:~kdub/mir/0.17.1-fix-1406725. I'll repropose tests+fixes to lp:mir, but this should get xmir going in the meantime. 2) is the more extensive fix, so I'll split that bug out into a different report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
my spike branch that averts the problem is here, based on 0.17.1: lp:~kdub/mir/0.17.1-fix-1406725 This branch doesnt have unit tests, and needs a bit more work on the new internal interfaces, so I'll probably have to rework the branch to get it to land in lp:mir. ** Branch linked: lp:~kdub/mir/0.17.1-fix-1406725 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
After today's investigation, I think the cachelines that are appearing as corruption are not from an lines that should have been invalidated, but are the flushed lines from the next frame. IE, we're releasing the buffer too early, and the flushed lines from the backbuffer render are appearing as corruption in the previous frame. I've been able to use the sync extensions from EGL_KHR_fence_sync to stabilize cpu rendering and make sure that OES_EGL_image_external is synchronized. Will continue testing before saying its figured out, but seems to be improved. It might take a bit more work to come up with the proper patch that makes both android and mesa happy though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
The corruption appears on krillin too, so probably not a specific chipset problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
glFinish and other flushing-commands (eg, eglClientWaitSyncKHR with the flush bit) seem to be other alternatives that work, but those aren't very good alternatives either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
Its seeming like the gpu-facing cache is the one that needs invalidation from the GL/gralloc driver, but is not being flushed. This is a CPU/GPU coordination issue, and the GPU-based scenarios all work through the same cache and do not experience this problem. If we use overlays, this is not an issue, as the MDP/CPU cache sync seems to work. (Unfortunately, overlays are not supported on external displays) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
A (bad) workaround is to map the buffer server-side, and then use glTexImage2D (instead of glTargetTexture2D) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
I've been able to trace the calls down into the kernel, and it does look like the kernel is flushing the cache at the appropriate time before sending the buffer back to the client. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
** Changed in: mir Assignee: (unassigned) => Kevin DuBois (kdub) ** Changed in: mir Milestone: None => 0.18.0 ** Changed in: mir Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
re: Should we be concerned about this?... no, these comments are a bit stale -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
The problem looks like a cpu cache problem. We call gralloc's unlock function, and digging through the gralloc code, it looks like the internal native buffer flag that should trigger a cache flush is behaving properly. Now seeing what I can find out in the kernel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in Mir: In Progress Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel
Just for clarity's sake, INTEL_DEBUG=sync doesn't seem to make any difference, but nbuffers=3 seems to avert the problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377872 Title: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel Status in Mesa: Confirmed Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Double-buffered compositing performance is sometimes artificially poor on some intel systems. When this happens the frame rate seen is halved - about 30 FPS. However at the same time, Mir is observed to use very little render time and both the CPU and GPU are still mostly idle. It's just the Intel DRM logic sometimes takes two frames (~32ms) to complete a single page flip. Two known workarounds avoid the issue: (a) Add glFinish() into the mesa DisplayBuffer code; or (b) env INTEL_DEBUG=sync for the Mir server binary. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel
I see the same symptoms on my intel system. The easiest way to reproduce the systems for me is to have a host (in bypass mode, with nbuffers=2), a nested server (with nbuffers = 2 or nbuffers = 3), and then run eglplasma connected to the nested server. If egltriangle is running, the host server composites at 60fps. If eglplasma is running, the host server composites at 30fps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377872 Title: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel Status in Mesa: Confirmed Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Double-buffered compositing performance is sometimes artificially poor on some intel systems. When this happens the frame rate seen is halved - about 30 FPS. However at the same time, Mir is observed to use very little render time and both the CPU and GPU are still mostly idle. It's just the Intel DRM logic sometimes takes two frames (~32ms) to complete a single page flip. Two known workarounds avoid the issue: (a) Add glFinish() into the mesa DisplayBuffer code; or (b) env INTEL_DEBUG=sync for the Mir server binary. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417581] Re: [regression] USC - mouse cursor on AMD graphics is drawing incorrectly
** Changed in: mir Milestone: 0.12.0 = 0.13.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1417581 Title: [regression] USC - mouse cursor on AMD graphics is drawing incorrectly Status in Mir: Fix Committed Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: New Bug description: [REGRESSION] I've a Lenovo Flex 2 14D, which has an AMD APU. In Unity-System-Compositor, the mouse cursor does not draw correctly. See previous version of this bug for visuals: https://bugs.launchpad.net/mir/+bug/1391975 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1417581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192908] Re: Mir/Mesa packaging have a dependency cycle so cannot be upgraded
we should move include/shared/mir_toolkit/mesa/native_display.h somewhere upstream, to mesa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1192908 Title: Mir/Mesa packaging have a dependency cycle so cannot be upgraded Status in Mir: New Status in “mesa” package in Ubuntu: Won't Fix Bug description: Mir/Mesa have a dependency cycle so cannot build if there are any significant changes in one (like a soname/ABI bump). Mesa depends on mirclient mirserver depends on Mesa what makes it a cycle is that mirclient and mirserver are a single source package. So if anything changes (like libmirclient0 changing to libmirclient1) then we're stuck and can't rebuild anything. Not sure which chicken or egg came first and how we made it work originally. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1192908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
