[Ubuntu-x-swat] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Daniel van Vugt]

I spent a little time on this bug last week.

Was able to reproduce it, yes, but the spinning thread was apparently
the libmirclient input thread, and not in any Xmir code. I didn't have
sufficient libmirclient symbols to debug it further before running out
of time. I had assumed this was an Xmir bug but it looks like it might
actually be a Mir bug.

-- 
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/1671731

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1674455] Re: Keyboard input disables when laptop is rotated

[tim474]

UPDATE: Ctrl+alt+F1 and terminal doesn't work too.

But here is a workaround with disabling accelerometer:

echo "0" > "/sys/bus/usb/devices/1-2.4/power/autosuspend"
echo "auto" > "/sys/bus/usb/devices/1-2.4/power/level"
echo 1-2.4 > /sys/bus/usb/drivers/usb/unbind


(after power on and resume from suspend).

-- 
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/1674455

Title:
  Keyboard input disables when laptop is rotated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
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/1671731

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Stephen M. Webb]

This is simple to reproduce.  The application has disappeared from the
screen but continues to run.

It looks like qtmir is closing the window (as requested) but no word
gets out to the actual process (ie. there is no session management).
I'm suspecting the Unity 8 lifecycle for desktops is not in place yet.

Here's a snippet from $HOME/.cahe/upstart/unity8.log.

