[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773087

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

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  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 

[Touch-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
** Attachment removed: "20190519-0814-CEST-apport.cups.k1bxh64q.apport"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829643/+attachment/5264742/+files/20190519-0814-CEST-apport.cups.k1bxh64q.apport

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

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

** Tags added: regression-potential

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1829643

Title:
  1 network printer + 3 configurations (copies) disappear

Status in cups package in Ubuntu:
  New

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID 

[Touch-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
FrankStefani, could you please run an apport-collect only once more to gather 
debugging information against the package cups:
apport-collect 1829643

** Package changed: linux (Ubuntu) => cups (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1829643

Title:
  1 network printer + 3 configurations (copies) disappear

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62
  DeviceURI 

[Touch-packages] [Bug 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread Christopher M. Penalver
FrankStefani, given the scope of this closed report was fixed in Ubuntu
10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to
do with your problem.

However, regarding the problem you are experiencing, it is most helpful if you 
use the computer the problem is reproducible with and file a new report by 
running the following from a terminal:
ubuntu-bug cups

Also, please feel free to subscribe me to it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/554172

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and 
either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the 
display shuts off, it will not wake up anymore, and the screen stays dark. A 
cycle of the following will leave the display dark:
  xset dpms force off; sleep 30; xset dpms force on

  WORKAROUND: A restart of the Xserver will bring back the display.

  WORKAROUND: Don't allow DPMS to switch off the display:
  xset dpms 0 0 0

  xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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

[Touch-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu

2019-02-05 Thread Christopher M. Penalver
Marko Muehlberg (markom2), would you be able to confirm the commit from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
is the root cause for your issue by testing a revert of it following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

** Description changed:

  It first appeared when I upgraded ubuntu studio to 18.04
  udevd started to use all available cpu.
- now I'm running ubuntu desktop from a usb key and it's still the same  
+ now I'm running ubuntu desktop from a usb key and it's still the same
  
  udevadm monitor returns:
  KERNEL[2512.539491] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.540201] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566574] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566866] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.567499] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594050] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594310] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.596510] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.620736] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.624606] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.634706] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  ...
  
+ WORKAROUND: Remove file:
+ /lib/udev/rules.d/97-hid2hci.rules
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.3
  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
  CasperVersion: 1.394
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Aug 20 18:54:48 2018
  ExecutablePath: /lib/systemd/systemd-udevd
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  MachineType: Dell Inc. Vostro 3300
  ProcEnviron:
-  LANG=C.UTF-8
-  PATH=(custom, no user)
+  LANG=C.UTF-8
+  PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3300
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

** Tags added: bios-outdated-a12 regression-release

** This bug is no longer a duplicate of bug 1759836
   systemd-udevd consumes 100% of CPU

** No longer affects: systemd (Ubuntu)

** 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788018

Title:
  udevd keeps binding and unbinding some usb device und uses all cpu

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It first appeared when I upgraded ubuntu studio to 18.04
  udevd started to use all available cpu.
  now I'm running ubuntu desktop from a usb key and it's still the same

  udevadm monitor returns:
  KERNEL[2512.539491] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.540201] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566574] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566866] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.567499] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594050] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594310] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.596510] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.620736] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  

[Touch-packages] [Bug 846873] Re: Certain text invisible in attached PDF file

2018-12-23 Thread Christopher M. Penalver
** Description changed:

+ Upstream reports:
+ https://bugzilla.gnome.org/show_bug.cgi?id=741681
+ https://gitlab.freedesktop.org/poppler/poppler/issues/153
+ 
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  
  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3) What is expected via 
https://launchpadlibrarian.net/79580879/ORelly-Running%20Linux%204th%20Edition.pdf
 is when one goes to page 58 of the book, at the bottom it shows the entire 
command, as it does in Adobe Reader:
  # fdisk /dev/hda
  
  4) What happens instead is it only shows:
  #
  
  WORKAROUND: Open with Chromium's built-in PDF viewer:
  apt-cache policy chromium-browser
  chromium-browser:
    Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Version table:
   *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   34.0.1847.116-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Sep 11 12:21:58 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  KernLog:
   Sep 11 10:06:44 mars kernel: [345609.072499] type=1400 
audit(1315721204.184:23): apparmor="STATUS" operation="profile_replace" 
name="/usr/bin/evince" pid=27132 comm="apparmor_parser"
   Sep 11 10:06:44 mars kernel: [345609.074807] type=1400 
audit(1315721204.184:24): apparmor="STATUS" operation="profile_replace" 
name="/usr/bin/evince-previewer" pid=27132 comm="apparmor_parser"
   Sep 11 10:06:44 mars kernel: [345609.076412] type=1400 
audit(1315721204.184:25): apparmor="STATUS" operation="profile_replace" 
name="/usr/bin/evince-thumbnailer" pid=27132 comm="apparmor_parser"
  ProcEnviron:
   LANGUAGE=ru:en
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: Upgraded to natty on 2011-04-15 (148 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/846873

Title:
  Certain text invisible in attached PDF file

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Upstream reports:
  https://bugzilla.gnome.org/show_bug.cgi?id=741681
  https://gitlab.freedesktop.org/poppler/poppler/issues/153

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected via 
https://launchpadlibrarian.net/79580879/ORelly-Running%20Linux%204th%20Edition.pdf
 is when one goes to page 58 of the book, at the bottom it shows the entire 
command, as it does in Adobe Reader:
  # fdisk /dev/hda

  4) What happens instead is it only shows:
  #

  WORKAROUND: Open with Chromium's built-in PDF viewer:
  apt-cache policy chromium-browser
  chromium-browser:
    Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Version table:
   *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   34.0.1847.116-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Sep 11 12:21:58 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  KernLog:
   Sep 11 10:06:44 mars kernel: [345609.072499] type=1400 
audit(1315721204.184:23): apparmor="STATUS" operation="profile_replace" 
name="/usr/bin/evince" pid=27132 comm="apparmor_parser"
   Sep 11 10:06:44 mars kernel: [345609.074807] type=1400 
audit(1315721204.184:24): apparmor="STATUS" operation="profile_replace" 

[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1554471

Title:
  Mouse not working

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have a Cougar 450M gaming mouse.  I am dual booting between Windows
  10 and Xubuntu.  The mouse works perfectly in Windows but fails
  dismally in any flavour of Ubuntu (tried Ubuntu, Lubuntu and Xubuntu)
  including during the OS installation phase.

  On very rare occasion it will work when I boot into Ubuntu, but 9 out
  of 10 times the only functions available are the mouse buttons and
  scroll wheel.

  There is also a DPI adjustment button on the 450M which cycles through
  the various available settings and changes colour based on the current
  DPI setting.  I have noted that if you press the button once, the
  button changes colour as expected, but if you continue to press the
  button, nothing happens.  It seems to freeze on that setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  8 10:52:02 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 
/ R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2730]
  InstallationDate: Installed on 2016-03-03 (4 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  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.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Mar  8 10:48:41 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  After updating the Ubuntu HWE stack in 14.04 to Xenial (kernel 4.4 and
  xserver-xorg-video-radeon-lts-xenial), system boots up fine and
  responsively, but screen is laggy; there is a tremendous performance
  regression in comparison to xorg-lts-vivid. Lots of video tearing that
  did not occur when using xserver-xorg-video-radeon-lts-vivid.

  System is an older Pentium laptop (Packard Bell EasyNote) with a Radeon 
Xpress 200M chip (r300 driver). Video acceleration was working with DRI2 under 
the Vivid stack (kernel 3.19-64-lowlatency + 
xserver-xorg-video-radeon-lts-vivid).
  I also tried upgrading to the Wily kernel (4.2.0-lowlatency), and video 
acceleration works fine with the Vivid xorg.

  I reported this in launchpad previously, and it was dismissed as "invalid" 
since Wily is EOL.
  The problem, however, persists in the Xenial stack, so I'm reporting it here.

  Attached are the respective Xorg.0 logs.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 247113] Re: Bars show with wrong thickness

2018-08-25 Thread Christopher M. Penalver
** No longer affects: poppler (Ubuntu)

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

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

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

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

** Description changed:

+ Upstream URL:
+ https://gitlab.freedesktop.org/poppler/poppler/issues/279
+ 
  Binary package hint: evince
  
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  
  2) apt-cache policy evince
  evince:
-   Installed: 3.14.1-0ubuntu1
-   Candidate: 3.14.1-0ubuntu1
-   Version table:
-  *** 3.14.1-0ubuntu1 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.14.1-0ubuntu1
+   Candidate: 3.14.1-0ubuntu1
+   Version table:
+  *** 3.14.1-0ubuntu1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3) What is expected to happen is when one creates the following PDF
  attachment (
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/247113/+attachment/316292/+files/sample.pdf
  ) via Lilypond, the bars look as they do in Adobe Reader.
  
  4) what happens instead is that some of the bars are the wrong thikcness as 
per the screenshot:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/247113/+attachment/316293/+files/comparison.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/247113

Title:
  Bars show with wrong thickness

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Upstream URL:
  https://gitlab.freedesktop.org/poppler/poppler/issues/279

  Binary package hint: evince

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one creates the following PDF
  attachment (
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/247113/+attachment/316292/+files/sample.pdf
  ) via Lilypond, the bars look as they do in Adobe Reader.

  4) what happens instead is that some of the bars are the wrong thikcness as 
per the screenshot:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/247113/+attachment/316293/+files/comparison.png

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 245620] Re: evince and selection on rotated text

2018-08-21 Thread Christopher M. Penalver
** No longer affects: poppler (Ubuntu)

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

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

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

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

** Description changed:

+ Upstream URL:
+ https://gitlab.freedesktop.org/poppler/poppler/issues/499
+ 
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  
  2) apt-cache policy evince
  evince:
-   Installed: 3.14.1-0ubuntu1
-   Candidate: 3.14.1-0ubuntu1
-   Version table:
-  *** 3.14.1-0ubuntu1 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.14.1-0ubuntu1
+   Candidate: 3.14.1-0ubuntu1
+   Version table:
+  *** 3.14.1-0ubuntu1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3) What is expected to happen via the attached document is that one may 
highlight the text that has been rotated at a 45 degree angle, one row at a 
time, just like Adobe Reader 10.x:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/245620/+attachment/314937/+files/m1.pdf
  
  4) What happens instead is it highlights parts of the line, along with 
others, as per the attached screenshot:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/245620/+attachment/314936/+files/Capture-1.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/245620

Title:
  evince and selection on rotated text

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Upstream URL:
  https://gitlab.freedesktop.org/poppler/poppler/issues/499

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via the attached document is that one may 
highlight the text that has been rotated at a 45 degree angle, one row at a 
time, just like Adobe Reader 10.x:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/245620/+attachment/314937/+files/m1.pdf

  4) What happens instead is it highlights parts of the line, along with 
others, as per the attached screenshot:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/245620/+attachment/314936/+files/Capture-1.png

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 164233] Re: [Upstream] Exporting pdf from LibreOffice with smooth gradient displays striped in Evince, shows correctly in Adobe Reader

2018-08-21 Thread Christopher M. Penalver
** No longer affects: cairo (Ubuntu)

** Project changed: libcairo => cairo (Ubuntu)

** Changed in: cairo (Ubuntu)
   Importance: Medium => Undecided

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

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

** No longer affects: cairo (Ubuntu)

** Project changed: evince => cairo (Ubuntu)

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

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

** Changed in: cairo (Ubuntu)
 Remote watch: GNOME Bug Tracker #656614 => None

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

** Description changed:

+ Upstream URL:
+ https://gitlab.freedesktop.org/poppler/poppler/issues/626
+ 
  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04
  
  2) apt-cache policy evince
  evince:
    Installed: 2.32.0-0ubuntu12.2
    Candidate: 2.32.0-0ubuntu12.2
    Version table:
   *** 2.32.0-0ubuntu12.2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.32.0-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  
  3) What is expected in Impress via the Terminal:
  
  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/164233/+attachment/2281555/+files/example.odp
  && loimpress -nologo example.odp
  
  export the file with Gradient 1 inserted into the background to pdf (
  
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/164233/+attachment/2281556/+files/example.pdf
  ), open the pdf with Evince and it looks as it does in both Impress and
  Adobe Reader.
  
  4) What happens instead is Evince shows a striped gradient.
  
  WORKAROUND: Open with chromium-browser or chrome built-in PDF reader
  (not Firefox).
  
  Use Adobe Reader.
  
  apt-cache policy acroread
  acroread:
    Installed: 9.4.2-0natty1
    Candidate: 9.4.2-0natty1
    Version table:
   *** 9.4.2-0natty1 0
  500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages
  100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/164233

Title:
  [Upstream] Exporting pdf from LibreOffice with smooth gradient
  displays striped in Evince, shows correctly in Adobe Reader

Status in cairo package in Ubuntu:
  New

Bug description:
  Upstream URL:
  https://gitlab.freedesktop.org/poppler/poppler/issues/626

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy evince
  evince:
    Installed: 2.32.0-0ubuntu12.2
    Candidate: 2.32.0-0ubuntu12.2
    Version table:
   *** 2.32.0-0ubuntu12.2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.32.0-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected in Impress via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/164233/+attachment/2281555/+files/example.odp
  && loimpress -nologo example.odp

  export the file with Gradient 1 inserted into the background to pdf (
  
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/164233/+attachment/2281556/+files/example.pdf
  ), open the pdf with Evince and it looks as it does in both Impress
  and Adobe Reader.

  4) What happens instead is Evince shows a striped gradient.

  WORKAROUND: Open with chromium-browser or chrome built-in PDF reader
  (not Firefox).

  Use Adobe Reader.

  apt-cache policy acroread
  acroread:
    Installed: 9.4.2-0natty1
    Candidate: 9.4.2-0natty1
    Version table:
   *** 9.4.2-0natty1 0
  500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 594205] Re: Evince cannot select one column in a two column PDF

2018-08-21 Thread Christopher M. Penalver
** No longer affects: poppler

** Description changed:

+ Upstream URL:
+ https://gitlab.freedesktop.org/poppler/poppler/issues/409
+ 
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  
  2)  apt-cache policy libpoppler[0-9]
  libpoppler47:
    Installed: 0.28.1-1ubuntu1
    Candidate: 0.28.1-1ubuntu1
    Version table:
   *** 0.28.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  
  apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3) What is expected to happen via
  https://launchpadlibrarian.net/53980611/Example.pdf is one is able to
  highlight one column at a time, just like in Adobe Reader.
  
  4) What happens instead is it highlights both columns at a time.
  
  WORKAROUND: Open with Chromium's built-in PDF reader:
   apt-cache policy chromium-browser
  chromium-browser:
    Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Version table:
   *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   34.0.1847.116-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/594205

Title:
  Evince cannot select one column in a two column PDF

Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Upstream URL:
  https://gitlab.freedesktop.org/poppler/poppler/issues/409

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2)  apt-cache policy libpoppler[0-9]
  libpoppler47:
    Installed: 0.28.1-1ubuntu1
    Candidate: 0.28.1-1ubuntu1
    Version table:
   *** 0.28.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via
  https://launchpadlibrarian.net/53980611/Example.pdf is one is able to
  highlight one column at a time, just like in Adobe Reader.

  4) What happens instead is it highlights both columns at a time.

  WORKAROUND: Open with Chromium's built-in PDF reader:
   apt-cache policy chromium-browser
  chromium-browser:
    Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064
    Version table:
   *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   34.0.1847.116-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1787651

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm experiencing a problem using a Jabra Evolve 65. When using the usb
  bluetooth dongle every time a sound is reproduced the mouse stops
  clicking.

  When i'm using the Jabra USB cable instead, it works correclty

  Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-lowlatency 4.10.3
  Uname: Linux 4.10.0-14-lowlatency 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: None
  CurrentDesktop: GNOME
  Date: Fri Aug 17 17:32:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2245]
  InstallationDate: Installed on 2016-04-24 (845 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20HES4KF02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-lowlatency 
root=/dev/mapper/vg_ldt-lv_root ro resume=/dev/mapper/vg_ldt-lv_swap
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES4KF02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET68W(1.43):bd11/10/2017:svnLENOVO:pn20HES4KF02:pvrThinkPadT470:rvnLENOVO:rn20HES4KF02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HES4KF02
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  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.7
  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: Fri Aug 17 15:57:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4157 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  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

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  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
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  // 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") 

[Touch-packages] [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 

[Touch-packages] [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
Touch seeded packages, 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)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // 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 

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-07-31 Thread Christopher M. Penalver
Vinícius Milanez Couto, in order to allow additional upstream mainline kernel 
developers to examine the issue, at your earliest convenience, could you please 
test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Project changed: bluez => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #199035 => None

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

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

** Tags added: bios-outdated-a15 regression-potential

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759836

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  // 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" 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  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 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  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: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  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:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 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:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  

[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1771539

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  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.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1771539

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  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.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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.
-  

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  New

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  WORKAROUND: Use GNOME Flashback (Metacity).

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  WORKAROUND: Use GNOME Flashback (Metacity).

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1770166

Title:
  The brightness of the notebook

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The brightness of the notebook does not lower or rise with the FN key. Acer 
Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0487]
  InstallationDate: Installed on 2018-06-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Aspire 5742
  Package: xorg 1:7.7+19ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.18
  dmi.modalias: 
dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5742
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging

2018-06-13 Thread Christopher M. Penalver
Nando, in addition to providing the test results from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/comments/4
:

1) As per TP-Link there are three versions of this device https://www
.tp-link.com/us/download/TL-WN722N.html. Which version do you have?

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

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

4) If you boot into a live environment (not text only) from 
http://cdimage.ubuntu.com/daily-live/current/ could you please provide 
debugging information by running the following in a terminal:
apport-collect 1775230

** No longer affects: network-manager (Ubuntu)

** Tags removed: tp-link usb wireless
** Tags added: needs-upstream-testing

** 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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1775230

Title:
  TP-LINK TL-WN722N causes 100% CPU usage due to  trace logging

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK
  TL-WN722N into the USB port, the CPU usage goes to 100%, and there are
  multiple reports of "stack traces" in dmesg.

  The attached snippet repeats multiple consecutive times in the dmesg
  output (albeit with a different trace id).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop

2018-06-11 Thread Christopher M. Penalver
Markus Baumann, thank you for reporting this and helping make Ubuntu
better.

1) To clarify, if you don't adjust the MTU does the LAN network still
connection cycle?

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?

** Tags added: bios-outdated-2.72 regression-release

** No longer affects: network-manager (Ubuntu)

** 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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash 

[Touch-packages] [Bug 1757561] Re: Wifi disconnects randomly under ubuntu 17.10

2018-06-11 Thread Christopher M. Penalver
Mijail Febres Soria, 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?

** No longer affects: network-manager (Ubuntu)

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

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

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087454/+files/RfKill.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087453/+files/PulseList.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087451/+files/ProcInterrupts.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087450/+files/ProcEnviron.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087452/+files/ProcModules.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087448/+files/PciNetwork.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087447/+files/NetworkManager.conf.txt

** Attachment removed: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087446/+files/NetDevice.wlp3s0.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087449/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087445/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.enp4s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087444/+files/NetDevice.enp4s0.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087441/+files/JournalErrors.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087440/+files/IwConfig.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087443/+files/Lsusb.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087442/+files/Lspci.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087438/+files/Dependencies.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087436/+files/CRDA.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087437/+files/CurrentDmesg.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087435/+files/AlsaInfo.txt

** Attachment removed: "nmcli-con.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087422/+files/nmcli-con.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087421/+files/WifiSyslog.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087419/+files/RfKill.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087420/+files/UdevDb.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087417/+files/ProcModules.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087416/+files/ProcInterrupts.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087415/+files/ProcEnviron.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087418/+files/PulseList.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087414/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087413/+files/PciNetwork.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087412/+files/NetworkManager.conf.txt

** Attachment removed: "NetDevice.wlp3s0.txt"
   

[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1771539

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  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.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1771539

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  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.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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 

[Touch-packages] [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
  

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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
     

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

  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

  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]
  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.
  

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

  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

  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]
  InstallationDate: Installed on 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

  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

  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]
  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: 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-06-01 Thread Christopher M. Penalver
Log in to Ubuntu (i.e. GNOME xorg) > double click
GS5007-GettingStartedWithDraw.odt > click Edit > Track Changes > Compare
Document... > highlight GS4207-GettingStartedWithDraw.odt > click button
Open > in window Manage Changes click button Close > File > Save As... >
in textbox Name GS5007-GettingStartedWithDraw-v2 > click button Save >
window pops up titled LibreOffice 6.0 Document Recovery with text "Due
to an unexpected error, LibreOffice crashed." but no files in /var/crash
generated by apport. However, apport does create crash files following
steps in
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/comments/7
so crash files not being being generated is dependent how LO crashes,
not always if LO crashes.

** Attachment added: "no-apport-crash-files-generated.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147686/+files/no-apport-crash-files-generated.PNG

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-06-01 Thread Christopher M. Penalver
2 of 2 reproduction documents for Bionic.

** Attachment added: "GS4207-GettingStartedWithDraw.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147685/+files/GS4207-GettingStartedWithDraw.odt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-06-01 Thread Christopher M. Penalver
1 of 2 reproduction documents for Bionic.

** Attachment added: "GS5007-GettingStartedWithDraw.odt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1537566/+attachment/5147684/+files/GS5007-GettingStartedWithDraw.odt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  New

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1094150] Re: Apport message makes no sense: The problem cannot be reported: The problem happened with the program /usr/lib/libreoffice/program/soffice.bin which changed since the

2018-05-30 Thread Christopher M. Penalver
** Attachment removed: "example.zip"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1094150/+attachment/3469321/+files/example.zip

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1094150

Title:
  Apport message makes no sense: The problem cannot be reported: The
  problem happened with the program
  /usr/lib/libreoffice/program/soffice.bin which changed since the crash
  occurred.

Status in apport package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  2) apt-cache policy apport
  apport:
Installed: 2.6.1-0ubuntu9
Candidate: 2.6.1-0ubuntu9
Version table:
   *** 2.6.1-0ubuntu9 0
  900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.6.1-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages

  3) What happens is when one types at a terminal:
  cd ~/Desktop && wget -c 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1074834/+attachment/3469304/+files/1074834_1-3.6.2%7Erc2-0ubuntu4.crash.zip
 -O example.zip && file-roller -h example.zip && ubuntu-bug 
_usr_lib_libreoffice_program_soffice.bin.1000.crash

  a window pops up noting:
  Sorry, Ubuntu 12.10 has experienced an internal error.
  If you notice further problems, try restarting the computer.
  (CHECKED) Send an error report to help fix this problem
  (UNCHECKED) Ignore future problems of this type

  click button Continue and one is able to file a new report.

  4) What happens instead is one gets a pop up window noting:
  The problem cannot be reported:
  The problem happened with the program 
/usr/lib/libreoffice/program/soffice.bin which changed since the crash occurred.

  However, as per the crash report, it was filed Dec. 28 2012 against
  the newest LO 3.6.2~rc2-0ubuntu4, and as per
  https://launchpad.net/ubuntu/+source/libreoffice Quantal LO updates
  hasn't changed since 2012-11-19. So, the pop up window makes no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apport 2.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportLog:
   
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  CheckboxSubmission: 30b6638832e19720cfe8f7a91e5798a4
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  Date: Thu Dec 27 17:15:55 2012
  InstallationDate: Installed on 2012-06-11 (199 days ago)
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120131.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to quantal on 2012-09-14 (104 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2012-11-30T17:05:21.362240

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1262915] Re: apport-gtk crashed with ValueError in _apt_pkg(): package acroread-bin does not exist

2018-05-30 Thread Christopher M. Penalver
I don't use 14.04, would never install EOL acroread, and issue was only
reproducible against EOL acroread.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1262915

Title:
  apport-gtk crashed with ValueError in _apt_pkg(): package acroread-bin
  does not exist

Status in apport package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  2) apt-cache policy apport-gtk
  apport-gtk:
Installed: 2.12.7-0ubuntu2
Candidate: 2.12.7-0ubuntu2
Version table:
   *** 2.12.7-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen if one installs
  
ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.5.5/enu/AdbeRdr9.5.5-1_i386linux_enu.deb

  acroread
  Segmentation fault (core dumped)

  and attempts to file a report against it, apport-gtk doesn't crash.

  4) What happens is it does.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.12.7-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:1000:116:820823:2013-12-19 16:53:09.824448585 -0600:2013-12-19 
16:53:10.824448585 
-0600:/var/crash/_opt_Adobe_Reader9_Reader_intellinux_bin_acroread.1000.crash
   640:1000:116:56516:2013-12-19 16:53:16.724448442 -0600:2013-12-19 
16:53:17.724448442 -0600:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  Date: Thu Dec 19 16:53:17 2013
  ExecutablePath: /usr/share/apport/apport-gtk
  ExecutableTimestamp: 1386690210
  InstallationDate: Installed on 2013-12-19 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131219)
  InterpreterPath: /usr/bin/python3.3
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcCwd: /home/moniker
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/apport/apport-gtk']
  SourcePackage: apport
  Title: apport-gtk crashed with ValueError in _apt_pkg(): package acroread-bin 
does not exist
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

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

- What was expected to happen is when LibreOffice crashes in Xenial, it
- logs a crash report to file against to errors.ubuntu.com.
+ What is expected to happen is when LibreOffice crashes, a crash report
+ is created in the /var/crash folder.
  
- What happened instead is LibreOffice crashed but apport didn't log a
- crash file in /var/crash despite being enabled. Other programs that
- crash are picked up by apport so appears LO+apport issue.
+ What happened instead is LibreOffice crashed but apport didn't create a
+ crash file in the /var/crash folder, despite running and being enabled.
+ Apport creating crash files in /var/crash used to happen in Xenial, and
+ in prior releases. Other programs that crash are picked up by apport so
+ appears LO+apport issue.
+ 
+ LibreOffice has reference to placing crash files as per:
+ cat /etc/libreoffice/sofficerc | grep crash
+ CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash
  
  I don't have any 3rd party LO plugins installed.
  
- apt-show-versions -r libreoffice* 
+ apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed
  
  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1
  
  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs
  
  default = 'ubuntu'
  
  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor
  
  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None
  
  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

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

-- 
You received this bug notification because 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-05-30 Thread Christopher M. Penalver
Confirmed in Bionic. What happens in Windows is that it offers to send a
crash report to https://crashreport.libreoffice.org/, where one may then
input the crash ID in to review the stack trace.

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What was expected to happen is when LibreOffice crashes in Xenial, it
  logs a crash report to file against to errors.ubuntu.com.

  What happened instead is LibreOffice crashed but apport didn't log a
  crash file in /var/crash despite being enabled. Other programs that
  crash are picked up by apport so appears LO+apport issue.

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice* 
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-05-30 Thread Christopher M. Penalver
Issue also happening in Artful as per:
https://bugs.launchpad.net/bugs/1772425

** Tags added: artful

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What was expected to happen is when LibreOffice crashes in Xenial, it
  logs a crash report to file against to errors.ubuntu.com.

  What happened instead is LibreOffice crashed but apport didn't log a
  crash file in /var/crash despite being enabled. Other programs that
  crash are picked up by apport so appears LO+apport issue.

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice* 
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-05-30 Thread Christopher M. Penalver
Adding Apport (Ubuntu) in case this is due to Apport not working
correctly, changes would need to happen in LO+Apport, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1537566

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What was expected to happen is when LibreOffice crashes in Xenial, it
  logs a crash report to file against to errors.ubuntu.com.

  What happened instead is LibreOffice crashed but apport didn't log a
  crash file in /var/crash despite being enabled. Other programs that
  crash are picked up by apport so appears LO+apport issue.

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice* 
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [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
Touch seeded packages, 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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  New

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  New

Bug description:
  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 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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") 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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)
  

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  New

Bug description:
  If I boot up with two external 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  New

Bug description:
  If I boot up with two external monitors connected, the login screen
  doesn't show up on any monitor.

  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.

  WORKAROUND: Use Trusty.

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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 

[Touch-packages] [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
Touch seeded packages, 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.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773612

Title:
  I am just loading the OS onto my computer

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am not sure yet on all this

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 19:42:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. NV44 [GeForce 6200 TurboCache] [1043:81d5]
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release i386 
(20180228)
  MachineType: Dell Inc. OptiPlex GX620
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=12a1802d-2e8f-4134-abe3-6ced79d9f318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8098
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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  

[Touch-packages] [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
Touch seeded packages, 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.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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: 

[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772917

Title:
  cannot maximize window

Status in unity package in Ubuntu:
  New

Bug description:
  I set auto hide Launcher,but when I do this,I cannot maximize window:the 
window cannot cover the launcher area
  my english is not very well,if you can understand Chinese ,pls read the 
follow Chinese words:
  我设置了启动器自动隐藏,而且启动器也自动隐藏了,但是最大化窗口的时候发现当前窗口并不能完全最大化:最大化的窗口不会覆盖启动器区域

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-127.153~14.04.1-generic 4.4.128
  Uname: Linux 4.4.0-127-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 23 21:09:25 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 
XT] [1002:94c8] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:012b]
  InstallationDate: Installed on 2018-04-30 (22 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  MachineType: Acer Aspire 4920
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=d3655307-16da-4f7c-8a4a-1037c602bd35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.20
  dmi.board.name: Tahoe
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.20:bd02/01/2008:svnAcer:pnAspire4920:pvr0100:rvnAcer:rnTahoe:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 4920
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May 23 20:59:07 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773015

Title:
  appli Notes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Bug.Does not start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 23 22:39:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mullins [Radeon R4/R5 Graphics] [17aa:3808]
  InstallationDate: Installed on 2017-08-11 (285 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80UM
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=a61d7236-19c8-4add-9fcb-be6756ebdfeb ro plymouth:debug 
vesafb.invalid=1 drm.debug=0xe nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Lenovo
  dmi.bios.version: 1QCN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 7E1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-17ACL
  dmi.modalias: 
dmi:bvnLenovo:bvr1QCN32WW:bd08/18/2016:svnLENOVO:pn80UM:pvrLenovoideapad110-17ACL:rvnLENOVO:rnNano7E1:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad110-17ACL:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UM
  dmi.product.version: Lenovo ideapad 110-17ACL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May 23 10:29:30 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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.

  This monitor configuration worked fine with this computer in 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`.

  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]
  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
  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

To manage notifications about this bug go 

[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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.

  This monitor configuration worked fine with this computer in 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`.

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773744

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773516

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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.

  What happens instead is that the login screen is only shown on the
  built-in screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: 

[Touch-packages] [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
Touch seeded packages, 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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  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.

  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]
  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
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773484/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  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'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  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.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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1768633

Title:
  desktop or window fallen over after standby

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  after wake up from standby the screen was flickering and a window was
  fallen over

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  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: Wed May  2 21:04:50 2018
  DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  MachineType: LENOVO 2441CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago)
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2441CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2441CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Wed May  2 20:59:06 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -2
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4589 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp



[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773575

Title:
  dual vga

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C46Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 N/A
  xserver.bootTime: Tue May 22 09:07:33 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 927 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773575

Title:
  dual vga

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C46Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 N/A
  xserver.bootTime: Tue May 22 09:07:33 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 927 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773516] Re: Right click not working on Lenovo touchpad

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

1) To clarify, how are you attempting to right click, tapping two
fingers on the clickpad, clicking the bottom right area of the clickpad?

2) If you boot into a kernel from 17.10 does right clicking work again?

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

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

** Summary changed:

- Right click not working on Lenovo touchpad
+ [Lenovo Yoga 300-11IBY] Right click not working

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773516

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773516] Re: Right click not working on Lenovo touchpad

2018-05-26 Thread Christopher M. Penalver
** Tags added: latest-bios-c0cn31ww

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773516

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773531] Re: graphics driver incssat728onsisten

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

1) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

If after HWE stack updating this issue is still reproducible:

2) Could you please provide a screenshot of the issue?

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

** Tags added: bios-outdated-a07

** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773531

Title:
  graphics driver incssat728onsisten

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  VGA driver is inconsistent. Most of the probable boot up goes with
  flickering and failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Sat May 26 14:42:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02cf]
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 1440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0K138P
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1440
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773544] Re: some bug you should see

2018-05-26 Thread Christopher M. Penalver
Mário Luiz Mendes de Araujo Junior, thank you for taking the time to
report this and helping to make Ubuntu better. Unfortunately, this
report didn't include enough information. You may find it helpful to
read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem,
2. The behavior you expected, and
3. The behavior you actually encountered (in as much detail as possible).

Thank you for your help.

** Tags added: bios-outdated-1.2.7

** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773544

Title:
  some bug you should see

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  some bug you should see

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  Date: Sat May 26 11:34:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2018-05-20 (6 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 004: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7c6c9274-21e1-4431-a45a-58d29ca5b059 ro acpi=off quiet splash 
nvidia-drm.modeset=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0P2WW4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/16/2017:svnDellInc.:pnInspiron7559:pvr1.2.3:rvnDellInc.:rn0P2WW4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
   
   
   ERROR: Error querying connected displays on GPU 0 (Missing Extension).
  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.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
  xserver.bootTime: Sun May 20 22:26:41 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773575] Re: dual vga

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

1) Regarding your Bug Description:
>"i tried to update the drivers in one way or another..."

This is not enough information. Could you please advise what you did
precisely, in a keyboard click-for-click fashion?

2) Are there any crash files in the /var/crash folder?

3) As per your logs, you install unsupported software (PPA) and have
installed the nvidia proprietary drivers when you don't have a nvidia
card installed. Hence, after removing all PPAs and the nvidia drivers,
and rebooting does this allow you to use the GUI?

** Tags added: latest-bios-a14

** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773575

Title:
  dual vga

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C46Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 N/A
  xserver.bootTime: Tue May 22 09:07:33 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 927 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

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

To advise, this report will only be scoped to one issue. With this in mind, in 
this report you have noted the following disparate problems:
1) As per your Bug Description, going from 16.04 to 18.04, where the monitor 
the login screen and system bar shows up on changed from where the cursor the 
monitor is on while booting up to the main monitor.
2) As per comment #3: "but does not help the first time, when no configuration 
was done".
3) As per comment #3: (or it falls back to the starting situation).
4) As per comment #3, going from 16.04 to 18.04, the monitor connected through 
the i-tec adapter is not automatically detected, requiring you to have the 
connect the i-tec adapter while the displays dialog is open.
5) As per comment #3: "A second minor problem when using this adapter is a 
mouse flickering effect."

Of the 5 disparate issues above, which one issue did you want this
report to focus on?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1596248] Re: [Dell XPS 13 9343] Touchpad stops working occasionally

2018-05-26 Thread Christopher M. Penalver
Kevin Dalley, thank you for reporting this and helping make Ubuntu
better. Please advise to all of the following:

1) To clarify, you regarding your self-compiled xserver-xorg-input-
synaptics, is that considered a WORKAROUND to the scope of this report?
If so, could you please provide the steps precisely you used in this
report (not provide a URL)?

2) Regarding your Bug Description "Occasionally, my cursor stops
following my mouse movements.":

2a) How often is occasionally, once a minute, once a day, etc.?

2b) Does this issue happen when using an external USB mouse?

2c) Is this issue influenced by how many fingers you have on the
touchpad, where on the touchpad you touch, what gesture you are using,
etc.?

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?

** Summary changed:

- Touchpad stops working occasionally
+ [Dell XPS 13 9343] Touchpad stops working occasionally

** Tags added: latest-bios-a15

** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1596248

Title:
  [Dell XPS 13 9343] Touchpad stops working occasionally

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, my cursor stops following my mouse movements.

  I followed instructions described here:

  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in 
the kernel itself and you should follow these steps:
  Provide the general information.

  Directly after logging in to GNOME, KDE, or Xfce open a terminal and
  enter the following commands:

  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log 
  Wait until your touchpad stops working.
  Open a Virtual Terminal by pressing Ctrl-Alt-F1.
  Enter the following commands:

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff 
  Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, 
~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 17:57:40 2016
  DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-05-18 (404 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  LightdmLog:
   [+7057.65s] DEBUG: Seat seat0 changes active session to 
   [+7063.85s] DEBUG: Seat seat0 changes active session to 40
   [+7145.78s] DEBUG: Seat seat0 changes active session to c7
   [+7145.78s] DEBUG: Session c7 is already active
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Christopher M. Penalver
Kevin Dalley:

1) To advise, you will not want to manually attach crash reports. This
is due to how they may contain sensitive information you would not want
to release publicly.

2) Regarding those crash reports, in order to process them automatically and in 
a privacy respectful way, it is best to execute the following via a terminal on 
each crash report:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is replaced with the actual file name.

3) Regarding i915.i915_enable_rc6=1 could you please advise to:
* Why you were using it to begin with?
* Now that you removed it, do you have more/less/same issues?

4) To rule out left over update cruft and self-compiled programs, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?

** Attachment removed: 
"/var/crash/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144845/+files/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash

** Attachment removed: "/var/crash/_usr_sbin_unity-greeter.119.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144823/+files/_usr_sbin_unity-greeter.119.crash

** Attachment removed: "/var/crash/_usr_bin_xfce4-power-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144822/+files/_usr_bin_xfce4-power-manager.1000.crash

** Attachment removed: "/var/crash/_usr_bin_plasmashell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144821/+files/_usr_bin_plasmashell.1000.crash

** Attachment removed: "/var/crash/_usr_bin_kwin_wayland.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144820/+files/_usr_bin_kwin_wayland.1000.crash

** Attachment removed: "/var/crash/_usr_bin_ksplashqml.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144819/+files/_usr_bin_ksplashqml.1000.crash

** Description changed:

  I can manually start lightdm, and that will give me a login screen,
  
  Unfortunately, most of the desktop environments crash after login.
  
  Only plasma gives me a little bit of clients, though even plasma
  complains
  
  All shell packages missing
  And
  Vboxclient warning
  
  Under 17.10, I successfully used Wayland
+ 
+ WORKAROUND: Use GNOME Flashback (Metacity).
  
  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Dell HD Graphics 5500 [1028:0665]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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: 

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-26 Thread Christopher M. Penalver
Frank Winklmeier, it will help immensely if you use 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
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1770374] Re: My login screen stays black

2018-05-26 Thread Christopher M. Penalver
Dieter Meyer, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770374/comments/3
regarding this being resolved with a reinstall. 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1770374

Title:
  My login screen stays black

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I can't login to my desktop cause my login screen is black. So I read
  on the forums that you could bypass the login screen by typing startx
  in the tty screen but that also doesn't work please could help me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 12:02:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.13.0-38-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 2nd Generation Core Processor Family 
Integrated Graphics Controller [1558:2500]
   NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0ded] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CLEVO/KAPOK Computer GF108M [GeForce GT 520M] [1558:2500]
  InstallationDate: Installed on 2018-02-27 (72 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  MachineType: GIGABYTE Q1532N
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=8f567cdc-b8e0-4a0f-b10b-1104f687f111 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Q1532N
  dmi.board.vendor: GIGABYTE
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/15/2011:svnGIGABYTE:pnQ1532N:pvrN/A:rvnGIGABYTE:rnQ1532N:rvrN/A:cvnGIGABYTE:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Q1532N
  dmi.product.version: N/A
  dmi.sys.vendor: GIGABYTE
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

2018-05-26 Thread Christopher M. Penalver
Manfred Steiner, thank you for reporting this and helping make Ubuntu
better.

1) Regarding the VGA monitor, 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 manufacturer and model?

2) Regarding the i-tec USB 3.0 Display Adapter could you please advise
to the full part number (ex. U3DUAL4KHDMI)?

3) Regarding the HDMI monitor, could you please provide the full
manufacturer and model?

4) If you unplug the i-tec device, and only use the VGA monitor, is this
detected in Settings > Devices > Displays? An alternative application to
this is arandr to rule out some app specific issue.

** 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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Christopher M. Penalver
Kevin Dalley, thank you for reporting this and helping make Ubuntu
better.

1) Regarding non-default kernel boot parameter i915.i915_enable_rc6=1 is
this required? If you remove it, how does it affect this issue?

2) After you login, are there crash files in the /var/crash folder?

3) To confirm, if you install gnome-session-flashback and login to it
does this provide a WORKAROUND?

4) Do you have any self-compiled/unsupported software installed?

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1773484

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  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.

  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

  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]
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-05-26 Thread Christopher M. Penalver
Roger Davis, could you please answer all the question previously asked
directly here in this report (not make duplicate reports or apport-
collect to this one)?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  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

  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

  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]
  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
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  

  1   2   3   4   5   6   7   8   9   10   >