[Ubuntu-x-swat] [Bug 1723279] Re: xwayland doesn't let root access the display, even via sudo or pkexec

2017-10-12 Thread Jean-Baptiste Lallement 
** Tags removed: wayland-session
** Tags added: wayland

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

Title:
  xwayland doesn't let root access the display, even via sudo or pkexec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1723279/+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 1665802] Re: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard

2017-10-12 Thread Daniel van Vugt 
P.S. client-side vsync isn't just a good idea that improves performance
on non-buggy drivers [2], but apparently also the norm. It is the design
used by gtk and clutter too. I had no idea it was so common till
recently.

If you disable client-side vsync in Mir then you take latency backwards
[1], and take rendering performance (on mature drivers) backwards [2]

[1] 
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive
[2] https://bugs.launchpad.net/mir/+bug/1388490

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

Title:
  [regression] mir_demo_client_eglplasma results in 100% cpu and hardly
  any updates in dragonboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1665802/+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 1665802] Re: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard

2017-10-12 Thread Daniel van Vugt 
Alberto:

I think what I was recommending in that last comment is to just not run
eglplasma on dragaonboard. It's a poor demo if the best it can get is
15FPS (you just never noticed it was so low). Change your demos to use
egltriangle (fullscreen to get bypass) and you won't hit this bug any
more, plus you should get 60 FPS.

Long term, you should push for a driver fix (bug 1211700) to resolve it.

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

Title:
  [regression] mir_demo_client_eglplasma results in 100% cpu and hardly
  any updates in dragonboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1665802/+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 1708874] Re: Touchpad stops working after a few seconds

2017-10-12 Thread Walker Gusmão 
/proc/bus/input/devices entry:

I: Bus=0018 Vendor=06cb Product=8251 Version=0100
N: Name="SYNA2B33:00 06CB:8251"
P: Phys=i2c-SYNA2B33:00
S: 
Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-4/i2c-SYNA2B33:00/0018:06CB:8251.0001/input/input12
U: Uniq=
H: Handlers=mouse0 event12 
B: PROP=1
B: EV=b
B: KEY=e520 3 0 0 0 0
B: ABS=6738103

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

Title:
  Touchpad stops working after a few seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1708874/+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 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
Used synaptic to "remove completely" all zulucrypt packages. Installed
the 4 .deb packages in order again. Same errors.

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
OK. Broke into synaptic with
https://ubuntuforums.org/showthread.php?t=2367294.

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
figured out xhost +local was not the command.

after running xhost +MyHostname

sudo synaptic
[sudo] password for tom:
No protocol specified
Unable to init server: Could not connect: Connection refused

(synaptic:5993): Gtk-WARNING **: cannot open display: :0

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1682978] Re: Random Screen Rotation

2017-10-12 Thread James Jones 
Today I grabbed the daily build of 17.10 and booted into it from a USB
drive. It still rotates--but at times I can't predict, the screen will
blank out and then come back rotated. (Should I create a new bug for
17.10?) I should mention that this happens on my laptop, an HP Pavilion
with AMD graphics. On my desktop, which has an Nvidia 960, it doesn't.

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

Title:
  Random Screen Rotation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+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 1723260] Re: Xorg crashed with SIGABRT

2017-10-12 Thread Apport retracing service 
*** This bug is a duplicate of bug 1557346 ***
https://bugs.launchpad.net/bugs/1557346

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1557346, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969266/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969269/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969280/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969282/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969283/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969284/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1723260/+attachment/4969285/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1557346
   Xorg crashed with SIGABRT in OsAbort()

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1723260/+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 1723260] [NEW] Xorg crashed with SIGABRT

2017-10-12 Thread Till Kamppeter 
*** This bug is a duplicate of bug 1557346 ***
https://bugs.launchpad.net/bugs/1557346

Public bug reported:

Probably crashed when I observed bug 1722988 happening to me.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Oct 12 15:36:51 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2218]
InstallationDate: Installed on 2015-04-30 (896 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20A8X50300
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=ff9fee12-fd92-4cfd-88bf-c8f57ffba318 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ()
 ()
 ()
 xf86VTEnter ()
 WakeupHandler ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 09/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GRET40WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20A8X50300
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8X50300:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8X50300:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X1 Carbon 2nd
dmi.product.name: 20A8X50300
dmi.product.version: ThinkPad X1 Carbon 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Oct 12 15:44:48 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.4-1ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-crash artful ubuntu

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

Title:
  Xorg crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1723260/+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 1720482] Re: Demote xterm to universe

