[Ubuntu-x-swat] [Bug 1773087] Re: Remove python3-apport as dependency of xserver-xorg

2019-10-14 Thread Christopher M. Penalver
sordna, regarding your specific problem, please file a bug against apport via a 
terminal:
ubuntu-bug apport

In this new report, please copy/paste the reproduction steps, and result
as per terminal command.

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

Title:
  Remove python3-apport as dependency of xserver-xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773087/+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 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC

2019-09-23 Thread Christopher M. Penalver
** No longer affects: mesa (Ubuntu)

** Project changed: mesa => mesa (Ubuntu)

** Changed in: mesa (Ubuntu)
   Status: Unknown => New

** Changed in: mesa (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #72877 => None

** Changed in: mesa (Ubuntu)
   Status: New => Triaged

** Description changed:

- Hi all,
+ Upstream report:
+ https://gitlab.freedesktop.org/mesa/mesa/issues/477
  
  I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on
  Lubuntu 14.04. Unfortunately all have issued false colors in games. They
  appear to be ABGR instead of RGBA, thus blue becomes green, red becomes
  alpha etc.
  
  This issue affects sdl2 applications either.
  
  The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04
  PowerPC.
  
  Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem.
  
  The transitional solution is to install the old Mesa 8.0.X with "Force
  Version" with the Synaptic package manager on new distributions.
  
  In my point of view, the problem is in the source file p_format.h in the
  directory src/gallium/include/pipe/. There is some code for translating
  colors for big-endian machines. The problem is, this code is only for
  the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards
  don't need this translating code but IBM pSeries machines without
  graphics cards need this code. This code translates the colors in a
  wrong way for Radeon graphics cards. I removed this code and after
  compiling Mesa again, the colors are displayed correctly. I released
  some unofficial Mesa versions with this patch.
  
  Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib-
  unofficial.html
  
  Hardware:
  
  AmigaOne X1000 (Nemo)
  PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU
  "Xena" 500MHz XMOS XS1-L2 124
  8GB DDR2 SDRAM
  XFX Radeon HD 6870, 1 GB RAM
  OCZ600MXSP 600 Switching power supply
  RTL 8139/8139C/8139C+ network card
  TSSTcorp CDDVDW SH-224BB dvd drive
  ATA ST2000DM001-9YN1 SEAGATE HD
  ATA ESA 3SF1240GB HD
  
  More information:
  
  http://en.wikipedia.org/wiki/AmigaOne_X1000
  http://www.supertuxkart-amiga.de/amiga/x1000.html
  
  Rgds,
  Christian
  ---
  ApportVersion: 2.20-0ubuntu3
  Architecture: powerpc
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] 
(prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107]
  Package: libgl1-mesa-dri 11.1.2-1ubuntu1
  PackageArchitecture: powerpc
  ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash
  ProcModules: kvm_pr 91899 0 - Live 0x
  Tags:  xenial ubuntu
  Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1

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

Title:
  Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/+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 1547235] Re: 1002:7942 [Samsung NP-R40FY0E/SEG] Graphical corruption

2019-09-20 Thread Christopher M. Penalver
** No longer affects: xserver-xorg-driver-ati

** Description changed:

- Ubuntu has graphical corruptions as per the attachment.
+ Graphical corruptions as per the attachment.
+ 
+ Upstream report:
+ https://gitlab.freedesktop.org/mesa/mesa/issues/333
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16 [modified: 
boot/vmlinuz-4.4.0-2-generic]
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  m  1199 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 18 22:40:06 2016
  HibernationDevice: RESUME=UUID=1a9cc3e7-ec1c-4f67-95c9-f96d010b2a7a
  InstallationDate: Installed on 2016-02-10 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R40P/R41P
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=860436bf-bd69-4811-8843-9ba08a391b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 06YE
  dmi.board.name: R40P/R41P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr06YE:bd07/18/2007:svnSAMSUNGELECTRONICSCO.,LTD.:pnR40P/R41P:pvr06YE:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR40P/R41P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R40P/R41P
  dmi.product.version: 06YE
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
- --- 
+ ---
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
-Subsystem: Samsung Electronics Co Ltd RS600M [Radeon Xpress 1250] 
[144d:c036]
+  Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
+    Subsystem: Samsung Electronics Co Ltd RS600M [Radeon Xpress 1250] 
[144d:c036]
  InstallationDate: Installed on 2016-02-10 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R40P/R41P
  Package: xorg 1:7.7+13ubuntu1
  PackageArchitecture: amd64
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=860436bf-bd69-4811-8843-9ba08a391b58 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-2-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 06YE
  dmi.board.name: R40P/R41P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr06YE:bd07/18/2007:svnSAMSUNGELECTRONICSCO.,LTD.:pnR40P/R41P:pvr06YE:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR40P/R41P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R40P/R41P
  dmi.product.version: 06YE
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  

[Ubuntu-x-swat] [Bug 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2019-07-27 Thread Christopher M. Penalver
Stephan Fabel, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1724307/comments/28 regarding you no longer use the
hardware. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you
again for taking the time to report this bug and helping to make Ubuntu
better. Please submit any future bugs you may find.

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

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

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2019-07-23 Thread Christopher M. Penalver
Quoc Khanh Le (qkle), it will help immensely if you use Ubuntu with the 
computer the problem is reproducible with and file a new report via a terminal 
to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1724307

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2019-07-23 Thread Christopher M. Penalver
Stephan Fabel, could you please advise to all of the following:

1) Has the issue been tested with using the latest DisplayLink driver
(now 5.2.14)?

2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

3) Would the following WORKAROUND work with your environment following
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1724307/comments/24 ?

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => 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/1724307

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307/+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 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2019-05-17 Thread Christopher M. Penalver
Michael Neuffer, this report has been missing key information since 2014
->
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/comments/33
.

Hence, could you please test http://cdimage.ubuntu.com/daily-live/current/ and 
if reproducible please run the following command once from a terminal by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information:
apport-collect 1268151

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

Title:
  [Dell M4800] DPMS support broken, fails to wake up the monitor after
  putting it to sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity

2019-03-28 Thread Christopher M. Penalver
Hark:

1) For one who is using 16.04, an upgrade for the X stack is available
following instructions from
https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Could you please
advise to the results?

2) Regarding the package xserver-xorg-video-ati, this is fixed as per
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
ati/+bug/1821505/comments/4 .

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Fix Released

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

Title:
  [radeon] screen cannot be turned back on after some time of inactivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+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 1821505] Re: screen cannot be turned back on after some time of inactivity

2019-03-24 Thread Christopher M. Penalver
Hark, thank you for reporting this and helping make Ubuntu better.

1) To confirm a regression, has this always been an issue since you
installed "Ubuntu-Server 10.04 LTS" or is this something that started to
happen after an update?

2) To clarify, did you personally test the WORKAROUNDs noted in the Bug
Description, and confirm this works for your hardware?

2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Tags added: latest-bios-1.18

** Description changed:

  When using my AMD Radeon X1300 card, if the screen turns off due to
  inactivity, it cannot be woken up by moving the mouse or by hitting a
  key.
  
- When I restart the display manager via ssh with another computer, the
- screen then comes to life again and I can log back in.
+ WORKAROUND: Type in a terminal:
+ xset -display :0.0 dpms force off
  
