[Touch-packages] [Bug 1800587] Re: gnome shell crashes, dock visible in lookscreen

[Kilian Pfeiffer]

** Attachment added: "picture of dock in lockscreen"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1800587/+attachment/5207036/+files/Screenshot%20from%202018-10-24%2011-23-03.png

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

Title:
  gnome shell crashes, dock visible in lookscreen

Status in apport package in Ubuntu:
  New

Bug description:
  gnome shell sometimes "crashes", especially when system auto locks.
  The user theme shell extension disappears (standard ui then) and the
  dock gets partly unresponsive and does not disappears. When the system
  is locked, the dock is still visible and one can launch programs,
  which are not visible but still started. Sometimes it seems like two
  gnome-shell guis are overlapping each other.

  I am using a gtk+ theme: https://github.com/nivekxyz/afflatus

  There is no crash file for gnome-shell in /var/crash.
  My whoopsi ID is: 
https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918

  Description:  Ubuntu 18.10
  Release:  18.10

  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1
    Version table:
   *** 3.30.1-2ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  This bug might be close to https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1799242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1800587/+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 1800587] [NEW] gnome shell crashes, dock visible in lookscreen

[Kilian Pfeiffer]

Public bug reported:

gnome shell sometimes "crashes", especially when system auto locks. The
user theme shell extension disappears (standard ui then) and the dock
gets partly unresponsive and does not disappears. When the system is
locked, the dock is still visible and one can launch programs, which are
not visible but still started. Sometimes it seems like two gnome-shell
guis are overlapping each other.

I am using a gtk+ theme: https://github.com/nivekxyz/afflatus

There is no crash file for gnome-shell in /var/crash.
My whoopsi ID is: 
https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918

Description:Ubuntu 18.10
Release:18.10

gnome-shell:
  Installed: 3.30.1-2ubuntu1
  Candidate: 3.30.1-2ubuntu1
  Version table:
 *** 3.30.1-2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

This bug might be close to https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1799242

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

** Attachment added: "log.txt"
   https://bugs.launchpad.net/bugs/1800587/+attachment/5207035/+files/log.txt

** Description changed:

  gnome shell sometimes "crashes", especially when system auto locks. The
  user theme shell extension disappears and the dock gets partly
  unresponsive and does not disappears. When the system is locked, the
  dock is still visible and one can launch programs, which are not visible
  but still started. Sometimes it seems like two gnome-shell guis are
  overlapping each other.
  
- There is no crash file for gnome-shell in /var/crash. 
+ There is no crash file for gnome-shell in /var/crash.
  My whoopsi ID is: 
https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918
  
  Description:  Ubuntu 18.10
  Release:  18.10
  
- This bug might be close to https://bugs.launchpad.net/ubuntu/+source
- /gnome-shell/+bug/1799242
+ gnome-shell:
+   Installed: 3.30.1-2ubuntu1
+   Candidate: 3.30.1-2ubuntu1
+   Version table:
+  *** 3.30.1-2ubuntu1 500
+ 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ 
+ 
+ This bug might be close to 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799242

** Description changed:

  gnome shell sometimes "crashes", especially when system auto locks. The
- user theme shell extension disappears and the dock gets partly
- unresponsive and does not disappears. When the system is locked, the
- dock is still visible and one can launch programs, which are not visible
- but still started. Sometimes it seems like two gnome-shell guis are
- overlapping each other.
+ user theme shell extension disappears (standard ui then) and the dock
+ gets partly unresponsive and does not disappears. When the system is
+ locked, the dock is still visible and one can launch programs, which are
+ not visible but still started. Sometimes it seems like two gnome-shell
+ guis are overlapping each other.
  
  There is no crash file for gnome-shell in /var/crash.
  My whoopsi ID is: 
https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918
  
  Description:  Ubuntu 18.10
  Release:  18.10
  
  gnome-shell:
-   Installed: 3.30.1-2ubuntu1
-   Candidate: 3.30.1-2ubuntu1
-   Version table:
-  *** 3.30.1-2ubuntu1 500
- 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.30.1-2ubuntu1
+   Candidate: 3.30.1-2ubuntu1
+   Version table:
+  *** 3.30.1-2ubuntu1 500
+ 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
- 
- This bug might be close to 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799242
+ This bug might be close to https://bugs.launchpad.net/ubuntu/+source
+ /gnome-shell/+bug/1799242

** Description changed:

  gnome shell sometimes "crashes", especially when system auto locks. The
  user theme shell extension disappears (standard ui then) and the dock
  gets partly unresponsive and does not disappears. When the system is
  locked, the dock is still visible and one can launch programs, which are
  not visible but still started. Sometimes it seems like two gnome-shell
  guis are overlapping each other.
+ 
+ I am using a gtk+ theme: https://github.com/nivekxyz/afflatus
  
  There is no crash file for gnome-shell in /var/crash.
  My whoopsi ID is: 
https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918
  
  Description:  Ubuntu 18.10
  Release:  18.10
  
  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate:

[Touch-packages] [Bug 1700750] Re: Cannot suddenly print to a samba printer on 17.04

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cannot suddenly print to a samba printer on 17.04

Status in cups package in Ubuntu:
  Expired

Bug description:
  I lost my samba printers from my Ubuntu 17.04 laptop; they're
  connected to my desktop and used to work, I guess they did work with
  17.04 before. I could install the samba printer anew - it would be
  autodetected and all. However upon printing, nothing is printed and
  for as long as the jobs are in the queue the following kinds of
  messages are spammed into the dmesg at 5-10 sec interval:

  [19132.636607] audit: type=1400 audit(1498562191.201:593): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=28009 
comm="cups-browsed" capability=12  capname="net_admin"
  [19136.312251] audit: type=1400 audit(1498562194.873:594): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=27904 comm="ipp" 
capability=12  capname="net_admin"

  % lsb_release -rd 
  Description:Ubuntu 17.04
  Release:17.04

  
  % apt-cache policy cups cups-browsed
  cups:
Installed: 2.2.2-1ubuntu1
Candidate: 2.2.2-1ubuntu1
Version table:
   *** 2.2.2-1ubuntu1 500
  500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com zesty/main 
amd64 Packages
  100 /var/lib/dpkg/status
  cups-browsed:
Installed: 1.13.4-1ubuntu1
Candidate: 1.13.4-1ubuntu1
Version table:
   *** 1.13.4-1ubuntu1 500
  500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com zesty/main 
amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1700750/+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 1727339] Re: Cups never prompts for username and password

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cups never prompts for username and password

Status in cups package in Ubuntu:
  Expired

Bug description:
  To print over a network, I have to provide my credentials that differ
  from those on my local workstation. This works, if as long as I hard
  code the credentials into /etc/cups/printers.conf with "DeviceURI
  smb://user:passowrd@printerurl". This is inconvenient, because I have
  to change the password regularly and do not want to update the
  printers.conf file every time. Cups should ask for the credentials
  when the line "AuthInfoRequired username,password" is added to the
  printer configuration, but this does not work for me. It were even
  better if cups had a smart password save option, that tries first the
  old password and prompts for a new one, whenever the old one does not
  work anymore. This is a bug which annoys me since years, but never
  reported, because there is the workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 25 15:02:10 2017
  InstallationDate: Installed on 2015-11-05 (720 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat:
   device for Lexmark_Lexmark_E232: usb://Lexmark/E232?serial=722DG57
   device for printer: smb://scomp5170/WURprinter_PS_Color
   device for Ricoh-MP-C5503: smb://scomp5170/WURprinter_PS_Color
   device for SCX-470x-Series: 
usb://Samsung/SCX-470x%20Series?serial=Z79JBADC200505H&interface=1
  MachineType: Notebook W230SS
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=2329e937-a4e4-4efc-a999-c0fa7d44c92b ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1727339/+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 1694680] Re: Extremely slow printing of pdf file made from a powerpoint with background

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Extremely slow printing of pdf file made from a powerpoint with
  background

Status in cups package in Ubuntu:
  Expired

Bug description:
  Hello. I've had this problems for years (Since Ubuntu 10.04) and I
  decided now to write about it. I have a few files that come from
  Powerpoint and saved into PDF. Those files have a background with some
  patterns/vectors/whatever that make the printing extremely slow.
  Processing of each of this pages takes several minutes.

  You can find the file here:
  https://www.dropbox.com/s/6rzee0q3nszbpd5/PPT%20with%20background.pdf?dl=0

  Im using the following driver: HP Color LaserJet 9500 pcl3, hpcups
  3.16.11. Using a Gutenprint driver seems to fix the issue. However.
  There are other several documents that have problems with Gutenprint,
  therefore, I would prefer to keep the HP driver and try with some
  different workaround.

  The command I'm using to print is:
  lp -d printer -o fit-to-page -o media=Letter -o number-up=4 -o 
page-border=none -o number-up-layout=btlr -o sides=two-sided-short-edge 
"/home/ubuntu/filename.pdf"

  I hope we can find the bug. I've find several similar problems and no
  solution yet.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1694680/+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 1728067] Re: CUPS : wrong imageable area A4 for Canon MG4200

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  CUPS : wrong imageable area A4 for Canon MG4200

Status in cups package in Ubuntu:
  Expired

Bug description:
  Prints are shifted to the bottom, end of the page is never printed. 
  I have a look on the ppd file of my printer and the imageablearea for size A4 
seems wrong.

  It's should be

  ImageableArea A4/A4: "18 36 577 806"

  but it's ImageableArea A4: "18 106 577 819"

  I tried to edit and change it, but on each reload of cups the wrong
  version come in place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1728067/+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 1716102] Re: canon LBP2900b printer does worked

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  canon LBP2900b printer does worked

Status in cups package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04 LTS

  RAM: 15.6 GiB
  Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz × 8 
  Graphics: GeForce GTX 1050 Ti/PCIe/SSE2
  OS type: 64-bit
  Method of Install for OS: UEFI with windows (dual boot)

  device URI: usb://Canon/LBP2900?serial=A3A50LNr
  Make and Model: Canon LBP2900 CAPT ver.1.5
  Driver used: linux-capt-drv-v271-uken.tar.gz

  printer status: Idle - Sending data to printer.

  Description:

  the printer is not working or printing even a test page.
  the test page print is disappeared or stopped.

  additional info:
  http://localhost:631/printers/
  Description:  Canon LBP2900
  Location: gopi
  Driver:   Canon LBP2900 CAPT ver.1.5 (grayscale)
  Connection:   usb://Canon/LBP2900?serial=A3A50LNr
  Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1716102/+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 1732554] Re: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in cups package in Ubuntu:
  Expired