2017-10-12 Thread Launchpad Bug Tracker 
This bug was fixed in the package xorg - 1:7.7+19ubuntu3

---
xorg (1:7.7+19ubuntu3) artful; urgency=medium

  * Add alternate dependency on gnome-terminal (LP: #1720482)

 -- Jeremy Bicha   Thu, 12 Oct 2017 10:25:30 -0400

** Changed in: xorg (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Demote xterm to universe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tk8.6/+bug/1720482/+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

Re: [Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
1. Synaptic doesn't run in Wayland (17.10 is wayland).

2. sudo xhost +local
no protocol specified
xhost: unable to open display ':0'

xhost +local
xhost: bad hostname 'local'

Yes, I have those packages installed, but they're the ones you told me to
install in the binary, which i installed per the README, in order.

What should I do step by step please? Should I look for these extra
packages? Should I try instead to remove packages? I'm not clear.

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1720482] Re: Demote xterm to universe

2017-10-12 Thread Jeremy Bicha 
** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg (Ubuntu)
   Status: New => Fix Committed

** Also affects: xinit (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xinit (Ubuntu)
   Status: New => Fix Released

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

Title:
  Demote xterm to universe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tk8.6/+bug/1720482/+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 1723250] [NEW] kworker blocked: nv50_disp_atomic_commit_work

2017-10-12 Thread David R. Hedges 
Public bug reported:

There's a moderate chance this is a duplicate of #1723245, but the lead-
up to the hang was different: I noticed some visual artifacting (perhaps
isolated to my Chromium window, but I don't remember for sure). I could
still move the mouse, and tried closing the current tab. Shortly
thereafter, the UI entirely stopped responding, but SSH was fine. The
syslog contained recent messages like this:

 [535575.990974] nouveau :01:00.0: gr: TRAP ch 5 [00ff534000 compiz[3891]]
 [535575.990985] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global  
[] warp 3f0009 [ILLEGAL_INSTR_ENCODING]
 [535575.991008] nouveau :01:00.0: gr: TRAP ch 5 [00ff534000 compiz[3891]]
 [535575.991016] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 2000d [OOR_REG]
 [535575.991028] nouveau :01:00.0: gr: TRAP ch 5 [00ff534000 compiz[3891]]
...
 [535575.992504] nouveau :01:00.0: gr: TRAP ch 5 [00ff534000 compiz[3891]]
 [535575.992511] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 2000d [OOR_REG]
 [535575.992522] nouveau :01:00.0: gr: TRAP ch 5 [00ff534000 compiz[3891]]
 [535575.992530] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3000d [OOR_REG]
 [535671.523894] nouveau :01:00.0: fifo: read fault at 0002645000 engine 00 
[GR] client 08 [GPC0/PE_2] reason 02 [PTE] on channel 7 [00ff3af000 
chromium-browse[9166]]
 [535671.523900] nouveau :01:00.0: fifo: gr engine fault on channel 7, 
recovering...
 [535692.272677] [drm:drm_atomic_helper_swap_state [drm_kms_helper]] *ERROR* 
[CRTC:37:head-0] hw_done timed out
 [535702.512751] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] hw_done timed out
 [535712.752833] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] flip_done timed out
 [535818.481524] [drm:drm_atomic_helper_swap_state [drm_kms_helper]] *ERROR* 
[CRTC:37:head-0] hw_done timed out
 [535828.721587] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] hw_done timed out
 [535838.961655] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] flip_done timed out
 [535849.201726] [drm:drm_atomic_helper_swap_state [drm_kms_helper]] *ERROR* 
[CRTC:37:head-0] hw_done timed out
 [535859.441805] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] hw_done timed out
 [535869.681862] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] flip_done timed out
 [535879.921931] [drm:drm_atomic_helper_swap_state [drm_kms_helper]] *ERROR* 
[CRTC:37:head-0] hw_done timed out
 [535890.162005] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:37:head-0] hw_done timed out
 [535895.282173] INFO: task kworker/u24:8:30368 blocked for more than 120 
seconds.
 [535895.282178]   Not tainted 4.10.0-35-generic #39-Ubuntu
 [535895.282179] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
 [535895.282181] kworker/u24:8   D0 30368  2 0x
 [535895.28] Workqueue: events_unbound nv50_disp_atomic_commit_work 
