[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Antonio Marra]

I've update all packages this morning, but they don't fix this.
Please note that this behavior doesn't always show (very often but not every 
time). 
I can confirm that when it occours, I can manage wifi, ethernet and VPNs 
profiles from Gnome Control Center, but not from gnome top menu.

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+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 1774029] Re: Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

[manuw2009]

boot-info file...

** Attachment added: "Boot-Info_20180530_1705.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774029/+attachment/5146559/+files/Boot-Info_20180530_1705.txt

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

Title:
  Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

Status in systemd package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot 
with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I 
tried 4.14 & 4.16 as well, to no avail).
  Booting with the 4.4 kernel leads to the login screen and everything works 
OK, while booting with the 4.15 kernel remains stalled on the Ubuntu startup 
screen with dots, ESC shows traces stuck? on "Reached target Network is Online"
  I can successfully boot the 18.04 desktop image though, so I am assuming the 
issue comes from configuration files and not from the kernel itself. Any help 
would be highly appreciated !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Tue May 29 19:05:08 2018
  InstallationDate: Installed on 2014-11-19 (1286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-22 20:51:41.459776
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774029/+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 1774216] [NEW] gdb incorrectly performs modulo 32 on 64 bit operands for 'x' command

[George Shuklin]

Public bug reported:

https://stackoverflow.com/questions/50607748/how-to-force-gdb-to-view-
at-a-given-address

$ gdb

(gdb) x 0x7f3ca4f68c20
0xa4f68c20: Cannot access memory at address 0xa4f68c20

Actual results: Attemp to read a value from 0xa4f68c20
Expected results: attempt to read a value from 0x7f3ca4f68c20.

This bug is present in GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
(bionic)

This bug does not present in GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5)
7.11.1 (xenial)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdb 8.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed May 30 18:20:11 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-22 (342 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: gdb
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gdb incorrectly performs modulo 32 on 64 bit operands for 'x' command

Status in gdb package in Ubuntu:
  New

Bug description:
  https://stackoverflow.com/questions/50607748/how-to-force-gdb-to-view-
  at-a-given-address

  $ gdb

  (gdb) x 0x7f3ca4f68c20
  0xa4f68c20: Cannot access memory at address 0xa4f68c20

  Actual results: Attemp to read a value from 0xa4f68c20
  Expected results: attempt to read a value from 0x7f3ca4f68c20.

  This bug is present in GNU gdb (Ubuntu 8.1-0ubuntu3)
  8.1.0.20180409-git (bionic)

  This bug does not present in GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5)
  7.11.1 (xenial)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed May 30 18:20:11 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-22 (342 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1774216/+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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Andreas Hasenack]

Upstream bug still not touched, and patch still not applied not even in
the ubuntu cosmic package, which is still a sync.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Andreas Hasenack]

Reproduced on trusty. In xenial the sleed.d packagekit hook is gone.

sudo apt install pm-utils packagekit

I hacked /usr/lib/pm-utils/pm-functions to log which hook it was
running, and forced a suspend with "pm-suspend". In my case I got
multiple runs of 98video-quirk-db-handler right after the incorrect
packagekit directory was hit:

hook var is
base is 99video
runing hook /usr/lib/pm-utils/sleep.d/99video
hook var is /usr/lib/pm-utils/sleep.d/99video
base is 98video-quirk-db-handler
runing hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
hook var is /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
base is 95packagekit
runing hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
hook var is /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler
base is 95led
runing hook /usr/lib/pm-utils/sleep.d/95led
hook var is /usr/lib/pm-utils/sleep.d/95led
base is 95hdparm-apm
...

With the proposed fix, the packagekit hook isn't run, and we also don't
get double runs of other hooks.

So the fix could be what is proposed, or/and moving the packagekit hook
to the right place.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+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 1773517] Re: lightdm takes too long to show up

[kenn]

I found the two bugs below may be related to my bug report. Removing the
accountsservice check of lightdm will fix the issue.

This bug is fixed, if it's not a regression, that fix doesn't work on the slow 
greeter problem.
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1443178

This one is still pending.
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791

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

Title:
  lightdm takes too long to show up

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04.4 with multiarch support. When I start the
  laptop it boots well till it reaches the lightdm screen. When the
  login text appears, screen goes black about 1.5-2 minutes then lightdm
  screen shows up. I have three users, I noticed that each user takes 25
  seconds timeout to complete the process.

  journalctl -b0 _SYSTEMD_UNIT=lightdm.service
  
  -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 
MSK. --
  May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1001: Timeout was reached
  May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User1000: Timeout was reached
  May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error 
updating user /org/freedesktop/Accounts/User64055: Timeout was reached
  May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error 
getting user list from org.freedesktop.Accounts: Timeout was reached
  May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" was met by user ""
  May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened 
for user  by (uid=0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => New

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1767292] Re: The bluetooth mouse cannot connect after sleep mode.

[Sarah]

We have tested this thoroughly at our office and found that it will
reconnect immediately after a reboot but will not on suspend/sleep. This
appears to be new when updating to 18.04 LTS.

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

Title:
  The bluetooth mouse cannot connect after sleep mode.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bluetooth mouse cannot connect after sleep mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giacomo1998 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Apr 27 09:49:41 2018
  InstallationDate: Installed on 2017-04-13 (378 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001PMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001PMC
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1767292/+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 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.103ubuntu4.11

---
initramfs-tools (0.103ubuntu4.11) trusty; urgency=medium

  * hook-functions: handle md arrays with nvme disk members. (LP:
#1771557)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Wed, 16 May 2018
09:47:01 -0300

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.

  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.

  (lsblk output of my test env:

  nvme0n1 259:0010G  0 disk
  └─nvme0n1p1 259:1010G  0 part
    └─md0   9:0010G  0 raid1 /
  nvme1n1 259:2010G  0 disk
  └─nvme1n1p1 259:3010G  0 part
    └─md0   9:0010G  0 raid1 /
  )

  2. Once system is booted, modify the "/etc/initramfs-
  tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep".

  3. Update your initramfs by running something like:
  "update-initramfs -u -k "

  The initramfs creating procedure will fail, unless the patch from this
  LP is present.

  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).

  [Other Info]
  * This issue is based on Debian bug #785147: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

  * Only Trusty is affected, Xenial and late contains the full fix as
  mentioned above :

  $ git describe --contains  8ac52dc0
  v0.121_rc1~11

  $ git describe --contains 3cb744c9
  v0.121_rc1~11

  $ rmadison initramfs-tools

   initramfs-tools | 0.103ubuntu4| trusty   | source, all
   ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates   | source, all
   initramfs-tools | 0.122ubuntu8| xenial   | source, all
   initramfs-tools | 0.122ubuntu8.11 | xenial-updates   | source, all
   initramfs-tools | 0.125ubuntu12   | artful   | source, all
   initramfs-tools | 0.125ubuntu12.1 | artful-updates   | source, all
   initramfs-tools | 0.130ubuntu3| bionic   | source, all
   initramfs-tools | 0.130ubuntu6| cosmic   | source, all

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1773268] Re: locked out of system when upgrading to bionic from xenial

[Cyrus Harmon]

Apport output attached.

** Attachment added: "apport.lightdm.je6ylqei.apport"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773268/+attachment/5146513/+files/apport.lightdm.je6ylqei.apport

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

Title:
  locked out of system when upgrading to bionic from xenial

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I was attempting to upgrade to bionic from xenial using do-release-
  upgrade but forgot to turn off screen locking. After an hour of
  inactivity, I ended up at the login screen but the keyboard won't
  allow me to enter keys in the login window and clicking the field
  results in a bizarre repeated "Failed to authenticate" message. See
  attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773268/+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 1660277] Re: AV Reciever (Marantz NR1506) pairs but won't connect (Resource temporarily unavailable)

[Launchpad Bug Tracker]

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

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

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

