** Attachment added: "For reference, the same video in Totem."
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181989/+files/Screenshot_20180828_205430.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to me
Freedesktop tells me it's a downstream Debian script file.
https://gitlab.freedesktop.org/xorg/meta/issues/6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1789523
Title:
The ssh-agent launcher
I only thought to mention the PPA to indicate that the bug still occurs
even in fairly bleeding edge Mesa code. I also still think it's either
something wrong with gstreamer-vaapi, or something that gstreamer-vaapi
is doing different from what mpv does for the same exact video. It
should probably b
Public bug reported:
Running startx starts X just fine, but at login I just get a blank
screen with a blinking cursor. If I hit Alt+F I can get a console
which allows me to login and run 'startx' at which point Gnome starts
normally after entering my keychain unlock password.
ProblemType: Bug
Dis
@ Julio A. Garcia Lopez
Well, you blame Canonical for not updating Kubuntu, which I think is kind of
unfair. Canonical is responsible for Ubuntu. Kubuntu is more a community
project supported by Canonical.
Of course you can have a try with Debian, at least then there is no company at
all to blam
First: Please do not quote full entries. This bug report is already full
of hundreds of posts so we do not need to have all those fully quoted.
I did not want to distinguish between blaming and criticising. I simply
meant that canonical is not responsible for kubuntu.
Because kde is _not_ officia
I'm starting to think that this has been patched for at least some
hardware, because I can no longer duplicate it on my HP G60 laptop in
Ubuntu 11.04. It hasn't happened in a long time in either Maelstrom or
Dosbox.
--
You received this bug notification because you are a member of Ubuntu-X,
whic
Public bug reported:
Ubuntu 20.04
No matter which virtual desktop is in focus, applications running on
other virtual desktop are displayed even if minimized. This makes it
impossible to interact with desktop icons without closing all running
applications. It is not possible to interact with the
** 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
*
Public bug reported:
Could not perform a system update upon fresh install
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libdrm-intel1:amd64 2.4.105-3~20.04.2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-
This bug affects me also. Fresh install yesterday.
Description:Ubuntu 14.04.2 LTS
Lenovo X230t
3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
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
Same message. Same observed behavior. On a MacBook Pro 11,1 (2013).
Happy to provide any other telemetry you all need.
--
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.launchpad.net/bugs/1462728
Ti
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(
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
I'm having a similar issue on Ubuntu 20.04. Currently, every time that I
reboot I'm unable to login. I just get a black screen after logging in.
I have noticed that if I first delete the contents of .config
Public bug reported:
have-no-space-bar.--no-#six--no-esc--and-other-key--functions--when-i-
instaled-Kubontu-20.four
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
.tmp.unity
Adding a comment to indicate that this is a problem with the 10bpc
support which is enabled in Radeon graphics. I am unsure if it is
enabled in Intel's drivers, so that would explain why it does not occur
there. Either VA-API is outputting wrong, the client library is
outputting wrong, or all the p
It appears it's still there, but only accessible to project members.
Which also excludes me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1789523
Title:
The ssh-agent launcher script fails to
As already stated above, the correct workaround, for now, is to
configure a drirc (probably in a conf.d directory, so it doesn't clash
with other settings files) so as to disable 10 bit per channel support
for Totem. The same had to be done with Chromium-vaapi, as it also
happens with that solution
This bug can only occur if 10bpc is enabled. There is no other
possibility. It is clearly a colorspace mismatch between VAAPI and the
decode target surface. If disabling 10bpc happens in Ubuntu Mesa
packages, then it is clearly someone using unofficial package builds of
Mesa which have 10bpc enable
Or as one user posted, the official AMDGPU Pro package, which also
enables 10bpc.
--
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/1767312
Title:
[radeon] Totem with gstreamer1.0-vaapi and Xorg: w
Public bug reported:
Failure to display prior desktop login GUI (Cinnamon).
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server i
I tried that and it didn't fix the problem. I am attaching the output of
some of those files again for further data.
** Attachment added: "dmesg output ( on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt
--
You received this
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
It seems unlikely to be a cable or signal problem since I can eventually
coax it into working, and it continues working until I reboot. If it
were a cable problem or something about the signal I would have to
physically modify the connection to create and/or correct the problem.
Since the mere act
I did plug/unplug the monitor because if I do that enough times is
generally resolves the problem until the next time I reboot. It has not
done so this time. I also tried a new cable, but that does not fix the
problem either.
--
You received this bug notification because you are a member of Ubunt
This is still 100% reproducible. I have attached the dmesg below.
** Attachment added: "dmesg from 2019/06/06"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5269157/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
w
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
https://bugs.launchpad.net/ubuntu/+sou
** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in U
This problem appears to be solved in Oneiric. I would go ahead and
close it out. I actually think updates fixed it before Oneiric came
out in Natty, but either way, it seems fixed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-v
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:
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
--
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.launchpad.net/bugs/1314924
Title:
Adressbox Entries
As I reported upstream (mozilla-bugs:1005501), the bug is due to
xserver-xorg-video-intel, and was fixed somewhere between 2:2.99.910 and
2:2.99.911 (c.f. freedesktop:79165).
The bug is therefore already fixed in 14.10, so it should be fixed in 14.04
once the 14.04.2 point release is published (
It may be possible to obtain the fix for 14.04 using the Intel Graphics
Installer 1.0.7, which installs xf86-video-intel 2.99.911.
--
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.launchpad.net/bugs
Public bug reported:
I connected two external monitors to my computer HP EliteBook 840:
Samsung S2RC450 over HDMI and Samsung SyncMaster 22BW over VGA. The
other connection is not visible in Ubuntu (xrandr says "DP2
disconnected").
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xo
https://bugs.freedesktop.org/show_bug.cgi?id=72795 > may be
relevant.
--
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.launchpad.net/bugs/1417124
Title:
Second monitor not used
To manage notific
You need to upgrade to the version for the 14.04.2 point release
(2:2.99.914-1~exp1ubuntu4.2~trusty1), see
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https
I apologize, I didn't mean to boss anyone around. I'm not in charge, nor am I a
maintainer or triager, I am just another user. Please don't take this as
representative of the ubuntu community.
I talked briefly with a maintainer of xserver-xorg-video-intel, and they
suggested the procedure for i
@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
andvaranaut, thatk you for this workaround! I've been searching for
quite some time for a solution to this problem. (I also posted your
solution to the big thread devoted to muxless amd systems,
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404,
of course with proper attributio
Hello, I am just writing to say that there is also a workaround for raring.
I've been searching for this for some time so I thought that maybe this will
help somebody in a similar situation: the lastest intel driver apparently
causes trouble so reverting to the driver from the quantal repos make
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
This is a diff of the actual changes made.
** Patch added: "xmir-keymap.patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1566487/+attachment/4649241/+files/xmir-keymap.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
** No longer affects: libertine (Ubuntu)
** No longer affects: libertine/trunk
** No longer affects: libertine/devel
** Changed in: libertine
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubun
@ diogoconstantino,
You are hitting a different issue than what this bug is describing. The
login screen is not an Xmir app. I believe the bug you are hitting is
bug #1565236.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubun
We're adding both Mir and Xmir to this as we aren't quite sure where the
problem is.
** Also affects: mir
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
You received this bug notification beca
** Changed in: libertine
Status: Triaged => In Progress
** Changed in: libertine
Milestone: None => 1.1
--
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/1543351
Title:
Add on-sc
@pitti,
There is bug in the Xkb patch in Xmir that has been fixed and is in the
Vivid overlay. I think Robert will need to respin the Xmir patch to fix
the bug.
That said, I'll mark this verification-failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You receiv
** 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/1566487
Title:
Container apps should use same keyboard layout as Unity
Also, I should note that we should go the SRU route for any Xmir updates
instead of the overlay so we can stay in sync with X in the archive.
--
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
There is already a pending xorg-server in xenial-proposed that has the
latest Xmir- https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.3-1ubuntu2.2
I've done the verification for the one bug targeted by that SRU, so it's
a matter of waiting for it to be promoted to -updates.
--
You receiv
The committed branch is only part of the solution and not complete, so
marking the Libertine task back to In Progress.
** Changed in: libertine
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-serv
The last SRU has landed in xenial-updates, so considering this Fix
Released.
** Changed in: canonical-devices-system-image
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://
@Pat,
Ok, I'll see if I can make some config that can be delivered in
Puritine.
--
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/1573470
Title:
BQ M10 tablet. Libreoffice Impress presentat
Given that it has been reported that turning hardware acceleration off
causes other regressed behaviors, then I think forcing it off in some
config setting in Puritine is probably not the right thing to do.
I'm really not sure what the right thing to do is though...
--
You received this bug noti
** Changed in: libertine
Milestone: 1.1 => 1.2
--
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/1543351
Title:
Add on-screen-keyboard support for Xmir/Libertine apps
To manage notifica
** Also affects: libertine/devel
Importance: High
Assignee: Brandon Schaefer (brandontschaefer)
Status: In Progress
** Also affects: libertine/trunk
Importance: Undecided
Status: New
** Changed in: libertine/trunk
Status: New => Triaged
** Changed in: libertine/tr
201 - 300 of 9504 matches
Mail list logo
