[Touch-packages] [Bug 1756632] Re: lightdm crashed with SIGSEGV in _dl_fini()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1675141, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082773/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082775/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082781/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082782/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082783/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082784/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756632/+attachment/5082785/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1675141
   lightdm crashed with SIGSEGV in munmap()

** Tags removed: need-amd64-retrace

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

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

Status in lightdm package in Ubuntu:
  New

Bug description:
  Crash occured on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:41:53 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2017-10-24 (144 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=skellat
   autologin-user-timeout=0
  ProcCmdline: lightdm --session-child 12 15
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>: mov0x8(%rax),%r15
   PC (0x7f4cc21acb3a) ok
   source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region 
(needed readable region)!
   destination "%r15" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   _dl_fini () at dl-fini.c:134
   __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
   __GI_exit (status=) at exit.c:139
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: lightdm crashed with SIGSEGV in _dl_fini()
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632/+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 1756632] [NEW] lightdm crashed with SIGSEGV in _dl_fini()

[Stephen Michael Kellat]

Public bug reported:

Crash occured on boot

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 17 21:41:53 2018
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2017-10-24 (144 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 autologin-user=skellat
 autologin-user-timeout=0
ProcCmdline: lightdm --session-child 12 15
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>:   mov0x8(%rax),%r15
 PC (0x7f4cc21acb3a) ok
 source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region (needed 
readable region)!
 destination "%r15" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 _dl_fini () at dl-fini.c:134
 __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
 __GI_exit (status=) at exit.c:139
 ()
  () at /lib/x86_64-linux-gnu/libc.so.6
Title: lightdm crashed with SIGSEGV in _dl_fini()
UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago)
UserGroups:

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


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

Status in lightdm package in Ubuntu:
  New

Bug description:
  Crash occured on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:41:53 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2017-10-24 (144 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=skellat
   autologin-user-timeout=0
  ProcCmdline: lightdm --session-child 12 15
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>: mov0x8(%rax),%r15
   PC (0x7f4cc21acb3a) ok
   source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region 
(needed readable region)!
   destination "%r15" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   _dl_fini () at dl-fini.c:134
   __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
   __GI_exit (status=) at exit.c:139
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: lightdm crashed with SIGSEGV in _dl_fini()
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Theodore Ts'o]

If you are trying to build from the unpacked debian sources for 1.43.x,
you'll need to run the commands:

./debian/rules mrproper
./debian/rules

... to have the build system figure out which antique version of Debian
build infrastructure you are using, and regenerate debian/control from
debian/control.in.   (Usually I just check

That may be what you are running into.   Note that starting in 1.44.0,
I've dropped all of the backwards compatibility stuff, on the theory
that people who want to support ancient Linux distribution systems are
paid the big bucks, and it wasn't worth my volunteer time to make it all
work and do all of the testing on ancient systems.  (And especially
since most enterpise distro folks weren't taking the latest bug fixes
anyway, and it's been over ten years since I've had to care about
enterprise distro customers.)

The short version is that the backwards compatibility stuff was all
about making things like the debug packages work.  It's all packaging
gunk, and so as long as you crate packages that pass lintian checks,
it's probably fine.

As a reminder, the distro packaging of the latest version of e2fsprogs
for old back-level enterpise distros may cause the distro release folks
to want to constain the default ext4 file system features that are
enabled, since the older versions of grub, the linux kernel, et. al,
might not support metadata checksuming (for example).   So I could
easily see that Ubuntu might want to adjust misc/mke2fs.conf.in file to
disable certain file system features from being enabled in freshly
created file systems by default, for example.   I also have a vague
memory that Ubuntu had a slightly different convention for supporting
debug symbol packages on older Ubuntu systems.  If so, that may require
more adjustments --- or maybe you'll just decide to disable the debug
symbol packages and call it a day.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Simon Iremonger]

HOWEVER, Trusty e2fsprogs backporting situation actually seems to be that, some 
change between  1.43.3-1~bpo8+1  and  1.43.4-2  is where the 
trusty-incompatibility has accrued, 1.43.9-2 does NOT build on trusty! :-
https://www.iremonger.me.uk/noidx/e2fs/e2fsprogs-1.43.9_trusty_build-fail.log

A simple patch to the 'debian/control' file adding the explicit '-dbg' package 
entries on the end *APPEARS* to solve all the problems, and allows 1.43.9 [or 
1.44.0 for that matter!] to SEEMINGLY build fine, pass all tests, and work fine 
on trusty without any issues I can find so-far!:-
https://www.iremonger.me.uk/noidx/e2fs/e2fsprogs-1.43.9_trusty_debian-control.patch
https://www.iremonger.me.uk/noidx/e2fs/e2fsprogs-1.44.0_trusty_debian-control.patch

This all SEEMS to work fine, but I'd like tytso to comment on this, is
this really a safe workaround or just 'fixing the symptom'.  From what I
can see all the right programs are generated and work fine.

AGAIN, I'd highly recommend installing byte-for-byte the 'original' mke2fs.conf 
in any trusty-backport version of e2fsprogs, so as to avoid any unwanted 
behavioural-changes or configuration-file-update-prompts :-.
https://www.iremonger.me.uk/noidx/e2fs/mke2fs.conf.trusty

>From what I can SEE, if doing a significant backport to trusty, I can't
see why not to just go straight to 1.44.0 in this case [again, hopefully
tytso can comment!].

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Simon Iremonger]

OK On further investigation, I have confirmed a lot of key-facts (1 of 2
linked comments).

e2fsprogs 1.44.0-1 backports to xenial with no difficulty whatsoever,
passes "make fullcheck" and works in every way I can tell, lots of
resizing and checking and use within gparted, etc, all (apparently)
behaving...

HOWEVER, for an official xenial-backport (and especially xenial-SRU), to 
minimize possible problems, I would highly recommend making single change of 
restoring the 'default' mke2fs.conf EXACTLY (byte-for-byte) as that which came 
with xenial e2fsprogs 1.42.13-1ubuntu1 :-
https://www.iremonger.me.uk/noidx/e2fs/mke2fs.conf.xenial
This (a) avoids prompting users who've customized their mke2fs.conf about 
merging-changes, and (b) avoids functional-change for those with 
automated-deployment-scripts etc. based upon ext4 creation.

I presume, a 'xenial-backport' -or- SRU "proposed" update can be started
straight-away?  xenial-SRU should DEFINITELY be considered for fsck
compatibility with bionic-created FS.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1756611] Re: systemd-journald crashed with SIGABRT in fsync()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1750855, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082633/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082636/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082643/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082645/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082646/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082647/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756611/+attachment/5082649/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1750855

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in fsync()

Status in systemd package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 18 01:01:50 2018
  ExecutablePath: /lib/systemd/systemd-journald
  MachineType: System manufacturer System Product Name
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=cbcfa05f-aab5-4712-aac2-06e455b4b0b0 ro splash quiet vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=18) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: Upgraded to bionic on 2018-03-17 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LE/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE/USB3:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756611/+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 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proces

[dino99]

** Changed in: unity (Ubuntu)
 Assignee: Janbert Cahilig (soulschester) => (unassigned)

** Tags removed: vivid
** Tags added: artful bionicl xenia

** Tags removed: bionicl xenia
** Tags added: bionic xenial

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Expired
Status in apport package in Ubuntu:
  Confirmed
Status in synaptic package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zenity package in Ubuntu:
  Confirmed

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467588/+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 1756602] [NEW] package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 10

[Rod Souza]

Public bug reported:

Bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.9
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Mar 16 19:56:00 2018
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 10

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.9
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 16 19:56:00 2018
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1756602/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

[Scott Palmer]

** Attachment added: "Fresh boot -- after re-plug -- woking sound from rear 
green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082539/+files/alsa-info-after.txt

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

[Scott Palmer]