[2017-03-20:19:34:52.953] qtmir.sessions: TaskController::onSessionStarting - 
sessionName=sol^M
[2017-03-20:19:34:52.954] qtmir.applications: 
Application["sol"]::setSession(session=qtmir::Session(0x4ecb3290))^M
[2017-03-20:19:34:53.457] 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Icon.qml:115:5: 
QML Image: Cannot open: file:///home/stephenw/.face^M
[2017-03-20:19:34:57.992] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::MirSurface(type=normal,state=restored,size=(480,376),parentSurface=QObject(0x0))^M
[2017-03-20:19:34:58.015] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::registerView(268052752) after=1^M
[2017-03-20:19:34:58.032] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setKeymap("us")^M
[2017-03-20:19:34:58.467] toplevelwindowmodel: prependSurface appId=sol 
surface=qtmir::MirSurface(0x3c828f80), filling out placeholder. after: 
(index=0,appId=sol,surface=0x3c828f80,id=11),(index=1,appId=unity8-dash,surface=0x225db2f0,id=4)^M
[2017-03-20:19:34:58.468] toplevelwindowmodel: setFocusedWindow(0x0)^M
[2017-03-20:19:34:58.499] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:34:58.514] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setReady()^M
[2017-03-20:19:34:58.520] qtmir.applications: 
Application["sol"]::setInternalState(state=Running)^M
[2017-03-20:19:34:58.537] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, 
MirSurface[0x3c828f80,"AisleRiot"]])^M
[2017-03-20:19:34:58.664] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::requestState(restored)^M
[2017-03-20:19:34:58.673] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:19.651] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::MirSurface(type=menu,state=restored,size=(172,66),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:19.801] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::registerView(745266864) after=1^M
[2017-03-20:19:35:20.080] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:20.093] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setFocused(true)^M
[2017-03-20:19:35:20.098] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setReady()^M
[2017-03-20:19:35:20.123] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:20.126] toplevelwindowmodel: 
setFocusedWindow(Window[0x33e53dc0, id=12, 
MirSurface[0x28beec90,"AisleRiot"]])^M
[2017-03-20:19:35:20.128] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:23.549] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::setLive(false)^M
[2017-03-20:19:35:23.552] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::unregisterView(745266864) after=0 live=false^M
[2017-03-20:19:35:23.553] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::updateExposure(false)^M
[2017-03-20:19:35:23.555] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.622] toplevelwindowmodel: 
setFocusedWindow(Window[0x28c28060, id=11, MirSurface[0x3c828f80,"Klondike"]])^M
[2017-03-20:19:35:23.625] qtmir.surfaces: 
MirSurface[0x28beec90,"sol"]::~MirSurface() viewCount=0^M
[2017-03-20:19:35:23.684] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::MirSurface(type=dialog,state=restored,size=(468,353),parentSurface=qtmir::MirSurface(0x3c828f80))^M
[2017-03-20:19:35:23.711] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::registerView(744596304) after=1^M
[2017-03-20:19:35:23.893] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setFocused(false)^M
[2017-03-20:19:35:23.904] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setFocused(true)^M
[2017-03-20:19:35:23.911] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setReady()^M
[2017-03-20:19:35:23.921] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::updateExposure(true)^M
[2017-03-20:19:35:23.923] toplevelwindowmodel: 
setFocusedWindow(Window[0x2e53a140, id=13, MirSurface[0x35577d70,"About 
Aisleriot"]])^M
[2017-03-20:19:35:23.924] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::setKeymap("us")^M
[2017-03-20:19:35:26.995] qtmir.surfaces: 
MirSurface[0x35577d70,"sol"]::activate()^M
[2017-03-20:19:35:57.911] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::close()^M
[2017-03-20:19:36:00.995] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::onCloseTimedOut()^M
[2017-03-20:19:36:01.013] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::setLive(false)^M
[2017-03-20:19:36:01.018] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::unregisterView(268052752) after=0 live=false^M
[2017-03-20:19:36:01.020] qtmir.surfaces: 
MirSurface[0x3c828f80,"sol"]::updateExposure(false)^M
[2017-03-20:19:36:01.025] qtmir.surfaces: 

[Ubuntu-x-swat] [Bug 1232471] Re: Java apps crash under XMir trying to set a custom cursor

[Don-vip]

Confirmed, this is an OpenJDK bug: 
https://bugs.openjdk.java.net/browse/JDK-8173853
Fixed in 8u152 and 9.

-- 
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/1232471

Title:
  Java apps crash under XMir trying to set a custom cursor

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1232471/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1232471] Re: Java apps crash under XMir trying to set a custom cursor

[Don-vip]

** Changed in: josm
   Importance: Unknown => High

-- 
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/1232471

Title:
  Java apps crash under XMir trying to set a custom cursor

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1232471/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.16.04.1

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.16.04.1) xenial; urgency=medium

  * SECURITY UPDATE:
- CVE-2017-0318 (LP: #1659586).
  * New upstream release.
  * debian/dkms_nvidia/patches/buildfix_kernel_4.9.patch,
debian/dkms_nvidia/patches/buildfix_kernel_4.10.patch,
debian/templates/dkms_nvidia.conf.in:
- Add support for Linux 4.9 and 4.10.

 -- Alberto Milone   Wed, 08 Mar 2017
15:02:55 +0100

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1659586

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1659586/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

[Tyler Hicks]

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1659586

Title:
  NVIDIA CVE-2016-8826 and CVE-2017-0318

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1659586/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1637316] Re: Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version 4.8.0-26-generic

[Dev]

*** This bug is a duplicate of bug 1663989 ***
https://bugs.launchpad.net/bugs/1663989

Yes it does actually, thanks for letting me know. You can close this as
a duplicate then. Thanks!

** This bug has been marked a duplicate of bug 1663989
   Screen flickering

-- 
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/1637316

Title:
  Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version
  4.8.0-26-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1637316/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: vlc (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1300215

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xine-ui (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1300215

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: vdr-plugin-xineliboutput (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1300215

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-lts-xenial (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1300215

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1674455] [NEW] Keyboard input disables when laptop is rotated

[tim474]

Public bug reported:

I have Dell Inspirion 11-3168 with accelerometer. Now I don't want to
use accelerometer. But if I turn the laptop to side, keyboard input
become disabled. I can switch to console by ctrl+alt+F1 and type in
console but I can't type in GUI when laptop is on it's side.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 20 22:03:18 2017
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

-- 
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/1674455

Title:
  Keyboard input disables when laptop is rotated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674455/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1636564] Re: Segfault from libX11.so.6.3.0

[Jan Lachnitt]

Another report and some thoughts below

HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
OS: Linux Mint 18 Cinnamon x64.
State before crash: Running X session using both displays ("big desktop"), 
several applications, Vivaldi browser active.
My aim: Lock the computer.
Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi 
displayed its menu (to be displayed upon pressing Alt), tapped the touchscreen 
to get rid of the menu and thus actually lock the computer.
Course of action, the UNUSUAL part: Black screen for a few seconds, then login 
screen, old X session gone.

syslog:
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925 
requests (2925 known processed) with 0 events remaining.
Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING: t+4492,79569s: 
cinnamon-session: Fatal IO error 11 (Prostředek je dočasně nepřístupný) on X 
server :0.
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus 
can't be made
Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler: 
Kritická chyba X - Restartování :0
Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]: segfault at 
968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in 
libX11.so.6.3.0[7f61ac35c000+135000]
Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128): 
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished

Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
event.

The segfault really seems to affect multiple users, especially with 
Chromium-based browsers, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?

I don't know if syslog preserves the order of events (within a second), but if 
yes, then the segfault is just a consequence of another problem, e.g.:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1636564

Title:
  Segfault from libX11.so.6.3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1636564/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1668428] Re: gnome screen shot behaves strange on zesty unity8

