[Touch-packages] [Bug 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

[Daniel van Vugt]

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

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

Title:
  Intel HD3000 Sandy Bridge - Wrong display driver used by X.org

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu
  desktop via X.org, a wrong display driver is used (llvmpipe). It will
  cause a horribly poor performance due to software acceleration.

  WORKAROUND: When I switch to Wayland, the correct driver (intel) with
  enabled hardware acceleration is loaded.

  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2018-01-27 13:13:29,681 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.13.0-39-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:167e]
  InstallationDate: Installed on 2016-11-02 (568 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  MachineType: Hewlett-Packard HP ProBook 4330s
  NonfreeKernelModules: wl
  Package: xorg (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/elementary--vg-root ro quiet splash 
resume=UUID=77b20f63-d6db-44a9-afa0-db8f4ce36867 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  wayland-session bionic ubuntu
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (117 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.09
  dmi.board.name: 167E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1A
  dmi.chassis.asset.tag: CNU13512RH
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4330s:pvrA0001D02:rvnHewlett-Packard:rn167E:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4330s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat May 20 09:05:05 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4912
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

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

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

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions

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

[Touch-packages] [Bug 1768967] Re: Screen randomly flips 180 degrees

[Daniel van Vugt]

I think the low level accelerometer logic is somewhere between the Linux
kernel and the iio-sensor-proxy package. Reassigning.

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

** Also affects: iio-sensor-proxy (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Screen randomly flips 180 degrees

Status in iio-sensor-proxy package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest-
  gtk, the laptop has a ST LIS3LV02DL Accelerometer with three axes.
  Axes 0 and 2 remain at 0 (center) no matter what I do. Axis 1 on the
  other hand senses how much the base of the laptop (the lower half of
  the clam shell, the part with the keyboard), is tilted. When the
  laptop is level, the Axis's value should be 0, but it can be anywhere
  from -20 to 20 while the laptop is being typed on. When its reading is
  above 0, the screen flips. These two facts cause the screen to flip
  seemingly randomly while it's being used.

  Workarround: Lock the screen orientation in GNOME.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 15:53:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: Classis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242
  dmi.product.name: HP Pavilion 350 G1 Notebook PC
  dmi.product.version: 05A620300
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1768967/+subscriptions

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

[Touch-packages] [Bug 1767552] Re: screen rotates if laptop tilts

[Daniel van Vugt]

There is a rotation lock button you can choose next to the power button
in the Gnome system menu. Please try that.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  screen rotates if laptop tilts

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have ran windows 7, 10, ubuntu 16.04, linux mint and maybe others
  and i can't recall it doing this before. it is hp 450 g2 laptop. it is
  not a 2in1 tablet/laptop. i looked for info in forums but had no luck.
  i also checked in settings because i thought it may have had a tablet
  setting i could turn off.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 21:58:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:2248]
 Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d0b638ce-09f3-4d54-a78f-b7aeebaef22f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.09
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.09:bd01/21/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3009DD10303:rvnHewlett-Packard:rn2248:rvrKBCVersion59.21:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G2
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1769022] Re: ubuntu 18.04 freezes after the login

[Daniel van Vugt]

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ubuntu 18.04 freezes after the login

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
  dmi.product.family: IDEAPAD
  dmi.product.name: 129925U
  dmi.product.version: Ideapad Z575
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 22:52:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1769029] Re: Display on Dell 1440x900 is not available

[Daniel van Vugt]

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

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

Title:
  Display on Dell 1440x900 is not available

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GZM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude

[Daniel van Vugt]

** No longer affects: xorg (Ubuntu)

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

Title:
  USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate
  16.04.4 , and DELL latitude

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am facing the problem that is similar to the one described in the
  thread: https://ubuntuforums.org/showthread.php?t=2342985

  Laptop (Dell Latitude 6420) randomly stops responding to the usb
  Trackball and Keyboard. Unplugging & plugging them back into a
  different port does not fix the problem. Sometimes the problem is
  fixed after rebooting or suspending the laptopo, then turning it on;
  but the problem re-appears almost immediately - after 10".

  The problem is related to the Logitech trackman wheel & Mircosoft PS2
  Keyboard, both are old.

  Command "lsusb" for the 2 devices gives:
  Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
  Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

  Command "tlp-stat -u" for the 2 devices gives:
  Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 
-- Logitech, Inc. TrackMan Wheel (usbhid)
  Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 
-- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

  Command "uname -ra" gives:
  Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  This problem tends to be very frustrating.

  note: I think this is not related with autosuspend, but rather with
  buffer overflow for the specific devices due to that they are not
  supported in the kernel code.

  Regards
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kpapadim   2115 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5
  InstallationDate: Installed on 2017-07-23 (292 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude E6420
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash 
usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1769450] Re: proper display panel missing, second monitor mirrored

[Daniel van Vugt]

It appears you are stuck in recovery mode, which prevents most graphics
drivers from working properly ("nomodeset"):

[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic
root=UUID=d2f3f98a-d42e-4ba5-8bcf-95d318ad089b ro recovery nomodeset

To fix this, reboot and as soon as the screen turns purple, tap Escape
once (and only once). Then choose Advanced options and select the normal
(not the recovery) kernel.

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

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

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

Title:
  proper display panel missing, second monitor mirrored

Status in Ubuntu:
  Invalid

Bug description:
  While I don't believe the initial upgrade to Bionic caused this, a
  series of power outages later (+4 in 2 days) and some possible data
  corruption, I no longer have the full display manager available, my 2
  displays are mirrored (no option to change) and are running in less
  than optimal resolution (no option to go higher). Previously working
  fine with "stretched" display using onboard AMD graphics and standard
  Ubuntu driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun May  6 07:19:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. M5A88-V EVO [1043:843e]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=d2f3f98a-d42e-4ba5-8bcf-95d318ad089b ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91+git1805020630.1ac3ec~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805051930.2f1ad7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805051930.2f1ad7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat May  5 23:00:10 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPrimax Kensington Eagle Trackball MOUSE, id 8
   inputDarfon USB Combo Keyboard KEYBOARD, id 9
   inputDarfon USB Combo Keyboard KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Touch-packages] [Bug 1796231] [NEW] package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[54krishna]

Public bug reported:

package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/up

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglib2.0-bin 2.56.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 cups-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct  5 09:45:57 2018
DuplicateSignature:
 package:libglib2.0-bin:2.56.1-2ubuntu1
 Setting up cups-common (2.2.7-1ubuntu2.1) ...
 dpkg: error processing package libglib2.0-bin (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-10-04 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: glib2.0
Title: package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/up

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-bin 2.56.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   cups-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct  5 09:45:57 2018
  DuplicateSignature:
   package:libglib2.0-bin:2.56.1-2ubuntu1
   Setting up cups-common (2.2.7-1ubuntu2.1) ...
   dpkg: error processing package libglib2.0-bin (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: glib2.0
  Title: package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1796231/+subscriptions

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

[Touch-packages] [Bug 510544] Re: Cups duplex printing possible through ipp but not through samba

[Launchpad Bug Tracker]

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

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

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

Title:
  Cups duplex printing possible through ipp but not through samba

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  I have a perculiar problem. I have a small file/print Ubuntu server
  running jaunty (9.04) with an HP Laserjet 1320 printer attached with a
  built-in duplex unit. The printer is shared via samba (smb://...). If
  the client uses the smb:// URI to print to this printer, duplex
  printing does not work. If I define the queue as an ipp:// one it
  works. Can't figure this out.

  Clients are Ubuntu Karmic desktops. With Jaunty on the desktops, this
  issue did not arise.

  Output of lsb_release -rd
  ***
  Description:  Ubuntu 9.04
  Release:  9.04

  Output of apt-cache policy cups:
  **
  cups:
Installed: 1.3.9-17ubuntu3.2
Candidate: 1.3.9-17ubuntu3.4
Version table:
   1.3.9-17ubuntu3.4 0
  500 http://in.archive.ubuntu.com jaunty-updates/main Packages
  500 http://security.ubuntu.com jaunty-security/main Packages
   *** 1.3.9-17ubuntu3.2 0
  100 /var/lib/dpkg/status
   1.3.9-17ubuntu1 0
  500 cdrom://Ubuntu 9.04 _Jaunty Jackalope_ - Release amd64 
(20090421.3) jaunty/main Packages
  500 http://in.archive.ubuntu.com jaunty/main Packages
  

  Will be grateful for help
  Thanks

  ProblemType: Bug
  Architecture: amd64
  CurrentDmesg:
   [   31.161261] eth0: no IPv6 routers present
   [   89.18] Clocksource tsc unstable (delta = -276640996 ns)
  Date: Thu Jan 21 14:01:35 2010
  DistroRelease: Ubuntu 9.04
  Lpstat: device for HPLASER: 
hp:/usb/hp_LaserJet_1320_series?serial=00CNHJ63P0XY
  Lsusb:
   Bus 002 Device 003: ID :  
   Bus 002 Device 002: ID 03f0:1d17 Hewlett-Packard LaserJet 1320
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP ProLiant ML115 G5
  Package: cups 1.3.9-17ubuntu3.2
  Papersize: a4
  PpdFiles: HPLASER: HP LaserJet 1320 hpijs, hpijs 3.9.2.49 - HPLIP 3.9.2
  ProcCmdLine: root=/dev/mapper/server-root ro quiet vga=792
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_IN
  ProcVersionSignature: Ubuntu 2.6.28-11.42-server
  SourcePackage: cups

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

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

[Touch-packages] [Bug 570308] Re: network printer wants authentication password. no such password exists. problem has incurred after printer updates in Ubuntu update bundle

[Launchpad Bug Tracker]

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

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

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

Title:
  network printer wants authentication password. no such password
  exists. problem has incurred after printer updates in Ubuntu update
  bundle

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: openoffice.org

  After Canon printer driver upgrades in regular Ubuntu upgrade, I can
  no longer use network printer. Jobs require authentication password,
  but no such password has been created. I have not managed to work
  around the problem. Means I can no longer print from network computer.

  Printer is attached to Mac with OS X, network notebook runs on Ubuntu.

  Printer is a Canon mp 750 model.

  
  Best regards,

  Lido

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: e36b18ec1c0d81d02864d0fec0ca6a90
  CheckboxSystem: c69722ecac764861be52925fa50b4dcc
  Date: Mon Apr 26 19:38:25 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: openoffice.org-core 1:3.1.1-5ubuntu1.1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-20-generic i686

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

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

[Touch-packages] [Bug 1796231] Re: package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1796231

Title:
  package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/up

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-bin 2.56.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   cups-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct  5 09:45:57 2018
  DuplicateSignature:
   package:libglib2.0-bin:2.56.1-2ubuntu1
   Setting up cups-common (2.2.7-1ubuntu2.1) ...
   dpkg: error processing package libglib2.0-bin (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: glib2.0
  Title: package libglib2.0-bin 2.56.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1796231/+subscriptions

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

[Touch-packages] [Bug 566887] Re: network printer + DNSSD + External DNS server -> won't print

[Launchpad Bug Tracker]

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

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

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

Title:
  network printer + DNSSD + External DNS server -> won't print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  My setup: 
  - Home LAN
  - my box: Ubuntu Lucid x64, eth0 is standard interface with DNS set to 
8.8.8.8 (Google) and not to our local router
  - Samsung ML-2850D (network printer)

  Problem:
  - Printer is shown active in the printer overview, but doesn't print
  - printing jobs fail with "dnssd error", even though everything worked out of 
the box before upgrading to Lucid

  My workaround:

  in /etc/cups/printers.conf, replace entry:
   > DeviceURI 
dnssd://Photosmart%208400%20series%20(D29CFB)._pdl-datastream._tcp.local/
  with 
   > DeviceURI socket://192.168.178.107:9100

  I'm not using a Photosmart printer of course, but the dnssd://-entry looked 
nearly the comparable.
  After I replaced the DeviceURI entry with the socket://-Adress and the local 
IP Address of my printer, everything worked fine.

  My question:
  Why did this error occur in the first place - I recall that before upgrading 
to Lucid, I never read anything about dnssd in cups and underneath my printer 
the ip address was shown?

  During my research I found out about a couple of topics on ubuntu-
  related forums which addressed the same topic so it seems like a bug
  and not a mistake on my side.

  Is it possible, that the external DNS server is influencing the dnssd
  in some bogus way?

  Thanks for your patience,

  -bf

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

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

[Touch-packages] [Bug 511278] Re: Officejet 6500 Wireless Using Draft In localhost:631 uses FastDraft

[Launchpad Bug Tracker]

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

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

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

Title:
  Officejet 6500 Wireless Using Draft In localhost:631 uses FastDraft

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Since using grayscale in the printing preferences through GNOME made
  it so firefox still  printed in color, I had to open up the
  localhost:631 page for once so I could change the printout mode to
  grayscale. However, there is a problem: Selecting Draft in
  localhost:631 uses FastDraft and not Draft for my wireless HP printer.
  So I have to select normal grayscale, so that paper doesn't shoot out
  of the printer like it was a weapon.

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

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

[Touch-packages] [Bug 634754] Re: TMPDIR environment variable not exported to backend

[Launchpad Bug Tracker]

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

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

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

Title:
  TMPDIR environment variable not exported to backend

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Description:Ubuntu 10.04.1 LTS
  Release:10.04

  cups:
Installiert: 1.4.3-1ubuntu1.2
Kandidat: 1.4.3-1ubuntu1.2
Versions-Tabelle:
   *** 1.4.3-1ubuntu1.2 0
  500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
  100 /var/lib/dpkg/status
   1.4.3-1 0
  500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages

  
  I'm writing a simple shell backend for cups, that should write the output to 
the temporary directory TMPDIR.

  But this variable does not seem to be exported to the backend although
  it is specified in the debug error log

  Error.log

  ...
  D [10/Sep/2010:10:07:59 +0200] [Job 2442] 
envp[12]="TMPDIR=/var/spool/cups/tmp"
  ...

  Because my backend kept crashing all time I added some debug info. I
  noticed that the environment variable TMPDIR does not seem to be
  exported to the backend.

  Export from my basic script

  echo "INFO: Software is ${SOFTWARE}" >&2
  echo "INFO: Device URI is ${DEVICE_URI}" >&2
  echo "INFO: TMPDIR is ${TMPDIR}" >&2

  And this is the output from my backend in error.log

  I [10/Sep/2010:10:00:12 +0200] [Job 2440] Software is CUPS/1.4.3
  I [10/Sep/2010:10:00:12 +0200] [Job 2440] Device URI is pdfandmail:/
  I [10/Sep/2010:10:00:12 +0200] [Job 2440] TMPDIR is

  TMPDIR should be "/var/spool/cups/tmp" as mentioned earlier.

  Regards,

  Robert

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

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

[Touch-packages] [Bug 577816] Re: Epson Stylus Office BX300F Won't print in selected reverse mode

[Launchpad Bug Tracker]

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

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

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

Title:
  Epson Stylus Office BX300F Won't print in selected reverse mode

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  1. Ubuntu Lucid Lynx 10.04 
  2. Foomatic-db-engine 4.0.4-0ubuntu1
  3.The Epson Stylus Office BX300F printer won't print in selected reverse mode.
 The result is always first page printed first whether "normal" or 
"reverse" is selected in printer options.
 The printer is networked.

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

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

[Touch-packages] [Bug 598446] Re: printer names have IP address attached

[Launchpad Bug Tracker]

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

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

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

Title:
  printer names have IP address attached

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Description:  Ubuntu 10.04 LTS
  Release:  10.04
  Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2

  Since the recent cups update, browsed printer names have IP addresses 
attached in /etc/printcap, as though
  BrowseShortNames No
  were in the cupsd.conf file.  (It isn't, and even adding BrowseShortNames Yes 
doesn't suppress the IP address).  This appears to afflict only 64-bit systems. 
 The same update on my 32-bit system with the same cupsd.conf did not cause IP 
addresses to get tacked on.  Here's how my cupsd.conf differs from the default

# Show shared printers on the local network.
  ! # Browsing Off
  ! Browsing On
BrowseOrder allow,deny
  ! BrowseAllow localhost
BrowseLocalProtocols CUPS dnssd
  ! BrowseAddress localhost
  ! BrowsePoll cups.research.att.com

  The printer formerly known as d227 is now d227@135.207.178.16, for
  example.  So far, everyone here running a 10.04 64-bit system has seen
  the problem since the recent cups update.  Nobody running a 32-bit
  system has seen it.  I can provide additional information as needed.
  -- jpl

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

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

[Touch-packages] [Bug 522676] Re: Cups shrinks legal size documents in Xerox Workcentre 4150

[Launchpad Bug Tracker]

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

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

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

Title:
  Cups shrinks legal size documents in Xerox Workcentre 4150

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Kubuntu 9.10, Kde 4.3.5 and 4.3.2.  I have a Xerox Workcentre 4150
  printer in my office which worked fine until the updates that came in
  the attached document.  We print mainly in legal size.  Since the
  updates, the cups shrinks legal size documents to letter; no matter if
  we choose legal as the paper size in all possible options:  printer
  defaults and printer options.  In order to test the system I ran a
  live cd and install the printer and everything worked fine.  Then I
  did a fresh install (kde 4.3.2) updated and experience the same
  problem.  Then I upgraded to 4.3.5 and have the same problem.  I have
  three computers in my office running Kubuntu Karmic 9.10.  One of the
  computers has not been been updated with the updates of the attached
  document and it prints fine.  The other two have been updated with the
  patches and experience the problem.  We have two other printers, a
  Brother MFC 8460n and a HP Laserjet P1006, which print fine.

  ProblemType: Bug
  Architecture: i386
  CupsErrorLog:
   E [15/Feb/2010:10:31:43 -0400] Unable to remove temporary file 
"/var/spool/cups/tmp/.hplip" - Is a directory
   E [15/Feb/2010:10:35:26 -0400] [cups-driverd] Bad driver information file 
"/usr/share/cups/drv/sample.drv"!
   E [15/Feb/2010:12:14:41 -0400] Unable to remove temporary file 
"/var/spool/cups/tmp/.hplip" - Is a directory
   E [15/Feb/2010:22:24:00 -0400] Unable to remove temporary file 
"/var/spool/cups/tmp/.hplip" - Is a directory
   E [16/Feb/2010:10:10:00 -0400] Unable to remove temporary file 
"/var/spool/cups/tmp/.hplip" - Is a directory
  Date: Tue Feb 16 10:14:35 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Lpstat:
   device for HP-LaserJet-P1006: hp:/usb/HP_LaserJet_P1006?serial=AC022BP
   device for Xerox: socket://10.0.0.68:9100
  MachineType: TOSHIBA Satellite L305D
  NonfreeKernelModules: fglrx
  Package: cups 1.4.1-5ubuntu2.2
  Papersize: letter
  PpdFiles:
   HP-LaserJet-P1006: HP LaserJet P1006 Foomatic/foo2xqx (recommended)
   Xerox: Xerox WorkCentre 4118 Foomatic/Postscript
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic 
root=UUID=d259b0b9-0248-44e9-b394-a58e249214d0 ro quiet splash
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: cups
  Uname: Linux 2.6.31-19-generic i686
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1871): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (firefox:1971): GLib-WARNING **: g_set_prgname() called multiple times
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Ant3
  dmi.board.vendor: ATI Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd05/23/2008:svnTOSHIBA:pnSatelliteL305D:pvrPSLC8U-00F010:rvnATICorp.:rnAnt3:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite L305D
  dmi.product.version: PSLC8U-00F010
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 588345] Re: Print server doesn't work w/ space on the end

[Launchpad Bug Tracker]

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

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

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

Title:
  Print server doesn't work w/ space on the end

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  The standard interface for CUPS in Ubuntu does NOT delete spaces in
  IP-adresses, so if I accidently press enter when entering an IP (eg.
  192.168.0.2[SPACE]) the computer will find the printer on 192.168.0.2,
  but then give me an error after "Describe Printer" that says 'client-
  error-not-possible" as it tries to connect to 192.168.0.2 :PORT
  instead of 192.168.0.2:PORT.

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

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

[Touch-packages] [Bug 521227] Re: Make Canon MF4270 work out of the box

[Launchpad Bug Tracker]

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

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

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

Title:
  Make Canon MF4270 work out of the box

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: libcups2

  The Canon MF4270 printer has drivers available from Canon, but it
  doesn't seem that they are packaged.  Instructions for getting this
  printer working can be found in the following forum thread:

  http://ubuntuforums.org/showthread.php?t=1140724

  These drivers should be packaged and included in Ubuntu in order to
  make installation of this printer less painful.

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

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

[Touch-packages] [Bug 588949] Re: CUPS conf IPv6 error - takes ::1 and [(xxxx:)^8], but crews up at [::1]

[Launchpad Bug Tracker]

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

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

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

Title:
  CUPS conf IPv6 error - takes ::1 and [(:)^8], but crews up at
  [::1]

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  cupsd.conf configuration file is inconsistent about IPv6 addressed in
  ACL rules (Allow / Deny)

  It takes "::1" and "[:::::::]" patterns,
  but daemon exits with its universal message (that it can't read config file) 
when it gets "[::1]" or IPv6 address without  [ ].

  It is quite hard to suspect, that (knowing that ::1 works and [::1] does not) 
it works this way.
  And by hard I mean >1h I spend by brute-forcing which of the lines causes 
trouble.

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

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

[Touch-packages] [Bug 575506] Re: Two-sided printing with non-duplex printer does not work well in Ubuntu

[Launchpad Bug Tracker]

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

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

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

Title:
  Two-sided printing with non-duplex printer does not work well in
  Ubuntu

Status in cups package in Ubuntu:
  Expired

Bug description:
  Steps to reproduce:
  Use your non-duplex inkjet printer to print some pages in duplex mode, e.g. a 
PDF from Evince.

  Expected behaviour:
  Your printer prints every second page and after half the job is done, a 
message is shown that tells you to put the paper back into the printer the 
other way around and then click a button.

  What actually happens:
  Your printer prints all pages, every second one rotated by 180 degrees.

  Not that user-friendly.

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

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

[Touch-packages] [Bug 557168] Re: nxclient and permissions on /usr/lib/cups/backend/ipp

[Launchpad Bug Tracker]

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

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

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

Title:
  nxclient and permissions on /usr/lib/cups/backend/ipp

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  When installing nxclient from NoMachine 
(http://www.nomachine.com/download.php) it complains about the permissions on 
ipp.
  If this is a valid complaint, then please fix in cups.

  Sætter nxclient (3.4.0-7) op...
  Showing file: /usr/NX/share/documents/client/cups-info

   CUPS Printing Backend

   The NX Client set-up procedure detected that your "IPP CUPS" printing
   backend doesn't allow printing from the NX session. In order to have
   printing support in your NX system, you need to set proper permissions
   on the IPP backend. Please execute:

 chmod 755 /usr/lib/cups/backend/ipp

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

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

[Touch-packages] [Bug 608015] Re: Not picking up connected printer.

[Launchpad Bug Tracker]

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

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

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

Title:
  Not picking up connected printer.

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  HP Laser printer via serial port has disappeared from cups, upon this
  start up. Will not connect.

  Have checked printer connections. Problem with printing system??

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

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

[Touch-packages] [Bug 1769880] Re: ubuntu 14.04 amd / ati radeon 6400/7400 video card is continuously requesting the monitor configuration

[Daniel van Vugt]

Can you explain in more detail what "continuously requesting the monitor
configuration" means?

Maybe a screenshot or photo of the problem?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  ubuntu 14.04 amd / ati radeon 6400/7400 video card is continuously
  requesting the monitor configuration

Status in Ubuntu:
  Incomplete

Bug description:
  Hi, my ubuntu 14.04 amd / ati radeon 6400/7400 video card is
  continuously requesting the monitor configuration, it has so many
  requests that it looks like virus windows. I appreciate the help and
  patience.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May  8 09:29:55 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-06 (63 days ago)
  InstallationMedia: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 649601] Re: no printing pdf files to wireless networked Brother HL 4070 CDW

[Launchpad Bug Tracker]

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

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

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

Title:
  no printing pdf files to wireless networked Brother HL 4070 CDW

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Ubuntu 10.4 pdf files for the most part refuse to print from any program that 
supports pdf. Or sometimes if I don't mind waiting an hour it will finally 
print some part of the page. Printer flashes during this period but more often 
that not nothing prints.
  Printer: Brother HL 4070 CDW wirelessly networked (prints pdf's in Windows 
and all other files in Ubuntu)

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

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

[Touch-packages] [Bug 1785421] Re: package bluez 5.48-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package bluez 5.48-0ubuntu3.1 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I have no more details that this. when I open my computer I get a
  message saying there was an error. I don't know what it is. this is
  the best I got.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic i686
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  Date: Sat Aug  4 14:34:52 2018
  DpkgHistoryLog:
   Start-Date: 2018-08-04  14:31:48
   Commandline: apt install -f
   Requested-By: woodsy (1000)
   Upgrade: libsystemd0:i386 (237-3ubuntu10.1, 237-3ubuntu10.3), udev:i386 
(237-3ubuntu10.1, 237-3ubuntu10.3), libudev1:i386 (237-3ubuntu10.2, 
237-3ubuntu10.3), libpam-systemd:i386 (237-3ubuntu10.1, 237-3ubuntu10.3), 
systemd:i386 (237-3ubuntu10.1, 237-3ubuntu10.3), libnss-systemd:i386 
(237-3ubuntu10.2, 237-3ubuntu10.3)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2012-09-15 (2149 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  InterestingModules: bluetooth
  MachineType: Dell Inc. Dell DXP061
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d5274408-d555-46cd-a38b-b197aa20407a ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: bluez
  Title: package bluez 5.48-0ubuntu3.1 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (84 days ago)
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0CT017
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd05/24/2007:svnDellInc.:pnDellDXP061:pvr:rvnDellInc.:rn0CT017:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell DXP061
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog: Aug 04 15:42:39 woodsy-Dell-DXP061 NetworkManager[1001]:   
[1533411759.0367] Loaded device plugin: NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

[TJ]

An strace shows:

$ sudo strace -o /tmp/dpkg.log -f  dpkg -i /var/cache/apt/archives/libc6
-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb

$ grep -E '(Mcrt1|error processing)' /tmp/strace-dpkg.log

22528 lstat("/usr/arm-linux-gnueabihf/lib/Mcrt1.o", 0x7ffef13bf320) = -1 ENOENT 
(No such file or directory)
22528 rename("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-tmp", 
"/usr/arm-linux-gnueabihf/lib/Mcrt1.o") = -1 ENOENT (No such file or directory)
22528 rmdir("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new") = -1 ENOENT (No 
such file or directory)
22528 rmdir("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-tmp") = -1 ENOENT (No 
such file or directory)
22528 openat(AT_FDCWD, "/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new", 
O_WRONLY|O_CREAT|O_EXCL, 000) = 11
22528 utimes("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new", 
[{tv_sec=1538707686, tv_usec=0} /* 2018-10-05T03:48:06+0100 */, 
{tv_sec=1537191595, tv_usec=0} /* 2018-09-17T14:39:55+0100 */]) = 0
22528 lstat("/usr/arm-linux-gnueabi/libhf/Mcrt1.o", 0x7ffef13bf320) = -1 ENOENT 
(No such file or directory)
22528 rename("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-tmp", 
"/usr/arm-linux-gnueabi/libhf/Mcrt1.o") = -1 ENOENT (No such file or directory)
22528 rmdir("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new") = -1 ENOTDIR (Not 
a directory)
22528 lstat("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new", 
{st_mode=S_IFREG|0644, st_size=448, ...}) = 0
22528 unlink("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new") = 0
22528 rmdir("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-tmp") = -1 ENOENT (No 
such file or directory)
22528 symlink("../../arm-linux-gnueabihf/lib/Mcrt1.o", 
"/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new") = 0
22528 lchown("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new", 0, 0) = 0
22528 utimensat(AT_FDCWD, "/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new", 
[{tv_sec=1538707686, tv_nsec=0} /* 2018-10-05T03:48:06+0100 */, 
{tv_sec=1537191595, tv_nsec=0} /* 2018-09-17T14:39:55+0100 */], 
AT_SYMLINK_NOFOLLOW) = 0
22528 openat(AT_FDCWD, "/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new", 
O_WRONLY) = -1 ENOENT (No such file or directory)
22528 write(2, "\33[1mdpkg:\33[0m error processing a"..., 219) = 219
22528 lstat("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-tmp", 0x7ffef13bff30) = 
-1 ENOENT (No such file or directory)
22528 rmdir("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new") = -1 ENOTDIR (Not 
a directory)
22528 lstat("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new", 
{st_mode=S_IFLNK|0777, st_size=37, ...}) = 0
22528 unlink("/usr/arm-linux-gnueabi/libhf/Mcrt1.o.dpkg-new") = 0
22528 lstat("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-tmp", 0x7ffef13bff30) = 
-1 ENOENT (No such file or directory)
22528 rmdir("/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new") = -1 ENOENT (No 
such file or directory)


At the same time an inotifywait shows:

$ grep Mcrt1 /tmp/inotifywait.log

/usr/arm-linux-gnueabihf/lib/ CREATE Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ OPEN Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ MODIFY Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ ATTRIB Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ CLOSE_WRITE,CLOSE Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ ATTRIB Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ DELETE Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ CREATE Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ ATTRIB Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ ATTRIB Mcrt1.o.dpkg-new
/usr/arm-linux-gnueabihf/lib/ DELETE Mcrt1.o.dpkg-new

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in cross-toolchain-base-ports package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Released
Status in cross-toolchain-base source package in Bionic:
  Fix Released
Status in cross-toolchain-base-ports source package in Bionic:
  Fix Released
Status in gcc-7 source package in Bionic:
  Fix Released
Status in gcc-7-cross source package in Bionic:
  Fix Released
Status in gcc-7-cross-ports source package in Bionic:
  Fix Released
Status in gcc-8 source package in Bionic:
  Fix Released
Status in gcc-8-cross source package in Bionic:
  Fix Released
Status in gcc-8-cross-ports source package in Bionic:
  Fix Released
Status in gcc-defaults source package in Bionic:
  Fix Released
Status in gcc-defaults-ports source package 

[Touch-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Kai-Heng Feng]

Not really. Maybe Skype, maybe pulse audio...

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1796093] Re: LAUNCH APLICATIONS

[Daniel van Vugt]

That's correct. The Intel graphics driver is built into the Linux kernel
and comes with no application.

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

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

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

Title:
  LAUNCH APLICATIONS

Status in Ubuntu:
  Invalid

Bug description:
  NO LAUNCH APLICATION FOR DRIVER GRAPHICS INTEL

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Oct  4 08:35:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-28-generic, x86_64: installed
   nvidia-390, 390.87, 4.10.0-28-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0585]
  InstallationDate: Installed on 2018-10-01 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. OptiPlex 3010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=532b727f-99d1-4f99-9834-367acdb4d126 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd11/16/2016:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Oct  4 08:22:08 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1796223] [NEW] package libcups2:i386 2.2.7-1ubuntu2.1 failed to install/upgrade: 依赖关系问题 - 仍未被配置

[程飞天]

Public bug reported:

安装snap商店中的wine时出现了这个错误

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libcups2:i386 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Fri Oct  5 10:29:08 2018
ErrorMessage: 依赖关系问题 - 仍未被配置
InstallationDate: Installed on 2018-09-07 (27 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: ASUSTeK COMPUTER INC. GL552VW
PackageArchitecture: i386
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2e9c0b76-7180-441b-a850-70e9a2dadfff ro quiet splash vt.handoff=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2e9c0b76-7180-441b-a850-70e9a2dadfff ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: cups
Title: package libcups2:i386 2.2.7-1ubuntu2.1 failed to install/upgrade: 依赖关系问题 
- 仍未被配置
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: apport-package bionic i386

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

Title:
  package libcups2:i386 2.2.7-1ubuntu2.1 failed to install/upgrade:
  依赖关系问题 - 仍未被配置

Status in cups package in Ubuntu:
  New

Bug description:
  安装snap商店中的wine时出现了这个错误

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcups2:i386 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Fri Oct  5 10:29:08 2018
  ErrorMessage: 依赖关系问题 - 仍未被配置
  InstallationDate: Installed on 2018-09-07 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  PackageArchitecture: i386
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2e9c0b76-7180-441b-a850-70e9a2dadfff ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2e9c0b76-7180-441b-a850-70e9a2dadfff ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: cups
  Title: package libcups2:i386 2.2.7-1ubuntu2.1 failed to install/upgrade: 
依赖关系问题 - 仍未被配置
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

[TJ]

I suspect the recent Bionic changes have broken the install. At least
I'm seeing the following:

$ sudo apt-get upgrade

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree


Reading state information... 0%

Reading state information... 0%

Reading state information... Done


Calculating upgrade... 0%

Calculating upgrade... 50%

Calculating upgrade... Done

The following packages will be upgraded:
  libc6-armhf-cross libc6-dev-armhf-cross
2 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/2,904 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 405785 files and directories currently installed.)
Preparing to unpack .../libc6-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb ...
Unpacking libc6-dev-armhf-cross (2.27-3ubuntu1cross1.1) over 
(2.27-3ubuntu1cross1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb 
(--unpack):
 unable to open '/usr/arm-linux-gnueabihf/lib/Mcrt1.o.dpkg-new': No such file 
or directory
No apport report written because the error message indicates an issue on the 
local system
Preparing to unpack .../libc6-armhf-cross_2.27-3ubuntu1cross1.1_all.deb ...
Unpacking libc6-armhf-cross (2.27-3ubuntu1cross1.1) over (2.27-3ubuntu1cross1) 
...
dpkg: error processing archive 
/var/cache/apt/archives/libc6-armhf-cross_2.27-3ubuntu1cross1.1_all.deb 
(--unpack):
 unable to open '/usr/arm-linux-gnueabihf/lib/ld-2.27.so.dpkg-new': No such 
file or directory
No apport report written because the error message indicates an issue on the 
local system
Errors were encountered while processing:
 /var/cache/apt/archives/libc6-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb
 /var/cache/apt/archives/libc6-armhf-cross_2.27-3ubuntu1cross1.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in cross-toolchain-base-ports package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Released
Status in cross-toolchain-base source package in Bionic:
  Fix Released
Status in cross-toolchain-base-ports source package in Bionic:
  Fix Released
Status in gcc-7 source package in Bionic:
  Fix Released
Status in gcc-7-cross source package in Bionic:
  Fix Released
Status in gcc-7-cross-ports source package in Bionic:
  Fix Released
Status in gcc-8 source package in Bionic:
  Fix Released
Status in gcc-8-cross source package in Bionic:
  Fix Released
Status in gcc-8-cross-ports source package in Bionic:
  Fix Released
Status in gcc-defaults source package in Bionic:
  Fix Released
Status in gcc-defaults-ports source package in Bionic:
  Fix Released

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the 

[Touch-packages] [Bug 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

[Treviño]

** Description changed:

+ [ Impact ]
+ 
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ [ Test case ]
+ 
+ 1. Open virt-manager
+ 2. Run a virtual machine
+ 3. Click on the toolbar menu that can be opened from the power button
+ 4. The items should be readable and have proper color
+ 
+ [ Regression potential ]
+ 
+ Menu items could not be visible in other menus
+ 
+ ---
+ 
+ ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
- PackageArchitecture: all
- SourcePackage: virt-manager
+ PackageArchitecture: allSourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

** Description changed:

  [ Impact ]
  
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.
  
  [ Test case ]
  
  1. Open virt-manager
  2. Run a virtual machine
  3. Click on the toolbar menu that can be opened from the power button
  4. The items should be readable and have proper color
  
  [ Regression potential ]
  
- Menu items could not be visible in other menus
+ Menu items could not be visible in other dark menus
  
  ---
  
  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: allSourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  [ Impact ]

  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  [ Test case ]

  1. Open virt-manager
  2. Run a virtual machine
  3. Click on the toolbar menu that can be opened from the power button
  4. The items should be readable and have proper color

  [ Regression potential ]

  Menu items could not be visible in other dark menus

  ---

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: allSourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

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

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

[Touch-packages] [Bug 1782038] Re: Window buttons are small in a maximized Chromium window

[Treviño]

** Description changed:

+ [ Impact ]
+ 
+ In maximized google-chrome / chromium window buttons for close,
+ minimize, and restore buttons should be normal-sized, but instead appear
+ small.
+ 
+ [ Test case ]
+ 
+ 1. Use the Ambiance or Radiance themes.
+ 2. Launch a Chromium or Google Chrome window.
+ 3. Ensure that in chrome settings, the "Use system borders" option is 
unchecked
+ 4. Maximize.
+ 5. Window buttons should have normal size.
+ 
+ [ Regression potential ]
+ 
+ Other windows buttons could loose the padding used for being closed.
+ 
+ ---
+ 
  Repro:
  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium window.
  3. Maximize.
  
  The window close, minimize, and restore buttons should be normal-sized,
  but instead appear small.
  
  This is because the buttons have a padding of 9px on the top and bottom,
  causing Chromium to think they're taller than they really are, so it
  downsizes them to fit the smaller headerbar on the maximized window.
  
  The attached patch removes the padding.  There are no changes in
  behavior in apps other than Chromium.

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

Title:
  Window buttons are small in a maximized Chromium window

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  In maximized google-chrome / chromium window buttons for close,
  minimize, and restore buttons should be normal-sized, but instead
  appear small.

  [ Test case ]

  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium or Google Chrome window.
  3. Ensure that in chrome settings, the "Use system borders" option is 
unchecked
  4. Maximize.
  5. Window buttons should have normal size.

  [ Regression potential ]

  Other windows buttons could loose the padding used for being closed.

  ---

  Repro:
  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium window.
  3. Maximize.

  The window close, minimize, and restore buttons should be normal-
  sized, but instead appear small.

  This is because the buttons have a padding of 9px on the top and
  bottom, causing Chromium to think they're taller than they really are,
  so it downsizes them to fit the smaller headerbar on the maximized
  window.

  The attached patch removes the padding.  There are no changes in
  behavior in apps other than Chromium.

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

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

[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

[Treviño]

** Description changed:

+ [ Impact ]
+ 
+ Running an application with Radiance theme shows an error
+ 
+ [ Test case ]
+ 
+ 1. Run an application (evince) in terminal using Radiance:
+GTK_THEME=Radiance evince
+ 2. No error should be spotted regarding a missing .css file
+ 
+ [ Regression potential ]
+ 
+ None
+ 
+ ---
+ 
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line
  
  @import url("apps/gnome-builder.css");
  
  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when running
  various applications (e.g. evince):
  
  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error: gtk-
  main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file
  or directory
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
- PackageArchitecture: all
- SourcePackage: ubuntu-themes
+ PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => 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/1773045

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

  Running an application with Radiance theme shows an error

  [ Test case ]

  1. Run an application (evince) in terminal using Radiance:
 GTK_THEME=Radiance evince
  2. No error should be spotted regarding a missing .css file

  [ Regression potential ]

  None

  ---

  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

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

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

[Touch-packages] [Bug 1781736] Re: Buttons aren't properly themed in Radiance theme under HiDPI

[Treviño]

** Description changed:

+ [ Impact ]
+ 
+ Buttons in radiance aren't properly themed in highdpi mode
+ 
+ [ Test case ]
+ 1. Run a gtk app with CSD (i.e.) gnome-disks with GDK_SCALE=2 and 
GTK_THEME=Radiance
+GDK_SCALE=2 GTK_THEME=Radiance gnome-disks
+ 2. Buttons should be properly themed and with high-quality borders in both 
normal and
+focused state.
+ 
+ [ Regression potential ]
+ 
+ No proper borders are painted on buttons under Radiance
+ 
+ --
+ 
  There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
  widgets.css that causes focused buttons to be drawn incorrectly in the
  radiance theme. The following change should be made to the file to fix
  the incorrect assets link:
  
  118c118
  <  url("assets/button-focused.png@2"));
  ---
  >  url("assets/button-focu...@2.png"));
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified: 
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
  ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
  Uname: Linux 4.15.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jul 14 15:41:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-23 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
- PackageArchitecture: all
- SourcePackage: ubuntu-themes
+ PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Buttons aren't properly themed in Radiance theme under HiDPI

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

Bug description:
  [ Impact ]

  Buttons in radiance aren't properly themed in highdpi mode

  [ Test case ]
  1. Run a gtk app with CSD (i.e.) gnome-disks with GDK_SCALE=2 and 
GTK_THEME=Radiance
 GDK_SCALE=2 GTK_THEME=Radiance gnome-disks
  2. Buttons should be properly themed and with high-quality borders in both 
normal and
 focused state.

  [ Regression potential ]

  No proper borders are painted on buttons under Radiance

  --

  There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
  widgets.css that causes focused buttons to be drawn incorrectly in the
  radiance theme. The following change should be made to the file to fix
  the incorrect assets link:

  118c118
  <  url("assets/button-focused.png@2"));
  ---
  >  url("assets/button-focu...@2.png"));

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified: 
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
  ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
  Uname: Linux 4.15.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jul 14 15:41:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-23 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+subscriptions

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

[Touch-packages] [Bug 1743373] Re: Combobox arrow and color are inverted

[Treviño]

** Description changed:

+ [ Test case ]
+ 
+ Comobobox lists extenders use invalid arrows
+  1. Both at the top and at the bottom, the arrow (triangle) points downwards.
+  2. Colors of sensitive and insensitive arrows are swapped.
+ 
+ [ Test case ]
+ 
+  1. Open gnome-terminal, in menu goes to:
+ Edit -> Profile Preferences -> Compatibility -> Encoding
+  2. The arrow at the top should point upwards
+  3. Tha arrow at the bottom should point downwards
+  4. Arrows should be visible only when there's actually something
+ to scroll up or down.
+ 
+ [ Regression potential ]
+ 
+ Arrows aren't shown as expected in menus or combo-box
+ 
+ ---
+ 
  Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit
  -> Profile Preferences -> Compatibility -> Encoding)
  
  Notice two bugs:
  
  1. Both at the top and at the bottom, the arrow (triangle) points
  downwards.
  
  Expected: At the top, the arrow should point upwards.
  
  2. Colors of sensitive and insensitive arrows are swapped. The arrow is
  black if you cannot scroll in that direction, gray if hovering starts to
  scroll.
  
  Expected: It should be black if you can scroll in that direction by
  hovering, and gray if you cannot.
  
  Adwaita doesn't suffer from either of these issues.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 17.10
+ ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan 15 13:44:49 2018
  InstallationDate: Installed on 2016-11-09 (431 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
- PackageArchitecture: all
- SourcePackage: ubuntu-themes
+ PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago)

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

Title:
  Combobox arrow and color are inverted

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Test case ]

  Comobobox lists extenders use invalid arrows
   1. Both at the top and at the bottom, the arrow (triangle) points downwards.
   2. Colors of sensitive and insensitive arrows are swapped.

  [ Test case ]

   1. Open gnome-terminal, in menu goes to:
  Edit -> Profile Preferences -> Compatibility -> Encoding
   2. The arrow at the top should point upwards
   3. Tha arrow at the bottom should point downwards
   4. Arrows should be visible only when there's actually something
  to scroll up or down.

  [ Regression potential ]

  Arrows aren't shown as expected in menus or combo-box

  ---

  Open a combobox with plenty of entries. (Example: gnome-terminal ->
  Edit -> Profile Preferences -> Compatibility -> Encoding)

  Notice two bugs:

  1. Both at the top and at the bottom, the arrow (triangle) points
  downwards.

  Expected: At the top, the arrow should point upwards.

  2. Colors of sensitive and insensitive arrows are swapped. The arrow
  is black if you cannot scroll in that direction, gray if hovering
  starts to scroll.

  Expected: It should be black if you can scroll in that direction by
  hovering, and gray if you cannot.

  Adwaita doesn't suffer from either of these issues.

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan 15 13:44:49 2018
  InstallationDate: Installed on 2016-11-09 (431 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: allSourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago)

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

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

