[Ubuntu-x-swat] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

2018-11-06 Thread Daniel van Vugt
Also, this is a SIGSEGV...

 OsSigHandler (signo=11

** Summary changed:

- Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() from 
_mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
+ Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from 
_mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754693/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-

2018-11-06 Thread Timo Aaltonen
** Changed in: libglvnd (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: libglvnd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+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 1798597] Re: Backport packages for 18.04.2 HWE stack

2018-11-06 Thread Timo Aaltonen
** Changed in: xorg-server (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.2 HWE stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1777994] Re: the header xcb/xinput.h is missing

2018-11-06 Thread Timo Aaltonen
I don't need this in bionic, so dropping from my TODO

** Changed in: libxcb (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: libxcb (Ubuntu Bionic)
 Assignee: Timo Aaltonen (tjaalton) => (unassigned)

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

Title:
  the header xcb/xinput.h is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1770271] Re: VegaM support

2018-11-06 Thread Timo Aaltonen
I think we'll just fix this in bionic via the HWE stack update. Backport
to xenial would basically mean updating stock bionic kernel/mesa and
then backport those to xenial. A big patchset to the kernel is unlikely
to get approved..

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  VegaM support

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1770271/+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 1500473] Re: nvidia-persistenced: Failed to query NVIDIA devices.

2018-11-06 Thread Aravind R
** Tags added: bonic

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

Title:
  nvidia-persistenced: Failed to query NVIDIA devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1500473/+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 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

2018-11-06 Thread knb
Here : https://bugs.freedesktop.org/show_bug.cgi?id=96312 some people
said this is caused by a "slow compositor" . In my case, it seems to me,
these log entries are probably caused by  a Xorg process running with
100% cpu blocking the UI for ~ 1 minute. This happens after animations
played (e.g. progressbars), window resizing, scrolling, when I have many
GUI apps open. I am still investigating.

My system: nvidia driver, 2 old GPUs, 18.04 with gdm3+Xorg

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

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1588009/+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 1801898] [NEW] Only one of two external (displayport) displays is working without hotplug

2018-11-06 Thread Andreas Vinsander
Public bug reported:

After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in my one of my 
two external displays will not be activated without hotplugging the other 
external display.
The display settings app shows the second display as inactive, and when trying 
to activate the settings app states that some hardware limitation stops it from 
being possible to apply the change.
The laptop lid is closed, the internal laptop display is not active.

Hotplugging the other external display solves the problem - after
hotplug both external displays are active. This makes the bug annoying
but workaroundable.

I am not sure if this bug belongs to the Xorg package or the linux
package.

Hardware:
Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two 
external displays connected through displayport (via docking station).

$ sudo lspci -v
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f000 (64-bit, non-prefetchable) [size=4M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at 6000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu8
  Candidate: 1:7.7+19ubuntu8
  Version table:
 *** 1:7.7+19ubuntu8 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy linux-image-4.18.0-10-generic
linux-image-4.18.0-10-generic:
  Installed: 4.18.0-10.11
  Candidate: 4.18.0-10.11
  Version table:
 *** 4.18.0-10.11 500
500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

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

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801898/+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 1801898] Re: Only one of two external (displayport) displays is working without hotplug

2018-11-06 Thread Andreas Vinsander
I am not using wayland.

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801898/+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 1798597] Re: Backport packages for 18.04.2 HWE stack

2018-11-06 Thread Sebastien Bacher
** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: llvm-toolchain-7 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.2 HWE stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-06 Thread Sebastien Bacher
Thanks for the data Mario, seems like it's not the backend then but that there 
is a bug in the key handling. Unsure we can describe it as "regression" though, 
the feature was not working at all, now it's half working.
Or was it something that is currently working on cosmic and which isn't now?

The log doesn't have informations on gnome-settings-daemon though which
would be useful to have (but unsure what's the easiest way to put in
debug mode, maybe restart it manually with --debug?)

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

Title:
  KEY_RFKILL is not passed to userspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-06 Thread Andrew Lendrum
@Alberto

This is my first time on launchpad, so please forgive any noob errors.

I followed the instructions to the letter:
I enabled bionic-proposed with: sudo add-apt-repository "deb 
http://archive.ubuntu.com/ubuntu/ $(lsb_release -sc)-proposed restricted main 
universe"
I created /etc/apt/preferences.d/proposed-updates with the specified content
I updated.
Then when I tried to install the packages I saw:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Release 'bionic-proposed' for 'nvidia-driver-390' was not found
E: Release 'bionic-proposed' for 'gdm3' was not found
E: Release 'bionic-proposed' for 'nvidia-settings' was not found
E: Release 'bionic-proposed' for 'libnvidia-gl-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-compute-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-decode-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-encode-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-ifr1-390' was not found
E: Release 'bionic-proposed' for 'libnvidia-fbc1-390' was not found