Title:
  AV Reciever (Marantz NR1506) pairs but won't connect (Resource
  temporarily unavailable)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am able to pair with my AV Reciever, but it won't connect.
  Pulseaudio bluetooth modules are installed and loaded. Tried
  connecting via hcitool and bluetoothctl, always the same error.
  Attached bluetoothd verbose logfile.

  Package / System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy bluez
  bluez:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy bluetooth
  bluetooth:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy pulseaudio
  pulseaudio:
Installiert:   1:9.0-2ubuntu2.1

  $ apt-cache policy pulseaudio-module-bluetooth 
  pulseaudio-module-bluetooth:
Installiert:   1:9.0-2ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1660277/+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 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Christopher M. Penalver]

Issue also happening in Artful as per:
https://bugs.launchpad.net/bugs/1772425

** Tags added: artful

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

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

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

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

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

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

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

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

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

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

  default = 'ubuntu'

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

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

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

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

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

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

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

[Christopher M. Penalver]

Adding Apport (Ubuntu) in case this is due to Apport not working
correctly, changes would need to happen in LO+Apport, etc.

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

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

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

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

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

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

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

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

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

  default = 'ubuntu'

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

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

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

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

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

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

[Touch-packages] [Bug 1771557] Update Released

[Adam Conrad]

The verification of the Stable Release Update for initramfs-tools 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1771557

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.

  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.

  (lsblk output of my test env:

  nvme0n1 259:0010G  0 disk
  └─nvme0n1p1 259:1010G  0 part
    └─md0   9:0010G  0 raid1 /
  nvme1n1 259:2010G  0 disk
  └─nvme1n1p1 259:3010G  0 part
    └─md0   9:0010G  0 raid1 /
  )

  2. Once system is booted, modify the "/etc/initramfs-
  tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep".

  3. Update your initramfs by running something like:
  "update-initramfs -u -k "

  The initramfs creating procedure will fail, unless the patch from this
  LP is present.

  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).

  [Other Info]
  * This issue is based on Debian bug #785147: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

  * Only Trusty is affected, Xenial and late contains the full fix as
  mentioned above :

  $ git describe --contains  8ac52dc0
  v0.121_rc1~11

  $ git describe --contains 3cb744c9
  v0.121_rc1~11

  $ rmadison initramfs-tools

   initramfs-tools | 0.103ubuntu4| trusty   | source, all
   ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates   | source, all
   initramfs-tools | 0.122ubuntu8| xenial   | source, all
   initramfs-tools | 0.122ubuntu8.11 | xenial-updates   | source, all
   initramfs-tools | 0.125ubuntu12   | artful   | source, all
   initramfs-tools | 0.125ubuntu12.1 | artful-updates   | source, all
   initramfs-tools | 0.130ubuntu3| bionic   | source, all
   initramfs-tools | 0.130ubuntu6| cosmic   | source, all

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1767292] Re: The bluetooth mouse cannot connect after sleep mode.

[Sarah]

We can also confirm that it does reconnect after toggling airplane mode
on and off but still not connecting after suspend/sleep.

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

Title:
  The bluetooth mouse cannot connect after sleep mode.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bluetooth mouse cannot connect after sleep mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giacomo1998 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Apr 27 09:49:41 2018
  InstallationDate: Installed on 2017-04-13 (378 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001PMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001PMC
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1767292/+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 1332959] Re: When you press the "print screen" key Firefox shows the full-screen message, making impossible to take screen-shots from videos without this notification

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => New

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

Title:
  When you press the "print screen" key Firefox shows the full-screen
  message, making impossible to take screen-shots from videos without
  this notification

Status in Mozilla Firefox:
  New
Status in Light Display Manager:
  Invalid
Status in Unity:
  Invalid
Status in firefox package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  
  HOW TO REPRODUCE
  

  1. In the Firefox browser, open a video played using an HTML 5 web-player 
(for example: http://youtu.be/wWC_WZ7gd6g)
  2. Click on the full screen button.
  3. Press the "print screen" key.

  
  **
  EXPECTED BEHAVIOUR
  **

  - To have taken an screen-shot of how the screen looked at that
  moment.

  **
  REAL BEHAVIOUR
  **

  - A message telling you went full screen appears in the screen-shot.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 30.0+build1-0ubuntu0.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  es20490446e   1959 F pulseaudio
   /dev/snd/controlC1:  es20490446e   1959 F pulseaudio
   /dev/snd/controlC0:  es20490446e   1959 F pulseaudio
  BuildID: 20140608211622
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Jun 22 15:37:57 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.130  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a226e310-01ec-4d7b-9bf6-29cc52140606
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=30.0/20140608211622 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu2
   icedtea-7-plugin  1.5-1ubuntu1
   totem-mozilla 3.10.1-1ubuntu4
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-a226e310-01ec-4d7b-9bf6-29cc52140606
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1332959/+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 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Confirmed
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1774246] [NEW] package libatk-adaptor (not installed) failed to install/upgrade: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from other ins

[Robert]

Public bug reported:

xubuntu
installed Steam
installed System Shock 2
tried to start it from Steam; did not work.
installed wine1.6
tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

Error install :

Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
 trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
Processing triggers for libc-bin (2.23-0ubuntu10) ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libatk-adaptor (not installed)
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
Date: Wed May 30 20:24:01 2018
DuplicateSignature:
 package:libatk-adaptor:(not installed)
 Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