Bug description:
  It is a fresh Ubuntu install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcups2:amd64 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Nov 15 12:18:41 2017
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-11-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron 3437
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 02JX3T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/24/2014:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn02JX3T:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1732554/+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 1733413] Re: package cups-client 2.1.3-4ubuntu0.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré

[Launchpad Bug Tracker]

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package cups-client 2.1.3-4ubuntu0.3 failed to install/upgrade:
  problèmes de dépendances - laissé non configuré

Status in cups package in Ubuntu:
  Expired

Bug description:
  no idea

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-client 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Nov 20 21:29:30 2017
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2017-10-15 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ZOTAC ZBOX-CI527/CI547
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-client 2.1.3-4ubuntu0.3 failed to install/upgrade: 
problèmes de dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P206
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1733413/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

[Daniel van Vugt]

Fix verified in version 0.99.8-2ubuntu0.1


** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Committed
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+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 1799998] Re: 20% of volume is like 0%

[Daniel van Vugt]

** Summary changed:

- [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%
+ 20% of volume is like 0%

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

Title:
  20% of volume is like 0%

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/178/+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 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

[Launchpad Bug Tracker]

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

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

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

Title:
  20% of volume is like 0%

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/178/+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 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

[Daniel van Vugt]

** No longer affects: linux (Ubuntu)

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

Title:
  20% of volume is like 0%

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/178/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Daniel van Vugt]

OK, that makes sense. In that case I was misled by apport automatically
writing this in the bug report:

UnreportableReason: This is not an official Pop!_OS package. Please
remove any third party package and try again.

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Tessa]

@vanvugt:  actually, PoP! is just a light themeing a driver PPA on top
of Ubuntu, it doesn't really change a lot. it also uses pulseaudio, I
installed jackd after I started having issues just in an attempt to get
usable sound on my system, but it didn't improve the situation. but
pulseaudio was definitely broken before I installed jack.

in any case, I'll uninstall jack and re-run the crash dump settings and
we'll see where we stand.

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1455520] Re: systemd-shim executes 'poweroff' after resuming from suspend-to-memory(S3)

[ftoledo]

I still have this issue on debian stretch.

Did someone fix it?

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

Title:
   systemd-shim executes 'poweroff' after resuming from suspend-to-
  memory(S3)

Status in systemd-shim package in Ubuntu:
  New

Bug description:
  Hi,all
  I'm using latest kernel 4.1-rc3 on ubuntu 14.04.2 LTS X86_64,
  and I found that, after resuming from suspend-to-memory,
  the systemd-shim deamon will execute a 'poweroff', which 
  shuts the system down. 

  here's my step to reproduce the bug:

  1.echo mem > /sys/power/state //ok
  2.wait for 30 seconds//ok
  3.push power button  //ok
  4.system resumes automatically //ok
  5.after a few seconds, system shutdown //oh no...

  I replace /sbin/shutdown with a script that prints the current process
  backtrace by pstree, then the system will not halt after resumming
  from suspend-to-memory. Here's my script:

  # cat /sbin/shutdown
  #!/bin/sh
  pstree -a > /home/chenyu/shutdown_trace.log

  and here's the backtrace when system is executing my 'shutdown', after
  resumming, we can see that, systemd-shim invokes 'sh -c
  /sbin/poweroff':

  
  init
