date:20180419

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: clutter-gst-3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: clutter-gst-3.0 (Ubuntu)
   Status: New => In Progress

** Changed in: clutter-gst-3.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Confirmed
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gst-3.0 package in Ubuntu:
  In Progress
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717449] Re: Titlebar height changes as buttons are added/removed

I think this was fixed in 18.04 recently, probably by:
https://launchpad.net/ubuntu/+source/ubuntu-themes/16.10+18.04.20180328-0ubuntu1

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

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

Title:
  Titlebar height changes as buttons are added/removed

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Using Ambiance theme, the titlebar height changes as buttons are 
added/removed. For example:
Settings > Devices > (click on the different options)

  The Adwaita theme however has no such problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170817-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 15 15:07:09 2017
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/+source/ubuntu-themes/+bug/1717449/+subscriptions

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

[Touch-packages] [Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login

This bug was fixed in the package xorg - 1:7.7+19ubuntu7

---
xorg (1:7.7+19ubuntu7) bionic; urgency=medium

  [ Simon Quigley ]
  * 60x11-common_xdg_path: If $XDG_CONFIG_DIRS is nonempty, don't discard the
contents.

  [ Didier Roche ]
  * 60x11-common_xdg_path:
- protect against multiple additions of the same paths to
  XDG_CONFIG_DIRS and XDG_DATA_DIRS, resulting to duplication on
  consecutive logout/logins due to older session hanging in and env
  being reused.
  Some consequences is that electron application crashes (LP: #1764355)
- remove readdition of defaults if XDG_CONFIG_DIRS isn't empty to respect
  user's selection (same logic than wayland session).

 -- Timo Aaltonen   Thu, 19 Apr 2018 17:47:42 +0300

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

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

Title:
  Visual Studio Code, Slack and other electrons apps crash due to
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1505368] Re: Bug reports after segmentation fault are never generated

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

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

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  Expired

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser (as described on https://wiki.ubuntu.com/Apport).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportLog:
   ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: called for pid 19798, 
signal 6, core limit 0
   ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: executable: 
/usr/lib/gnome-terminal/gnome-terminal-server (command line 
"/usr/lib/gnome-terminal/gnome-terminal-server")
   ERROR: apport (pid 4083) Fri Feb 17 22:37:25 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 4083) Fri Feb 17 22:37:39 2017: wrote report 
/var/crash/_usr_lib_gnome-terminal_gnome-terminal-server.1000.crash
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-12-12 (433 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  Package: apport 2.20.3-0ubuntu8.2
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Tags:  yakkety
  Uname: Linux 4.8.0-37-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (123 days ago)
  UserGroups: adm autopilot bumblebee cdrom dip libvirt libvirtd lp lpadmin 
plugdev sambashare saned sudo vboxusers
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1697786] Re: Graphic drivers may cause problem with booting

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

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

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

Title:
  Graphic drivers may cause problem with booting

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Please send information to my email.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  Date: Tue Jun 13 22:26:34 2017
  LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1697093] Re: Black Screen after boot.

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

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

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

Title:
  Black Screen after boot.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04 was working fine for a long time but since recently,
  while booting, after purple screen the screen goes blank. There is no
  mouse pointer. A cursor blinks for a few seconds and screen goes 100%
  black but still lit, and then after another few seconds, it goes
  completely dark as if it is turned off. I then switch to the command-
  line screen or tty1 to get the logs.

  I've tried: the `oibaf-drivers` but this didn't help.

  Using `startX` in tty1, the mouse pointer turns to a cross and only
  folders present on my desktop are visible, but no wallpaper can be
  seen, no side-dock, no launcher (after the click) and no status bar.
  The desktop is completely absent though desktop folders are visible
  and can be opened.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog: /dev/sda11: clean, 302776/3129344 files, 2203296/12499968 blocks
  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: Sat Jun 10 01:39:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
     Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
  InstallationDate: Installed on 2017-05-18 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO ACLU12
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic 
root=UUID=f693a857-8102-4f79-a16a-ad0d75fb8edc ro quiet splash nomodeset 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 3196STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pnACLU12:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3196STD:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.name: ACLU12
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git1706061830.b6f450~gd~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1706091930.d42fc6~gd~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1706091930.d42fc6~gd~x
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.9.99+git1705240733.d80d01~gd~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1706071933.6babcf~gd~x
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1704220733.a7c190~gd~x
  xserver.bootTime: Sat Jun 10 01:35:56 2017
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1717449] Re: Titlebar height changes as buttons are added/removed

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

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

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

Title:
  Titlebar height changes as buttons are added/removed

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Using Ambiance theme, the titlebar height changes as buttons are 
added/removed. For example:
Settings > Devices > (click on the different options)

  The Adwaita theme however has no such problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170817-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 15 15:07:09 2017
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/+source/ubuntu-themes/+bug/1717449/+subscriptions

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

[Touch-packages] [Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support

2018-04-19 Thread shankao

I solved the problem for my with "apt purge nux-tools"

** Summary changed:

- LLVMpipe renderer used instead of Intel on Xorg sessions
+ LLVMpipe renderer used instead of Intel on Xorg sessions because of unity 
leftover file /etc/X11/Xsession.d/50_check_unity_support

** Summary changed:

- LLVMpipe renderer used instead of Intel on Xorg sessions because of unity 
leftover file /etc/X11/Xsession.d/50_check_unity_support
+ LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions 
because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support

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

Title:
  LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg
  sessions because of unity leftover file
  /etc/X11/Xsession.d/50_check_unity_support

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

2018-04-19 Thread shankao

For the record:

$ dpkg -S /etc/X11/Xsession.d/50_check_unity_support
nux-tools: /etc/X11/Xsession.d/50_check_unity_support

$ apt rdepends --installed unity
unity
Reverse Depends:
  Breaks: ubuntu-session (<< 7.5.0+17.10.20170619)

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

Title:
  LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg
  sessions because of unity leftover file
  /etc/X11/Xsession.d/50_check_unity_support

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

2018-04-19 Thread shankao

So, after investigating this problem, I finally saw the cause: under
X.org, the environment variable LIBGL_ALWAYS_SOFTWARE is set to 1
*always*. Without it, it uses the intel driver as usual:

$ LIBGL_ALWAYS_SOFTWARE=0 glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0-rc5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

This is probably because I have an old unity file that's running when my
session starts (/etc/X11/Xsession.d/50_check_unity_support) with these
contents:

# This file is sourced by Xsession(5), not executed.
# If the hardware does not pass unity_support_test, fall back to LLVMpipe
# which does.

if [ "x$DESKTOP_SESSION" = "xubuntu" ]; then
/usr/lib/nux/unity_support_test || export LIBGL_ALWAYS_SOFTWARE=1
fi

And given that the file /usr/lib/nux/unity_support_test doesn't exist
anymore, it always exports the variable.

I think that there is still a bug here, and some possible fixes:

a) Remove the offending file when unity is removed
b) Fix the condition to check if unity_support_test exists
c) Be sure that ubuntu-bug reports the status of the flag for mesa bugs
d) Make that glxinfo prominently warns that the current env forces it to run in 
software mode

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

Title:
  LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg
  sessions because of unity leftover file
  /etc/X11/Xsession.d/50_check_unity_support

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:

[Touch-packages] [Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

Test PPA is available at $ sudo add-apt-repository ppa:ci-train-ppa-
service/3243

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

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

Title:
  networkd waits 10 seconds for ipv6 network discovery by default

Status in cloud-init package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On ipv6 less hosts, boot stalls for 10s
   * This is due to implicit RA being on, and wait-online awaiting for RA to 
timeout
   * Expectation is, that since explicit request for RA was not done, it should 
not block network-online.target, whilst all other aspects of 
network-online.target should be honored.

  [Test Case]

   * lxc network set lxdbr0 ipv6.address none
   * lxc launch ubuntu-daily:bionic lp1765173
   * sleep 20 && lxc exec lp1765173 systemd-analyze blame | head

  Bad result is:
   12.157s systemd-networkd-wait-online.service
  Good result is:
 739ms systemd-networkd-wait-online.service

  [Regression Potential]

   * If explicit IPv6 dhcp/ra was enabled in .network file, the boot
  will be blocked awaiting RA response

   * Only kernel implicit RA configuration will now become "async"

   * This is inline with behaviour of xenial systems

  [Other Info]

   * Original bug report

  1.
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2.
  $ apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu8
    Candidate: 237-3ubuntu8
    Version table:
   *** 237-3ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. systemd-networkd-wait-online doesn't block for 10 seconds waiting
  on an IPV6 Router Advertisement

  4. systemd-networkd sends at least two RA solicitation packets waiting
  for a response before setting the link to configured.  This blocks the
  boot for every Ubuntu system where it does not have a IPV6 router
  responding to solicitations.  THis includes bionic containers, cloud
  instances, vms and physical machines.

  --

  We can see that we're spending 13 seconds waiting  for networkd to say
  the network is up.

  % systemd-analyze blame
   13.326s systemd-networkd-wait-online.service
     999ms cloud-init-local.service
     954ms cloud-init.service
     887ms cloud-config.service
     749ms dev-vda1.device
     666ms cloud-final.service
     248ms keyboard-setup.service
     175ms systemd-udev-trigger.service
     171ms lxd-containers.service
     165ms snapd.service
     154ms apparmor.service
     147ms ssh.service
     144ms systemd-timesyncd.service
     133ms grub-common.service
     130ms systemd-journald.service
     130ms accounts-daemon.service
  99ms systemd-modules-load.service
  98ms systemd-resolved.service
  94ms apport.service
  92ms rsyslog.service
  88ms systemd-logind.service
  80ms lvm2-monitor.service
  75ms iscsid.service
  64ms ebtables.service
  62ms user@1000.service
  54ms dev-mqueue.mount
  53ms ufw.service
  52ms systemd-remount-fs.service
  52ms kmod-static-nodes.service
  34ms systemd-journal-flush.service
  34ms polkit.service
  32ms systemd-tmpfiles-setup-dev.service
  27ms systemd-udevd.service
  26ms systemd-networkd.service
  26ms systemd-sysctl.service
  25ms systemd-tmpfiles-setup.service
  21ms dev-hugepages.mount
  17ms sys-kernel-debug.mount
  16ms console-setup.service
  15ms plymouth-read-write.service
  15ms snapd.socket
  15ms plymouth-quit.service
  14ms systemd-update-utmp.service
  10ms systemd-user-sessions.service
   9ms boot-efi.mount
   8ms sys-fs-fuse-connections.mount
   8ms systemd-update-utmp-runlevel.service
   8ms lxd.socket
   7ms blk-availability.service
   5ms systemd-random-seed.service
   3ms setvtrgb.service
   3ms plymouth-quit-wait.service
   3ms sys-kernel-config.mount

  Here we can see that we start networking at 18:30:51.69, and then IPv6 NDISC 
runs for 10 seconds
  and then the link is configured at 18:31:05.  *AND* we see NDISC stays around 
and continues to see if it gets a RA packet.

  $ journalctl -o short-precise -u systemd-networkd.service  | egrep "(Starting 
Network|Discovering IPv6

[Touch-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

Sorry, I was wrong.

It seems the bug is in GTK's titlebar logic. For Xorg sessions that's
only used in "modern" apps with the thick headerbar. For Wayland
sessions, that's used in all apps.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

** Description changed:

+ [Impact]
+ 
+  * On ipv6 less hosts, boot stalls for 10s
+  * This is due to implicit RA being on, and wait-online awaiting for RA to 
timeout
+  * Expectation is, that since explicit request for RA was not done, it should 
not block network-online.target, whilst all other aspects of 
network-online.target should be honored.
+ 
+ [Test Case]
+ 
+  * lxc network set lxdbr0 ipv6.address none
+  * lxc launch ubuntu-daily:bionic lp1765173
+  * sleep 20 && lxc exec lp1765173 systemd-analyze blame | head
+ 
+ Bad result is:
+  12.157s systemd-networkd-wait-online.service
+ Good result is:
+  less than 3s
+ 
+ [Regression Potential]
+ 
+  * If explicit IPv6 dhcp/ra was enabled in .network file, the boot will
+ be blocked awaiting RA response
+ 
+  * Only kernel implicit RA configuration will now become "async"
+ 
+  * This is inline with behaviour of xenial systems
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  1.
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  2.
  $ apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu8
-   Candidate: 237-3ubuntu8
-   Version table:
-  *** 237-3ubuntu8 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 237-3ubuntu8
+   Candidate: 237-3ubuntu8
+   Version table:
+  *** 237-3ubuntu8 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. systemd-networkd-wait-online doesn't block for 10 seconds waiting on
  an IPV6 Router Advertisement
  
  4. systemd-networkd sends at least two RA solicitation packets waiting
  for a response before setting the link to configured.  This blocks the
  boot for every Ubuntu system where it does not have a IPV6 router
  responding to solicitations.  THis includes bionic containers, cloud
  instances, vms and physical machines.
  
  --
  
  We can see that we're spending 13 seconds waiting  for networkd to say
  the network is up.
  
  % systemd-analyze blame
-  13.326s systemd-networkd-wait-online.service
-999ms cloud-init-local.service
-954ms cloud-init.service
-887ms cloud-config.service
-749ms dev-vda1.device
-666ms cloud-final.service
-248ms keyboard-setup.service
-175ms systemd-udev-trigger.service
-171ms lxd-containers.service
-165ms snapd.service
-154ms apparmor.service
-147ms ssh.service
-144ms systemd-timesyncd.service
-133ms grub-common.service
-130ms systemd-journald.service
-130ms accounts-daemon.service
- 99ms systemd-modules-load.service
- 98ms systemd-resolved.service
- 94ms apport.service
- 92ms rsyslog.service
- 88ms systemd-logind.service
- 80ms lvm2-monitor.service
- 75ms iscsid.service
- 64ms ebtables.service
- 62ms user@1000.service
- 54ms dev-mqueue.mount
- 53ms ufw.service
- 52ms systemd-remount-fs.service
- 52ms kmod-static-nodes.service
- 34ms systemd-journal-flush.service
- 34ms polkit.service
- 32ms systemd-tmpfiles-setup-dev.service
- 27ms systemd-udevd.service
- 26ms systemd-networkd.service
- 26ms systemd-sysctl.service
- 25ms systemd-tmpfiles-setup.service
- 21ms dev-hugepages.mount
- 17ms sys-kernel-debug.mount
- 16ms console-setup.service
- 15ms plymouth-read-write.service
- 15ms snapd.socket
- 15ms plymouth-quit.service
- 14ms systemd-update-utmp.service
- 10ms systemd-user-sessions.service
-  9ms boot-efi.mount
-  8ms sys-fs-fuse-connections.mount
-  8ms systemd-update-utmp-runlevel.service
-  8ms lxd.socket
-  7ms blk-availability.service
-  5ms systemd-random-seed.service
-  3ms setvtrgb.service
-  3ms plymouth-quit-wait.service
-  3ms sys-kernel-config.mount
- 
+  13.326s systemd-networkd-wait-online.service
+    999ms cloud-init-local.service
+    954ms cloud-init.service
+    887ms cloud-config.service
+    749ms dev-vda1.device
+    666ms cloud-final.service
+    248ms keyboard-setup.service
+    175ms systemd-udev-trigger.service
+    171ms lxd-containers.service
+    165ms snapd.service
+    154ms apparmor.service
+    147ms ssh.service
+    144ms systemd-timesyncd.service
+    133ms grub-common.service
+    130ms systemd-journald.service
+    130ms accounts-daemon.service
+ 99ms

[Touch-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

In light of comment #51 above, I shall pursue uploading a udev-udeb with
modprobe.d config snippet that forces scsi_mod.scan=sync.

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04

** Changed in: debian-installer (Ubuntu)
Milestone: later => ubuntu-18.04

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

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based 
HDD/RAID arrays

  Tried with current bionic and current bionic-proposed installers
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
  kexec -l vmlinux -i initrd.gz
  kexec -e

  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
   kexec -l vmlinux -i initrd.gz
  kexec -e

  ---uname output---
  uname -a
  Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 
09:05:20 UTC 2018 ppc64le GNU/Linux

  Machine Type = 8247-22L (S822L)
   
  ---boot type---
  Network boot
   
  ---bootloader---
  petitboot shell
   
  ---Kernel cmdline used to launch install---
  #cat /proc/cmdline

  ---Bootloader protocol---
  http
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  US
   
  ---Point of failure---
  Problem during post-install (stage 2) configuration or other problem seen 
after reboot

  ===console error log===


?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM  ?
? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  ~ # lsmod | grep -i ipr
  ipr   148677  0
  ~ # modinfo ipr
  filename:   /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko
  version:2.6.4
  license:GPL
  description:IBM Power RAID SCSI Adapter Driver
  author: Brian King 
  srcversion: 05BB872A11F65B3A73AB352
  alias:  pci:v1014d04DAsv1014sd04FBbc*sc*i*
  alias:  pci:v1014d04DAsv1014sd04FCbc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C9bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C8bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04C7bc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Cbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Bbc*sc*i*
  alias:  pci:v1014d034Asv1014sd049Abc*sc*i*
  alias:  pci:v1014d034Asv1014sd0499bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0475bc*sc*i*
  alias:  pci:v1014d034Asv1014sd0474bc*sc*i*
  alias:  pci:v1014d034Asv1014sd04CAbc*sc*i*
  alias:  pci:v1014d034Asv1014sd046Dbc*sc*i*
  alias:  pci:v1014d034Asv1014sd03FEbc*sc*i*
  alias:

[Touch-packages] [Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

in summary the consensus is as follows:

- cloud-init should not provide accept-ra key to netplan.io
- netplan.io should not emit any accept-ra keys to networkd
- networkd, when not receiving any accept-ra keys should use kernel implicit 
default
- networkd, when in implicit RA mode, should not block on getting RA as a 
pre-condition for a link to become ready

I believe cloud-init & netplan.io portions are done already.

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: netplan.io (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  networkd waits 10 seconds for ipv6 network discovery by default

Status in cloud-init package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  1.
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2.
  $ apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu8
Candidate: 237-3ubuntu8
Version table:
   *** 237-3ubuntu8 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. systemd-networkd-wait-online doesn't block for 10 seconds waiting
  on an IPV6 Router Advertisement

  4. systemd-networkd sends at least two RA solicitation packets waiting
  for a response before setting the link to configured.  This blocks the
  boot for every Ubuntu system where it does not have a IPV6 router
  responding to solicitations.  THis includes bionic containers, cloud
  instances, vms and physical machines.

  --

  We can see that we're spending 13 seconds waiting  for networkd to say
  the network is up.

  % systemd-analyze blame
   13.326s systemd-networkd-wait-online.service
 999ms cloud-init-local.service
 954ms cloud-init.service
 887ms cloud-config.service
 749ms dev-vda1.device
 666ms cloud-final.service
 248ms keyboard-setup.service
 175ms systemd-udev-trigger.service
 171ms lxd-containers.service
 165ms snapd.service
 154ms apparmor.service
 147ms ssh.service
 144ms systemd-timesyncd.service
 133ms grub-common.service
 130ms systemd-journald.service
 130ms accounts-daemon.service
  99ms systemd-modules-load.service
  98ms systemd-resolved.service
  94ms apport.service
  92ms rsyslog.service
  88ms systemd-logind.service
  80ms lvm2-monitor.service
  75ms iscsid.service
  64ms ebtables.service
  62ms user@1000.service
  54ms dev-mqueue.mount
  53ms ufw.service
  52ms systemd-remount-fs.service
  52ms kmod-static-nodes.service
  34ms systemd-journal-flush.service
  34ms polkit.service
  32ms systemd-tmpfiles-setup-dev.service
  27ms systemd-udevd.service
  26ms systemd-networkd.service
  26ms systemd-sysctl.service
  25ms systemd-tmpfiles-setup.service
  21ms dev-hugepages.mount
  17ms sys-kernel-debug.mount
  16ms console-setup.service
  15ms plymouth-read-write.service
  15ms snapd.socket
  15ms plymouth-quit.service
  14ms systemd-update-utmp.service
  10ms systemd-user-sessions.service
   9ms boot-efi.mount
   8ms sys-fs-fuse-connections.mount
   8ms systemd-update-utmp-runlevel.service
   8ms lxd.socket
   7ms blk-availability.service
   5ms systemd-random-seed.service
   3ms setvtrgb.service
   3ms plymouth-quit-wait.service
   3ms sys-kernel-config.mount

  
  Here we can see that we start networking at 18:30:51.69, and then IPv6 NDISC 
runs for 10 seconds
  and then the link is configured at 18:31:05.  *AND* we see NDISC stays around 
and continues to see if it gets a RA packet.

  $ journalctl -o short-precise -u systemd-networkd.service  | egrep "(Starting 
Network|Discovering IPv6 routers|NDISC|Configured)" 
  Apr 18 18:30:51.691532 rharper-b1 systemd[1]: Starting Network Service...
  Apr 18 18:30:53.031041 rharper-b1 systemd-networkd[603]: ens3: Discovering 
IPv6 routers
  Apr 18 18:30:53.031306 rharper-b1 systemd-networkd[603]: NDISC: Started IPv6 
Router Solicitation client
  Apr 18 18:30:53.031612 rharper-b1 systemd-networkd[603]: NDISC: Sent Router 
Solicitation, next solicitation in 4s
  Apr 18 18:30:57.092282 rharper-b1

[Touch-packages] [Bug 1765463] Re: Bionic: systemd: rename interface

/etc/systemd/netword/uplink0.link

that's invalid path, no?

/etc/systemd/network/ is the right path, and should work.


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

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

Title:
  Bionic: systemd: rename interface

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu8

  3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

  /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT=""
  GRUB_CMDLINE_LINUX=""

  /etc/systemd/netword/uplink0.link
  [Match]
  Path=pci-:02:00.0

  [Link]
  Name=uplink0

  # update-initramfs -u

  4) journalctl -b | grep rename
  kernel: tg3 :02:00.1 eno2: renamed from eth1
  kernel: tg3 :02:00.0 eno1: renamed from eth0

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

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

[Touch-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland

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

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

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen with
  nouveau + Wayland

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

This bug was fixed in the package chrony - 3.2-4ubuntu4

---
chrony (3.2-4ubuntu4) bionic; urgency=medium

  * d/postrm: re-establish systemd-timesyncd on removal (LP: #1764357)
  * Notify chrony to update sources in response to systemd-networkd
events (LP: #1718227)
- d/links: link dispatcher script to networkd-dispatcher events routable
  and off
- d/control: set Recommends to networkd-dispatcher
- d/p/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch
- d/p/lp-1718227-nm-dispatcher-for-networkd.patch

 -- Christian Ehrhardt   Mon, 16 Apr
2018 17:04:06 +0200

** Changed in: chrony (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log

[Touch-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

Because middle click actions do work in Xorg sessions, and only fail in
Wayland. If you find something is broken in a Xorg session then it is
not this bug.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759754] Re: Ambiance titlebar gradient doesn't match the menubar colour

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

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

Title:
  Ambiance titlebar gradient doesn't match the menubar colour

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Ambiance titlebar gradient doesn't match the Terminal menubar colour.

  There's a hard line visible between a terminal's titlebar and menu
  bar.

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

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

[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:GI_libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

This bug was fixed in the package unattended-upgrades - 1.1ubuntu1

---
unattended-upgrades (1.1ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable (LP: #1764797)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Rename d/NEWS.Debian to d/NEWS to have it shipped
  - Fix typo in NEWS file
  - d/rules: Exclude mypy cache from source package.

unattended-upgrades (1.1) unstable; urgency=medium

  [ cgail914 ]
  * Update 50unattended-upgrades.Raspbian
added a semi-column sign on line 86 to facilitate uncommenting the line
for users and not end up with an error message when running
unattended-upgrades. And make the whole file consistent.

  [ Tobias Bannert ]
  * completed german translation

  [ Simon McVittie ]
  * d/rules: Exclude mypy cache from source package.

  [ Julian Andres Klode ]
  * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)

  [ Balint Reczey ]
  * Rename d/NEWS.Debian to d/NEWS to have it shipped
  * Fix typo in NEWS file
  * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option
  * Set UnattendedUpgradesCache.allowed_origins before calling
apt.Cache.__init__()
  * Find package candidates to adjust sweeping through all packages only once.
Later reuse the list candidates and filter out packages installed in the
meantime. Thanks to Julian Andres Klode for the original patch
  * Use updated python-apt in upgrade-between-snapshots test
  * upgrade-between-snapshots: Mount /proc, too, in the chroot.
Also clean up chroot properly on exit.
  * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
too
  * upgrade-between-snapshots: Remove packages installed as the side-effect of
updating apt and python-apt
  * Ignore errors from compiling backported packages
  * Make is_autoremove_valid() nondestructive.
Also fix autoremoval of packages when one package can't be removed and
keeps back other package removals due to missing cache.clear()
  * Fix tracking removed packages
  * Suggest default-mta | mail-transport-agent to keep Lintian happy

  [ Michael Vogt ]
  * unattanded-upgrades: refactor get_candidates_to_adjust() to
adjust_candidates()

 -- Balint Reczey   Tue, 17 Apr 2018 16:53:30 +0200

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

Status in python-apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
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/ubuntu/+source/python-apt/+bug/1737441/+subscriptions

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

[Touch-packages] [Bug 1764797] Re: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)

This bug was fixed in the package unattended-upgrades - 1.1ubuntu1

---
unattended-upgrades (1.1ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable (LP: #1764797)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Rename d/NEWS.Debian to d/NEWS to have it shipped
  - Fix typo in NEWS file
  - d/rules: Exclude mypy cache from source package.

unattended-upgrades (1.1) unstable; urgency=medium

  [ cgail914 ]
  * Update 50unattended-upgrades.Raspbian
added a semi-column sign on line 86 to facilitate uncommenting the line
for users and not end up with an error message when running
unattended-upgrades. And make the whole file consistent.

  [ Tobias Bannert ]
  * completed german translation

  [ Simon McVittie ]
  * d/rules: Exclude mypy cache from source package.

  [ Julian Andres Klode ]
  * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)

  [ Balint Reczey ]
  * Rename d/NEWS.Debian to d/NEWS to have it shipped
  * Fix typo in NEWS file
  * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option
  * Set UnattendedUpgradesCache.allowed_origins before calling
apt.Cache.__init__()
  * Find package candidates to adjust sweeping through all packages only once.
Later reuse the list candidates and filter out packages installed in the
meantime. Thanks to Julian Andres Klode for the original patch
  * Use updated python-apt in upgrade-between-snapshots test
  * upgrade-between-snapshots: Mount /proc, too, in the chroot.
Also clean up chroot properly on exit.
  * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
too
  * upgrade-between-snapshots: Remove packages installed as the side-effect of
updating apt and python-apt
  * Ignore errors from compiling backported packages
  * Make is_autoremove_valid() nondestructive.
Also fix autoremoval of packages when one package can't be removed and
keeps back other package removals due to missing cache.clear()
  * Fix tracking removed packages
  * Suggest default-mta | mail-transport-agent to keep Lintian happy

  [ Michael Vogt ]
  * unattanded-upgrades: refactor get_candidates_to_adjust() to
adjust_candidates()

 -- Balint Reczey   Tue, 17 Apr 2018 16:53:30 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Feature Freeze Justification
  

  Latest unattended-upgrades upload fixed multiple serious issues and
  includes a few minor fixes which are not worth skipping.

  Most notably it now runs upgrade-between-snapshots autopkgtest with
  updated python-apt thus regressions can block migration to release
  pocket and fixes frequent crashes due to using python-apt's API in a
  wrong way.

  Changes:
   unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
   .
     * Merge from Debian unstable (LP: #1764797)
   - Remaining changes:
     - unattended-upgrades: Do not automatically upgrade the development
   release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
   - Dropped changes, included in Debian:
     - Rename d/NEWS.Debian to d/NEWS to have it shipped
     - Fix typo in NEWS file
     - d/rules: Exclude mypy cache from source package.
   .
   unattended-upgrades (1.1) unstable; urgency=medium
   .
     [ cgail914 ]
     * Update 50unattended-upgrades.Raspbian
   added a semi-column sign on line 86 to facilitate uncommenting the line
   for users and not end up with an error message when running
   unattended-upgrades. And make the whole file consistent.
   .
     [ Tobias Bannert ]
     * completed german translation
   .
     [ Simon McVittie ]
     * d/rules: Exclude mypy cache from source package.
   .
     [ Julian Andres Klode ]
     * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
   .
     [ Balint Reczey ]
     * Rename d/NEWS.Debian to d/NEWS to have it shipped
     * Fix typo in NEWS file
     * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages 
option
     * Set UnattendedUpgradesCache.allowed_origins before calling
   apt.Cache.__init__()
     * Find package candidates to adjust sweeping through all packages only 
once.
   Later reuse the list candidates and filter out packages installed in the
   meantime. Thanks to Julian Andres Klode for the original patch
     * Use updated

[Touch-packages] [Bug 1759754] Re: Ambiance titlebar gradient doesn't match the Terminal menubar colour

** No longer affects: gnome-terminal (Ubuntu)

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

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

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

** Summary changed:

- Ambiance titlebar gradient doesn't match the Terminal menubar colour
+ Ambiance titlebar gradient doesn't match the menubar colour

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

Title:
  Ambiance titlebar gradient doesn't match the menubar colour

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Ambiance titlebar gradient doesn't match the Terminal menubar colour.

  There's a hard line visible between a terminal's titlebar and menu
  bar.

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

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

[Touch-packages] [Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login

This bug was fixed in the package gnome-session - 3.28.1-0ubuntu2

---
gnome-session (3.28.1-0ubuntu2) bionic; urgency=medium

  * debian/xdg_dirs_desktop_session.sh, debian/55gnome-session_gnomerc:
- protect against multiple additions of the same paths to
  XDG_CONFIG_DIRS and XDG_DATA_DIRS, resulting to duplication on
  consecutive logout/logins due to older session hanging in and env
  being reused.
  Some consequences is that electron application crashes (LP: #1764355)

 -- Didier Roche   Thu, 19 Apr 2018 16:43:50 +0200

** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Visual Studio Code, Slack and other electrons apps crash due to
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765561] [NEW] Nautilus path bar buttons are inconsistent

Public bug reported:

As per: https://github.com/CanonicalLtd/desktop-design/issues/28

There are a lot of different greys in the breadcrumbs at the top of the
Nautilus window which need some rationalisation.

Also it's very hard to discern what is selected.

** Affects: ubuntu-themes (Ubuntu)
 Importance: High
 Assignee: Carlo Lobrano (c-lobrano)
 Status: In Progress

** Branch linked: lp:~c-lobrano/ubuntu-themes/pathbar-review

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

Title:
  Nautilus path bar buttons are inconsistent

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As per: https://github.com/CanonicalLtd/desktop-design/issues/28

  There are a lot of different greys in the breadcrumbs at the top of
  the Nautilus window which need some rationalisation.

  Also it's very hard to discern what is selected.

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

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

[Touch-packages] [Bug 1568273] Re: Visual issues with linked buttons

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

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

Title:
  Visual issues with linked buttons

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  GTK buttons have many visual glitches. It looks like all default
  themes (Radiance, Ambiance and High Contrast) aren't compatible with
  GTK 3.18

  - Open Nautilus, on the left tool bar click on "Documents", then click on 
"Home". After that the "Home" button on the top bar will look all rounded, 
where it shouldn't be in the side next to the adjacent button:
  https://launchpadlibrarian.net/253125292/1-bad.png

  - On the top bar, point the mouse over the "Home" button. After that the 
"Home" button looks OK:
  https://launchpadlibrarian.net/253125315/2-ok.png

  - Keep Nautilus open and don't touch it. Open System Settings and go back to 
Nautilus. After that on the top bar the "Home" button suddenly looks OK:
  https://launchpadlibrarian.net/253125315/2-ok.png

  - On the left tool bar, click on "Recent". After that the right side of the 
"Recent" button doesn't have all its corners rounded:
  https://launchpadlibrarian.net/253125350/3-bad.png

  - On the top bar, point the mouse over the "Recent" button. Then the
  button will look fine until you move the mouse pointer away.

  This is just example, but there are many more visual issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-themes 14.04+16.04.20160324.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  9 13:23:43 2016
  InstallationDate: Installed on 2016-04-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160407)
  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/+source/ubuntu-themes/+bug/1568273/+subscriptions

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

[Touch-packages] [Bug 1726318] Re: Destructive actions on headerbar aren't properly themed

** Changed in: ubuntu-themes
   Status: In Progress => Fix Released

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

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

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

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing

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

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

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

Title:
  Nautilus sidebar theming is confusing

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The new theming of the Nautilus sidebar is confusing to users.  The icons and 
the icon labels have a different background colour, and when a specific 
location is selected the background colour of the selected icon changes to be 
the same as the background colour of the labels, while the other icons have a 
darker background colour.
  This is giving the impression that the text labels are a hierarchy of the 
icon, rather than simply being labels associated with each icon.

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

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

[Touch-packages] [Bug 1726322] Re: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows

** Changed in: ubuntu-themes
   Status: In Progress => Fix Released

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

Title:
  Suggested and Destructive action buttons in headerbar have wrong
  gradients in maximized windows

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Suggested and Desctructive action (simple-scan is an example for both)
  buttons still have the "normal" gradient when the window is maximized,
  while this should be inverted.

  See https://usercontent.irccloud-cdn.com/file/hm2uCy3D/image.png
  (shown both for reference)

  [Test case]

  1. Run simple scan
  2. Maximize the window
  3. The gradient should have consistent direction with other buttons around

  [Regression potential]

  Background gradients for windows with such buttons might be wrong in
  normal windows.

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

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

[Touch-packages] [Bug 1101298] Re: More resources must be added into Chromium profile

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

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

  [ Didier Roche ]
  * debian/patches/ubuntu/communitheme-snap-support.patch:
- support communitheme snap (LP: #1762983)

  [ Jamie Strandboge ]
  * debian/patches/ubuntu/add-chromium-browser.patch: adjust for newer
chromium (LP: #1101298, LP: #1594589, LP: #1647142)
- add attach_disconnected
- allow reading /proc/vmstat
- don't require owner match for /proc/pid/{stat,status} and task
  counterparts
- adjust pci[0-9] to be pci[0-9a-f]
- allow reading all uevents and /sys/devices/virtual/tty/tty0/active
- allow ptracing xdgsettings and lsb-release
- xdgsettings uses head and tr and looks at /usr/share/ubuntu/applications/
- lsb-release uses python 3.6 and looks at apport, apt.conf, dpkg and
  distro-info
- use 'm' on on sandbox
  * debian/patches/ubuntu/mimeinfo-snap-support.patch: allow reading
/var/lib/snapd/desktop/applications *.desktop and mimeinfo.cache
(LP: #1712039)

 -- Jamie Strandboge   Tue, 17 Apr 2018 20:15:16 +

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

Title:
  More resources must be added into Chromium profile

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  When I install apparmor-profiles package and set Chromium AppArmor
  profile to enforce mode,  Chromium cannot detect the default browser
  and claims that it is not the default browser even though I set so.
  And I see this line in dmesg:

  ... type=1400 audit(1358526376.204:84): apparmor="DENIED"
  operation="exec" parent=6216 profile="/usr/lib/chromium-browser
  /chromium-browser//xdgsettings" name="/usr/bin/gawk" pid=6220 comm
  ="xdg-mime" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  Now, there is only /usr/bin/mawk line in Chromium apparmor profile but
  users may use a different implementation thanks to the alternatives
  system.

  In addition, my dmesg is flooded by these lines:

  ... type=1400 audit(1358527121.548:197): apparmor="DENIED"
  operation="open" parent=6072 profile="/usr/lib/chromium-browser
  /chromium-browser"
  name="/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq" pid=8984
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  It would be nice to see
  "/sys/devices/system/**/cpufreq/cpuinfo_max_freq r," added to the
  profile.

  My patch regarding the issue is attached.

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

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

[Touch-packages] [Bug 1594589] Re: chromium-browser profile is too noisy for version 50.0.2661.102-0ubuntu0.16.04.1.1237

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

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

  [ Didier Roche ]
  * debian/patches/ubuntu/communitheme-snap-support.patch:
- support communitheme snap (LP: #1762983)

  [ Jamie Strandboge ]
  * debian/patches/ubuntu/add-chromium-browser.patch: adjust for newer
chromium (LP: #1101298, LP: #1594589, LP: #1647142)
- add attach_disconnected
- allow reading /proc/vmstat
- don't require owner match for /proc/pid/{stat,status} and task
  counterparts
- adjust pci[0-9] to be pci[0-9a-f]
- allow reading all uevents and /sys/devices/virtual/tty/tty0/active
- allow ptracing xdgsettings and lsb-release
- xdgsettings uses head and tr and looks at /usr/share/ubuntu/applications/
- lsb-release uses python 3.6 and looks at apport, apt.conf, dpkg and
  distro-info
- use 'm' on on sandbox
  * debian/patches/ubuntu/mimeinfo-snap-support.patch: allow reading
/var/lib/snapd/desktop/applications *.desktop and mimeinfo.cache
(LP: #1712039)

 -- Jamie Strandboge   Tue, 17 Apr 2018 20:15:16 +

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

Title:
  chromium-browser profile is too noisy for version
  50.0.2661.102-0ubuntu0.16.04.1.1237

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Just by running chromium I get these complaints:

  Jun 20 20:53:22 omicron kernel: [69605.494311] audit: type=1400
  audit(1466448802.236:2558): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq"
  pid=23577 comm="chromium-browse" requested_mask="r" denied_mask="r"
  fsuid=1001 ouid=0  Jun 20 20:53:22 omicron kernel:
  [69605.555829] audit: type=1400 audit(1466448802.296:2559):
  apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser
  /chromium-browser" name="/proc/23610/setgroups" pid=23610 comm
  ="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1001
  ouid=1001  Jun 20 20:53:22
  omicron kernel: [69605.555895] audit: type=1400
  audit(1466448802.296:2560): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/proc/23610/uid_map" pid=23610 comm="chromium-browse"
  requested_mask="w" denied_mask="w" fsuid=1001 ouid=1001
  Jun 20 20:53:22 omicron kernel: [69605.555952] audit: type=1400
  audit(1466448802.296:2561): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/proc/23610/gid_map" pid=23610 comm="chromium-browse"
  requested_mask="w" denied_mask="w" fsuid=1001 ouid=1001
  Jun 20 20:53:24 omicron kernel: [69607.268592] audit: type=1400
  audit(1466448804.008:2562): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq"
  pid=23610 comm="chromium-browse" requested_mask="r" denied_mask="r"
  fsuid=1001 ouid=0  Jun 20 20:53:24 omicron kernel:
  [69607.299658] audit: type=1400 audit(1466448804.040:2563):
  apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser
  /chromium-browser" name="/proc/1/stat" pid=23610 comm="chromium-
  browse" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Jun 20 20:53:24 omicron kernel: [69607.341170] audit: type=1400
  audit(1466448804.080:2564): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/proc/23610/setgroups" pid=23610 comm="chromium-browse"
  requested_mask="w" denied_mask="w" fsuid=1001 ouid=1001
  Jun 20 20:53:24 omicron kernel: [69607.341225] audit: type=1400
  audit(1466448804.080:2565): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/proc/23610/gid_map" pid=23610 comm="chromium-browse"
  requested_mask="w" denied_mask="w" fsuid=1001 ouid=1001
  Jun 20 20:53:24 omicron kernel: [69607.341272] audit: type=1400
  audit(1466448804.080:2566): apparmor="ALLOWED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser"
  name="/proc/23610/uid_map" pid=23610 comm="chromium-browse"
  requested_mask="w" denied_mask="w" fsuid=1001 ouid=1001

  I also get very annoying popup notifications for these...

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

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

[Touch-packages] [Bug 1647142] Re: usr.bin.chromium-browser terribly outdated

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

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

  [ Didier Roche ]
  * debian/patches/ubuntu/communitheme-snap-support.patch:
- support communitheme snap (LP: #1762983)

  [ Jamie Strandboge ]
  * debian/patches/ubuntu/add-chromium-browser.patch: adjust for newer
chromium (LP: #1101298, LP: #1594589, LP: #1647142)
- add attach_disconnected
- allow reading /proc/vmstat
- don't require owner match for /proc/pid/{stat,status} and task
  counterparts
- adjust pci[0-9] to be pci[0-9a-f]
- allow reading all uevents and /sys/devices/virtual/tty/tty0/active
- allow ptracing xdgsettings and lsb-release
- xdgsettings uses head and tr and looks at /usr/share/ubuntu/applications/
- lsb-release uses python 3.6 and looks at apport, apt.conf, dpkg and
  distro-info
- use 'm' on on sandbox
  * debian/patches/ubuntu/mimeinfo-snap-support.patch: allow reading
/var/lib/snapd/desktop/applications *.desktop and mimeinfo.cache
(LP: #1712039)

 -- Jamie Strandboge   Tue, 17 Apr 2018 20:15:16 +

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => 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/1647142

Title:
  usr.bin.chromium-browser terribly outdated

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  when using the Chromium Browser, the screen (LXDE) drowns in warning
  messages because of heaps of apparmor profile violations. Unusable
  without intense manual modifications.

  For some strange reason /etc/apparmor.d/usr.bin.chromium-browser is
  over a year old

  -rw-r--r-- 1 root root 8243 Sep  3  2015 usr.bin.chromium-browser

  
  and part of the apparmor-profiles and not of the chromium-package (where it 
would belong to). 

  It seems as if the chromium browser is continuously developed and re-
  compiled with new library versions, while the apparmor profile is
  frozen and noone takes care about, thus things are diverging more and
  more.

  IMHO the profile should be

  a) part of the chromium browser package
  b) maintained (tested) by the same package maintainers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Dec  4 12:44:25 2016
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic 
root=UUID=3e286927-f1b6-4954-8b0d-7cf23484309f ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (242 days ago)

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

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

[Touch-packages] [Bug 1712039] Re: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache

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

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

  [ Didier Roche ]
  * debian/patches/ubuntu/communitheme-snap-support.patch:
- support communitheme snap (LP: #1762983)

  [ Jamie Strandboge ]
  * debian/patches/ubuntu/add-chromium-browser.patch: adjust for newer
chromium (LP: #1101298, LP: #1594589, LP: #1647142)
- add attach_disconnected
- allow reading /proc/vmstat
- don't require owner match for /proc/pid/{stat,status} and task
  counterparts
- adjust pci[0-9] to be pci[0-9a-f]
- allow reading all uevents and /sys/devices/virtual/tty/tty0/active
- allow ptracing xdgsettings and lsb-release
- xdgsettings uses head and tr and looks at /usr/share/ubuntu/applications/
- lsb-release uses python 3.6 and looks at apport, apt.conf, dpkg and
  distro-info
- use 'm' on on sandbox
  * debian/patches/ubuntu/mimeinfo-snap-support.patch: allow reading
/var/lib/snapd/desktop/applications *.desktop and mimeinfo.cache
(LP: #1712039)

 -- Jamie Strandboge   Tue, 17 Apr 2018 20:15:16 +

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

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

Title:
  AppArmor profile misses entry for
  /var/lib/snapd/desktop/applications/mimeinfo.cache

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
  If evince is launched, the following gets logged to syslog:

  kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
  comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  I don't know if this should be allowed or denied. If you could add the
  correct behaviour to the profile, that would be nice; otherwise, every
  time evince is launched, a notification pops up (apparmor-notify
  installed).

  
  (Workaround:

  Add to original profile (/etc/apparmor.d/usr.bin.evince):
#include 

  Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
/var/lib/snapd/desktop/applications/mimeinfo.cache r,
  )

  Release: Ubuntu 16.04.3 LTS
  Package Version: evince-common 3.18.2-1ubuntu4.1

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

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

[Touch-packages] [Bug 1762983] Re: communitheme snap doesn't work with evince

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

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

  [ Didier Roche ]
  * debian/patches/ubuntu/communitheme-snap-support.patch:
- support communitheme snap (LP: #1762983)

  [ Jamie Strandboge ]
  * debian/patches/ubuntu/add-chromium-browser.patch: adjust for newer
chromium (LP: #1101298, LP: #1594589, LP: #1647142)
- add attach_disconnected
- allow reading /proc/vmstat
- don't require owner match for /proc/pid/{stat,status} and task
  counterparts
- adjust pci[0-9] to be pci[0-9a-f]
- allow reading all uevents and /sys/devices/virtual/tty/tty0/active
- allow ptracing xdgsettings and lsb-release
- xdgsettings uses head and tr and looks at /usr/share/ubuntu/applications/
- lsb-release uses python 3.6 and looks at apport, apt.conf, dpkg and
  distro-info
- use 'm' on on sandbox
  * debian/patches/ubuntu/mimeinfo-snap-support.patch: allow reading
/var/lib/snapd/desktop/applications *.desktop and mimeinfo.cache
(LP: #1712039)

 -- Jamie Strandboge   Tue, 17 Apr 2018 20:15:16 +

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

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

Title:
  communitheme snap doesn't work with evince

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  As mentioned on https://github.com/ubuntu/gtk-
  communitheme/issues/325#issuecomment-380383969, evince can't load the
  communitheme snap.

  Indeed, as the directory isn't a standard one (/snap/…), the protected
  applications by apparmor can't load it.

  As the snap is temporary, distro-patch (ubuntu only) common
  abstractions directory for theme and icons (similar than the flatpak
  patches).

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

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

[Touch-packages] [Bug 1765544] [NEW] Ubuntu 17.10 network-manager ingores and overwrites clonned MAC

2018-04-19 Thread George

Public bug reported:

I have installed
network-manager (1.8.4-1ubuntu3) artful;
network-manager-gnome (1.8.4-1ubuntu1) artful;

Also I'm running Ubuntu 17.10 with Xorg.

Problem 1
>From GUI Wired Settings I can't set Cloned MAC Address.
I'm forced to set it manually changing config file with cloned-mac-address that 
I need.
/etc/NetworkManager/system-connections/wiredcon

Problem 2 
After second reboot for some reason Network Manager overwrites my 
cloned-mac-address with defaults NIC address and I can't connect to the 
Internet, because I need my MAC that I set before.

I have participially solved problem by disabling 'connect automatically'
in Wired Settings and after system reboot cloned-mac-address is saved
with what I need and it is not changed and I have connected to Internet.

Problem 3
If I turn on again 'connect automatically' in Wired Settings the 
cloned-mac-address is overwritten
again by default NIC address and I can't connect to Internet.

So I can't change MAC address from GUI interface and I can't use
Internet auto connect option.

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


** Tags: mac-address network-manager ubuntu-17.10

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

Title:
  Ubuntu 17.10 network-manager ingores and overwrites clonned MAC

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have installed
  network-manager (1.8.4-1ubuntu3) artful;
  network-manager-gnome (1.8.4-1ubuntu1) artful;

  Also I'm running Ubuntu 17.10 with Xorg.

  Problem 1
  From GUI Wired Settings I can't set Cloned MAC Address.
  I'm forced to set it manually changing config file with cloned-mac-address 
that I need.
  /etc/NetworkManager/system-connections/wiredcon

  Problem 2 
  After second reboot for some reason Network Manager overwrites my 
cloned-mac-address with defaults NIC address and I can't connect to the 
Internet, because I need my MAC that I set before.

  I have participially solved problem by disabling 'connect
  automatically' in Wired Settings and after system reboot cloned-mac-
  address is saved with what I need and it is not changed and I have
  connected to Internet.

  Problem 3
  If I turn on again 'connect automatically' in Wired Settings the 
cloned-mac-address is overwritten
  again by default NIC address and I can't connect to Internet.

  So I can't change MAC address from GUI interface and I can't use
  Internet auto connect option.

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

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

[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2018-04-19 Thread Andrew

Is this the same as bug 1755305?

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

Title:
  nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET
  (widget)' failed

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  running 18.04 this message is spamming into syslog:
  > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' 
failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.8.4-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Feb 26 01:16:49 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (1611 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 proto static metric 600 
   169.254.0.0/16 dev wlan1 scope link metric 1000 
   192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago)
  
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan1  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  k2l 
7df024b1-9b89-4f95-84c1-03188bb67f77  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:02:17:7D  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 -- 
   eth1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1765531] [NEW] python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: ordinal not in range(128)

2018-04-19 Thread Battant

Public bug reported:

Hello,

I have eclipse 4.7

https://www.eclipse.org/downloads/


vim

and openjdk-8-jre

I just try to install eclim

http://eclim.org/

Here us my install process log

./eclim_2.7.2.bin 
Welcome to the installer for eclim 2.7.2.

Please specify the root directory of your eclipse install.
  Ex: /opt/eclipse
  /usr/local/eclipse


Please specify the directory where you would like the eclim vimfiles installed.
If you do not want to install the vimfiles (eg: emacs-eclim users), then type: 
skip
  Ex: ~/.vim
  ~/.vim/bundle/eclim
> ../.vim

Choose which eclim features you would like to install.
Type the number for each feature you want to install:
  Ex (Java and Python): 0 5
  Ex (Java and Python): 0,5
  Ex (Java, Web, and C/C++): 0-2
0) Java Development
1) Web Development
2) C/C++ Development
3) Ruby Development
4) Php Development
5) Python Development
6) Scala Development
7) Groovy Development
8) Android Development
> 5
Eclim plugins to install:
  Python Development
Is this correct? (y/n): y

running: ['java', '-Djava.net.useSystemProxies=true', '-jar', 
'/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar',
 '-initialize', '-debug'] ... Traceback (most recent call last):
  File "/tmp/eclim-installer.6Bte/install", line 1205, in 
main()
  File "/tmp/eclim-installer.6Bte/install", line 96, in main
install(options, eclim)
  File "/tmp/eclim-installer.6Bte/install", line 116, in install
step_dependencies(options, eclipse, plugins)
  File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies
eclipse.gc()
  File "/tmp/eclim-installer.6Bte/install", line 921, in gc
'-application', 'org.eclipse.equinox.p2.garbagecollector.application',
  File "/tmp/eclim-installer.6Bte/install", line 929, in execute
self._initialize()
  File "/tmp/eclim-installer.6Bte/install", line 900, in _initialize
info = self.execute('-initialize', '-debug')
  File "/tmp/eclim-installer.6Bte/install", line 936, in execute
stdout, stderr = execute(cmd)
  File "/tmp/eclim-installer.6Bte/install", line 624, in execute
stdout = stdout.decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: 
ordinal not in range(128)

Could you help me please to fix this bug ?

Thanks by advance for your support

Best regards

Battant

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python2.7 2.7.15~rc1-1
ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
Uname: Linux 4.15.0-17-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 19 23:48:56 2018
SourcePackage: python2.7
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
  position 56: ordinal not in range(128)

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Hello,

  I have eclipse 4.7

  https://www.eclipse.org/downloads/

  
  vim

  and openjdk-8-jre

  I just try to install eclim

  http://eclim.org/

  Here us my install process log

  ./eclim_2.7.2.bin 
  Welcome to the installer for eclim 2.7.2.

  Please specify the root directory of your eclipse install.
Ex: /opt/eclipse
/usr/local/eclipse

  
  Please specify the directory where you would like the eclim vimfiles 
installed.
  If you do not want to install the vimfiles (eg: emacs-eclim users), then 
type: skip
Ex: ~/.vim
~/.vim/bundle/eclim
  > ../.vim

  Choose which eclim features you would like to install.
  Type the number for each feature you want to install:
Ex (Java and Python): 0 5
Ex (Java and Python): 0,5
Ex (Java, Web, and C/C++): 0-2
  0) Java Development
  1) Web Development
  2) C/C++ Development
  3) Ruby Development
  4) Php Development
  5) Python Development
  6) Scala Development
  7) Groovy Development
  8) Android Development
  > 5
  Eclim plugins to install:
Python Development
  Is this correct? (y/n): y

  running: ['java', '-Djava.net.useSystemProxies=true', '-jar', 
'/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar',
 '-initialize', '-debug'] ... Traceback (most recent call last):
File "/tmp/eclim-installer.6Bte/install", line 1205, in 
  main()
File "/tmp/eclim-installer.6Bte/install", line 96, in main
  install(options, eclim)
File "/tmp/eclim-installer.6Bte/install", line 116, in install
  step_dependencies(options, eclipse, plugins)
File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies
  eclipse.gc()

[Touch-packages] [Bug 1513364] Re: valgrind-python.supp is outdated

This bug was fixed in the package python3-defaults - 3.6.5-3

---
python3-defaults (3.6.5-3) unstable; urgency=medium

  * Update valgrind support file. LP: #1513364.
  * debian/control.in (Michael Vogt):
- add Cnf-Visible-Pkgname hint to ensure command-not-found recommends
  installing "python3" instead of "python3-minimal" when it is missing.

 -- Matthias Klose   Tue, 10 Apr 2018 11:48:03 +0200

** Changed in: python3-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  valgrind-python.supp is outdated

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  While investigating bug 1512622 I decided to look if there's a
  /usr/lib/valgrind/python3.supp, and if it suffers from the same
  problem.

  I found it in python3-defaults, and it suffers from worse:

  - talks about python2.4
  - doesn't have all the suppressions from upstream
  - the suppressions it has are for 32-bit systems only

  This should be probably forwarded to Debian.

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

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

[Touch-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2018-04-19 Thread Bug Watch Updater

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

** Changed in: pulseaudio
   Importance: Unknown => Medium

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

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

[Touch-packages] [Bug 1762200] Re: nvidia detects 2 screen but there is no 2 screen

2018-04-19 Thread Ahmet Aksoy

I found the fix/solution; i tryed delete unknown screen(CRT-0) from 
nvidia-settings but its shows "Failed to generate X config file!" and i checked 
/etc/x11, xorg.conf was missing
So, i copied my 17.10 xorg.conf to 18.04 now its working i can see gdm greeter 

Also, this line caught my attention(xorg.conf line:30)  
Option "IgnoreDisplayDevices" "CRT"



~$ nvidia-settings

(nvidia-settings:18214): dbind-WARNING **: 23:26:48.227: Couldn't
register with accessibility bus: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the message
bus security policy blocked the reply, the reply timeout expired, or the
network connection was broken.

** (nvidia-settings:18214): WARNING **: 23:26:48.468: PRIME: Failed to execute 
child process “/usr/bin/prime-supported” (No such file or directory)
** Message: 23:26:48.468: PRIME: is it supported? no

WARNING:  Unable to parse X.Org version string.

Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found

ERROR: Unable to find a display device for screen 0!

ERROR: Failed to add X screen 0 to X config.

ERROR: Failed to add X screens to X config.


** Summary changed:

- nvidia detects 2 screen but there is no 2 screen
+ [xorg.conf missing]nvidia detects 2 screen but there is no 2 screen

** Also affects: xorg (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/1762200

Title:
  [xorg.conf missing]nvidia detects 2 screen but there is no 2 screen

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  System: Ubuntu 18.04 (08.04.2018 updated)
  PC: Dell inspiron n5110 laptop
  CPU: intel i7 2630QM
  GPU: nvidia gt 525m

  i installed latest nvidia driver, but driver detects 2 screen. bad thing is 
gdm, i can't see gdm dialogs only purple background. dialogs in 
primary(unknown) screen
  pls check screenshot

  U1804PC:~$ lspci
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 8 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 
525M] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio 
Controller (rev a1)
  05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI 
Express Fast/Gigabit Ethernet controller (rev 05)
  09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 
[Rainbow Peak] (rev 34)
  0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)
  U1804PC:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1762200/+subscriptions

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

[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

2018-04-19 Thread Norbert

Dear Sean!

I did installation as your wrote in comment 14.
I started with latest mini.iso from 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/
 .
Then selected *Xubuntu desktop* in tasksel. Here I got exactly the same result 
as your wrote. So no problem here. Such system has 1584 packages.

---

But if install only base system from mini.iso and then run `sudo apt-get 
install xubuntu-desktop` I get a lot stuff (including `gnome-control-center`) - 
so it is bad variant.
So there is something wrong with handling of `APT::Install-Recommends` and/or 
`APT::Install-Suggests` in APT regarding `xubuntu-desktop` meta-package.

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764108] Re: A lots of errors after install gnome-desktop

2018-04-19 Thread Steve Beattie

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  A lots  of errors after install gnome-desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  Frist, thanks for all ubuntu's team for their great efforts in developing 
this awesome os & platform. 
  after install gnome3 desktop beside xfce4 in ubuntu-studio 16,04 .
  I faced a lot of errors such in gnome-tweak ubuntu-tweak and many other 
issues about more than 10 systemd-crash-notification at every start-up. all of 
them related to sh -e /proc/self/fd/9
  I know that many of those back to being a beginner with ubuntu .so I could be 
grateful if someone help to solve those issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 15 13:31:29 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Tonga PRO [Radeon R9 
285/380] [174b:e306]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=2fab0ad1-9fc6-4072-8130-62b13bbb8f0e rw pci=nomsi drm.debug=0x4 
plymouth:debug modprobe radeon VIDEO_CARDS= amdgpu radeonsi radeon 
radeon.agpmode=-1 radeon.modeset=1 radeon.dpm=-1 radeon.runpm=-1 radeon.uvd=1 
radeon.vce=1 pci=nomsi amdgpu.si_support=1 amdgpu.cik_support=0 
radeon.si_support=0 radeon.cik_support=1 vblank_mode=1 glxgears
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1~xenial
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91+git1804061830.cb850c~oibaf~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1804140730.6a519a~oibaf~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1804140730.6a519a~oibaf~x
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.1+git1803151933.fdba53~oibaf~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1803090733.ac8f7b~oibaf~x
  xserver.bootTime: Sun Apr 15 13:11:40 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1763710] Re: lightdm-gnome-gdm not working

2018-04-19 Thread Steve Beattie

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  lightdm-gnome-gdm not working

Status in xorg package in Ubuntu:
  New

Bug description:
  lightdm-gnome-gdm not working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr 13 19:04:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 5.1.34, 4.13.0-37-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.13.0-38-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.15.0-13-generic, x86_64: installed
   virtualbox-guest, 5.1.34, 4.4.0-119-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. G84 [GeForce 8600 GT] [1043:8243]
  InstallationDate: Installed on 2017-11-06 (158 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer P5K SE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=27389c94-1e8b-4c77-9bc7-c34de7e09ec2 ro splash plymouth:debug quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/31/2007:svnSystemmanufacturer:pnP5KSE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K SE
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 10 19:10:04 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver MOUSE, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLITEON Technology USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1764423] Re: package base-files 9.4ubuntu4 failed to install/upgrade: paketas base-files neparuoštas konfigūravimui negaliu konfigūruoti (dabartinė būsena `half-installed')

2018-04-19 Thread Steve Beattie

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package base-files 9.4ubuntu4 failed to install/upgrade: paketas base-
  files neparuoštas konfigūravimui  negaliu konfigūruoti (dabartinė
  būsena `half-installed')

Status in base-files package in Ubuntu:
  New

Bug description:
  can't intall updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: base-files 9.4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Apr 15 14:40:26 2018
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package base-files (--configure):
paketas base-files neparuoštas konfigūravimui
negaliu konfigūruoti (dabartinė būsena `half-installed')
  ErrorMessage: paketas base-files neparuoštas konfigūravimui  negaliu 
konfigūruoti (dabartinė būsena `half-installed')
  InstallationDate: Installed on 2016-03-19 (758 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: base-files
  Title: package base-files 9.4ubuntu4 failed to install/upgrade: paketas 
base-files neparuoštas konfigūravimui  negaliu konfigūruoti (dabartinė būsena 
`half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-08-11 (612 days ago)

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

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

[Touch-packages] [Bug 1765230] Re: Immediate logout when using Chrome (and not only it)

2018-04-19 Thread Vlad Myachikov

Here are the main syslog lines when it happens:
Apr 19 22:52:00 vladiat0r dbus-daemon[929]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.97' (uid=1000 
pid=2112 comm="/opt/google/chrome/chrome " label="unconfined")
Apr 19 22:52:00 vladiat0r systemd[1]: Starting Hostname Service...
Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]: XIO:  fatal IO error 11 (Resource 
temporarily unavailable) on X server ":0"
Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]:   after 6865 requests (6865 
known processed) with 0 events remaining.
Apr 19 22:52:00 vladiat0r org.kde.kuiserver[1158]: kuiserver: Fatal IO error: 
client killed

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

Title:
  Immediate logout when using Chrome (and not only it)

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes when I open a new tab or start downloading a file with the
  Chrome browser, the system logs me out.  Then this problem persists so
  that I'm logged out very fast, and only reboot helps. Starting Firefox
  after the first crash also leads to logout. What exact information can
  I provide (some logs etc)? Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Apr 19 01:56:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 17.40-492261: added
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3418]
  InstallationDate: Installed on 2018-04-11 (7 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3806
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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 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-1ubuntu3
  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/1765230/+subscriptions

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

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

2018-04-19 Thread Dylan Borg

This is causing havoc! People installing .NET Core which depends on
libcurl3 cannot install cmake that is depending on libcurl4. The
nomenclature of these packages implies that they should be installable
side by side.

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

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

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

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

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

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

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

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

2018-04-19 Thread Seth Arnold

Here's the thread on debian-devel that describes the motivation for the
change:

https://lists.debian.org/debian-devel/2018/04/msg00058.html

Thanks

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  Confirmed
Status in ca-certificates package in Debian:
  Unknown

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

Note: GnuCash 3.0, when built from source, does not display the toolbar
correctly either.

When I run GtkInspector on GnuCash 3.0 (can't do it on Gnucash 2.7.19
because it's only available in gtk3) and examine the GtkSettings object,
it says that gtk-toolbar-style is set to both, as expected.

However, when I examine the toolbar-style setting on the GtkToolbar
object itself within GtkInspector, it has the wrong value, i.e., it's
value doesn't match what's in the GtkSettings object _on the same
process_.

Honestly, I have no idea WTF is going on here. I'm totally mystified,
and I've wasted most of a day trying to get to the bottom of this.

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

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions

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

[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-04-19 Thread Phillip Susi

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

** This bug has been marked a duplicate of bug 1652282
   Xwayland not using XAUTHORITY, prevents root applications from connecting

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765479] Re: In ubuntu 18.04, when I unplug the screen cable, the user session close's

2018-04-19 Thread مالك ب

** Description changed:

  I have submitted the first rapport yesterday, at the following link:
  https://bugs.launchpad.net/ubuntu/+bug/1765160
  And after the first reply from
  Ubuntu Foundations Team Bug Bot (crichton)
  I go to the page provided in this automated reply:
  https://wiki.ubuntu.com/Bugs/FindRightPackage
  and from this page I go to the following pages and I apply the step that 
match this case.
  https://wiki.ubuntu.com/X/Backtracing
  https://wiki.ubuntu.com/Apport
  https://wiki.ubuntu.com/Apport/DeveloperHowTo
  https://help.ubuntu.com/community/ReportingBugs
  https://help.ubuntu.com/community/DebuggingSystemCrash
   After I read the step described in these pages
  I run the following command in konsole (as root)
  ubuntu-bug xorg
- I click on submit, and then it take to this page.
+ I click on submit, and then it take me to this page.
  In the description I have done yesterday, i wrote:
- Hello.
+ "Hello.
  If I unplug the cable of the screen when I am logged to my user session in 
ubuntu 18.04, and then I plug again the cable of the screen, I found my session 
closed, and when I login again to my user session, I found all previous running 
programs closed.
  This bug reproduce every time I unplug the cable screen from the unit.
  what I expect: when I plug the screen cable to the unit, I must find my 
session open as I let it, and programs that were running still open or running
  What happened: after I plug the cable screen to the unit, i find my session 
and all programs closed, and when I login again to my account session, I find 
all previous programs closed.
  Distro: Ubuntu Bionic Beaver (development branch)
  CPU: Intel® Pentium(R) CPU G645 @ 2.90GHz × 2
  Graphic: Intel® Sandybridge Desktop
  Gnome: 3.28.1
  OS type: 64 bit
- If there is any other information needed to help solving this bug that i must 
submit, just let me know it.
+ If there is any other information needed to help solving this bug that i must 
submit, just let me know it."
  And today, I have included
  _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, 
text/plain)
  And I submit it again now
  Please tell me were I must continue with this bug, at this page or the 
previous (https://bugs.launchpad.net/ubuntu/+bug/1765160) or both of them, or 
it will be merged automatically
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Apr 19 11:08:03 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
  InstallationDate: Installed on 2018-03-18 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=ar_DZ:ar
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ar_DZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=18c8c08f-eab6-491b-b3aa-b8b9a415e1f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: H61M-HVS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd09/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-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

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

Title:
  In ubuntu 18.04,when I

[Touch-packages] [Bug 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts

2018-04-19 Thread uDude

I vote that this bug be closed based on #32, dnsmasq is fully
controllable.

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

Title:
Please make NetworkManager-controlled dnsmasq respect /etc/hosts

Status in network-manager package in Ubuntu:
Confirmed

Bug description:
Since 12.04 NetworkManager uses the dnsmasq plugin by default to
resolve DNS requests. Unfortunately the dnsmasq plug-in has --no-
hosts, etc. hard coded [1] which means (among other things) that after
the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS
requests. This changes the prior behavior of NetworkManager without
any visible warning to the end user. AFAICS there's no other way to
work around this problem as to manually revert the change and disable
the dnsmasq plug-in in the NetworkManager config, see [2,3]:

"To turn off dnsmasq in Network Manager, you need to edit
/etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq'
line then do a 'sudo restart network-manager'."

This is of course not a bug in the NetworkManager which just behaves
as intended. The problem is in the change of the configuration of the
Ubuntu packaging which will probably leave many wondering why their
/etc/hosts suddenly no longer works. This cost me considerable time to
debug and probably is a usability problem for others, too.

Maybe you could provide a more visible documentation than that in [3]?
E.g., *including a comment in /etc/hosts that explains the change* and
how to work around it would have saved me a lot of time. It would have
automatically alerted me on upgrade as manual changes to /etc/hosts
would then have triggered a prompt while leaving those users with
standard /etc/hosts in peace.

Probably similar problems arise with other disabled config files and
could be alerted to the users? Thinking of resolv.conf, etc.

[1]
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c,
line 285
[2] i.e. http://ubuntuforums.org/showthread.php?t=1968061
[3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/

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

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

[Touch-packages] [Bug 1576432] Re: gdb crashes when trying to start a debugging session

2018-04-19 Thread Seth Arnold

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

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

Title:
  gdb crashes when trying to start a debugging session

Status in gdb:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This bug log applies to Ubuntu Mate for raspberry PI.

  I cannot use gdb to debug a program. See below. This happens on any
  program, even programs that come with ubuntu, for example try gdb
  /bin/less. It always crashes in  d-linux-armhf.so.3

  gdb mythfrontend
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from mythfrontend...done.
  (gdb) start
  Temporary breakpoint 1 at 0x62c22: file main.cpp, line 1674.
  Starting program: 
/srv/storage/homexenial/peter/proj/mythtv-build/myth-p28/usr/bin/mythfrontend

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

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

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

[Touch-packages] [Bug 1765479] Re: In ubuntu 18.04, when I unplug the screen cable, the user session close's

2018-04-19 Thread مالك ب

** Description changed:

- I have submited the first rapport yesterday, at the following link:
+ I have submitted the first rapport yesterday, at the following link:
  https://bugs.launchpad.net/ubuntu/+bug/1765160
- And after the first reply from 
- Ubuntu Foundations Team Bug Bot (crichton) 
+ And after the first reply from
+ Ubuntu Foundations Team Bug Bot (crichton)
  I go to the page provided in this automated reply:
  https://wiki.ubuntu.com/Bugs/FindRightPackage
  and from this page I go to the following pages and I apply the step that 
match this case.
  https://wiki.ubuntu.com/X/Backtracing
  https://wiki.ubuntu.com/Apport
  https://wiki.ubuntu.com/Apport/DeveloperHowTo
  https://help.ubuntu.com/community/ReportingBugs
  https://help.ubuntu.com/community/DebuggingSystemCrash
-  After the step I described in 
+  After I read the step described in these pages
  I run the following command in konsole (as root)
  ubuntu-bug xorg
  I click on submit, and then it take to this page.
  In the description I have done yesterday, i wrote:
  Hello.
  If I unplug the cable of the screen when I am logged to my user session in 
ubuntu 18.04, and then I plug again the cable of the screen, I found my session 
closed, and when I login again to my user session, I found all previous running 
programs closed.
  This bug reproduce every time I unplug the cable screen from the unit.
  what I expect: when I plug the screen cable to the unit, I must find my 
session open as I let it, and programs that were running still open or running
  What happened: after I plug the cable screen to the unit, i find my session 
and all programs closed, and when I login again to my account session, I find 
all previous programs closed.
  Distro: Ubuntu Bionic Beaver (development branch)
  CPU: Intel® Pentium(R) CPU G645 @ 2.90GHz × 2
  Graphic: Intel® Sandybridge Desktop
  Gnome: 3.28.1
  OS type: 64 bit
  If there is any other information needed to help solving this bug that i must 
submit, just let me know it.
- And today, I have included 
- _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, 
text/plain) 
+ And today, I have included
+ _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, 
text/plain)
  And I submit it again now
  Please tell me were I must continue with this bug, at this page or the 
previous (https://bugs.launchpad.net/ubuntu/+bug/1765160) or both of them, or 
it will be merged automatically
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Apr 19 11:08:03 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
  InstallationDate: Installed on 2018-03-18 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  LANGUAGE=ar_DZ:ar
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=ar_DZ.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=ar_DZ:ar
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=ar_DZ.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=18c8c08f-eab6-491b-b3aa-b8b9a415e1f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: H61M-HVS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd09/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-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

[Touch-packages] [Bug 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts

2018-04-19 Thread Michael Kyle

I found a solution on stackoverflow thanks to @kbenoit there.

https://askubuntu.com/questions/117899/configure-networkmanagers-
dnsmasq-to-use-etc-hosts

This is not really a bug at all. You just have to configure stuff under
/etc/NetworkManager/dnsmasq.d instead, e.g.,

# echo "addn-hosts=/etc/hosts" > /etc/NetworkManager/dnsmasq.d/hosts.conf
# service network-manager restart

I will point out the following statement from the networkmanager.conf
man page ON THE GNOME WEBSITE (not on the ubuntu 16.04 man page):

It is possible to pass custom options to the dnsmasq instance by adding
them to files in the "/etc/NetworkManager/dnsmasq.d/" directory.

Add any options you want.

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

Title:
Please make NetworkManager-controlled dnsmasq respect /etc/hosts

Status in network-manager package in Ubuntu:
Confirmed

"To turn off dnsmasq in Network Manager, you need to edit
/etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq'
line then do a 'sudo restart network-manager'."

Probably similar problems arise with other disabled config files and
could be alerted to the users? Thinking of resolv.conf, etc.

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

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

[Touch-packages] [Bug 1765477] [NEW] 5s delay in AAAA dns resolving; artful and earlier is quick

2018-04-19 Thread Andreas Hasenack

Public bug reported:

Basic steps:
lxc launch ubuntu-daily:bionic bionic-daily
lxc exec bionic-daily bash
sleep 10s (because of #1765173)
time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

In bionic, there is a 5s delay when requesting the  record:


root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
Trying "wondrous-grackle.lxd"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;wondrous-grackle.lxd.  IN  A

;; ANSWER SECTION:
wondrous-grackle.lxd.   0   IN  A   10.0.100.125

Received 54 bytes from 127.0.0.53#53 in 0 ms
Trying "wondrous-grackle.lxd"

(5s delay here)


;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;wondrous-grackle.lxd.  IN  

Received 38 bytes from 127.0.0.53#53 in 1 ms
Trying "wondrous-grackle.lxd"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;wondrous-grackle.lxd.  IN  MX

Received 38 bytes from 127.0.0.53#53 in 0 ms

real0m5.023s


In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

See https://pastebin.ubuntu.com/p/KP5DBcKyJr/


In both cases, /etc/resolv.conf points at 127.0.0.53


systemd version:
 *** 237-3ubuntu8 500
500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  New

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()

2018-04-19 Thread Apport retracing service

** Tags added: bionic

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

Title:
  tracker-extract crashed with signal 31 in chdir()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  tracker crash while indexing my homedir

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-extract 1.12.0-0ubuntu1
  Uname: Linux 4.10.8-041008-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  8 14:00:45 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-extract
  ExecutableTimestamp: 1490023113
  JournalErrors:
   No journal files were found.
   -- No entries --
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcCwd: /home/bonnaudl
  Signal: 31
  SourcePackage: tracker
  Title: tracker-extract crashed with signal 31 in chdir()
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

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

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

[Touch-packages] [Bug 1765479] [NEW] In ubuntu 18.04, when I unplug the screen cable, the user session close's

2018-04-19 Thread مالك ب

Public bug reported:

I have submited the first rapport yesterday, at the following link:
https://bugs.launchpad.net/ubuntu/+bug/1765160
And after the first reply from 
Ubuntu Foundations Team Bug Bot (crichton) 
I go to the page provided in this automated reply:
https://wiki.ubuntu.com/Bugs/FindRightPackage
and from this page I go to the following pages and I apply the step that match 
this case.
https://wiki.ubuntu.com/X/Backtracing
https://wiki.ubuntu.com/Apport
https://wiki.ubuntu.com/Apport/DeveloperHowTo
https://help.ubuntu.com/community/ReportingBugs
https://help.ubuntu.com/community/DebuggingSystemCrash
 After the step I described in 
I run the following command in konsole (as root)
ubuntu-bug xorg
I click on submit, and then it take to this page.
In the description I have done yesterday, i wrote:
Hello.
If I unplug the cable of the screen when I am logged to my user session in 
ubuntu 18.04, and then I plug again the cable of the screen, I found my session 
closed, and when I login again to my user session, I found all previous running 
programs closed.
This bug reproduce every time I unplug the cable screen from the unit.
what I expect: when I plug the screen cable to the unit, I must find my session 
open as I let it, and programs that were running still open or running
What happened: after I plug the cable screen to the unit, i find my session and 
all programs closed, and when I login again to my account session, I find all 
previous programs closed.
Distro: Ubuntu Bionic Beaver (development branch)
CPU: Intel® Pentium(R) CPU G645 @ 2.90GHz × 2
Graphic: Intel® Sandybridge Desktop
Gnome: 3.28.1
OS type: 64 bit
If there is any other information needed to help solving this bug that i must 
submit, just let me know it.
And today, I have included 
_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, 
text/plain) 
And I submit it again now
Please tell me were I must continue with this bug, at this page or the previous 
(https://bugs.launchpad.net/ubuntu/+bug/1765160) or both of them, or it will be 
merged automatically

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
Uname: Linux 4.15.0-17-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CompositorRunning: None
Date: Thu Apr 19 11:08:03 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
InstallationDate: Installed on 2018-03-18 (31 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=ar_DZ:ar
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ar_DZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=18c8c08f-eab6-491b-b3aa-b8b9a415e1f8 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.50
dmi.board.name: H61M-HVS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd09/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash"
   
https://bugs.launchpad.net/bugs/1765479/+attachment/5122845/+files/_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash

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

Title:
  In ubuntu 18.04,when I unplug the screen cable, the user

[Touch-packages] [Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

More info... I've confirmed that on 17.10, the toolbar style is
controlled by /org/gnome/desktop/interface/toolbar-style. When I edit
that setting in dconf-editor in 17.10, the change is reflected in the
open GnuCash window, but when I edit that exact same setting in dconf-
editor in 18.04, it has no effect on the open GnuCash window.

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

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-04-19 Thread Daniel Holbert

Filed upstream: https://github.com/ibus/ibus/issues/2002

** Bug watch added: github.com/ibus/ibus/issues #2002
   https://github.com/ibus/ibus/issues/2002

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-04-19 Thread Daniel Holbert

> the bug might be better placed on https://github.com/ibus/ibus/issues
instead.

Thanks -- I'll file an issue there, too, later today. (I wish I knew how
to test old ibus builds & bisect between them so that I could extra-
confirm that it was an ibus change that broke this, and perhaps bisect
to find out which change...)

> So you only get the issue if GTK_IM_MODULE=ibus?

Correct. (And unfortunately, that's the default value. So I "only" get
it by default. :))

> What happens if you "unset GTK_IM_MODULE" and start firefox?

Then the issue does not happen.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2018-04-19 Thread Łukasz Zemczak

Hello Eloy, or anyone else affected,

Accepted ifupdown into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.10ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Committed
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Original test case, before dhclient was fixed:
  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 
dhcp) and reboot. It will fail to get a dhcp address during boot.

  New test case, showing failure when using dhclient in 'stateless' mode:
  Configure ifupdown like:

  auto eth0
  iface eth0 inet6 auto
    dhcp 1

  When eth0 is down, run 'sudo ifup eth0', and it will fail as dhclient
  fails to start on the interface.

  [Regression Potential]

  As this modifies the wait-for-dad function, its potential for
  regression is to introduce failures in starting dhclient, possibly by
  failing to wait for DAD to complete or due to some other failure in
  the wait for dad function.

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

This bug was fixed in the package systemd - 204-5ubuntu20.28

---
systemd (204-5ubuntu20.28) trusty; urgency=medium

  * logind: fix memleaks in session's free path and cgmanager glue code
(LP: #1750013)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Tue, 03 Apr 2018
13:38:08 +

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

[Touch-packages] [Bug 1765196] Re: 4.4.0-119-generic boot error - systemd[1]: Failed to start Load Kernel Modules.

2018-04-19 Thread Galen Thurber

solved by adding
linux-image-extra-(119)-generic package


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

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

Title:
  4.4.0-119-generic boot error - systemd[1]: Failed to start Load Kernel
  Modules.

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Boot up errors.
  System is reporting
  dmesg error
  # systemd[1]: Failed to start Load Kernel Modules.

  Video and WIFI are affected.
  Hard drive is not full.

  
  Xubuntu 16.04 LTS
  lsb_release
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch

  
  Reinstalling kernel via synaptic does not fix the problem

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

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

[Touch-packages] [Bug 1750013] Update Released

2018-04-19 Thread Łukasz Zemczak

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

[Touch-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2018-04-19 Thread Amr Ibrahim

** Bug watch added: freedesktop.org Bugzilla #106138
   https://bugs.freedesktop.org/show_bug.cgi?id=106138

** Also affects: pulseaudio via
   https://bugs.freedesktop.org/show_bug.cgi?id=106138
   Importance: Unknown
   Status: Unknown

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

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

[Touch-packages] [Bug 1765463] Re: Bionic: systemd: rename interface

systemd.network is working

cat /etc/systemd/network/uplink0.network 
[Match]
Path=pci-:02:00.0
#Name=uplkink0

[Network]
DHCP=yes

networkctl status eno1
 Path: pci-:02:00.0

This was no solution:
cp /etc/systemd/netword/uplink0.link /lib/systemd/network/
update-initramfs -u


** Description changed:

  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  2) apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu8
+   Installed: 237-3ubuntu8
  
  3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18
  
  /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT=""
  GRUB_CMDLINE_LINUX=""
  
- 
- /etc/systemd/networ/uplink0.link 
+ /etc/systemd/netword/uplink0.link
  [Match]
  Path=pci-:02:00.0
  
  [Link]
  Name=uplink0
  
  # update-initramfs -u
  
- 4) journalctl -b | grep rename 
+ 4) journalctl -b | grep rename
  kernel: tg3 :02:00.1 eno2: renamed from eth1
  kernel: tg3 :02:00.0 eno1: renamed from eth0

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

Title:
  Bionic: systemd: rename interface

Status in systemd package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu8

  3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

  /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT=""
  GRUB_CMDLINE_LINUX=""

  /etc/systemd/netword/uplink0.link
  [Match]
  Path=pci-:02:00.0

  [Link]
  Name=uplink0

  # update-initramfs -u

  4) journalctl -b | grep rename
  kernel: tg3 :02:00.1 eno2: renamed from eth1
  kernel: tg3 :02:00.0 eno1: renamed from eth0

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

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

[Touch-packages] [Bug 1765463] [NEW] Bionic: systemd: rename interface

Public bug reported:

1) lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

2) apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu8

3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""


/etc/systemd/networ/uplink0.link 
[Match]
Path=pci-:02:00.0

[Link]
Name=uplink0

# update-initramfs -u

4) journalctl -b | grep rename 
kernel: tg3 :02:00.1 eno2: renamed from eth1
kernel: tg3 :02:00.0 eno1: renamed from eth0

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


** Tags: kernel networ

** Package changed: linux-hwe-edge (Ubuntu) => systemd (Ubuntu)

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

Title:
  Bionic: systemd: rename interface

Status in systemd package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu8

  3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

  /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT=""
  GRUB_CMDLINE_LINUX=""

  
  /etc/systemd/networ/uplink0.link 
  [Match]
  Path=pci-:02:00.0

  [Link]
  Name=uplink0

  # update-initramfs -u

  4) journalctl -b | grep rename 
  kernel: tg3 :02:00.1 eno2: renamed from eth1
  kernel: tg3 :02:00.0 eno1: renamed from eth0

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

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

[Touch-packages] [Bug 1765463] [NEW] Bionic: systemd: rename interface

You have been subscribed to a public bug:

1) lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

2) apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu8

3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""


/etc/systemd/networ/uplink0.link 
[Match]
Path=pci-:02:00.0

[Link]
Name=uplink0

# update-initramfs -u

4) journalctl -b | grep rename 
kernel: tg3 :02:00.1 eno2: renamed from eth1
kernel: tg3 :02:00.0 eno1: renamed from eth0

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


** Tags: kernel networ
-- 
Bionic: systemd: rename interface
https://bugs.launchpad.net/bugs/1765463
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

Two additional notes:

1) This is not GnuCash-specific. You can see the same behavior in the
gtk-demo app included in gtk2.0-examples.

2) If I SSH into my Bionic box from a computer that's still on 17.10 and
run GnuCash on my 17.10 display over the X connection forwarded by SSH,
the toolbar are large and have labels.

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

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions

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

Re: [Touch-packages] [Bug 1726912] Re: fails to keep dhcplease

2018-04-19 Thread Jon Proulx

I can confirm this works in Bionic so close away

thanks,
-jon

On Tue, Apr 17, 2018, 4:11 PM Mathieu Trudel-Lapierre 
wrote:

> This would be a systemd-networkd bug, which I suspect might have already
> been fixed too. Reassigning to systemd.
>
> ** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1726912
>
> Title:
>   fails to keep dhcplease
>
> Status in systemd package in Ubuntu:
>   New
>
> Bug description:
>   Not 100% sure if this is a networkd bug or a nplan bug, but...
>
>   On new install of 17.10 systemd-networkd loops with:
>
>   Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
>   Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained
> IPv6LL
>   Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
>   Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
>   Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained
> carrier
>   Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4
> address 128.30.3.94/24 via 12
>   Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname:
> The name org.freedesktop
>   Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
>   Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease
> lost
>   Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained
> carrier
>   Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4
> address 128.30.3.94/24 via 12
>   Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname:
> The name org.freedesktop
>   Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
>   Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
>   Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease
> lost
>
>   that is the correct interface and address.
>
>   If I manually run 'dhclient nep129s0f0' the lease sticks and
>   'journalctl -fu systemd-networkd' shows:
>
>   Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained
> carrier
>   Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4
> address 128.30.3.94/24 via 12
>   Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname:
> The name org.freedesktop
>   Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured
>
>   installer generated 01-netcfg.yaml:
>
>   network:
> version: 2
> renderer: networkd
> ethernets:
>   enp129s0f0:
> dhcp4: yes
>
>   root@host:~#  lsb_release -rd;uname -r ; dpkg -l nplan  systemd
>   Description:  Ubuntu 17.10
>   Release:  17.10
>   4.13.0-16-generic
>   Desired=Unknown/Install/Remove/Purge/Hold
>   |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>   |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>   ||/ Name   VersionArchitecture   Description
>
> +++-==-==-==-=
>   ii  nplan  0.30   amd64  YAML network
> configuration abstraction fo
>   ii  systemd234-2ubuntu12  amd64  system and service
> manager
>
>
>   my current workaround:
>
>   root@host:~# cat /etc/rc.local
>   #!/bin/sh
>   dhclient enp129s0f0
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726912/+subscriptions
>

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

Title:
  fails to keep dhcplease

Status in systemd package in Ubuntu:
  New

Bug description:
  Not 100% sure if this is a networkd bug or a nplan bug, but...

  On new install of 17.10 systemd-networkd loops with:

  Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
  Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
  Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:29

[Touch-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

2018-04-19 Thread sojusnik

Why is this another bug?

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2018-04-19 Thread Christopher M. Penalver

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

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  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:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support to initramfs-tools

2018-04-19 Thread Balint Reczey

** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-16.03 => ubuntu-18.04.1

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

Title:
  Add LZ4 support to initramfs-tools

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Original Bug Text
  =

  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

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

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

[Touch-packages] [Bug 1765451] [NEW] im trying

2018-04-19 Thread Dr.Robert Frew

Public bug reported:

im am new to this but am trying. thankyou

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Apr 19 11:40:16 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Core Processor Integrated Graphics Controller 
[104d:9071]
InstallationDate: Installed on 2009-01-01 (3395 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Sony Corporation VPCEB3KFX
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=62bd1ac0-0e27-483e-9dd9-5b13196e0971 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 08/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y8:bd08/17/2010:svnSonyCorporation:pnVPCEB3KFX:pvrC6069R1G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEB3KFX
dmi.product.version: C6069R1G
dmi.sys.vendor: Sony Corporation
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.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
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
xserver.bootTime: Thu Apr 19 10:07:52 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful compiz-0.9 i386 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/1765451

Title:
  im trying

Status in xorg package in Ubuntu:
  New

Bug description:
  im am new to this but am trying. thankyou

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 19 11:40:16 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Core Processor Integrated Graphics Controller 
[104d:9071]
  InstallationDate: Installed on 2009-01-01 (3395 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Sony Corporation VPCEB3KFX
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=62bd1ac0-0e27-483e-9dd9-5b13196e0971 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 08/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1100Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias:

[Touch-packages] [Bug 34629] Re: Left-click clears PRIMARY buffer selection (Copy-paste with middle-button/mouse wheel fails)

2018-04-19 Thread Bug Watch Updater

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

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

Title:
  Left-click clears PRIMARY buffer selection (Copy-paste with middle-
  button/mouse wheel fails)

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Left-click clears the visible selection *and* PRIMARY buffer contents,
  rather than just clearing the visible selection.  This means that a
  user middle-click pasting finds the text has been dropped and that
  they can't paste what they expected to paste without going back and
  reselecting in the previous application again.

  1) Select some text.
  2) Click somewhere on the document.
  3) Click mouse wheel.

  Using the PRIMARY mechanism, text should be pasted like it works
  elsewhere in X. However, nothing is pasted in gedit.

  Using the CLIPBOARD mechanism, Ctrl-C, ctrl-V copy-pasting seems to
  work within gedit, so this is unrelated.

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

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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

2018-04-19 Thread Dirk F

If the swapfile is available as the initrd is handing over to the real
system, then it should work (in Bionic and fixed versions back probably
beyond Xenial).

What would happen is something like this:

- Grub[2] is loaded from yr /boot, an unencrypted partition or perhaps a
USB stick

- Grub loads the initial ram disk (named initrd* but an initramfs in
recent Linuxes) image which is responsible for loading the actual system

- the initrd discovers your physical, logical and encrypted disk devices
and will attempt to chain to the "actual" boot device as specified in
/boot/grub/grub.cfg ("the system disk")

- in this process you have to supply your passphrase or keyfile or token
to allow the encrypted system disk to be mounted

- finally the initrd morphs into the system on the system disk.

When resuming from hybrid-sleep (s2both) or hibernation, it is the
initrd script /scripts/local-premount/resume, copied to the initrd from
/usr/share/initramfs-tools by update-initramfs, that parses the resume
and resume_offset kernel parameters from the grub.cfg linux command
line. Those parameters may have been entered by hand or by an add-on
script in /etc/default/grub (in which case update-grub would be needed
to add the parameters).

The initrd resume script, which runs in a environment where all the
kernel command-line parameters are available as shell variables, has to
translate the resume parameters into a major:minor[:offset] format that
is understood by the kernel when written to /sys/power/resume.

If the resume parameters are set, the resume script will have to mount
the system disk to verify whether there is a resumable image, and that
should trigger the password prompt/use of keyfile or token. You can
debug the resume script using the break=premount kernel command-line
setting, which leaves you in a limited Busybox shell just before the
script would run (Ctrl+D to continue booting).

If the initrd kernel succeeds in loading the resumable image, it will be
directly overlaid by the image and you will get a running system as it
was when hibernated/hybrid-slept. If not, it will become a newly started
system from the root of the encrypted system disk.

When initiating hibernate or hybrid-sleep, the kernel knows about your
swapfile and will use it automatically (if it's big enough and there is
enough free memory to prepare the image) through the sys/power
interface. If your swapfile is on the encrypted system disk (or another
encrypted disk), it will automatically be protected.

In systemd versions, a small binary (why?) invokes the necessary
commands (printf "suspend|platform|shutdown"> /sys/power/disk; printf
"disk"> /sys/power/state) driven by sleep.conf(5); before that the pm-
utils kernel method attempted to do the same. It might seem logical to
stash the resume info at this point, but that's not what happens: would
you want a failed hibernation to destroy your grub.cfg?

This series of processes doesn't seem to be clearly laid out anywhere
but I thought it worth recording in case anyone wanted to implement
swapfile hibernation on pre-Bionic versions.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Incomplete

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

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

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

[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:GI_libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

2018-04-19 Thread Balint Reczey

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
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/ubuntu/+source/python-apt/+bug/1737441/+subscriptions

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-04-19 Thread Andreas Hasenack

Some troubleshooting I did with Trent today showed:

a) the "host -t soa local." call triggered a query to 127.0.0.53 as
expected, network-wise, which got a response right away

b) we snapshotted ip route and ip addr just before the host call, and
saw that the interface responsible for the default route (and route to
his dns server) was still down. I wonder if dns_reachable() in
/usr/lib/avahi/avahi-daemon-check-dns.sh is doing the right thing. It
looks for 127.0.0.1 (and not 127.0.0.53), and, failing that, for a
default route. The default route exists, but the link it goes through is
still down:

2: eno1:  mtu 1500 qdisc fq_codel
state DOWN group default qlen 1000

default via x.x.x.x dev eno1 onlink linkdown

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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

[Touch-packages] [Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login

** Branch linked: lp:~ubuntu-desktop/gnome-session/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/1764355

Title:
  Visual Studio Code, Slack and other electrons apps crash due to
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu1

---
gtk+3.0 (3.22.30-1ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
+ Install a settings.ini file to set our themes
+ Update debian/libgtk-3-0.symbols
+ debian/control.in:
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
  - box-shadow-changes-modify-clip.ui
  - label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch
  - gtksocket-unscale-before-sending-configurenotify.patch
  * New release includes fix for crash on container unrealize
(LP: #1759468, #1764548)

gtk+3.0 (3.22.30-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * Drop patches applied in new release (numbered 0009-0016)

  [ Simon McVittie ]
  * d/p/022_disable-viqr-im-for-vi-locale.patch:
Add reference to Ubuntu bug 191451, summarize the reason why this
is applied, and correctly attribute the patch to Ming Hua
(see #895043)

 -- Jeremy Bicha   Mon, 16 Apr 2018 20:23:45 -0400

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions

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

[Touch-packages] [Bug 1764548] Re: Update gtk+3.0 to 3.22.30 for bionic

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu1

---
gtk+3.0 (3.22.30-1ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
+ Install a settings.ini file to set our themes
+ Update debian/libgtk-3-0.symbols
+ debian/control.in:
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
  - box-shadow-changes-modify-clip.ui
  - label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch
  - gtksocket-unscale-before-sending-configurenotify.patch
  * New release includes fix for crash on container unrealize
(LP: #1759468, #1764548)

gtk+3.0 (3.22.30-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * Drop patches applied in new release (numbered 0009-0016)

  [ Simon McVittie ]
  * d/p/022_disable-viqr-im-for-vi-locale.patch:
Add reference to Ubuntu bug 191451, summarize the reason why this
is applied, and correctly attribute the patch to Ming Hua
(see #895043)

 -- Jeremy Bicha   Mon, 16 Apr 2018 20:23:45 -0400

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gtk+3.0 to 3.22.30 for bionic

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  New upstream bugfix release in the stable 3.22.x series.

  gtk3 is part of the GNOME microrelease exception. (For Ubuntu 17.10,
  we did an earlier gtk3 point release SRU using the GNOME microrelease
  exception.)

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.29...3.22.30

  Testing Done
  
  Built successfully on amd64. Apps seem to run ok after installing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1764548/+subscriptions

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

Re: [Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2018-04-19 Thread Balan Cosmin Tudorel

Tanks

On Tue, Apr 17, 2018 at 4:16 PM, Simon Déziel <1732...@bugs.launchpad.net>
wrote:

> It's already mentioned in the NEWS file but for those who would like to
> test the seccomp sanbox, all that's needed is:
>
>   APT::Sandbox::Seccomp "true";
>
> Thanks Julian
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1756652).
> https://bugs.launchpad.net/bugs/1732030
>
> Title:
>   'apt update' dies with seccomp error
>
> Status in apt package in Ubuntu:
>   Fix Released
> Status in libvirt package in Ubuntu:
>   Fix Released
>
> Bug description:
>   $ apt-get update
>   0% [Working]
> Seccomp prevented execution of syscall 78 on architecture
> amd64 
>   Reading package lists... Done
>   E: Method mirror has died unexpectedly!
>   E: Sub-process mirror returned an error code (31)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: apt 1.6~alpha5
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
>   ApportVersion: 2.20.7-0ubuntu4
>   Architecture: amd64
>   Date: Mon Nov 13 23:10:57 2017
>   ProcEnviron:
>LANGUAGE=en_US:en
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/zsh
>   SourcePackage: apt
>   UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+subscriptions
>

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

2018-04-19 Thread Łukasz Zemczak

I was just saying that if the decision was made to keep xkb-keymap then
there had to be a decision to start using it implicitly in ubiquity. And
by 'using' I didn't just mean the literal sense of us using the value
explicitly, but acting accordingly to what consequences it brings - as
it requires us to do one of the two as you mentioned in your post. So I
don't think there's much of a misunderstanding here. It's all good and I
guess for the next merge we should proceed with adjusting things so that
ubiquity is happy with the changes.

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Touch-packages] [Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login

2018-04-19 Thread Didier Roche

** Also affects: xorg (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/1764355

Title:
  Visual Studio Code, Slack and other electrons apps crash due to
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

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

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

  * debian/patches/fix-default-permissions.patch: fix default permissions
when creating the log directory. (LP: #1735929)

 -- Marc Deslauriers   Fri, 13 Apr 2018
11:31:45 -0400

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

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Fix Released
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in session-migration package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Released
Status in session-migration source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

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

[Touch-packages] [Bug 1765380] Re: Bionic: busybox sh preseed/late_command

If I'm using xenial and in pressed file bionic it's NOT working

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

Title:
  Bionic: busybox sh preseed/late_command

Status in busybox package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
  initrd.gz  2018-04-18 09:13 45M
  linux  2018-04-18 09:13 7.9M

  busybox:
Installed: 1:1.27.2-2ubuntu3

  
  3+4) preseed installation on Bionic, late_command almost the same in Xenial 
and there is working

  preseed.cfg
  d-i preseed/late_command  string  /tmp/late_command

  ls -l /bin/sh
  lrwxrwxrwx 1 root root 4 Sep 26  2014 /bin/sh -> busybox

  syslog:
  running: /tmp/late_command

  nothing happend on shell:
  /tmp/late_command

  head late_commaand
  #!/bin/sh
  printf '' > /usr/lib/finish-install.d/55netcfg-copy-config;

  in-target mkdir -p /opt/MegaRAID/MegaCli/;
  in-target mkdir -p /root/.ssh;
  in-target mkdir /etc/check_mk;

  So is there a bug in busybox sh?
  How can I debug busybox sh script.sh?

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

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

[Touch-packages] [Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

Also tried putting `gtk-toolbar-style = GTK_TOOLBAR_BOTH` in
~/.gtkrc-2.0 and `[Settings]\ngtk-toolbar-style = GTK_TOOLBAR_BOTH` in
~/.config/gtk-3.0/settings.ini. The latter causes the output of gtk-
query-settings to change, but neither of these settings causes GnuCash
to behave differently.

Also tried creating ~/.gtkrc-2.0.gnucash and putting the same contents
as for ~/.gtkrc-2.0. Didn't help.

When I run strace on gnucash, it shows that it is reading both
~/.gtkrc-2.0.gnucash and ~/.gtkrc-2.0.

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

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions

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

[Touch-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

2018-04-19 Thread Mathieu Trudel-Lapierre

There was a misunderstanding there: I never suggested we should use xkb-
keymap instead (or at least, that's not the message I was trying to
convey).

The intent was to reduce delta by not removing so much code, when
console-setup merges are already difficult. I didn't foresee that some
of that code setting a default would impact ubiquity (because ubiquity
does things specially with d-i components, sometimes running them
multiple times). There's always a need to update ubiquity after changing
d-i components; it's inevitable since some of them are embedded in
ubiquity source.

The removals of xkb-keymaps aren't ubiquity-specific: we don't use this
code in d-i, and instead use multiple screens to change keyboards.
That's a conscious decision.

The point for supporting xkb-keymap "in ubiquity" is more about making
sure that we either "rebuild" the value based on layoutcode/variantcode,
or otherwise unset it before running the configuration script -- ie.
leave it in, but just explicitly ignore its values.

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Touch-packages] [Bug 1765380] Re: Bionic: busybox sh preseed/late_command

If I'm using xenial and in pressed file bionic it's working

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

Title:
  Bionic: busybox sh preseed/late_command

Status in busybox package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
  initrd.gz  2018-04-18 09:13 45M
  linux  2018-04-18 09:13 7.9M

  busybox:
Installed: 1:1.27.2-2ubuntu3

  
  3+4) preseed installation on Bionic, late_command almost the same in Xenial 
and there is working

  preseed.cfg
  d-i preseed/late_command  string  /tmp/late_command

  ls -l /bin/sh
  lrwxrwxrwx 1 root root 4 Sep 26  2014 /bin/sh -> busybox

  syslog:
  running: /tmp/late_command

  nothing happend on shell:
  /tmp/late_command

  head late_commaand
  #!/bin/sh
  printf '' > /usr/lib/finish-install.d/55netcfg-copy-config;

  in-target mkdir -p /opt/MegaRAID/MegaCli/;
  in-target mkdir -p /root/.ssh;
  in-target mkdir /etc/check_mk;

  So is there a bug in busybox sh?
  How can I debug busybox sh script.sh?

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

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

[Touch-packages] [Bug 1765401] [NEW] gtk+ toolbar style setting ignored in bionic?

Public bug reported:

I like big buttons with text labels below them in GnuCash toolbars.

Fortunately, that's exactly what I had in Ubuntu 17.10.

However, having upgraded to 18.04 this morning, suddenly the GnuCash
toolbars are back to being small buttons with no text labels.

There are SO MANY PLACES to set this preference, and yet, it's not
working:

$ gconftool-2 --search-key-regex toolbar
 /desktop/gnome/interface/toolbar_style = both
 /desktop/gnome/interface/toolbar_detachable = false
 /desktop/gnome/interface/toolbar_icons_size = large-toolbar
$ gconftool --search-key-regex toolbar
 /desktop/gnome/interface/toolbar_style = both
 /desktop/gnome/interface/toolbar_detachable = false
 /desktop/gnome/interface/toolbar_icons_size = large-toolbar
$ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
toolbar-style='both'
$ gtk-query-settings | grep toolbar
! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

I have no idea why that last one says "both-horiz" rather than "both". I
honestly have no idea where that setting is coming from and can't find
any way to find out. (I even tried running strace on gtk-query-settings
to see what it was reading, and that didn't help.)

I can't find any way to change this setting in gnome-tweaks.

Is the ability to have large icons with text below them simply gone in
18.04, or has the setting migrated to yet another location that I have
to set it in now (it seems like Ubuntu and/or GNOME decides to move
settings to a completely new backend just for the heck of it every few
releases).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgtk2.0-bin 2.24.32-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 19 08:46:15 2018
InstallationDate: Installed on 2016-01-16 (824 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gtk+2.0
UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions

-- 
Mailing list:

[Touch-packages] [Bug 1765380] Re: busybox sh preseed/late_command

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

** No longer affects: linux-firmware (Ubuntu)

** Summary changed:

- busybox sh preseed/late_command
+ Bionic: busybox sh preseed/late_command

** Tags added: netinstall

** Description changed:

- 1) lsb_release -rd 
+ 1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
- 2) apt-cache policy busybox
- busybox:
-   Installed: 1:1.27.2-2ubuntu3
+ 2) 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
+ initrd.gz  2018-04-18 09:13 45M
+ linux  2018-04-18 09:13 7.9M
  
  3+4) preseed installation on Bionic, late_command almost the same in
  Xenial and there is working
  
  preseed.cfg
  d-i preseed/late_command  string  /tmp/late_command
  
  ls -l /bin/sh
  lrwxrwxrwx 1 root root 4 Sep 26  2014 /bin/sh -> busybox
  
- syslog: 
+ syslog:
  running: /tmp/late_command
  
  nothing happend on shell:
  /tmp/late_command
  
  head late_commaand
  #!/bin/sh
  printf '' > /usr/lib/finish-install.d/55netcfg-copy-config;
  
  in-target mkdir -p /opt/MegaRAID/MegaCli/;
  in-target mkdir -p /root/.ssh;
  in-target mkdir /etc/check_mk;
  
  So is there a bug in busybox sh?
  How can I debug busybox sh script.sh?

** Description changed:

  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  2) 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
  initrd.gz  2018-04-18 09:13 45M
  linux  2018-04-18 09:13 7.9M
  
- 3+4) preseed installation on Bionic, late_command almost the same in
- Xenial and there is working
+ busybox:
+   Installed: 1:1.27.2-2ubuntu3
+ 
+ 
+ 3+4) preseed installation on Bionic, late_command almost the same in Xenial 
and there is working
  
  preseed.cfg
  d-i preseed/late_command  string  /tmp/late_command
  
  ls -l /bin/sh
  lrwxrwxrwx 1 root root 4 Sep 26  2014 /bin/sh -> busybox
  
  syslog:
  running: /tmp/late_command
  
  nothing happend on shell:
  /tmp/late_command
  
  head late_commaand
  #!/bin/sh
  printf '' > /usr/lib/finish-install.d/55netcfg-copy-config;
  
  in-target mkdir -p /opt/MegaRAID/MegaCli/;
  in-target mkdir -p /root/.ssh;
  in-target mkdir /etc/check_mk;
  
  So is there a bug in busybox sh?
  How can I debug busybox sh script.sh?

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

Title:
  Bionic: busybox sh preseed/late_command

Status in busybox package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) 
http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
  initrd.gz  2018-04-18 09:13 45M
  linux  2018-04-18 09:13 7.9M

  busybox:
Installed: 1:1.27.2-2ubuntu3

  
  3+4) preseed installation on Bionic, late_command almost the same in Xenial 
and there is working

  preseed.cfg
  d-i preseed/late_command  string  /tmp/late_command

  ls -l /bin/sh
  lrwxrwxrwx 1 root root 4 Sep 26  2014 /bin/sh -> busybox

  syslog:
  running: /tmp/late_command

  nothing happend on shell:
  /tmp/late_command

  head late_commaand
  #!/bin/sh
  printf '' > /usr/lib/finish-install.d/55netcfg-copy-config;

  in-target mkdir -p /opt/MegaRAID/MegaCli/;
  in-target mkdir -p /root/.ssh;
  in-target mkdir /etc/check_mk;

  So is there a bug in busybox sh?
  How can I debug busybox sh script.sh?

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

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

[Touch-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

This bug was fixed in the package console-setup - 1.178ubuntu2

---
console-setup (1.178ubuntu2) bionic; urgency=medium

  * debian/keyboard-configuration.config:
- Drop the xkb-keymap bits once again as we're not ready for those yet, as
  it's currently causing an invalid default layout in the installer.
  (LP: #1758647)

 -- Łukasz 'sil2100' Zemczak   Thu, 19 Apr
2018 08:53:32 +0200

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

2018-04-19 Thread Sean Davis

I just tried using the netboot iso and installed the Xubuntu Desktop
task. Once installation finished and rebooted, I have a pristine Xubuntu
desktop with no additional indicators.

dpkg -l listing attached.

I will try another mini iso without a selected desktop if possible.

** Attachment added: "dpkg after Xubuntu Desktop task installation"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1754872/+attachment/5122515/+files/dpkg_output.txt

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-19 Thread ChristianEhrhardt

Fix for chrony (following networkd-dispatcher change in bug 1765152)
uploaded to bionic-unapproved as 3.2-4ubuntu4

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

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

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

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

2018-04-19 Thread Guilherme G. Piccoli

As mentioned by Dan in the above comments, some failures in autopkgtest
like:

autopkgtest [14:44:48]: test ubuntu-regression-suite: [---
Source Package Version: 4.4.0-1017.17
Running Kernel Version: 3.13.0-145.194
ERROR: running version does not match source package

Are "expected" due to LP #1723223.

Other than that, the proposed package passed in all other tests.
Thanks,

Guilherme

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

[Touch-packages] [Bug 1764474] Re: software-properties-gtk should not store the goa account-id used for livepatch in the keyring.

This bug was fixed in the package software-properties - 0.96.24.32.1

---
software-properties (0.96.24.32.1) bionic; urgency=medium

  * debian/control.in:
- Build-Depends on dh-migrations to fix the build

 -- Sebastien Bacher   Wed, 18 Apr 2018 16:50:03
+0200

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-gtk should not store the goa account-id used for
  livepatch in the keyring.

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  There is no need to store the goa account id in the keyring. gsettings
  should be enough.

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

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

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

2018-04-19 Thread Apport retracing service

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

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 #1754214, 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/1765369/+attachment/5122478/+files/CoreDump.gz

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

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

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

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

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

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

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

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't now

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:14 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-04-13 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 12
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.2-041602-generic 
root=UUID=b92b3da2-3d38-4200-a28c-5ac569f24583 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=140306407802624, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  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 __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02HAC.004.170626.WY.1442
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W720NZKAXEF
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8766A4G-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKAXEF:rvrSGL8766A4G-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 12
  dmi.product.version: P02HAC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1765196] Re: 4.4.0-119-generic boot error - systemd[1]: Failed to start Load Kernel Modules.

2018-04-19 Thread Galen Thurber

I did know that I had reported it as an apt problem.

Trying other kernels

linux-image-4.4.0-116-generic
linux-image-4.4.0-98-generic
both have the same issue as 119


however these work (loads video and wifi)
linux-image-4.4.0-116-lowlatency 
linux-image-4.4.0-98-lowlatency

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

Title:
  4.4.0-119-generic boot error - systemd[1]: Failed to start Load Kernel
  Modules.

Status in systemd package in Ubuntu:
  New

Bug description:
  Boot up errors.
  System is reporting
  dmesg error
  # systemd[1]: Failed to start Load Kernel Modules.

  Video and WIFI are affected.
  Hard drive is not full.

  
  Xubuntu 16.04 LTS
  lsb_release
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch

  
  Reinstalling kernel via synaptic does not fix the problem

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low