[nouveau]
 [535895.282223] Call Trace:
 [535895.282229]  __schedule+0x233/0x6f0
 [535895.282251]  ? nvkm_ioctl_ntfy_get+0x67/0xb0 [nouveau]
 [535895.282322]  schedule+0x36/0x80
 [535895.282324]  schedule_timeout+0x22a/0x3f0
 [535895.282353]  ? nvkm_client_ioctl+0x12/0x20 [nouveau]
 [535895.282373]  ? nvif_object_ioctl+0x41/0x50 [nouveau]
 [535895.282405]  ? nouveau_bo_rd32+0x2a/0x30 [nouveau]
 [535895.282432]  ? nv84_fence_read+0x2e/0x30 [nouveau]
 [535895.282434]  dma_fence_default_wait+0x1c8/0x250
 [535895.282435]  ? dma_fence_free+0x20/0x20
 [535895.282436]  dma_fence_wait_timeout+0x39/0xf0
 [535895.282446]  drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
 [535895.282472]  nv50_disp_atomic_commit_tail+0x55/0x3820 [nouveau]
 [535895.282475]  ? __switch_to+0x23c/0x520
 [535895.282502]  nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
 [535895.282504]  process_one_work+0x1fc/0x4b0
 [535895.282506]  worker_thread+0x4b/0x500
 [535895.282508]  kthread+0x109/0x140
 [535895.282509]  ? process_one_work+0x4b0/0x4b0
 [535895.282511]  ? kthread_create_on_node+0x60/0x60
 [535895.282513]  ret_from_fork+0x2c/0x40

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Oct 10 16:40:51 2017
DistUpgraded: 2017-06-09 12:39:15,077 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches

[Ubuntu-x-swat] [Bug 1723245] [NEW] kworker blocked: nv50_disp_atomic_commit_work

2017-10-12 Thread David R. Hedges 
Public bug reported:

I returned to my computer to find the lock screen up, but no keyboard or
mouse response. I saw the clock (upper right corner) hadn't updated in
several minutes.

I checked the syslog (remotely) and discovered some nouveau issues like
this:

 [165486.931750] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
 [165486.931757] nouveau :01:00.0: fifo: gr engine fault on channel 6, 
recovering...
 [165486.932317] nouveau :01:00.0: fifo: write fault at 001d0a engine 
00 [GR] client 0f [GPC0/PROP_0] reason 02 [PTE] on channel 5 [00ff534000 
compiz[3777]]
 [165486.932320] nouveau :01:00.0: fifo: gr engine fault on channel 5, 
recovering...
 [165675.247319] INFO: task kworker/u24:9:12665 blocked for more than 120 
seconds.
 [165675.247323]   Not tainted 4.10.0-37-generic #41-Ubuntu
 [165675.247324] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
 [165675.247326] kworker/u24:9   D0 12665  2 0x
 [165675.247368] Workqueue: events_unbound nv50_disp_atomic_commit_work 
[nouveau]
 [165675.247369] Call Trace:
 [165675.247374]  __schedule+0x233/0x6f0
 [165675.247396]  ? nvkm_ioctl_ntfy_get+0x67/0xb0 [nouveau]
 [165675.247397]  schedule+0x36/0x80
 [165675.247399]  schedule_timeout+0x22a/0x3f0
 [165675.247427]  ? nvkm_client_ioctl+0x12/0x20 [nouveau]
 [165675.247447]  ? nvif_object_ioctl+0x41/0x50 [nouveau]
 [165675.247474]  ? nouveau_bo_rd32+0x2a/0x30 [nouveau]
 [165675.247501]  ? nv84_fence_read+0x2e/0x30 [nouveau]
 [165675.247503]  dma_fence_default_wait+0x1c8/0x250
 [165675.247504]  ? dma_fence_free+0x20/0x20
 [165675.247506]  dma_fence_wait_timeout+0x39/0xf0
 [165675.247514]  drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
 [165675.247541]  nv50_disp_atomic_commit_tail+0x55/0x3820 [nouveau]
 [165675.247543]  ? __switch_to+0x23c/0x520
 [165675.247569]  nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
 [165675.247572]  process_one_work+0x1fc/0x4b0
 [165675.247573]  worker_thread+0x4b/0x500
 [165675.247575]  kthread+0x109/0x140
 [165675.247576]  ? process_one_work+0x4b0/0x4b0
 [165675.247578]  ? kthread_create_on_node+0x60/0x60
 [165675.247580]  ret_from_fork+0x2c/0x40

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Oct 12 15:01:21 2017
DistUpgraded: 2017-06-09 12:39:15,077 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 770] [1458:3606]
InstallationDate: Installed on 2016-10-24 (352 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: Upgraded to zesty on 2017-06-09 (125 days ago)
dmi.bios.date: 05/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4701:bd05/06/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Oct 10 16:44:45 2017
xserver.configfile:

[Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread mhogo mchungu 
I still use synaptic to manage packages because of its simplicity and zulucrypt 
packages you most likely have installed are those highlighted in the below 
image:

https://imgur.com/a/jFezM

I also suggest you use synaptic because doing stuff on the terminal is
not very user friendly.

1. Install synaptic with command: sudo apt-get install synaptic
2. Temporarily allow GUI programs to run privileged with command: xhost +local:
3. Run synaptic with command: sudo synaptic
4. Search for package "zuluCrypt"
5. Remove all installed packages you see. Installed packages will be green 
highlighted.

In any of the above commands,if you get a "could not acquire lock
error", keep trying to run the command on 2 seconds interval until it
succeeds.

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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

Re: [Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
dpkg -l zulucrypt*

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
iU  zulucrypt-cli  5.2.0-1  amd64tool for encrypting volumes
iU  zulucrypt-gui  5.2.0-1  amd64graphical front end for
zulucrypt

On Thu, Oct 12, 2017 at 1:05 PM, Tom Mercer  wrote:

> Before installing the binary, I ran sudo apt remove zuluCrypt-cli
> zuluCrypt-gui, then autoremoved. How would you advise to remove all
> zuluCrypt packages?
>
>

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1722708] Re: Crash when setting laptop display resolution

2017-10-12 Thread Ville Skyttä 
Wow, this is fixed after all now for me, somewhere between xwayland
and/or xserver* 2:1.19.3-1ubuntu7 -> 2:1.19.4-1ubuntu2.

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Crash when setting laptop display resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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

Re: [Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
dpkg -l *zulucrypt*

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
iU  libzulucrypt-d 5.2.0-1  amd64development files for
libzulucryp
in  libzulucrypt-eamd64(no description available)
ii  libzulucrypt1: 5.2.0-1  amd64shared libraries for
cryptsetup a
in  libzulucrypt1.amd64(no description available)
in  libzulucryptplamd64(no description available)
iU  zulucrypt-cli  5.2.0-1  amd64tool for encrypting volumes
iU  zulucrypt-gui  5.2.0-1  amd64graphical front end for
zulucrypt


On Thu, Oct 12, 2017 at 1:07 PM, Tom Mercer  wrote:

> dpkg -l zulucrypt*
>
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/
> trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
> +++-==---===
> ==
> iU  zulucrypt-cli  5.2.0-1  amd64tool for encrypting volumes
> iU  zulucrypt-gui  5.2.0-1  amd64graphical front end for
> zulucrypt
>
> On Thu, Oct 12, 2017 at 1:05 PM, Tom Mercer  wrote:
>
>> Before installing the binary, I ran sudo apt remove zuluCrypt-cli
>> zuluCrypt-gui, then autoremoved. How would you advise to remove all
>> zuluCrypt packages?
>>
>>
>

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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

Re: [Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
Before installing the binary, I ran sudo apt remove zuluCrypt-cli
zuluCrypt-gui, then autoremoved. How would you advise to remove all
zuluCrypt packages?

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread mhogo mchungu 
first,remove ALL zuluCrypt packages you have installed and then install the 
ones i provide, you are getting errors because you attempting to mix version 
5.0.2 from ubuntu and 5.2.0 from me.

Make sure all those with versions 5.0.2 are not in your system before
you continue.

The version i provide works without sudo.

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1723075] Re: System freeze after docking and display configuration change

2017-10-12 Thread Michael Thayer 
Just got this again with 4.13.0-15-generic after suspending and resuming
the laptop.  No docking station or screen reconfiguration.

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

Title:
  System freeze after docking and display configuration change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+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

Re: [Ubuntu-x-swat] [Bug 1722615] Re: zuluCrypt doesn't launch

2017-10-12 Thread tom 
So zuluCrypt-cli -o -d /home/USERNAME/filename fails, but
sudo zuluCrypt-cli -o -d /home/USERNAME/filename works, with either the old
zC or the new binary you gave me.

If I run through the GUI from the binary, it looks MUCH nicer than it has.
Finally modern look and scaling and windows and buttons. However, it fails
to load file, with error 255.

I'm prompted to "update" a bunch of things in software updater / sudo apt
upgrade, but look like regressions.

You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libzulucrypt-dev : Depends: libzulucrypt1.2.0 (= 5.2.0-1) but it is not
installed
 zulucrypt-cli : Depends: libzulucrypt-exe1.2.0 (>= 5.0.2) but it is not
installed
 Depends: libzulucrypt1.2.0 (>= 5.2.0) but it is not
installed
 Depends: libzulucryptpluginmanager1.0.0 (>= 5.0.2) but it
is not installed
 zulucrypt-gui : Depends: libzulucryptpluginmanager1.0.0 (>= 5.0.2) but it
is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or
specify a solution).


Should I "update" these dependencies?

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

Title:
  zuluCrypt doesn't launch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722615/+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 1722708] Re: Crash when setting laptop display resolution

2017-10-12 Thread Ville Skyttä 
** Changed in: xorg (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Crash when setting laptop display resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1722708] Re: Crash when setting laptop display resolution

2017-10-12 Thread Florin Ivan 
is not fixed.
I changed the status my mistake and can't undo it.

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

Title:
  Crash when setting laptop display resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1722708] Re: Crash when setting laptop display resolution

2017-10-12 Thread Florin Ivan 
** Changed in: xorg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Crash when setting laptop display resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1722708] Re: Crash when setting laptop display resolution

2017-10-12 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Crash when setting laptop display resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1722897] Re: Unexpected behavior with Wayland desktop

2017-10-12 Thread Timo Aaltonen 
I guess gnome-shell would be a more appropriate target

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Unexpected behavior with Wayland desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722897/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-10-12 Thread Jeremy Bicha 
** No longer affects: wayland (Ubuntu)

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1713313/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-10-12 Thread Phillip Susi 
The wayland package just needs to change its absurd default security
policy back to the one that X has used.


** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1713313/+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 1059947] Re: xvfb-run munges stdout and stderr together

2017-10-12 Thread Timo Aaltonen 
** Changed in: xorg-server (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  xvfb-run munges stdout and stderr together

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1059947/+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 1723075] [NEW] System freeze after docking and display configuration change

2017-10-12 Thread Michael Thayer 
Public bug reported:

I have been having regular system freezes after switching from using my
laptop stand-alone to waking it up on a docking station with an external
monitor.  I have seen this using two identical docking station plus
monitor combinations.  I am still trying to find a pattern.  I often
find the laptop going to sleep again immediately after being woken up.
When it freezes, the screen saver is visible on the internal display and
the external monitor is (I think) enabled but blank.  I saw this with
4.13.0-13-generic, and have not yet had the chance to test it with
4.13.0-15-generic.  I have also not had the chance yet to try to ssh in.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 11:52:51 2017
DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 
'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation 
script returned error exit status 1'
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
InstallationDate: Installed on 2016-05-31 (498 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude E6420
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A21
dmi.board.name: 0K0DNP
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful freeze ubuntu wayland-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/1723075

Title:
  System freeze after docking and display configuration change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+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 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding

2017-10-12 Thread Alex Tu 
with AOC monitor, it issued an unexpected acpi event after external
monitor be disabled, that caused mode switching.

 u@u-Vostro-7570:~$ sudo acpi_listen

 # now disable external screen by $DISPLAY=:0 xrandr --output HDMI-0 --off
 jack/lineout LINEOUT unplug
 jack/videoout VIDEOOUT unplug

 # wait for about 15 secs, this acpi event somehow be issued.
 video/switchmode VMOD 0080 
 jack/lineout LINEOUT plug
 jack/videoout VIDEOOUT plug

But, this issue not happens to Dell monitor, and this proposed package
passed both with Dell monitor ST2320L and P2415Qb. So, the patches helps
actually.

** Tags removed: verification-failed-xenial
** Tags added: verification-done-xenial

** Tags removed: verification-needed-xenial

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

Title:
  Fix shrinking behavior in rrCheckPixmapBounding

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1715586/+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 1722897] Re: Unexpected behavior with Wayland desktop

2017-10-12 Thread vmware-gos-Yuhua 
This is urgent issue because ubuntu will GA on Oct/19/17.

Is it possible to be get fixed in GA ?

thanks very much!

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

Title:
  Unexpected behavior with Wayland desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+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