[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Jarod]

jarod@ubuntu-pc:~$ ll /etc/resolv.conf 
-rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf

jarod@ubuntu-pc:~$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 114.114.114.114 # this entry is manually add by me
nameserver 127.0.1.1

jarod@ubuntu-pc:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2017-08-28 09:44:24 CST; 1 day 3h ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 3137 (systemd-resolve)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
   └─3137 /lib/systemd/systemd-resolved

Aug 28 09:44:24 ubuntu-pc systemd[1]: Starting Network Name Resolution...
Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Positive Trust Anchors:
Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.i
Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Using system hostname 
'ubuntu-pc'.
Aug 28 09:44:24 ubuntu-pc systemd[1]: Started Network Name Resolution.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1713448] Re: Adobe Reader doesn't print on OKI C911

[Kai-Heng Feng]

I guess it's more CUPS related...

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

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

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

Title:
  Adobe Reader doesn't print on OKI C911

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

Bug description:
  Out and over.
  I tried whatever I could think of, but whatever I send there, anything will 
make the printer blink, 'processing', forever, until I cancel the job. 
  The printer, however, prints the same files from okular, and from all other 
applications that I have tried so far. This would clearly point to acroread. 
  However, acroread prints to all other printers that we have standing about 
without any problem. 

  Logically, from what I could state so far, we have an AND-combination:
  everything works, except I print a file from acroread through OKI
  C911.

  Since I have other printers and other PDF-software, it is minor. And yet, I 
wouldn't mind helping to debug this thing.
  I'm using the OKI-provided ppd with cups. 

  adobereader-enu:i386 9.5.5
  cups 2.1.3-4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1458031] Re: sudo not properly cleaning out timestamp directory

[Bug Watch Updater]

** Changed in: sudo (Debian)
   Status: New => Fix Released

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

Title:
  sudo not properly cleaning out timestamp directory

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Wily:
  Fix Released
Status in sudo package in Debian:
  Fix Released

Bug description:
  Sudo 1.8.10 switched to a new time stamp file format that uses the
  monotonic clock. Timestamp files moved from /var/lib/sudo to
  /var/lib/sudo/ts.

  At boot, the contents of the /var/lib/sudo/ts directory needs to be
  deleted, as per the warning in the build log:

  configure: Warning: the /var/lib/sudo/ts directory must be cleared at boot 
time.
  configure:  You may need to create a startup item to do this.

  The sudo package ships with both an init script and a systemd unit
  file. Unfortunately, the init script sets the date on the timestamp
  files to epoch, which is no longer the proper way to invalidate them.
  The systemd unit file doesn't seem to work at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1458031/+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 1699283] Re: package click 0.4.43+16.04.20160203-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Expired

Bug description:
  An update that failed. Many thanks for your great contributions and
  efforts to improve a great product.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 12:17:04 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-04-01 (445 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1699283/+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 160738] Re: context menu positioned next to mouse pointer when using keyboard in stead of next to keyboard position (nautilus, gnome menus, ...)

[Bug Watch Updater]

** Changed in: gtk
   Status: Confirmed => Invalid

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

Title:
  context menu positioned next to mouse pointer when using keyboard in
  stead of next to keyboard position (nautilus, gnome menus, ...)

Status in GTK+:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  In nautilus the key that invokes the right-click context menu not works fine 
(In Windows works better).
  I like use the keyboard only, not the mouse.
  I put on an item, and if I press the key that invokes the right-click context 
menu, the submenu is where is the mouse, and not of nautilus (As Windows with 
explorer).
  Ubuntu 7.10.
  Greetings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/160738/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Daniel van Vugt]

Yes confirmed the bug is still in 17.10.

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Claude Champagne]

By the way, in Ubuntu 17.10 daily build, and LibreOffice 5.0.4, the bug
still exists. See attachement.

** Attachment added: "lo.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1704745/+attachment/4940498/+files/lo.PNG

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.

[Till Kamppeter]

Fixed in CUPS 2.2.4-4.

** Changed in: cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free:
  Assertion `*_head == _item' failed.

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  This crash just appeared during startup.
  Lots of CUPS updates and errors lately.
   Printer and scanner have worked mostly one way or the other using different 
apps.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: cups-daemon 2.1.0-1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion 
`*_head == _item' failed.
  CrashCounter: 1
  Date: Sat Sep 12 22:57:48 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-01-29 (226 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Brother-DCP-7065DN: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for Brother-DCP-7065DN-2: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for david@david-Lenovo-H535: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for PDF: cups-pdf:/
  MachineType: LENOVO 10117
  Papersize: letter
  PpdFiles:
   david@david-Lenovo-H535: Brother DCP-7065DN, using brlaser v3
   PDF: Generic CUPS-PDF Printer
   Brother-DCP-7065DN-2: Brother DCP-7065DN, using brlaser v3
   Brother-DCP-7065DN: Brother DCP-7065DN, using brlaser v3
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __assert_fail_base (fmt=0x7fed6ded1028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fed6e80d132 "*_head == _item", 
file=file@entry=0x7fed6e80d117 "entrygroup.c", line=line@entry=245, 
function=function@entry=0x7fed6e80d3b0 "avahi_entry_group_free") at assert.c:92
   __GI___assert_fail (assertion=0x7fed6e80d132 "*_head == _item", 
file=0x7fed6e80d117 "entrygroup.c", line=245, function=0x7fed6e80d3b0 
"avahi_entry_group_free") at assert.c:101
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
  Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: 
Assertion `*_head == _item' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT31AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-04-16T18:25:57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1495276/+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 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Till Kamppeter]

Fixed in CUPS 2.2.4-4.

** Changed in: cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] File o directory non esistente: 
'/proc/version_signature'
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: 
org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  Date: Sat Apr  4 11:48:06 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2014-10-23 (167 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat:
   device for Canon-LBP-5975: socket://192.168.1.130
   device for EPSON-Epson-Stylus-Photo-P50: 
usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint 
v5.2.10
   Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fca89173984 : cmpq   
$0x0,(%rdi)
   PC (0x7fca89173984) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  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.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x: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/cups/+bug/1442169/+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 1689803] Re: Driverless printing to EPSON EP-879AW always print with monochrome

[Till Kamppeter]

Fixed in CUPS 2.2.4-4.

** Changed in: cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Driverless printing to EPSON EP-879AW always print with monochrome

Status in cups package in Ubuntu:
  Fix Released
Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  I tried Zesty's driverless printing feature, to print my EPSON EP-879AW 
printer (which supports Apple Airprint).
  Seems well, except any printouts are monochrome.

  1) connect my Zesty machine to my home network via Wi-Fi
  2) connect the printer to my home network via Wi-Fi
  3) use system-config-printer, the print queue connected to the printer is 
automatically added.
  4) print some colored from any applications, like Chromium web browser, 
LibreOffice or else.

  Expected Result:
  - documents printed in color.

  Actual Result:
  - documents printed in monochrome.

  
  NOTE:
  driverlesstest.ppd, generated by following command is attached:

  $ lpadmin -p driverlesstest -E -v ipp://EPSONx.local:631/ipp/print
  -m everywhere

  
  By using FileDevice feature of CUPS, generated CUPS-raster file is already 
monochrome data.
  ---
  $ file /tmp/driverless.prn
  /tmp/driverless.prn: Cups Raster version 2, Big Endian, 360x360 dpi, 
2976x4209 pixels 1 bits/color 1 bits/pixel ColorOrder=Chunky ColorSpace=black
  ---

  I guess that the problem is pdftoraster filter generates monochrome
  data although the generated PPD contains "*ColorDevice: True."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1689803/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Till Kamppeter]

Fixed in CUPS 2.2.4-4.

** Changed in: cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1713205] Re: Slow suspend when wifi active

[Bug Watch Updater]

** Changed in: wpa (Debian)
   Status: Unknown => Fix Released

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  New
Status in wpa package in Debian:
  Fix Released

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1713205/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Claude Champagne]

It's not a feature, it's a bug in some themes. If it was a feature, the
"white square" would somehow appear in themes like Adwaita. But it
doesn't. It would also appear in MacOS or Windows. It doesn't. Please,
get real.  ;-)

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.

[Till Kamppeter]

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

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

Title:
  cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free:
  Assertion `*_head == _item' failed.

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  This crash just appeared during startup.
  Lots of CUPS updates and errors lately.
   Printer and scanner have worked mostly one way or the other using different 
apps.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: cups-daemon 2.1.0-1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion 
`*_head == _item' failed.
  CrashCounter: 1
  Date: Sat Sep 12 22:57:48 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-01-29 (226 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Brother-DCP-7065DN: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for Brother-DCP-7065DN-2: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for david@david-Lenovo-H535: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for PDF: cups-pdf:/
  MachineType: LENOVO 10117
  Papersize: letter
  PpdFiles:
   david@david-Lenovo-H535: Brother DCP-7065DN, using brlaser v3
   PDF: Generic CUPS-PDF Printer
   Brother-DCP-7065DN-2: Brother DCP-7065DN, using brlaser v3
   Brother-DCP-7065DN: Brother DCP-7065DN, using brlaser v3
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __assert_fail_base (fmt=0x7fed6ded1028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fed6e80d132 "*_head == _item", 
file=file@entry=0x7fed6e80d117 "entrygroup.c", line=line@entry=245, 
function=function@entry=0x7fed6e80d3b0 "avahi_entry_group_free") at assert.c:92
   __GI___assert_fail (assertion=0x7fed6e80d132 "*_head == _item", 
file=0x7fed6e80d117 "entrygroup.c", line=245, function=0x7fed6e80d3b0 
"avahi_entry_group_free") at assert.c:101
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
  Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: 
Assertion `*_head == _item' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT31AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-04-16T18:25:57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1495276/+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 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Till Kamppeter]

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

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] File o directory non esistente: 
'/proc/version_signature'
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: 
org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  Date: Sat Apr  4 11:48:06 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2014-10-23 (167 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat:
   device for Canon-LBP-5975: socket://192.168.1.130
   device for EPSON-Epson-Stylus-Photo-P50: 
usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint 
v5.2.10
   Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fca89173984 : cmpq   
$0x0,(%rdi)
   PC (0x7fca89173984) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  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.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x: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/cups/+bug/1442169/+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 1689803] Re: Driverless printing to EPSON EP-879AW always print with monochrome