** Attachment added: "Fresh boot -- no sound from rear green jack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082538/+files/alsa-info-before.txt

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

[Scott Palmer]

Also note that this problem also affects Bionic 18.04 users with
4.15.0-12-generic

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1754888] Re: Menulibre: invalid desktop files detected!

[Willem Hobers]

Sean, I can confirm that this fixes the issue for

  - usr/share/xubuntu/applications/Thunar-bulk-rename.desktop
  - usr/share/xubuntu/applications/Thunar.desktop
  - usr/share/xubuntu/applications/debian-uxterm.desktop
  - usr/share/xubuntu/applications/debian-xterm.desktop
  - usr/share/xubuntu/applications/thunar-settings.desktop
  - usr/share/xubuntu/applications/xfce4-terminal.desktop

Just the message about "vim" remains.

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Released
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/menulibre/+bug/1754888/+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 1756595] [NEW] disk space info inadvertently provides all installed snaps

[Andreas Hasenack]

Public bug reported:

When apport is reporting a crash, it includes the output of the "df"
utility, to list the free disk space information per mount point.

That output nowadays will inadvertently include all snaps that the user
may have installed, including their revision numbers.

Here is a simple df output:
andreas@nsn7:~$ df
Filesystem  1K-blocksUsed Available Use% Mounted on
udev  8119680   0   8119680   0% /dev
tmpfs 16301561828   1628328   1% /run
nsn7/ROOT/ubuntu433084288 2500608 430583680   1% /
tmpfs 8150776   1   8131888   1% /dev/shm
tmpfs5120   4  5116   1% /run/lock
tmpfs 8150776   0   8150776   0% /sys/fs/cgroup
nsn7/var/log430763136  179456 430583680   1% /var/log
nsn7/var/tmp430583808 128 430583680   1% /var/tmp
/dev/sda2 1032088  160336871752  16% /boot
/dev/sda1  5232482720520528   1% /boot/efi
nsn7/home   430651264   67584 430583680   1% /home
nsn7/var/cache  430653312   69632 430583680   1% /var/cache
nsn7/var/mail   430583808 128 430583680   1% /var/mail
nsn7/var/spool  430583808 128 430583680   1% /var/spool
tmpfs 1630152  16   1630136   1% /run/user/120
tmpfs 100   0   100   0% 
/var/lib/lxd/shmounts
tmpfs 100   0   100   0% 
/var/lib/lxd/devlxd
tmpfs 1630152  36   1630116   1% /run/user/1000
nsn7/lxd/containers/squid-ds216 431444096  860416 430583680   1% 
/var/lib/lxd/storage-pools/default/containers/squid-ds216
/dev/loop0  83712   83712 0 100% /snap/core/4206
/dev/loop1 102144  102144 0 100% 
/snap/git-ubuntu/402

You can see I have the core snap at revision 4206, and git-ubuntu at
revision 402.

There are already many bug reports in launchpad where one can see this
information.

Granted, the user can review it, refuse to send this data, etc. This bug
is about the unexpectedness of having that information in the disk space
data.

If the user sees a prompt like "Would you like to include disk free
space information in your report?", or "Would you like to include the
output of the df(1) command in your report?", that doesn't immediately
translate to "Would you like to include disk free space information and
a list of all installed snaps and their revision numbers in your
report?".

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

** Summary changed:

- disk space info inadvertently lists all installed snaps
+ disk space info inadvertently provides all installed snaps

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

Title:
  disk space info inadvertently provides all installed snaps

Status in apport package in Ubuntu:
  New

Bug description:
  When apport is reporting a crash, it includes the output of the "df"
  utility, to list the free disk space information per mount point.

  That output nowadays will inadvertently include all snaps that the
  user may have installed, including their revision numbers.

  Here is a simple df output:
  andreas@nsn7:~$ df
  Filesystem  1K-blocksUsed Available Use% Mounted on
  udev  8119680   0   8119680   0% /dev
  tmpfs 16301561828   1628328   1% /run
  nsn7/ROOT/ubuntu433084288 2500608 430583680   1% /
  tmpfs 8150776   1   8131888   1% /dev/shm
  tmpfs5120   4  5116   1% /run/lock
  tmpfs 8150776   0   8150776   0% 
/sys/fs/cgroup
  nsn7/var/log430763136  179456 430583680   1% /var/log
  nsn7/var/tmp430583808 128 430583680   1% /var/tmp
  /dev/sda2 1032088  160336871752  16% /boot
  /dev/sda1  5232482720520528   1% /boot/efi
  nsn7/home   430651264   67584 430583680   1% /home
  nsn7/var/cache  430653312   69632 430583680   1% /var/cache
  nsn7/var/mail   430583808 128 430583680   1% /var/mail
  nsn7/var/spool  430583808 128 430583680   1% /var/spool
  tmpfs 1630152  16   1630136   1% /run/user/120
  tmpfs 100   0   100   0% 
/var/lib/lxd/shmounts
  tmpfs 100   0   100   0% 
/var/lib/lxd/devlxd
  tmpfs 

[Touch-packages] [Bug 1756593] Re: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143

[Michael Neuffer]