InstallationDate: Installed on 2017-08-16 (286 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: at-spi2-atk
Title: package libatk-adaptor (not installed) failed to install/upgrade: trying 
to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different 
from other instances of package libatk-adaptor:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: at-spi2-atk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

** Summary changed:

- installed wine; after start program needed to install packages; it crashed: 
package libatk-adaptor (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from 
other instances of package libatk-adaptor:i386
+ package libatk-adaptor (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from 
other instances of package libatk-adaptor:i386

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

Title:
  package libatk-adaptor (not installed) failed to install/upgrade:
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which
  is different from other instances of package libatk-adaptor:i386

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  xubuntu
  installed Steam
  installed System Shock 2
  tried to start it from Steam; did not work.
  installed wine1.6
  tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
  installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

  Error install :

  Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
  Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
   trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  Processing triggers for libc-bin (2.23-0ubuntu10) ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libatk-adaptor (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 20:24:01 2018
  DuplicateSignature:
   package:libatk-adaptor:(not installed)
   Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
  InstallationDate: Installed on 2017-08-16 (286 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: at-spi2-atk
  Title: package libatk-adaptor (not installed) failed to 

[Touch-packages] [Bug 1774246] Re: package libatk-adaptor (not installed) failed to install/upgrade: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is different from other insta

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libatk-adaptor (not installed) failed to install/upgrade:
  trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which
  is different from other instances of package libatk-adaptor:i386

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  xubuntu
  installed Steam
  installed System Shock 2
  tried to start it from Steam; did not work.
  installed wine1.6
  tried to run autorun within the .local/share/Steam/steamapps/common/SS2/bin; 
error missing packages
  installed :sudo apt install libatk-adaptor:i386 libgail-common:i386

  Error install :

  Preparing to unpack .../libatk-adaptor_2.18.1-2ubuntu1_i386.deb ...
  Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
   trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  Processing triggers for libc-bin (2.23-0ubuntu10) ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libatk-adaptor (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 20:24:01 2018
  DuplicateSignature:
   package:libatk-adaptor:(not installed)
   Unpacking libatk-adaptor:i386 (2.18.1-2ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libatk-adaptor_2.18.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  ErrorMessage: trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', 
which is different from other instances of package libatk-adaptor:i386
  InstallationDate: Installed on 2017-08-16 (286 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: at-spi2-atk
  Title: package libatk-adaptor (not installed) failed to install/upgrade: 
trying to overwrite shared '/etc/X11/Xsession.d/90atk-adaptor', which is 
different from other instances of package libatk-adaptor:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1774246/+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 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

[Christopher M. Penalver]

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

** Tags added: bionic

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

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

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

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

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

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

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

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

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

  default = 'ubuntu'

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

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

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

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

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

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

[Touch-packages] [Bug 1774265] [NEW] Heavy flicker/flashing on external monitors using resolutions higher than 1920x1080

[Beau Graham]

Public bug reported:

Laptop model: Lenovo P51 20HH0011US
OS: Fresh install from USB ‘Ubuntu GNOME 16.04.4 LTS’
Monitors: Dell U2415b at 1920x1200, Asus PB278 at 2560x1440

Expected behavior: We install Ubuntu 16.04.4, plug in additional
monitors and those monitors work at the native resolution.

Actual behavior: This one is going to be hard to describe. But when we plug in 
a monitor, that monitor will flicker/flash extremely fast. With both HDMI and 
miniDP outputs. Most of the company has two external monitors and when we plug 
in a second monitor one or both of the external monitors flickered on 14 of the 
15 machines that we tested. We also tested with 20 or so monitors through our 
process of trying to isolate the problem. I will leave links of the video that 
we took of the issue. From the online preview you cannot tell what the problem 
is, but if you download the videos and play them with VLC or something locally, 
you should be able to see what we are talking about. 
https://drive.google.com/file/d/1oZQwIf8uaUEytQPQdihIy3eCpVRLe7-T/view?usp=sharing
https://drive.google.com/file/d/1eBrfXouqXhddobGHZijM_G4qNIKiLtaI/view?usp=sharing


We have noticed that if we change the resolution down to 1920x1080 the issue 
goes away. 

The monitors do not flicker on other models of Lenovo’s that we have tried. 
They also do not flicker with the same computer but running Windows or on any 
macbook that we have tried. The other weird issue is that once the monitor 
starts flickering, it stays flickering for about an hour even without a 
computer plugged into it or if we plug in a different computer that did not 
make that monitor flicker before it was plugged into a P51 running Ubuntu gnome 
16.04.4. 
Our current workaround is to install Ubuntu MATE 16.04.4 instead of gnome. The 
monitors work at native resolutions with MATE. 
Let us know if there is anything else we can do to help with this issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue May 29 15:24:31 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation Device [10de:13b6] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2251]
InstallationDate: Installed on 2018-05-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
MachineType: LENOVO 20HH0011US
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET41W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HH0011US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET41W(1.15):bd10/20/2017:svnLENOVO:pn20HH0011US:pvrThinkPadP51:rvnLENOVO:rn20HH0011US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HH0011US
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Heavy flicker/flashing on external monitors using resolutions higher
  than 1920x1080

Status in xorg package in Ubuntu:
  New

Bug description:
  Laptop model: Lenovo P51 20HH0011US
  OS: Fresh install from USB ‘Ubuntu GNOME 16.04.4 LTS’
  Monitors: Dell U2415b at 1920x1200, Asus PB278 at 2560x1440

  Expected behavior: We install Ubuntu 16.04.4, plug in additional
  monitors and those monitors work 

[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot

[Stanley Sisneros]

In Ubuntu 16.04 I made this work by adding the following to crontab -e

@reboot sleep 15; /sbin/sysctl -p

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

Title:
  Some sysctls are ignored on boot

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  /etc/init.d/procps.sh comes too early in the boot process to apply a
  lot of sysctl's. As it runs before networking modules are loaded and
  filesystems are mounted, there are quite a lot of commonly-used
  sysctl's which are simply ignored on boot and produce errors to the
  console.

  Simply renaming the symlink from S17 to > S40 probably isn't a great
  solution, as there are probably folk who want and expect some sysctl's
  to be applied before filesystems are mounted and so on. However,
  simply ugnoring something as important as sysctl settings isn't really
  on. Administrators expect the settings in /etc/sysctl.conf to take
  effect.

  One sto-gap solution would be to run sysctl -p twice; once at S17 and once at 
S41. There may still be some warnings and errors, but everything would be 
applied. A different, more complex approach might be to re-architect the sysctl 
configuration into something like;
   
  /etc/sysctl.d/$modulename

  and have the userland module-loading binaries take care of applying
  them after modules are loaded. Though this may take care of explicitly
  loaded modules only, I'm not sure.

  Incidentally, /etc/sysctl.conf still refers to
  /etc/networking/options, but hasn't that been deprecated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1774281] [NEW] Username displays incorrectly on login screen

[Matthew]

Public bug reported:

Just did a clean install on a mid 2012 15" macbook pro. Every time that
I get to the login screen, my username appears as strange blocks and
shapes as pictured here:

https://drive.google.com/file/d/0B4DXnUg-
SK6WOG1ybjFTYnBWQ3B6eWVEelR6TmJWcHNJb2ZR/view?usp=sharing


18.04 LTS
xorg:
  Installed: 1:7.7+19ubuntu7
  Candidate: 1:7.7+19ubuntu7
  Version table:
 *** 1:7.7+19ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 15:10:15 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fb]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
MachineType: Apple Inc. MacBookPro9,1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-22-generic ro 
root=UUID=bcac24f1-47fa-44d8-ae55-e5dff5f77a7d 
initrd=boot\initrd.img-4.15.0-22-generic
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-4B7AC7E43945597E
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-4B7AC7E43945597E
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "20180530_145930.jpg"
   
https://bugs.launchpad.net/bugs/1774281/+attachment/5146677/+files/20180530_145930.jpg

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

Title:
  Username displays incorrectly on login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Just did a clean install on a mid 2012 15" macbook pro. Every time
  that I get to the login screen, my username appears as strange blocks
  and shapes as pictured here:

  https://drive.google.com/file/d/0B4DXnUg-
  SK6WOG1ybjFTYnBWQ3B6eWVEelR6TmJWcHNJb2ZR/view?usp=sharing

  
  18.04 LTS
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:10:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fb]
   NVIDIA Corporation GK107M 

[Touch-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

[Christopher M. Penalver]

** Summary changed:

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

** Description changed:

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

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 

Re: [Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[James Grimaldi]

Brian,

I think this the file you want.


On Wed, May 30, 2018 at 11:10 AM, Brian Murray  wrote:

> Could any of the reporters of duplicates of this bug provide their apt-
> clone file for testing? You should be able to find one at /var/log/dist-
> upgrade/apt-clone_system_state.tar.gz. Thanks in advance.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768905
>
> Title:
>   package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
>   problems - leaving triggers unprocessed
>
> Status in apt package in Ubuntu:
>   Incomplete
> Status in menu package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I get this error when I update to 18.04
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: menu 2.1.47ubuntu2
>   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
>   Date: Thu May  3 16:51:28 2018
>   Dependencies:
>gcc-8-base 8-20180414-1ubuntu2
>libc6 2.27-3ubuntu1
>libgcc1 1:8-20180414-1ubuntu2
>libstdc++6 8-20180414-1ubuntu2
>   ErrorMessage: dependency problems - leaving triggers unprocessed
>   InstallationDate: Installed on 2018-04-11 (22 days ago)
>   InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64
> (20180106)
>   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2
>apt  1.6.1
>   SourcePackage: menu
>   Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
> problems - leaving triggers unprocessed
>   UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions
>


-- 
James A. Grimaldi


** Attachment added: "apt-clone_system_state.tar.gz"
   
https://bugs.launchpad.net/bugs/1768905/+attachment/5146695/+files/apt-clone_system_state.tar.gz

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Confirmed

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  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
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1772488] Re: ubuntu tries to report bugs against unofficial repository packages

[Brian Murray]

I'm fairly certain the dialog comes up before all the information has
been gathered so apport doesn't yet know that the package is from an
unofficial repository.

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

Title:
  ubuntu tries to report bugs against unofficial repository packages

Status in apport package in Ubuntu:
  New

Bug description:
  When a program dies a report problem to ubuntu window comes up, even
  if it can't actually report the problem to ubuntu because it isn't an
  official repository package. There is no reason for it to come up in
  the first place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1772488/+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 1660277] Re: AV Reciever (Marantz NR1506) pairs but won't connect (Resource temporarily unavailable)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  AV Reciever (Marantz NR1506) pairs but won't connect (Resource
  temporarily unavailable)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am able to pair with my AV Reciever, but it won't connect.
  Pulseaudio bluetooth modules are installed and loaded. Tried
  connecting via hcitool and bluetoothctl, always the same error.
  Attached bluetoothd verbose logfile.

  Package / System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy bluez
  bluez:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy bluetooth
  bluetooth:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy pulseaudio
  pulseaudio:
Installiert:   1:9.0-2ubuntu2.1

  $ apt-cache policy pulseaudio-module-bluetooth 
  pulseaudio-module-bluetooth:
Installiert:   1:9.0-2ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1660277/+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 1773268] Re: locked out of system when upgrading to bionic from xenial

[Daniel van Vugt]

** Tags added: bionic

** Description changed:

  I was attempting to upgrade to bionic from xenial using do-release-
  upgrade but forgot to turn off screen locking. After an hour of
  inactivity, I ended up at the login screen but the keyboard won't allow
  me to enter keys in the login window and clicking the field results in a
  bizarre repeated "Failed to authenticate" message. See attached
  screenshot.
+ 
+ ---
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2010-04-12 (2970 days ago)
+ InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: lightdm 1.26.0-0ubuntu1
+ PackageArchitecture: amd64
+ ProcCpuinfoMinimal:
+  processor: 3
+  vendor_id: GenuineIntel
+  cpu family   : 6
+  model: 42
+  model name   : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
+  stepping : 7
+  microcode: 0x25
+  cpu MHz  : 1689.366
+  cache size   : 6144 KB
+  physical id  : 0
+  siblings : 4
+  core id  : 3
+  cpu cores: 4
+  apicid   : 6
+  initial apicid   : 6
+  fpu  : yes
+  fpu_exception: yes
+  cpuid level  : 13
+  wp   : yes
+  flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt 
dtherm ida arat pln pts
+  bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
+  bogomips : 6219.77
+  clflush size : 64
+  cache_alignment  : 64
+  address sizes: 36 bits physical, 48 bits virtual
+  power management:
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-24 (5 days ago)
+ UserGroups: adm admin audio cdrom dialout lpadmin mythtv plugdev sambashare

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

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

Title:
  locked out of system when upgrading to bionic from xenial

Status in lightdm package in Ubuntu:
  New

Bug description:
  I was attempting to upgrade to bionic from xenial using do-release-
  upgrade but forgot to turn off screen locking. After an hour of
  inactivity, I ended up at the login screen but the keyboard won't
  allow me to enter keys in the login window and clicking the field
  results in a bizarre repeated "Failed to authenticate" message. See
  attached screenshot.

  ---
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2010-04-12 (2970 days ago)
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: lightdm 1.26.0-0ubuntu1
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 42
   model name   : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
   stepping : 7
   microcode: 0x25
   cpu MHz  : 1689.366
   cache size   : 6144 KB
   physical id  : 0
   siblings : 4
   core id  : 3
   cpu cores: 4
   apicid   : 6
   initial apicid   : 6
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer 
aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt 
dtherm ida arat pln pts
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
   bogomips : 6219.77
   clflush size : 64
   cache_alignment  : 64
   address sizes: 36 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (5 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin mythtv plugdev sambashare

To manage notifications about this bug go to:

[Touch-packages] [Bug 1767858] Re: Ubuntu 16.04 crashed when entering a black screen

[zixuan wang]

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

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

Title:
  Ubuntu 16.04 crashed when entering a black screen

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I did not know why. Following is the header:

  ProblemType: Crash
  DistroRelease: 16.04
  CrashInfo: Xorg crashed on SIGABORT at OsAbort()
  -- End header ---
  Xorg crashed on SIGABORT at OsAbort() is the problem.
  It became crashed everyday at 3PM after I installed Ubuntu 16.04. 
Occasionally, this is bad because I want to write some codes. It maybe still 
became crashed after booting after restarting my computer.

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

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

[Touch-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple lines at a time.

[Mike L]

1) That is correct. Only rebooting into Windows will trigger the bug when you 
go back into Ubuntu. I've tested this just now to confirm it.
2) OK. Will take note.

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

Title:
  [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll
  multiple lines at a time.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  In 16.04 and 18.04, the mouse scrolls multiple lines at time.
  Sometimes rebooting doesn't fix the issue. This problem doesn't happen
  in Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

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

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

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

[Touch-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

[Christopher M. Penalver]

Mike L, to clarify, does this issue happen when using a wired USB mouse?

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

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

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

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

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

[Christopher M. Penalver]

** Description changed:

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

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

-- 
You received this bug notification because 

[Touch-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

"So the fix could be what is proposed, or/and moving the packagekit hook
to the right place."

I'd say both.

I understand that, per
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/comments/8,
the PackageKit side of the issue would be fixed if Ubuntu shipped
version 0.8.14 or later, which has been true since Xenial as Andreas
observes in comment #10.

Regarding the pm-utils fix, the problems seem to be that no-one is
prepared to own and update pm-utils, and the systemd versions of Ubuntu
don't need pm-utils (in fact, could be seriously confused by it).
Consequently the fix should be implemented in Debian, as Christian says
in comment #7, where pm-utils has been recognised as orphaned and is
still being updated despite Debian using systemd.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+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 1774295] [NEW] Computer becomes slow

[Ivan Pedroso Barreto]

Public bug reported:

After 20 - 30 min of use (heavy graphic usage - photos), the system
becomes very slow. Sometimes even in the right click of the mouse the
menu takes a long time to be shown. It disappears if the machine is
rebooted but after 20 - 30 min. it start over again.

PS - It is not a fresh install. I used the upgrade mode in software
update (using LTS 14.04 before). This problem starts after the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May 30 20:58:00 2018
DistUpgraded: 2018-05-05 18:18:09,353 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
InstallationDate: Installed on 2016-08-02 (666 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20059
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=3f7904bb-d4b1-4e96-9e2f-be3cfb99134b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-05 (25 days ago)
dmi.bios.date: 04/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 29CN23WW(V2.01)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnLENOVO:bvr29CN23WW(V2.01):bd04/07/2010:svnLENOVO:pn20059:pvrIdeapadZ460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: 20059
dmi.product.version: Ideapad Z460
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat May  5 15:08:57 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 623 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Computer becomes slow

Status in xorg package in Ubuntu:
  New

Bug description:
  After 20 - 30 min of use (heavy graphic usage - photos), the system
  becomes very slow. Sometimes even in the right click of the mouse the
  menu takes a long time to be shown. It disappears if the machine is
  rebooted but after 20 - 30 min. it start over again.

  PS - It is not a fresh install. I used the upgrade mode in software
  update (using LTS 14.04 before). This problem starts after the
  upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 30 20:58:00 2018
  DistUpgraded: 2018-05-05 18:18:09,353 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA 

[Touch-packages] [Bug 1774136] Re: apport mistakenly duplicates bugs with similar but not identical python stacktraces

[Brian Murray]

Looking at a couple of crash reports from different releases in the
bucket we can see the DuplicateSignature is the same.

https://errors.ubuntu.com/oops/0df57774-6459-11e8-b827-fa163ed44aae

DuplicateSignature
/usr/bin/update-manager:AttributeError::resize_to_standard_width

https://errors.ubuntu.com/oops/b5eba116-1aca-11e8-aaf0-fa163e839e11

DuplicateSignature
/usr/bin/update-manager:AttributeError::resize_to_standard_width

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

Title:
  apport mistakenly duplicates bugs with similar but not identical
  python stacktraces

Status in apport package in Ubuntu:
  New

Bug description:
  apport duplicates bug 1774131 and bug 1269397 with similar but
  different python stack traces.

  bug 1269397
  update-manager crashed with AttributeError in resize_to_standard_width(): 
'NoneType' object has no attribute 'get_resolution'

  bug 1774131
  update-manager crashed with AttributeError in resize_to_standard_width(): 
'UpdateManager' object has no attribute 'signal_changed' 

  The following bucket also collect both traces based only on the first
  part of the trace: update-manager (AttributeError)  →
  resize_to_standard_width

  https://errors.ubuntu.com/problem/76971c92f002117650d5630a6b13a8ba683e2343

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 09:34:27 2018
  InstallationDate: Installed on 2014-07-15 (1414 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774136/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)

[Daniel van Vugt]

** Summary changed:

- Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and some apps in Xorg sessions)
+ Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and CSD apps in Xorg sessions)

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  (for all apps in Wayland sessions, and CSD apps in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/gnome-shell/+bug/1698083/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

Could any of the reporters of duplicates of this bug provide their apt-
clone file for testing? You should be able to find one at /var/log/dist-
upgrade/apt-clone_system_state.tar.gz. Thanks in advance.

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Confirmed

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  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
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1774212] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[weer]

Public bug reported:

happened during upgrade form 16.04 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 30 18:07:34 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  happened during upgrade form 16.04 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 18:07:34 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1774212/+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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration

[Rocko]

@Brian: just FYI, the /etc/X11/Xsession.d/50_check_unity_support file is
actually checking for ubuntu, not xubuntu: if [ "x$DESKTOP_SESSION" =
"xubuntu" ] will be true if $DESKTOP_SESSION is "ubuntu", because it's
prepending "x" to $DESKTOP_SESSION.

My unity_support_check was failing (it returns 1) so
LIBGL_ALWAYS_SOFTWARE was being set to one. However, after I removed the
/etc/X11/Xsession.d/50_check_unity_support file and reboot,
LIBGL_ALWAYS_SOFTWARE is not set but I still get a llvm_pipe session.

This bug looks a lot like #1752938, which is about losing hardware
acceleration but without removing unity.

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

Title:
  Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware
  acceleration

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 18.04 on a very plain Intel Skylake
  graphics, hardware acceleration is gone. Glxinfo and System
  Information report 'llvmpipe' (software rasterizer)

  It is caused by the file
  /etc/X11/Xsession.d/50_check_unity_support
  which can be deleted and then this problem goes away.

  > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520
  (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  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: Fri Apr 27 20:24:48 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1774320] [NEW] Printing icon missing from "Show Applications"

[Arno Versfeld]

Public bug reported:

I installed Ubuntu 18.04 last week and everything works beautifully except that 
the "printing" icon is missing from "Show Applications".
When I run "system-config-printer" from a terminal the "Printers - localhost" 
opens up and shows the network printer.
When I use Synaptic and search for "system-config-printer-common" it finds it 
and shows installed version 1.5.11-1ubuntu2.
When I run "system-config-printer" from a terminal the following displays 
before the app is opened:

root@Ubuntu-18:/home/arno# system-config-printer
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

(system-config-printer:6764): libnotify-WARNING **: 07:14:35.760: Failed
to connect to proxy

** Affects: ubuntu-touch-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Printing icon missing from "Show Applications"

Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 last week and everything works beautifully except 
that the "printing" icon is missing from "Show Applications".
  When I run "system-config-printer" from a terminal the "Printers - localhost" 
opens up and shows the network printer.
  When I use Synaptic and search for "system-config-printer-common" it finds it 
and shows installed version 1.5.11-1ubuntu2.
  When I run "system-config-printer" from a terminal the following displays 
before the app is opened:

  root@Ubuntu-18:/home/arno# system-config-printer
  Error creating proxy: The connection is closed (g-io-error-quark, 18)
  Error creating proxy: The connection is closed (g-io-error-quark, 18)
  Error creating proxy: The connection is closed (g-io-error-quark, 18)
  Error creating proxy: The connection is closed (g-io-error-quark, 18)
  Error creating proxy: The connection is closed (g-io-error-quark, 18)

  (system-config-printer:6764): libnotify-WARNING **: 07:14:35.760:
  Failed to connect to proxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1774320/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and some apps in Xorg sessions)

[Daniel van Vugt]

** Summary changed:

- Middle-click titlebar actions (like maximizing vertically) don't work in 
Wayland sessions
+ Middle-click titlebar actions (like maximizing vertically) don't work (for 
all apps in Wayland sessions, and some apps in Xorg sessions)

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  (for all apps in Wayland sessions, and some apps in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/gnome-shell/+bug/1698083/+subscriptions

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

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

[Christopher M. Penalver]

** Attachment removed: "example.zip"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1094150/+attachment/3469321/+files/example.zip

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

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

Status in apport package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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

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

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

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

[Christopher M. Penalver]

I don't use 14.04, would never install EOL acroread, and issue was only
reproducible against EOL acroread.

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

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

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

Status in apport package in Ubuntu:
  Invalid

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

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

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

  acroread
  Segmentation fault (core dumped)

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

  4) What happens is it does.

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

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen

[Chris Guiver]

The time of the Xorg crash file is ~correct for the crash that logged me
out (between 1st & 2nd line in my syslog snippet).  I was using XFCE or
Xubuntu-session login (this issue only ever happened with XFCE/Xubuntu
but I can't guarantee it was XFCE the first in list & not Xubuntu-
session; they look & act identical [for me] after login)

the other one (light-locker) I can't recall. Yes I've been testing sleep
(inc. other DEsktops but not at that time (I don't remember, this recall
is from scanning syslog messages). I can see I hand't put my machine to
sleep for some time before or after it, and the next minute opened a
terminal (common behavior), hence don't believe it's related.

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Wladimir J. van der Laan]

For me, "apt-get remove libnvidia-gl-390" solved it. No idea how it came
to be installed, but for some reason the active EGL driver was nvidia,
and that interfered with the X start sequence.

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  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.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  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.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 1774029] Re: Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

[Jean-Baptiste Lallement]

>From boot.log there are several timeout and dependency failure for the
mount points

[ TIME ] Timed out waiting for device 
dev-disk-by\x2duuid-5012d3a8\x2d10bc\x2d4218\x2d9563\x2de3243df441bc.device.
[DEPEND] Dependency failed for /media/DATA.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any mess left by 0dns-up.
[DEPEND] Dependency failed for File System Check on 
/dev/disk/by-uuid/5012d3a8-10bc-4218-9563-e3243df441bc.
[ TIME ] Timed out waiting for device 
dev-disk-by\x2duuid-D725\x2d5E75.device.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for File System Check on 
/dev/disk/by-uuid/D725-5E75.
[ TIME ] Timed out waiting for device 
dev-disk-by\x2duuid-2a28f257\x2d2c49\x2d4396\x2d87d8\x2d25febae99938.device.
[DEPEND] Dependency failed for 
/dev/disk/by-uuid/2a28f257-2c49-4396-87d8-25febae99938.
[DEPEND] Dependency failed for Swap.
[ TIME ] Timed out waiting for device 
dev-disk-by\x2duuid-72b61b47\x2d1391\x2d45b4\x2d8619\x2de51b48548e11.device.
[DEPEND] Dependency failed for File System Check on 
/dev/disk/by-uuid/72b61b47-1391-45b4-8619-e51b48548e11.
[DEPEND] Dependency failed for /home.

** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (Ubuntu)

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

Title:
  Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

Status in systemd package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot 
with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I 
tried 4.14 & 4.16 as well, to no avail).
  Booting with the 4.4 kernel leads to the login screen and everything works 
OK, while booting with the 4.15 kernel remains stalled on the Ubuntu startup 
screen with dots, ESC shows traces stuck? on "Reached target Network is Online"
  I can successfully boot the 18.04 desktop image though, so I am assuming the 
issue comes from configuration files and not from the kernel itself. Any help 
would be highly appreciated !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Tue May 29 19:05:08 2018
  InstallationDate: Installed on 2014-11-19 (1286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-22 20:51:41.459776
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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

[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen

[Christopher M. Penalver]

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

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

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

Status in xorg package in Ubuntu:
  New

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166.
   68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session opened for user 

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)

[Timo Aaltonen]

what does 'apt-cache policy libnvidia-gl-390' say?

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

Title:
  Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo
  P8600 / GMA 4500MHD)

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

Bug description:
  After upgrading to Ubuntu 18.04, my desktop uses software rendering, no 
matter what I do.
  As far as I know, all necessary packages are installed.
  Formerly I had oibaf installed, but suspecting that this may cause the 
problem, I removed it with ppa-purge. It didn't help.

  First I noticed the problem when I tried to play HD videos.
  It was fine before the upgrade. My hardware is capable for 3D acceleration, 
as it worked on 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 06:13:09 2018
  DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2014-06-10 (1432 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 6474B84
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6474B84
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6474B84
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun May 13 06:01:23 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+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 1774130] Re: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  after updating ubuntu 14.04 to ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 15:10:06 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-02 (909 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1774130/+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 1774132] [NEW] [Bionic]udev stop notifying when network interface added

[Talat Batheesh]

Public bug reported:

Expected:

After a network driver restart, the network interfaces are deleted and
added again, the udev should notify that new interface was added. then
the interface service should be started accordingly.

Actual:
Udev doesn't notify about that new interface is added and the interface service 
doesn't start.

More details:

We see this issue when using Mellanox OFED package.
Mellanox OFED add a service per network device and add udev rule to start this 
service when the interface added.
After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

The system should run from udev rules, since once the driver creates an
interface, there should be a udev event saying a new interface is added,
then this script will be ran by udev (the OS).

" /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

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

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

Title:
  [Bionic]udev stop notifying when network interface added

Status in systemd package in Ubuntu:
  New

Bug description:
  Expected:

  After a network driver restart, the network interfaces are deleted and
  added again, the udev should notify that new interface was added. then
  the interface service should be started accordingly.

  Actual:
  Udev doesn't notify about that new interface is added and the interface 
service doesn't start.

  More details:

  We see this issue when using Mellanox OFED package.
  Mellanox OFED add a service per network device and add udev rule to start 
this service when the interface added.
  After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

  The system should run from udev rules, since once the driver creates
  an interface, there should be a udev event saying a new interface is
  added, then this script will be ran by udev (the OS).

  " /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+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 1774029] [NEW] Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot 
with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I 
tried 4.14 & 4.16 as well, to no avail).
Booting with the 4.4 kernel leads to the login screen and everything works OK, 
while booting with the 4.15 kernel remains stalled on the Ubuntu startup screen 
with dots, ESC shows traces stuck? on "Reached target Network is Online"
I can successfully boot the 18.04 desktop image though, so I am assuming the 
issue comes from configuration files and not from the kernel itself. Any help 
would be highly appreciated !

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.17
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Tue May 29 19:05:08 2018
InstallationDate: Installed on 2014-11-19 (1286 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2018-05-22 20:51:41.459776
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done

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


** Tags: amd64 apport-bug bionic dist-upgrade
-- 
Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)
https://bugs.launchpad.net/bugs/1774029
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

-- 
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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[ Christian Ehrhardt ]

Seed changes accepted and merged in VCS.
Related ubuntu-meta update uploaded as 
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.421

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1774130] [NEW] package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu

[hopstone]

Public bug reported:

after updating ubuntu 14.04 to ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
Date: Wed May 30 15:10:06 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-12-02 (909 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  after updating ubuntu 14.04 to ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 30 15:10:06 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-02 (909 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.4+16.04.20160402.4-0ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1774130/+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 1774049] [NEW] df incorrectly reports available space left

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When using df command, it reports 19GB available on /home, however
trying to write anything to that gives a no space left error.

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


** Tags: bot-comment
-- 
df incorrectly reports available space left
https://bugs.launchpad.net/bugs/1774049
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to coreutils in Ubuntu.

-- 
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 1774136] [NEW] apport mistakenly duplicates bugs with similar but not identical python stacktraces

[Jean-Baptiste Lallement]

Public bug reported:

apport duplicates bug 1774131 and bug 1269397 with similar but different
python stack traces.

bug 1269397
update-manager crashed with AttributeError in resize_to_standard_width(): 
'NoneType' object has no attribute 'get_resolution'

bug 1774131
update-manager crashed with AttributeError in resize_to_standard_width(): 
'UpdateManager' object has no attribute 'signal_changed' 

The following bucket also collect both traces based only on the first
part of the trace: update-manager (AttributeError)  →
resize_to_standard_width

https://errors.ubuntu.com/problem/76971c92f002117650d5630a6b13a8ba683e2343

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: apport 2.20.10-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportLog:
 
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 09:34:27 2018
InstallationDate: Installed on 2014-07-15 (1414 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to cosmic on 2018-03-24 (66 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  apport mistakenly duplicates bugs with similar but not identical
  python stacktraces

Status in apport package in Ubuntu:
  New

Bug description:
  apport duplicates bug 1774131 and bug 1269397 with similar but
  different python stack traces.

  bug 1269397
  update-manager crashed with AttributeError in resize_to_standard_width(): 
'NoneType' object has no attribute 'get_resolution'

  bug 1774131
  update-manager crashed with AttributeError in resize_to_standard_width(): 
'UpdateManager' object has no attribute 'signal_changed' 

  The following bucket also collect both traces based only on the first
  part of the trace: update-manager (AttributeError)  →
  resize_to_standard_width

  https://errors.ubuntu.com/problem/76971c92f002117650d5630a6b13a8ba683e2343

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 09:34:27 2018
  InstallationDate: Installed on 2014-07-15 (1414 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774136/+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 1774151] [NEW] Xorg crashed with SIGABRT in RSetChanged()

[Nicolas Göddel]

Public bug reported:

I guess it happens because I made and update of my nvidia drivers using
apt-get dist-upgrade while gnome was up and running. Because during the
update gnome freezes and restarts itself after a while.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed May 30 10:34:15 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
 NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
InstallationDate: Installed on 2014-04-18 (1502 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
MachineType: LENOVO 24474GG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=b44fee51-1765-4794-b840-a8e5272c94c7 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 24474GG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET95WW(2.55):bd09/13/2013:svnLENOVO:pn24474GG:pvrThinkPadW530:rvnLENOVO:rn24474GG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 24474GG
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 30 10:11:32 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages 
ubuntu xenial

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

Title:
  Xorg crashed with SIGABRT in RSetChanged()

Status in xorg package in Ubuntu:
  New

Bug description:
  I guess it happens because I made and update of my nvidia drivers
  using apt-get dist-upgrade while gnome was up and running. Because
  during the update gnome freezes and restarts itself after a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed May 30 10:34:15 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
 

[Touch-packages] [Bug 1774049] Re: df incorrectly reports available space left

[Paul White]

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

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

Title:
  df incorrectly reports available space left

Status in coreutils package in Ubuntu:
  New

Bug description:
  When using df command, it reports 19GB available on /home, however
  trying to write anything to that gives a no space left error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1774049/+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 1774132] Re: [Bionic]udev stop notifying when network interface added

[Dimitri John Ledkov]

Could you please collect the udevadm monitor logs, across the openibd
restart, both with a previously known working release (e.g. xenial?!)
and bionic?

Together with dmesg output, to see what kernel was doing at the same
time.

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

Title:
  [Bionic]udev stop notifying when network interface added

Status in systemd package in Ubuntu:
  New

Bug description:
  Expected:

  After a network driver restart, the network interfaces are deleted and
  added again, the udev should notify that new interface was added. then
  the interface service should be started accordingly.

  Actual:
  Udev doesn't notify about that new interface is added and the interface 
service doesn't start.

  More details:

  We see this issue when using Mellanox OFED package.
  Mellanox OFED add a service per network device and add udev rule to start 
this service when the interface added.
  After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

  The system should run from udev rules, since once the driver creates
  an interface, there should be a udev event saying a new interface is
  added, then this script will be ran by udev (the OS).

  " /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+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 1772629] Re: Automatic logout when resuming from suspend on Xubuntu 18.04

[Paulo Marcel Coelho Aragão]

I have discovered that the automatic logout was caused by the Xorg
server crashing with SIGBUS. So this bug may and should be closed.

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

Title:
  Automatic logout when resuming from suspend on Xubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind
  automatically logs out of the current session if the laptop has stayed
  suspended for more than a couple of hours. If the interval between
  suspend and resume is short, it doesn't log out. I still haven't
  discovered how long this interval has to be in order to cause the
  logout.

  I enabled debug on the systemd-logind.service, creating file
  _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  which causes systemd-logind to log all D-Bus messages it handles, but
  couldn't spot anything that might have caused the logout.

  I scanned all systemd journal messages (`journalctl`) before systemd-
  logind starts killing the current session, investigated all that
  looked suspicious but couldn't find anything that might influence an
  automatic logout. Here are some of the messages that striked me as
  suspicious (they are not sequential, but pulled from different
  occasions):

  upowerd[1600]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0
  polkitd(authority=local)[840]: Unregistered Authentication Agent for 
unix-session:c2 (system bus name :1.46, object path 
/org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected 
from bus)
  wpa_supplicant[811]: dbus: fill_dict_with_properties 
dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter 
failed
  wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get 
object properties: (none) none
  at-spi-bus-launcher[7031]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[7031]:   after 30333 requests (30333 known processed) 
with 0 events remaining.
  systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager 
handles these events) pid=8611 uid=1000 mode=block stopped
  systemd-logind[779]: Electing new display for user paulo
  systemd-logind[779]: Ignoring session c8

  logind config doesn't have anything that might cause this:

  paulo:~$ loginctl show-session
  EnableWallMessages=no
  NAutoVTs=6
  KillUserProcesses=no
  RebootToFirmwareSetup=no
  IdleHint=no
  IdleSinceHint=0
  IdleSinceHintMonotonic=0
  BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key
  DelayInhibited=sleep
  InhibitDelayMaxUSec=5s
  HandlePowerKey=poweroff
  HandleSuspendKey=suspend
  HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=ignore
  HoldoffTimeoutUSec=30s
  IdleAction=ignore
  IdleActionUSec=30min
  PreparingForShutdown=no
  PreparingForSleep=no
  Docked=no
  RemoveIPC=yes
  RuntimeDirectorySize=615313408
  InhibitorsMax=8192
  NCurrentInhibitors=5
  SessionsMax=8192
  NCurrentSessions=1
  UserTasksMax=10813

  I can't find any anything that might cause an automatic logout after a
  time interval. I'm really stumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  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: XFCE
  Date: Tue May 22 07:36:59 2018
  InstallationDate: Installed on 2018-04-28 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 08FDW5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1772629/+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 1577575] Re: NFS share does not mount on boot using fstab

[Adrian Cantrill]

I have the same issue - installed version of 18.04 today and none of my
NFS mounts happen at boot.

May 30 17:23:41 can-srv systemd[1]: mnt-docker.mount: Directory /mnt/docker to 
mount over is not empty, mounting anyway.
May 30 17:23:41 can-srv systemd[1]: Mounting /mnt/docker...
May 30 17:23:41 can-srv mount[834]: mount.nfs: Network is unreachable
May 30 17:23:41 can-srv systemd[1]: mnt-docker.mount: Mount process exited, 
code=exited status=32
May 30 17:23:41 can-srv systemd[1]: mnt-docker.mount: Failed with result 
'exit-code'.
May 30 17:23:41 can-srv systemd[1]: Failed to mount /mnt/docker.

They work fine with a mount -a at login ... but i need them up before
services start.

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

Title:
  NFS share does not mount on boot using fstab

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen?

  I want an NFS share to be mounted on startup using

  
  192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ 
/media/captainplanet/banane/ nfs rw 0 0

  What happened instead?

  It does not mount on startup. Systemd waits 91sec instead and finally
  starts after failing.

  I can successfully mount the NFS share with

  sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575
  /media/captainplanet/banane/

  When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS
  share manually before shutdown fixes the second problem.

  
  Do you need more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  2 23:10:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DM003XUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JFET44WW(1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DM003XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DM003XUK
  dmi.product.version: ThinkPad S3 Yoga 14
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577575/+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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.421

---
ubuntu-meta (1.421) cosmic; urgency=medium

  * Refreshed dependencies
  * Moved open-iscsi to server-recommends (LP: #1630946)

 -- root   Wed, 30 May 2018 07:01:29 +

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1774029] Re: Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

[manuw2009]

Hi,
You're right but I get them as well with the working kernel.
How would I fix that though ?

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

Title:
  Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

Status in systemd package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot 
with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I 
tried 4.14 & 4.16 as well, to no avail).
  Booting with the 4.4 kernel leads to the login screen and everything works 
OK, while booting with the 4.15 kernel remains stalled on the Ubuntu startup 
screen with dots, ESC shows traces stuck? on "Reached target Network is Online"
  I can successfully boot the 18.04 desktop image though, so I am assuming the 
issue comes from configuration files and not from the kernel itself. Any help 
would be highly appreciated !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Tue May 29 19:05:08 2018
  InstallationDate: Installed on 2014-11-19 (1286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-22 20:51:41.459776
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774029/+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 1768539] Re: Conflicts between / and /usr

[Bug Watch Updater]

** Changed in: safe-rm (Debian)
   Status: Unknown => New

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Fix Committed
Status in safe-rm package in Ubuntu:
  Fix Released
Status in pm-utils package in Debian:
  Fix Released
Status in safe-rm package in Debian:
  New

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+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 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => New

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

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+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 1697959] Re: late package version collection can cause confusion

[Francis Ginther]

** Tags added: id-5b0dd6209f4e7cded9ed7ee4

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

Title:
  late package version collection can cause confusion

Status in apport package in Ubuntu:
  New

Bug description:
  The following OOPS contains some misinformation:

  https://errors.ubuntu.com/oops/3680877e-5046-11e7-89b7-fa163e54c21f

  The Date field is from before the package version in the report was
  accepted into -proposed. This likely happened because the .crash file
  was created and data collection, including adding the Package key, was
  done after systemd had been upgraded. This is alluded to in the
  UnreportableReason of the OOPS.

  UnreportableReason:
  Неполадка произошла с программой /lib/systemd/systemd-resolved, в которую 