[Till Kamppeter]

** Changed in: cups (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Driverless printing to EPSON EP-879AW always print with monochrome

Status in cups package in Ubuntu:
  Fix Committed
Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  I tried Zesty's driverless printing feature, to print my EPSON EP-879AW 
printer (which supports Apple Airprint).
  Seems well, except any printouts are monochrome.

  1) connect my Zesty machine to my home network via Wi-Fi
  2) connect the printer to my home network via Wi-Fi
  3) use system-config-printer, the print queue connected to the printer is 
automatically added.
  4) print some colored from any applications, like Chromium web browser, 
LibreOffice or else.

  Expected Result:
  - documents printed in color.

  Actual Result:
  - documents printed in monochrome.

  
  NOTE:
  driverlesstest.ppd, generated by following command is attached:

  $ lpadmin -p driverlesstest -E -v ipp://EPSONx.local:631/ipp/print
  -m everywhere

  
  By using FileDevice feature of CUPS, generated CUPS-raster file is already 
monochrome data.
  ---
  $ file /tmp/driverless.prn
  /tmp/driverless.prn: Cups Raster version 2, Big Endian, 360x360 dpi, 
2976x4209 pixels 1 bits/color 1 bits/pixel ColorOrder=Chunky ColorSpace=black
  ---

  I guess that the problem is pdftoraster filter generates monochrome
  data although the generated PPD contains "*ColorDevice: True."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1689803/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Daniel van Vugt]

I do see the issue in 17.10 still. But to me it looks like a feature, if
not a bug. The "white square" ties the close button to the document
area. So it looks intentional and logical. Maybe it's not intentional,
but either way not a big problem.

** Changed in: ubuntu-themes
   Importance: Medium => Low

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Medium => Low

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Till Kamppeter]

** Changed in: cups (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Fix Committed
Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1671159] Re: wget crashed with SIGSEGV

[Henning Meyer]

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

** This bug has been marked a duplicate of bug 1573307
   wget crashed with SIGSEGV in __memset_avx2()

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

Title:
  wget crashed with SIGSEGV

Status in wget package in Ubuntu:
  New

Bug description:
  wget crashed when I try to download one iso. a tried 2 different
  computer the status is the same.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar  8 17:05:38 2017
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2015-08-17 (569 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: wget 
http://mirror.infotronik.hu/mirrors/linuxmint/iso/stable/18.1/linuxmint-18.1-mate-64bit.iso
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f80d3dde720 <__memset_sse2+144>:movdqa 
%xmm0,(%rcx)
   PC (0x7f80d3dde720) ok
   source "%xmm0" ok
   destination "(%rcx)" (0x561bd7d3) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2016-05-03 (308 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1671159/+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 1713595] [NEW] gdebi-kde crash on app startup

[Arlen B Taylor]

Public bug reported:

Here is the back trace information:

Application: GDebi (gdebi-kde), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x in  ()
#7  0x7f018591ea3a in sip_api_get_cpp_ptr () at 
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#8  0x7f0185924b20 in  () at 
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#9  0x7f0185926a70 in  () at 
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#10 0x7f0185927293 in  () at 
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#11 0x7f0185927500 in  () at 
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#12 0x7f0184ceb7fa in  () at 
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-35m-x86_64-linux-gnu.so
#13 0x5567a18d828f in PyCFunction_Call (func=, args=, 
kwds=) at ../Objects/methodobject.c:109
#14 0x5567a188f1e9 in call_function (oparg=, 
pp_stack=0x7fffe5613070) at ../Python/ceval.c:4720
#15 0x5567a188f1e9 in PyEval_EvalFrameEx (f=Frame 0x5567a3f15e48, for file 
/usr/share/gdebi/GDebi/GDebiKDE.py, line 149, in __init__ 
(self=, 
'file': '', 'datadir': '/usr/share/gdebi'}) at ../Objects/typeobject.c:905
#24 0x5567a1916887 in PyObject_Call (func=, arg=, kw=) at 
../Objects/abstract.c:2166
#25 0x5567a188f961 in do_call (nk=, na=0, 
pp_stack=0x7fffe5613440, func=) at ../Python/ceval.c:4951
#26 0x5567a188f961 in call_function (oparg=, 
pp_stack=0x7fffe5613440) at ../Python/ceval.c:4747
#27 0x5567a188f961 in PyEval_EvalFrameEx (f=Frame 0x5567a37765c8, for file 
/usr/bin/gdebi-kde, line 87, in  (), throwflag=0) at 
../Python/ceval.c:3251
#28 0x5567a1893d16 in _PyEval_EvalCodeWithName (_co=, globals=, locals=, 
args=, argcount=, kws=0x0, kwcount=0, defs=0x0, 
defcount=0, kwdefs=0x0, closure=0x0, name=0x0, qualname=0x0) at 
../Python/ceval.c:4033
#29 0x5567a1894a1f in PyEval_EvalCodeEx () at ../Python/ceval.c:4054
#30 0x5567a1894a1f in PyEval_EvalCode (co=, 
globals=, locals=) at ../Python/ceval.c:777
#31 0x5567a1961b02 in run_mod (mod=, filename=, globals={'KCmdLineArgs': , 'description': , 
'OptionParsed': , '__name__': '__main__', 
'options': , 'sys': 
, 'KAboutData': , '__cached__': None, '__loader__': 
, 'ki18n': , 'afile': '', 'KMessageBox': , 'parser': 

[Touch-packages] [Bug 1713205] Re: Slow suspend when wifi active

[Brian Murray]

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

** Also affects: wpa (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835648
   Importance: Unknown
   Status: Unknown

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  New
Status in wpa package in Debian:
  Unknown

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1713205/+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 1713017] Re: Enable MIDI support

[wvengen]

For those seeking a workaround, see instructions here:
https://gist.github.com/wvengen/7ebd29da38c08540832fb228c4628171#bluez-546

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

Title:
  Enable MIDI support

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
  enable Bluetooth MIDI support. This did not seem to be enabled by
  default in the build from
  https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
  MIDI devices, gatttool could talk to them, but no MIDI device was
  made; also ldd showed no linkage to libasound.so.2).

  After recompiling it with libasound2-dev installed and --enable-midi
  in debian/rules, it worked.

  Suggestion: add libasound2-dev to bluez dependencies, add --enable-
  midi to rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+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 1713248] Re: pubkey auth hangs on high latency networks

[Seth Arnold]

You could use tc(8) to add predictable latency for testing
http://bencane.com/2012/07/16/tc-adding-simulated-network-latency-to-
your-linux-server/

Thanks

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

Title:
  pubkey auth hangs on high latency networks

Status in openssh package in Ubuntu:
  New

Bug description:
  This is a weird one. I use a small fleet of laptops to do professional
  network testing, and I wrote some tools that use SSH with pubkey auth
  to run simultaneous tests.

  The problem is, if the wifi connection isn't superb, the auth times
  out more often than not. For example, if I've got a long range 5 GHz
  connection which returns 100% of pings but has a median latency of
  100ms or so, auth hangs after send packet: type 50, never receiving
  the packet type 51 to complete the auth.

  debug2: key: /root/.ssh/id_ecdsa ((nil))
  debug2: key: /root/.ssh/id_ed25519 ((nil))
  debug3: send packet: type 5
  debug3: receive packet: type 6
  debug2: service_accept: ssh-userauth
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug3: send packet: type 50

  This is where it hangs; after approximately a 30 second timeout
  (haven't clocked it precisely) it falls through to any remaining
  available authentication methods - other keys, hostbased, password,
  whatever hasn't been explicitly disabled.

  Yes, UseDNS no is on, on both client and sender. I've also disabled
  all non-essential PAM modules, and disabled HostBasedAuth, RSAAuth,
  and GSSAPI on both client and sender.

  The same two laptops in the same location will complete password
  authentication without a problem - if a pubkey is present for the user
  on the client side, it'll have to time that out first before it fails
  through and asks for the password (which will be promptly accepted and
  work normally); but if there is no pubkey for the client user, it'll
  prompt for the password and accept it immediately.

  If I move the server laptop closer to the router, so that the median
  latency falls in something more like the 50ms range, the pubkey auth
  works fine. I want to reiterate here that we're talking about high
  latency, but we're *not* talking about dropped packets - pings between
  the laptops when they're having problems range from 100ms-900ms
  latency, but with 100% returns. (And, again, password auth works fine,
  it's only pubkey that has the issue - and only when latency is high.)

  I can't find anything on the internets referring to a problem with
  high latency pubkey authentication on machines where pubkey auth works
  fine with lower latency, but here I am.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 26 12:04:22 2017
  InstallationDate: Installed on 2016-11-05 (293 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713248/+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 1712675] Re: tzdata-2017b is not in any new LTS Ubuntu releases

[Brian Murray]

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  tzdata-2017b is not in any new LTS Ubuntu releases

Status in tzdata package in Ubuntu:
  New

Bug description:
  tzdata-2017b has been released since March 2017. There has been no new
  tzdata releases on LTS versions. I'm filing this as a bug since time
  is pretty critical. Requesting to add this package to the next
  release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1712675/+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 1713149] Re: resolv.conf symlink is broken after clean debootstrap

[Steve Langasek]

This may have been fixed just now by demoting resolvconf from important
to extra.  If the next image build is still broken after this change,
please shout.

Ideally the debootstrap would have worked at all points without archive
override changes, but having missed that, we should just get resolvconf
out of the way.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

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

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713149/+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 1650666] Re: GVim crashes when opening new tab

[Nish Aravamudan]

** Description changed:

+ [Impact]
+ 
+ A severe regression has been found in the GTK 3 variant of Gvim.
+ Upon start-up, it crashes immediately with multiple failed
+ assertions.
+ 
+ A second related, but less severe problem may occur when opening
+ new tabs within the GTK 3 variant of Gvim.
+ 
+ [Test Case]
+ 
+ Please note that in the following test cases, a given machine may
+ experience either of the test cases, while being unable to
+ experience the other test case. Please do /not/ discount
+ the merits of this SRU on being able to only confirm a single
+ test case, but not both.
+ 
+ This patch equally corrects both test cases listed below, to
+ produce a working GTK 3 Gvim variant.
+ 
+ IMPORTANT: Both test cases below require the package "vim-gtk3"
+ to be installed, prior to testing for either test case's
+ impact to one's machine.
+ 
+ [[TEST CASE #1]]
+ 
+ 1. From a terminal window, launch the GTK 3 variant of Gvim:
+ 
+   $ vim.gtk3
+ 
+ 2. Immediately upon launch (whereby the window may or may
+not briefly display); the terminal window will show error
+messages relating to `unity_gtk_menu_*` critical
+assertions.
+ 
+A full example of the experienced error output shown is:
+ 
+ ```
+ (gvim:13519): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= 
(gint)rarray->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_label: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ```
+ 
+ [[TEST CASE #2]]
+ 
+ 1. From a terminal window, launch the GTK 3 variant of Gvim:
+ 
+   $ vim.gtk3
+ 
+ 2. Upon the window opening, attempt to open a new tab by entering
+the key sequences ":tabnew" and pressing . The
+program should now SEGV and abort.
+ 
+ [Regression Potential]
+ 
+ * The bug is possibly applicable to all later Ubuntu releases,
+   which combine Unity and GTK 3.
+ 
+ * The upstream Vim project has not incorporated the fix, and
+   most likely will not. The specifics behind the fix might
+   be construed as too specific to the combination of Ubuntu,
+   Unity, and GTK 3; and not general enough to patch for all
+   downstream distributions.
+ 
+ [Other Info]
+ 
+ * Further information about this bug is available at the URLs:
+   https://github.com/vim/vim/issues/851
+   https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1650666
+ 
+ ---
+ 
  When I open new tab using :tabnew command, GVim crashes in
  unity_gtk_menu_section_get_item_attributes function of libunity-
  gtk3-parser0 package.
- 
  
  Steps to reproduce:
  1. Run gvim from vim-gtk3 package
  2. Type `:tabnew`
  3. GVim exits, the window closes
- 
  
  Stack trace obtained via gdb:
  
  mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null 
--noplugin
  Reading symbols from gvim...(no debugging symbols found)...done.
  gdb$ run
  Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe986d700 (LWP 11042)]
  [New Thread 0x7fffe906c700 (LWP 11043)]
  [New Thread 0x7fffe886b700 (LWP 11044)]
  
  (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <=
  (gint)rarray->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell:
  assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  Thread 1 "gvim" received signal SIGSEGV, Segmentation fault.
- unity_gtk_menu_section_get_item_attributes (model=, 
item_index=, 
- attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
+ unity_gtk_menu_section_get_item_attributes (model=, 
item_index=,
+ attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
  130   ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога.
- gdb$ backtrace 
+ gdb$ backtrace
  #0  0x7fffe9a82083 in unity_gtk_menu_section_get_item_attributes 
(model=, item_index=, attributes=0x7fff8b90) 
at ../../../lib/unity-gtk-menu-section.c:130
  #1  0x7653f23c in 

[Touch-packages] [Bug 1713578] [NEW] Migrate /etc/resolv.conf from resolvconf to systemd-resolved

[Mathieu Trudel-Lapierre]

Public bug reported:

Moving off of resolvconf and to systemd-resolved requires that
resolv.conf is properly handled both in the case of new installs (done
as per 234-2ubuntu9 at least), but also in the case of upgrades from
previous releases or previous versions of systemd.

There are various use cases to take into account:

1) upgrades where resolv.conf is more or less default and dynamic, uses
DHCP via ifupdown (servers), or 127.0.1.1/DHCP settings from
NetworkManager (desktops), etc.

2) upgrades from manual resolv.conf settings (the user has written their
own, it's static)

3) upgrades from manual resolv.conf managed via resolvconf.

3) No resolv.conf?

Lack of resolv.conf is simple, writing one is always sane.

Upgrades from dynamic files is also straightforward, copying it to
/run/systemd/resolve/resolv.conf will keep the current state;
/etc/resolv.conf will be symlinked to that.

In the case of a manually-configured resolv.conf; whether it comes from
resolvconf or is manually configured is non-trivial if we want to
maintain the current DNS configuration and also remove resolvconf. The
removal of resolvconf can be forced, but what do we do about the
existing /etc/resolv.conf file, knowing that /run is a tmpfs?

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

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

Title:
  Migrate /etc/resolv.conf from resolvconf to systemd-resolved

Status in systemd package in Ubuntu:
  New

Bug description:
  Moving off of resolvconf and to systemd-resolved requires that
  resolv.conf is properly handled both in the case of new installs (done
  as per 234-2ubuntu9 at least), but also in the case of upgrades from
  previous releases or previous versions of systemd.

  There are various use cases to take into account:

  1) upgrades where resolv.conf is more or less default and dynamic,
  uses DHCP via ifupdown (servers), or 127.0.1.1/DHCP settings from
  NetworkManager (desktops), etc.

  2) upgrades from manual resolv.conf settings (the user has written
  their own, it's static)

  3) upgrades from manual resolv.conf managed via resolvconf.

  3) No resolv.conf?

  Lack of resolv.conf is simple, writing one is always sane.

  Upgrades from dynamic files is also straightforward, copying it to
  /run/systemd/resolve/resolv.conf will keep the current state;
  /etc/resolv.conf will be symlinked to that.

  In the case of a manually-configured resolv.conf; whether it comes
  from resolvconf or is manually configured is non-trivial if we want to
  maintain the current DNS configuration and also remove resolvconf. The
  removal of resolvconf can be forced, but what do we do about the
  existing /etc/resolv.conf file, knowing that /run is a tmpfs?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713578/+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 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

[Steve Langasek]

Has this still been an issue since resolvconf and ifupdown were re-
promoted to Priority: important?

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

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

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit 
status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

* Always setup /etc/resolv.conf on new installations.
  On new installations, /etc/resolv.conf will always exist. Move it to /run
  and replace it with the desired final symlink. (LP: #1712283)
* Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713212/+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 1478659] Re: aa-genprof start but doesn't allow any action

[Christian Boltz]

I'm afraid the given information isn't enough to reproduce and debug
this problem :-(

If you hit this again, please reopen and provide some more details.

** Changed in: apparmor
   Status: New => Invalid

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

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

Title:
  aa-genprof start but doesn't allow any action

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid

Bug description:
  Package version: 2.8.95~2430-0u
  Ubuntu version: 14.04.2 LTS 64 bit server
  Kernel version: 3.16.0-39

  I tried to generate a profile for one of the tools in quagga:
  /usr/lib/quagga/bgp.

  I did the following:
  aa-autodep /usr/lib/quagga/bgp
  aa-genprof /usr/lib/quagga/bgp

  Genprof show the screen explaining you have to play with the app and
  to Scan at the end. However, it doesn't display those actions and
  stops at the paragraph "For each AppArmor event, you be given the
  opportunity to choose whether the access should be allowed or denied."

  There is no option whatsoever. Even pressing 's' then hitting Enter
  doesn't do anything. Or even just hitting Enter doesn't do anything.

  Note: I have installed auditd install because of 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1432350 and I can see 
events in the audit log from the program I'm monitoring
  Note 2: Apparmor (profile generation part) is also pretty much unusable on 
15.04 (different issues I think).

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1478659/+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 1713536] Re: udev: boot script does not trigger subsystem coldplug

[Steve Langasek]

** Package changed: initramfs-tools-ubuntu-touch (Ubuntu) => systemd
(Ubuntu)

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in systemd package in Ubuntu:
  New

Bug description:
  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713536/+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 1713565] [NEW] package libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Augusto Fontes]

Public bug reported:

this bug is not cool

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Aug 23 22:40:20 2017
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2017-06-21 (68 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qt4-x11
Title: package libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1713565

Title:
  package libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  this bug is not cool

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug 23 22:40:20 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-06-21 (68 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qt4-x11
  Title: package libqtgui4:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1713565/+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 1713566] [NEW] package libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Augusto Fontes]

Public bug reported:

need help

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Aug 23 22:40:24 2017
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2017-06-21 (68 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qt4-x11
Title: package libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1713566

Title:
  package libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  need help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug 23 22:40:24 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-06-21 (68 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qt4-x11
  Title: package libqt4-declarative:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1713566/+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 1713564] LightdmDisplayLog.txt

[Kent Lion]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940359/+files/LightdmDisplayLog.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713564/+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 1713564] Re: Repeated problem on login with damaged problem report.

[Kent Lion]

Running apport-collect -p xorg 1713564 appears to have been successful.

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940360/+files/LightdmLog.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940358/+files/JournalErrors.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940355/+files/CurrentDmesg.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

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

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

[Kent Lion]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940354/+files/BootLog.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713564/+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 1713564] [NEW] Repeated problem on login with damaged problem report.

[Kent Lion]

Public bug reported:

Sometimes every time I log in to Xubuntu 16.04, sometimes every other
time, the first thing I get are 2 dialogs saying there has been a
problem and 2 requests for permission to submit a problem report. I
always give permission, and after I do, everything seems to work fine.
Every time I've ever looked at the details, I find something that says
the problem report is damaged and cannot be processed, and refers to an
invalid core dump with a warning referencing /tmp/apport_core. This has
been going on for over a year, but doesn't seem to be a common problem,
since I find only 2 similar bug references. Bugs #1424864 and #1507461
appear to be giving a similar but not identical error message, and the
symptoms of neither match mine.

Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
--- 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
InstallationDate: Installed on 2016-07-02 (422 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. OptiPlex GX620
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Tags:  xenial ubuntu
Uname: Linux 4.4.0-93-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0PY423
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex GX620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: apport-collected ubuntu xenial

** Tags added: apport-collected ubuntu xenial

** Description changed:

  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to an
  invalid core dump with a warning referencing /tmp/apport_core. This has
  been going on for over a year, but doesn't seem to be a common problem,
  since I find only 2 similar bug references. Bugs #1424864 and #1507461
  appear to be giving a similar but not identical error message, and the
  symptoms of neither match mine.
  
- Using instructions from bug #1424864, I tried apport-collect -p xorg
- 1424864, and was told to open another bug report.
+ Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: ubuntu
+ DkmsStatus:
+  virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
+  virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 

[Touch-packages] [Bug 1713560] [NEW] Lenovo Ideapad 320 touchpad not detected

[ariel]

Public bug reported:

Ubuntu 17.04

xserver-xorg-input-synaptics:
  Installed: 1.9.0-1ubuntu1
  Candidate: 1.9.0-1ubuntu1
  Version table:
 *** 1.9.0-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

I get no response from touchpad. External mouse working.

Touchpad not detected in /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7
U: Uniq=
H: Handlers=rfkill kbd event5 
B: PROP=0
B: EV=13
B: KEY=101400800100c03 430 0 2
B: MSC=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event6 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event7 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=0bda Product=58ea Version=0008
N: Name="EasyCamera"
P: Phys=usb-:00:14.0-8/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input13
U: Uniq=
H: Handlers=kbd event11 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0005 Vendor=046d Product=b012 Version=0014
N: Name="MX Master"
P: Phys=C8:3D:D4:F8:3E:78
S: Sysfs=/devices/virtual/misc/uhid/0005:046D:B012.0001/input/input14
U: Uniq=CB:2B:20:FA:A0:6B
H: Handlers=sysrq kbd mouse0 event12 
B: PROP=0
B: EV=100017
B: KEY= 10007 ff8007ff febeffdfffef fffe
B: REL=143
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Aug 28 21:57:00 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 elantech-0608, 0.2, 4.10.0-33-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
 rtl8812au, 4.3.8.12175.20140902+dfsg, 4.10.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 520 [17aa:39c5]
InstallationDate: Installed on 2017-08-28 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80XG
ProcEnviron:
 LANGUAGE=en_IL:en
 TERM=xterm-256color
 PATH=(custom, no user)
 

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Carlo Lobrano]

I cannot reproduce the issue anymore with LibreOffice 5.4

** Attachment added: "Pic of the button fixed in LibreOffice"
   
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+attachment/4940289/+files/libreoffice-close-button-fixed-in-5.4.png

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1712701] Re: Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

[Bug Watch Updater]

** Changed in: gtk+3.0 (Debian)
   Status: New => Confirmed

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

Title:
  Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  This bug affects gtk3 >= 3.22.18.1.

  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.

  Note that this bug has already been reported in Arch and Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1712701/+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 1713536] [NEW] udev: boot script does not trigger subsystem coldplug

[bugproxy]

Public bug reported:

The udev initramfs-tools boot script does not trigger subsystem "add"
uevents. As a result, udev rules that listen to subsystem "add" events
are never activated. This problem exists on at least Ubuntu 16.04 and
17.10.

On s390, this results in a boot failure if the kernel is configured to
start with an active device black list (kernel parameter
cio_ignore=all,!condev). An example for an affected udev rule looks like
this:

ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
/proc/cio_ignore'"

A proposed fix would be:

Modify /usr/share/initramfs-tools/scripts/init-top/udev:

Replace line
udevadm trigger --action=add
with
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add

This would also be consistent with the steps that the systemd udev
coldplug unit file performs (see /lib/systemd/system/systemd-udev-
trigger.service).