Am I missing something?

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

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1801976] [NEW] Display does not work correctly

2018-11-06 Thread HeinzDiedrichsen
Public bug reported:

Initially everything was fine. Then came an update and now the display
is milky and too large. I dont know what to do. What would be the proper
BIOS Setting or how can the issue be settled?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Tue Nov  6 18:07:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d1]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 620M/630M/635M/640M 
LE] [144d:c0d1]
InstallationDate: Installed on 2018-11-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=e703b236-f073-42b6-bcef-3f6eca97246c ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABI.026.141024.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550P7C-T0ADE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABI.026.141024.dg:bd10/24/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP09ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550P7C-T0ADE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG SENS
dmi.product.name: 550P5C/550P7C
dmi.product.version: P09ABI
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
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 bionic 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/1801976

Title:
  Display does not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801976/+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 1801747] Re: External display not recognized, internal one goes to black

2018-11-06 Thread Dash
Ubuntu 18.10 does have the same problem, Ubuntu 16.04.2 has *NO*
problem. From where could I get an 4.4 kernel for 18.04 for testing
purpose ?

Other infos: when I check in systems, it show me 3 display despite the
fact that only 2 are connected:

1. internal display
2. unknown display with resolution 1024 x 768 (4:3) 800 x 600 (4:3) 848 x 480 
(16:9) !
3. external display with correct informations (Brand, model, )

I also discover that starting the laptop with the display connected,
shows me the splash image on both displays as it should. Problem arise
on greeting image. From here I see "No input signal" and the external
display goes black.

Daniel

PS: perhaps bug 1723025? could be identical but from my side, I can
start with or without external display, it's only when I use the fn
switch key that problem arise.

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

Title:
  External display not recognized, internal one goes to black

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-06 Thread Mario Vukelic
@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a
regression with xkb-data 2.23.1-1ubuntu1.18.10.1.

On this machine, the airplane mode key worked perfectly out-of-the-box
(i.e., the key enabled AND disabled the airplane mode) with the
development version of  Cosmic, using xkb-data 2.23. See my comment #13
further up in this bug.

Here's the debug output for gnome-settings-daemon:

[*** Airplane mode is off, Wifi and BT are on ***]

/usr/lib/gnome-settings-daemon/gsd-rfkill -v
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'WLAN' (idx=1): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 
'BLUETOOTH' (idx=11): soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.185: Registered client at 
path /org/gnome/SessionManager/Client29
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.187: Opened rfkill-input 
inhibitor.

[*** Here I am pressing the airplane mode key to enable Airplane mode >
Wifi/BT goes off ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.352: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.353: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing the airplane mode key again to DISable Airplane
mode > Wifi/BT should go back on. This fails and the airplane mode re-
engages immediately as described ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed Bluetooth rfkill 
with ID 11
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed Bluetooth rfkill 
with ID 11

[*** Here I am pressing DISabling Airplane mode from the Gnome panel
menu > Wifi/BT goes back on. This works ***]

(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 1 type 
1 (WLAN) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 11 
type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed rfkill with ID 1
(gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed Bluetooth rfkill 
with ID 11

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

Title:
  KEY_RFKILL is not passed to userspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-06 Thread Mario Vukelic
To be clear, the above debugging output is with xkb-data
2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of
airplane mode by the dedicated key being broken

$ aptitude show xkb-data
Package: xkb-data
Version: 2.23.1-1ubuntu1.18.10.1
State: installed

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

Title:
  KEY_RFKILL is not passed to userspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-06 Thread Andrew Lendrum
UPDATE: I found the packages in bionic-updates.

After setting prime-select nvidia and logging out, I got the attached
/var/log/gpu-manager.log.

It says that nvidia is not loaded, and my laptop still runs hot.

When I set prime-select intel, log out, and back in, nvidia is still not
loaded (according to the log) and my laptop still runs hot.

Any suggestings?

** Attachment added: "/var/log/gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5209748/+files/gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1801410] Re: Icons.keep.flashing

2018-11-06 Thread Seth Arnold
Ow, this looks painful:

[  OK  ] Started Disk Manager.
 Starting Firmware update daemon...
[   ***] (2 of 3) A start job is running for 
Firmware update daemon (2s / 1min 30s)
[  *** ] (3 of 3) A start job is running for 
Daily apt download activities (45s / no limit)
[  OK  ] Started Firmware update daemon.
[ ***  ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 6s / no limit)
[***   ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 7s / no limit)
[**] (2 of 2) A start job is running for Daily 
apt download activities (51s / no limit)
[* ] (2 of 2) A start job is running for Daily apt 
download activities (51s / no limit)
[**] (2 of 2) A start job is running for Daily 
apt download activities (52s / no limit)
[***   ] (1 of 2) A start job is running for 
Hold until boot process finishes up (1min 9s / no limit)

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

Title:
  Icons.keep.flashing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801410/+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 1801898] Re: Only one of two external (displayport) displays is working without hotplug

2018-11-06 Thread Daniel van Vugt
Please run this command to send us more information about the machine:

  apport-collect 1801898

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Tags added: cosmic multimonitor

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

Title:
  Only one of two external (displayport) displays is working without
  hotplug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801898/+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 1801747] Re: External display not recognized, internal one goes to black

2018-11-06 Thread Daniel van Vugt
** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

** Changed in: linux (Ubuntu)
   Status: Incomplete => New

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

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

Title:
  External display not recognized, internal one goes to black

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1801976] Re: Display does not work correctly