были внесены изменения с момента её аварийного завершения работы.

  It says that systemd-resolved was modified since the error occurred.

  As we can see in bug 1621396 this ended up confusing the developer and
  they were concerned about their fix not working. It seems like apport
  or whoopsie should do something better here.

  Ideas include not putting a package version in the Package field if
  the binary has been modified, or not uploading the crash to the Error
  Tracker if the binary has changed.  The latter would require some
  additional work because the UnreportableReason is translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697959/+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 1768539] Re: Conflicts between / and /usr

[Bug Watch Updater]

** Changed in: safe-rm (Debian)
   Status: New => Fix Released

** Changed in: pm-utils (Debian)
   Status: New => Fix Released

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Fix Committed
Status in safe-rm package in Ubuntu:
  Fix Released
Status in pm-utils package in Debian:
  Fix Released
Status in safe-rm package in Debian:
  Fix Released

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+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 1774132] Re: [Bionic]udev stop notifying when network interface added

[Talat Batheesh]

** Attachment added: "udevadm"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+attachment/5146404/+files/udevadm18.04.log

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

Title:
  [Bionic]udev stop notifying when network interface added

Status in systemd package in Ubuntu:
  New

Bug description:
  Expected:

  After a network driver restart, the network interfaces are deleted and
  added again, the udev should notify that new interface was added. then
  the interface service should be started accordingly.

  Actual:
  Udev doesn't notify about that new interface is added and the interface 
service doesn't start.

  More details:

  We see this issue when using Mellanox OFED package.
  Mellanox OFED add a service per network device and add udev rule to start 
this service when the interface added.
  After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

  The system should run from udev rules, since once the driver creates
  an interface, there should be a udev event saying a new interface is
  added, then this script will be ran by udev (the OS).

  " /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+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 1774170] [NEW] Applications block on eglswapBuffers due to buggy mesa version

[Mohamed Sharaf-El-Deen]

Public bug reported:

The mesa version that is available after installing packages has a bug
that leads to wayland applications blocking on eglSwapBuffers if egl
swap interval is set to Zero.

Ubuntu version: 18.04 LTS
Currently available mesa version for installation: 18.0.0~rc5

Versions where the bug is fixed:
17.3.8, 18.0.2, 18.1.0, or later

More details about the bug, how to reproduce it and the right mesa versions to 
use in here:
https://bugs.freedesktop.org/show_bug.cgi?id=106719

Would be so good if it is possible to provide one of the mesa versions
where the problem does not exist as a package for installation.

Thanks


Output from running:
apt-cache policy libegl-mesa0