** Affects: initramfs-tools-ubuntu-touch (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-158070 severity-medium 
targetmilestone-inin1604

** Tags added: architecture-s39064 bugnameltc-158070 severity-medium
targetmilestone-inin1604

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => initramfs-tools-ubuntu-touch (Ubuntu)

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  New

Bug description:
  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1713536/+subscriptions

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

Re: [Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

On Mon, Aug 28, 2017 at 01:47:23AM -, Jarod wrote:
> update to systemd (234-2ubuntu9) doesn't help, after reboot I still need
> manually add nameserver to /etc/resolve.conf

After your update, is /etc/resolv.conf a symlink to
/run/systemd/resolve/stub-resolv.conf ?

Please show the output of 'systemctl status systemd-resolved'.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1713536] [NEW] udev: boot script does not trigger subsystem coldplug

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The udev initramfs-tools boot script does not trigger subsystem "add"
uevents. As a result, udev rules that listen to subsystem "add" events
are never activated. This problem exists on at least Ubuntu 16.04 and
17.10.

On s390, this results in a boot failure if the kernel is configured to
start with an active device black list (kernel parameter
cio_ignore=all,!condev). An example for an affected udev rule looks like
this:

ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
/proc/cio_ignore'"

A proposed fix would be:

Modify /usr/share/initramfs-tools/scripts/init-top/udev:

Replace line
udevadm trigger --action=add
with
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add

This would also be consistent with the steps that the systemd udev
coldplug unit file performs (see /lib/systemd/system/systemd-udev-
trigger.service).

** Affects: initramfs-tools-ubuntu-touch (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-158070 severity-medium 
targetmilestone-inin1604
-- 
udev: boot script does not trigger subsystem coldplug
https://bugs.launchpad.net/bugs/1713536
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools-ubuntu-touch in Ubuntu.

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

[Touch-packages] [Bug 997200] Re: Add NetworkManager connectivity config package

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.8.2-1ubuntu5

---
network-manager (1.8.2-1ubuntu5) artful; urgency=medium

  * Add connectivity-allow-override.patch:
- Cherry-pick patch to fix using D-Bus to override connectivity check
  disabling in /etc/ . See GNOME bug 786890 for more details.

 -- Jeremy Bicha   Mon, 28 Aug 2017 09:23:01 -0400

** Changed in: network-manager (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Add NetworkManager connectivity config package

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in ubuntu-meta source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Confirmed
Status in network-manager package in Debian:
  Fix Released

Bug description:
  How to Disable This Feature
  ===
  Option 1
  
  If you are using the default Ubuntu or GNOME, open the Settings app, browse 
to Privacy and turn off Network Connectivity Checking.

  Option 2
  
  You could also disable it by adding a file to /etc/NetworkManager/conf.d/
  with this content:
  [connectivity]
  enabled=false

  Then restart NetworkManager or your computer, whichever is easier.

  Feature
  ===
  A separate network-manager-config-connectivity-ubuntu package that contains 
the 2-line config snippet to enable NetworkManager's connectivity check. This 
is the same approach taken by Fedora since 2014 (their package is named 
network-manager-config-connectivity-fedora).

  With this config, GNOME Shell will pop up a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals

  This new feature (and how to opt out) will be mentioned in Ubuntu
  17.10's Release Notes.

  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html

  Link to newer discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

  Original Bug Report
  ==
  When in a hotel there is a often a T page that is delivered when 
connecting to the network.  Some combination of network manager and update 
manager (or something else entirely) doesn't seem to be able to handle this, 
and update are left in a non-working state after not being able to read package 
headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/997200/+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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades

[Launchpad Bug Tracker]

This bug was fixed in the package shim-signed - 1.32~14.04.2

---
shim-signed (1.32~14.04.2) trusty; urgency=medium

  * Backport shim-signed 1.32 to 14.04. (LP: #1700170)

shim-signed (1.32) artful; urgency=medium

  * Handle cleanup of /var/lib/shim-signed on package purge.

shim-signed (1.31) artful; urgency=medium

  * Fix regression in postinst when /var/lib/dkms does not exist.
(LP #1700195)
  * Sort the list of dkms modules when recording.

shim-signed (1.30) artful; urgency=medium

  * update-secureboot-policy: track the installed DKMS modules so we can skip
failing unattended upgrades if they hasn't changed (ie. if no new DKMS
modules have been installed, just honour the user's previous decision to
not disable shim validation). (LP: #1695578)
  * update-secureboot-policy: allow re-enabling shim validation when no DKMS
packages are installed. (LP: #1673904)
  * debian/source_shim-signed.py: add the textual representation of SecureBoot
and MokSBStateRT EFI variables rather than just adding the files directly;
also, make sure we include the relevant EFI bits from kernel log.
(LP: #1680279)

shim-signed (1.29) artful; urgency=medium

  * Makefile: Generate BOOT$arch.CSV, for use with fallback.
  * debian/rules: make sure we can do per-arch EFI files.

shim-signed (1.28) zesty; urgency=medium

  * Adjust apport hook to include key files that tell us about the system's
current SB state.  LP: #1680279.

shim-signed (1.27) zesty; urgency=medium

  [ Steve Langasek ]
  * Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 binary from
Microsoft.
  * update-secureboot-policy:
- detect when we have no debconf prompting and error out instead of ending
  up in an infinite loop.  LP: #1673817.
- refactor to make the code easier to follow.
- remove a confusing boolean that would always re-prompt on a request to
  --enable, but not on a request to --disable.

  [ Mathieu Trudel-Lapierre ]
  * update-secureboot-policy:
- some more fixes to properly handle non-interactive mode. (LP: #1673817)

shim-signed (1.23) zesty; urgency=medium

  * debian/control: bump the Depends on grub2-common since that's needed to
install with the new updated EFI binaries filenames.

shim-signed (1.22) yakkety; urgency=medium

  * Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 binary from Microsoft.
  * Update paths now that the shim binary has been renamed to include the
target architecture.
  * debian/shim-signed.postinst: clean up old MokManager.efi from EFI/ubuntu;
since it's being replaced by mm$arch.efi.

shim-signed (1.21.3) vivid; urgency=medium

  * No-change rebuild for shim 0.9+1465500757.14a5905.is.0.8-0ubuntu3.

shim-signed (1.21.2) vivid; urgency=medium

  * Revert to signed shim from 0.8-0ubuntu2.
- shim.efi.signed originally built from shim 0.8-0ubuntu2 in wily.

shim-signed (1.20) yakkety; urgency=medium

  * Update to the signed 0.9+1465500757.14a5905-0ubuntu1 binary from Microsoft.
(LP: #1581299)

 -- Mathieu Trudel-Lapierre   Mon, 10 Jul 2017
20:29:28 -0400

** Changed in: shim-signed (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  update-secure-boot-policy behaving badly with unattended-upgrades

Status in shim-signed package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in shim-signed source package in Trusty:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Invalid
Status in shim-signed source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Invalid
Status in shim-signed source package in Yakkety:
  Fix Released
Status in unattended-upgrades source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  Any user with unattended upgrades enabled and DKMS packages in a Secure Boot 
environment might be prompted to change Secure Boot policy, which will fail and 
crash in unattended-upgrades.

  [Test case]
  = unattended upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) Install new package
  3) Trigger unattended-upgrades: unattended-upgrades -d

  Upgrade should run smoothly for all the processing but fail to
  complete; shim-signed should end the unattended upgrade with a error
  as unattended change of the Secure Boot policy can not be done.
  Upgrade should not hang in high CPU usage.

  = standard upgrade =
  1) Create /var/lib/dkms/TEST-DKMS
  2) install new package.
  3) Verify that the upgrade completes normally. 

  
  [Regression Potential]
  Any failure to prompt for or change Secure Boot policy in mokutil while in an 
*attended* upgrade scenario would constitute a regression of this SRU.

  Any other issues related to booting in Secure Boot mode should 

[Touch-packages] [Bug 1657897] Re: Failure to report rhosts

[Bug Watch Updater]

** Changed in: cyrus-sasl2
   Status: Unknown => New

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

Title:
  Failure to report rhosts

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1657897/+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 1713189] Re: Got stop job running c1 session

[Tyler Hicks]

** Information type changed from Private Security to Public

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

Title:
  Got stop job running c1 session

Status in xorg package in Ubuntu:
  New

Bug description:
  Got stop job running c1 session, takes long time to shutdown the pc

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 25 20:02:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8079]
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=bfd4a0da-f910-4231-82fd-4627708c9adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713189/+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 1657897] Re: Failure to report rhosts

[Andreas Hasenack]

I think we should defer to upstream on this one.

** Changed in: cyrus-sasl2 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: cyrus-sasl2 (Ubuntu)
   Importance: Critical => Wishlist

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Failure to report rhosts

Status in Cyrus-sasl2:
  Unknown
Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1657897/+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 1657897] Re: Failure to report rhosts

[Andreas Hasenack]

Is this log line enough for fail2ban purposes?

Jan 25 16:56:13 uvt-yakkety postfix/smtpd[3313]: warning:
unknown[192.168.122.1]: SASL login authentication failed: authentication
failure

You have:
- the service (smtpd)
- the ip (192.168.122.1)
- the failure reason ("authentication failure")

** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #346
   https://github.com/cyrusimap/cyrus-sasl/issues/346

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

Title:
  Failure to report rhosts

Status in Cyrus-sasl2:
  Unknown
Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1657897/+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 1657897] Re: Failure to report rhosts

[Andreas Hasenack]

Upstream issue: https://github.com/cyrusimap/cyrus-sasl/issues/346

** Also affects: cyrus-sasl2 via
   https://github.com/cyrusimap/cyrus-sasl/issues/346
   Importance: Unknown
   Status: Unknown

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

Title:
  Failure to report rhosts

Status in Cyrus-sasl2:
  Unknown
Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1657897/+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 1713513] [NEW] notification for extensions keep reapearing

[rafa el]

Public bug reported:

after installing lightdm and login in the guest session, all extensions
with notifications restart a few times (at least two, most I've seen is
6) this only started happening after logging off and on again in the
guest session. I couldn't find a way to solve this other then turning of
the notifications of those extensions, I tested and even the standard
extensions that come with Ubuntu Gnome 16.04 show the same issue

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

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

Title:
  notification for extensions keep reapearing

Status in lightdm package in Ubuntu:
  New

Bug description:
  after installing lightdm and login in the guest session, all
  extensions with notifications restart a few times (at least two, most
  I've seen is 6) this only started happening after logging off and on
  again in the guest session. I couldn't find a way to solve this other
  then turning of the notifications of those extensions, I tested and
  even the standard extensions that come with Ubuntu Gnome 16.04 show
  the same issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1713513/+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 537190] Re: gnumeric crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Bug Watch Updater]

** Changed in: gtk
   Status: New => Expired

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

Title:
  gnumeric crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Status in GTK+:
  Expired
Status in gnumeric package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnumeric

  $ lsb_release -rd
  Description:  Ubuntu lucid (development branch)
  Release:  10.04

  
  $ apt-cache policy  gnumeric
  gnumeric:
Installed: 1.10.0-1ubuntu1
Candidate: 1.10.0-1ubuntu1
Version table:
   *** 1.10.0-1ubuntu1 0
  500 http://us.archive.ubuntu.com lucid/universe Packages
  100 /var/lib/dpkg/status


  
  I was using gnumeric and didn't expect it to crash.

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Thu Mar 11 00:46:23 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/gnumeric
  Package: gnumeric 1.10.0-1ubuntu1
  ProcCmdline: gnumeric
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
  ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
  SegvAnalysis:
   Segfault happened at: 0x488a7a:  fldl   0x18(%ecx)
   PC (0x00488a7a) ok
   source "0x18(%ecx)" (0x0018) not located in a known VMA region (needed 
readable region)!
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnumeric
  StacktraceTop:
   ?? () from /usr/lib/libspreadsheet-1.10.0.so
   ?? () from /usr/lib/libspreadsheet-1.10.0.so
   _gtk_marshal_BOOLEAN__BOXED (closure=0x8128410, 
   g_type_class_meta_marshal (closure=0x8128410, 
   IA__g_closure_invoke (closure=0x8128410,
  Title: gnumeric crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
  Uname: Linux 2.6.32-15-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/537190/+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 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory

[Jeff Larson]

I just checked and this issue persists in python3.6.2.

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

Title:
  sysconfig.get_path('purelib') points to site-packages directory

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Confirmed

Bug description:
  purelib and platlib paths in Python 3 sysconfig module point to site-
  packages directory:

  $ python3 -m sysconfig

  Platform: "linux-x86_64"
  Python version: "3.4"
  Current installation scheme: "posix_prefix"

  Paths: 
data = "/usr"
include = "/usr/include/python3.4m"
platinclude = "/usr/include/python3.4m"
platlib = "/usr/lib/python3.4/site-packages"
platstdlib = "/usr/lib/python3.4"
purelib = "/usr/lib/python3.4/site-packages"
scripts = "/usr/bin"
stdlib = "/usr/lib/python3.4"
  ...

  whereas Python 2 points to dist-packages:

  Platform: "linux-x86_64"
  Python version: "2.7"
  Current installation scheme: "posix_local"

  Paths: 
data = "/usr/local"
include = "/usr/local/include/python2.7"
platinclude = "/usr/local/include/python2.7"
platlib = "/usr/local/lib/python2.7/dist-packages"
platstdlib = "/usr/lib/python2.7"
purelib = "/usr/local/lib/python2.7/dist-packages"
scripts = "/usr/local/bin"
stdlib = "/usr/lib/python2.7"
  ...

  One severe consequence of this is that automake is installing Python
  modules to a location which is not in sys.path, namely site-packages
  directory.

  When one uses automake to create a Makefile that installs a Python
  module to the system, it is installed into /usr/local/lib/python3.4
  /site-packages since automake/aclocal uses sysconfig to determine
  where the package will be installed.

  From /usr/share/aclocal-1.14/python.m4 file:

AC_CACHE_CHECK([for $am_display_PYTHON script directory],
  [am_cv_python_pythondir],
  [if test "x$prefix" = xNONE
   then
 am_py_prefix=$ac_default_prefix
   else
 am_py_prefix=$prefix
   fi
   am_cv_python_pythondir=`$PYTHON -c "
  $am_python_setup_sysconfig
  if can_use_sysconfig:
  sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
  <---
  else:
  from distutils import sysconfig
  ...

  Here, it can be seen that automake uses purelib path defined by the
  sysconfig module of Python. However, since this path is not included
  in sys.path, and thus the installed package cannot be used:

  $ python3 -c "import sys; print(sys.path)"
  ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', 
'/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', 
'/usr/lib/python3/dist-packages']

  
  Ubuntu version:14.10

  $ apt-cache policy python3-minimal 
  python3-minimal:
Installed: 3.4.2-1
Candidate: 3.4.2-1
Version table:
   *** 3.4.2-1 0
  500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092/+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 1713508] [NEW] package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Mary]

Public bug reported:

El sistema puso el aviso

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports:
 640:0:116:142134:2017-08-28 11:02:42.357357740 -0300:2017-08-28 
11:02:45.133304945 -0300:/var/crash/apport.0.crash
 644:0:116:0:2017-08-28 11:02:45.133304945 -0300:2017-08-28 11:02:45.133304945 
-0300:/var/crash/apport.0.upload
 600:109:116:0:2017-08-28 11:02:48.793189539 -0300:2017-08-28 
11:02:48.793189539 -0300:/var/crash/apport.0.uploaded
 600:0:116:127426:2017-08-28 11:01:20.158540487 -0300:2017-08-28 
11:02:59.644799651 -0300:/var/crash/apport-gtk.0.crash
Date: Mon Aug 28 11:01:21 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2015-08-11 (747 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: apport
Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to xenial on 2016-08-08 (385 days ago)

** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1713508

Title:
  package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in apport package in Ubuntu:
  New

Bug description:
  El sistema puso el aviso

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   640:0:116:142134:2017-08-28 11:02:42.357357740 -0300:2017-08-28 
11:02:45.133304945 -0300:/var/crash/apport.0.crash
   644:0:116:0:2017-08-28 11:02:45.133304945 -0300:2017-08-28 
11:02:45.133304945 -0300:/var/crash/apport.0.upload
   600:109:116:0:2017-08-28 11:02:48.793189539 -0300:2017-08-28 
11:02:48.793189539 -0300:/var/crash/apport.0.uploaded
   600:0:116:127426:2017-08-28 11:01:20.158540487 -0300:2017-08-28 
11:02:59.644799651 -0300:/var/crash/apport-gtk.0.crash
  Date: Mon Aug 28 11:01:21 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2015-08-11 (747 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (385 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1713508/+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 1408092] Re: sysconfig.get_path('purelib') points to site-packages directory

[Jeff Larson]

Is there any motion towards resolving this issue?

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

Title:
  sysconfig.get_path('purelib') points to site-packages directory

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Confirmed

Bug description:
  purelib and platlib paths in Python 3 sysconfig module point to site-
  packages directory:

  $ python3 -m sysconfig

  Platform: "linux-x86_64"
  Python version: "3.4"
  Current installation scheme: "posix_prefix"

  Paths: 
data = "/usr"
include = "/usr/include/python3.4m"
platinclude = "/usr/include/python3.4m"
platlib = "/usr/lib/python3.4/site-packages"
platstdlib = "/usr/lib/python3.4"
purelib = "/usr/lib/python3.4/site-packages"
scripts = "/usr/bin"
stdlib = "/usr/lib/python3.4"
  ...

  whereas Python 2 points to dist-packages:

  Platform: "linux-x86_64"
  Python version: "2.7"
  Current installation scheme: "posix_local"

  Paths: 
data = "/usr/local"
include = "/usr/local/include/python2.7"
platinclude = "/usr/local/include/python2.7"
platlib = "/usr/local/lib/python2.7/dist-packages"
platstdlib = "/usr/lib/python2.7"
purelib = "/usr/local/lib/python2.7/dist-packages"
scripts = "/usr/local/bin"
stdlib = "/usr/lib/python2.7"
  ...

  One severe consequence of this is that automake is installing Python
  modules to a location which is not in sys.path, namely site-packages
  directory.

  When one uses automake to create a Makefile that installs a Python
  module to the system, it is installed into /usr/local/lib/python3.4
  /site-packages since automake/aclocal uses sysconfig to determine
  where the package will be installed.

  From /usr/share/aclocal-1.14/python.m4 file:

AC_CACHE_CHECK([for $am_display_PYTHON script directory],
  [am_cv_python_pythondir],
  [if test "x$prefix" = xNONE
   then
 am_py_prefix=$ac_default_prefix
   else
 am_py_prefix=$prefix
   fi
   am_cv_python_pythondir=`$PYTHON -c "
  $am_python_setup_sysconfig
  if can_use_sysconfig:
  sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
  <---
  else:
  from distutils import sysconfig
  ...

  Here, it can be seen that automake uses purelib path defined by the
  sysconfig module of Python. However, since this path is not included
  in sys.path, and thus the installed package cannot be used:

  $ python3 -c "import sys; print(sys.path)"
  ['', '/usr/lib/python3.4', '/usr/lib/python3.4/plat-x86_64-linux-gnu', 
'/usr/lib/python3.4/lib-dynload', '/usr/local/lib/python3.4/dist-packages', 
'/usr/lib/python3/dist-packages']

  
  Ubuntu version:14.10

  $ apt-cache policy python3-minimal 
  python3-minimal:
Installed: 3.4.2-1
Candidate: 3.4.2-1
Version table:
   *** 3.4.2-1 0
  500 http://mirror.23media.de/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092/+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 1687486] Re: difference in "Open With" and "properties" -> "Open With" makes no sense

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  difference in "Open With" and "properties" -> "Open With" makes no
  sense

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04.2: The two named dialogues are different in a
  senseless way.

  Clicking with the right mouse button on a file and clicking "Open
  With" opens a dialogue not having "Default Application" topic. It
  lists the "Default Application" added in "Related Applications" which
  is different from the other "properties" -> "Open With" dialogue. This
  really make no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 23:57:06 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'253'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'"
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1687486/+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 1713391] Re: glib-compile-schemas invalid free in per session override

[Sebastien Bacher]

** Summary changed:

- glib-compile-schemas assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': double free or 
corruption (fasttop): 0x0043559a5bc0 ***
+ glib-compile-schemas invalid free in per session override

** This bug is no longer a duplicate of bug 1711545
   glib-compile-schemas invalid free in per session override

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273 

[Touch-packages] [Bug 1711545] Re: glib-compile-schemas invalid free in per session override

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1713391
   glib-compile-schemas invalid free in per session override

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 
/lib/x86_64-linux-gnu/libc-2.24.so
  7fb4dffce000-7fb4e01cd000 ---p 

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

[Sebastien Bacher]

There is an invalid read error in valgrind

==31343== at 0x4EA5439: g_strfreev (gstrfuncs.c:2496)
==31343== by 0x10C045: set_overrides (glib-compile-schemas.c:2115)
==31343== by 0x10C045: main (glib-compile-schemas.c:2269)
==31343== Address 0x634b8e8 is 8 bytes inside a block of size 16 free'd
==31343== at 0x4C2ED5B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31343== by 0x10BE82: set_overrides (glib-compile-schemas.c:2084)
==31343== by 0x10BE82: main (glib-compile-schemas.c:2269)


** Changed in: glib2.0 (Ubuntu)
   Importance: Medium => High

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

[Sebastien Bacher]

Copying that override in the schemas dir is enough to trigger the
segfault

** Attachment added: "50_sogoupinyin.gschema.override"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1713391/+attachment/4940167/+files/50_sogoupinyin.gschema.override

** Tags added: gnome-17.10

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7577000-f7579000 r--p 

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

[Launchpad Bug Tracker]

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7577000-f7579000 r--p 001b3000 08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7579000-f757a000 rw-p 001b5000 08:01 50856273

[Touch-packages] [Bug 1687486] [NEW] difference in "Open With" and "properties" -> "Open With" makes no sense

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On Ubuntu 16.04.2: The two named dialogues are different in a senseless
way.

Clicking with the right mouse button on a file and clicking "Open With"
opens a dialogue not having "Default Application" topic. It lists the
"Default Application" added in "Related Applications" which is different
from the other "properties" -> "Open With" dialogue. This really make no
sense.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May  1 23:57:06 2017
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'253'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'"
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug xenial
-- 
difference in "Open With" and "properties" -> "Open With" makes no sense
https://bugs.launchpad.net/bugs/1687486
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 997200] Re: Add NetworkManager connectivity config package

[Jeremy Bicha]

** Description changed:

  How to Disable This Feature
  ===
  Option 1
  
  If you are using the default Ubuntu or GNOME, open the Settings app, browse 
to Privacy and turn off Network Connectivity Checking.
  
  Option 2
  
  You could also disable it by adding a file to /etc/NetworkManager/conf.d/
  with this content:
  [connectivity]
  enabled=false
  
  Then restart NetworkManager or your computer, whichever is easier.
- 
- It appears that if option 2 is used, the on/off switch in gnome-control-
- center won't be able to be turned on.
  
  Feature
  ===
  A separate network-manager-config-connectivity-ubuntu package that contains 
the 2-line config snippet to enable NetworkManager's connectivity check. This 
is the same approach taken by Fedora since 2014 (their package is named 
network-manager-config-connectivity-fedora).
  
  With this config, GNOME Shell will pop up a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals
  
  This new feature (and how to opt out) will be mentioned in Ubuntu
  17.10's Release Notes.
  
  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html
  
  Link to newer discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html
  
  Original Bug Report
  ==
  When in a hotel there is a often a T page that is delivered when 
connecting to the network.  Some combination of network manager and update 
manager (or something else entirely) doesn't seem to be able to handle this, 
and update are left in a non-working state after not being able to read package 
headers file.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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

Title:
  Add NetworkManager connectivity config package

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in ubuntu-meta source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Confirmed
Status in network-manager package in Debian:
  Fix Released

Bug description:
  How to Disable This Feature
  ===
  Option 1
  
  If you are using the default Ubuntu or GNOME, open the Settings app, browse 
to Privacy and turn off Network Connectivity Checking.

  Option 2
  
  You could also disable it by adding a file to /etc/NetworkManager/conf.d/
  with this content:
  [connectivity]
  enabled=false

  Then restart NetworkManager or your computer, whichever is easier.

  Feature
  ===
  A separate network-manager-config-connectivity-ubuntu package that contains 
the 2-line config snippet to enable NetworkManager's connectivity check. This 
is the same approach taken by Fedora since 2014 (their package is named 
network-manager-config-connectivity-fedora).

  With this config, GNOME Shell will pop up a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  

[Touch-packages] [Bug 1713500] [NEW] installer

[conny]

Public bug reported:

In the installation of google chrome or other programs, the installer
hangs on some vwersucht but it can not

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug 28 14:58:02 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] 
[1002:0123]
InstallationDate: Installed on 2017-08-27 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=fa5128ac-0b1b-49e5-a14b-b8d3c1b10b12 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XM-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd01/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Aug 28 14:47:58 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  installer

Status in xorg package in Ubuntu:
  New

Bug description:
  In the installation of google chrome or other programs, the installer
  hangs on some vwersucht but it can not

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 28 14:58:02 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7480D] [1002:0123]
  InstallationDate: Installed on 2017-08-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=fa5128ac-0b1b-49e5-a14b-b8d3c1b10b12 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

The kernel patches were committed to the Ubuntu Artful kernel git repo:
https://lists.ubuntu.com/archives/kernel-team/2017-August/086714.html

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1567597/+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 1648901] Re: SPNEGO crash on mechanism failure

[Andreas Hasenack]

@mp26+launch, can you easily reproduce this on trusty? Or did you just
check the code?

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

Title:
  SPNEGO crash on mechanism failure

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Xenial:
  Fix Released

Bug description:
  == SRU JUSTIFICATION ==

  [Impact]

  * Chrome (and other things) crash (segfault) when Kerberos fails to
  authenticate.

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315 ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0 spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1 0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788,
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730,
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

  * context_handle=0x0, segfault occurs trying to dereference a null
  pointer.

  [Test Case]

   * Reproducer

  See dwmw2's (reporter of the bug) comment #3 :
  https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1648901/comments/3

  [Regression Potential]

   * none expected Y and Z release already has the krb5 upstream patch.
   * Debian has the patch as well.
   * A test package has been tested by more than 1 user with success (can't 
reproduce the crash) anymore)

  [Other Info]

   * Upstream fix :
  https://github.com/krb5/krb5/commit/3beb564cea3d219efcf71682b6576cad548c2d23

  * Pull Request :
  https://github.com/krb5/krb5/pull/385

  * Chrome Bug :
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  * A test pkg including the upstream commit has been proven to fix the
  crash. See:
  https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/comments/9

  ==

  [Original Description]

  Chrome (and other things) crash when Kerberos fails to authenticate:
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  This was fixed in MIT krb5 in January:
  https://github.com/krb5/krb5/pull/385

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315  ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788,
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730,
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1648901/+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 1648901] Re: SPNEGO crash on mechanism failure

[Martin Pohlack]

This is also an issue on trusty.

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

Title:
  SPNEGO crash on mechanism failure

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Xenial:
  Fix Released

Bug description:
  == SRU JUSTIFICATION ==

  [Impact]

  * Chrome (and other things) crash (segfault) when Kerberos fails to
  authenticate.

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315 ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0 spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1 0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788,
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730,
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

  * context_handle=0x0, segfault occurs trying to dereference a null
  pointer.

  [Test Case]

   * Reproducer

  See dwmw2's (reporter of the bug) comment #3 :
  https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1648901/comments/3

  [Regression Potential]

   * none expected Y and Z release already has the krb5 upstream patch.
   * Debian has the patch as well.
   * A test package has been tested by more than 1 user with success (can't 
reproduce the crash) anymore)

  [Other Info]

   * Upstream fix :
  https://github.com/krb5/krb5/commit/3beb564cea3d219efcf71682b6576cad548c2d23

  * Pull Request :
  https://github.com/krb5/krb5/pull/385

  * Chrome Bug :
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  * A test pkg including the upstream commit has been proven to fix the
  crash. See:
  https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/comments/9

  ==

  [Original Description]

  Chrome (and other things) crash when Kerberos fails to authenticate:
  https://bugs.chromium.org/p/chromium/issues/detail?id=554905

  This was fixed in MIT krb5 in January:
  https://github.com/krb5/krb5/pull/385

  Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffdd687700 (LWP 14851)]
  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, 
src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  2315  ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or 
directory.
  (gdb) bt
  #0  spnego_gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668,
  lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, 
ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, 
opened=0x7fffdd68572c)
  at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315
  #1  0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, 
context_handle=, src_name=0x7fffdd685788,
  targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, 
mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, 
locally_initiated=0x7fffdd685730,
  opened=0x7fffdd68572c) at 
../../../../src/lib/gssapi/mechglue/g_inq_context.c:114

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1648901/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

[Stuart Bishop]

** Also affects: layer-snap
   Importance: Undecided
   Status: New

** Changed in: layer-snap
   Importance: Undecided => Critical

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

[Michel-Ekimia]

Shall the WPA package be updated in 16.04 ? I guess the impact is so
limited that it's possible.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Confirmed

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1713457] [NEW] DNS search domain not removed from resolv.conf on disconnect

[Anders Kaseorg]

Public bug reported:

When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected.  But if I then disconnect and connect to a different network,
it is not removed from resolv.conf.  If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
first one, and so on.  Depending on the network, this can cause DNS
leaks, name resolution failures, or other misbehavior.

To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 172.20.20.1 dev wlp3s0 proto static metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
 wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
 enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
 lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful regression-release

** Description changed:

  When I connect to a wireless network that sets a DNS search domain name
- via DHCP, the line 'search domain' is added to /etc/resolv.conf as
+ via DHCP, the line 'search ' is added to /etc/resolv.conf as
  expected.  But if I then disconnect and connect to a different network,
  it is not removed from resolv.conf.  If the second network also sets a
  search domain name, that one gets appended to resolv.conf along with the
  first one, and so on.  Depending on the network, this can cause name
  resolution failures or other misbehavior.
  
  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IpRoute:
-  default via 172.20.20.1 dev wlp3s0 proto static metric 600 
-  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
-  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
+  default via 172.20.20.1 dev wlp3s0 proto static metric 600
+  169.254.0.0/16 dev wlp3s0 scope link metric 1000
+  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  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
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
-  wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  

[Touch-packages] [Bug 1713017] Re: Enable MIDI support

[wvengen]

Thanks, I agree that 18.04 would be good.

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

Title:
  Enable MIDI support

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
  enable Bluetooth MIDI support. This did not seem to be enabled by
  default in the build from
  https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
  MIDI devices, gatttool could talk to them, but no MIDI device was
  made; also ldd showed no linkage to libasound.so.2).

  After recompiling it with libasound2-dev installed and --enable-midi
  in debian/rules, it worked.

  Suggestion: add libasound2-dev to bluez dependencies, add --enable-
  midi to rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+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 1711545] Re: glib-compile-schemas invalid free in per session override

[dino99]

Like Jeremy said, i have not met that error again since that report.
Maybe the case has not been reproduced yet, and the problem will
reappear later.

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 
/lib/x86_64-linux-gnu/libc-2.24.so
  7fb4dffce000-7fb4e01cd000 ---p 001bc000 08:04 54 

[Touch-packages] [Bug 1711545] Re: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 ***

[Sebastien Bacher]

The invalid read

==31343==at 0x4EA5439: g_strfreev (gstrfuncs.c:2496)
==31343==by 0x10C045: set_overrides (glib-compile-schemas.c:2115)
==31343==by 0x10C045: main (glib-compile-schemas.c:2269)
==31343==  Address 0x634b8e8 is 8 bytes inside a block of size 16 free'd
==31343==at 0x4C2ED5B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==31343==by 0x10BE82: set_overrides (glib-compile-schemas.c:2084)
==31343==by 0x10BE82: main (glib-compile-schemas.c:2269)


** Summary changed:

- glib-compile-schemas assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): 
invalid pointer: 0x002601a1d1e0 ***
+ glib-compile-schemas invalid free in per session override

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149   

[Touch-packages] [Bug 1711545] Re: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 ***

[Sebastien Bacher]

The file attached triggers the segfault once copied in the schemas
system dir

** Attachment added: "50_sogoupinyin.gschema.override"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1711545/+attachment/4940012/+files/50_sogoupinyin.gschema.override

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1713435

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713435/+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 1713435] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Avishek Goyal]

Public bug reported:

invoke-rc.d: initscript ssh, action "start" failed.
● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms ago
  Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
 Main PID: 21687 (code=exited, status=255)

Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell server...
Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, c...a
Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure Shel
Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed state.
Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 'ex

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Aug 28 14:36:40 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-12 (258 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1713435

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713435/+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 1711545] Re: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 ***

[Sebastien Bacher]

Glancing on the code it seems there could be a double g_strfreev
(pieces) case at least when schemas == NULL? It frees it and continue
and then it's freed again at least before returning?

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 
/lib/x86_64-linux-gnu/libc-2.24.so
  7fb4dffce000-7fb4e01cd000 ---p 001bc000 08:04 54

[Touch-packages] [Bug 1711545] Re: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 ***

[Sebastien Bacher]

The issue is new and likely due to the per-session override code

** Changed in: glib2.0 (Ubuntu)
   Importance: Medium => High

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

Title:
  glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64
  -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid
  pointer: 0x002601a1d1e0 ***

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 
/lib/x86_64-linux-gnu/libc-2.24.so
  

[Touch-packages] [Bug 1713391] Re: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': double free or corruption (fasttop): 0x00000043559a5bc0

[Sebastien Bacher]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1711545
   glib-compile-schemas assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): 
invalid pointer: 0x002601a1d1e0 ***

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

Title:
  glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64
  -linux-gnu/glib-2.0/glib-compile-schemas': double free or corruption
  (fasttop): 0x0043559a5bc0 ***

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273 

[Touch-packages] [Bug 1694084] Re: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to install/upgrade: package libqt5script5:amd64 is not ready for configuration cannot configure (current status

[Launchpad Bug Tracker]

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

** Changed in: qtscript-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to
  install/upgrade: package libqt5script5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in qtscript-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  software center is crashing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5script5:amd64 5.5.1+dfsg-2build1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libqt5script5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 27 19:49:52 2017
  DpkgTerminalLog:
   dpkg: error processing package libqt5script5:amd64 (--configure):
package libqt5script5:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-13 (226 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: qtscript-opensource-src
  Title: package libqt5script5:amd64 5.5.1+dfsg-2build1 failed to 
install/upgrade: package libqt5script5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtscript-opensource-src/+bug/1694084/+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 1712660] Re: application menu icon in title bar has wrong size

[Philipp]

Seems to be fixed now.

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot

  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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