[kevin gunn]

retested, overhauled description based on the latest findings (at least
I no longer see the u8 lockup now)

** Summary changed:

- gnome screen shot full lock up on zesty unity8
+ gnome screen shot behaves strange on zesty unity8

** Changed in: canonical-devices-system-image
   Status: Incomplete => New

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

** No longer affects: unity8 (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Description changed:

- Feb 27 iso build of zesty, clean u8 exploration
+ Updated Mar 20 zesty, clean u8 exploration
  
- gnome screenshot completely locks up the shell and eventually unity8 just 
restarts
+ gnome screenshot will seemingly quit, and will not capture the desired screen
  to repro:
  1) launch screenshot app from the app drawer
  2) make indications to take a screenshot ( i selected custom area to select)
  3) "take screenshot"
- result: complete lock up along with windowing oddity, frozen until unity8 res
+ result: application bail out, in the instance of "select area" case, it will 
take a screen shot in the instance of "full screen".
+ expected: get a screen shot of desired and the application should remain on 
screen.
+ 
+ I suspect this is due to screenshot's reliance on X and our use of Xmir
+ not being completely worked out in terms of what the applications
+ perception of the screen vs it's own window is.

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) => Stephen M. Webb (bregma)

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => William Hua (attente)

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
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/1668428

Title:
  gnome screen shot behaves strange on zesty unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668428/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

xrandr output in rootless session:


igor:~% ps aux | grep Xorg
igor  3779  3.2  0.0 199348 51332 tty3 S+   15:49   0:00 
/usr/lib/xorg/Xorg vt3 -displayfd 3 -auth /run/user/1000/gdm/Xauthority 
-background none -noreset -keeptty -verbose 3


igor:~% xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 518mm x 324mm
   1920x1200 59.95*+
   1920x1080 60.00  
   1680x1050 59.95  
   1600x1200 60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

lightdm works, because it starts Xorg as root for itself, which causes
monitor initialization and consequently later started rootless session
work fine.

-- 
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/1672033

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

I don't have hybrid graphics. It's a normal desktop.

Yes, lightdm is working with KMS enabled and it is possible to log in
into gnome-shell Xorg session.

But lightdm is started as root:
root 10867  0.0  0.0 361724  6620 ?SLsl 15:41   0:00 
/usr/sbin/lightdm

-- 
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/1672033

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

[kevin gunn]

if so many caveats, then lets not target u8c-1

** Changed in: canonical-devices-system-image
Milestone: u8c-1 => u8c-2

-- 
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/1118903

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

** Description changed:

  xserver 1.19 has been out for quite some time now. Debian Stretch will
  release with it, and xmir has been recently ported so we can push 1.19
  to zesty now. It's currently being staged on a ppa:
  
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
  
  The main features of this release are:
  - PRIME synchronization support, should reduce tearing on hybrid setups
  - GLAMOR (2D accel over OpenGL) improvements
  - threaded input
  
  This bugreport is also for gathering testing feedback.
  
  Tested to be working fine on:
  - Intel Kabylake
  - Intel Broadwell
  - Intel+NVIDIA hybrid (Skylake + 930MX, with OSS and blob drivers)
  - Intel+NVIDIA hybrid (Haswell + NVIDIA GK107M [GeForce GT 755M])
  - Intel+NVIDIA hybrid (Ivybridge + NVIDIA GK107M [GeForce GT 660M])
  - Radeon SI (radeon & amdgpu drivers)
+ - qemu (QXL)

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

-libinput has been the default since 16.10 where it replaced -evdev
(-input-all pulls -libinput), so I don't consider this a blocker, since
it doesn't seem to be a widespread issue (I can't reproduce it with a
mouse either). Feel free to file a bug against -libinput, upstream too
if you can.

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2609

-- 
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/1393578

Title:
  Subpixel order not included in Mir display information

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1589447] Re: Xdummy cannot be used in Xenial

[Bharat Kunwar]

I have documented how I resolved this issue on my blog: 
http://brtknr.com/2017/03/15/permission-issues-with-xpra-on-ubuntu-16-04-when-tunnelling-through-SSH/

Turns out that the version of xpra (0.15.x) provided with Ubuntu 16.04
is not supported anymore and updating to 2.0.x resolved the issue.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-dummy in Ubuntu.
https://bugs.launchpad.net/bugs/1589447

Title:
  Xdummy cannot be used in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-dummy/+bug/1589447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[dino99]

This scrolling issue has been met also outside the ubuntu world:
https://ubuntuforums.org/showthread.php?t=2355713=13622468#post13622468

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[dino99]

Made some tests, with both xserver 18 & with/without input-libinput 23 ;
and xserver 19 with/without input-libinput 25

To clarify 'mouse': it's a generic usb mouse, no touchpad at all. Tests
made on two different ZZ partitions on the same desktop.

Test xserver 18
- note that comment #26 above is a bit confusing: i was talking about the 
partition using xserver 18
- xserver 18 without input-libinput 23: works well (as previouly said (#23)
- xserver 18 + input-libinput 23: no problem to select a range of calc's cells; 
but discovered an other 'scrolling' issue when trying to set the 'sort 
criteria' for keys: scrolling does not work.
That is when using Calc sorting; testing 'scrolling' inside 'nautilus' works 
well (confusing).
So i purge input-libinput hoping to get back a normal calc's sorting scrolling; 
that fails; closing calc / restating gnome-shell session / even logout/in the 
session does not set scrolling back (confusion again); Check System settings 
mouse options /gnome-tweak-tool but settings are as usual.

- xserver 19 + input-libinput 25 : problem initialy reported
- xserver 19 without input-libinput 25 (23 not installable due to abi, so cant 
test that case): selecting a cells range can be done as expected, scrolling for 
sorting also works !!!

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1637652] Re: stucked in a login loop

[Sébastien Lamy]

On ubuntu 16.04-2, This bug doesn't affect me with nvidia 304.134, but I had 
other problems with this 304.134 driver, and I tried to use nvidia 304.135 from 
the ppa:graphics-drivers/ppa.
With the 304.135 installed, I got stuck in the login loop.
Same thing when trying the 331 drivers

-- 
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/1637652

Title:
  stucked in a login loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637652/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

fwiw, I can't repro that bug on a touchpad using -libinput (synaptics
doesn't work right with it)

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1671799] Re: FFe: xserver 1.19.3

[Timo Aaltonen]

By mouse do you mean touchpad or an actual mouse? Touchpads use
-synaptics which got bumped to 1.9.0. Test a real mouse too if not
already.

-- 
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/1671799

Title:
  FFe: xserver 1.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Tim]

Also does lightdm work with KMS enabled for logging into gnome-shell
session?

-- 
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/1672033

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Tim]

what hardware are you running? I recall  some hybrid laptops fail to
advertise a "primary" display. what is the output of "xrandr -q" in a
working root-less X session?

-- 
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/1672033

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away

[Chris Halse Rogers]

Ah, OK. We've been arguing with different assumptions.

Symptom: Firefox's menus don't work
Bug: XMir's focus behaviour differs from a spec-compliant X11 window manager.

One solution here, which is what I've been suggesting, is to implement
spec-compliant focus behaviour in XMir.

But you're correct that simply making the popups non-focusable Mir
surfaces will make XMir behave more like a spec-compliant X11 window
manager, should make it behave *enough* like a spec-compliant WM to
resolve the symptom and may well be simpler to implement. This could be
an expedient solution for the short term.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846

Title:
  Xmir -rootless: Firefox menus pop up then close right away

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625846/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp