Ok, now I can use the multimedia and other special keys on my Microsoft
Digital Media Keyboard 1.0A and the mouse keeps working fine.
*But* my function keys (F1, F2, etc) don't work anymore. I've plugged in
a Dell keyboard as well (besides the Microsoft one) and the Dell one
keeps working just
@Daniel: Does your keyboard have an F-lock key like mine? If so,
check that it's on.
You're right. Thomas. I forgot about this key. It's been such a long time since
I last pressed it. :-)
Everything is working fine then.
--
You received this bug notification because you are a member of
Might have the same root cause as
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701
--
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/1298727
Title:
Xorg crashed with SIGABRT in
Took the liberty of correcting the bug title as unity does keep getting
touch events. It's the xserver mouse pointer emulation from touch events
that breaks badly.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Attaching detailed xserver log. The following steps were taken:
1- sudo restart lightdm (to restart the X server. so that de have a clean slate)
2- run a very simple qml app with qmlscene
3- tapped on that qmlscene window (touch id 1)
4- tapped on the desktop area (nautilus) (touch id 2)
5- sudo
xserver packages I used to take the logs above.
** Attachment added: xserver debian packages with detailed logging of input
events
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/+attachment/4106288/+files/xorg_debug_packages.zip
--
You received this bug notification because
Excerpt from #xorg-devel:
dandrader daniels, I've the following situation: clientX has a
XISelectEvents(TouchBegin|Update|End, childWindowA, slaveDevice1); clientY has
a XIPassiveGrabDevice(TouchBegin|Update|End|Ownership, rootWindow,
AllMasterDevices)
daniels, when a touch reaches xserver,
Is there a specific reason for calling XISelectEvents() for each
slave vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt?
Would have to dig into Qt code to tell that. But my guess is that
because it exposes QTouchDevice objects to applications. For every
QTouchEvent you can get
And here's the upstream bug I reported:
https://bugs.freedesktop.org/show_bug.cgi?id=78345
** Bug watch added: freedesktop.org Bugzilla #78345
https://bugs.freedesktop.org/show_bug.cgi?id=78345
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I confirm that the Qt from
https://launchpad.net/~canonical-x/+archive/x-staging does
XISelectEvents on the master pointer (instead of the touchscreen slave
device, as previously) and that the resulting behavior of the xserver is
good. Ie., touch ownership mechanics work properly and mouse pointer
Qt still XISelectEvents my N-Trig Pen stylus and N-Trig Pen eraser
slave devices though. But thankfully no events come from them and thus
peace is maintained :)
** Changed in: unity (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of
unity8 now supports applications with multiple top-level surfaces (shown
as windows in unity8). I suppose that might have fixed this bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: qtmir (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: qtmir
Status: Confirmed => Fix Released
** Changed in: unity8 (Ubuntu)
Status: Opinion => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Branch unlinked: lp:~dandrader/qtmir/cursorConfinement
--
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/1590099
Title:
Need to support pointer confinement in Mir and toolkits using Mir
** Branch linked: lp:~unity-team/qtmir/cursorConfinement
--
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/1590099
Title:
Need to support pointer confinement in Mir and toolkits using Mir
On 13/09/2016 08:49, Gerry Boland wrote:
> Could someone with a problematic system log into Unity7, and for a simple qml
> file, run:
> QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml
> and see does it fail?
It works fine.
--
You received this bug notification because you are a member of
Maybe the culprit is different Qt versions between xenial and yakkety?
--
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/1620934
Title:
Qt/QML apps don't render any more (logs say
This only happens in yakkety. The same qtmir, qtubuntu and unity8 runs
fine in xenial. Lost a couple of hours on this issue yesterday and my
"solution" was to reboot my test laptop into a xenial partition so I
could unblock myself.
--
You received this bug notification because you are a member
qtbase-opensource-src did get a new release on september 3rd. But xenial
stable-phone-overlay and yakkety seem to be carrying the very same qt
version, so scrap my theory from comment #30...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
Looks like you have multiple bugs in a single report. Not good.
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ub
Anyway, will investigate the one about kate toolbar buttons.
--
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/1669432
Title:
[unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
This is the first bug: Bug 1670361
--
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/1669432
Title:
[unity8] qt/gtk apps don't quite work in fullscreen/tablet mode
To manage notifications
The second issue is bug 1670390.
As for the crashes you mention, please be more specific (with a step-by-
step use case), preferably in a separate bug report.
** Changed in: unity8 (Ubuntu)
Status: In Progress => Incomplete
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Invalid
23 matches
Mail list logo
