** 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
I will add that when I see this in Pidgin, it leads me to believe
someone has highlighted me, but no, no one has and I just spent some
time context switching. And this keeps happening over and over again...
@dean, indeed, but Pidgin is wasting lots of my time with this
nonsense:)
--
You
I'll add that since updating from 18.04 to 20.04, Pidgin has been doing
this very consistently. Whenever I have Pidgin focused and then switch
focus to another window, some time later, I get a notification saying:
Pidgin Internet Messenger
"#foo" is ready
where #foo is the name of the last chat
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
signee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1672931
Title:
[regression] Qt & GTK apps on Unity8 are defaulting to
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.
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
** 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
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,
Is this on Zesty or X+O?
--
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/1675364
Title:
[Regression] xmir applications fail to render
Status in Canonical System Image:
Triaged
** Also affects: libertine
Importance: Undecided
Status: New
** Also affects: libertine/devel
Importance: Undecided
Status: New
** Also affects: libertine/trunk
Importance: Undecided
Status: New
** Also affects: libertine (Ubuntu)
Importance: Undecided
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
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,
** 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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846
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:
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846
Title:
Xmir
*** 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 Desktop
Packages,
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
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)
--
This has been the case since day 1 of Unity on the desktop. See bug
#1307618. Not sure why we never added unity8 to that bug, so let's dupe
that bug to this one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Err, I meant Unity *8* on the desktop:)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1644237
Title:
unity8 fails to start as guest user
Status in lightdm package in Ubuntu:
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
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
*** 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
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 Desktop
Packages, which is subscribed to xorg-server in
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1617932
Title:
Xmir with glamor is spending 11% of its CPU
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1581076
Title:
Xorg segfaults on start-up on Big Endian PPC
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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
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
** 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
** 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
** 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.
** 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
** 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
** 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
** 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.
+
+
** 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)
** 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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1471998
Title:
** Changed in: libertine (Ubuntu)
Status: Confirmed => 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/1591356
Title:
keyboard autorepeat in Xmir apps & GTK-on-Mir
Strange, I'm running a fully updated Yakkety system and Firefox and Gtk
apps start just fine in the Yakkety based Libertine container. The Mir
error in the attached logs look really fishy though...
--
You received this bug notification because you are a member of Desktop
Packages, which is
Looks to be a potential regression in Xmir due to the backtrace in the
Firefox log. Adding that package to the bug.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
You received this bug notification because you are a member of Desktop
** Also affects: content-hub (Ubuntu)
Importance: Undecided
Status: New
** Changed in: content-hub (Ubuntu)
Status: New => In Progress
** Changed in: content-hub (Ubuntu)
Importance: Undecided => Medium
** Changed in: content-hub (Ubuntu)
Assignee: (unassigned) => Ken
Invalidating the xmir part of this since this is going to be handled
using the pasted daemon, content-hub, and support in Qt.
** Branch linked: lp:~townsend/libertine/pasted
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
ibertine/devel
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: libertine/devel
Milestone: None => 1.3
** Changed in: libertine/trunk
Milestone: None => 1.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
This is actually Xmir using software rendering on armhf platforms as
Glamor in Xmir on that platform is not ready for prime time.
Marking xorg-server and use the xmir tag.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
You received
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
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.
** Changed in: libertine/trunk
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/1543351
Title:
Add on-screen-keyboard support for
** Branch linked: lp:~brandontschaefer/libertine/seed-packages-
workaround
** Changed in: libertine/devel
Status: In Progress => Fix Committed
** Changed in: libertine/trunk
Status: Triaged => In Progress
** Changed in: libertine/trunk
Milestone: None => 1.2
** Changed in:
** 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:
** Changed in: libertine
Milestone: 1.1 => 1.2
--
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/1543351
Title:
Add on-screen-keyboard support for Xmir/Libertine apps
Status in
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
@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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1573470
Title:
BQ M10 tablet. Libreoffice Impress
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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 Desktop
Packages, which is subscribed to
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
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1566487
Title:
Container apps should use same keyboard layout
@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
** 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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543351
Title:
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
@ 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 Desktop
Packages, which is subscribed to
** 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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is
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"
** 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 Desktop
Packages, which is subscribed to xorg-
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
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)
** Changed in: libertine/devel
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/1542028
Title:
xapp window should reflect app name
** Changed in: libertine/devel
Milestone: None => 1.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/1542028
Title:
xapp window should reflect app name rather than "Xmir root
** Changed in: libertine/trunk
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/1542028
Title:
xapp window should reflect app name
** Changed in: libertine/trunk
Milestone: None => 1.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/1542028
Title:
xapp window should reflect app name rather than "Xmir root
@Simon,
No, what I meant was that I have my phone paired with my car and as soon
as I answer a call or dial a number, the audio does not play over the
car's speaker. And many times when this happens, the phone and/or car
disconnects and then reconnects.
Sorry, I cannot provide any logs at this
** Changed in: libertine/trunk
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/1542028
Title:
xapp window should reflect app name
I should add that nothing fails when lsmod is not present, but i915
detection will not work properly without it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1552298
Title:
After looking at this further, I don't think this is really an issue. I
think something else is causing the failure we are seeing, so I'm going
to mark this Invalid.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
** Changed in: libertine/trunk
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/1542028
Title:
xapp window should reflect app name rather than
Public bug reported:
When trying to use Chromium on a Freiza tablet, /proc/modules does not
exist, thus the following workaround fails:
lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1
and causes /usr/bin/chromium-browser to fail.
That line should catch any errors from lsmod,
Public bug reported:
The chromium-browser package should depend on the kmod package due to
the following workaround in /usr/bin/chromium-browser:
lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1
There are situations in which chromium-browser can be installed without
kmod already
n Progress
** 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: avila
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858
Title:
Some puritine packaged apps don't open on some
** Also affects: libertine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libertine (Ubuntu)
Status: New => In Progress
** Changed in: libertine (Ubuntu)
Importance: Undecided => Critical
** Changed in: libertine (Ubuntu)
Assignee: (unassigned) => Ch
I need to get a silo for Libertine and then get it in the overlay PPA
and then it will be picked up in an image build.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858
Title:
: New => In Progress
** Changed in: puritine
Status: In Progress => Invalid
** Changed in: libreoffice (Ubuntu)
Status: Opinion => Invalid
** Changed in: libertine
Importance: Undecided => Critical
** Changed in: libertine
Assignee: (unassigned) => Chris
After chatting w/ kgunn, I found out that the M10 is based on the
aarch64 architecture whereas the Puritine chroot is made using the armhf
architecture. I'm betting that some library is not liking the
discrepancy in architectures. We need to test this theory by making a
proper aarch64 Puritine
I think the important parts of the log are these:
[Java framework] Error in function createSettingsDocument (elements.cxx).
javaldx failed!
Warning: failed to read path from javaldx
Searching for those types of errors generally leads to permission
problems on folders. However, I've been looking
So, I think we have finally figured out the cause of the issue. The
kernel on the m10 is aarch64 as denoted by uname -a:
$ uname -a
Linux ubuntu-phablet 3.10.93+ #11 SMP PREEMPT Wed Jan 13 08:30:56 EST 2016
aarch64 aarch64 aarch64 GNU/Linux
We use proot to call into the unprivileged Puritine
After doing some debugging on an M10, I'm pretty sure this isn't an arch
issue as the arch Ubuntu uses is armhf. More debugging to do to figure
out what might be causing this. I'm also pretty sure the pango warnings
in the logs are benign.
--
You received this bug notification because you are
Could you please provide ~/.cache/upstart/application-legacy-
puritine_libreoffice-startcenter_0.0-.log?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1532858
Title:
[Avila]
** Changed in: libertine (Ubuntu)
Status: New => Fix Released
** Changed in: libertine (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
I'm switching window managers in Libertine. We will now be using
Matchbox which is a very small and simple WM. When using Matchbox,
single window mode in Gimp is correct.
Once we release Libertine, I'll close out this bug.
--
You received this bug notification because you are a member of
Compiz is indeed running, but it is refusing to manage the window.
Looking at the Compiz code, there are only two ways that it will not
manage a newly created window:
"if (w->priv->serverFrame == event->xcreatewindow.window)"
and
"if (wa.root != event->xcreatewindow.parent)"
Those will prompt
*** This bug is a duplicate of bug 1517615 ***
https://bugs.launchpad.net/bugs/1517615
After some investigation, this is due to lightdm hard coding an option
passed to unity-system-compositor to enable the hardware cursor. Since
Unity 8 now provides its own cursor, this option is no longer
Public bug reported:
Recently, Unity 8 provides its own cursor, so we no longer need the
"--enable-hardware-cursor=true" option in unity-system-compositor.
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Affects: lightdm (Ubuntu Vivid)
Importance: Undecided
I really don't think this is a Libertine issue in and of itself. Looks
more like Xmir may be the culprit, at least that is probably where the
investigation should start.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
You received this
And another data point is that the scaling issue did not occur on my N4
when using Xmir from https://launchpad.net/~libertine-
team/+archive/ubuntu/devel/+packages.
As a matter of fact, I downgraded xmir to the version in the libertine
PPA and the scaling issue no longer occurs, so I'm pretty
1 - 100 of 827 matches
Mail list logo