- There is no problem waking the screen when I type "xset -display :0.0
- dpms force off" in a terminal. Moreover typing gnome-screensaver-command
- -a in a terminal turns my screen off and after typing this line, the
- screen can be woken up by moving the mouse or by hitting a key.
+ WORKAROUND: Typing the following in a terminal turns my screen off, and after 
typing this line, the screen can be woken up by moving the mouse or by hitting 
a key:
+ gnome-screensaver-command -a
+ 
+ WORKAROUND: When I restart the display manager via ssh with another
+ computer, the screen then comes to life again and I can log back in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 24 11:11:17 2019
  DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] 
[1458:215c]
+  Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] 
[1458:215c]
  InstallationDate: Installed on 2010-05-13 (3236 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  MachineType: FUJITSU SIEMENS ESPRIMO E5720
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic 
root=/dev/mapper/orao-root ro rootfstype=ext4 quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago)
  dmi.bios.date: 02/05/2009
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.18.2594.A1
  dmi.board.name: D2594-A1
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2594-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr:
  dmi.product.name: ESPRIMO E5720
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Mar 24 11:06:06 2019
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech USB Receiver KEYBOARD, id 8
-  inputLogitech USB Receiver KEYBOARD, id 9
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputLogitech USB Receiver KEYBOARD, id 8

[Ubuntu-x-swat] [Bug 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

2019-03-23 Thread Christopher M. Penalver
Hark (cab902), it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

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

Title:
  screen cannot be turned back on after being switched off after some
  time of inactivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-03-07 Thread Christopher M. Penalver
yoshiki2, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-26 Thread Christopher M. Penalver
opensas:

1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/43
 >"Then I tried with several versions from the upstream kernels..."

Which upstream kernels did you test precisely?

2)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/46
 >"Any idea about how should I proceed?"

If it is confirmed via your testing that it doesn't work in Ubuntu 
kernel 4.13.0-19, then one could reverse commit bisect from 4.13.0-19 to 
4.13.0-21 to find which commit(s) is the fix following 
https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernels 
.

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-24 Thread Christopher M. Penalver
** Tags added: needs-bisect- needs-upstream-testing

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-24 Thread Christopher M. Penalver
opensas, the next step is to fully commit bisect from 4.13.13 to 4.15.

This will allow for a direct review of the offending commit for either
reverting, or further improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks who don't know anything about linux, so it's easy to
follow.

Please note, finding adjacent kernel versions, or providing a commit
without testing it and reverting it is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the bad commit (not kernel version) has
been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-22 Thread Christopher M. Penalver
opensas:

To further narrow the regression, in Ubuntu 18.04 or higher, if you
install kernel 4.13.3 from https://wiki.ubuntu.com/Kernel/MainlineBuilds
does the touchpad work again?

** Tags removed: regression-potential
** Tags added: regression-release

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-21 Thread Christopher M. Penalver
opensas:

To confirm the regression point, could you please test a live
environment of https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes and
advise to the results?

** Description changed:

- The touchpad doesn't work.
+ The touchpad doesn't work unless the cursor is moved slowly.
  
  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  

[Ubuntu-x-swat] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-21 Thread Christopher M. Penalver
opensas:

1) To advise, you don't have to apport-collect any further unless
specifically requested to do so.

2) Does the touchpad work in the live environment of 18.04 without using
any WORKAROUND?

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-21 Thread Christopher M. Penalver
opensas, please advise to all of the following:

1) When discussing this issue, please keep it to only one machine (the
Dell XPS 13 L321X, not multiple) and Ubuntu (not popos! or some other
unsupported distro, unofficial flavor, etc.).

2) Regarding this issue with the Dell XPS 13 L321X, is this reproducible
in a live environment of Ubuntu 18.04 via
https://wiki.ubuntu.com/BionicBeaver ?

3) Do you know which package, that after when updated, this problem is
reproducible in?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

** Tags removed: bionic cosmic

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1816947/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-21 Thread Christopher M. Penalver
** Description changed:

+ The touchpad doesn't work.
  
- already filed at: 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046
- 
- check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
- synaptics/+bug/1096046/comments/33
- 
- affects: xserver-xorg-input-synaptics (Ubuntu)
- 
- The bug is marked expired an low priority, but it really prevents me
- from using ubuntu or any other distro based on it on my machine. Please
- reopen it!
- 
- the bug has been successfully reproduced on my machine using the latest
- daily build
- 
- ---
- 
- $ lspci -v
- 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
-   Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller
-   Flags: bus master, fast devsel, latency 0
-   Capabilities: 
- 
- 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA 
controller])
-   Subsystem: Dell 2nd Generation Core Processor Family Integrated 
Graphics Controller
-   Flags: bus master, fast devsel, latency 0, IRQ 30
-   Memory at f000 (64-bit, non-prefetchable) [size=4M]
-   Memory at e000 (64-bit, prefetchable) [size=256M]
-   I/O ports at 2000 [size=64]
-   [virtual] Expansion ROM at 000c [disabled] [size=128K]
-   Capabilities: 
-   Kernel driver in use: i915
-   Kernel modules: i915
- 
- 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
-   Subsystem: Dell 6 Series/C200 Series Chipset Family MEI Controller
-   Flags: bus master, fast devsel, latency 0, IRQ 31
-   Memory at f0605000 (64-bit, non-prefetchable) [size=16]
-   Capabilities: 
-   Kernel driver in use: mei_me
-   Kernel modules: mei_me
- 
- 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
-   Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host 
Controller
-   Flags: bus master, medium devsel, latency 0, IRQ 16
-   Memory at f060a000 (32-bit, non-prefetchable) [size=1K]
-   Capabilities: 
-   Kernel driver in use: ehci-pci
- 
- 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
-   Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition 
Audio Controller
-   Flags: bus master, fast devsel, latency 0, IRQ 33
-   Memory at f060 (64-bit, non-prefetchable) [size=16K]
-   Capabilities: 
-   Kernel driver in use: snd_hda_intel
-   Kernel modules: snd_hda_intel
- 
- 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5) (prog-if 00 [Normal decode])
-   Flags: fast devsel, IRQ 16
-   Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
-   Capabilities: 
-   Kernel driver in use: pcieport
- 
- 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5) (prog-if 00 [Normal decode])
-   Flags: bus master, fast devsel, latency 0, IRQ 17
-   Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
-   Memory behind bridge: f050-f05f
-   Capabilities: 
-   Kernel driver in use: pcieport
- 
- 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5) (prog-if 00 [Normal decode])
-   Flags: bus master, fast devsel, latency 0, IRQ 19
-   Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
-   Memory behind bridge: f040-f04f
-   Capabilities: 
-   Kernel driver in use: pcieport
- 
- 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
-   Subsystem: Dell 6 Series/C200 Series Chipset Family USB Enhanced Host 
Controller
-   Flags: bus master, medium devsel, latency 0, IRQ 23
-   Memory at f0609000 (32-bit, non-prefetchable) [size=1K]
-   Capabilities: 
-   Kernel driver in use: ehci-pci
- 
- 00:1f.0 ISA bridge: Intel Corporation QS67 Express Chipset LPC Controller 
(rev 05)
-   Subsystem: Dell QS67 Express Chipset Family LPC Controller
-   Flags: bus master, medium devsel, latency 0
-   Capabilities: 
-   Kernel driver in use: lpc_ich
-   Kernel modules: lpc_ich
- 
- 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port Mobile SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
-   Subsystem: Dell 6 Series/C200 Series Chipset Family 6 port Mobile SATA 
AHCI Controller
-   Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 29
-   I/O ports at 2088 [size=8]
-   I/O ports at 2094 [size=4]
-   I/O ports at 2080 [size=8]
-   I/O ports at 