2018-11-06 Thread Daniel van Vugt
That sounds unusual. Can you please attach a photo of the display when
it is "milky and too large" ?

** Tags added: hybrid nouveau

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

Title:
  Display does not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801976/+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 1801225] Re: cmake files are misplaced

2018-11-06 Thread Seth Arnold
Sylvestre, you already closed the corresponding Debian bug report with
fixes :)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862328#42

llvm-toolchain-5.0 (1:5.0.2-2) unstable; urgency=medium
llvm-toolchain-6.0 (1:6.0.1~+rc1-1~exp2) experimental; urgency=medium

https://launchpad.net/debian/+source/llvm-toolchain-5.0/1:5.0.2-2
https://launchpad.net/debian/+source/llvm-toolchain-6.0/1:6.0.1~+rc1-1~exp2

Now we "just" need someone who knows cmake / llvm well enough to help
out with an SRU. :)

Thanks

** Bug watch added: Debian Bug tracker #862328
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862328

** Also affects: llvm-toolchain-5.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cmake files are misplaced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-5.0/+bug/1801225/+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 1801976] Re: Display does not work correctly

2018-11-06 Thread Daniel van Vugt
Also, please run these commands and send the output:

  sudo apt install edid-decode
  for e in /sys/class/drm/*/edid ; do edid-decode $e ; done


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Display does not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801976/+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 1801747] Status changed to Confirmed

2018-11-06 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   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/1801747

Title:
  External display not recognized, internal one goes to black

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1801976] Re: Display does not work correctly

2018-11-06 Thread Daniel van Vugt
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Display does not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801976/+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 1724901] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

2018-11-06 Thread Ramesh
This bug reports says "Launching 17.10" so I guess its present in ubuntu
17.10 but my system is Ubuntu 16.04.5 and I have the same problem.

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

Title:
  Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724901/+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 1801410] Re: Icons.keep.flashing

2018-11-06 Thread Daniel van Vugt
Can you please provide a photo or video of the problem "icons keep
flashing"?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Icons.keep.flashing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801410/+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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)

2018-11-06 Thread Benjamin Li
I am so so so sorry for I made a mistake of selecting the wrong kernel
with the wrong architecture to install, which lead to all those error
messages during boot in v4.19. (My laptop should install the kernel with
architecture amd64 but I installed i386, I am so sorry for making things
more complicated, SORRY!!!)

Anyway, I "apt purge" the wrong kernel (4.19 with architecture i386) and
just installed the proper one(architecture amd64).

However! The issue in the v4.17 remain in the 4.19! I don't see anything
improve in my situation, I still can't get in the system, getting stuck
in the black screen after the Ubuntu logo during the boot, I can only
access the system in recovery mode; the brightness of my display can't
be adjusted; the setting for my display still says "Unknown Display",
and the laptop can't get back if I put the whole system into sleep
mode(by turn off the display)

Any idea? Please help Thanks in advance!

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

Title:
  Xorg freeze (black screen after ubuntu logo during boot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+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 1801225] Re: cmake files are misplaced

2018-11-06 Thread Sylvestre Ledru
@doko if I prepare the patch, can you help with a SRU? Thanks

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

Title:
  cmake files are misplaced

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