Start of the log (above is only the tail end where it gets stuck during the 
cpio:
root@charion:/boot# update-initramfs -u -k 4.15.0-12-generic -b /boot -t -v
Keeping /boot/initrd.img-4.15.0-12-generic.dpkg-bak
update-initramfs: Generating /boot/initrd.img-4.15.0-12-generic
Copying module directory kernel/drivers/usb/host
(excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci-hcd.ko)
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp116x-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/ssb/ssb.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/ssb-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/r8a66597-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/oxu210hp-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/max3421-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/bcma/bcma.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/bcma-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp1362-hcd.ko
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/fotg210-hcd.ko
Copying module directory kernel/drivers/usb/c67x00
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/c67x00/c67x00.ko
Copying module directory kernel/drivers/usb/chipidea
Adding module 
/lib/modules/4.15.0-12-generic/kernel/drivers/usb/gadget/udc/udc-core.ko
[...]

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0
  Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0
  Adding binary /sbin/dumpe2fs
  Calling hook dmsetup
  Calling hook klibc-utils
  /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not 
executable
  /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
  dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_files.so.2
  Adding library /lib/i386-linux-gnu/libnss_files-2.27.so
  dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so
  dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2
  Adding library-link /lib/i386-linux-gnu/libresolv.so.2
  Adding library /lib/i386-linux-gnu/libresolv-2.27.so
  Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:17:40 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 143
  InstallationDate: Installed on 2018-02-28 (17 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  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 143
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1756593

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0
  Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0
  Adding binary /sbin/dumpe2fs
  Calling hook dmsetup
  Calling hook klibc-utils
  /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not 
executable
  /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
  dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_files.so.2
  Adding library /lib/i386-linux-gnu/libnss_files-2.27.so
  dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so
  dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2
  Adding library-link /lib/i386-linux-gnu/libresolv.so.2
  Adding library /lib/i386-linux-gnu/libresolv-2.27.so
  Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:17:40 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 143
  InstallationDate: Installed on 2018-02-28 (17 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  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 143
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Michael Neuffer]

Public bug reported:

Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0
Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0
Adding binary /sbin/dumpe2fs
Calling hook dmsetup
Calling hook klibc-utils
/usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2
Adding library-link /lib/i386-linux-gnu/libnss_files.so.2
Adding library /lib/i386-linux-gnu/libnss_files-2.27.so
dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2
Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2
Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so
dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2
Adding library-link /lib/i386-linux-gnu/libresolv.so.2
Adding library /lib/i386-linux-gnu/libresolv-2.27.so
Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 17 21:17:40 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 143
InstallationDate: Installed on 2018-02-28 (17 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
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 143
UpgradeStatus: No upgrade log present (probably fresh install)

** 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/1756593

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0
  Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0
  Adding binary /sbin/dumpe2fs
  Calling hook dmsetup
  Calling hook klibc-utils
  /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not 
executable
  /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
  /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
  dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_files.so.2
  Adding library /lib/i386-linux-gnu/libnss_files-2.27.so
  dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2
  Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so
  dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2
  Adding library-link /lib/i386-linux-gnu/libresolv.so.2
  Adding library /lib/i386-linux-gnu/libresolv-2.27.so
  Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:17:40 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 143
  InstallationDate: Installed on 2018-02-28 (17 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  

[Touch-packages] [Bug 1756324] Re: No signal after upgrading on 18.04

[Launchpad Bug Tracker]

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

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

Title:
  No signal after upgrading on 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
  the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
  just boots to nothing, my screen display "No signal detected",
  although I can hear the drum sound. Using nomodeset works but my
  computer is set at a wrong frequency (stuck to 77Hz, even forcing via
  xrandr doesn't work). So using nomodeset  I got into i3, downloaded
  mesa drivers and tried radeon too, and rebooted. Now still shows no
  signal, but I can get into a fluent 60Hz i3, if I go to recovery mode,
  then press normal boot. The problem also with that is that GNOME
  doesn't work, when I leave i3, log onto GNOME, it shows a blackscreen
  and just sends me back to the login menu. I've noticed this error
  appeared at boot: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

  Here's xrandr output: xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  0.00* 
 1280x1024  0.00  
 1024x768   0.00  
 800x6000.00  
 640x4800.00  

  
  Thanks for any future help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756324/+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 1756324] Re: No signal after upgrading on 18.04

[Jhonny Oliveira]

I'm not entirely sure if this is related, but I'm also having the same
error and games that rely on opengl stoped working since (~02/03/2018 -
dd-mm-):

I have an AMD Radeon HD 7850 installed.

It seems to be related to the xorg update or the other ones around (please see 
attachment):
/var/log/apt/history
xserver-xorg-core:amd64 (2:1.19.6-1ubuntu1, 2:1.19.6-1ubuntu2)


/var/log/kernel
Mar 15 19:21:22 dktp kernel: [2.118654] [drm] VGACON disable radeon kernel 
modesetting.
Mar 15 19:21:22 dktp kernel: [2.118687] [drm:radeon_init [radeon]] *ERROR* 
No UMS support in radeon module!
Mar 15 19:21:22 dktp kernel: [2.216849] [drm:amdgpu_init [amdgpu]] *ERROR* 
VGACON disables amdgpu kernel modesetting.

Making a basic tests, it seems to perform better with software
rendering... ?!?

$ glxgears -info
GL_RENDERER = AMD PITCAIRN (DRM 2.50.0 / 4.15.0-11-generic, LLVM 5.0.1)
GL_VERSION = 3.0 Mesa 18.0.0-rc4
GL_VENDOR = X.Org
(...)
VisualID 1064, 0x428
355 frames in 5.0 seconds = 70.940 FPS
300 frames in 5.0 seconds = 59.997 FPS

$ LIBGL_ALWAYS_SOFTWARE=1 glxgears -info
GL_RENDERER = llvmpipe (LLVM 5.0, 128 bits)
GL_VERSION = 3.0 Mesa 18.0.0-rc4
GL_VENDOR = VMware, Inc.
(...)
VisualID 1064, 0x428
6604 frames in 5.0 seconds = 1320.753 FPS
6758 frames in 5.0 seconds = 1351.475 FPS

Further details:
$ xdpyinfo | grep DRI
DRI2
DRI3
$ lspci -k | grep -EA3 'VGA|3D|Display' 
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB 
GDDR5 DVI-I/DVI-D/HDMI/DP
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

Can anyone help?

** Attachment added: "Radeon.issue"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756324/+attachment/5082513/+files/Radeon.issue

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

Title:
  No signal after upgrading on 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
  the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
  just boots to nothing, my screen display "No signal detected",
  although I can hear the drum sound. Using nomodeset works but my
  computer is set at a wrong frequency (stuck to 77Hz, even forcing via
  xrandr doesn't work). So using nomodeset  I got into i3, downloaded
  mesa drivers and tried radeon too, and rebooted. Now still shows no
  signal, but I can get into a fluent 60Hz i3, if I go to recovery mode,
  then press normal boot. The problem also with that is that GNOME
  doesn't work, when I leave i3, log onto GNOME, it shows a blackscreen
  and just sends me back to the login menu. I've noticed this error
  appeared at boot: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

  Here's xrandr output: xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  0.00* 
 1280x1024  0.00  
 1024x768   0.00  
 800x6000.00  
 640x4800.00  

  
  Thanks for any future help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756324/+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 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proces

[Launchpad Bug Tracker]

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

** 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/1467588

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Expired
Status in apport package in Ubuntu:
  Confirmed
Status in synaptic package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zenity package in Ubuntu:
  Confirmed

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467588/+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 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proces

[Jerry Quinn]

It's very easy to reproduce this:

jlquinn@cerberus:~/Pictures$ zenity --info --text='Hi there'
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Ubuntu 16.04

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Expired
Status in apport package in Ubuntu:
  Confirmed
Status in synaptic package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zenity package in Ubuntu:
  Confirmed

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467588/+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 1756581] [NEW] Greeter is not showing. I get wallpaper and can enter password.

[Mike Bee]

Public bug reported:

I'm only seeing greeter wall paper.  There is no username or dialog box
to enter my password -- no prompt.  However, if I blindly type my
password, I can log on.  I was installing cuda 8.0 today.  I entered:

sudo nvidia-xconfig --enable-all-gpus
sudo nvidia-xconfig --cool-bits=12

and then I restarted lightdm with

sudo systemctl restart lightdm.service

After that the system rebooted, and I no longer saw a greeter prompt.

I appreciate any help.

Thank you,

MikeyBee

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lightdm 1.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Mar 17 14:47:20 2018
InstallationDate: Installed on 2017-05-08 (313 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Greeter is not showing.  I get wallpaper and can enter password.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm only seeing greeter wall paper.  There is no username or dialog
  box to enter my password -- no prompt.  However, if I blindly type my
  password, I can log on.  I was installing cuda 8.0 today.  I entered:

  sudo nvidia-xconfig --enable-all-gpus
  sudo nvidia-xconfig --cool-bits=12

  and then I restarted lightdm with

  sudo systemctl restart lightdm.service

  After that the system rebooted, and I no longer saw a greeter prompt.

  I appreciate any help.

  Thank you,

  MikeyBee

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Mar 17 14:47:20 2018
  InstallationDate: Installed on 2017-05-08 (313 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756581/+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 1538284] Re: Unescaped left brace in regex is deprecated

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.8-3.6ubuntu1

---
pam (1.1.8-3.6ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable.
- Fixes unescaped brace in pam_getenv regex.  LP: #1538284.
- Fixes pam_namespace defaults for compatibility with dash.  LP: #1081323.
  * Remaining changes:
- debian/control: have libpam-modules recommend update-motd package
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
  not present there or in /etc/security/pam_env.conf. (should send to
  Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
  there are non-default services running.
- debian/libpam0g.postinst: check if gdm is actually running before
  trying to reload it.
- debian/libpam0g.postinst: the init script for 'samba' is now named
  'smbd' in Ubuntu, so fix the restart handling.
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
  initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/pam_umask_usergroups_from_login.defs.patch:
  Deprecate pam_unix's explicit "usergroups" option and instead read it
  from /etc/login.def's "USERGROUP_ENAB" option if umask is only defined
  there. This restores compatibility with the pre-PAM behaviour of login.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
  /etc/legal once, then set a flag in the user's homedir to prevent
  showing it again.
- debian/update-motd.5, debian/libpam-modules.manpages: add a manpage
  for update-motd, with some best practices and notes of explanation.
- debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8)
  to update-motd(5)
- debian/local/common-session{,-noninteractive}: Enable pam_umask by
  default, now that the umask setting is gone from /etc/profile.
- debian/local/pam-auth-update: Add the new md5sums for pam_umask addition.
- debian/patches-applied/extrausers.patch: Add a pam_extrausers module
  that is basically just a copy of pam_unix but looks at
  /var/lib/extrausers/{group,passwd,shadow} instead of /etc/
- debian/libpam-modules-bin.install: install the helper binaries for
  pam_extrausers to /sbin
- debian/rules: Make pam_extrausers_chkpwd sguid shadow
- pam-configs/mkhomedir: Added a config for pam_mkhomedir, disabled
  by default.
- don't notify about xdm restarts during a release-upgrade
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
  so they don't get regenerated during build and cause a multiarch
  installation issue.
  * Dropped changes, included in Debian:
- Build-depend on libfl-dev.
- debian/patches-applied/pam-limits-nofile-fd-setsize-cap: cap the default
  soft nofile limit read from pid 1 to FD_SETSIZE.
  * Fix references to /var/run in update-motd.5.  LP: #1571864
  * Fix service restart handling to integrate with systemd instead of
upstart.

pam (1.1.8-3.6) unstable; urgency=medium

  * Non-maintainer upload.
  * cve-2015-3238.patch: Add the changes in the generated pam_exec.8
and pam_unix.8 in addition to (and after) the changes to the
source .xml files. This avoids unwanted rebuilds that can cause
problems due to differing files on different architectures of
the Multi-Arch: same libpam-modules. (Closes: #851545)

pam (1.1.8-3.5) unstable; urgency=medium

  * Non-maintainer upload.
  * Build-Depend on libfl-dev:native as well, for cross builds.
Re-closes: #846459
  * Fix "Unescaped left brace in regex" with Perl 5.22. Closes: #810873

pam (1.1.8-3.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Add libfl-dev to Build-Depends, fixing FTBFS.  Closes: #846459
  * Move xsl stuff to Build-Depends from -Indep to fix misbuilt manpages.
Closes: #812566

pam (1.1.8-3.3) unstable; urgency=low

  * Non-maintainer upload.
  [ Steve Langasek ]
  * Updated Swedish translation to correct a typo, thanks to Anders Jonsson
and Martin Bagge.  Closes: #743875
  * Updated Turkish translation, thanks to Mert Dirik .
(closes: #756756)
  * d/applied-patches/pam-limits-nofile-fd-setsize-cap: cap the default
soft nofile limit read from pid 1 to FD_SETSIZE.  Thanks to Robie Basak
 for the patch.  Closes: #783105.
  * Acknowledge security NMU.
  * pam-auth-update: don't mishandle trailing whitespace in profiles.
LP: #1487103.

  [ Laurent Bigonville ]
  * debian/control: Fix Vcs-* and Homepage fields (Closes: #752343)
  * debian/watch: Update watch file and point it to http://www.linux-pam.org
  * debian/patches-applied/pam_namespace_fix_bashism.patch: Fix bashism in
namespace.init script (Closes: #624842)
  * debian/control: Build-depends against debhelper (>= 9) to match the
defined debhelper compatibility
  * Rename the cve-2011-4708.patch to cve-2010-4708.patch to match reality,
   

[Touch-packages] [Bug 1081323] Re: /bin/sh illegal option -p when using pam_namespace.so

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.8-3.6ubuntu1

---
pam (1.1.8-3.6ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable.
- Fixes unescaped brace in pam_getenv regex.  LP: #1538284.
- Fixes pam_namespace defaults for compatibility with dash.  LP: #1081323.
  * Remaining changes:
- debian/control: have libpam-modules recommend update-motd package
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
  not present there or in /etc/security/pam_env.conf. (should send to
  Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
  there are non-default services running.
- debian/libpam0g.postinst: check if gdm is actually running before
  trying to reload it.
- debian/libpam0g.postinst: the init script for 'samba' is now named
  'smbd' in Ubuntu, so fix the restart handling.
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
  initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/pam_umask_usergroups_from_login.defs.patch:
  Deprecate pam_unix's explicit "usergroups" option and instead read it
  from /etc/login.def's "USERGROUP_ENAB" option if umask is only defined
  there. This restores compatibility with the pre-PAM behaviour of login.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
  /etc/legal once, then set a flag in the user's homedir to prevent
  showing it again.
- debian/update-motd.5, debian/libpam-modules.manpages: add a manpage
  for update-motd, with some best practices and notes of explanation.
- debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8)
  to update-motd(5)
- debian/local/common-session{,-noninteractive}: Enable pam_umask by
  default, now that the umask setting is gone from /etc/profile.
- debian/local/pam-auth-update: Add the new md5sums for pam_umask addition.
- debian/patches-applied/extrausers.patch: Add a pam_extrausers module
  that is basically just a copy of pam_unix but looks at
  /var/lib/extrausers/{group,passwd,shadow} instead of /etc/
- debian/libpam-modules-bin.install: install the helper binaries for
  pam_extrausers to /sbin
- debian/rules: Make pam_extrausers_chkpwd sguid shadow
- pam-configs/mkhomedir: Added a config for pam_mkhomedir, disabled
  by default.
- don't notify about xdm restarts during a release-upgrade
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
  so they don't get regenerated during build and cause a multiarch
  installation issue.
  * Dropped changes, included in Debian:
- Build-depend on libfl-dev.
- debian/patches-applied/pam-limits-nofile-fd-setsize-cap: cap the default
  soft nofile limit read from pid 1 to FD_SETSIZE.
  * Fix references to /var/run in update-motd.5.  LP: #1571864
  * Fix service restart handling to integrate with systemd instead of
upstart.

pam (1.1.8-3.6) unstable; urgency=medium

  * Non-maintainer upload.
  * cve-2015-3238.patch: Add the changes in the generated pam_exec.8
and pam_unix.8 in addition to (and after) the changes to the
source .xml files. This avoids unwanted rebuilds that can cause
problems due to differing files on different architectures of
the Multi-Arch: same libpam-modules. (Closes: #851545)

pam (1.1.8-3.5) unstable; urgency=medium

  * Non-maintainer upload.
  * Build-Depend on libfl-dev:native as well, for cross builds.
Re-closes: #846459
  * Fix "Unescaped left brace in regex" with Perl 5.22. Closes: #810873

pam (1.1.8-3.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Add libfl-dev to Build-Depends, fixing FTBFS.  Closes: #846459
  * Move xsl stuff to Build-Depends from -Indep to fix misbuilt manpages.
Closes: #812566

pam (1.1.8-3.3) unstable; urgency=low

  * Non-maintainer upload.
  [ Steve Langasek ]
  * Updated Swedish translation to correct a typo, thanks to Anders Jonsson
and Martin Bagge.  Closes: #743875
  * Updated Turkish translation, thanks to Mert Dirik .
(closes: #756756)
  * d/applied-patches/pam-limits-nofile-fd-setsize-cap: cap the default
soft nofile limit read from pid 1 to FD_SETSIZE.  Thanks to Robie Basak
 for the patch.  Closes: #783105.
  * Acknowledge security NMU.
  * pam-auth-update: don't mishandle trailing whitespace in profiles.
LP: #1487103.

  [ Laurent Bigonville ]
  * debian/control: Fix Vcs-* and Homepage fields (Closes: #752343)
  * debian/watch: Update watch file and point it to http://www.linux-pam.org
  * debian/patches-applied/pam_namespace_fix_bashism.patch: Fix bashism in
namespace.init script (Closes: #624842)
  * debian/control: Build-depends against debhelper (>= 9) to match the
defined debhelper compatibility
  * Rename the cve-2011-4708.patch to cve-2010-4708.patch to match reality,
   

[Touch-packages] [Bug 1487103] Re: [PATCH] pam-auth-update - don't break because of trailing whitespace in /usr/share/pam-configs/* files

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.8-3.6ubuntu1

---
pam (1.1.8-3.6ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable.
- Fixes unescaped brace in pam_getenv regex.  LP: #1538284.
- Fixes pam_namespace defaults for compatibility with dash.  LP: #1081323.
  * Remaining changes:
- debian/control: have libpam-modules recommend update-motd package
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
  not present there or in /etc/security/pam_env.conf. (should send to
  Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
  there are non-default services running.
- debian/libpam0g.postinst: check if gdm is actually running before
  trying to reload it.
- debian/libpam0g.postinst: the init script for 'samba' is now named
  'smbd' in Ubuntu, so fix the restart handling.
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
  initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/pam_umask_usergroups_from_login.defs.patch:
  Deprecate pam_unix's explicit "usergroups" option and instead read it
  from /etc/login.def's "USERGROUP_ENAB" option if umask is only defined
  there. This restores compatibility with the pre-PAM behaviour of login.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
  /etc/legal once, then set a flag in the user's homedir to prevent
  showing it again.
- debian/update-motd.5, debian/libpam-modules.manpages: add a manpage
  for update-motd, with some best practices and notes of explanation.
- debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8)
  to update-motd(5)
- debian/local/common-session{,-noninteractive}: Enable pam_umask by
  default, now that the umask setting is gone from /etc/profile.
- debian/local/pam-auth-update: Add the new md5sums for pam_umask addition.
- debian/patches-applied/extrausers.patch: Add a pam_extrausers module
  that is basically just a copy of pam_unix but looks at
  /var/lib/extrausers/{group,passwd,shadow} instead of /etc/
- debian/libpam-modules-bin.install: install the helper binaries for
  pam_extrausers to /sbin
- debian/rules: Make pam_extrausers_chkpwd sguid shadow
- pam-configs/mkhomedir: Added a config for pam_mkhomedir, disabled
  by default.
- don't notify about xdm restarts during a release-upgrade
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
  so they don't get regenerated during build and cause a multiarch
  installation issue.
  * Dropped changes, included in Debian:
- Build-depend on libfl-dev.
- debian/patches-applied/pam-limits-nofile-fd-setsize-cap: cap the default
  soft nofile limit read from pid 1 to FD_SETSIZE.
  * Fix references to /var/run in update-motd.5.  LP: #1571864
  * Fix service restart handling to integrate with systemd instead of
upstart.

pam (1.1.8-3.6) unstable; urgency=medium

  * Non-maintainer upload.
  * cve-2015-3238.patch: Add the changes in the generated pam_exec.8
and pam_unix.8 in addition to (and after) the changes to the
source .xml files. This avoids unwanted rebuilds that can cause
problems due to differing files on different architectures of
the Multi-Arch: same libpam-modules. (Closes: #851545)

pam (1.1.8-3.5) unstable; urgency=medium

  * Non-maintainer upload.
  * Build-Depend on libfl-dev:native as well, for cross builds.
Re-closes: #846459
  * Fix "Unescaped left brace in regex" with Perl 5.22. Closes: #810873

pam (1.1.8-3.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Add libfl-dev to Build-Depends, fixing FTBFS.  Closes: #846459
  * Move xsl stuff to Build-Depends from -Indep to fix misbuilt manpages.
Closes: #812566

pam (1.1.8-3.3) unstable; urgency=low

  * Non-maintainer upload.
  [ Steve Langasek ]
  * Updated Swedish translation to correct a typo, thanks to Anders Jonsson
and Martin Bagge.  Closes: #743875
  * Updated Turkish translation, thanks to Mert Dirik .
(closes: #756756)
  * d/applied-patches/pam-limits-nofile-fd-setsize-cap: cap the default
soft nofile limit read from pid 1 to FD_SETSIZE.  Thanks to Robie Basak
 for the patch.  Closes: #783105.
  * Acknowledge security NMU.
  * pam-auth-update: don't mishandle trailing whitespace in profiles.
LP: #1487103.

  [ Laurent Bigonville ]
  * debian/control: Fix Vcs-* and Homepage fields (Closes: #752343)
  * debian/watch: Update watch file and point it to http://www.linux-pam.org
  * debian/patches-applied/pam_namespace_fix_bashism.patch: Fix bashism in
namespace.init script (Closes: #624842)
  * debian/control: Build-depends against debhelper (>= 9) to match the
defined debhelper compatibility
  * Rename the cve-2011-4708.patch to cve-2010-4708.patch to match reality,
   

[Touch-packages] [Bug 1571864] Re: update-motd.5 manpage references /var/run/motd

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.8-3.6ubuntu1

---
pam (1.1.8-3.6ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable.
- Fixes unescaped brace in pam_getenv regex.  LP: #1538284.
- Fixes pam_namespace defaults for compatibility with dash.  LP: #1081323.
  * Remaining changes:
- debian/control: have libpam-modules recommend update-motd package
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
  not present there or in /etc/security/pam_env.conf. (should send to
  Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
  there are non-default services running.
- debian/libpam0g.postinst: check if gdm is actually running before
  trying to reload it.
- debian/libpam0g.postinst: the init script for 'samba' is now named
  'smbd' in Ubuntu, so fix the restart handling.
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
  initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/pam_umask_usergroups_from_login.defs.patch:
  Deprecate pam_unix's explicit "usergroups" option and instead read it
  from /etc/login.def's "USERGROUP_ENAB" option if umask is only defined
  there. This restores compatibility with the pre-PAM behaviour of login.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
  /etc/legal once, then set a flag in the user's homedir to prevent
  showing it again.
- debian/update-motd.5, debian/libpam-modules.manpages: add a manpage
  for update-motd, with some best practices and notes of explanation.
- debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8)
  to update-motd(5)
- debian/local/common-session{,-noninteractive}: Enable pam_umask by
  default, now that the umask setting is gone from /etc/profile.
- debian/local/pam-auth-update: Add the new md5sums for pam_umask addition.
- debian/patches-applied/extrausers.patch: Add a pam_extrausers module
  that is basically just a copy of pam_unix but looks at
  /var/lib/extrausers/{group,passwd,shadow} instead of /etc/
- debian/libpam-modules-bin.install: install the helper binaries for
  pam_extrausers to /sbin
- debian/rules: Make pam_extrausers_chkpwd sguid shadow
- pam-configs/mkhomedir: Added a config for pam_mkhomedir, disabled
  by default.
- don't notify about xdm restarts during a release-upgrade
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
  so they don't get regenerated during build and cause a multiarch
  installation issue.
  * Dropped changes, included in Debian:
- Build-depend on libfl-dev.
- debian/patches-applied/pam-limits-nofile-fd-setsize-cap: cap the default
  soft nofile limit read from pid 1 to FD_SETSIZE.
  * Fix references to /var/run in update-motd.5.  LP: #1571864
  * Fix service restart handling to integrate with systemd instead of
upstart.

pam (1.1.8-3.6) unstable; urgency=medium

  * Non-maintainer upload.
  * cve-2015-3238.patch: Add the changes in the generated pam_exec.8
and pam_unix.8 in addition to (and after) the changes to the
source .xml files. This avoids unwanted rebuilds that can cause
problems due to differing files on different architectures of
the Multi-Arch: same libpam-modules. (Closes: #851545)

pam (1.1.8-3.5) unstable; urgency=medium

  * Non-maintainer upload.
  * Build-Depend on libfl-dev:native as well, for cross builds.
Re-closes: #846459
  * Fix "Unescaped left brace in regex" with Perl 5.22. Closes: #810873

pam (1.1.8-3.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Add libfl-dev to Build-Depends, fixing FTBFS.  Closes: #846459
  * Move xsl stuff to Build-Depends from -Indep to fix misbuilt manpages.
Closes: #812566

pam (1.1.8-3.3) unstable; urgency=low

  * Non-maintainer upload.
  [ Steve Langasek ]
  * Updated Swedish translation to correct a typo, thanks to Anders Jonsson
and Martin Bagge.  Closes: #743875
  * Updated Turkish translation, thanks to Mert Dirik .
(closes: #756756)
  * d/applied-patches/pam-limits-nofile-fd-setsize-cap: cap the default
soft nofile limit read from pid 1 to FD_SETSIZE.  Thanks to Robie Basak
 for the patch.  Closes: #783105.
  * Acknowledge security NMU.
  * pam-auth-update: don't mishandle trailing whitespace in profiles.
LP: #1487103.

  [ Laurent Bigonville ]
  * debian/control: Fix Vcs-* and Homepage fields (Closes: #752343)
  * debian/watch: Update watch file and point it to http://www.linux-pam.org
  * debian/patches-applied/pam_namespace_fix_bashism.patch: Fix bashism in
namespace.init script (Closes: #624842)
  * debian/control: Build-depends against debhelper (>= 9) to match the
defined debhelper compatibility
  * Rename the cve-2011-4708.patch to cve-2010-4708.patch to match reality,
   

[Touch-packages] [Bug 1756364] Re: [ffe] Livepatch integration

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => New

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

Title:
  [ffe] Livepatch integration

Status in software-properties package in Ubuntu:
  New

Bug description:
  One feature we want to add to the desktop for the LTS is to allow
  users to enable livepatch from the desktop.

  The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
  
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

  That's based on the gnome-online-account ubuntu sso provider which has
  been added to bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1756364/+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 1756364] Re: [ffe] Livepatch integration

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  [ffe] Livepatch integration

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  One feature we want to add to the desktop for the LTS is to allow
  users to enable livepatch from the desktop.

  The software-properties utility has been updated to add a control allowing to 
enable livepatch, the code is up for review there:
  
https://code.launchpad.net/~azzar1/software-properties/add-canonical-livepatch/+merge/341427

  That's based on the gnome-online-account ubuntu sso provider which has
  been added to bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1756364/+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 1756446] Re: Include JournalErrors.txt

[Sebastien Bacher]

Indeed without the error logs it's often difficult to guess what the
issue is. Even some limited sample or filtered values would be better
than having nothing included as today.

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

Title:
  Include JournalErrors.txt

Status in whoopsie package in Ubuntu:
  New

Bug description:
  JournalErrors is not in the list of acceptable_fields for whoopsie,
  this is a good thing given how large it can get. That being said it
  would be useful (per seb128) to include a portion of JournalErrors in
  the crash reports in the Error Tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756446/+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 1656100] Re: Unable to remove signing keys using gnome-software-properties

[Scott Palmer]

Confirmed.  This affects me on an up-to-date 18.04.

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

Title:
  Unable to remove signing keys using gnome-software-properties

Status in Ubuntu GNOME:
  Invalid
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am
  unable to remove signing keys in the Authentication tab. If I select a
  key I wish to remove and click the Remove button, either nothing will
  happen, or it will ask me for authentication, upon giving it the
  correct password all that will happen is it will deselect the key I
  select, but at no point will it actually remove it, which is rather
  annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 12 21:35:55 2017
  InstallationDate: Installed on 2017-01-09 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1656100/+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 1753954] Re: Intel Whiskey Lake (WHL) graphics support

[Launchpad Bug Tracker]

This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu3

---
xorg-server (2:1.19.6-1ubuntu3) bionic; urgency=medium

  * dri2-Sync-i965_pci_ids.h-from-Mesa.patch: Update i965_pci_ids.h to
include latest CFL. (LP: #1753954)
  * server-1.19.diff: Pull fixes from upstream stable branch.
(LP: #1748926)

 -- Timo Aaltonen   Tue, 13 Mar 2018 11:59:01 +0200

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

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1756169] Re: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Failure on upgrade to 4.13.0-37-generic. Fixed with "dpkg --configure
  -a"

  1) Ubuntu release
  Description:Ubuntu 17.10
  Release:17.10

  2) Package version

  initramfs-tools:
Installed: 0.125ubuntu12
Candidate: 0.125ubuntu12
Version table:
   *** 0.125ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  3) Expected result
  Successful upgrade

  4) Actual result

  Commandline: aptdaemon role='role-commit-packages' sender=':1.15386'
  Install: linux-signed-image-4.13.0-37-generic:amd64 (4.13.0-37.42, 
automatic), linux-image-extra-4.13.0-37-generic:amd64 (4.13.0-37.42, 
automatic), linux-tools-4.13.0-37-generic:amd64 (4.13.0-37.42, automatic), 
linux-headers-4.13.0-37-generic:amd64 (4.13.0-37.42, automatic), 
linux-headers-4.13.0-37:amd64 (4.13.0-37.42, automatic), 
linux-tools-4.13.0-37:amd64 (4.13.0-37.42, automatic), 
linux-image-4.13.0-37-generic:amd64 (4.13.0-37.42, automatic)
  Upgrade: linux-tools-generic:amd64 (4.13.0.36.38, 4.13.0.37.40), 
linux-headers-generic:amd64 (4.13.0.36.38, 4.13.0.37.40), linux-libc-dev:amd64 
(4.13.0-36.40, 4.13.0-37.42), libcurl3:amd64 (7.55.1-1ubuntu2.3, 
7.55.1-1ubuntu2.4), linux-image-generic:amd64 (4.13.0.36.38, 4.13.0.37.40), 
linux-signed-image-generic:amd64 (4.13.0.36.38, 4.13.0.37.40), 
libcurl4-gnutls-dev:amd64 (7.55.1-1ubuntu2.3, 7.55.1-1ubuntu2.4), 
linux-signed-generic:amd64 (4.13.0.36.38, 4.13.0.37.40), 
firefox-locale-en:amd64 (58.0.2+build1-0ubuntu0.17.10.1, 
59.0+build5-0ubuntu0.17.10.1), firefox-locale-ru:amd64 
(58.0.2+build1-0ubuntu0.17.10.1, 59.0+build5-0ubuntu0.17.10.1), 
linux-image-extra-virtual:amd64 (4.13.0.36.38, 4.13.0.37.40), firefox:amd64 
(58.0.2+build1-0ubuntu0.17.10.1, 59.0+build5-0ubuntu0.17.10.1), 
linux-tools-common:amd64 (4.13.0-36.40, 4.13.0-37.42), curl:amd64 
(7.55.1-1ubuntu2.3, 7.55.1-1ubuntu2.4), linux-generic:amd64 (4.13.0.36.38, 
4.13.0.37.40), libcurl3-gnutls:amd64 (7.55.1-1ubuntu2.3, 7.55.1-1ubuntu2.4)
  Error: Sub-process /usr/bin/dpkg returned an error code (2)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   ericb  9557 F...m pulseaudio
   /dev/snd/controlC0:  ericb  9557 F pulseaudio
  Date: Thu Mar 15 18:40:01 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=80eb49d9-d022-4d10-b1b2-f48b38027aeb
  InstallationDate: Installed on 2017-01-26 (412 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro nosplash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to artful on 2017-11-06 (128 days ago)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 1756555] [NEW] Include openshot.developers stable PPA contents in default Ubuntu repos

[Jeb E.]

Public bug reported:

Please include the Stable 'openshot.developers' PPA contents in the default 
Ubuntu "universe" repositories. Openshot is the premiere (and pretty much only) 
solution out there for Linux GUI machines as an alternative to (defunct) 
Windows Movie Maker and most of the basics in Adobe Premiere Pro and Elements. 
Openshot has progressed quite a bit since added to the Ubuntu repos, but the 
actual new "stable" versions published by the Openshot developers have not been 
added to these same repos.

Current version in Ubuntu (17.10) repos: 1.4.3
Latest actual stable version published in 'openshot.developers' PPA: 2.4.1

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apt 1.5.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13
Uname: Linux 4.13.0-37-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 17 10:15:01 2018
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt
 Importance: Undecided
 Status: New

** Affects: openshot
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug artful wayland-session

** Also affects: apt
   Importance: Undecided
   Status: New

** Also affects: openshot
   Importance: Undecided
   Status: New

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

Title:
  Include openshot.developers stable PPA contents in default Ubuntu
  repos

Status in APT:
  New
Status in OpenShot Video Editor:
  New
Status in apt package in Ubuntu:
  New

Bug description:
  Please include the Stable 'openshot.developers' PPA contents in the default 
Ubuntu "universe" repositories. Openshot is the premiere (and pretty much only) 
solution out there for Linux GUI machines as an alternative to (defunct) 
Windows Movie Maker and most of the basics in Adobe Premiere Pro and Elements. 
  Openshot has progressed quite a bit since added to the Ubuntu repos, but the 
actual new "stable" versions published by the Openshot developers have not been 
added to these same repos.

  Current version in Ubuntu (17.10) repos: 1.4.3
  Latest actual stable version published in 'openshot.developers' PPA: 2.4.1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13
  Uname: Linux 4.13.0-37-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 10:15:01 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1756555/+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 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Antoine Monmayrant]

Hello again,

Here is another way to look at this unexpected unknown key press and airplane 
mode activated (ie wifi killed):
acpi_listen 
# Folding to tablet mode and back to laptop mode again
button/wlan WLAN 0080  K
button/wlan WLAN 0080  K
button/wlan WLAN 0080  K

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 

[Touch-packages] [Bug 1754888] Re: Menulibre: invalid desktop files detected!

[Launchpad Bug Tracker]

This bug was fixed in the package xubuntu-default-settings - 18.04.4

---
xubuntu-default-settings (18.04.4) bionic; urgency=medium

  * Fix invalid desktop files (LP: #1754888)
- usr/share/xubuntu/applications/Thunar-bulk-rename.desktop
- usr/share/xubuntu/applications/Thunar.desktop
- usr/share/xubuntu/applications/debian-uxterm.desktop
- usr/share/xubuntu/applications/debian-xterm.desktop
- usr/share/xubuntu/applications/thunar-settings.desktop
- usr/share/xubuntu/applications/xfce4-terminal.desktop
  * usr/share/xubuntu/templates/xdg-xubuntu-templates:
- Fix FileNotFound error (LP: #1694471)
- Fix UnicodeDecode error (LP: #1668191)
  * etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml:
- Set Net/FallbackIconTheme for correct icon inheritance
  on GTK+ 2 (LP: #1756187)
  * etc/xdg/xdg-xubuntu/xfce4/panel/default.xml:
- Add notification plugin to panel

 -- Sean Davis   Sat, 17 Mar 2018 09:05:16
-0400

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  Menulibre: invalid desktop files detected!

Status in MenuLibre:
  Fix Released
Status in menulibre package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  Not sure whether to report this as a bug, but:

  Running xubuntu 18.04, updated.

  Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13
  18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Menulibre 2.1.5

  On starting menulibre I get a warning: Menulibre: invalid desktop
  files detected!

  See: http://i.imgur.com/Jqdge9z.png

  If I click on details, I get:

  http://i.imgur.com/H7RwsOO.png

  I think these invalid desktop files are part of the initial installation of 
menulibre/xubuntu.
  As a simple end user I do not know what to do with this warning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/menulibre/+bug/1754888/+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 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Antoine Monmayrant]

Hello, I confirm I face the very same bug on my HP Spectre x360 G2 with both 
17.10 and 18.04 beta (it was OK on 17.04):
# Folding to tablet mode and back to laptop mode:
## Unknown keypress is registered:
grep Unknown /var/log/syslog
Mar 17 14:24:53 lyre kernel: [11312.248585] atkbd serio0: 
Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
## Airplane gets activated and has to be manually deactivated

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 

[Touch-packages] [Bug 1756551] Re: perl crashed with SIGABRT in _dbus_abort()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1743216, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082265/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082267/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082271/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082272/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082273/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082274/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1756551/+attachment/5082275/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1743216

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 13:57:30 2018
  ExecutablePath: /usr/bin/perl
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (5 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1756551/+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 8949] Re: Opening a deleted 'recent document' results in a new file.

[Luke B.]

I can confirm this issue no longer affects Ubuntu 18.04, as recently
viewed items are removed upon deletion.

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

Title:
  Opening a deleted 'recent document' results in a new file.

Status in GNOME Panel:
  Invalid
Status in GTK+:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  http://bugzilla.gnome.org/show_bug.cgi?id=143385

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/8949/+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 1756526] Re: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

[dino99]

** Description changed:

  Gnome-shell session on xorg, with no opened apps
  
  Getting this logged:
  
  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running
  
  per https://www.x.org/wiki/FAQErrorMessages/
  
  i join the listening.txt output
  
  and there is no XO-lock file on the system, which seems abnormal.
+ 
+ As this missing XO-lock file should be set by system and/or app, report
+ also against gdm3 & systemd & gnome-shell (no idea which one to blame).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 17 12:10:02 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: r8168, 8.045.08, 4.15.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
-Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
+  Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
+    Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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 N/A
  xserver.bootTime: Wed Feb 28 14:50:36 2018
  xserver.configfile: default
  xserver.devices:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.19.6-1ubuntu2

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

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

** Also affects: gnome-shell (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/1756526

Title:
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Gnome-shell session on xorg, with no opened apps

  Getting this logged:

  oem@ubuntu:~$ journalctl -b | grep XSERV
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransSocketUNIXCreateListener: 
...SocketCreateListener() failed
  /usr/lib/gdm3/gdm-x-session[1289]: _XSERVTransMakeAllCOTSServerListeners: 
server already running

  per https://www.x.org/wiki/FAQErrorMessages/

[Touch-packages] [Bug 1756177] Re: FFe: e2fsprogs 1.44, support for largedir and ea_inode

[Simon Iremonger]

FWIW 'this seems to WORK in bionic, including "make fullcheck" on the
source, system able to check itself on boot, resizing other system
disks, no issues so far as I can.  Thankyou for agreeing//doing this so
quickly.

Backporting related matters to be discussed separately in:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874

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

Title:
  FFe: e2fsprogs 1.44, support for largedir and ea_inode

Status in e2fsprogs package in Ubuntu:
  Fix Released

Bug description:
  e2fsprogs 1.44 landed in Debian unstable on March 8, missing feature
  freeze / Debian import freeze by about a week.  Per upstream
  
(https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/comments/17),
  1.44 includes two new not-enabled-by-default features which would be
  good to have available in the 18.04 userspace: largedir, and ea_inode.

  This is a rather stable and well-maintained codebase with stable
  interfaces, so I believe the risks are small to taking this post-FF.
  The one known change in behavior relative to Ubuntu 16.04 is the
  enablement of metadata checksums by default, which is a change we
  already have via the 1.43.9 package, so shouldn't count against an
  FFe.

  The main (but still small) risk to the release from taking this change
  would be disruption to image builds / installation as a result of
  broken tools.  This would be detected fairly quickly through our
  automated image testing, and if any regressions are introduced we
  should roll back the e2fsprogs update immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1756177/+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 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

[Francis Ginther]

** Tags added: id-5aac06833481524435312429

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  New
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.

  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify
  --w--- 1 root root 4096 Mar 16 13:50 ungroup
  -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs
  -r--r--r-- 1 root root 4096 Mar 16 13:50 state
  drwxr-xr-x 2 root root0 Mar 16 13:50 power
  -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size
  -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name
  -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid
  -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type
  -r--r--r-- 1 root root 4096 Mar 16 13:50 bridge_state
  drwxr-xr-x 2 root root0 Mar 16 13:50 blkt
  drwxr-xr-x 3 root root0 Mar 16 13:50 net

  $ echo 'encc006' | sudo tee driver/unbind 
  encc006
  tee: driver/unbind: No such device

  $ echo 'cdev0' | sudo tee driver/unbind 
  cdev0
  tee: driver/unbind: No such device

  $ echo '0.0.c006' | sudo tee driver/unbind 
  0.0.c006
  ubuntu@s1lp14:/sys/class/net/encc006/device$ Mar 16 13:52:28 s1lp14 
sudo[8046]:   ubuntu : TTY=pts/1 ; PWD=/sys/devices/qeth/0.0.c006 ; USER=root ; 
COMMAND=/usr/bin/tee driver/unbind
  Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session opened for 
user root by ubuntu(uid=0)
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to establish connection.
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time server 
91.189.89.198:123 (ntp.ubuntu.com).
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006.2653: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to establish connection.
  Mar 16 13:52:28 s1lp14 kernel: failed to kill vid 8100/2653 for device encc006
  Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session closed for 
user root
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time server 

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Daniele Besana (WP-OK)]

I installed Slack ignoring the dependency and works:
dpkg --ignore-depends libcurl3 -i slack-desktop-3.1.0-amd64.deb

but now every apt operation tell me there's the broken dependency.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1706837] Re: systemd-journald crashed with SIGABRT in epoll_wait()

[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/1706837

Title:
  systemd-journald crashed with SIGABRT in epoll_wait()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Wed Jul 26 21:03:54 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-03-25 (854 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267
   sd_event_run () from /lib/systemd/libsystemd-shared-233.so
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0
  Title: systemd-journald crashed with SIGABRT in error_tail()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-yakkety
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-yakkety
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706837/+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 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

[dino99]

Doing some testing:

- first modifying options into /etc/gdm3/custom.conf 
   set [daemon] WaylandEnable=false to force xorg login :
 my feeling is that should be the default now as ubuntu as made that choice for 
the release (and wayland / apps still does not well together in many cases)

- then rebboting

And now the problem existing with my hardware and reported here is gone: no 
distorted screen.
That system is using the 'proposed' archive and is fully updated.
What is also different now: the login options (gear button) have dropped the 
wayland ones.

So my conclusion are:
- /etc/gdm3/custom.conf  should use xorg, not wayland
- the issue reported gere seems have been introduced by the wayland (1.14.0-2) 
changes (patch)

*
wayland (1.14.0-2) unstable; urgency=medium

  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
- libXcursor before 1.1.15 has various integer overflows that could lead
  to heap buffer overflows when processing malicious cursors, e.g., with
  programs like GIMP. It is also possible that an attack vector exists
  against the related code in cursor/xcursor.c in Wayland through
  1.14.0.
  * switch back to use upstream tarball
  * debian/control: bump standards version, drop priority stanzas

 -- Héctor Orón Martínez   Sun, 04 Mar 2018 11:56:31 +0100
***

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-16612

** Package changed: mutter (Ubuntu) => gdm3 (Ubuntu)

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

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

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

** Changed in: wayland (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Graphics corruption just before login animation to Xorg sessions
  (Intel gen9 GPUs only)

Status in X.Org X server:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  New

Bug description:
  Immediately after login (I enter the password and hit enter) the screen 
"crumbles" for few seconds, then all becomes normal and the system works fine. 
I have done apt update+upgrade many times, also with proposed enabled, I have 
also installed a new ISO (now i'm using the Alpha dated 20180305) but the 
problem remains. The problem happens with the x11 session but not with wayland. 
  Also problem does not show with different hardware. 

  corrado@corrado-p7-bb-0305:~$ inxi -Fx
  System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 
gcc: 7.3.0
 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu 
Bionic Beaver (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 
3081 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 38.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: 
systemd runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.181) inxi: 2.3.56 
  corrado@corrado-p7-bb-0305:~$

  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: ubuntu:GNOME
  Date: Tue Mar  6 15:47:50 2018
  DistUpgraded: Fresh install
  

[Touch-packages] [Bug 1756511] [NEW] Xorg freezes on bionic kernel 4.15.0-12

[Rob Ludwick]

Public bug reported:

Similar thing that happens here:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839

The difference is that I can't log in.  So it dies before it asks me to
login.

The workaround is to boot into an old kernel.

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

** Description changed:

- Same thing that happens here:
+ I have a Dell XPS 15 9650, and it freezes with the latest kernel for
+ bionic.
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
  
- And freezes in exactly the same way.
+ The solution is to run a very old kernel.

** Description changed:

- I have a Dell XPS 15 9650, and it freezes with the latest kernel for
- bionic.
+ Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
- 
- The solution is to run a very old kernel.

** Description changed:

  Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
+ 
+ The difference is that I can't log in.  So it dies before it asks me to
+ login.

** Description changed:

  Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
  
  The difference is that I can't log in.  So it dies before it asks me to
  login.
+ 
+ The workaround is to boot into an old kernel.

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

Title:
  Xorg freezes on bionic kernel 4.15.0-12

Status in xorg package in Ubuntu:
  New

Bug description:
  Similar thing that happens here:

  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839

  The difference is that I can't log in.  So it dies before it asks me
  to login.

  The workaround is to boot into an old kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756511/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

[Simon Iremonger]

e2fsprogs 1.44.0 for bionic18.04 has apparently been agreed:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1756177

[launchpad build-logs suggest its' been built for PROPOSED but not yet
seen it 'come through' as a package or appear on 'packages.ubuntu.com'
...].

Hopefully that will go through.  Is the first-step thereafter, to then
"xenial-backports" 1.44.0 and "trusty-backports" 1.43.9 ?  -- I believe
devs spoke of accepting an SRU (full stable-release-update) for xenial
e2fsprogs, but I suspect backporting in first instance may be a good
approach [?].

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1756438] Re: Merge 0.62.0-2 from Debian

[Hans Joachim Desserud]

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  Merge 0.62.0-2 from Debian

Status in poppler package in Ubuntu:
  New

Bug description:
  Please merge poppler 0.62.0-2 from Debian. It contains packaging
  fixes.

  poppler (0.62.0-2) unstable; urgency=medium

* 01-new-gtk-doc.patch: patch from upstream git, fix FTBFS with new
  gtk-doc-tools. Closes: #887525.
* rules: don't hardcode CXXFLAGS when setting -g, instead append to it
  so that we also get dpkg's buildflags.
* rules: pass CFLAGS down to CMake. This should get x32 the required flags
  from dpkg to build with hardening=pie. This was lost during the switch
  to CMake as it doesn't use CFLAGS directly. Closes: #883881.
* debian/tests/test-qt4.cpp: drop, the qt4 build is gone.
* qt-visibility.diff: drop qt4 hunk.
* control: Switch Vcs to salsa.
* Upload to unstable.

   -- Emilio Pozuelo Monfort   Sun, 04 Mar 2018
  11:37:52 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1756438/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Sebastian Stark]

I should mention that updating libva is not necessary. It is enough to
update the intel-vaapi-driver.

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain 

[Touch-packages] [Bug 1756506] [NEW] snd_hda_intel module rejected by new kernel with retpoline

[Oleg Korobkin]

Public bug reported:

After a routine software update (which updated the kernel) alsa
recognises no sound card although lspci reports an audio device: Audio
device: Intel Corporation 8 Series HD Audio Controller (rev 04).

$ uname -a
Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

$ aplay -l
aplay: device_list:268: no soundcards found...

$ dmesg | grep snd
[4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload 
modversions ' should be '3.13.0-143-generic SMP mod_unload modversions 
retpoline '

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  snd_hda_intel module rejected by new kernel with retpoline

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a routine software update (which updated the kernel) alsa
  recognises no sound card although lspci reports an audio device: Audio
  device: Intel Corporation 8 Series HD Audio Controller (rev 04).

  $ uname -a
  Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

  $ aplay -l
  aplay: device_list:268: no soundcards found...

  $ dmesg | grep snd
  [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload 
modversions ' should be '3.13.0-143-generic SMP mod_unload modversions 
retpoline '

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