[Ubuntu-x-swat] [Bug 1096046] Re: [HP Folio 13 Notebook PC] Touchpad not working after last apt-get upgrade in Precise

2019-02-21 Thread Christopher M. Penalver
** Summary changed:

- Touchpad not working after last apt-get upgrade
+ [HP Folio 13 Notebook PC] Touchpad not working after last apt-get upgrade in 
Precise

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

Title:
  [HP Folio 13 Notebook PC] Touchpad not working after last apt-get
  upgrade in Precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+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 1555431] Re: vlc crashed with SIGSEGV

2019-02-03 Thread Christopher M. Penalver
Closing as upstream issue, not using Xenial, not using older version of
VLC or xserver-xorg-video-intel, and issue may already be addressed in
later versions of Ubuntu with later version of xserver-xorg-video-intel
and VLC.

** No longer affects: vlc

** No longer affects: xserver-xorg-video-intel

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  vlc crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1555431/+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 1492639] Re: external monitor doesnt wake up after suspend

2018-12-23 Thread Christopher M. Penalver
** Tags removed: bios-outdated-2.34
** Tags added: bios-outdated-2.50 cosmic

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

Title:
  external monitor doesnt wake up after suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1492639/+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 1552040] Re: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor

2018-12-23 Thread Christopher M. Penalver
** Tags removed: bios-outdated-2.49
** Tags added: bios-outdated-2.50

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

Title:
  [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external
  monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1552040/+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 1554471] Re: Mouse not working

2018-12-23 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/comments/9 .

** Changed in: xorg (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Mouse not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/+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 1610591] Re: Video acceleration regression for Radeon Xpress 200M (r300) in xorg-lts-xenial & xorg-lts-wily

2018-09-15 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1610591/comments/53
.

** No longer affects: xserver-xorg-video-ati (Ubuntu)

** Project changed: xserver-xorg-driver-ati => xserver-xorg-driver-ati
(Ubuntu)

** Changed in: xserver-xorg-driver-ati (Ubuntu)
   Importance: Unknown => Undecided

** Changed in: xserver-xorg-driver-ati (Ubuntu)
   Status: Unknown => New

** Changed in: xserver-xorg-driver-ati (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #97228 => None

** No longer affects: xserver-xorg-driver-ati (Ubuntu)

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Video acceleration regression for Radeon Xpress 200M (r300) in xorg-
  lts-xenial & xorg-lts-wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1610591/+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 1085751] Re: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!

2018-09-01 Thread Christopher M. Penalver
** No longer affects: xserver-xorg-video-ati (Ubuntu Precise)

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

Title:
  [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1085751/+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 1085751] Re: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!

2018-09-01 Thread Christopher M. Penalver
** Package changed: fedora => xorg (Fedora)

** Changed in: xorg (Fedora)
   Importance: High => Undecided

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

** Changed in: xorg (Fedora)
 Remote watch: freedesktop.org Bugzilla #54133 => None

** No longer affects: linux (Ubuntu Quantal)

** No longer affects: linux (Ubuntu Precise)

** No longer affects: linux (Ubuntu)

** Changed in: xorg (Fedora)
   Status: New => Invalid

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

Title:
  [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1085751/+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 1040844] Re: Left Mouse Button Sometimes Gets Stuck in Unity (12.04)

2018-08-22 Thread Christopher M. Penalver
Norm Paul, it is most helpful if you use the host computer (not VM) the problem 
is reproducible with and file a new report with Ubuntu by first ensuring the 
package xdiagnose is installed, and click the Yes button for attaching 
additional debugging information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to 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/1040844

Title:
  Left Mouse Button Sometimes Gets Stuck in Unity (12.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1040844/+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 1787651] Re: Mouse stops clicking using Jabra Evolve 65 via bluetooth

2018-08-21 Thread Christopher M. Penalver
Marking Fix Released as not reproducible in latest Ubuntu release as per
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1787651/comments/3, and as defined by
https://wiki.ubuntu.com/Bugs/Status .

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

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

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787651/+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 1787651] Re: Mouse stops clicking using Jabra Evolve 65 via bluetooth

2018-08-20 Thread Christopher M. Penalver
Leônidas, one may update their kernel and xorg stack in 16.04 via
https://wiki.ubuntu.com/Kernel/LTSEnablementStack .

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

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

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787651/+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 1787651] Re: Mouse stop clicking Jabra

2018-08-17 Thread Christopher M. Penalver
Leônidas, thank you for reporting this and helping make Ubuntu better.

1) To see if this is already resolved in Ubuntu, could you please test
this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?

2) To clarify, does the following provide a WORKAROUND:
 Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following and 
restart xorg-server:
Section "InputClass"
 Identifier "Jabra"
MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
 Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
EndSection

** Tags added: bios-outdated-1.52

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Summary changed:

- Mouse stop clicking Jabra 
+ Mouse stops clicking using Jabra Evolve 65 via bluetooth

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

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1787651/+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 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2018-08-17 Thread Christopher M. Penalver
Leônidas (leonidasklein), it is most helpful if you use the computer the 
problem is reproducible with and file a new report with Ubuntu, by first 
ensuring the package xdiagnose is installed, and click the Yes button for 
attaching additional debugging information after running the following from a 
terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to 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/1619307

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619307/+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 1784998] Re: After a while touchpad doesn't work

2018-08-15 Thread Christopher M. Penalver
fokedFromTheLife:

1) Regarding the following non-default kernel parameters in use, could you 
please advise to each individually on why it was put in place, and if it is 
necessary for the touchpad to work:
nouveau.modeset=0
tpm_tis.interrupts=0
acpi_osi=Linux
i915.preliminary_hw_support=1
idle=nomwait

** Description changed:

- after a while my touch pad don't work but mouse with usb work in my laptop
- my laptop : Asus GL553V
+ By default, touchpad doesn't work, but USB mouse works.
+ 
+ WORKAROUND: Install the NVIDIA proprietary drivers, and use non-default 
kernel parameters:
+ nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux 
i915.preliminary_hw_support=1 idle=nomwait
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  2 10:23:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
-Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
+  Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
+    Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
  InstallationDate: Installed on 2018-04-29 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
-  Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. 
-  Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
+  Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp.
+  Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash 
nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux 
i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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
  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

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

Title:
  After a while touchpad doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+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 1784998] Re: After a while touchpad doesn't work

2018-08-15 Thread Christopher M. Penalver
** Tags added: cosmic

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

Title:
  After a while touchpad doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+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 1552040] Re: [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor

2018-08-11 Thread Christopher M. Penalver
Sergey Menshikov, it is most helpful if you use the computer the problem is 
reproducible with, and file a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external
  monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1552040/+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 1784998] Re: After a while touchpad doesn't work

2018-08-11 Thread Christopher M. Penalver
fokedFromTheLife:

1)
>"so when i install ubuntu the touchpad don't work i go to 
>http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked"

To clarify, you are stating that by default, the touchpad doesn't work
at all. However, after using the non-default kernel parameters, and
installing the NVIDIA proprietary drivers, the touchpad then begins to
work?

2) 
>"after an update my touchpad stopped again"

Which update precisely, and what date was the update applied?

3) To confirm this is resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

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

Title:
  After a while touchpad doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+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 1784998] Re: After a while touchpad doesn't work

2018-08-11 Thread Christopher M. Penalver
fokedFromTheLife, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following:

1) Regarding your Bug Description comment:
>"after a while..."

1a) Could you please define specifically how long a while is? Seconds, minutes, 
hours, etc.?
1b) Could you please advise to after a while from when? Boot up, login, opening 
a program, etc.? 

2) Is this issue something that started to happen after an update? If
so, which and when precisely?

3) Regarding the non-default kernel parameters:
nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux 
i915.preliminary_hw_support=1 idle=nomwait

If you remove these, is the issue still reproducible?

** Tags added: bios-outdated-307

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1784998

Title:
  After a while touchpad doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2018-08-04 Thread Christopher M. Penalver
** Tags removed: bios-outdated-1.42
** Tags added: bionic bios-outdated-1.46

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

2018-07-31 Thread Christopher M. Penalver
Chris Guiver, you may need to use:
sudo ubuntu-bug /var/crash/FILENAME.crash

when filing crash reports in order for the upload/uploaded files to be
generated, and, in turn, to get the errors reported successfully.

Given the reproducibility of the crash, and how you are using the latest
Ubuntu release, I'll mark this Triaged for now, and an xorg developer
may further review.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

2018-07-31 Thread Christopher M. Penalver
** Description changed:

  // this bug was reported for 18.04.
  // I had just had it occur (first time) on 18.10
  // new details will be comment @ end
  
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)
  
  I sleep my XFCE (xubuntu) machine rather than turning it off at night.
  
  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank screen
  with a RADEON two-line text message top left on screen which appear only
  momentarily as screen is erased and I get the login/greeter screen.
  
  (it's happened 4-5 times, but does NOT happen every time)
  
  I can login fine, but my xfce session is new.
  
  I have grep'd for the message I see (yesterday & today), but can't find
  it as i usually recall little but the radeon word...
  
  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d
  
  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)
  
  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166.
   68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session opened for user guiverc by (uid=0)
   69 May 22 09:37:39 d960-ubu2 systemd-logind[1108]: New session 178 of user 
guiverc.
   70 May 22 09:38:11 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out 

[Ubuntu-x-swat] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

2018-07-31 Thread Christopher M. Penalver
Chris Guiver:

1) While the issue is being root caused, please keep light-locker, and
caffeine uninstalled.

2) Regarding the file:
-rw-r- 1 guiverc whoopsie 20M Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash

No error reports have been reported to errors since 2018-07-11. One may
further confirm is if in the folder /var/crash there are files .upload
and .uploaded found along with the same .crash file (or a bug report is
created on Launchpad). Clicking on the crash GUI doesn't indicate if a
crash was successfully reported. For more on this, please see
https://help.ubuntu.com/community/ReportingBugs .

Hence, could you please report the crash, and advise to the additional
files in /var/crash?

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)

2018-07-29 Thread Christopher M. Penalver
Chris Guiver:

1) To confirm, please run the following command and post the results:
sudo cat /var/lib/whoopsie/whoopsie-id

2) To confirm a WORKAROUND in 18.10, if you uninstall both light-locker
and caffeine simultaneously, is a crash still reproducible?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: Invalid => Incomplete

** Tags added: cosmic

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen  (18.04 & 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1613863] Re: Fails to power off monitor when locking screen

2018-07-28 Thread Christopher M. Penalver
Anders Magnus Andersen, this bug report is being closed due to your last
comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1613863/comments/10 regarding you don't have the equipment
anymore. For future reference you can manage the status of your own bugs
by clicking on the current status in the yellow line and then choosing a
new status in the revealed drop down box. You can learn more about bug
statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for
taking the time to report this bug and helping to make Ubuntu better.
Please submit any future bugs you may find.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Medium => Undecided

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Fails to power off monitor when locking screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1613863/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-07-23 Thread Christopher M. Penalver
Chris Guiver, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/comments/17
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Importance: Low => Undecided

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

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

2018-07-01 Thread Christopher M. Penalver
vik:

1) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full monitor manufacturer and model?

2) Regarding how you have the monitor connected, is it plugged into the
dock's DVI-I, or DisplayPort port? If you switch the port is this still
reproducible?

3) Regarding the connection of the monitor to the dock, is this via
straight DVI-I cord, using dongle/adapter, etc.?

4) If you instead undock the computer, and plug the monitor directly
into the computer, is this still reproducible?

5) Regarding the Lenovo ThinkPad OneLink Pro Dock, have you applied the
latest firmware to it?

** Tags removed: latest-bios-1.29
** Tags added: bios-outdated-1.38 regression-potential

** Attachment removed: "syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+attachment/4780928/+files/syslog.txt

** Changed in: xorg (Ubuntu)
   Importance: Medium => Low

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

** Summary changed:

- Laptop sometimes doesn't detect external monitor when docked
+ [Lenovo ThinkPad Yoga Type 20C0] Laptop sometimes doesn't detect external 
monitor when docked into ThinkPad OneLink Pro Dock

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

Title:
  [Lenovo ThinkPad Yoga Type 20C0] Laptop sometimes doesn't detect
  external monitor when docked into ThinkPad OneLink Pro Dock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+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 1552040] Re: Laptop sometimes doesn't detect external monitor

2018-07-01 Thread Christopher M. Penalver
Kai Mast:

1) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full monitor manufacturer and model?

2) Regarding how you have the monitor connected, is this straight into
the computer's miniDP cable, mDP to something else adapter, etc.?

3) Did this issue start to happen after an update? If so, which and when
precisely?

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Confirmed => Incomplete

** Summary changed:

- Laptop sometimes doesn't detect external monitor
+ [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external monitor

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

Title:
  [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external
  monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1552040/+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 1552040] Re: Laptop sometimes doesn't detect external monitor

2018-07-01 Thread Christopher M. Penalver
** Tags removed: bios-outdated-2.41
** Tags added: bios-outdated-2.49

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

Title:
  [Lenovo ThinkPad T440s] Laptop sometimes doesn't detect external
  monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1552040/+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 268506] Re: Cannot configure Synaptics TouchStyk settings (e.g. sensitivity, tapping, press/select)

2018-06-23 Thread Christopher M. Penalver
James (jamestheawesomedude), it will help immensely if you use the computer the 
problem is reproducible with, file a new report with Ubuntu by first ensuring 
the package xdiagnose is installed, and click the Yes button for attaching 
additional debugging information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

** No longer affects: libinput (Ubuntu)

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

Title:
  Cannot configure Synaptics TouchStyk settings (e.g. sensitivity,
  tapping, press/select)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268506/+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 1771539] Re: Xorg crash

2018-06-20 Thread Christopher M. Penalver
Mario Costa:

A) Could you please provide the result of the following terminal command:
sudo cat /var/lib/whoopsie/whoopsie-id

B) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the result?

** Changed in: xorg (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/1771539

Title:
  Xorg crash

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

2018-06-20 Thread Christopher M. Penalver
** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1771539

Title:
  Xorg crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-06-20 Thread Christopher M. Penalver
** Description changed:

  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)
  
  I sleep my XFCE (xubuntu) machine rather than turning it off at night.
  
  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank screen
  with a RADEON two-line text message top left on screen which appear only
  momentarily as screen is erased and I get the login/greeter screen.
  
  (it's happened 4-5 times, but does NOT happen every time)
  
  I can login fine, but my xfce session is new.
  
  I have grep'd for the message I see (yesterday & today), but can't find
  it as i usually recall little but the radeon word...
  
  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d
  
  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)
  
  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
-  48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
-  49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
-  50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
-  51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
+  48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
+  49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
+  50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
+  51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
-  52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
-  53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
-  54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
-  55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
-  56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
-  57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
-  58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
-  59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
-  60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
-  61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
-  62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
-  63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
-  64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
-  65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
-  

[Ubuntu-x-swat] [Bug 1298578] Re: Brightness is low after resume from suspend, can't be increased

2018-06-19 Thread Christopher M. Penalver
Paulo Marcel Coelho Aragão, as this report is closed, if you would like your 
issue addressed, report your problem by using the computer the problem is 
reproducible with, and provide necessary debugging logs by filing a new report 
with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  Brightness is low after resume from suspend, can't be increased

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1298578/+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 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-06-18 Thread Christopher M. Penalver
** Changed in: xorg (Ubuntu)
   Importance: Medium => Low

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1770306

Title:
  X display is black after 18.04 upgrade from 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+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 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-06-18 Thread Christopher M. Penalver
Kevin Dalley, to clarify your comment:

>"I tried the cdimage mentioned above, and it works. What does that
ultimately suggest? I didn't have a login screen for the cdimage, of
course."

You said the image works, but you don't have a login screen. Not having
a login screen would be considered not working. Could you please
clarify?

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

Title:
  X display is black after 18.04 upgrade from 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+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 1509776] Re: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

2018-06-17 Thread Christopher M. Penalver
liontamer, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/1509776/comments/33 regarding this being fixed with an
update. For future reference you can manage the status of your own bugs
by clicking on the current status in the yellow line and then choosing a
new status in the revealed drop down box. You can learn more about bug
statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for
taking the time to report this bug and helping to make Ubuntu better.
Please submit any future bugs you may find.

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1509776/+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 1770166] Re: The brightness of the notebook

2018-06-15 Thread Christopher M. Penalver
Adrian:

1) Is this something that stopped working after an update? If so, which
and when precisely?

2) Could you please provide the missing information from
https://wiki.ubuntu.com/Kernel/Debugging/Backlight ?

** Tags added: bios-outdated-1.30

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

Title:
  The brightness of the notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770166/+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 503041] Re: Mouse lags while moving it and clicking any keys

2018-06-08 Thread Christopher M. Penalver
** No longer affects: xserver-xorg-input-synaptics (Ubuntu)

** Project changed: evdev => xserver-xorg-input-evdev (Ubuntu)

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Importance: Medium => Undecided

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Status: Won't Fix => New

** Changed in: xserver-xorg-input-evdev (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #29870 => None

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Importance: Undecided => Low

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Status: New => Incomplete

** Package changed: xserver-xorg-input-evdev (Ubuntu) => xserver-xorg-
input-synaptics (Ubuntu)

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

Title:
  Mouse lags while moving it and clicking any keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/503041/+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 1771539] Re: Xorg crash

2018-06-06 Thread Christopher M. Penalver
Mario Costa:

1) Please provide the output of the following terminal command (not manually 
attach anything found):
ls -la /var/crash

2) As per your Bug Description, you are using the non-default kernel parameter:
radeon.runpm=0

Could you please advise to if this is required to use?

Also, if you remove it, does the crash still happen?

3) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full monitor manufacturer and model?

4) How are you connecting the monitor to the computer, via DisplayPort-
to-DisplayPort cable, DisplayPort-to-HDMI cable, dongle/adapter, etc.?

5) If you keep the external monitor disconnected from the computer on
boot up, and after login then plug it in does this provide a WORKAROUND?

6) Does the crash only happen after coming up from a cold boot, only
after resuming from suspend, etc.?

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

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

Title:
  Xorg crash

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

2018-06-06 Thread Christopher M. Penalver
** Tags removed: bios-outdated-1.44
** Tags added: latest-bios-1.44

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

Title:
  Xorg crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-06-05 Thread Christopher M. Penalver
Chris Guiver, to confirm a WORKAROUND, if you uninstall both light-
locker and caffeine simultaneously, is a crash still reproducible?

** Changed in: xorg (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/1772542

Title:
  after waking from sleep i get text radeon error message then return
  login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-05 Thread Christopher M. Penalver
Roger Davis, could you please provide undo the WORKAROUND, and provide
the missing information from https://wiki.ubuntu.com/DebuggingKernelBoot
?

** Description changed:

  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it offers,
  and get by it, after which things look and work normally until a reboot,
  which may or may not occur correctly.
  
  I also usually get "System error detected, Report? at the same time, so
  I agree to report it.
  
- Please note that I'm using 16.04 (fully updated), Gnome Flashback
- Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
- . This problem shows up no matter which of the above I'm using, or
- Unity.
- 
- roger@roger-desktop:~$ uname -a
- Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ This problem shows up using GNOME Flashback or Unity.
  
  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348
  
  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000
  
- I have found a WORK-AROUND. Using x-diagnose, I selected all options
- under both Debug and Workarounds.  After this, all works normally every
- time.  However, I take this as a crutch, not a fix, and think other
- action should be taken
- 
- Selecting "View Errors" shows no errors, so I never tried reporting from
- that point.
- 
- This gives me a presumption that there is a bug in coding that interacts
- badly with my system and a few others like it, which I encountered in my
- search for a solution.
- 
- Also, if I simply go to 18.04 (I don't really want to just yet.) will it
- likely fix this or might this block or damage the upgrade?
- 
- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
- roger@roger-desktop:~$ lsb_release -rd
- Description:  Ubuntu 16.04.4 LTS
- Release:  16.04
- 
- 2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
- roger@roger-desktop:~$ apt-cache policy pkgname
- N: Unable to locate package pkgname
- ALSO - I'm unable to locate this information in Software Center
- 
- 3) What you expected to happen
- Normal boot, no errors or problems
- 
- 4) What happened instead
- "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages
+ WORKAROUND: Using x-diagnose, I selected all options under both Debug
+ and Workarounds.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
+  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Ubuntu-x-swat] [Bug 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread Christopher M. Penalver
d a i s y, to advise, the boot options in
https://wiki.ubuntu.com/DebuggingKernelBoot are so that you can provide
a screencast and/or log of a bad boot to root cause.

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread Christopher M. Penalver
** Description changed:

  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.
  
  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*
  
  Output of sudo lshw -c display
  
  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d
  
  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset
+ 
+ WORKAROUND: Edit the file /etc/gdm3/custom.conf and change:
+ #WaylandEnable=false
+ 
+ to:
+ WaylandEnable=false
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-04 Thread Christopher M. Penalver
Roger Davis:

a) You are responding multiple times to the same comment, causing confusion. 
Hence, it is best if you looked at the bug report (not email inbox) to confirm 
if you have already responded, and use the website to respond (not send emails):
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386

It is helpful if you use the website to "Hide" the duplicate comments
(#6, #9,  and #11) so others don't get confused.

b) Regarding your comment:
>"I'll hold off on filing a bug on Xdiagnose..."

Agreed. If you are using non-default kernel parameters, a potential
response would be "don't do that". However, if you have to use them so
the scope of this report doesn't happen, that's a different story.

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386/+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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-03 Thread Christopher M. Penalver
Roger Davis:

 A) Regarding your comment:
>"sudo apt-get install --install-recommends linux-generic-hwe-16.04 
>xserver-xorg-hwe-16.04"

That doesn't confirm you are booted into the HWE kernel. That only shows
that certain packages are installed (which you provided already in a
previous comment).

If you want to demonstrate what kernel is being using currently type:
uname -a

 B) Regarding your comment:
>"...but now after additional other updates, and using Xdiagnose with various 
>settings, I haven't seen a boot problem for a few updates. I will continue to 
>monitor for a few days with Xdiagnose off to assure that problem is really 
>gone."

Sounds good.

 B) Regarding your comment:
>"...actually causes a problem in my system. It sets and locks the theme to 
>Ambiance, even though the setting properly shows Adwaita."

Could be a bug, but that isn't the scope of this report. If you want it
fixed, you would have to file a new report.

 C) Regarding your comment:
>"Please tell me before I deal with this if this is possibly something done by 
>Xdiagnose..."

Given you don't recall doing it, it was done by Xdiagnose when you
checked its checkboxes.

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386/+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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-03 Thread Christopher M. Penalver
Roger Davis:

1) To clarify, when using the upgraded HWE stack, did this influence the
reported issue "message - Low Graphics mode - about 2/3 of startups -
not all"?

2) To narrow down, could you please provide the output of the following 
terminal command (not manually attach anything found):
ls -la /var/crash

3) To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

4) If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386/+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 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-31 Thread Christopher M. Penalver
** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1772183

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+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 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-30 Thread Christopher M. Penalver
Mike L, to clarify, does this issue happen when using a wired USB mouse?

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+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 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-30 Thread Christopher M. Penalver
** Summary changed:

- [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple 
lines at a time.
+ [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes 
mouse to scroll multiple lines at a time

** Description changed:

- In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes
- rebooting doesn't fix the issue. This problem doesn't happen in Windows
- 10.
+ What happens when booting immediately from Windows to Ubuntu is that the
+ mouse scrolls multiple lines at time. This problem doesn't happen when
+ booting to and using Windows 10.
  
  WORKAROUND: https://sourceforge.net/projects/resetmsmice/
+ 
+ WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
+ Windows.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+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 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-30 Thread Christopher M. Penalver
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1771204

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/+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 1773744] Re: Desktop session crash

2018-05-30 Thread Christopher M. Penalver
** Tags added: regression-release

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1773744

Title:
  Desktop session crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-05-30 Thread Christopher M. Penalver
** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1772542

Title:
  after waking from sleep i get text radeon error message then return
  login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-05-29 Thread Christopher M. Penalver
Chris Guiver:

1) Going forward, please don't quote snips of logs, as the root cause
issue could have happened well before this, and what you are snipping is
collateral damage. Instead, attach the log in its entirety as you have
done.

2) Regarding #7:
>"New crash reports in /var/crash are
-rw-r- 1 guiverc whoopsie 882227 May 29 14:17 
_usr_bin_light-locker.1000.crash
-rw-r- 1 guiverc whoopsie 24809765 May 30 09:54 
_usr_lib_xorg_Xorg.1000.crash"

To clarify, did these both happen after a resume from suspend, and then
you attempted to login? If so, what desktop session specifically (e.g.
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/1772542

Title:
  after waking from sleep i get text radeon error message then return
  login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-05-29 Thread Christopher M. Penalver
** Tags added: regression-release

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+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 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-29 Thread Christopher M. Penalver
Thomas Diesenreiter, the next step is to fully commit bisect from 4.13.4
to 4.15.17, in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
without testing it and reverting it is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the bad commit (not kernel version) has
been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+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 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-29 Thread Christopher M. Penalver
** Tags removed: kernel-bug-exists-upstream-4.17.0-041700rc6-generic
** Tags added: kernel-bug-exists-upstream-4.17-rc6

** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+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 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

2018-05-29 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849

** Description changed:

- I'm running bionic on a Lenovo X230 laptop.
- It works fine to boot it with either my hdmi monitor or my VGA monitor.
- It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.
+ If I boot up with two external monitors connected, the login screen
+ doesn't show up on any monitor.
  
- But if both are connected while I boot, the graphical login prompt never
- appears, and just the mouse appears in the laptop window on a blue
- screen, with the HDMI monitor showing a blank blue screen, and the VGA
- monitor getting no signal.
+ The laptop display shows the mouse cursor on a blue screen, the HDMI
+ monitor shows a blank blue screen, and the VGA monitor shows no signal.
  
- This monitor configuration worked fine with this computer in Trusty.
+ WORKAROUND: Use Trusty.
  
- I ran apport-bug to report the problem, and chose the first option:
- "Display (X.org)". I'm not positive what I'm running, but note that
- after booting and getting both monitors plugged in and running after
- login, I see both an Xwayland process and an Xorg process.  I suggest
- also changing apport-bug to appropriately reflect that wayland is
- somehow involved, and I hope that the included debug info will include
- any appropriate wayland info.  I note that it does seem to be possible
- to get some info via `apport-bug xwayland`.
+ WORKAROUND: Boot with only one external monitor connected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
-  TERM=screen
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

** This bug has been marked a duplicate of bug 1760849
   Enhancement: Make the login screen follow the mouse to other monitors

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

2018-05-29 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849

Neal McBurnett:

1) Regarding your crash files, please execute the following via a terminal to 
have them automatically processed:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is the file name of the crash file to report.

The upload is successful when the file with extension .uploaded is
subsequently created.

2) With regard to this report, you have at least two to three bugs here. One 
for each of the distinct crash files you noted, which reporting them will help 
to see them resolved. The third is along the lines of your Title+Bug 
Description:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760849

>From my cursory viewpoint, the crashes appear to be unrelated to the
login issue reported.

Hence, for now, let this be marked a duplicate of LP#1760849. However,
if after it is resolved your issue is still present, this report may
always be unduplicated, and resumed from there.

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773850/+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 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

2018-05-29 Thread Christopher M. Penalver
Mike L:

1) Regarding your comment:
>"removing and reinserting the transciever fixes it until you reboot into 
>Windows 10 again."

To clarify, you personally tested with your hardware that after removing
and reinserting, you can reboot Ubuntu as many times as you want and
this will never happen. However, if you reboot into Windows, then reboot
back into Ubuntu, the problem will occur again?

2) Going forward, it is most helpful you advise to what you have
personally tested with the hardware in your possession, versus cite what
someone else speculates, said they did, what you think might occur but
didn't confirm yourself, etc.

** Summary changed:

- Microsoft Mice on dual boot systems can scroll multiple lines at a time.
+ [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple 
lines at a time.

** Description changed:

- Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who
- knows how long. See https://askubuntu.com/questions/47100/mouse-wheel-
- scrolling-too-fast. Installing the workaround package or removing the
- transceiver appears to be a workaround for the time being. Xorg should
- automatically scroll normally, not multiple lines at time after
- rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions
- the bug dating back to Natty.
+ In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes
+ rebooting doesn't fix the issue. This problem doesn't happen in Windows
+ 10.
+ 
+ WORKAROUND: https://sourceforge.net/projects/resetmsmice/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
-Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
+    Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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 

[Ubuntu-x-swat] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

2018-05-29 Thread Christopher M. Penalver
** Tags added: latest-bios-f.49

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

Title:
  Microsoft Mice on dual boot systems can scroll multiple lines at a
  time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+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 1773612] Re: I am just loading the OS onto my computer

2018-05-29 Thread Christopher M. Penalver
Gary De Maroney, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which and when precisely?

2) Do you have any actual issues uing the OS?

3) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: latest-bios-a11

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (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/1773612

Title:
  I am just loading the OS onto my computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773612/+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 1773744] Re: Desktop session crash

2018-05-29 Thread Christopher M. Penalver
Sami Pietila:

1) Regarding the crash files, please report these via executing the following 
at a terminal:
ubuntu-bug _opt_Gitter_linux64_Gitter.1000.crash
ubuntu-bug _usr_bin_gnome-shell.1000.crash
ubuntu-bug _usr_bin_Xwayland.1000.crash
ubuntu-bug _usr_lib_chromium-browser_chromium-browser.1000.crash
ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

The reporting is successful if files with the extension .uploaded are
populated after a few minutes.

2) In regard to gnome-session-flashback, at the login screen you clicked
the gear, chose GNOME Flashback (Metacity), logged in, didn't launch any
programs, connected the third monitor, and then the desktop crashed?

3) As per the sticker of the monitors (not from the Bug Description, or
the result of a terminal command), could you please provide the full
manufactuer and model?

4) How are you connecting your computer to the monitors?

5) Are you using any dongles/adapters when connecting to the monitors?

6) To confirm a regression, could you please test
http://releases.ubuntu.com/xenial/ubuntu-16.04.4-desktop-amd64.iso and
advise to the results?

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

Title:
  Desktop session crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+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 1773744] Re: Desktop session crash

2018-05-29 Thread Christopher M. Penalver
** Tags added: cosmic

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

Title:
  Desktop session crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+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 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

2018-05-29 Thread Christopher M. Penalver
** Description changed:

- Hello,
+ In Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu
+ desktop via X.org, a wrong display driver is used (llvmpipe). It will
+ cause a horribly poor performance due to software acceleration.
  
- in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via 
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor 
performance due to software acceleration.
- When I switch to Wayland, the correct driver (intel) with enabled hardware 
acceleration is loaded.
+ WORKAROUND: When I switch to Wayland, the correct driver (intel) with
+ enabled hardware acceleration is loaded.
  
- I have two exactly the same laptops, the same issue on both.
- 
- Hardware:
- HP ProBook 4330s
- Intel i5-2430M
- 8GB RAM
- 512GB SDD
- Kernel: 4.15.0-20-generic
- 
- Installed packages:
- 
- ii  intel-gpu-tools1.22-1 
 
- ii  intel-microcode3.20180312.0~ubuntu18.04.1 
 
- ii  libdrm-intel1:amd642.4.91-2   

- ii  libdrm-intel1:i386 2.4.91-2  
- 
- ii  libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-dri:amd64  18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-dri:i386   18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-glx:amd64  18.0.0~rc5-1ubuntu1
 
- ii  libgl1-mesa-glx:i386   18.0.0~rc5-1ubuntu1
 
- ii  libglapi-mesa:amd6418.0.0~rc5-1ubuntu1
 
- ii  libglapi-mesa:i386 18.0.0~rc5-1ubuntu1
 
- ii  libgles2-mesa:amd6418.0.0~rc5-1ubuntu1
 
- ii  libglu1-mesa:amd64 9.0.0-2.1build1
 
- ii  libglu1-mesa:i386  9.0.0-2.1build1
 
- ii  libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libglx-mesa0:i386  18.0.0~rc5-1ubuntu1
 
- ii  libosmesa6:amd64   18.0.0~rc5-1ubuntu1
 
- ii  libosmesa6:i38618.0.0~rc5-1ubuntu1
 
- ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  mesa-utils 8.4.0-1
 
- ii  mesa-va-drivers:amd64  18.0.0~rc5-1ubuntu1
 
- ii  mesa-vdpau-drivers:amd64   18.0.0~rc5-1ubuntu1 
- 
- ii  libva-wayland2:amd64   2.1.0-3
 
- ii  libwayland-client0:amd64   1.14.0-2   
 
- ii  libwayland-cursor0:amd64   1.14.0-2   
 
- ii  libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1
 
- ii  libwayland-server0:amd64   1.14.0-2   
 
- ii  xwayland   2:1.19.6-1ubuntu4 
-   
- ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1
- ii  xorg-docs-core 1:1.7.1-1.1
 
- ii  xserver-xorg   1:7.7+19ubuntu7
 
- ii  xserver-xorg-core  2:1.19.6-1ubuntu4  
 
- ii  xserver-xorg-input-all 1:7.7+19ubuntu7
 
- ii  xserver-xorg-input-libinput0.27.1-1   
 
- ii  xserver-xorg-input-wacom   1:0.36.1-0ubuntu1  
 
- ii  xserver-xorg-legacy2:1.19.6-1ubuntu4  
 
- ii  xserver-xorg-video-all 1:7.7+19ubuntu7
 
- ii  xserver-xorg-video-amdgpu  18.0.1-1   
 
- ii  xserver-xorg-video-ati 1:18.0.1-1  

[Ubuntu-x-swat] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

2018-05-28 Thread Christopher M. Penalver
Mike L, thank you for reporting this and helping make Ubuntu better.

1) As per the sticker of the mouse itself (not from the Bug Description,
or the result of a terminal command), could you please provide the full
model?

2) As per the title:
"...on dual boot systems..."

is there some dependency on dual booting, where this issue only shows up
when using a dual boot versus not? Are you stating this happens in
Windows also?

3) Regarding your Bug Description:
>"Noticed this bug in 16.04 and earlier for who knows how long."

Did you personally test the mouse on a release earlier than 16.04? If
so, which precisely?

4) As per the sticker of the computer itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full computer model?

5) Regarding your Bug Description:
>"Installing the workaround package..."

Please state which package precisely (not expect folks to dumpster dive
URLs/guess).

6) Regarding your Bug Description:
>"...or removing the transceiver appears to be a workaround..."

Are you stating that you remove it and then plug it back in? If so, do
you have to keep doing this every so often, or is it good until you
restart?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Tags added: xenial

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

Title:
  Microsoft Mice on dual boot systems can scroll multiple lines at a
  time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+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 1772917] Re: cannot maximize window

2018-05-28 Thread Christopher M. Penalver
** Package changed: xorg (Ubuntu) => unity (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/1772917

Title:
  cannot maximize window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1772917/+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 1773015] Re: appli Notes

2018-05-28 Thread Christopher M. Penalver
LLAMAs, thank you for reporting this and helping make Ubuntu better.

1) Regarding your Bug Description:
>"Does not start."

What precisely does not start?

2) Is this something that started to happen after an update? If so,
which and when precisely?

3) If you remove the following non-default kernel parameters you are using, is 
it still reproducible:
plymouth:debug vesafb.invalid=1 drm.debug=0xe nopat

4) To see if this is already resoled in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: latest-bios-1qcn32ww

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (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/1773015

Title:
  appli Notes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773015/+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 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

2018-05-28 Thread Christopher M. Penalver
Neal McBurnett, thank you for reporting this and helping make Ubuntu
better.

1) As per the sticker of the monitors (not from the Bug Description, or
the result of a terminal command), could you please provide the full
manufacturer and model?

2) Are you using any dongles/adapters to connect to either monitor?

3) To clarify, if you boot up with nothing attach, then login, then
attach both the VGA and HDMI, are you then able to configure all three
screens to display the desired output while logged in?

4) Was there a release newer than Trusty, but older then Bionic where
this issue wasn't reproducible?

5) Regarding desktop environment, are you presently using GNOME, Unity,
etc.?

6) Could you please post the output of the following terminal command (not 
manually attach files):
ls -la /var/crash

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (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/1773850

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773850/+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 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

2018-05-28 Thread Christopher M. Penalver
** Tags added: bios-outdated-2.70 regression-release

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773850/+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 1773744] Re: Desktop session crash

2018-05-28 Thread Christopher M. Penalver
Sami Pietila, thank you for reporting this and helping make Ubuntu
better.

1) To clarify, did this issue start after an update? If so, which and
when precisely?

2) Please provide the ouput of the following terminal command (not manually 
attach files):
ls -la /var/crash

3) To verify a WORKAROUND, if you install gnome-session-flashback does
this crash also?

4) To advise, keep in mind that this issue may be due to upgrade cruft
being left behind from your OS upgrade. Hence, testing
http://cdimage.ubuntu.com/daily-live/current/ would help rule this out.

** Tags added: bios-outdated-02.71

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (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/1773744

Title:
  Desktop session crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+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 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

2018-05-28 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1759300 ***
https://bugs.launchpad.net/bugs/1759300

Phill, if you install gnome-tweak-tool and configure GNOME Tweak Tool >
Keyboard & Mouse > Mouse Click Emulation > Area checked then it is a
configuration issue, and in turn, a duplicate.

However, if you have this configured and it still doesn't work, that's a
different issue.

Could you please advise?

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773516/+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 1773484] Re: Login screen not moved to used monitor

2018-05-28 Thread Christopher M. Penalver
Sending to gnome-shell for review, given monitor does display output
immediately after first configuration via Settings > Devices > Display
(i.e. appears not driver/kernel issue).

** Description changed:

- On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
- the monitor where the mouse pointer is located. On Ubuntu 18.04 login
- dialog and system menues are restricted to the main monitor.
+ What is expected to happen is that with my computer turned off, when I
+ plug in my external VGA monitor into my laptop for the first time, and
+ boot up to the login screen, the display is in mirror mode and I can see
+ the login screen on both the built-in screen, and external monitor.
  
- So if you have a notebook with defect lcd display you can work with it
- using Ubuntu 16.04 and an external monitor, but you cannot work with
- Ubuntu 18.04, because you are not able to login!
- 
- This problem was also asked on:
- 
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04
+ What happens instead is that the login screen is only shown on the
+ built-in screen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  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:220c]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_AT.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_AT.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

** Summary changed:

- Login screen not moved to used monitor
+ First bootup with external VGA monitor plugged in doesn't display anything at 
login screen

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1773484

Title:
  First bootup with external VGA monitor plugged in doesn't display
  anything at login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor

2018-05-28 Thread Christopher M. Penalver
Manfred Steiner, in order to finely scope this report on "one issue",
this report will only focus on the first time one boots up with the
external VGA monitor connected (no Beamer), and is at the login screen
(not after login).

Regarding the behavior above, what is reasonable is either, it does what
it did before in 16.04, or the monitor is properly detected and is in
mirror mode. Either way, one may login.

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

Title:
  First bootup with external VGA monitor plugged in doesn't display
  anything at login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773484/+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 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

2018-05-28 Thread Christopher M. Penalver
Krishnan Sreenivas:

Regarding using PPAs, PPAs are not supported in Ubuntu. Hence, if a PPA
is used, and it brakes the system, it is out of scope for a bug report.

In regard to the scope of this report, given the history of what changed
and how wasn't documented and provided, you kept making large,
unsupported, and undocumented changes after the break that appeared to
cause additional breakage, there isn't anything this report can be
scoped to. Hence, it is being closed.

Thank you again for taking the time to report this and helping to make
Ubuntu better. Please submit any future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+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 1773484] Re: Login screen not moved to used monitor

2018-05-27 Thread Christopher M. Penalver
Manfred Steiner:

1) What is "Beamer"? Is this a program available from the Ubuntu
repositories, a piece of hardware, etc.?

2) To clarify the table in #10, it appears the only part that isn't as
expected is how after configuring the Internal LCD to be off and VGA to
be active, you restart, and at the login screen the Internal LCD is
turned on, while the external VGA is not displaying. However, you are
expecting that the external VGA is on, while Internal LCD is off.
Correct?

To use your table to further clarify:

.. Connected ... Internal LCD ... VGA...GOOD?
-
First time ... Monitor on VGA .. L+S  E ... Yes
After Login .. Monitor on VGA .. S .. E ... Yes
After reconfiguration  Monitor on VGA .. Off  S ... Yes
After Restart  Monitor on VGA .. Off  L+S . Yes
After Login .. Monitor on VGA .. Off  S ... Yes
Restart with Beamer .. Beamer on VGA ... L+S  E ... No
Restart with Monitor . Monitor on VGA .. L+S  E ... No
After Login .. Monitor on VGA .. Off  S ... Yes

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

Title:
  Login screen not moved to used monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor

2018-05-27 Thread Christopher M. Penalver
Manfred Steiner:

1) When the display is set to mirror, at the login screen does it show
up on one monitor or both?

2) When the display is set to mirror, after you login does the system
bar show up on one monitor or both?

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

Title:
  Login screen not moved to used monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1768633] Re: desktop or window fallen over after standby

2018-05-27 Thread Christopher M. Penalver
Stefan Helmert, I do not see any visual imperfections in the screenshot
you most recently attached. Could you please advise?

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

Title:
  desktop or window fallen over after standby

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+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 1773484] Re: Login screen not moved to used monitor

2018-05-27 Thread Christopher M. Penalver
Manfred Steiner, with only the VGA monitor connected, and the output
sent to both the laptop internal monitor, and external monitor, could
you please provide a screenshot of the Settings > Devices > Display GUI
menu?

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

Title:
  Login screen not moved to used monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773575] Re: dual vga

2018-05-27 Thread Christopher M. Penalver
mustafa, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/comments/5
regarding this being resolved. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  dual vga

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

2018-05-27 Thread Christopher M. Penalver
mustafa:

1) Regarding crash files, you would not want to attach them, as they may
contain sensitive information you don't want to reveal publicly.

Instead, one may report them in a privacy respectful way via a terminal:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is the name of the crash file.

2) It is advised to immediately back up your data (config files, list of
what apps you have installed, etc.), so that in the event of a disaster
(hardware failure, OS stops working entirely, etc.) you may perform a
clean install and bring the OS back to the desired state. Stating "i do
not want to lose my server configuration and reinstall Ubuntu and all
the configuration and apps that i used" doesn't mean you won't have to
do it. This is a matter of how prepared are you if you must.

3) Post the results of the following terminal command:
history

4) To confirm a WORKAROUND, if you install the package gnome-session-
flashback and login to GNOME (Metacity), does this allow you to use the
GUI again?

** Attachment removed: 
"_usr_lib_x86_64-linux-gnu_unity_compiz-config-profile-setter.1000_copy.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/+attachment/5145036/+files/_usr_lib_x86_64-linux-gnu_unity_compiz-config-profile-setter.1000_copy.crash

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

Title:
  dual vga

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


  1   2   3   4   5   6   7   8   9   10   >