|-ModemManager
|   `-2*[{ModemManager}]
|-NetworkManager
|   `-3*[{NetworkManager}]
|-acpid -c /etc/acpi/events -s /var/run/acpid.socket
|   `-sh -c /etc/acpi/powerbtn.sh
|-anacron -s
|-avahi-daemon
|   `-avahi-daemon
|-bluetoothd
|-cron
|-cups-browsed
|-cupsd -f
|   `-dbus dbus:// 
|-dbus-daemon --system --fork
|-getty -8 38400 tty4
|-getty -8 38400 tty5
|-getty -8 38400 tty2
|-getty -8 38400 tty3
|-getty -8 38400 tty6
|-irqbalance
|-kerneloops
|-login --   
|   `-bash
|   `-sudo -s
|   `-bash
|-ondemand /etc/init.d/ondemand background
|   `-sleep 60
|-polkitd --no-debug
|   `-2*[{polkitd}]
|-rsyslogd
|   `-3*[{rsyslogd}]
|-sshd -D
|-systemd-logind
|-systemd-shim
|   |-sh -c /sbin/poweroff
|   |   `-shutdown /sbin/shutdown -h -P now
|   |   `-pstree -a
|   `-2*[{systemd-shim}]
|-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   |-systemd-udevd --daemon
|   `-systemd-udevd --daemon
|-upstart-file-br --daemon
|-upstart-socket- --daemon
|-upstart-udev-br --daemon
`-whoopsie
`-2*[{whoopsie}]

  Since I'm not sure why systemd-shim act like this, I would be 
  happy to debug with your suggestion, and give feedback to you.


  Best Regards,
  Yu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1455520/+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 1766074] Re: unity 7.4.5.5+16.04.20180221-0ubuntu1 Crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1766074

Title:
  unity 7.4.5.5+16.04.20180221-0ubuntu1 Crash

Status in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/x86_64-linux-gnu/unity/compiz-config-profile-setter

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.1:
   
  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
  Date: Sun Apr 22 12:58:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82Q963/Q965 Integrated Graphics 
Controller [103c:2808]
  InstallationDate: Installed on 2014-08-29 (1331 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Compaq dc5700 Microtower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=364b6e92-64f0-41cf-a72c-57b437758d52 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E2 v02.04
  dmi.board.name: 0A60h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC7424GG3
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E2v02.04:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5700 Microtower
  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 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: Sun Apr 22 12:56:18 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

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

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Both during and after installation (meaning while running the USB iso
  and booting from HDD after) ubuntu will rapidly become unresponsive
  and eventually hang when my 4k monitor is plugged in. I have 2
  monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly
  if I only use the 1920 monitor (this is where I am working from right
  now) but the moment the other monitor is plugged in I get problems.

  When I cold boot into the system from the small 1920x1080 monitor and
  then plug in the 4k monitor, the screen on my smaller monitor will
  glitch before returning to normal a few seconds later, while the 4k
  monitor never displays an image. The OS begins to bog down, the mouse
  begins to lag and become less responsive. If I open the display
  manager I can see that ubuntu has properly detected the 4k monitor and
  has the correct default settings (resolution, refresh rate, etc.) but
  attempting to make any changes will result in an immediate crash/hang
  upon pressing the "apply" button.

  If I cold boot ubuntu with only the 4k monitor plugged in, I see
  purple splash screen and ubuntu logo screens (at the correct
  resolutions) but the monitor output stops and I see only a black
  screen before the login screen is reached.

  If I cold boot with both monitors plugged in I see the splash screen
  and logo, there is a brief moment where the small monitor glitches,
  and then I see only the magenta backdrop of the login screen but there
  are no UI elements, and This is only seen on the small monitor; the 4k
  monitor has once again lost input and turned black.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 29 17:32:16 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518]
  InstallationDate: Installed on 2018-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI
  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.18.0-10-generic 
root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-SLI-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 

[Touch-packages] [Bug 1800479] Re: 18.10 Wayland segmentation fault (11) for any qt application

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** No longer affects: xorg (Ubuntu)

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.deskt

[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Daniel van Vugt]

More simply, please try this command and then reboot:

sudo apt remove jackd jackd2 jackd2-firewire

** Changed in: pulseaudio (Ubuntu)
   Status: Opinion => Incomplete

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Daniel van Vugt]

Tessa,

I think these two things might be related...

1. Pop!OS doesn't like pulseaudio:

UnreportableReason: This is not an official Pop!_OS package. Please
remove any third party package and try again.

2. You have two sound servers and should only have one:

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes

Jack:
  Installed - Yes (/usr/bin/jackd)
  Running - No

It sounds like System76's Pop!OS ships with jackd and they don't want
you using pulseaudio. Certainly having both installed I would expect one
of them might fail to access the sound hardware. This also means I am
not sure the correct way to fix this other than it sounds like
pulseaudio shouldn't be installed at all in Pop!OS.

Suggested quick fix: Uninstall either your jackd packages, OR your
pulseaudio packages.

Fully clean fix: Reinstall Ubuntu from scratch, downloading it from here:
http://releases.ubuntu.com/18.10/


** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Opinion

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Opinion

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799868] Re: seq command has problems near its max integer

[C de-Avillez]

Hello Kevin, and thank you for opening this bug and helping make Ubuntu
better.

The info page for seq (info seq) has the following note:

" On most systems, seq can produce whole-number output for values up to
at least 2^{53}.  Larger integers are approximated.  The details differ
depending on your floating-point implementation.  *Note Floating
point::.  A common case is that ‘seq’ works with integers through
2^{64}, and larger integers may not be numerically correct:

 $ seq 5000 2 5004
 5000
 5000
 5004

   However, note that when limited to non-negative whole numbers, an
increment of 1 and no format-specifying option, seq can print
arbitrarily large numbers.

   Be careful when using ‘seq’ with outlandish values: otherwise you may
see surprising results, as ‘seq’ uses floating point internally.  For
example, on the x86 platform, where the internal representation uses a
64-bit fraction, the command:

 seq 1 0.001 1.009

   outputs 1.007 twice and skips 1.008."

Now, 2^64 is 18446744073709551616, which is *much* smaller than the
values you are using. So... you are in the boundary of the map, where it
is written "here be dragons."

I ran 'seq' with your initial value, and increment of 1, and varying
end-values, all larger than the initial value. All seemed to work
correctly. But the moment I changed the increment... things went south
very fast (including what seemed as an infinite loop, with 'seq'
outputting the same value over and over).

I am in a mind of closing this bug INVALID, but wanted to have your
input before that.

Thank you.

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

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

Title:
  seq command has problems near its max integer

Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  I can use seq(1) to generate sequences of large numbers if I use the
  default increment:

  $ seq 170141183460469231731687303715884105721 
170141183460469231731687303715884105725
  170141183460469231731687303715884105721
  170141183460469231731687303715884105722
  170141183460469231731687303715884105723
  170141183460469231731687303715884105724
  170141183460469231731687303715884105725
  $

  However, if I use an increment of 2 (which should stop 2 short of the max 
int,) it starts with the max integer+1 (2^127) and outputs it forever:
  $ seq 170141183460469231731687303715884105721 2 
170141183460469231731687303715884105725 | less
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  .
  .
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 24 20:17:15 2018
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1799868/+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 997217] Re: salsauthd maxes cpu

[Brian Murray]

Hello David, or anyone else affected,

Accepted cyrus-sasl2 into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cyrus-
sasl2/2.1.26.dfsg1-14ubuntu0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cyrus-sasl2 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  salsauthd maxes cpu

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Precise:
  Won't Fix
Status in cyrus-sasl2 source package in Trusty:
  Invalid
Status in cyrus-sasl2 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The rimap authentication mechanism in saslauthd can hit a condition
  where it will start spinning and using all available CPU. This
  condition can be easily encountered when an authentication is
  happening and the imap service is being restarted.

  Furthermore, the saslauthd child process that picked up that
  authentication request and that is spinning now won't be reaped nor
  can it service further requests. If all children are left in this
  state, the authentication service as a whole won't be working anymore.

  [Test Case]

  This test can be performed in a LXD or VM.

  * install the needed packages. mail-stack-delivery is used to have an
  imap server available on localhost that needs no further
  configuration. Accept the defaults for all debconf prompts:

  sudo apt update
  sudo apt install sasl2-bin mail-stack-delivery

  * set the password "ubuntu" for the ubuntu user
  echo ubuntu:ubuntu | sudo chpasswd

  * start saslauthd like this, with just one child:
  sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1

  * restart dovecot
  sudo service dovecot restart

  * test saslauthd authentication:
  $ sudo testsaslauthd -u ubuntu -p ubuntu
  0: OK "Success."

  * Now let's break it. In one terminal watch the output of top:
  top

  * in another terminal, run the following:
  sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop

  * observe in the "top" terminal that saslauthd is consuming a lot of
  cpu. If that's not happening, try starting dovecot again and adjusting
  the sleep value in the previous test command, but 1s was enough in all
  my runs.

  * start dovecot and repeat the authentication request. Since the only 
saslauthd child is now spinning, this will block:
  sudo service dovecot start
  $ sudo testsaslauthd -u ubuntu -p ubuntu
  

  [Regression Potential]
  This fix relies on read(2) returning zero bytes when the connection is 
dropped, and that is clearly documented in its manpage:

  "On  success,  the  number  of  bytes read is returned (zero indicates
  end of file),"

  The select manpage also documents such a case being a valid case to
  indicate that a socket is ready to be read from, and that it won't
  block:

  "The file descriptors listed in readfds will be watched to see if
  characters become available for reading (more precisely, to see  if  a
  read will  not  block;  in  particular, a file descriptor is also
  ready on end-of-file)"

  This patch is what was used upstream, and is also present in bionic.

  I can't think of regressions specific to this change, other than the
  usual risk of rebuilding a widely used library (sasl2) in an
  environment different from the one from when xenial was released,
  i.e., different libraries available, maybe different system-wide build
  options, etc.

  [Other Info]
  Trusty is still not accounting for read() returning zero being an end-of-file 
case, but the loop there has a counter and it eventually exits, not leading to 
a perpetual spin or high cpu usage (see comment #17 for a brief history on how 
this fix was dropped in the xenial package).

  The fix is simp

[Touch-packages] [Bug 1800559] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)

[Randy Nyle Adamson]

You can e-mail me @ adamsonra...@outlook.com Thanks

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

Title:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Status in adduser package in Ubuntu:
  New

Bug description:
  randy@randy-Inspiron-518:~$ sudo apt-get updates
  [sudo] password for randy: 
  E: Invalid operation updates
  randy@randy-Inspiron-518:~$ sudo apt-get update
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
 
  Hit:2 http://archive.canonical.com/ubuntu xenial InRelease
 
  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
 
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]   
 
  Fetched 216 kB in 1s (147 kB/s)   
 
  Reading package lists... Done
  randy@randy-Inspiron-518:~$ sudo apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
linux-generic linux-headers-generic linux-image-generic
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  4 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.122ubuntu8.13) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-image-extra-4.4.0-137-generic (4.4.0-137.163) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.4.0-137-generic /boot/vmlinuz-4.4.0-137-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-4.4.0-137-generic 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-extra-4.4.0-137-generic; however:
Package linux-image-extra-4.4.0-137-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-image-generic (= 4.4.0.137.143); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for initramfs-tools (0.122ubuntu8.13) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
No apport report written because the error message 
indicates its a followup error from a previous failure.
  update-initramfs: 
Generating /boot/initrd.img-4.4.0-137-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-4.4.0-137-generic
   linux-image-generic
   linux-generic
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  randy@randy-Inspiron-518:~$ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  4 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up initramfs-tools (0.122ubuntu8.13) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-image-extra-4.4.0-137-generic (4.4.0-137.163) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.4.0-137-generic /boot/vmlinuz-4.4.0-137-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
  run-parts: /etc/kern

[Touch-packages] [Bug 1800559] [NEW] E: Sub-process /usr/bin/dpkg returned an error code (1)

[Randy Nyle Adamson]

Public bug reported:

randy@randy-Inspiron-518:~$ sudo apt-get updates
[sudo] password for randy: 
E: Invalid operation updates
randy@randy-Inspiron-518:~$ sudo apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease 
Hit:2 http://archive.canonical.com/ubuntu xenial InRelease 
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB] 
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Fetched 216 kB in 1s (147 kB/s)
Reading package lists... Done
randy@randy-Inspiron-518:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.122ubuntu8.13) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-extra-4.4.0-137-generic (4.4.0-137.163) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-4.4.0-137-generic 
(--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-extra-4.4.0-137-generic; however:
  Package linux-image-extra-4.4.0-137-generic is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 4.4.0.137.143); however:
  Package linux-image-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.122ubuntu8.13) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.
  No apport report written because the error message 
indicates its a followup error from a previous failure.
update-initramfs: 
Generating /boot/initrd.img-4.4.0-137-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were 
encountered while processing:
 linux-image-extra-4.4.0-137-generic
 linux-image-generic
 linux-generic
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
randy@randy-Inspiron-518:~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.122ubuntu8.13) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-extra-4.4.0-137-generic (4.4.0-137.163) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-137-generic 
/boot/vmlinuz-4.4.0-137-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-137-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-137-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-4.4.0-137-generic 
(--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-extra-4.4.0-137-generic; however:
  Package linux-image-extra-4.4.0-137-generic is not configured yet.

dpkg: error processing package linux-image-generic (--config

[Touch-packages] [Bug 1800550] [NEW] Xorg freeze

[Vincent Ragusa]

Public bug reported:

Both during and after installation (meaning while running the USB iso
and booting from HDD after) ubuntu will rapidly become unresponsive and
eventually hang when my 4k monitor is plugged in. I have 2 monitors, a
1920x1080, and a 4k. Everything works absolutely perfectly if I only use
the 1920 monitor (this is where I am working from right now) but the
moment the other monitor is plugged in I get problems.

When I cold boot into the system from the small 1920x1080 monitor and
then plug in the 4k monitor, the screen on my smaller monitor will
glitch before returning to normal a few seconds later, while the 4k
monitor never displays an image. The OS begins to bog down, the mouse
begins to lag and become less responsive. If I open the display manager
I can see that ubuntu has properly detected the 4k monitor and has the
correct default settings (resolution, refresh rate, etc.) but attempting
to make any changes will result in an immediate crash/hang upon pressing
the "apply" button.

If I cold boot ubuntu with only the 4k monitor plugged in, I see purple
splash screen and ubuntu logo screens (at the correct resolutions) but
the monitor output stops and I see only a black screen before the login
screen is reached.

If I cold boot with both monitors plugged in I see the splash screen and
logo, there is a brief moment where the small monitor glitches, and then
I see only the magenta backdrop of the login screen but there are no UI
elements, and This is only seen on the small monitor; the 4k monitor has
once again lost input and turned black.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 29 17:32:16 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
 NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518]
InstallationDate: Installed on 2018-10-29 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI
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.18.0-10-generic 
root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-SLI-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.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-SLI
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic freeze 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/1800550

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Both during and after i

[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta

[Brian Murray]

Hello Patrick, or anyone else affected,

Accepted shim-signed into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.37~18.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: shim-signed (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
  signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1)

Status in shim-signed package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Incomplete
Status in shim-signed source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * When Secure Boot is enabled and MOK is not set and a new dkms
  module is installed sim-signed asks for a Secure Boot MOK, or aborts
  package installation in non-interactive mode. When unattended-upgrades
  performed the upgrade the aborted installation leaves an unconfigured
  system behind that may even fail to boot. In nvdidia's special case
  the new module is actually just a new version of the nvidia module
  which should be fine to install.

   * The fix in shim-signed now handles nvidia dkms module directory
  renames as simple upgrades and also does not handle module removals as
  a reason to abort installation.

  [Test Case (shim-signed)]

  1. Set up Bionic system with Secure Boot enabled.

  2. Install packagages to trigger MOK enrollment and enroll the key:

   apt install dkms shim-signed r8168-dkms

  3. Create a new key to be enrolled again:

   rm /var/lib/shim-signed/mok/MOK.der
   update-secureboot-policy  --new-key

  4. Simulate module removal and test that the command returns 0:
   
  # echo /var/lib/dkms/zzz >> /var/lib/shim-signed/dkms-list
  # env DEBIAN_FRONTEND=noninteractive update-secureboot-policy  --enroll-key; 
echo $?
  Running in non-interactive mode, doing nothing.
  0

  5.  Simulate nvidia module rname and test that the command returns 0:

  # cat > /var/lib/shim-signed/dkms-list < /var/lib/shim-signed/dkms-list  < 
/etc/apt/apt.conf.d/51unattended-upgrades-all

  5. Observe u-u keeping back the new package:
  unattended-upgrade --verbose --dry-run --debug
  ...
  Checking: r8168-dkms ([])
  pkg new-dkms-dep may trigger secure boot key prompt
  sanity check failed
  ...

  [Regression Potential (shim-signed)]

  * The fix lets installation of nvidia dkms module upgrades continue and also 
lets dkms module removals continue when MOK is not set and those should not 
cause regressions themselves. In case of an implementation mistake a new module 
installation could go undetected and could cause the system not load a dkms 
module on next boot.
  In practice not loading new modules rarely cause regressions, but if a module 
is converted from being in the kernel to a dkms module upon an upgrade this is 
possible.
   * I tested the module addition, removal, nvidia module upgrade and not 
module change cases with stubs pretending that the system is secure-boot 
capable an found the changed script working properly.

  [Regression Potential (unattended-upgrades)]

  * Since the fix is holding back packages from installation it is
  expected that systems that would have otherwise broke during the
  installation would not receive all updates. Since exact detection of
  the installation failure reported here does not seem possible u-u
  holds back more packages than it would be absolutely necessary.

  * Administrators are expected to set up email notifications about the
  updates performed by u-u and act on held back packages.

  * Si

[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

[Matt Johnson]

I recently switched back to Ubuntu, only to find that Slack in a snap is
still crashing on Wayland! I previously reported what seems like a
related bug on snapcraft-- here's the link to the related bug with logs
and some details from experiences on Fedora28 and Arch.
https://forum.snapcraft.io/t/slack-for-linux-crash-on-wayland/5909

Currently still experiencing the issue with Ubuntu 18.10:

```
$ snap info slack
name: slack
summary: Team communication for the 21st century.
publisher: Slack✓
contact: https://get.slack.help/hc/en-us
license: Proprietary
description: |
  Caution: Slack for Linux is in beta. We’re still busy adding features and 
ironing out potential
  issues.

  Slack brings team communication and collaboration into one place so you can 
get more work done,
  whether you belong to a large enterprise or a small business. Check off your 
to-do list and move
  your projects forward by bringing the right people, conversations, tools, and 
information you need
  together. Slack is available on any device, so you can find and access your 
team and your work,
  whether you’re at your desk or on the go.

  Scientifically proven (or at least rumored) to make your working life 
simpler, more pleasant, and
  more productive. We hope you’ll give Slack a try.

  Stop by and learn more at: https://slack.com/
snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD
channels:
  stable: 3.3.3 (9) 148MB classic
  candidate: ↑
  beta: ↑
  edge: 3.3.1 (8) 148MB classic
```

```
$ snap --version
snap 2.35.5+18.10
snapd 2.35.5+18.10
series 16
ubuntu 18.10
kernel 4.18.0-10-generic
```

I'm happy to provide any testing or log resources-- let me know if
there's anything I can help out with!

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sa

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

Posted on alsa-devel mailing list ...

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.

[Touch-packages] [Bug 1800055] Re: iwd does not work with network manager

[Mathieu Trudel-Lapierre]

Oh, I know you didn't. It was a comment about Will's suggestion on his
bug (I marked duplicate of this one).

FWIW, I'm all for changing the default if testing shows there's a
benefit, and my suggestion was that if we're to do it, do it sooner
rather than later; but it *does* require concerted, planned testing, and
a risk analysis... and probably carrying the patches for TLS EAP
methods.

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

Title:
  iwd does not work with network manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I configured network manager to use iwd, unfortunately it doesn't
  work:

  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.4358] 
device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: 
assertion 'g_variant_type_check (type)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: 
assertion 'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.7492] 
device (wlp4s0): new IWD device state is (null)
  Oct 25 15:12:23 malefic NetworkManager[17004]:  [1540501943.7492] 
device (wlp4s0): State (null) unknown
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

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

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted xkeyboard-config into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/xkeyboard-
config/2.23.1-1ubuntu1.18.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-cosmic

** Changed in: xkeyboard-config (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Committed
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Please test proposed package

[Brian Murray]

Hello Jeremy, or anyone else affected,

Accepted xkeyboard-config into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/xkeyboard-
config/2.23.1-1ubuntu1.18.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Committed
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted upower into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.8-2ubuntu0.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Committed
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 1800055] Re: iwd does not work with network manager

[James Troup]

Mathieu Trudel-Lapierre  writes:

> AFAIK at the moment there isn't proper WPA Enterprise support (well,
> most TLS methods appears to be missing kernel patches). Let's please be
> careful about changing the default wireless daemon to iwd, there's a
> couple of moving parts there, it's not just about changing the software.

To be clear, I wasn't suggesting changing the default yet.  As you
say, doing so today would be a regression.  I'd just like folks who
don't require WPA Enterprise support to be able to test iwd (with
network manager).

In my limited testing (by hand, not using network-manager) at a recent
sprint iwd is orders of magnitude better than wpasupplicant in 'busy'
wireless networks.

-- 
James

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

Title:
  iwd does not work with network manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I configured network manager to use iwd, unfortunately it doesn't
  work:

  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.4358] 
device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: 
assertion 'g_variant_type_check (type)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: 
assertion 'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.7492] 
device (wlp4s0): new IWD device state is (null)
  Oct 25 15:12:23 malefic NetworkManager[17004]:  [1540501943.7492] 
device (wlp4s0): State (null) unknown
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Tessa]

@vanvugt: alright, it's been uploaded, it says it's at this URL but I don't 
have permissions to view that and verify:
https://errors.ubuntu.com/oops/ffc53e0c-dba2-11e8-9fcf-fa163e6cac46

packages list is attached


** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+attachment/5206826/+files/allpackages.txt

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1734040] Re: openssh: The concurrency of settimeofday and ssh connect would lead to coredump

[Andreas Hasenack]

Is there a sccenario where this can be easily triggered? I'm thinking
both in terms of priority for this fix, and for an SRU test case
description.

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

Title:
  openssh: The concurrency of settimeofday and ssh connect would lead to
  coredump

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  New
Status in openssh source package in Bionic:
  New

Bug description:
  Hi, pals:
  we found a coredump when we do ssh connection. the basic information as 
follow:
  the stack trace in coredump:
  (gdb) bt
  #0 0x20007510 in raise () from /lib/libc.so.6
  #1 0x2000c718 in abort () from /lib/libc.so.6
  #2 0x2053d42c in __mulvsi3 (a=, b=) at 
/home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159
  #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, 
ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871
  #4 0x204d2568 in ssh_exchange_identification 
(timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580
  #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, 
hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, 
timeout_ms=5000)
  at sshconnect.c:1346
  #6 0x204c433c in main (ac=, av=) at ssh.c:1326

  the direct cause of the coredump, is that the function __mulvsi3 in
  gcc checked the plus operation is overflow, then this gcc function
  abort().

  the reason of the overflow is cause by the time-setting operation when
  do ssh connect. in function ms_subtract_diff . the timeoutp get a very
  big value because of the time-change.

  So could we add a limitation for the differ of the 2 values get from 
gettimeofday ? if it's too big, would lead to overflow, we set a default value 
and report a warning log.
  thanks for you attention and expect your reply.

  B.R.
  Le Wang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1734040/+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 1800297] Re: localectl updates /etc/default/locale without root privileges

[Dimitri John Ledkov]

root group is irrelevant here, and should not be used to enforce ACLs.

On Ubuntu, root user is disabled by default. Instead, regular user
accounts are treated as admin accounts if they have the permission to
`sudo` into root. This is done, by default, by adding user accounts to
`sudo` group. This is also what gnome account services / policykit / etc
use to determine `who is admin`.

E.g. in gnome-settings on Ubuntu, one can toggle user accounts between
normal and administrator, which removes/adds sudo group to a given
account.

Policykit does correct authentication to execute this action. Accounts
in `sudo` group can execute it directly, otherwise a policykit popup
appears listing all existing `sudo` group members and asking to
authenticate as one of those people. I have just tested that this all
works correctly on cosmic.

So, if you don't expect this behaviour on this particular account,
`sudo` group is the one to remove. But note that is the same group that
makes `sudo -i` work, so please don't lock yourself out if that's the
only sudo capable account!

Thus everything works as expected, and administrator accounts can do the
same action (with less validation) via `sudo nano /etc/default/locale`.


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

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

Title:
  localectl updates /etc/default/locale without root privileges

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  localectl updates /etc/default/locale when it is run as non root user:
  $ localectl set-locale LANG=en_US.UTF-8

  $ ls -l /etc/default/locale 
  -rw-r--r-- 1 root root 17 Oct 26 12:46 /etc/default/locale

  My account is neither root nor in group root:
  $ groups
  christian adm cdrom sudo dip plugdev lpadmin sambashare

  $ ls -al `which localectl`
  -rwxr-xr-x 1 root root 21916 Oct  4 16:58 /usr/bin/localectl

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 18.10
  MachineType: Dell Inc. MM061
  Package: systemd 239-7ubuntu10
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/vg0-fedora ro
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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.
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800297/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Gijs Molenaar]

Is it possible to upload a fixed package to bionic backports?

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1644643] Re: apt failed to run due to link time reference error

[MrMe01]

Julian, I get something similar, but different.
"# apt
apt: relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: symbol 
_ZN9pkgSystem9LockInnerEv, version APTPKG_5.0 not defined in file 
libapt-pkg.so.5.0 with link time reference"

apt-cache policy is the same, and so is apt libapt-pkg5.0.

What can I do to rectify this? I started asking on reddit, got
redirected to askubuntu, and someone pointed me to this page, I was the
one who confirmed it, as I experienced the same or similar issues.

I am contemplating reinstalling as using the same install media in a VM
(mini.iso) resulted in a working state, and apt functions as expected,
so I doubt the .deb files are the issue here, more likely the state of
apt on my box.

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Khurshid Alam]

This will be fixed soon.

See
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569/comments/18

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  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.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+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 1800458] Re: [Intel Corporation UHD Graphics 620] Xorg freeze

[Cristian Aravena Romero]

** Package changed: xorg (Ubuntu) => xorg-server (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/1800458

Title:
  [Intel Corporation UHD Graphics 620] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Mon Oct 29 13:13:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
     Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
  InstallationDate: Installed on 2018-10-15 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 14u G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.01.08
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.50.00
  dmi.chassis.asset.tag: 5CG8305291
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP ZBook 14u G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800458/+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 1800329] Re: Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name)
  queries through DHCP assigned DNS (cached) server on local network

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubnutu 18.04 KDE Neon does not resolve local (or single name) queries
  through DHCP assigned DNS (cached) server on local network.

  ** How to reproduce? **

  1. Let's have local network (e.g. 192.168.123.0/24) connected to the Internet 
through router called GATE
  2. The GATE provides local DNS server cache (via Dnsmasq) and contains couple 
of local name translations (e.g. SuperCooolLocalServer pointing to 
192.168.123.50).
  3. Let's have fresh new Ubuntu 18.04 (KDE Neon)
  4. Connect to the local network through WIFI (WPA2 encrypted, jsut enter 
password)

  ** What happens? **

  Any desktop application trying to connect to SuperCooolLocalServer
  will fail when resolving the name to IP.

  When tested in terminal "host SuperCooolLocalServer" will return
  SERVFAIL.

  ** What is expected? **

  The system should resolve the name SuperCooolLocalServer to
  192.168.123.50 as it did until Ubuntu 16.04 LTS.

  ** Observation **

  The system should do the resolution in the same logic as other home
  appliances running various operating systems (my iPhone, my wife's
  Galaxy, ours Ubuntu 16.04LTS, Windows 7, 8.1 10 and our other network
  components running various Linux based distributions.)

  I did quick test and the bug shows also on clean Ubuntu 18.04 (without
  the KDE Neon flavour).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800329/+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 1800297] Re: localectl updates /etc/default/locale without root privileges

[Sebastien Bacher]

** Tags added: rls-cc-incoming

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

Title:
  localectl updates /etc/default/locale without root privileges

Status in systemd package in Ubuntu:
  New

Bug description:
  localectl updates /etc/default/locale when it is run as non root user:
  $ localectl set-locale LANG=en_US.UTF-8

  $ ls -l /etc/default/locale 
  -rw-r--r-- 1 root root 17 Oct 26 12:46 /etc/default/locale

  My account is neither root nor in group root:
  $ groups
  christian adm cdrom sudo dip plugdev lpadmin sambashare

  $ ls -al `which localectl`
  -rwxr-xr-x 1 root root 21916 Oct  4 16:58 /usr/bin/localectl

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 18.10
  MachineType: Dell Inc. MM061
  Package: systemd 239-7ubuntu10
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/vg0-fedora ro
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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.
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800297/+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 1799265] Re: avahi-daemon high cpu, unusable networking

[Matt]

Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.

Thanks for looking into it.

** Attachment added: "avahi.zip"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+attachment/5206777/+files/avahi.zip

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1799265] Re: avahi-daemon high cpu, unusable networking

[Matt]

Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.

Thanks for looking into it.

** Attachment added: "avahi.zip"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+attachment/5206776/+files/avahi.zip

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1799265] Re: avahi-daemon high cpu, unusable networking

[Matt]

Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.

Thanks for looking into it.

** Attachment added: "avahi.zip"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+attachment/5206775/+files/avahi.zip

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1800055] Re: iwd does not work with network manager

[Mathieu Trudel-Lapierre]

AFAIK at the moment there isn't proper WPA Enterprise support (well,
most TLS methods appears to be missing kernel patches). Let's please be
careful about changing the default wireless daemon to iwd, there's a
couple of moving parts there, it's not just about changing the software.

For instance, iwd's design makes me expect that some hardware will no
longer be supported unless it is fully ported to using netlink rather
than ioctls (hopefully I am wrong about this). That's not a problem for
Intel-based wireless, but AIUI there are still lots of other drivers in
the wild.

My 0.02$: if we want to change from wpasupplicant to iwd, let's make
sure we have everything in place as early as possible (kernel patches),
and let's do some careful regression testing on a variety of hardware so
we can try to catch issues before they happen.

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

Title:
  iwd does not work with network manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I configured network manager to use iwd, unfortunately it doesn't
  work:

  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.4358] 
device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: 
assertion 'g_variant_type_check (type)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: 
assertion 'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.7492] 
device (wlp4s0): new IWD device state is (null)
  Oct 25 15:12:23 malefic NetworkManager[17004]:  [1540501943.7492] 
device (wlp4s0): State (null) unknown
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+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 1800479] XorgLog.txt

[Gigzbyte]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206764/+files/XorgLog.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: ena

[Touch-packages] [Bug 1800479] XorgLogOld.txt

[Gigzbyte]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206765/+files/XorgLogOld.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409

[Touch-packages] [Bug 1800479] Re: 18.10 Wayland segmentation fault (11) for any qt application

[Gigzbyte]

And another info - it doesn't matter if i have all monitors connected or
only laptop, in any case i have this crash.

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

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29

[Touch-packages] [Bug 1800479] Re: 18.10 Wayland segmentation fault (11) for any qt application

[Gigzbyte]

I can provide any additional details and do some debug if anyone can provide 
insstructions.
Also, i have coredump from this segvfault.
$ file core 
core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 
-d', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, 
execfn: '/usr/bin/Xwayland', platform: 'x86_64'

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault)

[Touch-packages] [Bug 1800479] xdpyinfo.txt

[Gigzbyte]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206767/+files/xdpyinfo.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: e

[Touch-packages] [Bug 1800479] Xrandr.txt

[Gigzbyte]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1800479/+attachment/5206766/+files/Xrandr.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enable

[Touch-packages] [Bug 1800479] UdevDb.txt

[Gigzbyte]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1800479/+attachment/5206763/+files/UdevDb.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enable

[Touch-packages] [Bug 1800479] ProcInterrupts.txt

[Gigzbyte]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206761/+files/ProcInterrupts.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-softw

[Touch-packages] [Bug 1800479] ProcModules.txt

[Gigzbyte]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206762/+files/ProcModules.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[34

[Touch-packages] [Bug 1800479] MonitorsUser.xml.txt

[Gigzbyte]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206757/+files/MonitorsUser.xml.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-s

[Touch-packages] [Bug 1800479] ProcCpuinfo.txt

[Gigzbyte]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206758/+files/ProcCpuinfo.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[34

[Touch-packages] [Bug 1800479] ProcEnviron.txt

[Gigzbyte]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206760/+files/ProcEnviron.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[34

[Touch-packages] [Bug 1800479] ProcCpuinfoMinimal.txt

[Gigzbyte]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206759/+files/ProcCpuinfoMinimal.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gno

[Touch-packages] [Bug 1800479] Lspci.txt

[Gigzbyte]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1800479/+attachment/5206755/+files/Lspci.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enabled 

[Touch-packages] [Bug 1800479] Lsusb.txt

[Gigzbyte]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1800479/+attachment/5206756/+files/Lsusb.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enabled 

[Touch-packages] [Bug 1800479] DpkgLog.txt

[Gigzbyte]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206754/+files/DpkgLog.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: ena

[Touch-packages] [Bug 1800479] Dependencies.txt

[Gigzbyte]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1800479/+attachment/5206753/+files/Dependencies.txt

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

Title:
  18.10 Wayland segmentation fault (11)  for any qt application

Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[

[Touch-packages] [Bug 1800479] Re: 18.10 Wayland segmentation fault (11) for any qt application

[Gigzbyte]

apport information

** Tags added: apport-collected cosmic ubuntu

** Description changed:

  Dear all!
  Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
  COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
  I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
  If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
  During usual xorg session everything is OK.
  Here's what i have in general log:
  ___
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
  Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
  Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
  Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enabled plugins: 
desktop-categories, fwupd, os-release, packagekit, packagekit-local, 
packagekit-offline, packagekit-proxy, packagekit-refine-repos, packag
  ___
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDe

[Touch-packages] [Bug 1800458] Re: [Intel Corporation UHD Graphics 620] Xorg freeze

[Cristian Aravena Romero]

Checking the logs, it appears that there are two video cards, but
according to the backtrace there are problems with the video card
'Intel'.

CurrentDmesg.txt:
[   98.239676] Call Trace:
[   98.239685]  v4l_enum_fmt+0x74/0x110 [videodev]
[   98.239689]  __video_do_ioctl+0x370/0x380 [videodev]
[   98.239692]  ? terminate_walk+0x8e/0xf0
[   98.239696]  video_usercopy+0x24d/0x640 [videodev]
[   98.239700]  ? video_ioctl2+0x20/0x20 [videodev]
[   98.239704]  video_ioctl2+0x15/0x20 [videodev]
[   98.239709]  v4l2_ioctl+0xc8/0xf0 [videodev]
[   98.239741]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
[   98.239744]  do_vfs_ioctl+0xa8/0x630
[   98.239746]  ? kmem_cache_free+0x1b3/0x1e0
[   98.239749]  ? putname+0x4c/0x60
[   98.239751]  ? do_sys_open+0x13e/0x2c0
[   98.239780]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
[   98.239782]  SyS_ioctl+0x79/0x90
[   98.239786]  do_syscall_64+0x73/0x130
[   98.239790]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

** Summary changed:

- Xorg freeze
+ [Intel Corporation UHD Graphics 620] Xorg freeze

** Description changed:

  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station
  
  ---
+ 
+ Checking the logs, it appears that there are two video cards, but
+ according to the backtrace there are problems with the video card
+ 'Intel'.
  
  CurrentDmesg.txt:
  [   98.239676] Call Trace:
  [   98.239685]  v4l_enum_fmt+0x74/0x110 [videodev]
  [   98.239689]  __video_do_ioctl+0x370/0x380 [videodev]
  [   98.239692]  ? terminate_walk+0x8e/0xf0
  [   98.239696]  video_usercopy+0x24d/0x640 [videodev]
  [   98.239700]  ? video_ioctl2+0x20/0x20 [videodev]
  [   98.239704]  video_ioctl2+0x15/0x20 [videodev]
  [   98.239709]  v4l2_ioctl+0xc8/0xf0 [videodev]
  [   98.239741]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
  [   98.239744]  do_vfs_ioctl+0xa8/0x630
  [   98.239746]  ? kmem_cache_free+0x1b3/0x1e0
  [   98.239749]  ? putname+0x4c/0x60
  [   98.239751]  ? do_sys_open+0x13e/0x2c0
  [   98.239780]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
  [   98.239782]  SyS_ioctl+0x79/0x90
  [   98.239786]  do_syscall_64+0x73/0x130
  [   98.239790]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  
  ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Mon Oct 29 13:13:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
     Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
  InstallationDate: Installed on 2018-10-15 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 14u G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.01.08
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.50.00
  dmi.chassis.asset.tag: 5CG8305291
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP ZBook 14u G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git

[Touch-packages] [Bug 1800171] Re: n-m doesn't support iwd as a backend

[Mathieu Trudel-Lapierre]

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

Marking as a duplicate to bug 1800055

** This bug has been marked a duplicate of bug 1800055
   iwd does not work with network manager

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

Title:
  n-m doesn't support iwd as a backend

Status in network-manager package in Ubuntu:
  New

Bug description:
  iwd is an alternative to wpa_supplicant.

  It can be enabled as backend for n-m at run time, but n-m needs to be
  built with support for it.

  iwd is in universe in Cosmic.

  It would be good to get this switched on for DD so that we can test
  and think about making it the default for EE before the next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800171/+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 1800479] [NEW] 18.10 Wayland segmentation fault (11) for any qt application

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Dear all!
Starting from some beta 18.10 i experience continious segv fault in Wayland 
session.
COnfiguration is acer swift 5 with 2 additional 24" dell monitors.
I choose wayland session in gdm. Everything starts smoothly and good, gnome 
applications runs ver good. If i will not use any qt application - everything 
is good.
If i start any qt - graphical server crashes immediately and drops me to gdm 
prompt.
During usual xorg session everything is OK.
Here's what i have in general log:
___
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace:
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea]
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation 
fault at address 0x68
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: Fatal server error:
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE)
Oct 29 16:30:51 dshuvalovpc update-notifier[3412]: Could not open X display
Oct 29 16:30:51 dshuvalovpc gnome-software[3409]: Could not open X display
Oct 29 16:30:52 dshuvalovpc gnome-software[3409]: enabled plugins: 
desktop-categories, fwupd, os-release, packagekit, packagekit-local, 
packagekit-offline, packagekit-proxy, packagekit-refine-repos, packag
___

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

-- 
18.10 Wayland segmentation fault (11)  for any qt application
https://bugs.launchpad.net/bugs/1800479
You received this bug notification because yo

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Konrad]

same here, when monitor is plugged in I mouse coursor is flickering on
host display, additionally sometimes sites do not work correctly when on
screen 2, coursor is flickering too (but much less).

When I've tried to apply solution from #108 after the reboot the second
monitor was not detected at all, I had to revert back my settings.

-

Ubuntu 16.04 version:
Linux 4.15.0-38-generic #41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Graphic cards (when connected):
  *-display   
   description: VGA compatible controller
   product: Broadwell-U Integrated Graphics
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:44 memory:f600-f6ff memory:d000-dfff 
ioport:f000(size=64) memory:c-d
  *-display
   description: VGA compatible controller
   product: Opal XT [Radeon R7 M265]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:08: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:45 memory:e000-efff memory:f700-f703 
ioport:e000(size=256) memory:f704-f705

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1800467] [NEW] qtquickcontrols2-5-private-dev package missing

[Kevin Funk]

Public bug reported:

Looks like there's no qtquickcontrols2-5-private-dev package in Ubuntu
repositories.

This package should install the private headers for the qtquickcontrols2
module.

Private headers expected:

qquickanimatednode_p.h
qquickclippedtext_p.h
qquickiconimage_p.h
qquickiconlabel_p_p.h
qquickpaddedrectangle_p.h
qquickstyle_p.h
qquickstyleselector_p_p.h
qtquickcontrols2-config_p.h
qquickattachedobject_p.h
qquickcolorimage_p.h
qquickiconimage_p_p.h
qquickitemgroup_p.h
qquickplaceholdertext_p.h
qquickstyleplugin_p.h
qquicktheme_p.h
qtquickcontrols2global_p.h
qquickchecklabel_p.h
qquickcolor_p.h
qquickiconlabel_p.h
qquickmnemoniclabel_p.h
qquickproxytheme_p.h
qquickstyleselector_p.h
qquicktumblerview_p.h

** Affects: qtquickcontrols2-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: qtquickcontrols-opensource-src (Ubuntu) =>
qtquickcontrols2-opensource-src (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtquickcontrols-
opensource-src in Ubuntu.
Matching subscriptions: touch
https://bugs.launchpad.net/bugs/1800467

Title:
  qtquickcontrols2-5-private-dev package missing

Status in qtquickcontrols2-opensource-src package in Ubuntu:
  New

Bug description:
  Looks like there's no qtquickcontrols2-5-private-dev package in Ubuntu
  repositories.

  This package should install the private headers for the
  qtquickcontrols2 module.

  Private headers expected:

  qquickanimatednode_p.h
  qquickclippedtext_p.h
  qquickiconimage_p.h
  qquickiconlabel_p_p.h
  qquickpaddedrectangle_p.h
  qquickstyle_p.h
  qquickstyleselector_p_p.h
  qtquickcontrols2-config_p.h
  qquickattachedobject_p.h
  qquickcolorimage_p.h
  qquickiconimage_p_p.h
  qquickitemgroup_p.h
  qquickplaceholdertext_p.h
  qquickstyleplugin_p.h
  qquicktheme_p.h
  qtquickcontrols2global_p.h
  qquickchecklabel_p.h
  qquickcolor_p.h
  qquickiconlabel_p.h
  qquickmnemoniclabel_p.h
  qquickproxytheme_p.h
  qquickstyleselector_p.h
  qquicktumblerview_p.h

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtquickcontrols2-opensource-src/+bug/1800467/+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 1800359] Re: libosmesa6 is not installable in 18.04

[Timo Aaltonen]

your mirror is out of date or something..

apt install libosmesa6
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  libosmesa6
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1280 kB of archives.
After this operation, 4334 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libosmesa6 
amd64 18.0.5-0ubuntu0~18.04.1 [1280 kB]
Fetched 1280 kB in 1s (1745 kB/s)  
Selecting previously unselected package libosmesa6:amd64.
(Reading database ... 48125 files and directories currently installed.)
Preparing to unpack .../libosmesa6_18.0.5-0ubuntu0~18.04.1_amd64.deb ...
Unpacking libosmesa6:amd64 (18.0.5-0ubuntu0~18.04.1) ...
Setting up libosmesa6:amd64 (18.0.5-0ubuntu0~18.04.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...


** Changed in: mesa (Ubuntu)
   Status: New => 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/1800359

Title:
  libosmesa6 is not installable in 18.04

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at
  version 18.0.5-0ubuntu0~18.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libosmesa6 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Oct 28 10:55:42 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2018-10-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=e8def74e-6e50-4d6e-9adb-07d2b230cb55 ro quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1.1~ppa
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1800359/+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 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop

[Launchpad Bug Tracker]

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

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

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

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

Title:
  DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to 
my server.
  Everything connected and worked as it should.

  When I disconnect the VPN, DNS resolution stops working.

  Looking at "systemd-resolve --status" shows that the correct DNS
  server is listed for the interface  when the connection is torn down,
  and I can ping it.  Doing a nslookup setting the server to the IP
  address shown in --status shows that DNS resolution is working
  correctly.

  resolv.conf says nameserver 127.0.0.53

  Restart resolved makes things work again.
  (Also, restarting Network Manager makes it work again.)

  Trying to ping a hostname from the cli when in the broken state yields
  zero output from resolved logs when in debug mode.  Almost like it's
  not even hitting resolved, so this bug could very well be somewhere
  else.

  I've checked, and I can ping 127.0.0.1 and the default routes look OK,
  although there is a route to the VPN server left over.

  I'm all out of ideas.  Any ideas?

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

[Cristian Aravena Romero]

** Description changed:

  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station
+ 
+ ---
+ 
+ CurrentDmesg.txt:
+ [   98.239676] Call Trace:
+ [   98.239685]  v4l_enum_fmt+0x74/0x110 [videodev]
+ [   98.239689]  __video_do_ioctl+0x370/0x380 [videodev]
+ [   98.239692]  ? terminate_walk+0x8e/0xf0
+ [   98.239696]  video_usercopy+0x24d/0x640 [videodev]
+ [   98.239700]  ? video_ioctl2+0x20/0x20 [videodev]
+ [   98.239704]  video_ioctl2+0x15/0x20 [videodev]
+ [   98.239709]  v4l2_ioctl+0xc8/0xf0 [videodev]
+ [   98.239741]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
+ [   98.239744]  do_vfs_ioctl+0xa8/0x630
+ [   98.239746]  ? kmem_cache_free+0x1b3/0x1e0
+ [   98.239749]  ? putname+0x4c/0x60
+ [   98.239751]  ? do_sys_open+0x13e/0x2c0
+ [   98.239780]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
+ [   98.239782]  SyS_ioctl+0x79/0x90
+ [   98.239786]  do_syscall_64+0x73/0x130
+ [   98.239790]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
+ 
+ ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Mon Oct 29 13:13:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
-Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
+  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
+    Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
  InstallationDate: Installed on 2018-10-15 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd 
-  Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd
+  Bus 001 Device 002: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 14u G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.01.08
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.50.00
  dmi.chassis.asset.tag: 5CG8305291
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP ZBook 14u G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station

  ---

  CurrentDmesg.txt:
  [   98.239676] Call Trace:
  [   98.239685]  v4l_enum_fmt+0x74/0x110 [videodev]
  [   98.239689]  __video_do_ioctl+0x370/0x380 [videodev]
  [   98.239692]  ? terminate_walk+0x8e/0xf0
  [   98.

[Touch-packages] [Bug 1800458] Re: Xorg freeze

[Cristian Aravena Romero]

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19

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

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

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station

  ---

  CurrentDmesg.txt:
  [   98.239676] Call Trace:
  [   98.239685]  v4l_enum_fmt+0x74/0x110 [videodev]
  [   98.239689]  __video_do_ioctl+0x370/0x380 [videodev]
  [   98.239692]  ? terminate_walk+0x8e/0xf0
  [   98.239696]  video_usercopy+0x24d/0x640 [videodev]
  [   98.239700]  ? video_ioctl2+0x20/0x20 [videodev]
  [   98.239704]  video_ioctl2+0x15/0x20 [videodev]
  [   98.239709]  v4l2_ioctl+0xc8/0xf0 [videodev]
  [   98.239741]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
  [   98.239744]  do_vfs_ioctl+0xa8/0x630
  [   98.239746]  ? kmem_cache_free+0x1b3/0x1e0
  [   98.239749]  ? putname+0x4c/0x60
  [   98.239751]  ? do_sys_open+0x13e/0x2c0
  [   98.239780]  ? cmd_handler_mi_batch_buffer_start+0x6a2/0x710 [i915]
  [   98.239782]  SyS_ioctl+0x79/0x90
  [   98.239786]  do_syscall_64+0x73/0x130
  [   98.239790]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Mon Oct 29 13:13:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
     Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
  InstallationDate: Installed on 2018-10-15 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 14u G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.01.08
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.50.00
  dmi.chassis.asset.tag: 5CG8305291
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP ZBook 14u G5
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://

[Touch-packages] [Bug 1800462] [NEW] Request to add "ens" and "bond" interface to interface-order

[Suho Meso]

Public bug reported:

Can you please add new systemd interfaces "ens*" and "bond*" to interface-order?
The interfaces are covered with the "*" in the last line, but IPv6 should be 
preferred to IPv4.
Also, the rndssd interface is not covered.
You should add something like *.rdnssd. The actual interface is called "000".
/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x
/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x
/run/resolvconf/interface/ens3.dhclient:domain abz.com
/run/resolvconf/interface/ens3.dhclient:search abz.com
/run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.x

root@host:/etc/resolvconf# dpkg -l | grep resolvconf
ii resolvconf 1.78ubuntu6 all name server information handler
root@host:/etc/resolvconf# dpkg -l | grep rdnssd
ii rdnssd 1.0.1-1ubuntu2 amd64 IPv6 recursive DNS server discovery daemo

root@host:/etc/resolvconf# cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

root@host:/etc/resolvconf# uname -a
Linux host 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  Request to add "ens" and "bond" interface to interface-order

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Can you please add new systemd interfaces "ens*" and "bond*" to 
interface-order?
  The interfaces are covered with the "*" in the last line, but IPv6 should be 
preferred to IPv4.
  Also, the rndssd interface is not covered.
  You should add something like *.rdnssd. The actual interface is called "000".
  /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x
  /run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::x
  /run/resolvconf/interface/ens3.dhclient:domain abz.com
  /run/resolvconf/interface/ens3.dhclient:search abz.com
  /run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.x

  root@host:/etc/resolvconf# dpkg -l | grep resolvconf
  ii resolvconf 1.78ubuntu6 all name server information handler
  root@host:/etc/resolvconf# dpkg -l | grep rdnssd
  ii rdnssd 1.0.1-1ubuntu2 amd64 IPv6 recursive DNS server discovery daemo

  root@host:/etc/resolvconf# cat /etc/issue
  Ubuntu 16.04.4 LTS \n \l

  root@host:/etc/resolvconf# uname -a
  Linux host 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1800462/+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 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

So for anyone affected by this bug:

1. Make sure it actually is this bug (mentions precisely 
_ZlsRSoRKN3APT9PrettyPkgE, not another mangled name)
2. Provide output of apt-cache policy apt libapt-pkg5.0

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1800458] [NEW] Xorg freeze

[Unknown]

Public bug reported:

Whenever i dock my laptop it freezes and I have to power it off. Black screen.
HP 2013 UltraSlim Docking Station

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
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: Mon Oct 29 13:13:09 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
   Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
InstallationDate: Installed on 2018-10-15 (14 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ZBook 14u G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2018
dmi.bios.vendor: HP
dmi.bios.version: Q78 Ver. 01.01.08
dmi.board.name: 83B2
dmi.board.vendor: HP
dmi.board.version: KBC Version 04.50.00
dmi.chassis.asset.tag: 5CG8305291
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.01.08:bd06/05/2018:svnHP:pnHPZBook14uG5:pvr:rvnHP:rn83B2:rvrKBCVersion04.50.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP ZBook 14u G5
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze 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/1800458

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever i dock my laptop it freezes and I have to power it off. Black screen.
  HP 2013 UltraSlim Docking Station

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Mon Oct 29 13:13:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
 Subsystem: Hewlett-Packard Company Lexa XT [Radeon PRO WX 3100] [103c:83b5]
  InstallationDate: Installed on 2018-10-15 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5e7 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 14u G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=d3e1c50d-47e9-40de-b6a9-d01ad701f5fd ro quiet splash vt.handoff=1
  SourcePack

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

tobst4r, then your system is broken. You are mixing artful and xenial,
which is not a supported thing to do.

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

I do not believe that apt 1.2.29 with libapt-pkg5.0 1.5.1 fails with
that error, btw. I believe it fails with:

symbol _ZN9pkgSystem9LockInnerEv version APTPKG_5.0 not defined in file
libapt-pkg.so.5.0 with link time reference

Which is expected (since 1.2.29 gained a new frontend locking symbol),
and brings us back to the point of partial upgrades not being supported.

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1644643] Re: apt failed to run due to link time reference error

[Tobias]

For me it works after installing apt 1.2.9 and libapt-pkg5.0_1.2.29_amd64.deb
When i now run apt update && apt upgrade, it tells me that libapt-pkg5.0 was 
kept back.

If i now run apt install -f it will install libapt-pkg5.0:amd64 (1.5.1)

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

So, 1.5.1 is from artful (and that's EOL), and 1.2.29 is from xenial.
Partial upgrades are not supported. I suggest you find some help
returning your system to xenial, such as forums, mailing lists, or IRC.

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

[Matthias Klose]

it's ongoing, but these look like all these are also in the release
pocket. will summarize later

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Committed
Status in python3.6 source package in Cosmic:
  Fix Committed

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+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 1644643] Re: apt failed to run due to link time reference error

[Tobias]

The problem occured after upgrading to:

libapt-pkg5.0:amd64 (1.5.1)
apt (1.2.29)

It works well wit apt 1.2.10 and libapt 1.2.10

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1768026] Re: echo message hides cursor

[Yariv]

Could you backport the fix to the 18.04 LTS? This is super annoying for
vim users.

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

Title:
  echo message hides cursor

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/w0rp/ale/issues/1536#issuecomment-385056702
  upstream bug https://github.com/vim/vim/issues/2612

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1453-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:16:35 2018
  InstallationDate: Installed on 2017-05-17 (347 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/vim/+bug/1768026/+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 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap

[Mantas Kriaučiūnas]

** Description changed:

- Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed 
or swap is encrypted.
+ [Impact]
+ 
+ Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled 
(for example zram-config installed) or swap is encrypted.
+ Today lots of users have SSD instead of HDD disk drives and use zram swap 
instead of swap partition or swap file, but if initrd is generated when zram 
swap is enabled then system can become "unbootable" from the user's perspective 
(Users with SSD storage doesn't wait 2 or more minutes...)
+ 
+ This bug is already fixed in Debian initramfs-tools ver 0.132, please accept 
this simple 3 lines patch from Debian into Ubuntu 18.04 LTS
+ 
https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d
+ 
+ [Test Case]
+ Install zram-config package and regenerate and initrd, for example with 
+ sudo update-initramfs -u
+ 
  When generating initrd I get this message in terminal:
  
  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
- I: Set the RESUME variable to override 
this.###.] 
+ I: Set the RESUME variable to override 
this.###.]
  
  So the local-premount script in initramfs was waiting for a swap device
  that was not available, until it timed out. The relevant message was
  gave up waiting for suspend/resume device.
  
- To disable this (as resuming from swap is not possible with an encrypted
- swap, and I don't use hibernation anyway), I modified this file: /etc
- /initramfs-tools/conf.d/resume. In this file, a line with RESUME=none
- (instead of the UUID that was here) will disable waiting for a resume
- device.
+ [Regression Potential]
  
- Run sudo update-initramfs -u to apply the changes.
+ None, patch simply adds case for /dev/zram*:
  
- Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10
+ 60case "$resume_auto" in
+ 61/dev/zram*)
+ 62ephemeral=true
+ 63;;
+ 64esac
+ 
+ 
+ [Other Info]
+ Manual method to disable this (as resuming from swap is not possible with an 
encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add 
(or change) line
+ RESUME=none
+ (instead of the UUID that was here) will disable waiting for a resume device.
+ and run sudo update-initramfs -u to apply the changes.

** Summary changed:

- Slow startup with zram-config installed (/dev/zram0) or encrypted swap
+ [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap

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

Title:
  [SRU] Slow startup with zram-config installed (/dev/zram0) or
  encrypted swap

Status in Default settings and artwork for Baltix OS:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zram-config package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  [Impact]

  Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled 
(for example zram-config installed) or swap is encrypted.
  Today lots of users have SSD instead of HDD disk drives and use zram swap 
instead of swap partition or swap file, but if initrd is generated when zram 
swap is enabled then system can become "unbootable" from the user's perspective 
(Users with SSD storage doesn't wait 2 or more minutes...)

  This bug is already fixed in Debian initramfs-tools ver 0.132, please accept 
this simple 3 lines patch from Debian into Ubuntu 18.04 LTS
  
https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d

  [Test Case]
  Install zram-config package and regenerate and initrd, for example with 
  sudo update-initramfs -u

  When generating initrd I get this message in terminal:

  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
  I: Set the RESUME variable to override 
this.###.]

  So the local-premount script in initramfs was waiting for a swap
  device that was not available, until it timed out. The relevant
  message was gave up waiting for suspend/resume device.

  [Regression Potential]

  None, patch simply adds case for /dev/zram*:

  60case "$resume_auto" in
  61/dev/zram*)
  62ephemeral=true
  63;;
  64esac

  
  [Other Info]
  Manual method to disable this (as resuming from swap is not possible with an 
encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add 
(or change) line
  RESUME=none
  (instead of the UUID that was here) will disable waiting for a resume device.
  and run sudo update-initramfs -u to apply the changes.

To manage n

[Touch-packages] [Bug 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap

[Launchpad Bug Tracker]

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

** Changed in: zram-config (Ubuntu)
   Status: New => Confirmed

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

Title:
  Slow startup with zram-config installed (/dev/zram0) or encrypted swap

Status in Default settings and artwork for Baltix OS:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zram-config package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed 
or swap is encrypted.
  When generating initrd I get this message in terminal:

  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
  I: Set the RESUME variable to override 
this.###.] 

  So the local-premount script in initramfs was waiting for a swap
  device that was not available, until it timed out. The relevant
  message was gave up waiting for suspend/resume device.

  To disable this (as resuming from swap is not possible with an
  encrypted swap, and I don't use hibernation anyway), I modified this
  file: /etc/initramfs-tools/conf.d/resume. In this file, a line with
  RESUME=none (instead of the UUID that was here) will disable waiting
  for a resume device.

  Run sudo update-initramfs -u to apply the changes.

  Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1781746] Re: Slow startup with zram-config installed (/dev/zram0) or encrypted swap

[Mantas Kriaučiūnas]

This issue is fixed in Debian, initramfs-tools version 0.132, please
accept this simple, 3 lines patch from Debian into Ubuntu 18.04

https://salsa.debian.org/kernel-team/initramfs-
tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d

** Patch added: "Patch from Debian initramfs-tools 0.132 to fix booting when 
zram swap is enabled"
   
https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1781746/+attachment/5206679/+files/312393b0cf1231125eeff3d1a2b6b778a935c21d.diff

** Tags added: bionic patch patch-accepted-debian

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

Title:
  Slow startup with zram-config installed (/dev/zram0) or encrypted swap

Status in Default settings and artwork for Baltix OS:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zram-config package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Ubuntu 18.04 startup slowdowns for 30-60 seconds when zram-config installed 
or swap is encrypted.
  When generating initrd I get this message in terminal:

  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
  I: Set the RESUME variable to override 
this.###.] 

  So the local-premount script in initramfs was waiting for a swap
  device that was not available, until it timed out. The relevant
  message was gave up waiting for suspend/resume device.

  To disable this (as resuming from swap is not possible with an
  encrypted swap, and I don't use hibernation anyway), I modified this
  file: /etc/initramfs-tools/conf.d/resume. In this file, a line with
  RESUME=none (instead of the UUID that was here) will disable waiting
  for a resume device.

  Run sudo update-initramfs -u to apply the changes.

  Please, fix it already. Duplicate of Bug #1768230 on Ubuntu 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1795407] Re: python-apt frontend locking

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt - 1.6.3

---
python-apt (1.6.3) bionic; urgency=medium

  * Frontend locking and related locking improvements (LP: #1795407)
- apt.Cache: Keep / Re-establish the system lock in commit()
- apt.Cache: Keep archive locked during commit()/ in fetch_archives()
- apt.Cache: Reinstate locks in a finally / run dpkg inside try
- Introduce frontend locking
- Convert apt.Cache.commit and apt_pkg.DepCache.commit to FE lock
  * Other changes to make that work:
- Cherry-pick apt_pkg.Error type hint from 1.7
- travis CI: bionic only; stretch does not have FE locking nor PPA
  * As always, updated mirror lists

 -- Julian Andres Klode   Mon, 01 Oct 2018 16:00:14
+0200

** Changed in: python-apt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  python-apt frontend locking

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:

  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.

  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().

  The fix is based on the apt fix, which makes apt_pkg.SystemLock()
  manage both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.

  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it
  itself.

  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run

  The locking behavior can be observed via strace.

  [Regression potential]
  The dpkg lock changed the most: Some lock counting might go wrong and 
programs might fail as a result. Any problems will be isolated, though - dpkg 
still acquires its locks, and if a lock miscount happens, apt would not tell 
dpkg to skip acquiring the frontend lock, so even if we were losing the lock 
anywhere, dpkg would still try to acquire it and not run unlocked.

  The archive lock done by commit()/fetch_archives() in apt.Cache() is
  now hold as long as the fetcher object exists though (as it uses the
  fetcher's get_lock method), which might cause unexpected behavior in
  apps not expecting that.

  The lists/ lock is unaffected by the changes, so there should not be
  any regressions when it comes to updating index files.

  [Other info (1)]
  CI changes: There were some improvements to type hints for mypy needed to 
make type checks pass, and changes to the CI's Dockerfile to pull a new apt 
from the apt stable PPA (as a new enough apt is only in unapproved atm). 
Neither of those files are used anywhere outside of the package, so they should 
not cause any problems.

  [Other info (2)]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

  - This SRU depends on the apt SRU above, and breaks unattended-
  upgrades in bionic without its SRU due to a bug in the u-u code in
  handling the new API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1164016] Re: restore type-ahead find

[javier]

I changed to Dolphin :-(

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1795407] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for python-apt has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  python-apt frontend locking

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:

  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.

  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().

  The fix is based on the apt fix, which makes apt_pkg.SystemLock()
  manage both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.

  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it
  itself.

  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run

  The locking behavior can be observed via strace.

  [Regression potential]
  The dpkg lock changed the most: Some lock counting might go wrong and 
programs might fail as a result. Any problems will be isolated, though - dpkg 
still acquires its locks, and if a lock miscount happens, apt would not tell 
dpkg to skip acquiring the frontend lock, so even if we were losing the lock 
anywhere, dpkg would still try to acquire it and not run unlocked.

  The archive lock done by commit()/fetch_archives() in apt.Cache() is
  now hold as long as the fetcher object exists though (as it uses the
  fetcher's get_lock method), which might cause unexpected behavior in
  apps not expecting that.

  The lists/ lock is unaffected by the changes, so there should not be
  any regressions when it comes to updating index files.

  [Other info (1)]
  CI changes: There were some improvements to type hints for mypy needed to 
make type checks pass, and changes to the CI's Dockerfile to pull a new apt 
from the apt stable PPA (as a new enough apt is only in unapproved atm). 
Neither of those files are used anywhere outside of the package, so they should 
not cause any problems.

  [Other info (2)]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

  - This SRU depends on the apt SRU above, and breaks unattended-
  upgrades in bionic without its SRU due to a bug in the u-u code in
  handling the new API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers

[Sebastien Bacher]

** Tags added: rls-cc-incoming

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

Title:
  The wlan/bt hotkey doesn't work for all Dell Latitude and Precision
  computers

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New
Status in systemd source package in DD-Series:
  New

Bug description:
  [Impact]

   * All Dell Latitude and Precision computer users can not use the
  wlan/bt hotkey.

  [Test Case]

   * Use any Dell Latitude and Precision computer to check the wlan/bt
  hotkey.

   * If you don't have the computer above, you can use the following
  command to check, and the expected output is "KEYBOARD_KEY_88=!wlan"
  instead of "KEYBOARD_KEY_88=!".

   `systemd-hwdb query
  
evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  | grep KEYBOARD_KEY_88`

  [Regression Potential]

   * No regression

  [Other Info]

   * None

  Just install the official Ubuntu 18.10 on any Dell Latitude or
  Precision computer and press wlan/bt hotkey on the keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 15:37:41 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 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: 10/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.0.24
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.

[Launchpad Bug Tracker]

This bug was fixed in the package friendly-recovery - 0.2.31ubuntu2

---
friendly-recovery (0.2.31ubuntu2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * Actually use a friendly-recovery.target which systemd boots to
using a generator for default.target symlink. This ensures that
one is not in the middle of a boot transaction during recovery
and can start/stop/change systemd units without interference.
  * Cleanup lintian warnings. (LP: #1766872)

 -- Eric Desrochers   Tue, 02 Oct 2018
14:43:12 -0400

** Changed in: friendly-recovery (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1475945] Re: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1786574
   remove i2c-i801 from blacklist

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

Title:
  blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus
  other hardware

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  file:
  /etc/modprobe.d/blacklist.conf

  contains the text:
  # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
  blacklist i2c_i801

  note: actually the correct LP id appears to be
  https://bugs.launchpad.net/bugs/16602

  after short discussion at
  https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 I'm
  raising this as a bug

  as well as preventing trackpad detection in the case of Acer C710,
  there is an older bug open at https://bugs.launchpad.net/bugs/857175.
  Here this same blacklist entry breaks some functionality for a
  Thinkpad T41. In turn, that bug includes a reference to another source
  (http://permalink.gmane.org/gmane.linux.drivers.i2c/9120) where the
  blacklist entry has required support effort.

  lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1475945/+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 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

[Łukasz Zemczak]

The python3-defaults upload lists a lot autopkgtest regression. Someone
has to look through them, check if they're regressions or not and/or re-
run if needed.

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Committed
Status in python3.6 source package in Cosmic:
  Fix Committed

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+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 1786574] Please test proposed package

[Andy Whitcroft]

Hello AaronMa, or anyone else affected,

Accepted kmod into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/kmod/22-1ubuntu5.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Committed
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Cosmic:
  Fix Committed

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Please test proposed package

[Andy Whitcroft]

Hello AaronMa, or anyone else affected,

Accepted kmod into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: kmod (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Committed
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Cosmic:
  Fix Committed

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Re: remove i2c-i801 from blacklist

[Andy Whitcroft]

Hello AaronMa, or anyone else affected,

Accepted kmod into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/kmod/25-1ubuntu1.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: kmod (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: kmod (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Committed
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Cosmic:
  Fix Committed

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1800428] Re: graphics

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description 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. 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. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1800428

Title:
  graphics

Status in Ubuntu:
  Incomplete

Bug description:
  brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 29 13:25:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  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:0601]
  InstallationDate: Installed on 2018-10-28 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire 5733Z
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=59b65994-6d4b-43c1-a661-1217840ccd01 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnAcer:bvrV1.02:bd04/20/2011:svnAcer:pnAspire5733Z:pvrV1.02:rvnAcer:rnAspire5733Z:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.02
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1800428/+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 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

apt  1.2.15ubuntu0.2 properly depends on libapt-pkg5.0 (>=
1.2.15ubuntu0.2), so assuming that this apt is installed, and the system
is not broken, this must be working (as it passed verification).

In any case, this bug is incomplete, as it does not clearly mention
which versions of apt, libapt-pkg5.0 are installed.

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

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1644643] Re: apt failed to run due to link time reference error

[Julian Andres Klode]

Downgrading libapt-private especially should not make a difference, as
it's in the same package as apt.

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

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