libegl-mesa0:
  Installed: 18.0.0~rc5-1ubuntu1
  Candidate: 18.0.0~rc5-1ubuntu1
  Version table:
 *** 18.0.0~rc5-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Applications block on eglswapBuffers due to buggy mesa version

Status in mesa package in Ubuntu:
  New

Bug description:
  The mesa version that is available after installing packages has a bug
  that leads to wayland applications blocking on eglSwapBuffers if egl
  swap interval is set to Zero.

  Ubuntu version: 18.04 LTS
  Currently available mesa version for installation: 18.0.0~rc5

  Versions where the bug is fixed:
  17.3.8, 18.0.2, 18.1.0, or later

  More details about the bug, how to reproduce it and the right mesa versions 
to use in here:
  https://bugs.freedesktop.org/show_bug.cgi?id=106719

  Would be so good if it is possible to provide one of the mesa versions
  where the problem does not exist as a package for installation.

  Thanks


  Output from running:
  apt-cache policy libegl-mesa0

  
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1774170/+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 344814] Re: Synthetic emboldening/italic/italic-bold fails for single-styled fonts

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => Confirmed

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/344814/+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 1768539] Re: Conflicts between / and /usr

[Dimitri John Ledkov]

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

** Changed in: safe-rm (Debian)
   Status: Fix Released => Unknown

** Changed in: safe-rm (Debian)
 Remote watch: Debian Bug tracker #812545 => Debian Bug tracker #759410

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Fix Committed
Status in safe-rm package in Ubuntu:
  Fix Released
Status in pm-utils package in Debian:
  Fix Released
Status in safe-rm package in Debian:
  Unknown

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+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 1774132] Re: [Bionic]udev stop notifying when network interface added

[Talat Batheesh]

Thank you Dima, 
Added requested files.

yours,
Talat

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

Title:
  [Bionic]udev stop notifying when network interface added

Status in systemd package in Ubuntu:
  New

Bug description:
  Expected:

  After a network driver restart, the network interfaces are deleted and
  added again, the udev should notify that new interface was added. then
  the interface service should be started accordingly.

  Actual:
  Udev doesn't notify about that new interface is added and the interface 
service doesn't start.

  More details:

  We see this issue when using Mellanox OFED package.
  Mellanox OFED add a service per network device and add udev rule to start 
this service when the interface added.
  After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

  The system should run from udev rules, since once the driver creates
  an interface, there should be a udev event saying a new interface is
  added, then this script will be ran by udev (the OS).

  " /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+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 1774132] Re: [Bionic]udev stop notifying when network interface added

[Talat Batheesh]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+attachment/5146405/+files/dmesgub18.04.log

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

Title:
  [Bionic]udev stop notifying when network interface added

Status in systemd package in Ubuntu:
  New

Bug description:
  Expected:

  After a network driver restart, the network interfaces are deleted and
  added again, the udev should notify that new interface was added. then
  the interface service should be started accordingly.

  Actual:
  Udev doesn't notify about that new interface is added and the interface 
service doesn't start.

  More details:

  We see this issue when using Mellanox OFED package.
  Mellanox OFED add a service per network device and add udev rule to start 
this service when the interface added.
  After driver restart ("/etc/init.d/openibd restart") the network devices 
doesn't loaded, since udev doesn't notify.

  The system should run from udev rules, since once the driver creates
  an interface, there should be a udev event saying a new interface is
  added, then this script will be ran by udev (the OS).

  " /bin/systemctl --no-block start mlnx_interface_mgr@ib0.service "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774132/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[FrancisJiang]

Having the same problem with Ubuntu 18.04 LTS release.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Julian Andres Klode]

I think it's a fundamental problem that interest triggers are not
considered for ordering packages, and hence cannot be used reliably.
Fixing this bug is probably a matter of making all the triggers noawait,
although I can't reproduce it, so I can't test any SRU.

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Confirmed

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  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
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Sami Pietila]

Hi

1) I did run given commands.

2) I rebooted the machine with three monitors connected. I tried with
both Metacity and Compiz options which had appeared. Trying to log in
resulted crash and returning back to login screen.

3) HP ZR2440, HP 27i, Dell UltraSharp U2515H

4) Monitors are connected with Display port cables. Two of displays are
connected to the integrated intel graphics controller. One display is
connected to Radeon card.

5) No.

6) The 16.04.4 live cd seems to work just fine with my three monitors.

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

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

  The errors happend with both Wayland and X.

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

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

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

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Robert C Jennings]

I'll mention this here because I believe it's related, if not please
correct me and I'll file a separate bug.  When cron jobs are run
/snap/bin is not in the path.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[ Christian Ehrhardt ]

Other than the mistake to not update to my name on the upload this is
resolved.

>From now on you can remove it:

# apt remvoe open-iscsi
E: Invalid operation remvoe
root@c:~# apt remove open-iscsi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  open-iscsi
0 upgraded, 0 newly installed, 1 to remove and 51 not upgraded.
After this operation, 1412 kB disk space will be freed.
Do you want to continue? [Y/n]

As it is just a recommends.

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Launchpad Bug Tracker]

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

** Changed in: snapd (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/1771858

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Launchpad Bug Tracker]

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

** Changed in: snapd (Ubuntu Bionic)
   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/1771858

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Launchpad Bug Tracker]

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

** Changed in: snapd (Ubuntu Xenial)
   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/1771858

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[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/1771858

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

Awesome, thanks again!

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Christopher M. Penalver]

** Tags added: regression-release

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

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  New

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

  The errors happend with both Wayland and X.

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

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

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

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

[Thomas Diesenreiter]

Hi there,

I fear that I do not have the time to do such in-depth debugging atm. As I 
said, I used the latest kernel with my previous 17.10 install without this 
problem, and it occurred with the first kernel of the 18.04 release. I know 
that it would be easier for you to know the specific kernel version where the 
digression was introduced, but maybe it would be possible to have a look at the 
old bug here (https://bugs.freedesktop.org/show_bug.cgi?id=64332) and take a 
look at the specific files which got patched back then to find the digression. 
I'm just a php coder, so my knowledge about kernel development is too limited 
to take a look into it myself.

** Bug watch added: freedesktop.org Bugzilla #64332
   https://bugs.freedesktop.org/show_bug.cgi?id=64332

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

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

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

[Christopher M. Penalver]

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

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1738524] Re: package rsync 3.1.1-3ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu, and sorry for taking to long to
get to it.

There is a loop between some of your initscripts.

If this problem is still happening, please try this first:

sudo apt update
sudo apt -f install

If it happens again, then please attach the following file to this bug:

/etc/init.d/cups

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

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

Title:
  package rsync 3.1.1-3ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  I don't know :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsync 3.1.1-3ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Sat Dec 16 10:40:13 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-03 (346 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: rsync
  Title: package rsync 3.1.1-3ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1738524/+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 1774204] [NEW] asdf

[Christopher Arroyo]

Public bug reported:

adsf

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 08:41:14 2018
DistUpgraded: 2018-05-21 13:20:06,969 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 18.20-579836, 4.15.0-20-generic, x86_64: installed
 amdgpu, 18.20-579836, 4.15.0-22-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
 Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (prog-if 00 [VGA controller])
   Subsystem: Dell FirePro M5100 [1028:05cc]
InstallationDate: Installed on 2018-05-21 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Dell Inc. Precision M4800
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=ffa4c69d-899f-4e51-ae7e-bae9d551b398 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-21 (8 days ago)
dmi.bios.date: 05/19/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0V5GVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  asdf

Status in xorg package in Ubuntu:
  New

Bug description:
  adsf

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 08:41:14 2018
  DistUpgraded: 2018-05-21 13:20:06,969 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.20-579836, 4.15.0-20-generic, x86_64: installed
   amdgpu, 18.20-579836, 4.15.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (prog-if 00 [VGA controller])
 Subsystem: Dell FirePro M5100 [1028:05cc]
  InstallationDate: Installed on 2018-05-21 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Precision M4800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=ffa4c69d-899f-4e51-ae7e-bae9d551b398 ro quiet splash vt.handoff=1
  Renderer: