Public bug reported:
On previous versions of Ubuntu, after 5 minutes, my monitor would turn
off as per settings. Since I reinstalled fresh 21.10, this is not
happening. Screen becomes black and stays powered on.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
@bozubuntu
hey, thanks for the report, but this bug is for the discontinued unity8
desktop. I suggest you log a bug against ubuntu-desktop with as much
information as you can supply:
https://bugs.launchpad.net/~ubuntu-desktop
exo-open is new to me, have you tried xdg-open?
--
You received
Public bug reported:
I was doing the update from 16 to 18
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: language-pack-gnome-en-base 1:16.04+20160627
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion:
Reopening as Mir has sufficiently good Wayland support to support Qt5.
qtubuntu can be removed from the archive
** Changed in: qtubuntu (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ok, VMWare is setting the current crtc mode at a generic 800x600, which isn't
in the list of modes for the connected display. Only approach I see is to
compare the mode name with "preferred", for which I see prior art:
https://github.com/wayland-project/weston/blob/master/compositor/main.c#L1068
Problem is that the "real" KMS platform is unable to determine the
current mode when running on VMware, leaving the current_mode_index at
an invalid value of UINTMAX, which is being passed through to the nested
platform.
--
You received this bug notification because you are a member of Ubuntu
Relevant info to reproduce:
Saviq, the first way to test the multiple-connection situation
would probably be to create a custom .desktop file that removes
GDK_BACKEND from the app's environment, which will force it to autoprobe
and use Mir instead
--
You received this bug notification because
** Branch linked: lp:~gerboland/qtmir/nouveau-workaround
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in
I've an ancient NVidia box at home, can try it out. I'm attaching
patches for qtubuntu/qtmir to force Qt to use single threaded GL on
nouveau.
** Branch linked: lp:~gerboland/qtubuntu/nouveau-workaround
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Was suspecting this is bug 1536279 but they don't quite match either
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1675357
Title:
Mir sending key repeat events continually
Turning on input event printing[1], when using Ctrl+Alt+F1 switching
away from unity8, I see a continuous stream of input events being sent
from Mir to Unity8, while on VT1:
[2017-03-23:12:36:53.419] qtmir.mir.input: Received
MirKeyboardEvent(action=repeat,key_code=0x1008ff2b). Dispatching to
Ok, no need for separate bug, the updated description shows me what you
want.
** Package changed: qtmir (Ubuntu) => qtubuntu (Ubuntu)
** Changed in: qtubuntu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Could you log separate bug about QWindow::raise/QWindow::requestActivate
against qtubuntu. Mir has an api for that, but we've not implemented it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
, please re-open this
bug and say why. I'd definitely like to know what your use-case is.
-G
** Changed in: qtubuntu (Ubuntu)
Status: New => Invalid
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification becau
Oh, I was the original author! Hah :D
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1238838
Title:
[qpa] QUbuntuIntegration requests screen info which open mir client
Thanks for that. Can confirm it is nothing gpu/graphics related, it is a
bug in our UITK. Fix on the way...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1671449
Title:
Hey dinamic! Thanks for the bug!
Did this happen suddenly, or you never see shadows at all?
What GPU and driver are you using?
Could you provide a pastebin of the unity8.log file, ideally just after
unity8 starts up so we get the initial output as unity8 starts.
--
You received this bug
Actually, might be easier/more-reliable just to edit /etc/environment
and add "QSG_RENDER_LOOP=basic" and restart.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1553328
I have Qt configured (in QtUbuntu/QtMir) to use multi-threaded GL
rendering, so we're probably hitting Nouveau's limitations here.
As workaround, I can add code to QtUbuntu/QtMir use single-threaded GL
for Nouveau.
If this is easily reproduced, can you try
initctl set-env --global
Looking into QtMir, we're only using the relative mouse motion in our
calculation of the cursor position. We need that to implement the push-
against-screen-edge behaviour for a mouse.
We've not considered tablet input devices at all. I see Mir's associates
a device with each input event, so it
Looking into QtMir, we're using relative
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1670670
Title:
Unity8 pointer does not stay in sync with Qemu VM tablet input
Status
> Also very important that those apps (toolkits) choose native Mir over
> X when both are available.
Qt isn't designed to make the choice itself, it expects to be told if either X
or Mir should be used.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: mir (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1670670
Title:
Unity8 pointer does not stay in sync with Qemu
> AFAIK the only thing stopping us from using Mir's native input coordinates
> was the inability to implement barriers/edge resistance in places.
We had other use-cases where unity8 having control over mouse position
was useful. One example coming to mind is phone docked to an external
display,
I tried on Zesty with my AMD machine, no lock up for me. Browser comes
up ok. I do get lots of libGL errors though
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
@vanvugt - yep it's not ideal. For phone/tablet, to make device rotation
animation as good as we could, was easiest to give the OSK a fullscreen
surface and have it rotate itself, letting application shine through in
the translucent area.
But that is certainly an area we can improve.
** Changed
I've tracked this down to the following mir bug:
https://bugs.launchpad.net/mir/+bug/1670876
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1669444
Title:
[regression] OSK
Probably also relevant: https://bugs.launchpad.net/mir/+bug/1560498
** Tags added: unity8-desktop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1670717
Title:
Unity8/mir
Mir needs to support whatever API VMs use to communicate the "display"
size changed. QtMir supporta display sizes changing already (can been
seen by changing resolution)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
ethod Surfaces created, removing the old one!" but it fails to work
anyway.
** Affects: unity8 (Ubuntu)
Importance: Medium
Assignee: Gerry Boland (gerboland)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1655644
Title:
unity8 crash after create a new online
Does Mir provide enough api to allow application ask user a question
before shutdown? In Unity7, typically that is requesting focus and
popping up a dialog - should be ok, but good to think about it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: qtmir
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1597205
Title:
Not sending relative
One small warning message is printed during display on flicker:
http://pastebin.ubuntu.com/24053776/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1667001
Title:
[amd]
Ok, with Alexandros' help I've dug a bit more.
On my hardware, I tear everything down and just run
sudo mir_demo_server_basic --arw-file
I can see clients ok.
I forked mir_demo_client_display_config to add extra bits:
https://code.launchpad.net/~gerboland/+git/display-configurator
which
@alf:
http://pastebin.ubuntu.com/24053520/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1667001
Title:
[amd] screen-unblanking seems to flicker backlight on/off 5 times
Public bug reported:
Peek is a utility to grab screencast to animated GIFs.
They have an open bug to add Mir support:
https://github.com/phw/peek/issues/39
Current mirscreencast util only works as root, due to Unity8 replacing
the renderer with its own custom one (which does not support
Here is what Qt is doing, on upload:
https://code.woboq.org/qt5/qtdeclarative/src/quick/scenegraph/qsgdefaultdistancefieldglyphcache.cpp.html#158
It saves & restores the alignment, and assumes the default alignment of 4 for
drawing. IMO Mir isn't playing along, as it changes the alignment but
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1665705
Title:
Deleting a QRasterWindow crashes
Status in qtubuntu:
Yep can reproduce easily. Obvious fix is to remove the makeCurrent call
from the BackingStore destructor, but that undoes a previous fix I made
for surface resizing errors. I need to study the other QPAs to see what
they do
--
You received this bug notification because you are a member of Ubuntu
** Also affects: qtubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1665705
Title:
Deleting a QRasterWindow crashes
** Changed in: qtubuntu (Ubuntu)
Status: New => Confirmed
** Changed in: qtubuntu (Ubuntu)
Importance: Undecided => Critical
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
--
You received this bug notification because you are
I've hacked qtmir to print the subpixel hint that Mir is supplying.
http://pastebin.ubuntu.com/24007971/ is my output. First I run a simple
qml demo shell as nested server under USC, get "0" hint.
Then I run again as host server, get a hint "1 = RGB".
The "Subpixel hint" output of the 2 cases
Just testing it now, AFAICS a nested server is not getting the correct
subpixel data passed to it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1393578
Title:
Subpixel
UITK already using NativeRendering for text when GU<10.
Text *might* be improved by setting Qt's DPI and sub-pixel rendering
hints correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1583088
Title:
Randomly corrupt font / text /
d
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Description changed:
- Corrupted characters in text rendering, mainly in Unity8 window
- titlebars.
+ Corrupted characters in tex
I'm looking into this now. I took an api trace of some simple font
rendering by Qt on Mir showing the problem, and executed it on my X11
session. It renders ok on X11. Reading through the apitrace, Qt seems to
be doing the right thing.
I suspect the mismatch we have between Mir creating a GLES
@kgunn - yes I can reproduce it quite reliably too. No need to try the
glyph cache workaround thing, I checked it and it had no impact.
@duflu - Qt is rendering the text.
Since Qt renders text ok in Unity7, there must be some GL configuration
problem in QtMir/QtUbuntu causing this kind of issue.
I've a bunch of questions. Any time you see EGL complaints, it is often
down to the graphics driver.
1. is this complaint for an NVidia-based system only? The log indicates
it has the proprietary nvidia driver installed, which Mir does not
support (and so Unity8 does not run). How are you
** Changed in: qtmir
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title:
[regression] OSK appears blank
One backtrace, slightly confusing: http://pastebin.ubuntu.com/23874652/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1655644
Title:
unity8 crash after create a new
Relevant unity8.log output before crash:
http://pastebin.ubuntu.com/23874565/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1655644
Title:
unity8 crash after create a
Yes mir_output_set_scale_factor is needed, as the settings app needs an
API to communicate the desired scale factor to unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
So while a menu is open, only that surface should get mouse hover
events.
That is how things work today. Do we want Design input on that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Public bug reported:
Version in the pkgconfig file is 0.2
Version of libcontent-hub according to the debian packaging is 0.3.x
The minor version should match at least, no?
** Affects: content-hub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Ok, rather marginal use-cases then :)
At least Mir allows this kind of request can be filtered by Unity8 in
future, to prevent this kind of thing being abused. Perhaps need a
system so that privileged clients can do this if they need.
--
You received this bug notification because you are a
> It is actually valid for apps to be able to change the power mode
> of the display. mirout in Mir 0.26.0 has such an option. But I agree
> it's bad for apps to do it unexpectedly
@vanvugt can you share examples of times when this is valid? I'm of the
opinion display on/off/suspend should be
ged in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Branch linked: lp:~gerboland/qtubuntu/quit-gracefully-on-no-
mirconnection
** Changed in: qtubuntu (Ubuntu)
Status: New => In Progress
** Changed in: qtubuntu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qtubuntu (Ubuntu)
Assignee: (unassigned) => Ger
So is actual desired fix to not crash, just quit gracefully?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1655936
Title:
clients crash with
I'm adding Oxide to the bug, as the browser chrome is being rendered ok.
I also see these strings in the browser log:
[0111/095625:ERROR:layer_tree_host_impl.cc(2189)] Forcing zero-copy tile
initialization as worker context is missing
[0111/095625:ERROR:oxide_compositor_gpu_shims.cc(258)] Error
I'm failing to reproduce this unfortunately. I'm also failing to create
a libertine container. It was failing due to bug 1653973, so I installed
silo 2341, but now it fails with:
Failed to download http://images.linuxcontainers.org//meta/1.0/index-user
LxcContainer.py:254: ERROR:
** Branch linked: lp:~gerboland/qtmir/initial-surface-expose
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: qtmir
Status: Confirmed => In Progress
*
Please paste in the output of
dpkg -l | grep mir
and the contents of the greeter process log around the time of this crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1413121
Title:
MainView is missing an API to dynamically set supported orientations
Status in
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1504551
Title:
Text input popover and selection cursors not oriented properly in
shell
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1462489
Title:
Allow apps to keep the screen on
Status in Canonical System Image:
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1510968
Title:
external monitor grid units are not set correctly
Status in Canonical System Image:
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1558663
Title:
Ubuntu Components is hard on the disk and CPU when loading images
Status in
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1621370
Title:
UITK on Intel i915 (atom)is very slow
Status in ubuntu-ui-toolkit package
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1647415
Title:
units.gu() emits changed signal before completion
Status in
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1585723
Title:
UbuntuShape on intel i915 (Atom) uses fallback CPU rendering
Status in
** Tags added: unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1573118
Title:
"units" context property is app-global
Status in ubuntu-ui-toolkit package
Unity8 is overriding the client-requested window size in phone/tablet
mode, but this shouldn't be happening for desktop mode.
We also need to save the client-requested window geometry in case shell
later wishes to apply that.
Agreed I'd like a specific example
** Changed in: qtmir (Ubuntu)
Could you also share hte output of
xargs -n 1 -0 < /proc/`pidof unity8`/enviro | grep QT_
in case there are Qt dynamic scaling env vars set in your environment
too. (e.g. QT_DEVICE_PIXEL_RATIO, QT_AUTO_SCREEN_SCALE_FACTOR,
QT_SCALE_FACTOR, QT_SCREEN_SCALE_FACTORS)
--
You received this bug
Oops, safer to use grep:
xargs -n 1 -0 < /proc/`pidof unity8`/environ | grep GRID_UNIT
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1642272
Title:
incorrect UI scale on
Contents of $HOME/.cache/upstart/unity8.log might be handy too
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1642272
Title:
incorrect UI scale on high-resolution desktop
Hey,
this is weird. Would you be able to open a terminal and run the following
command:
xargs -n 1 -0 < /proc/`pidof unity8`/environ | ag GRID_UNIT
(it prints all the environment variables that the unity8 process has, and just
returns the GRID_UNIT_PX one)
Thanks
-G
--
You received this bug
Yeah the unity8 log makes me suspect qtmir, it deals with disabling the
display ok, but enabling it doesn't yield 2 screens again
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Status: New => Confirmed
** Changed in: qtmir
Importance: Undecided
QtMir/Unity8 is designed to deal with spanning displays - it is actually
cloned displays it needs work to support!
@jonas Could you give us a means to test this behaviour?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Can you give me steps to repro the problem clearly?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1628646
Title:
new windows not respecting width and height
Why is there not a better fallback cursor than a fully blank one?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1625853
Title:
Mouse cursor disappears (or just never
AFAICS Mir has means to ask clients to close windows, but I don't see an
API to ask the client itself to quit.
** No longer affects: unity (Ubuntu)
** Changed in: qtmir (Ubuntu)
Status: New => Confirmed
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Medium
--
You received
Note it is only Unity8 which is mixing GL and GLES calls, clients are
not doing that. Qt clients are only doing GL calls on desktop.
Nothing obvious comes to mind here.
It may be Qt's EGL configuration code is failing - code that QtUbuntu is
using. Another consumer of that same code is the EGL
This issue was worked around, but with a far-from-ideal solution
** Also affects: lttng-ust (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qtmir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtmir (Ubuntu)
Status: New => Triaged
** Changed
I'd be interested if this makes any impact:
https://code.launchpad.net/~gerboland/qtubuntu/eglconvenience-
retry/+merge/298114
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
Ah no, I'm reading the API wrong (kudos to faenil for correcting me):
QPoint pixelDelta
is in integers, as are all QWheelEvent calculations. So that's not going to
work without breaking Qt APIs, which is unlikely.
An alternative option might be to us Qt's support for native gesture
events - this
Are you looking at the right code? I see this from Qt5.4 source
(qtbase/src/gui/kernel/qwindowsysteminterface.h)
static void handleWheelEvent(QWindow *w, const QPointF & local, const
QPointF & global, QPoint pixelDelta, QPoint angleDelta, Qt::KeyboardModifiers
mods = Qt::NoModifier,
https://github.com/libhybris/libhybris/pull/316 has been landed. I can
remove the QtUbuntu workaround
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1594198
Title:
Of course we will. We need to re-land the fix. It was reverted because
it broke something else, but that's been solved now. Sorry for the
delay, but it takes time to get things done just right.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
That would imply the distance field texture is corrupted.
As a note to myself, there is a nice glyph test application in this bug:
https://bugreports.qt.io/browse/QTBUG-49490
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Also worth noting, there are env vars:
QT_DEFAULT_TEXTURE_GLYPH_CACHE_WIDTH & HEIGHT to set the size of the glyph
cache. Need to see what size texture Qt is creating, perhaps it is creating one
too large for the hardware
--
You received this bug notification because you are a member of Ubuntu
If you can reproduce this relative easily, could you try setting
QML_USE_GLYPHCACHE_WORKAROUND=1 for unity8. This should do the trick:
stop unity8 && start unity8 QML_USE_GLYPHCACHE_WORKAROUND=1
Can also try these:
QSG_DISTANCEFIELD_ANTIALIASING=subpixel-lowq or gray
Need to determine if that
QPA has nothing to do with rendering itself, and only selects the
default unix font renderer for Qt to use.
We need information on your hardware, linux install, GPU, etc. I suspect
a MESA bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1585723
Title:
UbuntuShape on intel
https://github.com/libhybris/libhybris/pull/316 has a better solution to
this issue for now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1594198
Title:
Terminal app
Digging into the actual root cause, QOpenGLES3Helper has QLibrary load
"libGLESv2.so" but this is failing. Using LD_DEBUG=libs you can see:
5646: find library=libGLESv2.so [0]; searching
5646: search path=/vendor/lib:/system/lib
(LD_LIBRARY_PATH)
5646:
My eglconvenience branch does cause this, but annoyingly by doing the
correct thing.
Before eglconvenience, we hardcoded GLESv2.0 into QtUbuntu. With
eglconvenience, we query the GL version string and correctly fetch the
GL version the driver supports. On several of our devices, that is
actually
1 - 100 of 407 matches
Mail list logo