Hi Carlos,
I tried these patches. Coupled with the Gtk+ fix, this does indeed fix
the various scrolling issues! Hopefully the patches will be
reviewed/accepted soon.
Thanks a million for addressing this!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
@Doug,
That's strange, I'm not seeing that behavior on my 14.04 system. I'm
using a USB wheel mouse w/ patches applied and a fully updated system.
Could you describe the exact steps you are doing to reproduce this or if
you created a new bug, point me there if you have steps in it?
--
You rece
@Mark,
I'm not sure which version of Ubuntu you are using, but this is only
currently fixed for 14.04. It is scheduled to be included in an SRU for
13.10, but unfortunately, I don't have a time table of when that will
be.
--
You received this bug notification because you are a member of Ubuntu-
Doug,
I'm still not seeing the Nautilus crash you are seeing even after
creating a new folder on the Desktop and left double clicking it. I
don't think anyone has a patched xserver in a PPA. I can try uploading
it today to my PPA.
Have you tried downgrading your xserver packages and see if the
Hi Vassili,
This still requires a fix to xorg-server for the whole fix to be
complete and the patch is still waiting to be ack'd upstream.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/124
** Changed in: unity/7.1
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1232726
Title:
Dash bg color doesn't match its surroundings
To manage notific
Public bug reported:
Since mesa 10.0 has been released, our Unity continuous-integration
tests are failing on armhf builds. This is a snippet of the log:
libEGL warning: DRI2: failed to authenticate
Segmentation fault (core dumped)
The log can be found here for reference:
https://jenkins.qa.ubu
** Description changed:
Since mesa 10.0 has been released, our Unity continuous-integration
tests are failing on armhf builds. This is a snippet of the log:
libEGL warning: DRI2: failed to authenticate
Segmentation fault (core dumped)
The log can be found here for reference:
htt
Sure do: https://jenkins.qa.ubuntu.com/job/unity-trusty-armhf-
autolanding/40/consoleFull
This was on Dec. 9 which had Mesa version 9.2.2-1ubuntu2.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
whi
I'm quite certain that this is not a Unity issue as completely separate
merge proposals all fail armhf CI. However, we don't have definitive
proof of that, so we are trying other ways to debug this.
We tried the LIBGL_ALWAYS_SOFTWARE=1 env var in an amd64 build, but no
where in the log does it sa
For reference, the reconfigured Mesa is just reverting this change:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/trusty/mesa/trusty/revision/206/debian/rules
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a membe
Is there an ETA on when the patches are going to be merged into master?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll wheel not working in gedit & System Moni
Is there an ETA on when the patches are going to be merged into master?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enabling typical bindings in "Desktop-ba
Is there an ETA on when the patches are going to be merged into master?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour and window focus has changed and
Is there an ETA on when the patches are going to be merged into master?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrolling with a touchpad is jerky with bindi
** Changed in: libertine
Milestone: 1.3 => 1.4
** Changed in: libertine/trunk
Milestone: 1.3 => 1.4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1471998
Title:
[enhancement] Su
** Branch linked: lp:~dandrader/qtubuntu/content-hub-clipboard
** Changed in: qtubuntu (Ubuntu)
Status: Triaged => In Progress
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Tags removed: xmir
** No longer affects: xorg-server (Ubuntu)
**
** Description changed:
+ [Impact]
+
+ A crash in Xmir can be observed sometimes when starting particular X
+ applications.
+
+ [Test Case]
+
+ 1. Create a Libertine container and install supertux.
+ 2. Try to run supertux.
+
+ Obverse there is no longer a crash in Xmir in /var/crash.
+
+ [Re
** Description changed:
+ [Impact]
+
+ Auto key repeating does not work in Libertine X apps which is very
+ frustrating to users.
+
+ [Test Case]
+
+ 1. Install xterm in libertine
+ 2. Start xterm from the "Xapps" scope
+ 3. Wait for xterm to appear
+ 4. Press and hold a key
+
+ See how it onl
** Description changed:
+ [Impact]
+
+ Users seeing graphics corruption is not good and leaves a poor user
+ experience.
+
+ [Test Case]
+
+ 1. Create a Libertine container.
+ 2. Install an X app in it.
+ 3. Start the X app.
+ 4. Resize the window.
+
+ Observe that the window does not have gra
** Description changed:
+ [Impact]
+
+ Users would like to use smooth scrolling and have a good user
+ experience.
+
+ [Test Case]
+
+ 1. Create a Libertine container.
+ 2. Install an X application in it.
+ 3. Start application.
+ 4. Using a touchpad, use gesture for scrolling.
+
+ Observe smo
** Description changed:
- Xmir: xrandr outputs information is lost after root window resize (non-
- rootless mode)
+ [Impact]
+
+ Users trying to use xrandr on Xmir will get bogus info for the root
+ window after resizing it.
+
+ [Test Case]
+
+ 1. Start up an X application through Xmir.
+ 2. T
** Description changed:
+ [Impact]
+
+ This will allow copy & paste to work with X apps on desktop systems
+ using U8.
+
+ [Test Case]
+
+ 1. Compile & install the Libertine branch found here:
+ https://code.launchpad.net/~townsend/libertine/pasted/+merge/299603
+ 2. Create a Libertine containe
** Description changed:
Enviroment:
current build number: 169
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-08-16 10:23:29
version version: 169
version ubuntu: 20160816
version device: 20160809.0
version custom: 20160805--42-20-vivid
Hey Daniel,
I do not see this issue on Yakkety xmir on desktop, nor do I see it on
Xenial+overlay using a locally compiled xmir made from the head of the
xmir git tree.
However, I can reproduce the issue described in the bug on my frieza
using the version of xmir found in the Vivid overlay candid
Update:
So I tried rotating the tablet into portrait mode as suggested, and the
buttons suddenly work!
I'm not sure where the bug lies in this case, but wherever the bug is,
the version of xmir that is currently in the overlay is not affected by
it whereas the overlay candidate is.
--
You recei
Here is the debdiff between the version of xmir in the overlay (working)
and the candidate version:
http://pastebin.ubuntu.com/23064583/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/16137
I have enabled xenial-proposed and installed xmir. I can confirm this
bug is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
I have enabled xenial-proposed and installed xmir. I can confirm this
bug is fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
I enabled xenial-proposed and installed xmir. I can confirm this bug is
fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.n
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1581076
Title:
Xorg segfaults on start-up on Big Endian PPC hardware
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1617932
Title:
Xmir with glamor is spending 11% of its CPU time in
e
I have installed xmir from xenial-proposed and confirmed no regressions
are caused by this change.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https
*** This bug is a duplicate of bug 1628589 ***
https://bugs.launchpad.net/bugs/1628589
I'm going to dup this bug to bug #1628589 as the crux of the problem is
proper session management for Libertine X apps.
** This bug has been marked a duplicate of bug 1628589
Need better session manageme
Looks to me like Java is querying display modes and doesn't receive
anything back. Jave doesn't handle this gracefully and crashes.
Xmir should probably at least return something meaningful back when
being queried for display modes.
--
You received this bug notification because you are a member
Public bug reported:
Using xmir on the Xenial arm64 based image on a frieza, xmir crashes
immediately upon starting.
Here is the output in the app's upstart log:
glamor EGL version: 1.4 Android META-EGL
glamor EGL extensions: EGL_KHR_get_all_proc_addresses
EGL_ANDROID_presentation_time EGL_KHR_
Ok, I looked a bit, and it appears Firefox is trying to use the GDK-Mir
backend, but I'm guessing the GDK-Mir backend is not mature enough yet
(?), so the app bails.
Definitely not an Xmir issue as Xmir is not even trying to be used in
this case.
** No longer affects: xorg-server (Ubuntu)
--
Yo
Public bug reported:
In the move to using Xmir in -rootless mode and the landing of child
surfaces in U8, Firefox menus do not work.
The menu will show very briefly and then disappear.
To test Xmir in -rootless mode w/ U8 and Libertine, please install
https://bileto.ubuntu.com/#/ticket/2452 and
*** This bug is a duplicate of bug 1625846 ***
https://bugs.launchpad.net/bugs/1625846
** This bug has been marked a duplicate of bug 1625846
Xmir -rootless: Firefox menus pop up then close right away
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
Yeah, this is going to become more of an issue since we are enabling
rootless by default for Libertine apps.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846
Title:
Xmir -rootless:
I'm not really sure where the problem here is, but I'm pretty sure it's
not Libertine in and of itself causing the issue.
My first suspicion is maybe Xmir is not doing something right, so I'll
just add that task to this bug for completeness and mark the Libertine
bug Invalid.
** Also affects: xor
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Tags added: unity8-desktop
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846
Title:
Xm
After some more investigation, in the non-rootless mode, Xmir sets the
_MIR_WM_PERSISTENT_ID atom on the root window, and since pasted just
queries the default root window, this works fine.
However, in rootless move, one of the children on the "root" window gets
the _MIR_WM_PERSISTENT_ID atom, thu
I don't doing it in xmir is the right place now, especially for
rootless, because a new window that is opened from the app will get it's
own unique persistent surface id. pasted will definitely need to be
modified to account for the rootless scenario.
Removing the xmir task...
** No longer affec
Is this on Zesty or X+O?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1675364
Title:
[Regression] xmir applications fail to render
To manage notifications about this bug go to:
https:/
Public bug reported:
I'm trying to use the '-fd' option in Xmir and get a crash when Xmir
starts up.
This is what I'm doing:
I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at
/tmp/.X11-unix/X0 (or whatever available display number). DISPLAY is
then set based on this. Then, whe
** Description changed:
I'm trying to use the '-fd' option in Xmir and get a crash when Xmir
starts up.
This is what I'm doing:
I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at
/tmp/.X11-unix/X0 (or whatever available display number). DISPLAY is
then set based
** Description changed:
I'm trying to use the '-fd' option in Xmir and get a crash when Xmir
starts up.
This is what I'm doing:
I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at
/tmp/.X11-unix/X0 (or whatever available display number). DISPLAY is
then set based
The following diff seems to fix the crash:
http://pastebin.ubuntu.com/24242549/
I haven't committed it yet since I'm really not sure if this method is
valid or if there is a bug.
After a client connects to the X socket and Xmir is started with the fd
returned from accept(), the client just hangs.
Ok, I've traced this down to bug #1675448 being the root of the issue.
Xmir is started no matter what and if an application natively supports
Mir such as a Gtk or Qt app, then there are multiple connections to Mir,
which is what the aforementioned bug is about.
So a decision needs to be made. Eit
signee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1672931
Title:
[regression] Qt & GTK apps on Unity8 are defaulting to Xm
Hey Daniel,
That xmir commit does not fix this issue:) It only fixes the crash. I'm
still working on a proper solution for xmir, which I'm close to
committing.
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are
** Changed in: libertine/devel
Status: In Progress => Triaged
** Changed in: libertine/devel
Assignee: Christopher Townsend (townsend) => (unassigned)
** Changed in: libertine/devel
Milestone: 1.8 => None
** Changed in: libertine/trunk
Milestone: 1.8 => None
*
For those that still see this issue, I'm tracking this under bug
#989588. I think I have a fix and will propose a solution soon. Please
follow that bug since this bug is already Fix Released.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xser
I did some investigating on Ted's u-a-l branch that starts Xmir
(https://code.launchpad.net/~ted/ubuntu-app-launch/xmir-support) and
removed the '-rootless' option to Xmir and now it works.
I guess it's easy enough to remove "-rootless" from the MP, but I
wouldn't think Xmir should be crashing wit
Public bug reported:
When having an Xmir window up and running and then trying to read or set
an xprop, the Xmir window immediately exits. This is what is printed in
application's upstart log:
(EE)
Fatal server error:
(EE) Failed to connect to Mir: Failed to process connect response:
/build/mir
I'm also adding Mir to this since the error kind of implicates it.
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1
I also ran xprop in gdb to see what may be causing the Xmir window to
clsoe and just the simple exit(0) at the end of xprop.c causes it to
close.
Based on the call to XCloseDisplay() and xprop exiting causing Xmir to
close, I'm wondering if Xmir is being too aggressive on cleaning up when
the appl
I'm not sure if Xmir crashes. I ran xprop w/ gdb and it just seems Xmir
exits when the client closes the display. I also don't get any crash
file nor any evidence of a core dump.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ub
Most definitely not the lack of the graphics drivers as I have those
installed on my machine and have a working Unity 8 desktop session.
Another data point is that this doesn't occur when running against
mir_demo_server, but only when running in a Unity 8 desktop session. I
start an Xmir instance
Public bug reported:
In trying to get Compiz working under Xmir in Unity 8 desktop mode, I
have found that when a Mir window opens and then resizes to whatever
Unity 8 tells it to, the resize event does not get propagated down until
another resize event occurs.
For example, I start up an X app.
Well, my patch-foo seems week as I can't seem to generate a good diff.
At any rate, here's what I'm proposing:
Using a fully patched source tree, open hw/xmir/xmir-input.c. Find the
xmir_handle_input_in_main_thread() function. In the
mir_event_type_resize case add the following after the ErrorF(
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enabling typical
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll wheel not workin
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour and windo
Since the proposed patches to X have been rejected, what can be done
here to fix this properly?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrolling with a touc
Yes, this is most likely a mesa bug and the software renderer will
result in high CPU usage.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
** Changed in: compiz
Status: Invalid => In Progress
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: compiz
Milestone: None => 0.9.11.0
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** C
** Also affects: compiz
Importance: Undecided
Status: New
** Changed in: compiz
Status: New => In Progress
** Changed in: compiz
Importance: Undecided => High
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed i
** Changed in: compiz
Status: Invalid => In Progress
** Changed in: compiz
Importance: Undecided => Medium
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: compiz
Milestone: None => 0.9.11.0
** Also affects: co
** Also affects: compiz
Importance: Undecided
Status: New
** Changed in: compiz
Status: New => In Progress
** Changed in: compiz
Importance: Undecided => High
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed i
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enabling typical bindings in "Desktop-ba
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrolling with a touchpad is jerky with bindi
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll wheel not working in gedit & System Moni
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour and window focus has changed and
** Changed in: compiz
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll wheel not working in gedit & System Monitor
T
** Changed in: compiz
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour and window focus has changed and is inc
** Changed in: compiz (Ubuntu)
Status: In Progress => Fix Released
** Changed in: compiz
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/11
** Changed in: compiz (Ubuntu)
Status: In Progress => Fix Released
** Changed in: compiz
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/12
** Changed in: compiz (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behaviour and window focus has changed an
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1268146
Title:
Very high cpu usage for compiz in 14.04 (mesa incorrectly using
** No longer affects: compiz
** Also affects: compiz
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.net/bugs/269904
Title:
Screen refre
=> In Progress
** Changed in: compiz
Importance: Undecided => High
** Changed in: compiz
Assignee: (unassigned) => Christopher Townsend (townsend)
** Also affects: compiz-core
Importance: Undecided
Status: New
** Also affects: compiz-core/0.9.8
Importance:
@Ryan,
This bug is about random log off's, not preventing a machine from going
to sleep and issues derived from that. I believe you commented in the
wrong bug. Please either find an appropriate bug or enter a new bug
report altogether. Thanks!
All others,
This is a bug closed as Fixed Released
Hi Joey,
I doubt this is a Unity issue. However, I'm trying to determine how you
are setting your resolution. I see you are using the binary fglrx
driver from the Ubuntu archives, so are you using the Catalyst Control
Center or are you using the Displays settings in Ubuntu to set your
resolution
On or around April 17, a new version of mesa (9.1.1-0ubuntu1) was
released which pulled in a pretty big upstream mesa release. I'm
thinking this could be a source of the issue here, so I'm going to open
up a mesa package task on this bug in the hopes that someone familiar
with the mesa workings ca
Marking the Unity bug invalid and duping this bug to bug #982889 since
the bug reporter is pretty confident the lightdm/plymouth updates fix
this.
** Changed in: unity
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Well, I would mark this as a duplicate to bug #982889, but the "Save
duplicate" function of the "Mark as duplicate" feature has been broken
all day:/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs
So apparently the reason why it can't be duplicated to bug #982889 is
because of a performance issue in Launchpad (see
https://answers.launchpad.net/launchpad/+question/227581 for more info).
I don't really feel comfortable changing the bug status in that bug in
order to duplicate this bug, so I gu
rogress
** Changed in: libertine/trunk
Status: New => Triaged
** Changed in: libertine/trunk
Importance: Undecided => High
** Changed in: libertine/devel
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: libertine/trunk
Assignee: (unassigned) =&
** Changed in: libertine/trunk
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "Xmir ro
** Changed in: libertine/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "X
** Changed in: libertine/trunk
Milestone: None => 1.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "Xmir root window"
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "
** Changed in: libertine/devel
Milestone: None => 1.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "Xmir root window"
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1542028
Title:
xapp window should reflect app name rather than "
After doing some more investigation, there is a new Mir input event
called mir_event_type_keymap which is sent every time a Mir surface is
focused. This event should be caught by Xmir and handled by applying
the sent keymap to the current Xmir/Mir surface.
** Also affects: xorg-server (Ubuntu)
Hey Daniel,
I'm not I understand the correlation between this bug and bug #1565236.
The referenced bug seems something specific to Unity 8 & Mir whereas
this bug is about getting the keymap correct for the apps in the Xmir
surface.
--
You received this bug notification because you are a member o
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => In Progress
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I have a fix ready in the attached patch. The fix is in Xmir and the
patch is just a refreshed xmir.patch with the added code. Let's try to
get this in for OTA11.
** Patch added: "xmir.patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1566487/+attachment/4649239/+files/xmir.p
1 - 100 of 235 matches
Mail list logo