[Touch-packages] [Bug 1781736] Re: Buttons aren't properly themed in Radiance theme under HiDPI

[Treviño]

** Summary changed:

- Typo in assets link for focused buttons in Radiance theme
+ Buttons aren't properly themed in Radiance theme under HiDPI

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

Title:
  Buttons aren't properly themed in Radiance theme under HiDPI

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

Bug description:
  There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
  widgets.css that causes focused buttons to be drawn incorrectly in the
  radiance theme. The following change should be made to the file to fix
  the incorrect assets link:

  118c118
  <  url("assets/button-focused.png@2"));
  ---
  >  url("assets/button-focu...@2.png"));

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified: 
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
  ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
  Uname: Linux 4.15.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jul 14 15:41:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-23 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+subscriptions

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

[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

[Treviño]

** No longer affects: ubuntu-themes

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

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

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

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

[Touch-packages] [Bug 1761684] Re: Regression in lists like gnome-boxes

[Treviño]

** Description changed:

+ [ Impact ]
+ 
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.
+ 
+ [ Test case ]
+ 
+ 1. Run gnome-boxes (install the same package if not available)
+ 2. Click on "New" box button
+ 3. The first page should show a list of available machines, content should be
+readable.
+ 
+ [ Regression potential ]
+ 
+ Other gnome-boxes lists are not properly themed

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

  [ Test case ]

  1. Run gnome-boxes (install the same package if not available)
  2. Click on "New" box button
  3. The first page should show a list of available machines, content should be
 readable.

  [ Regression potential ]

  Other gnome-boxes lists are not properly themed

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

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

[Touch-packages] [Bug 1739931] Re: Separator lines in shell popup menus are too faint to see

[Treviño]

** Description changed:

+ [ Impact ]
+ 
+ Separators in gnome-shell menuitems are not visible
+ 
+ [ Test case ]
+ 
+ 1. Right - Click on a dock icon
+ 2. Separators between menu items should be visible
+ 
+ [ Regression potential ]
+ 
+ Nothing known
+ 
+ 
+ 
  when I click on the dock icons, some of the lines in the popup menus are
  blank and some of them appear to be incorrect. see top left of attached
  screenshot.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 17.10
+ ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 23 22:24:40 2017
  InstallationDate: Installed on 2016-08-18 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: nautilus
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bashSourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Separator lines in shell popup menus are too faint to see

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  [ Impact ]

  Separators in gnome-shell menuitems are not visible

  [ Test case ]

  1. Right - Click on a dock icon
  2. Separators between menu items should be visible

  [ Regression potential ]

  Nothing known

  

  when I click on the dock icons, some of the lines in the popup menus
  are blank and some of them appear to be incorrect. see top left of
  attached screenshot.

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 23 22:24:40 2017
  InstallationDate: Installed on 2016-08-18 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1795635] Re: Drop transitional dummy packages for qtquick2 and qttest

[Khurshid Alam]

** Branch linked: lp:~khurshid-alam/unity-api/fix-build-cosmic

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

Title:
  Drop transitional dummy packages for qtquick2 and qttest

Status in unity-api package in Ubuntu:
  Triaged

Bug description:
  qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just
  transitional dummy packages. Instead use qml-module-qtquick2 and qml-
  module-qttest

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

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

[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons

[Treviño]

** Description changed:

  Impact
  --
  The suggestion action button does not have correct text styling when the 
action button is "insensitive" (greyed out). This makes the text basically 
invisible since it has the same dark grey color for both the foreground text 
and the background.
- 
  
  Test Case 1
  ---
  1. Open the file browser.
  2. Open the ☰ menu and select New Folder.
  
  What happens:
  1. In the New Folder dialog, the top right button has invisible text. 
Screenshot attached.
  
  What should happen:
  It should show the word Create but greyed out.
  
  Test Case 2
  ---
  1. Open the gedit text editor.
  2. Open the ☰ menu and select Save As.
  3. In the Name field, delete all the text to make the field empty.
  
  What happens:
  The word Save in the top right button becomes invisible.
  
+ Regression Potential
+ 
+ Color for elements other than the label of suggested actions is wrong
+ 
  Other Info
  --
  Ubuntu 18.04.1 LTS
  light-themes 16.10+18.04.20180421.1-0ubuntu1
  Ambiance theme
  libgtk-3-0 3.22.30-1ubuntu1

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

Title:
  Invisible text in insenstitive suggested action buttons

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  The suggestion action button does not have correct text styling when the 
action button is "insensitive" (greyed out). This makes the text basically 
invisible since it has the same dark grey color for both the foreground text 
and the background.

  Test Case 1
  ---
  1. Open the file browser.
  2. Open the ☰ menu and select New Folder.

  What happens:
  1. In the New Folder dialog, the top right button has invisible text. 
Screenshot attached.

  What should happen:
  It should show the word Create but greyed out.

  Test Case 2
  ---
  1. Open the gedit text editor.
  2. Open the ☰ menu and select Save As.
  3. In the Name field, delete all the text to make the field empty.

  What happens:
  The word Save in the top right button becomes invisible.

  Regression Potential
  
  Color for elements other than the label of suggested actions is wrong

  Other Info
  --
  Ubuntu 18.04.1 LTS
  light-themes 16.10+18.04.20180421.1-0ubuntu1
  Ambiance theme
  libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 382938] Re: ufw should be enabled by default

[Santeri Kannisto]

Jeremy,

I believe that without a graphical tool it is even more critical to have
ufw enabled and running by default. Anyway, no worries about my patch
and bug reports. I forked and patched ufw and have the package available
in my PAA at
https://launchpad.net/~santerikannisto/+archive/ubuntu/desktop

At this point I don't see any point or need in implementing a GUI config
tool for ufw by myself nor participating in such effort. For my needs
it's enough that ufw is enabled and running out-of-the-box blocking by
default all incoming traffic with logging switched off.

Cheers,

Santeri

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

Title:
  ufw should be enabled by default

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: ufw

  ufw should be enabled by default in Ubuntu.

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

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

[Touch-packages] [Bug 1796191] Re: package wswiss 20161207-4 failed to install/upgrade: installed wswiss package post-removal script subprocess returned error exit status 139

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

Title:
  package wswiss 20161207-4 failed to install/upgrade: installed wswiss
  package post-removal script subprocess returned error exit status 139

Status in igerman98 package in Ubuntu:
  New

Bug description:
  I am just have installed clean 18.04.1
  I have logged in first time and do nothing and got this crash report

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: wswiss 20161207-4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Oct  5 00:03:56 2018
  DuplicateSignature:
   package:wswiss:20161207-4
   Removing wswiss (20161207-4) ...
   Segmentation fault (core dumped)
   dpkg: error processing package wswiss (--remove):
installed wswiss package post-removal script subprocess returned error exit 
status 139
  ErrorMessage: installed wswiss package post-removal script subprocess 
returned error exit status 139
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: igerman98
  Title: package wswiss 20161207-4 failed to install/upgrade: installed wswiss 
package post-removal script subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1796193] [NEW] unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Paul Larson]

Public bug reported:

I'm trying to do some automated testing that involved upgrading a system
from xenial to bionic, so I need it to not ask for user input.

Before running do-release-upgrade, the system got a fresh dist-upgrade
and reboot.

To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

Processing triggers for libc-bin (2.27-3ubuntu1) ...

/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be
opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or
directory

/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be
opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
directory

Setting up apt (1.6.3ubuntu0.1) ...

Installing new version of config file /etc/apt/apt.conf.d/01autoremove
...


Configuration file '/etc/cron.daily/apt-compat'

 ==> Deleted (by you or by a script) since installation.

 ==> Package distributor has shipped an updated version.

   What would you like to do about it ?  Your options are:

Y or I  : install the package maintainer's version

N or O  : keep your currently-installed version

  D : show the differences between the versions

  Z : start a shell to examine the situation

 The default action is to keep your current version.

Comparing the sha1 of apt-compat before the upgrade to another xenial
system that has been unmodified, they are the same:

In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796191] [NEW] package wswiss 20161207-4 failed to install/upgrade: installed wswiss package post-removal script subprocess returned error exit status 139

[Daniil Troshkov]

Public bug reported:

I am just have installed clean 18.04.1
I have logged in first time and do nothing and got this crash report

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: wswiss 20161207-4
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Fri Oct  5 00:03:56 2018
DuplicateSignature:
 package:wswiss:20161207-4
 Removing wswiss (20161207-4) ...
 Segmentation fault (core dumped)
 dpkg: error processing package wswiss (--remove):
  installed wswiss package post-removal script subprocess returned error exit 
status 139
ErrorMessage: installed wswiss package post-removal script subprocess returned 
error exit status 139
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: igerman98
Title: package wswiss 20161207-4 failed to install/upgrade: installed wswiss 
package post-removal script subprocess returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package wswiss 20161207-4 failed to install/upgrade: installed wswiss
  package post-removal script subprocess returned error exit status 139

Status in igerman98 package in Ubuntu:
  New

Bug description:
  I am just have installed clean 18.04.1
  I have logged in first time and do nothing and got this crash report

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: wswiss 20161207-4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Oct  5 00:03:56 2018
  DuplicateSignature:
   package:wswiss:20161207-4
   Removing wswiss (20161207-4) ...
   Segmentation fault (core dumped)
   dpkg: error processing package wswiss (--remove):
installed wswiss package post-removal script subprocess returned error exit 
status 139
  ErrorMessage: installed wswiss package post-removal script subprocess 
returned error exit status 139
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: igerman98
  Title: package wswiss 20161207-4 failed to install/upgrade: installed wswiss 
package post-removal script subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[Timo Aaltonen]

** Package changed: xserver-xorg-video-intel (Ubuntu) => mesa (Ubuntu)

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Touch-packages] [Bug 1794033] [NEW] i965: Failed to submit batchbuffer: Bad address

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20171229-1
  Candidate: 2:2.99.917+git20171229-1
ubuntu: 18.04 LTS bionic
gnome: 3.28.2
gdm3:
  Installed: 3.28.2-0ubuntu1.4
  Candidate: 3.28.2-0ubuntu1.4
os type: 64 bit
kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
mesa-va-drivers:
  Installed: 18.0.5-0ubuntu0~18.04.1
  Candidate: 18.0.5-0ubuntu0~18.04.1

from syslog:

Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
 - but 
(followed by pages upon pages of applications within gnome failing.)

nothing in kern.log around that time.

Singular gnome crash, taking down all applications running within it.
Not yet reproduced. gdm successfully started a new session afterwards.
Was definitely in a palermoon session on some website or other.

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

** Affects: xserver-xorg-video-intel (Fedora)
 Importance: Unknown
 Status: Unknown


** Tags: bionic
-- 
 i965: Failed to submit batchbuffer: Bad address
https://bugs.launchpad.net/bugs/1794033
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa 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 1796180] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This is nearly identical to bug #1795678, but I note that errno 2 is
  returned, not 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1638 F pulseaudio
emount 2667 F pulseaudio
  Date: Thu Oct  4 16:20:25 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2017-11-15 (322 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ad47f34e-3e20-4f5d-9f96-d5ecbad7848f ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1796180] [NEW] package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[ELDRIDGE MOUNT]

Public bug reported:

This is nearly identical to bug #1795678, but I note that errno 2 is
returned, not 1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1638 F pulseaudio
  emount 2667 F pulseaudio
Date: Thu Oct  4 16:20:25 2018
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
InstallationDate: Installed on 2017-11-15 (322 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ad47f34e-3e20-4f5d-9f96-d5ecbad7848f ro quiet splash 
nouveau.modeset=0 vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.4
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This is nearly identical to bug #1795678, but I note that errno 2 is
  returned, not 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1638 F pulseaudio
emount 2667 F pulseaudio
  Date: Thu Oct  4 16:20:25 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2017-11-15 (322 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ad47f34e-3e20-4f5d-9f96-d5ecbad7848f ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

[Treviño]

It still seem to crash in my kvm installation:

ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy 
xserver-xorg-video-fbdev
xserver-xorg-video-fbdev:
  Installed: 1:0.5.0-1ubuntu1
  Candidate: 1:0.5.0-1ubuntu1
  Version table:
 *** 1:0.5.0-1ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

See attached journalctl that includes the Xorg.log

It's also weird that using `std` driver works in live, while not once
installed.

** Attachment added: "kvm-journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+attachment/5197280/+files/kvm-journalctl.log

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Touch-packages] [Bug 1796172] Re: systemd-journald crashed with SIGABRT in fsync()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  error message popped up during a file copy shortly after a fresh
  installation

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Thu Oct  4 19:57:08 2018
  ExecutablePath: /lib/systemd/systemd-journald
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 17ef:6019 Lenovo 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=38078717-9be6-42c5-88a8-fbec911fe53c ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   fsync (fd=98) at ../sysdeps/unix/sysv/linux/fsync.c:27
   ?? () from /lib/systemd/libsystemd-shared-239.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-239.so
   ?? () from /lib/systemd/libsystemd-shared-239.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-239.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in fsync()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/30/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-SLI Premium ACPI BIOS Revision 1005
  dmi.board.name: A8N-SLI Premium
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIPremiumACPIBIOSRevision1005:bd05/30/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIPremium:rvr1.02: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/systemd/+bug/1796172/+subscriptions

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

[Touch-packages] [Bug 1791484] Re: [FFe] Update tracker and tracker-miners to 2.1.4

[Jeremy Bicha]

We have removed the new tracker version from cosmic-proposed because of
bug 1793550.

** Changed in: tracker-miners (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: tracker (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  [FFe] Update tracker and tracker-miners to 2.1.4

Status in tracker package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid

Bug description:
  To go along with the rest of GNOME 3.30
  Both tracker and tracker-miners 2.1.4 will be synced from Debian. 

  tracker is not installed by default on any Ubuntu Flavours, but does
  provide an important part of the GNOME-Shell experience.

  These releases bring lots of fixes and a few new features.

  Tracker NEW in 2.1.4 - 2018-09-04
  =

* Fix build with format-security flag

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Fix resource refcounting issues in database. Reset is advised.
* Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights
* Fix superfluous ontology checks on second tracker-store run
* Use more SPARQL1.1 correct syntax.
* Allow use of domain rules outside prefix
* Compatibility fixes with C++

  Translations: gl, id, ko

  NEW in 2.1.2 - 2018-08-15
  =

* libtracker-sparql: Delete TrackerResource elements one by one
* libtracker-sparql: Fix compilation with C++
* build: Fixes for FreeBSD
* build: Fixes on meson

  Translations: cs, el, fr, fur, hu, sl, tr, zh_TW

  NEW in 2.1.1 - 2018-08-01
  =

* libtracker-direct: Plug leaks
* libtracker-sparql-backend: Fix fallback from direct to bus
  connection for queries.

  Translations: es, lt, ro

  NEW in 2.1.0 - 2018-07.22
  =

* Brown paper bag release
* All features from unreleased 2.0.5 apply
* One feature was missed: TrackerResource is now able to output
  JSON-LD. This is a new API call, so a minor bump should happen
  as per Semantic Versioning.

From 2.0.5 NEWS:
* build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
* build: Various meson build fixes
* tests: Many fixes to functional tests
* libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
* libtracker-direct: Majorly rewritten
* tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  Tracker-miners NEW in 2.1.4 - 2018-09-04
  =

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Unbreak watch on domain ontology owner. Fixes miners spuriously
  exiting.

  NEW in 2.1.2 - 2018-08-30
  =

* Allow use of domain rules outside prefix
* Add core-as-subproject as explicit meson option
* Ensure utf8ness in TrackerResource helpers
* Fix multiple cardinality issues in different extractors/properties
* Other minor SPARQL correctness fixes

  Translations: gl, id, ko

  NEW in 2.1.1 - 2018-08-15
  =

* tracker-miner-fs: Ignore mercurial repositories
* build: Fix build with -Werror=format-security
* tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors
* tracker-extract: Do not add named destinations to PDF TOCs
* tracker-extract: Ignore XMP image metadata on PDFs
* tracker-extract: Fix ISO 8601 date string generation on gstreamer 
extractor

  Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW

  NEW in 2.1.0 - 2018-07-23
  =

* tests: Many updates and fixes to functional tests
* tracker-extract: Better infrastructure for tests, based on JSON-LD
* tracker-miner-fs: Restart tracker extract from the right domain
* tracker-extract: Persistently avoid files that trigger recoverable
  errors, to avoid log spamming on restarts.

  Translations: de, es, it, pl, pt_BR, ro, sv

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

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

[Touch-packages] [Bug 1793550] Re: tracker 2.1.4+ library needs ontology files from tracker binary package

[Jeremy Bicha]

We just ran out of time to coordinate everything to fix this issue.

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

Title:
  tracker 2.1.4+ library needs ontology files from tracker binary
  package

Status in nautilus package in Ubuntu:
  Invalid
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  See the Debian bug for more details.

  The tracker 2.1.4 libraries will exit with an error, basically
  crashing the app if they can't find /usr/share/tracker/domain-
  ontologies/default.rule which is currently provided by the tracker
  binary package.

  The most obvious consequence is this means that nautilus won't run if
  tracker is not installed. But the tracker binary package isn't yet in
  main. The MIR is LP: #1770877

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

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

[Touch-packages] [Bug 1793550] Re: tracker 2.1.4+ library needs ontology files from tracker binary package

[Jeremy Bicha]

Let me give an update on the situation. For more details, see the Debian
bug and its duplicate.

Tim split tracker-common out of tracker and pushed that change to the
Debian packaging. This fixed this issue, but a key Debian maintainer for
this package believed that this issue should be worked out upstream
instead. I opened an upstream bug, but there hasn't been any patch
proposed yet.

nautilus may end up needing a hard dependency on tracker because the
idea suggested upstream which may work for brasero may not work for
nautilus. Ubuntu can't add that dependency yet because the tracker-
miners MIR isn't finished yet.

Finally, the new tracker version hasn't gotten a lot of testing in
Ubuntu yet and it's not necessary for anything else in Ubuntu.
Therefore, we made the decision to remove tracker and tracker-miner from
cosmic-proposed today. Hopefully, everything will be in place for Daring
Dragon.

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

Title:
  tracker 2.1.4+ library needs ontology files from tracker binary
  package

Status in nautilus package in Ubuntu:
  Invalid
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  See the Debian bug for more details.

  The tracker 2.1.4 libraries will exit with an error, basically
  crashing the app if they can't find /usr/share/tracker/domain-
  ontologies/default.rule which is currently provided by the tracker
  binary package.

  The most obvious consequence is this means that nautilus won't run if
  tracker is not installed. But the tracker binary package isn't yet in
  main. The MIR is LP: #1770877

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

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

[Touch-packages] [Bug 1793550] Re: tracker 2.1.4+ library needs ontology files from tracker binary package

[Jeremy Bicha]

** Summary changed:

- tracker library needs ontology files from tracker binary package
+ tracker 2.1.4+ library needs ontology files from tracker binary package

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

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

Title:
  tracker 2.1.4+ library needs ontology files from tracker binary
  package

Status in nautilus package in Ubuntu:
  Invalid
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  See the Debian bug for more details.

  The tracker 2.1.4 libraries will exit with an error, basically
  crashing the app if they can't find /usr/share/tracker/domain-
  ontologies/default.rule which is currently provided by the tracker
  binary package.

  The most obvious consequence is this means that nautilus won't run if
  tracker is not installed. But the tracker binary package isn't yet in
  main. The MIR is LP: #1770877

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

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

[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

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

Title:
  Invisible text in insenstitive suggested action buttons

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  The suggestion action button does not have correct text styling when the 
action button is "insensitive" (greyed out). This makes the text basically 
invisible since it has the same dark grey color for both the foreground text 
and the background.

  
  Test Case 1
  ---
  1. Open the file browser.
  2. Open the ☰ menu and select New Folder.

  What happens:
  1. In the New Folder dialog, the top right button has invisible text. 
Screenshot attached.

  What should happen:
  It should show the word Create but greyed out.

  Test Case 2
  ---
  1. Open the gedit text editor.
  2. Open the ☰ menu and select Save As.
  3. In the Name field, delete all the text to make the field empty.

  What happens:
  The word Save in the top right button becomes invisible.

  Other Info
  --
  Ubuntu 18.04.1 LTS
  light-themes 16.10+18.04.20180421.1-0ubuntu1
  Ambiance theme
  libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.10

---
apparmor (2.10.95-0ubuntu2.10) xenial-security; urgency=medium

  * lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:23:46 +

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

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

Title:
  Debian/Ubuntu AppArmor policy gaps in evince

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in evince source package in Trusty:
  In Progress
Status in apparmor source package in Xenial:
  Fix Released
Status in evince source package in Xenial:
  In Progress
Status in apparmor source package in Bionic:
  Fix Released
Status in evince source package in Bionic:
  In Progress
Status in apparmor source package in Cosmic:
  Fix Released
Status in evince source package in Cosmic:
  Fix Released

Bug description:
  [Note on coordination: I'm reporting this as a security bug to both Ubuntu
  (because Ubuntu is where this policy originally comes from, and Ubuntu is also
  where AppArmor is most relevant) and Debian (because the AppArmor policy has
  been merged into Debian's version of the package). It isn't clear to me who
  really counts as upstream here...]

  Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
  things, restricts evince-thumbnailer. The Ubuntu security team seems to
  incorrectly believe that this policy provides meaningful security isolation:

  https://twitter.com/alex_murray/status/1032780425834446849
  https://twitter.com/alex_murray/status/1032796879640190976

  This AppArmor policy seems to be designed to permit everything that
  evince-thumbnailer might need; however, it does not seem to be designed to
  establish a consistent security boundary around evince-thumbnailer.

  
  For example, read+write access to almost the entire home directory is granted:

  
  /usr/bin/evince-thumbnailer {
  [...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/**  rw,
  }

  As the comment notes, a couple files are excluded to prevent you from just
  overwriting well-known executable scripts in the user's home directory, like
  ~/.bashrc:

  [...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,

# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
  [...]

  Verification:

  user@ubuntu-18-04-vm:~$ cat preload2.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
  printf("success\n");
} else {
  perror("open .bashrc");
}
exit(0);
  }
  user@ubuntu-18-04-vm:~$ sudo gcc -shared -o 
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
  user@ubuntu-18-04-vm:~$ 
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
  constructor running from evince-thumbnailer
  open .bashrc: Permission denied
  user@ubuntu-18-04-vm:~$ dmesg|tail -n1
  [ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED" 
operation="open" profile="/usr/bin/evince-thumbnailer" 
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000

  
  But of course blacklists are brittle and often trivially bypassable. For
  example, did you know that it is possible to override the system's 
thumbnailers
  by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
  command lines that will be executed by nautilus. To demonstrate that it is
  possible to create .thumbnailer files from evince-thumbnailer:

  user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
  ls: cannot access '.local/share/thumbnailers/': No such file or directory
  user@ubuntu-18-04-vm:~$ cat preload3.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
  err(1, "mkdir");
FILE *f = 

[Touch-packages] [Bug 1794848] Re: private-files-strict and user-files abstractions should also limit access to directories

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.10

---
apparmor (2.10.95-0ubuntu2.10) xenial-security; urgency=medium

  * lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:23:46 +

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

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

Title:
  private-files-strict and user-files  abstractions should also limit
  access to directories

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor source package in Cosmic:
  Fix Released

Bug description:
  This is to track the private-files-strict and user-files portion of
  https://bugs.launchpad.net/apparmor/+bug/1794820

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Łukasz Zemczak]

Hello Daniel, or anyone else affected,

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

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

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

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

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

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     

[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.12-4ubuntu5.1

---
apparmor (2.12-4ubuntu5.1) bionic-security; urgency=medium

  * lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:20:54 +

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

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

Title:
  Debian/Ubuntu AppArmor policy gaps in evince

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in evince source package in Trusty:
  In Progress
Status in apparmor source package in Xenial:
  Fix Committed
Status in evince source package in Xenial:
  In Progress
Status in apparmor source package in Bionic:
  Fix Released
Status in evince source package in Bionic:
  In Progress
Status in apparmor source package in Cosmic:
  Fix Released
Status in evince source package in Cosmic:
  Fix Released

Bug description:
  [Note on coordination: I'm reporting this as a security bug to both Ubuntu
  (because Ubuntu is where this policy originally comes from, and Ubuntu is also
  where AppArmor is most relevant) and Debian (because the AppArmor policy has
  been merged into Debian's version of the package). It isn't clear to me who
  really counts as upstream here...]

  Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
  things, restricts evince-thumbnailer. The Ubuntu security team seems to
  incorrectly believe that this policy provides meaningful security isolation:

  https://twitter.com/alex_murray/status/1032780425834446849
  https://twitter.com/alex_murray/status/1032796879640190976

  This AppArmor policy seems to be designed to permit everything that
  evince-thumbnailer might need; however, it does not seem to be designed to
  establish a consistent security boundary around evince-thumbnailer.

  
  For example, read+write access to almost the entire home directory is granted:

  
  /usr/bin/evince-thumbnailer {
  [...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/**  rw,
  }

  As the comment notes, a couple files are excluded to prevent you from just
  overwriting well-known executable scripts in the user's home directory, like
  ~/.bashrc:

  [...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,

# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
  [...]

  Verification:

  user@ubuntu-18-04-vm:~$ cat preload2.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
  printf("success\n");
} else {
  perror("open .bashrc");
}
exit(0);
  }
  user@ubuntu-18-04-vm:~$ sudo gcc -shared -o 
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
  user@ubuntu-18-04-vm:~$ 
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
  constructor running from evince-thumbnailer
  open .bashrc: Permission denied
  user@ubuntu-18-04-vm:~$ dmesg|tail -n1
  [ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED" 
operation="open" profile="/usr/bin/evince-thumbnailer" 
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000

  
  But of course blacklists are brittle and often trivially bypassable. For
  example, did you know that it is possible to override the system's 
thumbnailers
  by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
  command lines that will be executed by nautilus. To demonstrate that it is
  possible to create .thumbnailer files from evince-thumbnailer:

  user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
  ls: cannot access '.local/share/thumbnailers/': No such file or directory
  user@ubuntu-18-04-vm:~$ cat preload3.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
  err(1, "mkdir");
FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer", 

[Touch-packages] [Bug 1794848] Re: private-files-strict and user-files abstractions should also limit access to directories

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.12-4ubuntu5.1

---
apparmor (2.12-4ubuntu5.1) bionic-security; urgency=medium

  * lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:20:54 +

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

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

Title:
  private-files-strict and user-files  abstractions should also limit
  access to directories

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor source package in Cosmic:
  Fix Released

Bug description:
  This is to track the private-files-strict and user-files portion of
  https://bugs.launchpad.net/apparmor/+bug/1794820

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

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

[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.6~14.04.4

---
apparmor (2.10.95-0ubuntu2.6~14.04.4) trusty-security; urgency=medium

  * {,14.04-}lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:38:50 +

** Changed in: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929

Title:
  Debian/Ubuntu AppArmor policy gaps in evince

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in evince source package in Trusty:
  In Progress
Status in apparmor source package in Xenial:
  Fix Committed
Status in evince source package in Xenial:
  In Progress
Status in apparmor source package in Bionic:
  Fix Committed
Status in evince source package in Bionic:
  In Progress
Status in apparmor source package in Cosmic:
  Fix Released
Status in evince source package in Cosmic:
  Fix Released

Bug description:
  [Note on coordination: I'm reporting this as a security bug to both Ubuntu
  (because Ubuntu is where this policy originally comes from, and Ubuntu is also
  where AppArmor is most relevant) and Debian (because the AppArmor policy has
  been merged into Debian's version of the package). It isn't clear to me who
  really counts as upstream here...]

  Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
  things, restricts evince-thumbnailer. The Ubuntu security team seems to
  incorrectly believe that this policy provides meaningful security isolation:

  https://twitter.com/alex_murray/status/1032780425834446849
  https://twitter.com/alex_murray/status/1032796879640190976

  This AppArmor policy seems to be designed to permit everything that
  evince-thumbnailer might need; however, it does not seem to be designed to
  establish a consistent security boundary around evince-thumbnailer.

  
  For example, read+write access to almost the entire home directory is granted:

  
  /usr/bin/evince-thumbnailer {
  [...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/**  rw,
  }

  As the comment notes, a couple files are excluded to prevent you from just
  overwriting well-known executable scripts in the user's home directory, like
  ~/.bashrc:

  [...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,

# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
  [...]

  Verification:

  user@ubuntu-18-04-vm:~$ cat preload2.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
  printf("success\n");
} else {
  perror("open .bashrc");
}
exit(0);
  }
  user@ubuntu-18-04-vm:~$ sudo gcc -shared -o 
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
  user@ubuntu-18-04-vm:~$ 
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
  constructor running from evince-thumbnailer
  open .bashrc: Permission denied
  user@ubuntu-18-04-vm:~$ dmesg|tail -n1
  [ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED" 
operation="open" profile="/usr/bin/evince-thumbnailer" 
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000

  
  But of course blacklists are brittle and often trivially bypassable. For
  example, did you know that it is possible to override the system's 
thumbnailers
  by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
  command lines that will be executed by nautilus. To demonstrate that it is
  possible to create .thumbnailer files from evince-thumbnailer:

  user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
  ls: cannot access '.local/share/thumbnailers/': No such file or directory
  user@ubuntu-18-04-vm:~$ cat preload3.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  __attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
  err(1, "mkdir");
FILE *f = 

[Touch-packages] [Bug 1794848] Re: private-files-strict and user-files abstractions should also limit access to directories

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.6~14.04.4

---
apparmor (2.10.95-0ubuntu2.6~14.04.4) trusty-security; urgency=medium

  * {,14.04-}lp1788929+1794848.patch:
- disallow writes to thumbnailer dir (LP: #1788929)
- disallow access to the dirs of private files (LP: #1794848)

 -- Jamie Strandboge   Thu, 27 Sep 2018 18:38:50 +

** Changed in: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1794848

Title:
  private-files-strict and user-files  abstractions should also limit
  access to directories

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Committed
Status in apparmor source package in Cosmic:
  Fix Released

Bug description:
  This is to track the private-files-strict and user-files portion of
  https://bugs.launchpad.net/apparmor/+bug/1794820

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

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

[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Invisible text in insenstitive suggested action buttons

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  The suggestion action button does not have correct text styling when the 
action button is "insensitive" (greyed out). This makes the text basically 
invisible since it has the same dark grey color for both the foreground text 
and the background.

  
  Test Case 1
  ---
  1. Open the file browser.
  2. Open the ☰ menu and select New Folder.

  What happens:
  1. In the New Folder dialog, the top right button has invisible text. 
Screenshot attached.

  What should happen:
  It should show the word Create but greyed out.

  Test Case 2
  ---
  1. Open the gedit text editor.
  2. Open the ☰ menu and select Save As.
  3. In the Name field, delete all the text to make the field empty.

  What happens:
  The word Save in the top right button becomes invisible.

  Other Info
  --
  Ubuntu 18.04.1 LTS
  light-themes 16.10+18.04.20180421.1-0ubuntu1
  Ambiance theme
  libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons

[Treviño]

** No longer affects: ubuntu-themes

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Invisible text in insenstitive suggested action buttons

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  The suggestion action button does not have correct text styling when the 
action button is "insensitive" (greyed out). This makes the text basically 
invisible since it has the same dark grey color for both the foreground text 
and the background.

  
  Test Case 1
  ---
  1. Open the file browser.
  2. Open the ☰ menu and select New Folder.

  What happens:
  1. In the New Folder dialog, the top right button has invisible text. 
Screenshot attached.

  What should happen:
  It should show the word Create but greyed out.

  Test Case 2
  ---
  1. Open the gedit text editor.
  2. Open the ☰ menu and select Save As.
  3. In the Name field, delete all the text to make the field empty.

  What happens:
  The word Save in the top right button becomes invisible.

  Other Info
  --
  Ubuntu 18.04.1 LTS
  light-themes 16.10+18.04.20180421.1-0ubuntu1
  Ambiance theme
  libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1767730] Re: Chrome / Chrome Browser Title Bar Button Bug

[Treviño]

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

** This bug has been marked a duplicate of bug 1782038
   Window buttons are small in a maximized Chromium window

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

Title:
  Chrome / Chrome Browser Title Bar Button Bug

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  Chrome / Chrome Browser Title Bar Button Bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1767730/+subscriptions

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

[Touch-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

Any idea the problem with Skype I mentioned above?

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

I see a difference in the ALSA driver version being used now so maybe
this problem was recently fixed?

# in alsa-info output

!!ALSA Version
!!

# Before 
k4.14.55-1-MANJARO

# Now
k4.14.71-1-MANJARO

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

I cannot reproduce the problem now. Recording via arecord with channels locked 
in pavucontrol works OK.  The problem seems to only still exist using Skype (my 
version is 8.29.0.50) which strangely is not allowing me to unlock the 
channels.  
 
My Alsa-info: 
http://www.alsa-project.org/db/?f=9dd883825d6f6c832cfc36c9eb1eaafa347fc4d8

System:
  Host: G50 Kernel: 4.14.71-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 
  Desktop: Xfce 4.12.4 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: LENOVO product: 80E3 v: Lenovo G50-45 
  serial:  
  Mobo: LENOVO model: Lancer 5B2 v: 31900058 STD serial:  
  UEFI: LENOVO v: A2CN45WW(V2.13) date: 08/04/2016 
Battery:
  ID-1: BAT1 charge: 23.2 Wh condition: 23.2/31.7 Wh (73%) 
  model: LENOVO PABAS0241231 status: Full 
CPU:
  Topology: Quad Core model: AMD A6-6310 APU with AMD Radeon R4 Graphics 
  bits: 64 type: MCP arch: Puma rev: 1 L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 14378 
  Speed: 1648 MHz min/max: 1000/1800 MHz Core speeds (MHz): 1: 1681 2: 1505 
  3: 1296 4: 1556 
Graphics:
  Device-1: AMD Mullins [Radeon R4/R5 Graphics] driver: radeon v: kernel 
  bus ID: 00:01.0 
  Display: x11 server: X.Org 1.20.1 driver: ati,radeon unloaded: modesetting 
  resolution: 1366x768~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: AMD MULLINS (DRM 2.50.0 4.14.71-1-MANJARO LLVM 6.0.1) 
  v: 4.5 Mesa 18.2.1 direct render: Yes 
Audio:
  Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:01.1 
  Device-2: AMD FCH Azalia driver: snd_hda_intel v: kernel bus ID: 00:14.2 
  Sound Server: ALSA v: k4.14.71-1-MANJARO 
Network:
  Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter 
  driver: rtl8723be v: kernel port: 3000 bus ID: 01:00 
  IF: wlp1s0 state: up mac:  
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8168 v: 8.045.08-NAPI port: 2000 bus ID: 02:00 
  IF: enp2s0 state: down mac:  
Drives:
  Local Storage: total: 465.76 GiB used: 103.86 GiB (22.3%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
Partition:
  ID-1: / size: 144.89 GiB used: 103.55 GiB (71.5%) fs: ext4 dev: /dev/sda5 
  ID-2: swap-1 size: 6.96 GiB used: 260.8 MiB (3.7%) fs: swap dev: /dev/sda6 
Sensors:
  System Temperatures: cpu: 51.2 C mobo: N/A gpu: radeon temp: 50 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 227 Uptime: 2d 15h 08m Memory: 6.77 GiB used: 4.28 GiB (63.2%) 
  Init: systemd Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 inxi: 3.0.21

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Damiön la Bagh]

I have still have two machines that need upgrading from 14.04 -> 16.04 -> 
18.04. I want to replace them and test the upgrade in the lab.
The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in landscape-client source package in Bionic:
  New
Status in systemd source package in Bionic:
  Confirmed
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions

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

[Touch-packages] [Bug 1784347] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From kyle.mahlk...@ibm.com 2018-10-04 13:56 EDT---
>156 asprintf(, "%.*s%zu", w, dev, partno);
>157 if (access(res, F_OK) == 0){
>158p = "";

Given the example originally used to open the bug, dev=mpatha, partno=1
and so p is set to "" and that will display "mpatha1". Please correct me
if I'm wrong.

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk. 
  Running the fdisk -l and ls -l showing the conflict name for the mpath. 

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 1132472319  41943040   20G 83 Linux

  == Comment: #5 - Kyle Mahlkuch  - 2018-06-26 13:50:12 
==
  I have created and submitted a patch that should help with this bug. I will 
update when/if the patch is accepted.

  == Comment: #9 - Kyle Mahlkuch  - 2018-07-27 09:10:44 
==
  Here is the patch: 
  
https://github.com/karelzak/util-linux/commit/73775189767195f1d9f5b6b6f6a54e51f61c4356

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784347/+subscriptions

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

[Touch-packages] [Bug 1765832] Re: Two finger scrolling not working after suspend

[rathboma]

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

I have this exact issue.

I'm running a Thinkpad X1 Carbon 5th generation. Sometimes two-finger
scrolling half-works, sometimes it breaks entirely.

Everything was working fine until a software update at the end of
September.

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

Title:
  Two finger scrolling not working after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When waking up my laptop, two finger scrolling is not working anymore.

  Running:

  $ modprobe -r psmouse
  $ modprobe psmouse

  restores the functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 20 08:23:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2018-04-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: LENOVO 20BTS09800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET26W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS09800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS09800
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

[Eric Desrochers]

I think the "|| true;" is a good test to validate but I might have to
find something more viable to SRU.

I'll see how upstream populate MOUNT(u)->just_mounted, and try to mimic
that as well instead of forcing "true" implicitly.

This is where I'm at the moment.

Stay tuned.

- Eric

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  From the PR:
  Currently, if there are two /proc/self/mountinfo entries with the same
  mount point path, the mount setup flags computed for the second of
  these two entries will overwrite the mount setup flags computed for
  the first of these two entries. This is the root cause of issue #7798.
  This patch changes mount_setup_existing_unit to prevent the
  just_mounted mount setup flag from being overwritten if it is set to
  true. This will allow all mount units created from /proc/self/mountinfo
  entries to be initialized properly.

  One line fix in https://github.com/systemd/systemd/pull/7811/files

  Referenced issue: https://github.com/systemd/systemd/issues/7798

  Related kubernetes issue:
  https://github.com/kubernetes/kubernetes/issues/57345

  systemd v237 has this fix, but we'd like to have it fixed in 16.04.

  [Other Informations]

  It only affect systemd for Xenial, later release already has the fix:

  $ git describe --contains 65d36b495
  v237~140

  ==>  systemd | 229-4ubuntu21.4  | xenial-updates  
   systemd | 237-3ubuntu10.3  | bionic-updates  
   systemd | 239-7ubuntu9 | cosmic

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

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

[Touch-packages] [Bug 1794843] Re: New release of 'gstreamer1.0' (1.14.4)

[Iain Lane]

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  New release of 'gstreamer1.0' (1.14.4)

Status in gstreamer1.0 package in Ubuntu:
  In Progress

Bug description:
  Hello,

  https://packages.debian.org/source/sid/gstreamer1.0

  'Source Package: gstreamer1.0 (1.14.3-1)'

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ---

  https://gstreamer.freedesktop.org/releases/1.14/#1.14.3

  == 1.14.3 ==

  The third 1.14 bug-fix release (1.14.3) was released on 16 September
  2018.

  This release only contains bugfixes and it should be safe to update
  from 1.14.x.

  Highlighted bugfixes in 1.14.3
  opusenc: fix crash on 32-bit platforms
  compositor: fix major buffer leak when doing crossfading on some but not all 
pads
  wasapi: various fixes for wasapisrc and wasapisink regressions
  x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. 
Rebuild to..." runtime errors with x264 version ≥ 153
  audioaggregator, audiomixer: caps negotiation fixes
  input-selector: latency handling fixes
  playbin, playsink: audio visualization support fixes
  dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand 
profile
  opencv: Fix build for opencv >= 3.4.2
  h265parse: miscellaneous fixes backported from h264parse
  pads: fix changing of pad offsets from inside pad probes
  pads: ensure that pads are blocked for IDLE probes if they are called from 
the streaming thread too

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.2-2
  Uname: Linux 4.18.10-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 13:43:05 2018
  InstallationDate: Installed on 2017-10-13 (349 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+subscriptions

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

[Touch-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Kai-Heng Feng]

Brad, 
Please try kernel parameter "snd-hda-intel.model=inv-dmic".

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk

[Ken VanDine]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  [FFe] Seed xdg-desktop-portal-gtk

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Security and MIR reviews have been completed for xdg-desktop-portal-
  gtk[1] and xdg-desktop-portal[2].

  These packages can improve desktop integration of snap packages.  The
  risk is low as nothing in the default desktop install actually
  exercises the portals at this time.  We need to seed the portals so
  they are available when snaps are installed that can utilize them.
  Flatpak packages will also benefit.

  1. 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
  2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672

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

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

[Touch-packages] [Bug 1794690] Re: Backport 0.8.2 for a CVE update

[Timo Aaltonen]

Not that I know of..

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

Title:
  Backport 0.8.2 for a CVE update

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  In Progress

Bug description:
  [Impact]
  0.8.2 has completed the fuzzing work started in 0.8.1, so backport the 
package from cosmic to fix these CVE's:

  CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.

  upstream NEWS:

  libxkbcommon 0.8.2 - 2018-08-05
  ==

  - Fix various problems found with fuzzing (see commit messages for
    more details):

  - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior
    in the XKB text format parser.

  libxkbcommon 0.8.1 - 2018-08-03
  ==

  - Fix various problems found in the meson build (see commit messages for more
    details):

  - Fix compilation on Darwin.

  - Fix compilation of the x11 tests and demos when XCB is installed in a
    non-standard location.

  - Fix xkbcommon-x11.pc missing the Requires specification.

  - Fix various problems found with fuzzing and Coverity (see commit messages 
for
    more details):

  - Fix stack overflow in the XKB text format parser when evaluating boolean
    negation.

  - Fix NULL-dereferences in the XKB text format parser when some 
unsupported
    tokens appear (the tokens are still parsed for backward compatibility).

  - Fix NULL-dereference in the XKB text format parser when parsing an
    xkb_geometry section.

  - Fix an infinite loop in the Compose text format parser on some
  inputs.

  - Fix an invalid free() when using multiple keysyms.

  - Replace the Unicode characters for the leftanglebracket and 
rightanglebracket
    keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to
    MATHEMATICAL LEFT/RIGHT ANGLE BRACKET.

  - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and
    xkb_keysym_to_utf32.

  [Test case]
  install the update, check that nothing breaks wrt keyboard handling

  [Regression potential]
  slim, this has been in cosmic for some time already, and upstream 
specifically asked to backport this to stable releases

  There are some other changes to the packaging, but these are harmless
  and won't regress anything.

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

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

[Touch-packages] [Bug 1759942] Re: [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a asus laptope model e200h. I install the ubunto desktop. but
  it seems that the audio does not work. I went through the whole
  troubleshooting, but it still dose not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2314/fd/14: Stale file handle
   Cannot stat file /proc/2314/fd/15: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2517 F pulseaudio
  CasperVersion: 1.376.2
  CurrentDesktop: Unity
  Date: Thu Mar 29 20:07:58 2018
  LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio failed
  Symptom_Card: Intel HDMI/DP LPE Audio - Intel HDMI/DP LPE Audio
  Symptom_DevicesInUse:
   Cannot stat file /proc/2314/fd/14: Stale file handle
   Cannot stat file /proc/2314/fd/15: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2517 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: E
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1759942/+subscriptions

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

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[gf]

Hi Patrick,
I just want to clarify the issue for the programmers.
Could you post the exact steps to reproduce?
For example,
1. Open terminal.
2. type "synaptic...
3
Thanks
G

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Dimitri John Ledkov]

** Changed in: klibc (Ubuntu Cosmic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Fix Released
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions

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

[Touch-packages] [Bug 1702125] Re: PCI/internal sound card not detected

[Launchpad Bug Tracker]

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

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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  ASUS E200H Laptop

  Ubuntu 16.04 LTS

  USB sound works - AOK

  Internal sound card not detected

  Thanks
  Vince

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jul  3 08:17:00 2017
  InstallationDate: Installed on 2017-07-01 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1702125/+subscriptions

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

[Touch-packages] [Bug 1653237] Re: PCI/internal sound card not detected

[Launchpad Bug Tracker]

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

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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Intel Z8500 interal audio chip
  ASUS E200HA

  no audio

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Dec 30 13:02:35 2016
  InstallationDate: Installed on 2016-12-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.302:bd11/11/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653237/+subscriptions

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

[Touch-packages] [Bug 1761684] Re: Regression in lists like gnome-boxes

[Adolfo Jayme]

** Changed in: gnome-boxes (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

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

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

[Touch-packages] [Bug 1666369] Re: PCI/internal sound card not detected

[Launchpad Bug Tracker]

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

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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  He instalado Ubuntu 16.04 LTS en mi Asus e200ha y no escucho ningún sonido. 
Todo está activado en el equipo. Ingreso a los diferentes navegadores y 
reproductores de audio pero no logro escuchar nada.
  Muchas Gracias!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Feb 20 22:07:57 2017
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.207:bd02/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666369/+subscriptions

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Dimitri John Ledkov]

systemd-shim removed from the archive, so cannot be fixed really.

** Changed in: systemd-shim (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

** Changed in: systemd-shim (Ubuntu)
   Status: Incomplete => Won't Fix

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd-shim (Ubuntu Cosmic)
   Importance: High
 Assignee: Steve Langasek (vorlon)
   Status: Won't Fix

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

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Confirmed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1795697] Re: Danish translation probably not synchronizing

[Ask Hjorth Larsen]

Thank you very much.  I will open this in a few more projects that seem
to be affected as well.

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

** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-font-viewer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Danish translation probably not synchronizing

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New
Status in gnome-font-viewer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  EDIT: This has been fixed for gtk+; the bug has been marked as also
  affecting several other modules because they seem to have the same
  problem.

  The Danish translation here is not complete:

  
https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details

  However we always fully translate GNOME upstream for each release, so
  it should be complete.

  Something is probably wrong with the import queue again.

  See also https://bugs.launchpad.net/ubuntu/+source/gnome-
  software/+bug/1795695

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

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

[Touch-packages] [Bug 1795697] Re: Danish translation probably not synchronizing

[Ask Hjorth Larsen]

This appears to have affected gtk+-properties as well, but that
translation is up to date now.  Probably was fixed at the same time as
for the main gtk+ package.

** Description changed:

+ EDIT: This has been fixed for gtk+; the bug has been marked as also
+ affecting several other modules because they seem to have the same
+ problem.
+ 
  The Danish translation here is not complete:
  
  
https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details
  
  However we always fully translate GNOME upstream for each release, so it
  should be complete.
  
  Something is probably wrong with the import queue again.
  
  See also https://bugs.launchpad.net/ubuntu/+source/gnome-
  software/+bug/1795695

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

Title:
  Danish translation probably not synchronizing

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New
Status in gnome-font-viewer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  EDIT: This has been fixed for gtk+; the bug has been marked as also
  affecting several other modules because they seem to have the same
  problem.

  The Danish translation here is not complete:

  
https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details

  However we always fully translate GNOME upstream for each release, so
  it should be complete.

  Something is probably wrong with the import queue again.

  See also https://bugs.launchpad.net/ubuntu/+source/gnome-
  software/+bug/1795695

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

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

[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

[Dimitri John Ledkov]

How is reboot requested/triggered?
Systemd has 30min timeout on the reboot, so things must timeout and 
force-self-reboot after 30min.

** No longer affects: systemd (Ubuntu Bionic)

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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

[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1795157] Re: packagekitd crashed with SIGABRT in std::terminate()

[Sebastien Bacher]

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

** This bug is no longer a duplicate of private bug 1788099
** This bug has been marked a duplicate of private bug 1787653

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

Title:
  packagekitd crashed with SIGABRT in std::terminate()

Status in packagekit package in Ubuntu:
  New

Bug description:
  I was just opening chrome and suddenly some error popped up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Sep 28 20:30:00 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-09-22 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/sh
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT in std::terminate()
  UpgradeStatus: Upgraded to cosmic on 2018-09-26 (3 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1795706] Re: packagekitd crashed with SIGABRT

[Sebastien Bacher]

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

** This bug is no longer a duplicate of private bug 1788099
** This bug has been marked a duplicate of private bug 1787653

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  Probably very similar to the ones involving SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct  2 11:07:49 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2017-12-06 (300 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/sh
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-07-10 (84 days ago)
  UserGroups: colord

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

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

[Touch-packages] [Bug 1793851] Re: packagekitd crashed with SIGABRT

[Sebastien Bacher]

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

** This bug is no longer a duplicate of private bug 1788099
** This bug has been marked a duplicate of private bug 1787653

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  Error happened in backround, while installing packages from Software
  Center

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Sat Sep 22 09:59:39 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-09-14 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1796039] Re: packagekitd crashed with SIGABRT in std::terminate()

[Sebastien Bacher]

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

** This bug is no longer a duplicate of private bug 1788099
** This bug has been marked a duplicate of private bug 1787653

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

Title:
  packagekitd crashed with SIGABRT in std::terminate()

Status in packagekit package in Ubuntu:
  New

Bug description:
  Just tried installing Gnome Boxes from the App Store

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Thu Oct  4 10:25:25 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-09-29 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT in std::terminate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails

[Dimitri John Ledkov]

** No longer affects: systemd (Ubuntu Cosmic)

** Tags added: cosmic

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

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

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

[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

[Dimitri John Ledkov]

Hi,

I recommend you to change your test system.

For example, you can modify /etc/systemd/system.conf and change DefaultTasksMax 
there. But that is for the systemd started units...
Note that TasksMax these days can accept % values of kernel configured max 
tasks too, meaning i.e. one can set it to 100%. The upstream default is 15% 
and we reverted that, meaning setting it to unlimited.

However something odd is going on.

I wonder if you are actually hitting UserTasksMax instead (which appears
to be under-documented).

I wonder if setting UserTasksMax=100 in /etc/systemd/logind.conf in
the [Login] section, restarting systemd-logind, creating a brand new
user session (logout _all_ sessions, and relogin) would actually solve
your problem?


ps. Also you can use a "drop-in" instead of modifying a config file, as all 
config files in systemd support .d `drop-ins` like so:

instead of modifying /etc/systemd/system.conf one can instead install
files like these:

/{lib,etc,run}/systemd/system.conf.d/bump-tasks-max.conf

with like contents of
   [Manager]
   DefaultTasksMax=100

Depending on whether you want it to be packaged in a package, be a
config file, or be a runtime adjustment.

** Tags added: cosmic

** No longer affects: systemd (Ubuntu Cosmic)

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

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Nitish]

Not facing any issues due to heating so far. Primarily using the laptop for 
coding.
It does occasionally gets heated, but then nothing that causes any problems. 
I'll update if I face anything.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 1796100] [NEW] crashes while trying to open auxfiles as .deb

[Julian Andres Klode]

Public bug reported:

[Impact]
unattended-upgrades does not work (reliably) in (bionic and) cosmic with the 
mirror:// method, as it tries to open the mirror file - which recent apt 
versions store in auxfiles - as a .deb:


2018-10-04 08:58:46,801 ERROR failed to read deb file 
/var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature)
2018-10-04 08:58:46,801 ERROR failed to read deb file 
/var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature)
2018-10-04 08:58:46,807 ERROR Apt returned an error, exiting
2018-10-04 08:58:46,807 ERROR error message: E:Invalid archive signature
2018-10-04 08:58:46,808 ERROR An error occurred: E:Invalid archive signature
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1595, in main
install_start_time)
  File "/usr/bin/unattended-upgrade", line 1800, in run
if conffile_prompt(item.destfile):
  File "/usr/bin/unattended-upgrade", line 860, in conffile_prompt
deb = apt_inst.DebFile(destFile)
apt_pkg.Error: E:Invalid archive signature

[Test case]
To figure out. It did work for me sometimes, so...

[Regression potential]
To figure out.

** Affects: unattended-upgrades (Ubuntu)
 Importance: High
 Status: Triaged

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Triaged

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- tries to open auxfiles as .deb
+ crashes while trying to open auxfiles as .deb

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

Title:
  crashes while trying to open auxfiles as .deb

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  unattended-upgrades does not work (reliably) in (bionic and) cosmic with the 
mirror:// method, as it tries to open the mirror file - which recent apt 
versions store in auxfiles - as a .deb:

  
  2018-10-04 08:58:46,801 ERROR failed to read deb file 
/var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature)
  2018-10-04 08:58:46,801 ERROR failed to read deb file 
/var/lib/apt/lists/auxfiles/_etc_apt_mirrors.list (E:Invalid archive signature)
  2018-10-04 08:58:46,807 ERROR Apt returned an error, exiting
  2018-10-04 08:58:46,807 ERROR error message: E:Invalid archive signature
  2018-10-04 08:58:46,808 ERROR An error occurred: E:Invalid archive signature
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1595, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1800, in run
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 860, in conffile_prompt
  deb = apt_inst.DebFile(destFile)
  apt_pkg.Error: E:Invalid archive signature

  [Test case]
  To figure out. It did work for me sometimes, so...

  [Regression potential]
  To figure out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1796100/+subscriptions

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

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

[Jeremy Bicha]

Mario, I believe GNOME is planning to do a gnome-settings-daemon
3.30.1.2 release soon disabling the feature by default (at compile
time). See https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/issues/78 and its attached merge proposal especially the NEWS
entry.

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Triaged

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

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

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